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. 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. With the changing landscape of the oil and gas industry, companies are under increasing pressure to improve operational efficiencies as prices continue to remain low and margins are narrowed. In order to reduce costs and increase efficiency, many service supply organizations are implementing API Spec Q2.
Accupoint’s SAM™ solution ensures compliance and the correct documentation to meet the API Q2 requirements. It defines strategies, goals and best practices and the means to secure them. Our system provides industry best practices for all components including: service quality, risk assessment, employee training, document control, MOC, corrective actions and preventive maintenance. A comprehensive solution may seem difficult for an industry with such vast core areas to cover; however, incorporating common standards of practice is essential to realizing integrated process management and operational excellence simultaneously. The bottom line: API Spec Q2 tells your customers that you are at the top of your class and aiming for the best in quality and delivery of services, ultimately ensuring customer loyalty, operational efficiency and growth. Please contact us today for more information on our family of quality management systems specific to the petroleum industry. It has come to our attention that a large number of people in the oil and natural gas industry are struggling with the topic of management of change (MOC). Although the details of implementation will be very different for different situations, great MOC programs are developed from the same basic foundation.
The first fundamental 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. Risk Analysis 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. Implementation of the change First, we will want to execute any per-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. About Accupoint Accupoint Software is a global provider of innovative compliance management systems. Our integrated platforms streamline business processes, increase customer satisfaction and help organizations navigate today’s complex regulatory requirements. Companies relying on the traditional spreadsheet to manage their QMS often find it to be overwhelming to manage as the data volume continues to grow. Those using spreadsheets have to contend with issues like how best to collaborate when working within the same sheet or how to maintain data integrity. Integrated quality management software can be advantageous for organizations that want to save time and improve productivity when managing data.
Barriers with the traditional spreadsheet Traditional spreadsheets can be challenging to keep updated. Different individuals working on the same spreadsheet can lead to versioning issues where it’s difficult to keep track of the most current file. Collaboration within a spreadsheet is also limited. Comments can be hidden or mistakenly overlooked due to the very layout of the spreadsheet. Working within multiple spreadsheets can lead to difficulty when reconciling data. One version may have been edited with the current information, while a team member works concurrently on a different file at the same time, making updates to a different item. It can be challenging to reconcile the two versions. Integrated quality management software makes for a good alternative to the long and often cumbersome spreadsheet. Top advantages of a quality management software solution Millions of companies are utilizing integrated quality management solutions to answer the need for a better way to manage data and information. Both management and team members alike recognize the value in being able to better manage large volumes of data in order to improve their information flow. Adopting Integrated Quality Management Software Accupoint’s quality management solutions can automate your program updates based on parameters set. This means that you don’t have to worry about changing and overhauling your system because the solution evolves as your business needs do.
Cutting costs with accurate real-time data and improved collaboration are the most common reasons for making the switch to an integrated quality management software solution. Better reporting, collaboration, data integrity, and automated program updates become possible with the right solution in place. Excel spreadsheets can serve a purpose for a specified amount of time; when data is limited in volume. As the amount of data grows, management must be prepared to evaluate an integrated quality management system if they are to remain productive. For more information on Accupoint solutions or to schedule a platform demonstration, please call us toll-free 800.563.6250 or visit us at www.accupointsoftware.com |
Categories
All
|