Ignition
Use exposed gateway data to investigate process events alongside batch records.
Put this connection to work Read the platform connection docs
Investigate a process event. Use the permitted Ignition records and show me the supporting evidence.
Compare exposed process observations with the relevant batch timeline.
Data returned by approved gateway and module routes in your Ignition installation.
Investigate a process event
- Findings linked to source records
- Missing evidence and unresolved questions
- Follow-up work for your team
What’s connected.
Use exposed gateway data to investigate process events alongside batch records. Scope an API integration so neil can use the permitted records to prepare analysis, reports and follow-up work.
Connection setup and permissions
Ignition 8.3 exposes a gateway OpenAPI specification. Select read-only routes from the installed modules; additional process-data endpoints may require gateway configuration. This does not grant control of equipment.
This is an API integration option to scope and implement, not a ready-made Seal connector. Start with read access; any source-system changes need separately configured actions and controls.
What could neil do with Ignition?
Once the relevant API access and data mappings are configured:
- Investigate a process event
- Compare exposed process observations with the relevant batch timeline.
- Prepare a gateway review
- Summarise selected diagnostic information for the automation team.
- Collect operational evidence
- Attach the returned data and its retrieval context to an investigation draft.
Connection questions.
Will this work with our Ignition environment?
We check your product edition, API availability, authentication and permitted records against the job you want neil to do. The linked provider documentation describes the interface; it does not mean a connection is already installed in Seal.
Before it goes live.
Access and write-back
Reading records and writing back are separate decisions. Define which records are in scope, whose permissions apply and which changes require approval.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.