INFORMATION QMS FAMILY PACK

Table of Contents

Section 1 - Family Summary

This Family inherits the governance requirements defined in the Unified Governance Manual (SOP-QMS-GOV), including the Quality Manual, Risk Management Program (RMP), Internal Audit Program (IAP), and Material Review Board (MRB) governance (SOP-QA-MRB). All IT responsibilities and WINs must align with these L2 authorities.

The Information Technology (IT) Process Family governs all WHAT-level controls ensuring that computerized systems used within the Quality Management System (QMS) remain secure, accurate, reliable, validated, and compliant. IT establishes the controls needed to maintain system access security, electronic record integrity, electronic signature authenticity, backup and recovery reliability, and proper performance of all regulated applications.

IT provides WHAT-level governance for:

As a critical GMP support Family, IT ensures that:

IT controls support:

Effective IT controls prevent:

IT interacts with all other Process Families—including QA, QCL, QCP, PROD, PKG, WH, MNT, SAN, PROC, and Document Control—by providing:

Risk Tier Classification: HIGH. Failures in IT controls can compromise electronic data integrity, record authenticity, system availability, and GMP compliance. Because IT systems support every Family, failures create enterprise-wide regulatory exposure.

Section 2 - Purpose, Scope & Regulatory Anchors

SOP ID SOP Title Purpose (Control Intent) Scope (Operational Boundary) Regulatory Anchors
SOP-IT-ACCESS System Access Control Establishes WHAT-level controls for creating, modifying, disabling, and managing system access to ensure only authorized and trained personnel can access computerized systems used for GMP activities and decision-making. Applies to all computerized systems, applications, servers, cloud services, and equipment that store, process, or produce GMP-relevant data. Includes user provisioning, access removal, role- based access control, and periodic access reviews. 21 CFR: 11.10(d), 11.300(a); 111.105, 111.140.
NSF/ANSI 455-2: 4.9.1, 4.9.2 (system access & security).
SOP-IT-ESIG Electronic Signatures Defines WHAT-level controls for creation, use, authentication, and protection of electronic signatures used within GMP systems to ensure signatures are attributable, secure, and compliant. Applies to all electronic systems where signatures represent approval, review, verification, or decision-making related to GMP records, including QA approval, QC review, training completions, and batch record executions. 21 CFR: 11.50, 11.100, 11.200.
NSF/ANSI 455-2: 4.9.3 (electronic records & signatures).
SOP-IT-BACKUP Backup Management Establishes WHAT-level controls for backing up, protecting, storing, and restoring GMP data to ensure data integrity, availability, and business continuity. Applies to all servers, systems, applications, databases, and GMP-relevant data repositories that require retention, restoration, or preservation to support quality and compliance needs. 21 CFR: 11.10(c), 111.605, 111.610.
NSF/ANSI 455-2: 4.9.2 (data protection & retention).
SOP-IT-VALIDATE Computer System Validation Defines WHAT-level controls to ensure computerized systems used for GMP activities are validated for intended use, function as designed, and remain in a validated state throughout their lifecycle. Applies to all GMP-relevant computerized systems requiring validation, including LIMS, QMS, LMS, ERP, laboratory instruments with software, and data management systems. 21 CFR: 11.10(a), 11.10(k); 111.503.
NSF/ANSI 455-2: 4.9.4 (computer validation requirements).

AA Type–Specific Execution Requirements

Check (CHK) Requirements

Checks (CHK) are verification activities used to confirm that required, GMP-critical actions, reviews, or prerequisites have been completed in accordance with the governing SOP or WIN. Checks do not instruct how to perform tasks; they verify that required conditions or outcomes have been met.

Log (LG) Requirements

Logs provide chronological documentation of repeated or ongoing monitoring activities. Logs in this Process Family must:

Template (TMP) Requirements

Templates provide standardized data fields for recording measurements, quantities, equipment settings, sampling results, or other structured GMP data. Templates in this Process Family must:

Record / Form (FRM) Requirements

Records (FRMs) capture the finalized GMP evidence for this Process Family. All Records must comply with ALCOA+, GDP, Part 11 requirements for electronic records, and the metadata and retention standards defined in L0 Section 16 — AA Governance. Records may incorporate Checks, Logs, and Templates as embedded evidence.

Citations above support WHAT requirements; compliance traceability is maintained at the L0 level.

Section 3 - General Training Requirements

