Automation & Control-System Integrators
Operational enablement — Engineering & facilities
The firms that specify, build, and integrate the control systems regulated processes run on — PLCs, DCS, SCADA, historians, and the MES/EBR layer above them. Their work sits at the join of good engineering practice and computerised-system validation, and it decides whether process data is trustworthy by design.
What this page does not claim
The rings are SPEQ’s map of who operates in the regulated ecosystem, not a legal or regulatory classification. Where an organization type already has a canonical page, this points at it rather than describing it twice.
Control systems generate and hold the process data quality decisions rest on; their design determines whether that data is trustworthy and whether the process stays in control.
The regulated-relevance test — an adjacent subject belongs only when it materially affects one of ten regulated concerns.
- Design and configure control systems (PLC/DCS/SCADA) and their interfaces
- Build the historian, alarm, and batch layers that record what the process did
- Configure user roles, access privileges, and audit-trail settings for the control layer
- Integrate control systems with MES/EBR, LIMS, and enterprise systems
- Support factory and site acceptance testing and the CSV that follows
Control systems are GxP computerised systems: their configuration determines whether records are attributable, complete, and protected — data integrity is engineered here at configuration time or it is not achieved at all.
A GAMP 5 risk-based approach lets the integrator and owner focus validation on the functions that affect product quality and data integrity rather than exhaustively testing every tag, keeping the effort proportionate and defensible.
Access control, audit trails, and time synchronisation are configuration choices the integrator makes that an inspector will later test directly — and that decide whether the process data can be trusted.
- Shared or generic logins and disabled audit trails baked into the control layer
- Undocumented configuration that cannot be validated or restored after a change
- Treating the control system as engineering-only, so CSV and data-integrity controls are bolted on late and incompletely
The 4 standards SPEQ maps to this org type’s quality interface, across 4 regulatory bodies: EMA, ISPE, ASTM, ASME.
FREQUENTLY ASKED
Is a control-system integrator a software vendor?
Related but distinct. A software vendor supplies a product; an automation integrator engineers and configures a control system — often assembling vendor products — into a working, validated whole for a specific process. SPEQ keeps the system class (what a control system is) separate from the vendor directory; both must feed the owner’s CSV effort.
Why does automation work fall under data integrity?
Because the control layer is where process data is created and first recorded. Whether entries are attributable, whether the audit trail is on, whether operators share logins, and how time is synchronised are all configuration decisions made during integration — and they are exactly what an inspector probes when testing data integrity.