Private Deployment & Data Boundaries
A discussion brief for a Cement Agent Plant Pilot — how a private pilot is scoped, what data it uses, and what it does not touch. It is a starting point for a conversation, not a legal or security contract or guarantee. Specific terms are settled with your authority before any pilot.
Advisory only. The pilot is a workflow and knowledge layer — not process control and not advanced process control (APC). There is no control-system writeback and no plant-system integration unless explicitly scoped later with your authority. It records, structures, and routes; it authorizes nothing.
1. Deployment posture
- A private pilot configuration scoped to a single plant.
- An advisory workflow layer — intake, triage, handoff, and review.
- No control-system writeback.
- No plant-system integration unless explicitly scoped later, in writing, with your authority.
2. Data boundary principles
- Use only source material your authority has approved.
- Avoid credentials, passwords, personal data, confidential incident details, and proprietary criteria unless explicitly approved by your authority.
- Your authority decides which plant procedures and terminology may be used and how.
3. Source material options
- Public / general corpus only (no plant-specific material).
- Customer-approved excerpts of procedures or references.
- Sanitized or redacted examples.
- Workflow dry-run notes produced during the pilot.
4. What the pilot does not do
- No process control or advanced process control (APC).
- No compliance determination or environmental determination.
- No safety clearance.
- No authorization of operation, shutdown, restart, field work, lockout/tagout, or product release/hold/rejection.
- No writeback to CMMS, DCS, historian, lab/LIMS, safety systems, or environmental reporting systems.
5. Review and approval model
- Your plant authority approves the sources, terminology, workflow boundaries, and any private content.
- Humans remain the decision owners for every action — the pilot routes to them, it does not decide.
6. Questions to settle before a pilot
- Hosting preference (where the private configuration runs).
- Who owns content approval on the plant side.
- Which workflows are in scope.
- What source material is allowed.
- What outputs are allowed and who may see them.
- Retention and export expectations for any pilot artifacts.
Next steps
Use the Pilot Discovery Guide to work through these in conversation, and the Pilot Inquiry Checklist to prepare what is useful to have ready. To frame how a first pilot could be bounded, see Pilot Scope Options. When you're ready to reach out, see Pilot Inquiry Contact. For the overview and the shareable summary, see the pilot page and the pilot brief.