Files

T

Joseph Doherty 7dc30085be docs(api-specs): capture the as-deployed DelmiaRecipeDownload contract from prod vd03 (method, site handshake, keys, observed calls); link from the legacy dnc spec

Claude-Session: https://claude.ai/code/session_013L3XdmVii9i5sY4FChU8pB

2026-09-02 12:43:21 -04:00

dnc

docs(api-specs): capture the as-deployed DelmiaRecipeDownload contract from prod vd03 (method, site handshake, keys, observed calls); link from the legacy dnc spec

2026-09-02 12:43:21 -04:00

mes

docs: former-api-specs (MES + DNC/Delmia) + inbound compile-error known issue

2026-06-26 04:13:19 -04:00

README.md

docs(api-specs): capture the as-deployed DelmiaRecipeDownload contract from prod vd03 (method, site handshake, keys, observed calls); link from the legacy dnc spec

2026-09-02 12:43:21 -04:00

README.md

Former API Specs

Reference specifications for the predecessor / legacy APIs that ScadaBridge replaces or interoperates with. These are not ScadaBridge's own contracts — they are kept here as historical reference when porting integrations onto ScadaBridge's Inbound API (#14) and External System Gateway (#7), and for parity-checking behavior during cutover.

ScadaBridge's own component design docs live under docs/requirements/; this folder holds only the outgoing/legacy systems' specs.

Subfolders

mes/ — the legacy MES API (ServiceStack "WWSupport / APIServer", a.k.a. mesapi) that bridges MES ↔ AVEVA Wonderware via MXAccess. Source repo: ~/Desktop/mesapi.
dnc/ — the legacy DNC integration: DELMIA Apriso document/recipe download + Wonderware recipe-download notification (~/Desktop/delmiaintegration).

Drop the relevant spec documents into the matching subfolder.

ScadaBridge's own externally-called contracts, captured as deployed, live in ../api-specs/.