Digital Lock On

Appearance

Verification Matrix — Plant Operations ​

Implements:

  • REQ-PLANT-001 Locking Known Plant On (QR)
  • REQ-PLANT-002 Locking Miscellaneous Plant On (Manually)
  • REQ-PLANT-003 Plant Handover (Operator or MPC)
  • REQ-PLANT-004 Plant Lock-off

Requirement → Scenario Index ​

Requirement RefRequirement (short)Scenario IDs
REQ-PLANT-001: QR Plant Lock-on
EDR-1SP initiates plant lock-on, QR scan availableTC-PLANT-LOCKON-001
EDR-2QR scanned, plant details displayedTC-PLANT-LOCKON-001
EDR-3Operator assigned during lock-on (mandatory)TC-PLANT-LOCKON-001, TC-PLANT-LOCKON-002, TC-PLANT-VAL-004
EDR-4MPC assigned during lock-on (optional)TC-PLANT-LOCKON-002, TC-PLANT-VAL-005
EDR-5Success confirmation displayedTC-PLANT-LOCKON-001, TC-PLANT-LOCKON-002
EDR-6Plant list updatedTC-PLANT-LOCKON-001, TC-PLANT-LOCKON-002
EDR-7Offline QR lock-on supportedTC-PLANT-EDGE-001
UBI-1SP can self-assign as Operator/MPCTC-PLANT-LOCKON-005, TC-PLANT-LOCKON-006
REQ-PLANT-002: Manual Plant Lock-on
EDR-1Manual lock-on availableTC-PLANT-MANUAL-001, TC-PLANT-MANUAL-002
EDR-2Creates new plant record and locks onTC-PLANT-MANUAL-001, TC-PLANT-MANUAL-002
EDR-3Minimal data required for plant recordTC-PLANT-MANUAL-001, TC-PLANT-MANUAL-002
EDR-4Offline operation supportedTC-PLANT-EDGE-002
REQ-PLANT-003: Plant Handover
EDR-1Handover Operator to different workerTC-PLANT-HANDOVER-001
EDR-2Handover MPC to different workerTC-PLANT-HANDOVER-002
EDR-3Handover both Operator and MPCTC-PLANT-HANDOVER-003
EDR-4Current assignments displayed before handoverTC-PLANT-HANDOVER-001, TC-PLANT-HANDOVER-002, TC-PLANT-HANDOVER-003
EDR-5Independent role changes in single operationTC-PLANT-HANDOVER-003
EDR-6Offline handover supportedTC-PLANT-EDGE-003
UBI-1SP can assign themselves during handoverTC-PLANT-HANDOVER-001, TC-PLANT-HANDOVER-002
REQ-PLANT-004: Plant Lock-off
EDR-1QR lock-off succeedsTC-PLANT-LOCKOFF-001
EDR-2Manual lock-off succeedsTC-PLANT-LOCKOFF-002
EDR-3Clears Operator and MPC assignmentsTC-PLANT-LOCKOFF-003
EDR-4Multiple plant handled correctlyTC-PLANT-LOCKOFF-004
EDR-5Offline lock-off supportedTC-PLANT-EDGE-004
Cross-cutting
UNW-1Same person as both Operator and MPC blockedTC-PLANT-VAL-001
UNW-2Plant already locked on elsewhere blocks lock-onTC-PLANT-VAL-002
UNW-3Plant already locked on same site blocks lock-onTC-PLANT-VAL-003
UNW-4Operator assignment mandatoryTC-PLANT-VAL-004
UNW-5MPC assignment optionalTC-PLANT-VAL-005
UNW-6Wrong authority blocks plant operationsTC-PLANT-PERM-001, TC-PLANT-PERM-002
UNW-7Worker must be locked on for assignmentTC-PLANT-VAL-006
AUD-1Audit trail captures all plant operationsTC-PLANT-AUDIT-001

Scenarios (at a glance) ​

