InnerWeb
Skip to main content

Management of Change (MOC) in a Chemical Plant

A chemical plant, an essential entity under NIS2, replaced a plant component during one turnaround without a formal change assessment. The contractor acted in good faith and the change was agreed verbally. This case shows how a digital change workflow linked to work permits closes that gap with around 20 external companies on site.

ok. 20
external companies in maintenance
6 weeks
time to go live
PLN 12,600
one-off implementation, net (indicative range from 2025–2026 deployments; individual quotation)
80 h
less per year in the change workflow (illustrative calculation)
Source: example calculation

Starting point

The site is a chemical plant within an international group, with the status of an essential entity under NIS2. Around 20 external companies work in maintenance, and every month several dozen people from outside the workforce enter the site, often for hot work, work at height and work in tanks.

Work permits lived in binders, so there was no current picture of open jobs. Induction training took place at the gate and delayed the start of work, and the validity of qualifications (electrical SEP, UDT, work at height) was tracked by hand. On paper, nothing enforced the order of safeguards, measurements and signatures.

The problem: a change during a turnaround without formal MOC

During the turnaround, a contractor proposed swapping a valve for a different type that was available immediately. The decision was made on the spot, with a foreman and the duty operator on the plant side. No change request was raised, the impact on safety device settings and on process documentation was not assessed, and the pre-startup review covered only leak tightness.

The change was spotted only when a drawing was compared with the installation while preparing for an audit. There were no incidents. The conclusion was clear, though: an MOC process existed in the procedure but was not tied to any tool that an external company must pass through in order to start work at all.

  • The change was agreed verbally and not entered in any register.
  • No assessment of impact on safety devices and process documentation.
  • Pre-startup review limited to a leak test.
  • The contractor had no obligation to declare the change in the permit.

Workflow time for one plant change (illustrative calculation)

Workflow time for one plant change (illustrative calculation)Comparison of change workflow time: 3 hours on paper and 1 hour in the digital workflow0123hoursPaper workflow: 3 hours3 hoursPaper workflowDigital workflow: 1 hours1 hoursDigital workflow
Source: Illustrative calculation based on the assumptions in the Result section: 3 h on paper, 1 h digital

The solution: one path from training to permit to change

A single path was introduced for external companies. A named invitation with a QR code arrives by e-mail or SMS, online training with a randomised question test ends with a declaration in two language versions, and a register of companies and qualifications tracks expiry dates. The system does not admit anyone without current training.

A digital permit is created in a dozen or so seconds, goes through approvals and prints as a PDF in one of two plant templates. Particularly hazardous work types have their own safeguard checklists, and authorisation matrices control who may issue and approve a permit. The permit template drives the flow: preparatory, main and closing tasks are configured on the data side of the installation.

The change workflow is linked to the permit. If a job changes the configuration of the plant, a preparatory task appears in the template to confirm the change decision, assigned to an authorised role on the plant side. Only a plant user can approve or reject particularly hazardous work. When it turns out in the field that the scope differs from the permit, the plant user suspends the permit, and closing of tasks is blocked for all except those on the unblocking task list.

The result: figures and an illustrative calculation

The rollout took 6 weeks. Up to 10 users worked on the plant side, and the plant did not need to invest in its own infrastructure. The one-off implementation cost was PLN 12,600 net, with monthly maintenance for 10 users of PLN 2,000 net (indicative ranges from 2025–2026 deployments; individual quotation). The scope covered a server with accounts for 50 people, a training module in 2 language versions, permits and particularly hazardous work, QR checks in the field, a register of companies and a process manual.

Illustrative calculation of the effect on the change workflow. Assumptions: 40 plant changes during an annual turnaround, 3 hours of paper workflow per change (agreeing, signatures, searching for documents), 1 hour in the digital workflow, and an engineer hour costing PLN 120. The time saving is 40 × 2 h = 80 h a year, or PLN 9,600. The main effect is not financial, however: every change has an author, a time, an assessment and an approval, and the register serves as audit evidence.

Changes to selected data (permits, the taxonomy of hazardous work, training results) are recorded with the author and time. The QR check in the field shows training, qualifications and the permit for today, so a plant inspector can verify within seconds whether the person at the tank is working within an approved job.

Lessons for other plants

First, the MOC procedure must be tied to an action that the contractor cannot bypass. The best anchor point is the work permit, because no work starts without it. Second, the role that approves a change should be assigned by name or by function and be visible in the system, not agreed on site. Third, the pre-startup review should have a checklist that depends on the type of change.

A plant with a similar profile can start with a week of reviewing changes from the last turnaround: how many there were, how many were recorded, how many updated the drawings. That balance is a strong argument in a conversation with management and a starting point for measurement after rollout.

Video

Frequently asked questions

Does a work permit replace an MOC request?

No. The permit is the point at which the system forces a pass through a change-related task. Risk assessment and approval of the change still belong to authorised plant staff.

What about minor like-for-like replacements?

The plant defines in its procedure which replacements count as like-for-like and which count as a change. The boundary should be described with examples and checked through spot audits.

How many people operate the system on the plant side?

In the described rollout, up to 10 plant users, with accounts prepared for 50 people. External companies use the same path for training and permits.

Sources

See the change workflow on your own example

We will walk through your last turnaround with you and show where a change could have bypassed the formal workflow. Book a conversation or a demo.

Let's talk