Accupoint Software

  • Home
  • QHSE Software
    • API Spec Q1 QMS Software
    • API Spec Q2 QMS Software
    • ISO 29001 QMS Software
    • ISO QHSE Software
    • Renewable Energy QHSE Software
    • Field Service Software
    • PSM Software
  • QHSE Services
    • Consulting
    • Support Services
    • Mobile App Services
  • Pricing
  • About Us
    • Company
    • Partner Programs
    • Contact Us
  • Resources
    • Blog
    • Videos
    • Client Resources
  • Home
  • QHSE Software
    • API Spec Q1 QMS Software
    • API Spec Q2 QMS Software
    • ISO 29001 QMS Software
    • ISO QHSE Software
    • Renewable Energy QHSE Software
    • Field Service Software
    • PSM Software
  • QHSE Services
    • Consulting
    • Support Services
    • Mobile App Services
  • Pricing
  • About Us
    • Company
    • Partner Programs
    • Contact Us
  • Resources
    • Blog
    • Videos
    • Client Resources

Management of Change : PArt 3

10/16/2019

 
​Last week we continued our discussion on more aspects of a great management of change program. In Part 1 & 2 of our overview, we explored the actions that precipitate making the change. Today, we will discuss the implementation of the change, as well as required follow-up actions.
 
First, we will want to execute any pre-implementation changes and corresponding mitigation efforts that were identified. Subsequent to the implementation we will want to perform any post-implementation tasks that are required.  Example would include updating procedures or modifying training materials to address the change.  
 
Next, we need to confirm the effectiveness of the change.  Once the change has been implemented it is important to make sure that the change does what it was intended to do. Sometimes organizations experience undesirable results. When this happens, we must determine if the system should be restored to the old model, or develop a new MOC to address the unintended results.
 
Finally, we need to follow-up and confirm the success of our mitigation efforts. This ensures that the new system will not produce any unseen difficulties for the organization. Also, we need to verify that the change is going to leave the system running smoothly and safely. Once all of these steps have been completed in their entirety, then the change can be closed.
 
After closure, we still have one final but critical step remaining. We must perform surveillance audits to confirm the changes were carried out consistently and the system is being used as intended. Comprehensive process audits are a great way to determine implementation results.   Randomly selecting a few processes related to the change and auditing them is a good way to achieve this. It is important to remember that audits should be performed at periodic intervals.  The frequency of audits depends on several factors, but should be scheduled in a manner that guarantees the sustainability of the change.
 
For more information on how Accupoint Software can help streamline your MOC program, contact us today.

Management of Change: Part 2

10/9/2019

 
Last week we talked about three crucial aspects of a great Management of Change (MOC) program. Those areas were the specificity and detail in the change requests, followed by risk and reward analysis, and the proper selection of a MOC evaluation team. This week we’re going to touch base on a few more important parts to a fully functional MOC program.
 
The API Spec Q2 requirements take a risk-based approach to quality management. When making changes, risks must be identified and measured by level of acceptability. Risks that are deemed unacceptable must be paired with mitigation plans. These plans are then designated to be carried out before, during, or after the implementation process. The purpose of the mitigation plans is to help bring the risk down to an acceptable level.
 
The next area we will address deals with the approval aspect of MOC. Many organizations get into trouble in this area, confusing the need for approval with the need to inform. It’s important to note that every change doesn’t have to have the same approver. A great MOC program should have an approval matrix describing who needs to approve which type of decisions, as well as a list of people who “must be informed”. If your organization gets these steps right, the approval process will be quick and painless.
 
This leads us to the communication section nicely. As stated before, there are those who need to “approve” and those who “must be informed”. We need to track our communication efforts with respect to the MOC.  In other words, any message and corresponding response must be documented. The person responsible for sending the message is also responsible for getting a confirmation from the recipient. This means after the change is communicated, a receipt confirmation should be requested. Also, it is important to make it clear to your organization that an email response should be expected from the recipient. Simply flagging it as “Request a Read Receipt” isn’t going to get the job done. Once the recipient has responded, stating that they have received the message and understand the information, then the responsibility shifts to them to carry out the appropriate action.
 
Be sure to check back next week for part 3 of our overview of Management of Change. For more information on how Accupoint Software can help streamline your MOC program, contact us today.

Management of Change: Part 1

10/1/2019

 
It has come to our attention that many organizations continue to struggle with the implementation of an effective management of change (MOC) program. To that end, we are presenting a three-part overview outlining the fundamentals of a best in class MOC program. 

The first aspect of MOC is the actual change request. What change needs to be made? What are the individual specs for the materials needed? What plans and documents need to be included in the change request to fully communicate what is needed? If you can’t clearly communicate what it is that needs to be changed, then the change can’t be implemented properly.
 
The next aspect of MOC that needs addressed is the reward of the change. Why am I even making this change? Each change should be fully connected to satisfying a business objective. Again, specificity is important in addressing these concerns. The reward needs to clearly satisfy a business goal. If it does not, why even bother taking the risk?
 
Possibly the most important foundation of the MOC program is the evaluation team. The MOC evaluation team is responsible for the objective evaluation of the requests. Members should represent different areas of expertise throughout the organization, with different experiences under their belt. There shouldn’t be any aspect of a request that the team can’t properly address and evaluate. Team members should be respected among their peers, and confident enough to speak up when they have concerns. If these criteria are used, your organization will select a MOC evaluation team that can handle any challenge put in front of them.
 
Check back next week, for part 2 of our overview on Management of Change.   In the meantime, please contact us for more information on how Accupoint Software can help streamline your MOC program,  today.

    Archives

    December 2022
    November 2022
    October 2022
    September 2022
    August 2022
    June 2022
    May 2022
    April 2022
    March 2022
    February 2022
    January 2022
    December 2021
    November 2021
    October 2021
    August 2021
    July 2021
    May 2021
    April 2021
    March 2021
    February 2021
    January 2021
    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    July 2020
    June 2020
    May 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    October 2019
    September 2019
    August 2019
    July 2019
    June 2019
    May 2019
    March 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    September 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    January 2014
    December 2013
    November 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013


Accupoint Software Links

Oil and Gas QMS SoLUTIONS

  • InterLink  | API Specification Q1 Software
  • SAM | API Specification Q2 Software
  • Acurx | ISO 29001 QMS Software​
  • OpX | Process Safety Management Software

Renewable ENERGY QMS SoLUTION

  • Energia | Renewable Energy QHSE Software

Manufacturing QHSE SoLUTION

  • OpLink | Integrated ISO QMS Software

Workflow Management SOLUTIONS​

  • UpStream | Field Service Management Software
  • MPX | Mobile Application Development
Vertical Divider
About Us
​Accupoint Software is a global provider of innovative software solutions to the oil and energy industry.  Our integrated compliance software expands operational awareness, improves efficiency and manages complex regulatory and customer requirements.

Contact Us
API Spec Q1 and API Spec Q2 Quality Management Software
Sales, Technical Inquiries and Customer Support:
| 800.563.6250
​| websupport@accupointsoftware.net
Oil & Gas Software, Consulting, Training and Documentation​

Copyright © 2023.  Accupoint Software.  API Spec Q1, API Spec Q2, ISO 9001 and ISO 29001 Quality Management Software for the Oil and Energy Industry.