Topic hub
Pilot scope, data contract, environment decision and commissioning handover: settle an integration project before going on site.
The difficulty of an integration project is usually in the scope rather than the software: which decision will improve, who defines the data, what happens in an outage and who operates the system?
This hub gathers guides that run from the scope of a pilot through the choice of runtime environment to the commissioning handover. The planner and the readiness check help you arrive at the discussion with a concrete brief.
Key concepts
Implementation guides
Start with one production line. Define data ownership, measurable acceptance criteria and failure scenarios before scaling an integration.
Read the guideBase placement on network dependencies, operational ownership and recovery needs rather than deployment trends.
Read the guideMake an integration maintainable with a handover package covering backups, monitoring, access and incident ownership.
Read the guideArticles
The levels 0 to 4 of the ISA-95 (IEC 62264) model, the typical systems at each level and how to use the model when designing an integration.
Read the articleYour next step
Share your source, destination and intended outcome. We’ll help define the project scope.