Programmable logic controllers and SCADA systems run the equipment that makes the product, from autoclaves and bioreactors to cleanroom monitoring. They are often validated as part of equipment qualification, which is sensible only if the software and data aspects are not lost along the way.
Treat control software as part of the qualification
GAMP 5 recognises that automation often involves configured or custom-coded software. The user requirements should state the control functions, alarms, interlocks, recipes, data to be recorded and security needs. The design documentation, such as functional and software design specifications, then links to testing at factory acceptance, site acceptance and qualification stages.
What to test
Beyond confirming that the equipment performs its process, the testing should demonstrate the integrity of the control and data layers:
- Alarm and interlock behaviour, including limits, set points and response to power loss and recovery
- Recipe and parameter management, with controlled changes and clear versions
- Data recorded by the SCADA or historian, its time source, accuracy and any gaps on communication failure
- User levels, password settings and audit trails for parameter and alarm changes
- Interfaces to MES, building management or laboratory systems
Keep the code under control
Ladder logic and configuration files are software. Maintain an inventory of program versions, store backups under change control, and compare running code against the approved version periodically. Many sites find that a controller was modified at the panel during a breakdown and never documented, which is a change control failure waiting to be found.
Think about the operational technology environment
These systems often run old operating systems, cannot be patched freely and may be connected to wider networks. Segmentation, restricted removable media and clear responsibilities between engineering, IT and quality are part of keeping them in a validated state.
Resourcing and ownership
Computerised systems fail most often at the boundary between functions. Name a business owner who is accountable for the data, a system owner who runs the technology, and a quality representative who approves the validated state. Agree how they will meet and which metrics they will review, such as open changes, access review results and outstanding actions. Clear ownership is cheap and prevents many findings.
How PQRA helps
PQRA supports the planning and review of automation validation, from user requirements and risk assessments to acceptance testing strategy, data integrity assessments of SCADA and historian data, and the procedures needed to keep controller software under change control.
Contact PQRA to discuss your computerised systems and data governance programme.


No responses yet