SMP 365 Isolation & Lockout

What is SMP 365 Isolation & Lockout?

SMP 365 Isolation & Lockout organises isolation records, energy sources, procedures, lock accountability, verification, custody transfers and return-to-service reviews. It gives maintenance and operational teams a structured way to follow the information surrounding an isolation rather than relying on an equipment name and a single completion checkbox.

The distinction between the record and the physical control is fundamental. Software does not isolate equipment, prove the absence of hazardous energy or make a plant safe to operate. Those activities remain with competent, authorised people using the organisation’s approved procedures. The system supports the visibility and review of their recorded evidence.

Describe the isolation boundary and energy sources

An isolation record includes the plant identifier, isolation boundary, procedure reference and planned return date. Related energy-source records distinguish the source identifier, energy type, isolation point and stored-energy controls. This structure helps reviewers understand what the isolation covers and which sources have been considered.

During configuration, agree consistent equipment identifiers and location terminology with operations and maintenance. Ambiguous names make it harder to distinguish similar equipment. Demonstrate a job with several energy sources and review how each relates to the overall boundary. The content of an isolation plan must come from the approved technical process, not be inferred by the software.

Connect procedure revisions with lock accountability

Procedure records include a number, revision, scope, steps and review date. A useful implementation makes the applicable procedure identifiable, so a reviewer can distinguish the instruction used for a job from a later revision. Decide how approved documents are maintained and referenced before importing an existing library.

The lock register captures the associated isolation, lock number, holder, lock box, condition and an accountability note. It supports a clearer account of personal lock control; it is not an instruction to remove a lock. Exceptional removal must remain subject to your organisation’s approved authority and process, regardless of what an administrative status displays.

Record the actual verification evidence

A verification result needs more context than “complete”. The product’s verification record provides fields for the energy source, instrument identifier, calibration date, actual test and observed result, method, reading, unit, acceptance basis and verification time. These details help a reviewer understand what evidence was recorded and how it relates to the source being checked.

Agree which evidence is required for each relevant procedure and who is competent to assess it. The system does not independently validate an instrument, a test method or a reading. A populated field should never be treated as proof that the physical verification was correctly performed.

Make custody transfers and restoration reviews explicit

Longer jobs may extend beyond one person’s period of responsibility. Transfer records identify the outgoing and incoming custodians, lock box, lock accountability and transfer conditions. Review how your shift arrangements will be represented so that ownership is not left implicit when personnel change.

Return-to-service records distinguish personal locks remaining, work-party accountability, restored safeguards, plant condition and the return procedure. These are prompts for an accountable review, not an automated clearance to energise equipment. Demonstrate a job with an unresolved condition and confirm how it remains visible to the person responsible for the restoration decision.

Introduce the system without losing operational context

Before rollout, review the quality of equipment identifiers, approved procedures and the current lock register. Decide how active isolations will be represented at cutover and who checks the migrated information against the governing records. Historical records and live operational controls need a clear distinction.

Ask for a demonstration using a realistic maintenance scenario, including a transfer and a return-to-service review. For deployment within your Microsoft environment, confirm permissions, document access, device suitability and the boundary with permit-to-work or asset systems. Integrations, field connectivity and offline operation should be agreed explicitly; they should not be assumed from the presence of a mobile browser.

Isolation & Lockout questions