Acronyms Are Hard MOC

Acronyms can be hard to figure out. If you want proof, look no further than our Acronyms Are Hard Series! When jumping in between a few different industries, these seemingly harmless terms can lead to confusion, mass hysteria, or worse potential problems with the end result.

Management of Change

Stems from the OSHA 1910.119 standard, Process Safety Management of Highly Hazardous Chemicals. You can read the whole thing here. Generally the standard requires an “organized and efficient” process for documenting changes.

Why do we need to document these changes? Mostly to have written proof a what, when, and why something was changed in case of an accident. Remember this is specifically for highly hazardous chemicals, we should all feel a little bit more safe with these regulations in place.

Performing MOC can include the following reasons (Government documentation typically doesn’t limit themselves to additional reasons)

  • Process Chemicals
  • Technology
  • Equipment
  • Procedures
  • Number of employees working on the process.

When performing an MOC be sure to include

  • The technical basis for the proposed change
  • The impact of change on safety and health
  • Modifications to operating procedures
  • Necessary time period for the change
  • Authorization requirements for the proposed change

Where to find MOC’s?

Want to know more? Heck yeah! Corso actually has a fair amount of experience with both using, creating, and implementing MOC’s.

Much of what we’ve experienced has been based on the application and the time in which an MOC was instituted. For example, many customers who are currently in an upgrade cycle are looking to integrate their new MOC within their existing systems. Ignition is a fantastic platform for this and there are fully functioning MOC’s built on Ignition. As a side note, because of the flexibility of Ignition, we can build just about anything, including LIMS applications.

Outside of Ignition, there are many custom built application, such as .NET applications. Those .NET applications can either be stand alone, or you can work on integrating them with the Rockwell Factory Talk suite.

There are always stand alone software solutions. These solutions offer everything that you’ll (in theory) need to use standard best practices for MOC.

It is with mild trepidation that we tell you that performing MOC with paper and a pencil will still (probably) keep you in compliance. You will lose all the benefits of having the information digitally and being able to re-confirm the process and easily find the past changes to compare against production and project future results.

What are you using your MOC to do?

That’s a question, let us know what you’re doing with you MOC, how it’s been developed, if you like it. All the important things.

If you’re interested in adding MOC and/or having Corso help put together a solution for you, please reach out and let us know!