IDTitleType
2.1 QR Plant Lock-on (REQ-PLANT-001)
TC-PLANT-LOCKON-001 (3.9.1.1)QR lock-on with Operator assignment onlyPositive
TC-PLANT-LOCKON-002 (3.9.1.2)QR lock-on with Operator and MPC assignmentPositive
TC-PLANT-LOCKON-005 (3.9.1.3)SP assigns self as OperatorPositive
TC-PLANT-LOCKON-006 (3.9.1.4)SP assigns self as MPCPositive
2.2 Manual Plant Lock-on (REQ-PLANT-002)
TC-PLANT-MANUAL-001 (3.9.2.1)Manual lock-on creates plant record with OperatorPositive
TC-PLANT-MANUAL-002 (3.9.2.2)Manual lock-on with Operator and MPCPositive
2.3 Plant Handover (REQ-PLANT-003)
TC-PLANT-HANDOVER-001 (3.9.3.1)Handover Operator only to different workerPositive
TC-PLANT-HANDOVER-002 (3.9.3.2)Handover MPC only to different workerPositive
TC-PLANT-HANDOVER-003 (3.9.3.3)Handover both Operator and MPC togetherPositive
2.4 Plant Lock-off (REQ-PLANT-004)
TC-PLANT-LOCKOFF-001 (3.9.4.1)QR lock-off succeedsPositive
TC-PLANT-LOCKOFF-002 (3.9.4.2)Manual lock-off succeedsPositive
TC-PLANT-LOCKOFF-003 (3.9.4.3)Lock-off when worker operates multiple plantPositive
2.5 Validation Rules
TC-PLANT-VAL-001Block same person as Operator and MPCDefensive
TC-PLANT-VAL-002Block plant already locked on elsewhereDefensive
TC-PLANT-VAL-003Block plant already locked on same siteDefensive
TC-PLANT-VAL-004 (3.9.1.1, 3.9.1.2, 3.9.2.1, 3.9.2.2)Require Operator assignment (mandatory)Defensive
2.6 Permission Boundaries
TC-PLANT-PERM-001SP (Other) cannot lock on plantNegative
TC-PLANT-PERM-002RPO cannot lock on plantNegative
2.7 Edge Cases
TC-PLANT-EDGE-001Offline QR lock-on succeedsEdge
TC-PLANT-EDGE-002Offline manual lock-on succeedsEdge
TC-PLANT-EDGE-003Offline handover succeedsEdge
TC-PLANT-EDGE-004Offline lock-off succeedsEdge
2.8 Audit Trail
(contained in all scenarios above)Audit data captures all plant operationsPositive

Scenario details ​

2.1 QR Plant Lock-on (REQ-PLANT-001) ​

TC-PLANT-LOCKON-001: QR lock-on with Operator assignment only
  • Arrange
    • User is logged in as Site Protector assigned to Worksite A
    • Worksite A is Enabled
    • Plant (known, with QR code) state: Not on Site
    • Worker A is Locked On (Active) at Worksite A
    • Device is online
  • Act
    • SP initiates plant lock-on workflow
    • SP scans plant QR code
    • System displays plant details
    • SP selects Worker A as Operator
    • SP leaves MPC assignment blank
    • SP confirms lock-on
  • Assert
    • System displays success confirmation
    • Plant state changes to Locked On (Active)
    • Plant assigned to Worksite A
    • Operator: Worker A
    • MPC: (none)
    • Plant appears in active plant list
    • Audit trail records QR lock-on method, Operator assignment, timestamp

TC-PLANT-LOCKON-002: QR lock-on with Operator and MPC assignment
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worksite A is Enabled
    • Plant (known, with QR code) state: Not on Site
    • Worker A is Locked On (Active) at Worksite A
    • Worker B is Locked On (Active) at Worksite A
    • Worker A ≠ Worker B
    • Device is online
  • Act
    • SP initiates plant lock-on workflow
    • SP scans plant QR code
    • System displays plant details
    • SP selects Worker A as Operator
    • SP selects Worker B as MPC
    • SP confirms lock-on
  • Assert
    • System displays success confirmation
    • Plant state changes to Locked On (Active)
    • Plant assigned to Worksite A
    • Operator: Worker A
    • MPC: Worker B
    • Plant appears in active plant list with both assignments visible
    • Audit trail records QR lock-on method, Operator and MPC assignments, timestamp

TC-PLANT-LOCKON-005: SP assigns self as Operator
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worksite A is Enabled
    • Plant (known, with QR code) state: Not on Site
    • No workers currently locked on (SP only on site)
    • Device is online
  • Act
    • SP initiates plant lock-on workflow
    • SP scans plant QR code
    • SP selects themselves as Operator
    • SP confirms lock-on
  • Assert
    • System allows self-assignment
    • Plant state changes to Locked On (Active)
    • Operator: Site Protector (self)
    • MPC: (none)
    • Plant appears in active plant list
    • Self-assignment recorded in audit trail

