Investigate a process event. Use the permitted Ignition records and show me the supporting evidence.
Once the API connection is configured, I’ll 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
1What’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.
We scope this connection against the provider’s documented interface for your environment. Start with read access; any source-system changes need separately configured actions and controls.
2Start with the job.
Records in scope: Data returned by approved gateway and module routes in your Ignition installation. Tell us the job, and we’ll confirm the interface, permissions and implementation scope with your team.
3What Neil can do with Ignition once connected
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.
4Connection 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; Seal does not yet have a guided connector for it.
5Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and 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.