Lockout tag out incidents - Genetec Mission Control™ 2.12

Genetec Mission Control™ Supplemental Guide for Incident Workflow Configurations 2.12.1.0

Applies to
Genetec Mission Control™ 2.12
Last updated
2019-11-28
Content type
Guides
Guides > User guides
Language
English (United States)
Product line
Mission Control > Genetec Mission Control™
Version
2.12

To protect workers from risk or harm during lockout maintenance procedures, there are mandatory safety procedures. During lockout work, the usual safety systems on machinery can be off, making additional precautions necessary. You must therefore incorporate established safety procedures into your incident procedures and your workflow design.

Considerations for Lockout tag out incident configuration

Lockout incidents are generally planned work. There is less system automation and more incident procedure to be monitored and logged.

The Lockout tag out incident configuration must include the following:
Identity
Define the incident. Select an icon and color scheme that is unique and reflects the nature of the incident.

Your operators can see all the incidents assigned to them in the incident list in the Incident monitoring task in Security Desk. Having dedicated icons and color schemes gives them an instant snapshot of the state of their zones or areas.

Properties
The operator must be able to trigger the incident manually. This can be configured by selecting Allow manual trigger in the Properties page of the Incident configuration task.
Recipients
Select recipients for incident management and notification.

Because Lockout tag out incidents are typically triggered manually by the operators in Security Desk, you can select Simple recipient configuration in the Recipients page of the Incident configuration task.

In this example, everyone is notified that Lockout tag out work has begun.

Triggers
While Lockout tag out incidents are planned work and need a manual trigger, they can also be configured with system events as triggers. System incident triggers can be system events, such as Zone maintenance started, with conditions of equipment failure, such as AC fail or Battery fail.
Procedure
This incident needs a dynamic incident procedure so the system and procedure can adapt to operator responses.
Workflow
In this example, the only two actions that the system needs to perform can be configured in the incident workflow using the Disarm zone activity and Dispatch incident activity.

Procedure for Lockout tag out incidents

If a procedure already exists to handle Lockout tag out incidents, you can import those steps from a CSV file into the dynamic incident procedure of the incident.

If not, create an incident procedure that validates existing safety measures and provides steps of action to complete the task:
  1. Check if the equipment can be disengaged during maintenance.
    If it can be disengaged, follow the steps for lockout procedure:
    • Disconnect power supply to it.
    • Ensure the installation is dead. If it is, then carry out earthing and short-circuiting.
    • Ensure that there is protection against adjacent live parts.
  2. If the equipment cannot be disengaged, ensure that there is an equipment-specific servicing procedure.
    • If there are no safety measures in place, stop the job and notify the supervisors.
    • If there are safety measure in place, proceed with the lockout procedure.