TC-PLANT-LOCKON-006: SP assigns self as MPC
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worksite A is Enabled
    • Plant (known, with QR code) state: Not on Site
    • Worker A is Locked On (Active) at Worksite A
    • Device is online
  • Act
    • SP initiates plant lock-on workflow
    • SP scans plant QR code
    • SP selects Worker A as Operator
    • SP selects themselves as MPC
    • SP confirms lock-on
  • Assert
    • System allows self-assignment as MPC
    • Plant state changes to Locked On (Active)
    • Operator: Worker A
    • MPC: Site Protector (self)
    • Plant appears in active plant list
    • Self-assignment recorded in audit trail

2.2 Manual Plant Lock-on (REQ-PLANT-002) ​

TC-PLANT-MANUAL-001: Manual lock-on creates plant record with Operator
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worksite A is Enabled
    • Plant needs to be locked on but has no QR code (miscellaneous plant)
    • Worker A is Locked On (Active) at Worksite A
    • Device is online
  • Act
    • SP initiates manual plant lock-on
    • SP enters plant details:
      • Plant type (e.g., V/MP/HRV)
      • Plant description/identifier
      • Other required fields
    • SP selects Worker A as Operator
    • SP leaves MPC assignment blank
    • SP confirms lock-on
  • Assert
    • New plant record created in Admin database
    • Plant immediately locked on to Worksite A
    • Plant state: Locked On (Active)
    • Operator: Worker A
    • MPC: (none)
    • Plant appears in active plant list
    • All required fields captured
    • Audit trail records manual lock-on method, plant creation, Operator assignment

TC-PLANT-MANUAL-002: Manual lock-on with Operator and MPC
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worksite A is Enabled
    • Plant needs to be locked on but has no QR code (miscellaneous plant)
    • Worker A is Locked On (Active) at Worksite A
    • Worker B is Locked On (Active) at Worksite A
    • Worker A ≠ Worker B
    • Device is online
  • Act
    • SP initiates manual plant lock-on
    • SP enters plant details
    • SP selects Worker A as Operator
    • SP selects Worker B as MPC
    • SP confirms lock-on
  • Assert
    • New plant record created
    • Plant immediately locked on to Worksite A
    • Plant state: Locked On (Active)
    • Operator: Worker A
    • MPC: Worker B
    • Plant appears in active plant list with both assignments visible
    • Audit trail records manual lock-on method, plant creation, both assignments

2.3 Plant Handover (REQ-PLANT-003) ​

TC-PLANT-HANDOVER-001: Handover Operator only to different worker
  • Arrange
    • User is logged in as Site Protector (Own)
    • Plant is Locked On (Active) at Worksite A
    • Current Operator: Worker A
    • Current MPC: Worker B
    • Worker C is Locked On (Active) at Worksite A
    • All workers are different people
    • Device is online
  • Act
    • SP selects plant for handover
    • System displays current assignments:
      • Operator: Worker A
      • MPC: Worker B
    • SP selects Worker C as new Operator
    • SP leaves MPC unchanged (Worker B)
    • SP confirms handover
  • Assert
    • System displays success confirmation
    • Plant remains Locked On (Active)
    • New Operator: Worker C
    • MPC unchanged: Worker B
    • Plant list reflects new Operator assignment
    • Audit trail records Operator handover from Worker A to Worker C, timestamp

TC-PLANT-HANDOVER-002: Handover MPC only to different worker
  • Arrange
    • User is logged in as Site Protector (Own)
    • Plant is Locked On (Active) at Worksite A
    • Current Operator: Worker A
    • Current MPC: Worker B
    • Worker D is Locked On (Active) at Worksite A
    • All workers are different people
    • Device is online
  • Act
    • SP selects plant for handover
    • System displays current assignments:
      • Operator: Worker A
      • MPC: Worker B
    • SP leaves Operator unchanged (Worker A)
    • SP selects Worker D as new MPC
    • SP confirms handover
  • Assert
    • System displays success confirmation
    • Plant remains Locked On (Active)
    • Operator unchanged: Worker A
    • New MPC: Worker D
    • Plant list reflects new MPC assignment
    • Audit trail records MPC handover from Worker B to Worker D, timestamp

