Allow-list
An agent can only write to tags declared for it, through approved DCS or APC interfaces.
Nitreum is designed around three facts: ammonia is safety-critical, recipes and process settings are intellectual property, and the plant's existing automation and safety systems must keep running if Nitreum stops. This page is the design posture; certifications are on the roadmap and not claimed.
Illustrative scenario: Complex run · one urea granulation campaign from synthesis gas to bagged lot · ammonia loop, urea synthesis and evaporation, granulator, dryer and cooler, NPK bagging line. Not a measured run.
An agent can only write to tags declared for it, through approved DCS or APC interfaces.
Per-tag rate and magnitude limits, declared and versioned, inside documented recipe, quality, safety, emissions, equipment and rollback bounds.
Shadow, assist or bounded, set per loop; nothing writes in shadow; every ammonia-loop stage is safety-gated.
Safety envelope, interlock state, grade, shift and operator presence evaluated before every write; moves that violate a process-safety or emissions control are blocked.
Anything above the threshold, every safety-adjacent move and every release waits for a named person; ammonia-loop moves beyond the envelope wait for a process engineer and a process-safety approver.
If Nitreum stops, the plant runs on its existing DCS, APC and safety systems.
Every tool invocation, argument and result is written to an immutable, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the plant. The log below is the scenario run, not a measured one.
Goal, plan, thought, action, observation, exactly as the orchestrator would record it.
Run campaign U-4471 from synthesis gas to bagged lot: ammonia loop at target conversion per unit of energy, melt at exact concentration, granules on spec with minimum dust and recycle, conditioned for storage, bagged to weight and released with full genealogy and emissions readings.
Simulate the whole campaign on the twin first. Lead with conversion so evaporation gets the right melt and the granulator gets the right concentration. Verify emissions and the safety envelope continuously. Let the granulator chase the size band only inside the approved window; hold any ammonia-loop move beyond the envelope for a human.
The standing practice runs the loop and the granulator on fixed setpoints and corrects after the assay. With live conversion, concentration and granule distribution the loop and the granulator can sit at target. The saving is energy, recycle and dust, not safety margin: the safety-instrumented envelope and the permit limits are never candidates for optimization.
twin.simulate(candidates=24) → plan #9: conversion on target, melt concentration on spec, granule distribution inside the band, permit margin unchanged, lowest predicted energy per tonne.
Plan #9 wants a purge-rate change on the ammonia loop beyond the bounded envelope. The policy engine routes that single move to the shift process engineer and the process-safety approver and permits the other seven writes.
Execute plan #9 at the bounded stage: loop temperature, evaporator, granulator, coating and blend writes proceed; emissions are verified continuously; the purge move waits.
Approval granted at 06:05:06 with a smaller step and the safety-instrumented envelope untouched. Two dust spikes were attributed to spray nozzle 3 and corrected by Granulate-and-Prill inside the approved window.
Scenario complete. The lot is released with conversion and energy per tonne, melt concentration, granule distribution, nutrient assay, emissions readings and the human decision in the genealogy. No measured plant result is claimed; this is the run the platform is designed to execute.
Nitreum writes to production equipment in a plant that handles ammonia. Every capability is scoped, every write is policy-checked, every output is cited, and every action is written to an append-only audit log the plant owns.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I readiness | Cloud control plane | QUEUED Roadmap, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Roadmap, 6 to 12 months |
| Process-safety and emissions procedures | Grounding and record-keeping | RUNNING Design basis for retrieval and the audit log |
| Per-tenant isolation | Data, memory, models | RUNNING Design rule |
| On-prem and plant-edge deployment | IP- and safety-sensitive sites | RUNNING Design option |
Nitreum supports your process-safety, quality and emissions records. It is not a certification and it does not replace your safety program or management of change.
A plant does not go from manual to bounded control in one step. Nitreum makes the stage explicit per loop, auditable and reversible at any time, and some decisions never leave the person. On the ammonia side every stage is safety-gated.
| Stage | What the agent does | What the person does | When |
|---|---|---|---|
| Shadow | Predicts conversion, concentration, granule quality, nutrient content, energy, emissions and off-spec risk; writes nothing | Runs the plant as today; compares predictions to assay, historian and engineer outcomes | First phase with every design partner |
| Assist | Recommends bounded loop, evaporation, granulation, coating and blend moves with the evidence | A process engineer approves or rejects each one | After accuracy is proven against the baseline |
| Bounded | Writes low-risk granulation, conditioning and blending setpoints inside documented recipe, quality, safety, emissions, equipment and rollback limits | Approves anything above the limits and every ammonia-loop move beyond the envelope; reviews the shift record | After the safety and ROI gates agreed up front |
| Exceptions | Escalates anything outside its envelope, safety-adjacent moves and release decisions | Always decides these; the agent never does | Permanent |
Stated plainly. Items on the roadmap are roadmap items.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I readiness | Cloud control plane | QUEUED Roadmap, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Roadmap, 6 to 12 months |
| Emissions and safety assurance packages | Design partners | QUEUED Roadmap, 6 to 12 months |
| Process-safety and emissions procedures, standards | Grounding and records | RUNNING Design basis; not a certification of Nitreum |
| IP-safe and plant-edge deployment | Recipes, process settings, safety records | RUNNING Design rule; on-prem option |
| Data | Where it stays |
|---|---|
| Recipes, process settings, product and emissions models | Tenant-scoped; on-prem option |
| Feedstock, catalyst and supplier data | Tenant-scoped |
| Audit log and lot genealogy | The plant's own storage, exportable |
| Rare-upset and drift patterns | Federated, IP-isolated transfer across similar units (planned, opt-in) |
Two agents will want the same actuator. The orchestrator arbitrates on the run goal, with process safety above everything, and the handoff is logged like any other step.
Yield-and-Takt wants a lower purge rate on the ammonia loop so less hydrogen is lost and energy per tonne falls for the campaign.
Reform-and-Synthesize requires the purge rate that keeps inerts inside the loop envelope the process-safety review approved. That envelope is not an optimization variable.
Process safety outranks energy under every run goal. The envelope wins the actuator; the request for a lower purge is logged with its score and the reason it lost, and a smaller step is routed to a named approver.
Yield-and-Takt recovers the energy target by shifting the dryer duty and the changeover window instead. Takt is met without touching the loop envelope.
One policy model, one audit trail and one set of yield, energy, emissions and granule-quality benchmarks across every complex in the group, with each site's recipes, process settings and emissions models kept private to that site.
The questions complex operations managers, process engineers and HSE leads ask in the first meeting.
Only at the autonomy stage your plant has set, and only to an explicit allow-list of low-risk loops inside documented limits, through the approved DCS or APC interfaces. Every design partner starts in shadow mode, where Nitreum predicts and writes nothing. Assist mode follows, where a process engineer approves each recommendation. Bounded autonomy on granulation, conditioning and blending loops comes after the safety and ROI gates agreed up front.
Safety-instrumented systems, interlocks, trip settings and permit limits are not optimization variables. Nitreum reads and verifies them, writes them to an immutable audit log and never writes to them. Any ammonia-loop move outside the bounded envelope waits for a named process engineer and a process-safety approver, and management of change stays with your plant. Nitreum is grounded in your process-safety and emissions procedures; it is not a certification and does not replace them.
Nitreum sits above your existing automation as a supervisory layer. If it stops, the plant keeps running on its current DCS, APC and safety systems. A Nitreum outage degrades the plant to the way it runs today, not to a stop.
The first phase is shadow mode on one unit: Nitreum reads your historian, analyzers, emissions sensors, lab assays and MES while you run the plant as usual, and we measure its predictions against your assay, historian and engineer outcomes. Recommendations start when accuracy is proven against that baseline, and improve as site-specific history and engineer corrections accumulate.
Recipes, process settings, product and emissions models and plant IP are tenant-scoped and never used to train another customer's models. Retrieval is multi-tenant isolated and permission-aware. Cross-site learning, where a customer opts in, is federated and IP-isolated. On-prem and plant-edge deployment is available for sensitive sites.
You are, the same as with any control strategy. That is why every write is policy-checked, bounded, logged and reversible, every output carries a citation to the spec or procedure it relied on, and anything above your threshold waits for a named approver. The audit log records the request, the reasoning, the limits applied and the human decision.
As a design partner, on one unit, with one hard metric: energy per tonne on the ammonia loop, granule size distribution and moisture on a granulator, off-spec and recycle tonnes, or emissions variance. We instrument the unit in shadow mode, measure the baseline, move to assist mode when accuracy is proven, and expand only when the number holds.
Full multi-unit autonomy across the entire complex, long-tail integrations beyond the design partners' stacks, and self-serve onboarding. The first release is one wedge workflow, its connectors, the agent loop with human checkpoints, the review console and the assurance-grade quality, emissions and safety audit log.
The design posture, the data flows and the roadmap dates, written for an HSE lead, a process-safety engineer and an IT/OT lead.
↑↓ navigate↵ openesc close