Section 4 - Unified Responsibility & High-Level Control Mapping

Role Primary Responsibilities (WHAT) High-Level Controls (WHAT Requirements)
IT • Maintain system access controls and ensure access is granted only to authorized and trained personnel.
• Manage user provisioning, role assignments, password policies, and access removal.
• Maintain electronic signature configurations, authentication methods, and audit trail protections.
• Oversee backup creation, storage, restoration testing, and integrity validation.
• Own computer system validation lifecycle activities across GMP-relevant systems.
• Escalate system security issues, data integrity concerns, or validation gaps.
• Enforce secure, role-based access aligned with training and job responsibilities.
• Maintain data integrity and ALCOA+ controls for electronic systems.
• Ensure validated status of computerized systems used for GMP work.
• Maintain secure and retrievable backups for regulated data.
• Preserve audit trails, electronic signature mappings, and authentication configurations.
QA • Approve IT-controlled procedures affecting electronic records and signature integrity.
• Review and approve validation documentation and change control for regulated systems.
• Verify that electronic signatures and audit trails meet GMP expectations.
• Review backup, restoration evidence, and IT compliance documentation during audits and investigations.
• Ensure compliance with 21 CFR Part 11 and electronic record requirements.
• Approve validation approaches, protocols, and reports.
• Apply independent review of system access lists and periodic access reviews.
• Enforce alignment between IT controls and corporate QMS requirements.
QA-SOD • Independently verify IT-controlled actions that require second-level approval, including electronic signature assignments, validation steps, or access removals.
• Review discrepancies or exceptions flagged during IT security, validation, or access monitoring.
• Apply independent verification controls to ensure system integrity and security.
• Ensure impartial review of access rights, audit trails, and validation evidence.
• Confirm documentation completeness and data integrity for IT-controlled activities.
QC • Use validated systems for data entry, review, testing documentation, and record approval.
• Report system access issues, data integrity concerns, or electronic signature anomalies.
• Comply with password, access, and security expectations for electronic systems.
• Ensure data entered in systems meets ALCOA+ principles.
• Maintain security of login credentials.
• Support audit readiness through complete and accurate electronic records.
• Escalate system or data discrepancies to IT and QA.
Functional Supervisors
(WH, PRO, PKG, SAN, ENG)
• Identify access needs for personnel in their departments.
• Ensure personnel complete system training prior to requesting access.
• Notify IT and QA when personnel roles change or access must be removed.
• Support validation activities requiring functional SMEs.
• Maintain accurate mapping of system access to job responsibilities.
• Ensure system users maintain required qualifications.
• Support periodic access reviews and remediation.
• Provide functional input during validation or change control.
Document Control • Maintain controlled versions of IT-relevant SOPs, WINs, and validation documents.
• Ensure electronic forms and templates are controlled and published through approved systems.
• Support retrieval of electronic and validation records during audits.
• Ensure document lifecycle is synchronized with validated system changes.
• Maintain traceability for controlled electronic document revisions.
• Prevent use of outdated or uncontrolled electronic documentation.
Training & Competency • Maintain training assignments for system-specific use, validation awareness, and Part 11 compliance.
• Ensure users complete required training before IT grants access.
• Maintain traceable system-training records for audits and inspections.
• Ensure training aligns with system functionality and security requirements.
• Maintain ALCOA+ integrity of training records.
• Support periodic retraining if system functionality or procedures change.
HR • Provide IT and QA with updates on personnel status changes (new hires, role changes, terminations).
• Support identity verification processes for account provisioning.
• Maintain personnel records that affect access eligibility.
• Ensure access removal triggers are accurately communicated to IT.
• Support validation or audit inquiries regarding employment history.
• Maintain alignment between HR data and system access requirements.
BRM • Maintain governance alignment across all systems and ensure IT controls integrate with enterprise workflows.
• Identify cross-family risks related to electronic systems, validation, or data integrity.
• Support harmonization of IT controls with L0 and enterprise processes.
• Validate consistency in IT-related requirements across all Families.
• Support evaluation of changes affecting IT systems or electronic record processes.
• Maintain visibility into IT impacts on cross-functional operations.
BPO • Own governance of IT-related quality processes and ensure SOP alignment with L0 requirements.
• Maintain oversight of validation strategy, system risk classification, and electronic data integrity controls.
• Escalate systemic risks involving electronic systems or data security.
• Ensure IT Family Pack compliance with L0 governance and regulatory expectations.
• Validate enterprise-wide consistency of IT controls.
• Support audits, assessments, and regulatory inspections involving computerized systems.