TC-PLANT-HANDOVER-003: Handover both Operator and MPC together
  • Arrange
    • User is logged in as Site Protector (Own)
    • Plant is Locked On (Active) at Worksite A
    • Current Operator: Worker A
    • Current MPC: Worker B
    • Worker C is Locked On (Active) at Worksite A
    • Worker D is Locked On (Active) at Worksite A
    • All workers are different people
    • Device is online
  • Act
    • SP selects plant for handover
    • System displays current assignments:
      • Operator: Worker A
      • MPC: Worker B
    • SP selects Worker C as new Operator
    • SP selects Worker D as new MPC
    • SP confirms handover
  • Assert
    • System displays success confirmation
    • Plant remains Locked On (Active)
    • New Operator: Worker C
    • New MPC: Worker D
    • Plant list reflects both new assignments
    • Audit trail records both Operator and MPC handovers in single operation, timestamp
    • Independent role changes completed together

2.4 Plant Lock-off (REQ-PLANT-004) ​

TC-PLANT-LOCKOFF-001: QR lock-off succeeds
  • Arrange
    • User is logged in as Site Protector (Own)
    • Plant is Locked On (Active) at Worksite A
    • Plant has QR code
    • Operator: Worker A
    • MPC: Worker B
    • Device is online
  • Act
    • SP initiates plant lock-off
    • SP scans plant QR code
    • SP confirms lock-off
  • Assert
    • System displays success confirmation
    • Plant state changes to Not on Site
    • Operator assignment cleared
    • MPC assignment cleared
    • Plant removed from active plant list
    • Audit trail records QR lock-off method, previous assignments, timestamp

TC-PLANT-LOCKOFF-002: Manual lock-off succeeds
  • Arrange
    • User is logged in as Site Protector (Own)
    • Plant is Locked On (Active) at Worksite A
    • Operator: Worker A
    • MPC: Worker B
    • Device is online
  • Act
    • SP initiates manual plant lock-off
    • SP selects plant from active plant list
    • SP confirms lock-off
  • Assert
    • System displays success confirmation
    • Plant state changes to Not on Site
    • Operator assignment cleared
    • MPC assignment cleared
    • Plant removed from active plant list
    • Audit trail records manual lock-off method, previous assignments, timestamp

TC-PLANT-LOCKOFF-003: Lock-off when worker operates multiple plant
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker A is Operator for Plant X (Locked On - Active)
    • Worker A is also Operator for Plant Y (Locked On - Active)
    • Both Plant X and Plant Y at Worksite A
    • Device is online
  • Act
    • SP locks off Plant X only
  • Assert
    • Plant X state changes to Not on Site
    • Plant X Operator assignment cleared
    • Plant Y remains Locked On (Active)
    • Worker A remains Operator for Plant Y (unchanged)
    • Only Plant X cleared from assignments
    • Worker A still visible as assigned to Plant Y
    • Audit trail shows Plant X lock-off only

2.5 Validation Rules ​

TC-PLANT-VAL-001: Block same person as Operator and MPC
  • Arrange
    • User is logged in as Site Protector (Own)
    • Plant state: Not on Site
    • Worker A is Locked On (Active) at Worksite A
    • Device is online
  • Act
    • SP initiates plant lock-on (QR or manual)
    • SP selects Worker A as Operator
    • SP attempts to select Worker A as MPC
  • Assert
    • System blocks assignment
    • Validation error displayed: "Cannot assign same person as both Operator and MPC"
    • Lock-on cannot proceed until MPC changed or cleared
    • Worker A remains available for selection but validation prevents duplicate assignment

TC-PLANT-VAL-002: Block plant already locked on elsewhere
  • Arrange
    • User is logged in as Site Protector for Worksite A
    • Plant is currently Locked On (Active) at Worksite B (different worksite, same or different PWA)
    • Device is online
  • Act
    • SP attempts to lock on plant to Worksite A
    • SP scans plant QR
  • Assert
    • System blocks lock-on
    • Error message: "Plant already locked on at different worksite, must lock off first"
    • Lock-on cannot proceed
    • Plant state remains Locked On at Worksite B

