MoC Overview

Table of Contents

• Introduction – what it does
• Stages to Implementation
• MoC Process Overview
• Low Risk MoC Overview
• Full Risk Overview

Baytouch’s PSMmonitor Management of Change (MoC) application supports a formalized yet flexible process for managing change in high hazard chemical manufacturing and handling facilities that works!

It is an integrated risk assessment and management program to accompany plant installations or changes, including software and personnel, and has a high level of configurability which enables it to fit many PSM circumstances and plants and manufacturingoperations of all sizes.

MoC benefits include:

• Enforces strict adherence to predefined MoC processes with appropriate risk assessments, notifications to relevant parties and sign-offs.
• Approvals and next stage sign-offs are notified electronically thereby ensuring rapid but assured progress for an MoC.
• Electronic sign-offs make it is easy to see the progress of MoCs that the user is participating in and anticipate and remove any stalled stages, e.g. tardy responses to authority sign-off requests, employee unavailability, etc., which will result in speedier change and reduced cost implementations.
• Integration with the PSMmonitor’s Action Tracking module makes Actions from MoCs – Pre- and Post- Startup Safety Reviews (PSSRs) – easy for the individual to manage and account for and the 2-way linkage means that within an MoC, the Action item status can be seen at a glance.
• Attachments can be added throughout the MoC process including Microsoft Office, text-based PDFs and P&IDs along with manual sign off sheets.
• MoC text is searchable throughout as well as the attachment content in Microsoft Office documents and Adobe text PDFs.

Mobile devices such as smartphones and tablets are supported for certain tasks such as reviewing MoC content and signing off.

Information required to implement the MoC module, assuming PSMmonitor has already been set up with users and supervisors for the core Action Tracking module, will include:

1. Personnel groups based upon unique role names – e.g. PSM Managers, EHS Managers, Product Managers, Process Engineer, Maintenance Managers, Environmental Engineers are examples which will be configured during the setting up process This makes it easy to select people within functions to process MoCs.

2. Link Units to PHA reference numbers

3. Onscreen tab titles, section subtitles within tabs, risk assessment questions for the sections and PSSRs, which in turn can link to Actions created if answered “yes”.

4. The Approvals and Sign-off levels will need to be mapped into the MoC process, which will be based on any existing workflow process.

5. Risk level question strategy which determines which questions trigger the risk levels that govern whether an MoC is subject to a Low Risk or Full process.

6. Subject and email bodies for various email communications such as daily temporary MoC initial reminders, daily reminders, past due date and secondary reminders.

Even though Baytouch has been through this procedure many times in the past, each site’s implementation will take time to configure by applying the foregoing information but it does mean that it can be easily changed at a later stage if changes are made to the process.

It is less costly and less risky to implement than resorting to bespoke coding and more flexible when adapting to changing business requirements.

Whilst in the PSMmonitor MoC tab, select Create MoC in the lower of the top left hand MoC menu. You are then presented with a risk matrix which determines Risk Level and whether you should be undertaking a Low Risk or Full MoC.

The questions and the matrix behind them determining the Risk Level is set up at implementation time and is configurable so it can be changed to suit business requirements.

In the demo system used for the example screenshots, a Risk Level 0 or 1 will trigger a Low Risk MoC (on a scale of 0 to 4).

In the screenshot below, Create –> MoC brings up the pre-configured initial Risk Assessment form.

If the Risk Level has resulted in a 0 or 1, a Low Risk MoC form is created, as below:

The various stages’ Approvals and Sign-offs are then followed according to the MoC Low Risk process as configured.

If in the initial risk assessment, the Risk Level equals or exceeds the defined threshold for a Full MoC, a form similar to the initial Low Risk MoC opens up, as below. The difference with Low Risk at this stage is that there is no Risk Assessment (Section 5) or MoC Requirements (PSSR – Section 9) as in the Lower half screenshot above until later in the processes when various approvals and sign-offs have been enacted.

Once the initial MoC request has been approved, its moved on to its successive stages as defined in MoC operational processes:

Below are screenshots illustrating a selection of tabs that define the process and risk assessments through configuration which demonstrates how flexible and configurable MoC is.

Related Topics:

• MoC Approval Process