3.5 Work instructions & e-records

Paper work instructions are a liability. They are static, easily defaced, and impossible to revoke instantly. If an Engineering Change Order (ECO) is released at 09:00, a paper-based factory is still building the “Old Way” at 10:00. The goal of Electronic Work Instructions (EWI) is not to “digitize the binder,” but to synchronize the operator’s visual field with the active BOM, Revision, and User Capability.

Station control & skill enforcement

Before showing a single instruction, the system must validate the human at the screen. Access is a privilege, not a default state.

1. The login logic

It is recommended to avoid generic “Line 1” accounts whenever possible. Every interaction should trace back to a specific, legal identity.

• Mechanism: Utilize RFID Badge Scans or Biometrics. (Typing passwords is often too slow for the fast-paced production floor).
• Timeout: Implement “Auto-Logout” functionality based on inactivity (e.g. 15 minutes) to prevent “Ghost Records,” where Operator B unintentionally works under Operator A’s login.

2. The skill matrix gate (certification check)

Just because you can log in doesn’t mean you can build.

• Logic: When a Work Order requires a specific skill level (e.g. “Soldering Class 3”) and the user’s profile lacks that certification, the system should block the station and display a “Certification Missing” notice.
• Expiry: When the Certification Date has passed, the system should block the station.
• Override: This typically requires a Supervisor Badge scan to authorize a “Trainee Mode” (where the Supervisor formally accepts liability for the trainee’s work).

3. Shift handover

Production is continuous; shifts are not.

• The “Hot Swap”: Allow Operator B to scan in while Operator A is still logged into the station.
• Action: The system gracefully closes Operator A’s session (recording the End Timestamp) and starts Operator B’s session (recording the Start Timestamp) instantly, preventing unnecessary downtime.

The architecture of EWI

It is insufficient to merely display a static PDF on a monitor. An effective EWI system should be Context-Aware and Interactive.

Context-aware display

The MES knows the Work Order, the Unit ID, and the Routing Step. The screen must filter the content accordingly.

• Logic: When the Unit is Variant A, the system displays Assembly Image A and hides Image B.
• Logic: When the Operator is designated as a Trainee, the system enforces “Step-by-Step” confirmation. Conversely, when the Operator is an Expert, the system may allow a consolidated “Batch” confirmation.

The “read and understood” gate

Operators often ignore updates because they look like the old instructions. Acknowledgment of change must be forced.

• Mechanism: Track the Last_Acknowledged_Rev for every User-Product pair.
• Logic:
  • When the Current Revision is newer than the user’s last acknowledged revision, the system should lock the operational screen.
  • Action: The system displays a “Change Summary” (Diff) and requires a Digital Signature to proceed.
  • Result: This process systematically eliminates the common excuse, “I didn’t know it changed.”

Electronic records (e-records)

The EWI serves as the Input; the e-Record is the resulting Output. Every action taken by the operator generates a permanent, immutable database row. This structured data is your primary defense during an audit (e.g. FDA 21 CFR Part 11 / GMP compliance).

Data capture types

1. Implicit Data (Passive):
   • Who: User ID.
   • When: Timestamp (UTC).
   • Duration: Time_End - Time_Start. (Detects if an operator blindly clicked “OK” in 1 second for a 5-minute task).
2. Explicit Data (Active):
   • Confirmation: “I have inspected the seal.” (Checkbox).
   • Variable: “Torque Value = 4.5 Nm.” (Keypad/Tool Input).
   • Evidence: “Photo of the cable routing.” (Camera Input).

Validation logic

It is important to not accept data blindly. The system should validate data at the point of entry.

• Range Check: When an input value falls outside the defined limits (e.g. a 4.0 to 5.0 range), the system should reject the entry and display an “Out of Spec” warning.
• Format Check: When the operator inputs text into a field expecting a numerical float, the system should block the entry to prevent database errors.
• Mandatory Fields: When a critical required field remains empty, the system should disable the “Complete” or “Next” button.

The “ALCOA+” standard

The ALCOA+ framework must be aligned with to ensure strong data integrity. A robust MES architecture consistently guarantees these five attributes for every digital record:

1. Attributable: Linked to a unique User ID.
2. Legible: Stored in human-readable format (or easily rendered).
3. Contemporaneous: Recorded at the exact moment of execution.
4. Original: The first record is the master.
5. Accurate: Validated against limits (Min/Max) at the source.

Handling corrections

Operators occasionally make mistakes. The system must allow for corrections while simultaneously preserving the original historical record.

The Audit Trail Logic

• Scenario: Operator enters “50mm”, saves, realizes it should be “5.0mm”.
• Action: Operator updates value.
• Database Record:
  • Row 1: Value=“50”, Status=“Obsolete”, Timestamp=10:00, User=John.
  • Row 2: Value=“5.0”, Status=“Active”, Timestamp=10:01, User=John, Reason=“Entry Error”.
• Constraint: As a rule, a direct SQL UPDATE or DELETE must never be performed on a production compliance record. An audit trail must always be established by performing an INSERT command to create a new, versioned row.

Final Checkout: Work instructions & e-records

Category	Metric / Control	Threshold / Rule
Access	Skill Gate	Block Login if User_Certification is missing or expired.
Identity	Attribution	100% of records linked to a specific User ID (No generic logins).
Versioning	Rev Match	Engineering Work Instruction (EWI) Revision must match the Work Order Bill of Materials (BOM) Revision.
Training	Change Control	Force “Read & Sign” pop-up when Operator encounters a new Revision.
Integrity	Immutability	Ensure Zero DELETE permissions exist on the Production History tables.
Inputs	Logic Gates	Block the “Next Step” action until all designated Mandatory Fields are populated.
Audit	Correction	Field edits require a formal “Reason Code” and must preserve the original value.