TC-PLANT-VAL-003: Block plant already locked on same site
  • Arrange
    • User is logged in as Site Protector (Own)
    • Plant is currently Locked On (Active) at Worksite A
    • Device is online
  • Act
    • SP attempts to lock on same plant again to Worksite A
    • SP scans plant QR or selects plant
  • Assert
    • System blocks lock-on
    • Error message: "Plant already locked on to this worksite"
    • Lock-on cannot proceed
    • Duplicate lock-on prevented

TC-PLANT-VAL-004: Require Operator assignment (mandatory)
  • Arrange
    • User is logged in as Site Protector (Own)
    • Plant state: Not on Site
    • Device is online
  • Act
    • SP initiates plant lock-on (QR or manual)
    • SP does not select an Operator
    • SP leaves MPC blank as well
    • SP attempts to confirm lock-on
  • Assert
    • System blocks lock-on
    • Validation error: e.g. "Operator required"
    • Lock-on button disabled or validation prevents submission
    • Cannot proceed until Operator assigned

2.6 Permission Boundaries ​

TC-PLANT-PERM-001: SP (Other) cannot lock on plant
  • Arrange
    • User is logged in as Site Protector assigned to Worksite B
    • Attempting to lock on plant to Worksite A
    • Plant state: Not on Site
  • Act
    • SP (Other) attempts to initiate plant lock-on for Worksite A
  • Assert
    • Access denied
    • Plant lock-on action not available or blocked for Worksite A
    • SP (Other) cannot perform operations on different worksites

TC-PLANT-PERM-002: RPO cannot lock on plant
  • Arrange
    • User is logged in as RPO assigned to PWA 2
    • Attempting to access plant lock-on for Worksite A (in different PWA 1)
    • Plant state: Not on Site
  • Act
    • RPO attempts to initiate plant lock-on
  • Assert
    • Access denied
    • Plant lock-on action not available to RPO
    • RPO does not have plant operation permissions unless also acting as Site Protector

2.7 Edge Cases ​

TC-PLANT-EDGE-001: Offline QR lock-on succeeds
  • Arrange
    • User is logged in as Site Protector (Own)
    • Device is offline
    • Plant (known, with QR code) state: Not on Site (cached)
    • Worker A is Locked On (Active) at Worksite A (cached)
  • Act
    • SP initiates plant lock-on workflow offline
    • SP scans plant QR code
    • SP selects Worker A as Operator
    • SP confirms lock-on
  • Assert
    • Lock-on succeeds locally
    • Plant state changes to Locked On (Active) in local cache
    • Operator: Worker A
    • Event queued for sync when connection restored
    • User experience uninterrupted by offline state

TC-PLANT-EDGE-002: Offline manual lock-on succeeds
  • Arrange
    • User is logged in as Site Protector (Own)
    • Device is offline
    • Worker A is Locked On (Active) at Worksite A (cached)
  • Act
    • SP initiates manual plant lock-on offline
    • SP enters plant details
    • SP selects Worker A as Operator
    • SP confirms lock-on
  • Assert
    • New plant record created locally
    • Plant locked on locally with state: Locked On (Active)
    • Operator: Worker A
    • Event queued for sync when connection restored
    • Plant appears in local active plant list

TC-PLANT-EDGE-003: Offline handover succeeds
  • Arrange
    • User is logged in as Site Protector (Own)
    • Device is offline
    • Plant is Locked On (Active) at Worksite A (cached)
    • Current Operator: Worker A (cached)
    • Worker B is Locked On (Active) at Worksite A (cached)
  • Act
    • SP initiates handover offline
    • SP changes Operator from Worker A to Worker B
    • SP confirms handover
  • Assert
    • Handover succeeds locally
    • New Operator: Worker B (in local cache)
    • Event queued for sync when connection restored
    • Plant list reflects change locally

TC-PLANT-EDGE-004: Offline lock-off succeeds
  • Arrange
    • User is logged in as Site Protector (Own)
    • Device is offline
    • Plant is Locked On (Active) at Worksite A (cached)
    • Operator: Worker A (cached)
  • Act
    • SP initiates lock-off offline
    • SP confirms lock-off
  • Assert
    • Lock-off succeeds locally
    • Plant state changes to Not on Site in local cache
    • Operator assignment cleared locally
    • Event queued for sync when connection restored
    • Plant removed from local active plant list

Internal use only