CM97001 is Emerson's PAC Change Management software — a centralized version control and compliance tool for industrial automation programs running on PACSystems controllers. It addresses the four most common program-management failures on the plant floor: editing the wrong version of an application, overwriting a colleague's changes, loading an outdated backup after a controller replacement, and losing time searching network drives for the correct project file.

What problems does PAC Change Management solve?

In a typical plant, PLC and HMI programs live as files on individual engineering laptops or a loosely organized network share. A controls engineer making an emergency edit at 2 AM may grab last week's version by mistake. Two engineers working on different features of the same machine may overwrite each other's changes. When a controller fails and the maintenance team loads the backup, there is no way to know whether that backup is the last approved version or a test build from six months ago. PAC Change Management replaces this ad-hoc approach with a centralized repository: every program check-in is versioned, every check-out is tracked, and the software prevents simultaneous editing of the same object. The system answers the question "what is running on this controller, and who last changed it?" — a question that becomes critical during regulatory audits, incident investigations, or controller replacement events.

Electronic signatures and audit trails for regulated industries

For pharmaceutical, food and beverage, and other FDA-regulated manufacturing environments, 21 CFR Part 11 compliance requires electronic records and signatures that are attributable, legible, contemporaneous, original, and accurate (ALCOA). PAC Change Management provides electronic signature workflows: a program change requires authorized sign-off before it can be downloaded to a controller, and the signature is permanently recorded with the version history. The audit trail logs every action — who opened which project, what changes were made, when the change was approved, and when it was deployed — creating a defensible chain of custody for automation program changes. Scheduled backup operations ensure that a current, verified copy of every program exists on the management server, eliminating the risk of loading an obsolete backup during a controller replacement.