This is the second part in a series of five articles that will provide a deep dive into the Safety module of core Maximo. In the first part we examined Hazards and Precautions. You can find it here:

Hazards and Precautions

The Safety module is a sub-module of the Planning module. Following our review of the Lock Out / Tag Out application we will see how Hazards, Precautions, Hazardous Materials and these Lock Out / Tag Out rules come together when you build a Safety Plan.

The first thing to recognise in the Lock Out / Tag Out application is that these records are defined at the Site level. The second point is that they are defined against locations or assets and an asset/location can have multiple Tag Out sequences defined for it.

When creating a Tag Out record Location and Asset fields are mutually exclusive, if you enter an Asset, 11430 in this case, then the Location field becomes read-only. Similarly, if you had entered a Location, the Asset field would be read-only.

The Required State field is the end point state of the Tag Out record, after applying the operations in the Apply Sequence. To reach the state when there is no water flowing through the centrifugal pump there are five operations to perform and then a physical tag can be applied to the assets which identifies the person who applied the locking device, the tag will have a highly visible “Stop” sign with wording like “Do not operate” in red lettering.

In this example, to isolate asset 11430, you lock off asset 12222, another centrifugal pump, close intake valve 339-A, open drain valve 339-D giving time for full drainage, and then you close drain valve 339-D, before writing out and applying a tag to asset 12222. This is the sequence defined by the Apply Sequence attribute, the exact sequence to follow.

After maintenance of asset 11430, the unlocking process starts with opening Intake Valve 339-A, checking for leaks, and then removing the lock on the centrifugal pump 12222 and then its tag. Not all of the steps used in the Apply Sequence will be used in the Remove Sequence. Notice, that you do not have to have assets records for all of the equipment used in a Lock Out / Tag Out procedure.

There is likely to be a drawing showing the isolation procedure, and so this would be usefully added as a linked document, as long as any updates to the original drawing will be reflected in the attached document visible from within Maximo.

In the second example on the same asset 11430, we have a LOTO procedure for electrically isolating the centrifugal pump, the Required State is EL-ISO. There is no domain on this attribute (REQUIREDSTATE), but it would be useful to provide an ALN domain for it during implementation.

In this example to isolate the Centrifugal Pump you open breaker 429-A-13, then close breaker 429-A-14, then you can open breaker 429-B-07. At each step you would apply a locking device with padlock, and the padlock keys would then be added to a lock box to keep them safe.

Notice, in this case, the removal sequence (de-isolation) is not the same as the apply sequence (isolation) but in reverse.

As you look at a Lock Out / Tag Out record, the header is the TAGOUT object. There are 8 crossover fields on this object, TAG01 to TAG08, which can be used for additional information. The data entered into these fields will be copied to the Work Order Tag Out fields with the same names in object WOTAGOUT. The table window in the Lock Out / Tag Out application comes from the LOCKOUT object. This has 10 crossover fields LCK01 to LCK10 and they copy to the same fields in the Work Order Lock Out object WOLOCKOUT. 

The Safety Module Overview article has two entity diagrams and documents all of the standard crossover fields used with the safety applications.