Skip to content
View as markdown Ask ChatGPT Ask Claude

Validate and Go Live#

Validation Gates#

Complete and retain evidence for every applicable item before production release.

Gate 1 — Configuration Review#

  • The Industrial Equipment and Connect IoT and packages are deployed.
  • The Resource, hierarchy, process model, and state model are approved.
  • The server profile expected for each Resource is confirmed using the Profile Selection Rule.
  • Endpoint, credentials, certificate ownership, and trust responsibilities are recorded.
  • Namespace resolves the Resource tree and the generated IndEqOpcUaBaseNodeId is correct.
  • ConnectIoTRequestTimeout and MachineReplyTimeout are recorded and sized for the validated response paths.
  • The enabled feature scope and machine node inventory are approved.
  • Recipe, Data Collection, state mappings, parameter types, node ownership, and recovery behavior are documented.

Gate 2 — Connection#

  • The Automation Manager can reach the intended endpoint.
  • Authentication and certificate trust succeed.
  • The intended complete server profile is selected.
  • Namespace and IndEqOpcUaBaseNodeId resolve correctly.
  • Every required node can be browsed.
  • Read, write, and subscription permissions match the ownership matrix.
  • OPC UA data types match the interface definition.
  • Subscriptions receive controlled value changes.

Gate 3 — Feature Tests#

  • A normal machine-initiated transaction succeeds.
  • An operator-initiated transaction succeeds when the station is hybrid.
  • MES validation rejection leaves the performed signal inactive and does not commit the operation.
  • Invalid or missing machine payload produces the expected diagnostic.
  • A machine confirmation received before MachineReplyTimeout allows the operation to commit.
  • Suppressing the machine confirmation causes the command to fail after MachineReplyTimeout and the MES transaction to roll back.
  • The timeout scenario can be reconciled without repeating an uncertain physical action.
  • The handshake resets and the next valid cycle is detected once.
  • Recipe, Data Collection, and State behavior passes its feature-specific checklist.
  • Microstops and rapid state transitions are filtered before State values are published to MES.

Gate 4 — Recovery and Release#

Test in a controlled environment:

  • OPC UA disconnection before a request is detected and reported.
  • OPC UA disconnection during a pending handshake follows the approved reconciliation procedure.
  • A ConnectIoTRequestTimeout failure produces a clear diagnostic.
  • Certificate or credential rejection prevents the connection and reports the cause.
  • Restart performs the initial state synchronization and restores required subscriptions.
  • MES and physical machine state are reconciled before any retry.
  • Support ownership, escalation contacts, recovery steps, and collected evidence are approved.

Minimum End-to-End Test#

sequenceDiagram
    participant M as Machine
    participant I as Connect IoT
    participant E as Critical Manufacturing MES

    M->>I: Track In request and Material
    I->>E: Track In
    E-->>I: Success and Recipe
    I->>M: Recipe values and Track In performed
    M-->>I: Track In confirmed

    M->>I: Data Collection request and values
    I->>E: Store process reading
    E-->>I: Reading stored
    I->>M: Post Data performed

    M->>I: Track Out request
    I->>E: Track Out
    E-->>I: Success
    I->>M: Track Out performed
    M-->>I: Track Out confirmed