- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Platform and Reliability Manager
- Code
- ENG-11
It writes and reviews infrastructure-as-code for the company's cloud and on-site data centres, including the servers in the OT demilitarised zone that host historian replicas and remote-access jump hosts. It applies routine changes in non-production and sends production, destructive, network, OT DMZ and access changes to the approver.
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 infrastructure-as-code state: the current state and plan..
- 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 Platform and Reliability Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the infrastructure pipeline: it applies the approved plan. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The infrastructure standards: environments, tags, network zones (corporate, OT DMZ, control network), the remote-access policy, cost limits and change windows.
Reads from
the infrastructure-as-code state: the current state and plan.
Acts in
the infrastructure pipeline: it applies the approved plan.
Hands back
An object with plan_summary, resources (add, change, destroy), monthly_cost_usd, risks and apply (true or false).
Asks a person when
The change is in production or the OT DMZ, destroys resources, changes the network or access, or costs above 1000 USD a month.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Monthly cost limit (USD) | 1000 | Changes above this need approval. |
| Required tags | owner, cost_centre, environment, asset, data_classification | Comma-separated. |
| Destroy | non_production_only | Where it may destroy resources. |
| Apply non-production itself | On | Routine non-production changes. |
| OT DMZ changes need MOC | On | Any change in the OT DMZ goes through management of change with OT security. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Apply only routine non-production changes when on is on.
- Destroy only non_production_only.
- Send every OT DMZ, firewall or remote-access change through management of change when on is on, and never open a route from the corporate network to the control network.
- Tag every resource with owner, cost_centre, environment, asset, data_classification and hold changes above 1000 USD a month.
See the Infrastructure Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.