octoplant Pharma and Life Sciences Guide: Validated Change Control for Automation

octoplant pharma use rests on one idea: in a validated plant, a change to PLC or HMI code is a change to the validated state, and the plant must be able to show what changed, who changed it, why, and that it was approved and tested. Most pharma sites manage that with paper or electronic change requests that describe the change. What they often cannot show is that the code in the controller today is the code that was approved. This page explains how automation change management fits GMP change control, what validating the tool itself involves, and where it gets hard. It sits under octoplant use cases by industry in our independent AMDT overview.

What this page does not repeat. The audit trail requirements of FDA 21 CFR Part 11 and EU Annex 11, and how octoplant’s records map to them, are covered on audit trail and 21 CFR Part 11. The wider regulatory picture is on Compliance.

Where automation code escapes change control

The quality system is usually strong at the document level and weak at the device level. Code changes reach validated equipment through routes the change request never sees:

• Online edits during a breakdown. A technician changes a timer or an interlock to recover a batch, intending to raise the change request in the morning.
• Vendor service visits. An OEM engineer updates the firmware or logic on a skid during preventive maintenance and leaves a service report that says “software updated.”
• Restores from the wrong file. After a hardware failure, someone loads the program from a network share that holds three versions with similar names.
• Commissioning carry-over. Code changed during qualification runs is not the version that was frozen in the documentation.

Illustrative scenario. A CIP skid alarms on low return temperature. A night-shift technician lowers the alarm setpoint by two degrees in the PLC to finish the cycle. The batch completes. Three weeks later an auditor asks for evidence that the cleaning validation parameters are unchanged since qualification, and the plant discovers the edit only by comparing the running program against the qualified version. Every batch cleaned since is now part of an investigation.

AMDT frames the stake the same way on its pharma page: changes to automation configurations “can affect a validated production environment and trigger investigation, documentation, testing, or revalidation activities” (AMDT).

How octoplant pharma use maps to GMP change control

Change control step	What the plant must be able to show	What octoplant can contribute	What stays with people and the QMS
Baseline	The qualified version of each program	A stored, versioned approved copy per device	Declaring which version is the qualified one
Implementation	That the change made matches the change approved	Check-in and check-out with user, time and comment	Linking the version to the change request number
Verification	Exactly what changed, for the test scope	A Smart Compare report of new against old	Deciding what to test and signing it off
Ongoing control	No unrecorded changes since release	Scheduled upload and compare, with alerts	Investigating each difference as a possible deviation
Recovery	The validated program can be restored	Restore of the approved version	Post-restore verification before release to production

Validating the tool itself

A tool used to hold GxP evidence becomes a computerised system in its own right, and it needs to be qualified. AMDT lists IQ/OQ Services among its offerings: installation qualification (the software is installed as specified) and operational qualification (it works as specified in your environment). Performance qualification against your processes, the user requirements and the risk assessment remain the plant’s work. How a site categorises the tool under GAMP 5 is a decision for its validation lead, not the vendor.

Two history points matter for buyers. AUVESY sold a versiondog GxP Edition; whether octoplant has a direct equivalent is not confirmed in public sources. AMDT’s published editions are Core, Plus and Premium, with Premium described as the package for “medium and large or highly regulated environments” (octoplant pricing), as of October 2026. The per-edition feature split is not published, so ask which audit trail, approval and reporting features sit in which edition before you write the user requirements. Sites still on versiondog should read versiondog and AutoSave, because moving a validated system to a new platform is itself a validated change.

octoplant pharma case study and the frameworks AMDT cites

AMDT’s one named pharma story is Reliable OT Data at Humanwell Pharmaceutical. Yichang Humanwell makes anesthetic and other controlled products. As AMDT tells it, parameters had been set by hand and checked through several control steps, and documenting changes took considerable effort. Humanwell selected “the AMDT solution” in 2019 and first used it on a new freeze-dried emulsion line in 2020, for central storage of device programs, automatic backups and a record of changes. The story describes benefits, including “faster access to validated process configurations”, but not how the tool itself was validated or any figures. Note the dates: the selection predates octoplant, so the product in use may have been a predecessor. AMDT’s pharma page names FDA 21 CFR Part 11, cGMP (21 CFR Parts 210 and 211), EU GMP Annex 11, GAMP 5 and NIS2 as the frameworks it addresses (AMDT).

What changes for each team

Adopting the tool shifts work between groups, and the change control SOP should say so:

• Quality assurance reviews compare reports instead of narrative descriptions of a change, which makes the impact assessment more precise and the test scope easier to defend.
• Automation engineering works from a checked-out approved version rather than “the latest file on the share,” and records the change request number at check-in.
• Maintenance restores from the approved version after a failure and hands the device back to QA for verification, instead of loading whatever file is closest.
• Periodic review of each computerised system becomes faster, because a compare of running against qualified versions answers the first question an inspector asks.

Where it gets hard

• Upgrading a validated tool. octoplant releases regularly (105 in August 2025, 107 in April 2026, per AMDT). Each upgrade on a validated installation is a change with its own assessment and testing, so many sites fall behind and lose device support for newer editors.
• Two audit trails. The engineering software and the change management tool each keep a record. Decide which one is the record of truth for each kind of change, and write it into the SOP.
• DCS and batch systems. API plants often run a DCS with its own configuration management. Check AMDT’s current matrix for your system before assuming coverage.
• Skids during qualification. Code changes fast during commissioning and qualification. Bring the vendor’s skid code under control before the first protocol is executed, not after.
• Vendor validation packages. Some skid suppliers deliver their own validation documents. Bringing the skid under plant-side backup and compare should not invalidate that package, so write the requirement into the user requirement specification before the purchase order.
• Restore is a GMP event too. Loading the approved version after a failure still needs verification and a record before the equipment returns to production. Rehearse it once, on a non-critical system, so the first real restore is not also the first time anyone reads the SOP.
• Alert handling. A compare difference is a potential deviation. Without a defined triage route, sites either drown in alerts or stop reading them.

An owner’s representative who understands both the quality system and the automation layer shortens most of these; see owner’s engineer and our guide to quality, MES and traceability. For a sector where speed of change rather than validation drives the case, compare octoplant in food and beverage.

---

Related: octoplant use cases by industry · Audit Trail and 21 CFR Part 11 · Food and Beverage · AMDT hub