Mining AI agent · Safety & compliance
Safety & Compliance AI Agent (SWMS & Isolation)
Draft task-and-site-specific SWMS, assemble isolation points from the plant register, check permit packs and surface stale documents — while the issuing officer, isolation officer and statutory mine manager keep every signature.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Approval to work
- Named person
- After launch
- Agent Care
What this agent does
Prepares the paperwork, not the authorisation
In
- 01
Take the task, the work area, the plant and the crew from the work order, shutdown plan or permit request.
- 02
Read the site's own procedures, PHMPs, isolation standards, drawings and plant register at their current revision.
Reason
- 03
Draft the SWMS against this task and this work area, carrying the site's own control wording rather than a template's.
- 04
Assemble the isolation points for the job from the plant register and the P&IDs, including stored-energy sources.
- 05
Check the permit pack against the site's requirement list and name what is missing, unsigned or out of date.
Decide
- 06
Flag generic wording, isolation points nobody has verified at the plant, and documents that have gone stale.
- 07
Route what it cannot resolve to the supervisor, the isolation officer or the issuing officer named for that job.
Out
- 08
Present the SWMS draft, the candidate isolation list and the gap list — as drafts, with the sources beside them.
- 09
Retain every source read, the revision of each standard used, the rationale and every officer amendment.
Product statement
The agent drafts, assembles and checks. Permits, isolation certificates, risk-assessment sign-off and declaring an area safe stay with the named person.
Example workflow
One job, end to end
- 1Job receivedWork order, shutdown task, permit request or a change to plant or procedure
- 2Site standards readProcedures, PHMPs, isolation standards, drawings and the plant register at their current revision
- 3Pack draftedSWMS against this task and work area, candidate isolation points, permit pack checked against the requirement list
- 4Gaps markedGeneric wording, unverified isolation points, missing signatures, expired tickets and documents gone stale
No human action required
Stages 1 to 4 run without a person in the loop — reading, drafting and the gap list finish before anyone is asked to read anything. Nothing is issued in that stretch.
Reaches the officer as a complete draft.
Goes to the supervisor before it goes further.
Supervisor or issuing officer
Reads the draft, the candidate isolation list, the sources and the gaps, then decides whether to amend, refuse or sign.
Accept draft · Amend · Request review
Draft accepted — handed back
- 6Pack routed for signatureHanded to the named officer as a draft; no permit, certificate or lockout is issued by the agent
- 7Outcome evaluatedOfficer amendments, isolation points corrected at the plant, and what the audit found by cohort
Amendments
Wording an officer rewrites is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Issuing a permit to work or hot-work permit.
- Signing an isolation certificate or authorising a lockout.
- Authorising entry to a confined space.
- Clearing, removing or overriding an isolation or lockout.
Automation boundary
Agent acts unaided
- ✓Draft the SWMS against the task, the work area and the site's own standards.
- ✓Assemble isolation points from the plant register.
- ✓Check a permit pack against the site's requirement list.
- ✓Trace which documents a change to plant or procedure touches, and what has gone stale.
Write actions run only inside the approval boundaries agreed during implementation. A permit or certificate is never one.
- Bypassing an interlock, a guard or a protective device.
- Declaring an area safe or lifting an exclusion zone.
- Signing off a risk assessment or a SWMS.
- Changing a procedure, standard or isolation register.
Example output
One job pack, annotated
Everything the agent drafts is attached to the job and the document revision it came from.
Draft pack · one job, one shift
Illustrative example- Job as requested
- Conveyor gearbox change-out
- Work area
- Drive head, working at height
- Last SWMS
- Rev 4
- Drafted
- SWMS, isolation list
- Confidence
- 88%
- Permit
- Not issued by the agent
As received
The job, the work area and the SWMS the crew last used, taken as they arrived — nothing on this side is rewritten.
Evidence used
- Plant register, current rev
- Drive-head P&ID
- Working-at-height standard
Why it differs from rev 4
The drive head was re-piped since rev 4, so two points on that list are gone.
What the score decides
Confidence decides how hard the officer reads the draft, not whether the job may start.
Action
Accept draftAmendRequest reviewValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every job needing paperwork
Work order, shutdown task or change
Work to the site's own standards
Use the mine's procedures, PHMPs, isolation standards, drawings and plant register at the revision current for that shift.
Stop the template being the document
The draft starts from this task and this work area, so the officer's reading goes on whether the controls fit the job rather than on stripping a template back to it.
Put the gaps in front of a person first
Unverified isolation points, missing signatures and stale documents reach the supervisor before the pack reaches the issuing officer.
Build an evidence trail
Retain the sources read, the revision of each standard, the isolation points proposed, the confidence and every officer amendment — on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Safety management system
- Cintellate
- INX InControl
- Damstra
- Document control
Maintenance & plant register
- SAP PM
- Pronto
- Maximo
- Plant register
- asset hierarchy
Permits & isolation
- Permit-to-work systems
- tag boards
- Isolation registers
- lockout registers
Agent
Safety & compliance documentation
- Reads site standards
- Drafts the pack
- Routes for signature
Drawings & standards
- P&IDs
- single-line diagrams
- Procedure library
- PHMPs
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the permit pack
Each control wraps the one inside it. A draft clears every layer before an officer reads it, and the signature sits outside all six.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Decide whether the draft may stand
- L3
- Decides what a person confirms at the plant
- L4 – L5
- Keep the signature with a person and the record intact
- L6
- Pulls automation back when signals degrade
How Nestack evaluates it
Evaluate the whole pack — not only the SWMS an officer reads.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the draft pack the officer opens
- E1Final-output evaluationWas the SWMS specific to this task and this work area?
- E2Step-level evaluationDid it read the current revision of the right standard and drawing?
- E3Tool evaluationDid it resolve the correct plant item, register entry and permit type?
- E4Isolation recallHow many isolation points were missed against the verified walk-down?
- E5Slice evaluationHow does draft quality change across specific job cohorts?
- E6Business outcomeHow much did the officer amend, and what did the audit find?
Floor — the work that is actually done at the plant
Failure modes
Where each failure originates in the agent
Seven failure modes plotted against the five stages of the agent lifecycle.
Agent lifecycle
Direction of processing →
01 · Retrieval
2 modes
- SF-01
Stale isolation point
An old point survives a re-pipe and reaches a draft.
- SF-02
Superseded revision read
An older procedure revision is treated as current.
Stage gathers
Site standards, drawings, the plant register and the revision
02 · Drafting
2 modes
- SF-03
Generic SWMS wording
Template controls survive into a task-specific draft.
- SF-04
Stored energy omitted
Accumulators, springs or trapped pressure are not listed.
Stage proposes
Draft SWMS text, isolation points and the gap list
03 · Verification
1 mode
- SF-05
Permit gap not raised
A missing signature or expired ticket passes the check.
Stage checks
Specificity, signatures, expiry and change impact
04 · Handoff / write
1 mode
- SF-06
Over-flagging floods review
So much is queried that the gap list stops being read.
Stage presents
The draft pack the officer reads and the queue it enters
05 · Change / Version
1 mode
- SF-07
Procedure change untracked
A revision reaches drafts with no named approver or record.
Stage tracks
Model, prompt, standard and procedure-revision changes
- Sev-1 · a crew could work to a wrong document
- Sev-2 · a defective document reaches an officer
- Sev-3 · drafting degrades, more is amended
Affected slices
The jobs that go wrong are not the ordinary ones
A draft is only as current as the plant it describes. Re-piped equipment, crews new to the site and jobs with no precedent draw the amendments; routine shutdown work does not. Nestack reports performance by slice, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Re-piped or modified plant | 5.6% | 3.6× | Review | |
| Contractor crews, first job | 4.4% | 2.8× | Review | |
| Night-shift permit packs | 3.0% | 1.9× | Watch | |
| Routine shutdown work orders | 1.2% | 0.8× | Normal |
Bar: amended-or-rejected draft rate, lift vs. routine-shutdown baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
A wrong document is fixed everywhere it appears
An amendment to one SWMS does not close the finding. The standard behind it, the register entry or the retrieval rule is changed under change control.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Officer amendments or audit findings move in a cohort.
- 02
Diagnose
Which revision did it read, and why did the check pass it?
- 03
Improve
The rule or standard reference goes through change control, with an approver.
- 04
Verify
Re-drafted against held-out jobs from the affected cohort.
- 05
Learn
That job is kept as a regression case and the rule enters the drafting runbook.
Learn → Detect
The return edge. A change to a standard or an isolation register is made by a named approver.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources and standards, drafting and isolation logic, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Workflow discovery and automation-boundary definition.Week 1
- 02Standard and procedure-source assessment.Week 1, Week 2
- 03Statutory positions and approval paths.Week 1, Week 2
- 04Plant register and drawing access.Week 2
- 05SWMS drafting against task and work area.Week 2, Week 3
- 06Isolation-point and stored-energy assembly.Week 3
- 07Permit-pack and expiry gap checks.Week 3, Week 4
- 08Change-impact tracing and staleness flags.Week 4
- 09Evaluation suite, isolation recall and regression cases.Week 4, Week 5
- 10Officer review and amendment capture.Week 5
- 11Permit-system integration and write-back.Week 5, Week 6
- 12Observability, deployment and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
| Capability✓ in scope · — not at this tier | PilotOne job type, one site | ProductionProduction document integration | AdvancedMulti-site / multi-commodity |
|---|---|---|---|
| Introduced at Pilot | |||
| SWMS drafting against task and work area | ✓ | ✓ | ✓ |
| Isolation-point assembly and stored energy | ✓ | ✓ | ✓ |
| Permit-pack and expiry gap checks | ✓ | ✓ | ✓ |
| Change-impact tracing and staleness flags | ✓ | ✓ | ✓ |
| Signature stays with the named person | ✓ | ✓ | ✓ |
| Baseline evaluation | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Additional job types and work areas | — | ✓ | ✓ |
| Officer review workflow and write-back | — | ✓ | ✓ |
| Observability and evaluation | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-site and multi-commodity document sets | — | — | ✓ |
| Multiple permit and isolation systems | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on document sources, plant-register and drawing integrations, the number of sites and job types, approval controls and deployment requirements.
- Separate from build
- Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bring
We build with it
01Your SWMS library, procedures and principal hazard management plans
→Standard and procedure-source assessment
Week 102The statutory positions at your site and who signs what
→Statutory positions and approval paths
Week 103Access to the plant register, drawings and the permit system
→Plant register and drawing access
Week 204Your isolation standard, including the stored-energy rules
→Isolation-point and stored-energy assembly
Week 305Real packs that were sent back, and your audit findings
→Evaluation suite, isolation recall and regression cases
Week 406Your change-control process and its named approvers
→Change-impact tracing and staleness flags
Week 407Named supervisors and issuing officers to review drafts
→Officer review workflow, then pilot packs and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. Week 5 carries both the evaluation work and the first packs an officer reviews.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Standards, statutory positions and the automation boundary
W2Plant register, drawings and document sources wired in
W3SWMS drafting and isolation-point assembly on the first job type
W4Evaluation suite, isolation recall and change-impact tracing
W5Permit-system integration, supervised packs and targeted corrections
W6The officers who sign work live drafts and amend them, then Agent Care starts
- Reading the band
- Week 4 is the isolation walk-down comparison; week 5 is the first pack an officer sees. That order is why the bars overlap.
- At the end of W6
- Officers have amended live drafts and re-read the cited standards against the plant register, then Agent Care takes over monitoring.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Mining AI agent
Build a safety-documentation agent around your statutory regime.
Show us your SWMS library, your isolation standard and the permit pack an officer signs today. You get back one job drafted to your own standards, with each isolation point marked verified at the plant or not verified at all.
- Typical delivery
- 4–6 weeks
- Deployment
- Your mine's document stack
- Approval to work
- Named person, always
- After launch
- Agent Care available
Nestack Agents · Safety & compliance documentation
AGT-MN-01 · Agent Care available after launch