Reference · built on requestOperator by FibricSafety, security & compliance

Lockout Verification

Compares lockout work orders with the equipment's tag state and proposes the isolation checklist, flagging assets still energized.

Request accessPricing ↗

About

Lockout Verification is an operator job for the moment between a work order being assigned and a technician putting hands on a machine. It reads work orders that call for lockout from IBM Maximo, Fiix, MaintainX, or UpKeep, with the asset and the isolation points your procedure lists for it. It reads the state of those points from the control layer: tag values through KEPServerEX, Allen-Bradley Logix controller tags, SIMATIC S7 tags over OPC UA, or Modbus registers on a drive.

Where a tag shows a motor running, a drive enabled, or a disconnect closed while the work order says lockout applied, it flags the asset and proposes the isolation checklist for that procedure. The technician still tries the start button. OSHA 1910.147 puts that verification on the authorized employee, not on a tag.

This is a reference listing. It documents what Fibric would read from Lockout Verification and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Work orders that require lockout: mxapiwodetail in IBM Maximo, WorkOrder records in Fiix, /workorders in MaintainX, and /work-orders/ in UpKeep, with asset and status
  • The energy isolation points for each asset and the procedure steps, as you keep them against the asset or in a sheet
  • Tag values with quality and timestamp from KEPServerEX through /iotgateway/read, and controller-scope tags from Allen-Bradley Logix by symbolic name
  • Run, enable, and fault states from SIMATIC S7 tags exposed over OPC UA, and drive registers such as run state and speed over Modbus TCP
  • Work order events: assigned, started, and closed, from the maintenance connector's webhooks or status changes

Proposed actions

  • Target capability: propose the isolation checklist for the asset, attached to the work order, with each point, its tag reading, and its expected isolated state
  • Target capability: propose flagging an asset as still energized to the technician and supervisor in Microsoft Teams or Slack, with tag, value, and timestamp
  • Target capability: propose a hold on the work order's start until every point reads isolated and the technician records the try-out step
  • Target capability: propose the record of isolation and restoration times on the work order at close, with the readings at each step

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Check a conveyor before the Maximo order starts

    A Maximo work order with a lockout flag names the conveyor. The operator reads the motor run bit through KEPServerEX and proposes the checklist; a run bit still true flags the asset in Teams.

    With IBM Maximo Manage, KEPServerEX, Microsoft Teams

  • Read the Logix tags directly

    For a press on an Allen-Bradley Logix controller, the operator reads the drive-enable and safety-relay tags by name and attaches them to the MaintainX work order's checklist with timestamps, posting the flag in Slack.

    With Allen-Bradley Logix 5000, MaintainX, Slack

  • Cover the drives over Modbus

    A Fiix work order on a pump station reads run state and speed from each drive over Modbus TCP. Any drive still running when lockout is claimed becomes a flag to the supervisor in Teams.

    With Fiix, Modbus TCP, Microsoft Teams

  • Log restoration on the S7 line

    At close, the operator reads S7 tags over OPC UA for the line and proposes the isolation and restoration times on the UpKeep work order, with readings at each step.

    With SIMATIC S7-1500, UpKeep

Requirements

  • One maintenance connector whose work orders can carry a lockout requirement: IBM Maximo, Fiix, MaintainX, or UpKeep
  • One industrial connector that exposes the asset's state: KEPServerEX, Allen-Bradley Logix 5000, SIMATIC S7-1500 over OPC UA, or Modbus TCP
  • A list per asset of isolation points and the tags that reflect them, kept against the asset or in the operator's configuration
  • One messaging connector for flags to the technician and supervisor: Microsoft Teams or Slack
Authentication
Reads work orders through the maintenance connector's API key and tag values through the industrial connectors' gateway or controller credentials; it writes only to work orders and channels, and holds no credentials of its own.

Limits

  • A tag is not a lock. It reads a controller's view of state and cannot see a padlock, a blank flange, or stored energy
  • It never writes to a controller, drive, or disconnect. It does not stop, start, or isolate anything
  • An isolation point with no tag behind it is listed on the checklist without a reading, and the technician confirms it by hand
  • It supports, and does not replace, the energy control procedure and periodic inspection that OSHA 1910.147 requires of the employer

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Lockout Verification ↗

Questions and answers

What does the technician or supervisor approve?
The technician or supervisor approves the checklist, any hold, and the close-out record. Each shows the work order, the isolation points, the tag readings with their times, and the expected state. A flag is a message; a hold changes the work order only after approval.
What stays on the work order?
One receipt per work order: the points, each reading with timestamp and quality, the checklist as approved, any flag raised, the try-out step as the technician recorded it, and restoration readings at close. It stays on the work order.
Does a green checklist mean it is safe to work?
No. It means the tags the operator can read agree with the isolation claimed. The authorized employee still verifies isolation and de-energization before starting, as 1910.147(d)(6) requires. The checklist records that step; it does not perform it.
Ask about Lockout Verification

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy