Workflow inbox
Cited briefings BooleX prepares on plant events, for a person to review.
Workflows run on plant events and post a cited result to the Workflows inbox. They only read: a workflow step that would control, write or store anything is always refused. A person reviews every result.
The built-in workflows
| Workflow | Trigger | Result |
|---|---|---|
| Alarm briefing | An alarm activates (alarms in a flood carry their flood group) | Within 60 seconds: the alarm's meaning, likely causes from its cause chain, the current values on that chain, and its last five occurrences with their recorded fixes |
| Stop evidence | A stop | The sequence of events around the stop |
| Trip evidence | An interlock trips | The sequence of events, the interlock's condition and the equipment it acts on |
| Maintenance briefing | A work order is opened | The asset's stops and alarms in the last 30 days, past work orders on the same fault, the parts and stock likely needed, the relevant manual and drawing pages, and the site's isolation procedure for the asset, cited (BooleX never composes isolation steps itself) |
| Return-to-service check | The first completed run after a work order closed | That run compared with the good runs, with the deviations, within 15 minutes of the run ending |
| Part change, journal draft | A part change is recorded | A draft journal record for an expert to confirm |
| Part change, 24-hour watch | 24 hours after a part change | Deviations of the tags on that part's cause chains from the good runs during those 24 hours |
| Shift handover | A shift ends (the site's shift table) | The handover summary for that shift, within 5 minutes |
| Code change review | A new code revision is imported | The changed code elements that lie on an alarm or interlock cause chain, citing both revisions |
| Recurring fault | A stop or an alarm | On the third occurrence within 7 days on an asset: a notice listing the occurrences and their recorded fixes |
Each site's definitions are in the workflow file named in site.yaml.
Review a result
Results are listed newest first. Filter results by Asset, Trigger event and Review state (awaiting review, accepted, rejected). Open one to read its cited statements; click a source ID to open the source viewer.
Technicians, shift leads and experts Accept, Reject or Add note; each review is recorded with the time and the note. Viewers can read results only. A run that failed is listed as failed with the reason.
Record a part change
Record a part change takes the asset, Part number, Serial number (optional) and Work order. It starts the two part-change workflows and becomes a part:// source. Parts issued on a closed CMMS work order are recorded the same way, automatically.
Outside the edge PC
Site tools (messaging, the CMMS, an MES) can poll workflow results through the read-only integration API. The edge PC pushes nothing out.