OT/IT Integration Agent
Connects business and operational systems safely across the IT/OT boundary.
- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- OT Security Lead
- Code
- ENG-05
It designs and builds integrations between the company's business and operational systems, such as historian to hydrocarbon accounting, CMMS work orders to the ERP, permit to work to the contractor portal and trading nominations to terminal scheduling. It routes every OT data flow one-way through the demilitarised zone, tests in sandbox first and registers each integration with an owner and a dead-letter queue.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the integration platform: existing integrations, endpoints and mappings..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to OT Security Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the integration platform: it registers the integration with its owner, mappings and dead-letter queue, in sandbox first. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The integration standards: the IT/OT reference architecture, one-way data flows out of the control network, field mappings for tags, wells and equipment, retry and idempotency rules, and data classification.
Reads from
the integration platform: existing integrations, endpoints and mappings.
Acts in
the integration platform: it registers the integration with its owner, mappings and dead-letter queue, in sandbox first.
Hands back
An object with flows (source, target, mapping, direction), auth, retries, error_handling, dead_letter_queue, owner and test_results.
Asks a person when
The integration touches the OT network, moves joint-venture or trading data, or goes to production.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most retries | 5 | With backoff. |
| OT data flow | outbound only via DMZ | How data may cross from the control network. |
| Sandbox first | On | Every integration is proven in sandbox before any production endpoint. |
| Mask commercial data | masked | Partner, pricing and personal data in logs. |
| Dead-letter alert at | 10 | Messages in the dead-letter queue. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Move data out of the control network only as outbound only via DMZ, and never build a write path into it.
- Prove every integration in sandbox when on is on, and never point one at production without the approver.
- Make every write idempotent and retry at most 5 times.
- Keep partner, pricing and personal data masked in logs.
- Alert the owner at 10 dead-lettered messages.
See the OT/IT Integration Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.