Choose one priority line for the focused pilot, up to three areas for Foundation, or a cross-functional scope for Core. Agree who can release the equipment and who can approve the result.
| Pilot | Proposed One-Time Fee | Agreed Starting Scope |
|---|---|---|
| Focused Small Plant | $5,000 | One line or operating area and one or two recurring issues; remote delivery using approved entries and files. |
| Foundation Deployment | $12,500 | One facility, up to three priority operating areas, leadership kickoff and a shared corrective-action review. |
| Core Plant | $22,500 | One facility with cross-functional production, maintenance and quality participation and an approved operational-impact model. |
| Enterprise Plant | $35,000 | One complex facility, corporate stakeholders, deployment governance and assessment of a possible multi-site rollout. This is not a pilot across an entire network. |
Before day one, agree the operating areas, data sources, participants, review cadence, delivery effort, measures and exit process. The focused pilot excludes hardware, custom connectors, on-site travel and open-ended consulting. Larger scopes still require explicit service boundaries.
Days 1–15 — Establish the baseline. Choose recurring issues that the plant recognizes. Review event history and prior repairs. Name the production and maintenance owners. Record the current frequency, downtime, evidence quality and approved cost assumptions. Agree what will count as a verified result.
Days 16–30 — Put the workflow into use. Configure the agreed records and approved imports. Train the participating shifts. Capture what operators observed, what maintenance suspects and what evidence verifies. Establish the weekly review and corrective-action commitments.
Days 31–60 — Follow the correction through the plant. Track parts, authority, release windows, shift coverage and changed work instructions. Record why a commitment moved and what additional events occurred. Collect completion evidence and have the authorized person verify the operating test.
Days 61–90 — Review whether recovery is holding. Compare the agreed baseline with observed operation. Review related events, adoption, unresolved constraints and finance-approved calculations. Deliver a findings report and a recommendation to continue, change scope or stop.
The final report includes the baseline, event and action history, deployment evidence, verification results, open items, recovery assumptions and the recommended next scope. A 90-day pilot does not guarantee that a long service-life issue has completed its monitoring period. Where sufficient operating exposure has not elapsed, the issue stays open for monitoring.