Pilot Scope Options
Scope options to react to during a Cement Agent Plant Pilot discovery conversation. This is a discussion aid — not a proposal, quote, contract, or promise of service. It carries no pricing; scope and terms are settled with your authority.
Advisory only. Every option is an advisory workflow layer — not process control and not advanced process control (APC), with no control-system writeback. It records, structures, and routes; it authorizes nothing. Decisions stay with the appropriate human authority.
How to choose a pilot scope
- Start narrow — one clearly bounded slice is easier to evaluate than a broad rollout.
- Pick workflows that have clear owners on the plant side.
- Use only approved source material.
- Keep every decision with human authority — the pilot routes, it does not decide.
Option A — single-workflow dry run
- One workflow, one owner group.
- Public / general corpus plus customer-approved examples.
- Good for validating whether the advisory output is useful and whether the boundaries hold.
Example starting points: issue intake and triage or safety observation carry-forward.
Option B — department workflow pilot
- Two or three related workflows for one department — for example process, reliability, QC, or safety.
- Includes workflow examples and a handoff review for that department.
Example combinations: QC out-of-trend review, dust collector trend review, preheater restriction trend review, or finish mill ventilation trend review.
Option C — shift-handover / cross-functional pilot
- Issue intake and triage plus shift handover across selected departments.
- Emphasizes routing and carry-forward consistency between shifts and teams.
What every scope keeps out
- No process control or advanced process control (APC).
- No control-system writeback.
- No authorization of operation, shutdown, restart, field work, lockout/tagout, or product release/hold/rejection.
- No compliance, environmental, safety-clearance, or legal determinations.
Scope questions
- Who owns the workflows and the content on the plant side?
- Which workflows are in scope?
- What source material is allowed?
- What outputs are allowed, and who may see them?
- What review cadence works for your team?
- What are the data boundaries?
- Which qualitative success questions will you use to judge it?
Next step
Work through the options with the Pilot Discovery Guide, prepare with the Pilot Inquiry Checklist, and review deployment and data handling in Private Deployment & Data Boundaries. When you're ready to reach out, see Pilot Inquiry Contact. For the overview and shareable summary, see the pilot page and the pilot brief.