Section 5 - Required AAs & Traceability Matrix (IT)

This section defines the authoritative Auditable Artifacts (AAs) required to demonstrate execution of Information Technology (IT) controls governing system access, electronic signatures, backup management, and computer system validation. All AAs listed below provide objective L4 evidence supporting Part 11, 21 CFR 111, and NSF/ANSI 455-2 requirements.

SOP WIN AA Doc ID AA Name Type Purpose
SOP-IT-ACCESS WIN-IT-ACCESS AA-CHK-IT-ACCESS-APR System Access Approval Checklist CHK Verifies QA-approved provisioning, modification, or removal of system access.
SOP-IT-ACCESS WIN-IT-ACCESS AA-LOG-IT-ACCESS-REL User Access Change Log LOG Chronological record of all user access lifecycle events.
SOP-IT-ESIG WIN-IT-ESIG AA-FRM-IT-ESIG-REL Electronic Signature Authorization Form FRM Authorizes users for compliant electronic signature use.
SOP-IT-ESIG WIN-IT-ESIG AA-REC-IT-ESIG-EVT Electronic Signature Audit Record REC Provides objective evidence of Part 11–compliant e-signature execution.
SOP-IT-BACKUP WIN-IT-BACKUP AA-LOG-IT-BACKUP-DLY System Backup Execution Log LOG Documents successful execution of scheduled system backups.
SOP-IT-BACKUP WIN-IT-BACKUP AA-REC-IT-RESTORE-EVT Backup Restore Test Record REC Demonstrates verified system data restoration capability.
SOP-IT-VALIDATE WIN-IT-VALIDATE AA-FRM-IT-VAL-APR Validation Approval Form FRM Documents QA approval of system validation lifecycle activities.
SOP-IT-VALIDATE WIN-IT-VALIDATE AA-REC-IT-VAL-REL Validation Summary Report REC Confirms validated state and fitness for intended system use.

Authoritative, version-controlled instances of these AAs are maintained in the Enterprise Artifact System of Record (SOR) governed at the L0 level.

Section 6 - AA Deliverable Requirements

6.1 AA Deliverable Definitions

6.2 Emergency Use Only Checklist Mockup

Emergency Use Only — Not a Controlled Record

SYSTEM ACCESS APPROVAL CHECKLIST

[ ] Access request documented
[ ] Role-based access defined
[ ] Segregation of duties verified
[ ] QA approval obtained
[ ] Access provisioned
[ ] Access change logged

Operator Signature: __________  Date: ______
QA Signature: _________________ Date: ______
  

6.3 AA Type–Specific Execution Requirements

Section 7 - WIN Layer (High-Level Operational Workflow)

WIN-IT-ACCESS — System Access Control

  1. Access need is identified and formally requested.
  2. Requested access is role-defined and reviewed.
  3. QA verifies segregation of duties and approves access.
  4. Authorized IT personnel provision or modify access.
  5. Access actions are documented in logs and checklists.

WIN-IT-ESIG — Electronic Signatures

  1. User eligibility for electronic signatures is assessed.
  2. Authorization form is completed and approved.
  3. Signature credentials are issued and activated.
  4. Electronic signatures are applied during GMP activities.
  5. Signature audit records are retained as evidence.

WIN-IT-BACKUP — Backup Management

  1. Backup schedules are established and maintained.
  2. Automated backups execute per approved schedule.
  3. Backup completion is logged.
  4. Periodic restore testing is performed.
  5. Restore test results are documented and retained.

WIN-IT-VALIDATE — Computer System Validation

  1. System scope and validation risk are defined.
  2. Validation activities are executed.
  3. QA reviews validation outcomes.
  4. Validation approval is documented.
  5. Validation summary report is archived.

Section 8 - Governance Inheritance

This Family Pack inherits all enterprise-level governance defined in the L0 Unified Governance Document (L0-QMS-UGD), which serves as the authoritative source for quality, documentation, data integrity, and system requirements. All SOPs, WINs, and FORMs within this Family must be created, maintained, and executed in alignment with L0 rules, including:

L0 requirements apply uniformly and supersede all Family-level content. This Family Pack does not replace or modify L0 governance and operates fully within the enterprise-wide QMS architecture.