Pilot Inquiry Checklist
A pre-conversation checklist to help you prepare for a Cement Agent Plant Pilot discovery call. It is a static, advisory checklist — not a form. Nothing is collected or submitted on this page; bring what is relevant to the conversation, and only what your authority approves sharing.
Advisory only. This checklist helps you prepare; it does not collect data, connect to any plant system, or imply any integration. The pilot itself is advisory only and authorizes nothing — see the pilot overview.
1. Plant context
Enough to scope a single, focused pilot — gathered for your own preparation:
- Plant / line / area in scope.
- Department owner and decision-maker for the pilot.
- Intended pilot audience (operators, supervisors, QC, maintenance/reliability, process, safety).
- Preferred workflows to pilot (see the candidates below).
2. Workflow candidates
The advisory workflows you could exercise — pick the few that matter most:
- Issue intake and triage.
- Shift handover.
- Safety observation carry-forward.
- QC out-of-trend review.
- Dust collector trend review.
- Preheater restriction trend review.
- Finish mill ventilation trend review.
3. Source-material readiness
What helps configure the advisory layer to your plant — share only what your authority approves:
- Approved SOP / procedure excerpts (or pointers to them).
- OEM / manual references relevant to the chosen workflows.
- Existing shift-log examples (redacted as needed).
- Existing safety observation / near-miss format.
- Approved plant terminology and area names.
4. Boundaries and exclusions
So expectations are clear before the call — the pilot does not cross these lines:
- No control-system writeback.
- No process control or advanced process control (APC).
- No safety clearance or authorization of any action.
- No compliance determination or environmental determination.
- No plant criteria or proprietary standards (limits, setpoints, thresholds, acceptance criteria) unless explicitly approved and supplied by your authority.
5. Success questions
A pilot is how you answer these for your own plant — they are evaluation questions, not promises of any outcome:
- Would a structured intake / triage handoff make first-touch routing clearer for your teams?
- Are the advisory handoffs and shift carry-forwards useful and accurate enough to be worth reviewing?
- Do the advisory-only boundaries and authority routing hold up in your real workflows?
- Is the configuration effort justified by the value your stakeholders see in the dry runs?
- Which workflows, if any, would your stakeholders want to take further?
6. What not to send
Please do not share, on this page or in advance of an agreed scope:
- Passwords or access credentials of any kind.
- System access or remote-connection details.
- Confidential incident details or anything under investigation.
- Personal data about individuals.
- Proprietary standards or plant criteria unless explicitly approved by your authority.
Next step
When the relevant items are ready, see Pilot Inquiry Contact to start a conversation, return to the pilot overview for the suggested pilot structure, or share the concise pilot brief with a colleague. The Pilot Discovery Guide outlines the conversation itself, and Private Deployment & Data Boundaries covers deployment posture and data handling. For how the advisory layer is structured and its limits, see the safety guardrails and About.