Week 1-2
Integration and baseline setup
Connect read-only telemetry, align context windows, and establish structural baseline.
Run a scoped pilot in one environment, measure early-warning performance, and leave with operator-ready findings.
What We Scope
Timeline
Week 1-2
Connect read-only telemetry, align context windows, and establish structural baseline.
Week 3-4
Run detection pipeline and review high-signal relationship shifts with your operators.
Week 5-6
Compare findings against known incidents or controlled events to measure warning window.
Week 7-8
Deliver rollout recommendation, operating playbook, and next-facility deployment plan.
Deliverables
Relationship model of normal system behavior across operating regimes.
Measured warning window and confidence levels against your selected risk events.
Prioritized checks and response guidance linked to detected drift patterns.
Commercials
Final pricing is set after fit-call scoping.
Pilot ROI Calculator
Pilot FAQ
Read-only deployment. We start with existing historians/telemetry exports and scope to one environment first.
No control writes. Pilot is designed for observational analysis and operator-facing findings.
Scoped data access, read-only connectors, and clear boundary mapping before ingestion begins.
Most teams see directional findings in weeks 3-4, followed by structured verification by pilot close.
Operator Brief
Share this with operators and plant leadership: problem, approach, pilot plan, and simulation disclosure.
Ready to scope your pilot?