CPNET watches machine setpoints and operational actions, then quantifies their impact on quality, scrap, throughput, energy, OEE, and alerts—so you can keep the good changes and roll back the bad fast.
What is CPNET Change / Impact Tracker?
A purpose-built workflow that detects recipe/setpoint edits, mode toggles, operator actions, and SOP changes, then links each change to pre/post performance on your critical KPIs. It normalizes for product mix and conditions, shows who changed what and when, and auto-generates a change impact report for your daily production meeting.
Built for: steel, plastics, construction materials, and other continuous manufacturing where small setpoint moves can ripple into big quality and cost swings.
How customers use CPNET for Change & Impact
Connect & define “a change”
Map tags for controllables (temps, speeds, pressures, ratios), recipe loads, mode flags, and SOP steps. In a simple Form, define what counts as a change (e.g., ±3 °C, ±0.1 m/s, recipe version bump).
Detect & attribute
CPNET detects change events and builds matched pre/post windows (e.g., −30/+120 min), normalized by grade, line, ambient, and downtime. It ties affected lots/coils/rolls to each event.
Measure impact
For each change, CPNET runs uplift tests (difference-in-differences/CUSUM/SPC) on CTQs (Cpk/spec-ratio), scrap %, startup duration, throughput/hr, energy/ton, OEE components, alert count/severity—with confidence and sample size.
Explain drivers
See which co-changes (other setpoints, alarms, load) likely influenced the outcome using correlation and SHAP-based importance.
Decide fast
Changes get a KEEP / WATCH / ROLLBACK recommendation based on impact and risk thresholds. Bad changes trigger alerts; good ones become playbooks/SOP updates.
Report automatically
CPNET assembles a daily Change Impact Report: top positive/negative changes, KPIs affected, who/when/where, and open actions—export to PDF/CSV or email before the morning huddle.
Optional: If you also run Rx+, you can turn a promising change into a small
batch of follow-up settings
Why teams choose CPNET for Change Tracking
Accountability without blame
Clear “who/when/what” with normalized, fair impact measurement.
From noise to signal
Automatic matching filters out mix and downtime effects—see the true effect of the change.
Faster decisions
KEEP/WATCH/ROLLBACK recommendations and alerts shrink the time from change to action.
Repeatable wins
Promote proven positive changes into guardrails, SOP steps, and checklists.
Works with your stack
Historian/MES/LIMS + alarm logs and identity (Keycloak/MES) in; dashboards and scheduled reports out.
- Get Started
