Our Software
Marshal
Answers are good. Finished work is better.
Marshal runs multi-step engineering jobs end to end: isolation plans, impact analyses, scope reviews. Human checkpoints sit exactly where your procedures require judgment and sign-off. The work arrives finished, with its evidence attached.
Most industrial AI stops at an answer
The backlog is not made of questions. It is made of work: isolations to plan, investigations to close, hazard reviews to run, change requests to process. The economic value lives in the work that follows the answer.
- Briefed the way an engineer is briefed. Marshal plans each job from three sources, in order: the operator's request, the plant's own procedures, and standard practice. Where the plant has a procedure, Marshal follows it. Where it does not, it presents its plan first.
- Grounded at every step. Every intermediate result cites its source on the graph: the sheet, the tag, the document revision. The audit trail writes itself as the work runs.
- Finished means finished. The deliverable is the work product an engineer would deliver: the plan, the study, the analysis, ready for sign-off.
The workflows
Where customers start.
Five jobs, run end to end on the compiled graph. The list is where deployments begin, not where they end.
Process isolation
Every line feeding the work traced across sheets, every energy source enumerated, the plan drafted for an engineer to approve. Explore
Root cause analysis
The complete evidence file within hours: what failed, what was upstream, what changed, and which documents prove it. Explore
Hazard and operability
Nodes, deviations, and consequences drafted from the graph; your experts spend the study on the exceptions. Explore
Management of change
The change classified, the impact analyzed, the package routed, the documents updated. Explore
Turnaround scope
A risk-ranked scope where every job earns its place, with the evidence behind every work-list item. Explore
Division of labor
MarshalRuns the job
- Traces the topology, pulls the history, sweeps the documents
- Drafts the plan, the study, or the analysis, cited throughout
- Assembles the evidence package as the work runs
- Stops at every checkpoint and presents what it has
Your teamOwns the judgment
- Chooses which steps require an engineer's sign-off
- Reviews the evidence at each checkpoint and approves or redirects
- Signs the finished work, with the record attached
“It did in an afternoon what my team had backlogged for a quarter.”
Senior process engineer, Fortune-100 refiner
All workflows The graph it runs on Where the trust is earned