Today we are announcing ChangeIQ, an application that automates the slowest part of Management of Change: assembling the package. Built on the Plant360 asset knowledge graph, ChangeIQ turns MoC preparation from a multi-day document hunt into a reviewed, auditable workflow that starts with the assets themselves. Early customers are seeing more than a 40% reduction in preparation time.
The Management of Change problem
Every safe change to a process plant runs through Management of Change, and every MoC starts with the same grind. An engineer identifies the affected equipment, then goes hunting: which P&IDs show this line, which datasheets apply, which procedures reference this tag, what interlocks and relief cases are in scope, and what past changes touched the same assets. The information exists, but it is scattered across document management, the EAM, and people's memory. Assembling a complete package can take days, and an incomplete one is a safety and compliance risk.
The cost is not only time. Because assembly is manual, coverage depends on who does it. An experienced engineer finds the obscure interlock; a new one may not. That variability is exactly what a formal MoC process is supposed to remove.
Auto-assembled packages from the live graph
ChangeIQ starts from the asset, not from a blank template. Point it at the equipment or line you intend to change, and it traverses the graph to pull everything connected to it into a draft package.
Every P&ID and Smart Drawing the affected tags appear on, at the current revision.
Linked datasheets, specifications, and design conditions for the equipment in scope.
Related procedures, interlocks, relief cases, and prior changes that reference the same assets.
Open and historical work orders from the connected EAM, so maintenance context is in the package from the start.
Because the graph is the same system of record engineering maintains, the package reflects the current state of the plant rather than a stale export. The engineer reviews and edits a draft instead of building one from nothing, which is where the bulk of the time saving comes from.
Risk routing to the right reviewers
A complete package is only useful if the right people review the right parts of it. ChangeIQ scores the change against the assets and documents it touches and routes review accordingly. A modification that affects a relief case or a safety instrumented function is flagged and sent to process safety; a change confined to a non-critical utility line follows a lighter path. Reviewers see the specific graph context behind each item, so an approval is grounded in evidence rather than a signature on a summary.
The package should know what it touches. When the assembly is driven by the graph, risk routing stops being a manual judgment call and becomes a property of the change itself.
A complete audit trail
Every action in ChangeIQ is recorded against the graph: what was pulled into the package, which revision each document was at, who reviewed and approved each element, and how the change moved through its stages. When an auditor or an incident investigation asks why a change was considered safe, the answer is a traceable record rather than a reconstruction from email. Provenance is captured as the work happens, not assembled afterward.
The result
Across early deployments, ChangeIQ is cutting MoC preparation time by more than 40%, while making coverage consistent regardless of who runs the change. Engineers spend their time on judgment, not on hunting for documents. Process safety reviews the changes that actually carry risk. And the audit trail is complete by construction. ChangeIQ is available now on the Plant360 platform for teams whose asset data already lives in the graph, and as part of a digitization-to-agent rollout for teams starting from scanned drawings.
