Catching the mistake before it happens.
Most plant software shows you a dashboard and waits. Phase 2 puts OpsPulse to work cross-checking the plan against live constraints — and warning the right person before the decision is made.
Phase 2 builds on the data Phase 1 · Foundation collects. Most plants start with Phase 1 and add Phase 2 once it's running — or set up both on day one.
A plant runs on the gut of its most experienced person.
In many plants, one person just knows how the place actually works. They know that committing to extra loads the same week a dock door is down will blow the schedule. They know you can't run the batching line on a certain product without adjusting pump speeds.
That judgment is the most valuable asset in the building — and it only works when that person happens to be in the room.
- Undocumented — in nobody's manual or system
- Unscheduled — fires only by chance, in the moment
- Unscalable — can't be in two rooms at once
- At risk — walks out the door when they leave
When the gut isn't in the room, the plant pays for it.
Over-commitment
Yes to extra loads the same week multiple dock doors are down for maintenance — capacity blown, shipments missed.
Unqualified runs
A mineral-water run started with no certified MI Level 1 technician on site — quality and compliance risk.
Idle lines & rework
A PM with no parts on hand, or a changeover with no materials on hand — the line stalls and waits.
Silent quality holds
Commitments logged, constraints ignored — problems surface only after product is already moving.
Each of these is a known failure mode. The experienced manager would have caught every one — if they'd been watching that exact decision at that exact moment.
Hold three things in memory. Check every decision against them.
The plant model
Everything that must be true for a plan to actually work.
The constraint states
The live status of docks, staffing, inventory and quality holds.
The schedule
What's planned today and what's coming onto the calendar next.
Most software stops at describing what happened or predicting what might. OpsPulse takes the step after: catch what's about to go wrong and tell you what to check.
Three kinds of reviews, running together.
Playbooks — scheduled
Run every morning, no matter what's scheduled.
- Production vs. yesterday's plan
- Dock constraint status
- PTO coverage for critical roles
- Manifest vs. capacity
- Open quality holds
- Inventory vs. today's needs
Dependency chains — event-triggered
Fire when a specific event hits the calendar.
- Mineral water → skid status + cert check
- PM → sanitation + QA availability
- Changeover → expertise + parts on hand
- New commitment → capacity vs. constraints
Discovered — from failures
No intake form. The registry grows from failures.
- A missed combination is saved as a rule
- Dock-PM + extra loads, flagged every time
- The same miss gets caught next time
- Smarter every week it runs
A plain-language warning, in the plant's own words.
“There are no dock appointments open tomorrow and 10 more shipments were scheduled to ship tomorrow.”
“A water changeover to Alkaline is scheduled without a QA Tech with an MI Skid Level 2 cert.”
Meeting log
A meeting on the calendar can be logged. Commitments trigger a capacity check, new constraints are flagged for the dependency registry, and decisions land in the audit trail.
Root cause assistance
Describe a symptom and get likely causes — each backed by the plant's past fixes, downtime records and the OEM manual page. Your tech makes the call.
OpsCadence as the source of truth
Certifications tied to training that actually happened become live facts the checks can query — which is what makes the warnings trustworthy.
Start with the paperwork. Grow from there.
Phase 1 cleans up the forms, reports and SOPs. Phase 2 reads what Phase 1 collected. Phase 3 — supply planning on the same data — is on the roadmap. Nothing to re-enter, nothing thrown away.