變更管理程序

1、Procedure / 程序File No. SH-ESHQ-3.10Procedure for Management of Change變更管理Evonik Sanzheng(Yingkou) Fine Chemical Co.,LtdRevision00First ReleasePage10 of 10Procedure for Management of Change變更管理程序Rev.Published byReviewed byApproved byAmendatory RemarksDateThe latest changes were marked in light blue i

2、n the contents.Signed copy archived by document controller 目錄Table of Contents1. 目的Objective 32. 范圍Scope 33. 定義Definitions 34. 責(zé)任Responsibility 45. 程序Procedure 55.1 變更申請Request for change 55.2 可行性和風(fēng)險(xiǎn)評估Operability & risk assessment 55.3 變更批準(zhǔn)Approval of change 65.4 運(yùn)行投用前審核Pre-startup review 65.5 批

3、準(zhǔn)運(yùn)行Approval of startup 75.6 告知/溝通Notification/Communication 75.7 信息更新&文件保存Information update & documentation 75.8 特殊變更Special MOCs 75.9 培訓(xùn)和審核Training & audit 96. 附件Attachment 9附件1：基于風(fēng)險(xiǎn)的變更分級與授權(quán)矩陣Attachment 1: Risk based change classification and authorization matrix 10附件2：變更申請表Attachment

4、2: <Request for Change Form> 11附件 3： 變更管理流程圖Attachment 3: MOC Flowchart 121. 目的1. Objective建立本程序的目的是管理和控制可能影響到安全、健康和環(huán)境的有關(guān)設(shè)備、設(shè)施、程序以及組織機(jī)構(gòu)的變更，并將變更帶來的風(fēng)險(xiǎn)最小化。This procedure is established for managing and controlling changes made to equipment, facilities, procedures and organizational structure is e

5、ssential to the safety, health and environment at facilities to minimize risks associated with those changes. 2. 范圍2. Scope本程序適用于贏創(chuàng)三征（營口）精細(xì)化工有限公司。This Procedure is applicable to the Evonik Sanzheng(Yingkou) Fine Chemical Co.,Ltd3. 定義3 Definition變更：指任何在工藝或設(shè)施上發(fā)生的與已有規(guī)范或?qū)嶋H的偏離，包括增加，減少，修改和替換（同類替換除外）。變更的對象

6、可以是工藝技術(shù)、控制系統(tǒng)、設(shè)備設(shè)施、人員組織以及程序規(guī)定。Change is considered a deviation from the specifications or practices as specified for the process or facility which may include addition, deletion, alteration, or replacement (except for replacement-in-kind). The changing objects may include process/technology, controll

7、ing system, equipment/facility, personnel/organization and procedure.同類替換：指不超出既定設(shè)計(jì)規(guī)格/控制范圍的有關(guān)設(shè)備或程序的變化。包括以相同或等同的設(shè)備及零件進(jìn)行替換，以及在系統(tǒng)試運(yùn)轉(zhuǎn)或測試時(shí)進(jìn)行的在操作規(guī)程規(guī)定范圍內(nèi)的修改等。同類替換不在變更管理程序的控制范圍內(nèi)。Replacement-in-kind (RIK) is the equipment and procedural alteration that do not vary from the documented design specifications whi

8、ch include identical equipment and spare parts replacement, and modification for completing trials or tests of equipment within the defined operating procedures. RIK is not subject to MOC procedures.變更分類（基于風(fēng)險(xiǎn)的分類）：按照變更所對應(yīng)的風(fēng)險(xiǎn)等級的高低，可將變更分為較小變更、中等變更和重大變更。具體的劃分標(biāo)準(zhǔn)參見附件1。Classification of Change (Risk basis)

9、: Based on the different levels of risk, the changes can be divided into the Minor Change, Moderate Change and Major Change. Refer the criteria of classification to Attachment1. 臨時(shí)變更：指預(yù)先設(shè)定的只將短期（6個(gè)月內(nèi)）存在的變更。Temporary Change is a change that is intended to exist for a short, predetermined, finite perio

10、d (within 6 months).緊急變更：當(dāng)執(zhí)行常規(guī)變更管理程序可能導(dǎo)致不可接受的安全風(fēng)險(xiǎn)，環(huán)境或安保事故或嚴(yán)重經(jīng)濟(jì)損失的變更。Emergency Change is a change needed in a situation where the time required for following the normal MOC procedure could result in an unacceptable safety hazard, a significant environmental or security incident, or an extreme economi

11、c loss.變更管理協(xié)調(diào)人:負(fù)責(zé)所在區(qū)域內(nèi)變更管理相關(guān)事宜執(zhí)行的協(xié)調(diào)人員，他將負(fù)責(zé)確保實(shí)際變更管理執(zhí)行與程序的符合性和完整性。Management of Change (MOC) Coordinator is a person to coordinate activities associated with the MOC within the responsible area and ensure compliance and integrity with the MOC procedure through its implementation.變更申請人：最初提出變更需求的人，他將提出書

12、面的申請并提供相關(guān)信息和資料。Change Originator is a person who raises the idea for a change initially and submits the written request for change and provides related information & documentation.變更審核人：對申請的變更進(jìn)行可行性和風(fēng)險(xiǎn)評估的人員（或小組），并且在必要的情況下提供變更實(shí)施所需要的整改措施。Change Reviewer is a person (or a team) who reviews the propo

13、sed change by evaluating the operability and risk and also provides relevant amendment required for change Implementation if necessary.變更批準(zhǔn)人：指批準(zhǔn)變更實(shí)施以及系統(tǒng)運(yùn)行的人，將由對應(yīng)不同風(fēng)險(xiǎn)等級的變更分類（依據(jù)附件1劃分）決定批準(zhǔn)人的角色，如： 較小變更區(qū)域主管 中等變更工廠/部門經(jīng)理 重大變更生產(chǎn)/部門主任變更批準(zhǔn)人與變更審核人通常情況下由不同的人員擔(dān)任。Change Authorizer is a person who gives the approv

14、al of implementing the change and startup, fulfilled with the role that depends on different level of changes (according to attachment 1), for example, Minor Change Area Supervisor Moderate Change Plant/Dept. Manager Major Change Production/Dept. DirectorNormally Authorizer and Reviewer are taken by

15、 different people.4. 責(zé)任4. Responsibility變更管理協(xié)調(diào)人MOC Coordinator 負(fù)責(zé)組織協(xié)調(diào)變更管理流程的執(zhí)行 確保落實(shí)相關(guān)變更管理程序要求 保存并維護(hù)負(fù)責(zé)區(qū)域內(nèi)所有變更管理的相關(guān)文件和記錄 Responsible for coordinating the MOC process related fairs within the plant. Ensure the requirements of MOC procedure have been fulfilled. Keep and maintain all documentation and re

16、cord associated with MOC in his/her responsible area. 變更申請人Change Originator 提出變更的書面申請，明確變更的初始信息，如變更范圍、對象和類型等，并且提供變更相關(guān)的支持文件和資料 判斷變更的分類 確保變更執(zhí)行后，及時(shí)更新關(guān)聯(lián)的信息和文檔 確保將已更新的相關(guān)信息及時(shí)傳達(dá)給所有涉及的部門和人員 Raise the written request for change and clearly define the initial information e.g. scope, object and classification

17、 of the change etc. and also provide supporting documents and data associated with the change. Classify the change. Ensure timely update change related information and documents after change implementation. Ensure the updated information is timely communicated to all department and personnel involve

18、d.變更審核人Change Reviewer 確保變更的可行性和風(fēng)險(xiǎn)已得到適當(dāng)評估，并且已制定了相關(guān)應(yīng)對和控制措施 跟蹤并確認(rèn)所有既定措施已落實(shí)到位 Ensure that operability and risk of the change have been properly evaluated and relevant control measures have been established. Follow up and verify all written control measures have been carried out.變更批準(zhǔn)人Change Authorizer 基

19、于評估的結(jié)果，最終決定是否批準(zhǔn)變更的實(shí)施 批準(zhǔn)已變更系統(tǒng)的投入運(yùn)行 Decide to final approve the implementation of the change based on the outcome of assessment. Approve the changed system to be running.區(qū)域負(fù)責(zé)人Area Responsible 確保在所轄范圍內(nèi)遵照變更管理程序執(zhí)行 確保參與變更管理的人員經(jīng)過適當(dāng)?shù)呐嘤?xùn) Ensure compliance with MOC procedure within the responsible area. Ensure

20、 proper trained and qualified people fulfill the roles in MOC.EHSQ部門EHSQ Department 負(fù)責(zé)參與變更相關(guān)ESH風(fēng)險(xiǎn)評估和審核 負(fù)責(zé)維護(hù)、更新及發(fā)布變更管理程序 提供變更管理程序的相關(guān)培訓(xùn) 組織對變更管理程序執(zhí)行情況的審計(jì) Participate in MOC related ESH risk assessment and review. Maintain, update and release the MOC procedure. Provide MOC procedure related training. Ar

21、range the audit for implementation of MOC. 5. 程序5. Procedure5.1 變更申請5.1 Request for Change 變更申請人首先應(yīng)判斷是否屬于變更管理程序的控制范疇，如果屬于同類替換的，則無需按照變更管理程序執(zhí)行。 The change originator shall first make the judgment of whether the applied procedure belong to the scope of MOC, if it is a RIK, MOC procedure will not be fol

22、lowed. 變更申請人應(yīng)清楚寫明變更初始內(nèi)容，至少包括變更理由、預(yù)期結(jié)果、相關(guān)技術(shù)設(shè)計(jì)以及工作范圍，并且還應(yīng)提供相關(guān)文件、資料和圖表等輔助信息。 The change originator shall clearly define the initial information of the change, which shall at least include reason of change, desired results, technical design and work scope, and all supporting documents, data and diagram

23、shall be provided as well. 變更申請人應(yīng)識別變更的類型，附件1中的基于風(fēng)險(xiǎn)的變更分類指南將作為依據(jù)。當(dāng)對變更分類存在疑問時(shí)，可就具體情況咨詢風(fēng)險(xiǎn)評估組/審核人確定。 The change originator shall identify the classification of the change with taking the <Risk Based Change Classification Guideline> in Attachment 1, and the risk assessment team/change reviewer could

24、 be consulted for identification if in doubt. 變更申請人將填寫變更申請表（參見附件2），將填好的表格遞交給相關(guān)變更管理協(xié)調(diào)人。 The change originator will submit the <Request for Change Form> (see attachment 2) to the area MOC coordinator.5.2 可行性和風(fēng)險(xiǎn)評估5.2 Operability & Risk Assessment 變更協(xié)調(diào)人將基于變更的對象和規(guī)模，組建一個(gè)合適的變更可行性和風(fēng)險(xiǎn)評估小組。變更小組的成員可能

25、包括：· 項(xiàng)目負(fù)責(zé)人· 工藝工程師· 設(shè)備工程師· 維修工程師· 化學(xué)工程師· 操作人員· ESH專家· 供應(yīng)商和外部專家等 The MOC coordinator shall establish a proper MOC team based on the object and size of the change. The MOC team may include:· Project responsible· Plant operator· Process engineer

26、3; Equipment engineer· Maintenance engineer· Chemist · ESH specialist· Supplier and external expert etc. 變更小組將根據(jù)變更申請表中提供的初始信息和支持文件，采取適當(dāng)?shù)墓ぞ?方法實(shí)施ESH風(fēng)險(xiǎn)評估，可以包括：檢查表、HAZOP、What-if等，評估的結(jié)果將被記錄下來并與變更申請表關(guān)聯(lián)。 The MOC team shall select an appropriate tool/method to conduct the ESH risk assess

27、ment based on the initial information and supporting documents obtained from the request for change form, which may include: check list, HAZOP, What-if etc. And the results of the evaluation will be recorded and attached to the request form. 變更審核人將對評估結(jié)果作總的簽字確認(rèn)。 The change reviewer shall sign to conf

28、irm the assessment results.5.3 變更批準(zhǔn)5.3 Approval of Change 變更批準(zhǔn)人將根據(jù)審核人對變更相關(guān)可行性和風(fēng)險(xiǎn)評估的結(jié)果，決定是否批準(zhǔn)變更的實(shí)施，并在變更申請表中簽字確認(rèn)；如不批準(zhǔn)變更，則需要在表格中記錄原因。 The change authorizer shall decide whether approve the change into implementation or not according to the operability and risk assessment by the reviewers and sign on th

29、e form of <Request for change form> if not approved, relevant reasons shall be recorded on the form. 在變更系統(tǒng)投入運(yùn)行前，變更批準(zhǔn)人將基于現(xiàn)場條件以及控制措施落實(shí)情況，決定是否批準(zhǔn)變更系統(tǒng)投入運(yùn)行，并在變更申請表中簽字確認(rèn)；如不批準(zhǔn)變更，則需要在表格中記錄原因。 The change authorizer shall decide whether approve the change into implementation or not according to the opera

30、bility and risk assessment by the reviewers and sign on the form of <Request for change form> if not approved, relevant reasons shall be recorded on the form.5.4 運(yùn)行/投用前審核5.4 Pre-startup review 在變更系統(tǒng)投入運(yùn)行前，變更協(xié)調(diào)人將組織相關(guān)人員對系統(tǒng)進(jìn)行ESH審核，以確保：· 變更已經(jīng)按照描述安裝· 沒有其他的額外變更· 標(biāo)準(zhǔn)操作規(guī)程已被更新/歸檔/溝通傳達(dá)·

31、; 已完成對運(yùn)行和維護(hù)人員的相關(guān)培訓(xùn)· 已將在風(fēng)險(xiǎn)評估中識別出的所有安全控制措施落實(shí)到位· 已完成開車計(jì)劃方案· 已建立應(yīng)急響應(yīng)預(yù)案并明確了聯(lián)系人名單· 已維護(hù)存在問題/解決方法的記錄并與審查表關(guān)聯(lián) Prior to startup of the changed system, an ESH review shall be carried out by the change coordinator to ensure:· Modification is installed as described.· No other changes

32、 were made.· SOPs have been updated / documented / communicated.· Operation and maintenance training for staff have been completed. · All safety control measures identified in the risk assessment of the change have been carried out.· Startup plan has been completed.· Emergen

33、cy response plan has been established with contact list included.· Notes of issues/solutions have been maintained and attached to the review form. 變更審核人將對關(guān)鍵項(xiàng)的完成進(jìn)行簽字確認(rèn)。 The Change Reviewer shall sign on the completion of key items to ensure they have been finished. 對于新建項(xiàng)目或較為復(fù)雜或高風(fēng)險(xiǎn)的系統(tǒng)，在實(shí)施變更后試運(yùn)行開始

34、之前還應(yīng)組織進(jìn)行開車前安全審查（PSSR），具體內(nèi)容參見開車前安全審查程序。 For the new project or complex or high risk system, implementation of change and before commissioning of the system, A Pre-Startup Safety Review (PSSR) shall also be conducted, refer details to <procedure for PSSR>.5.5 批準(zhǔn)運(yùn)行5.5 Approval of Start-up 在變更系統(tǒng)投入

35、運(yùn)行前，變更批準(zhǔn)人將基于現(xiàn)場條件以及控制措施落實(shí)情況，決定是否批準(zhǔn)變更系統(tǒng)投入運(yùn)行，并在變更申請表中簽字確認(rèn)；如果不批準(zhǔn)變更，則需要在表格中記錄原因。 The change authorizer shall decide whether approve the change into implementation or not according to the operability and risk assessment by the reviewers and sign on the form of <Request for change-2> if not approved,

36、 relevant reasons shall be recorded on the form.5.6告知/溝通5.6 Notification/Communication 在變更實(shí)施前，區(qū)域變更管理協(xié)調(diào)人應(yīng)確保及時(shí)告知所有可能受到變更影響的人員。并在必要時(shí)，向相關(guān)人員提供防范措施。 Prior to the implementation of the change, the area MOC coordinator shall notify all personnel who could be impacted by the change in time. Corresponding cou

37、ntermeasures and precautions will be given to those people if necessary.5.7 信息更新&文件保存5.7 Information update & Documentation 任何已變更的內(nèi)容都應(yīng)及時(shí)在相關(guān)系統(tǒng)、程序和/或文件中更新。 Any changed contents shall be timely updated in all related system, procedure and/or documents. 各區(qū)域?qū)⒈４嫠蠱OC的完整文件，一份變更管理的完整文件包括：變更申請表、會(huì)議紀(jì)要、

38、風(fēng)險(xiǎn)評估記錄、檢查清單、簽到表、培訓(xùn)記錄、相關(guān)支持文件圖表等。區(qū)域中的變更協(xié)調(diào)員將負(fù)責(zé)MOC文件的歸檔保存。 Each area shall keep the total files package of allMOCs which shall include: request of change forms, meeting notes, risk assessment records, checklists, attendance sheets, training information and supporting documents & drawings etc. The MO

39、C coordinator of the area shall be responsible for the documentation of MOC files. 5.8特殊變更5.8 Special MOCs臨時(shí)變更Temporary MOC 變更存在期限小于6個(gè)月的變更即屬于臨時(shí)變更。 The change with the existing period of less than 6 months is considered to be a temporary change. 變更申請人應(yīng)在變更申請表中注明是否屬于臨時(shí)變更以及變更預(yù)計(jì)恢復(fù)的日期。 The change originat

40、or shall mark in <Request for Change form> if it belongs to temporary change and also define the expected restore date. 臨時(shí)變更與永久變更的在管理流程是一致的，但是臨時(shí)變更關(guān)注變更帶來的短期風(fēng)險(xiǎn)。 The temporary change will be following the same procedure as the permanent one, but more focused on the short-period risk caused by the

41、 change. 當(dāng)臨時(shí)變更存在時(shí)間即將超過6個(gè)月時(shí)，應(yīng)執(zhí)行下列操作中的一種：· 基于臨時(shí)變更中的數(shù)據(jù)和信息提出一個(gè)新的永久變更申請并審核；· 將臨時(shí)變更的系統(tǒng)復(fù)原；· 在經(jīng)過進(jìn)一步審核后延長臨時(shí)變更的期限。 After a short-term implementation period, one of the following must occur: · A new permanent MOC must be initiated for review using data from the temporary change as justifica

42、tion;· The system must be returned to its original condition;· The temporary change can be extended, with further review.較小變更Minor MOC 當(dāng)判斷變更類型屬于較小變更時(shí)，可執(zhí)行快速變更流程，即在變更申請表執(zhí)行過程中直接從附件2的部分B跳轉(zhuǎn)至部分E，經(jīng)過最終批準(zhǔn)后直接實(shí)施變更。 If the change has been identified as Minor Change, the quick MOC process can be activa

43、ted, which means the <Request for Change Form> process in Attachment 2 can be jumped from part B to part E, and the change is able to implement after the final approval obtained. 緊急變更Emergency MOC 緊急變更只適用于延遲變更可能導(dǎo)致對人員安全、環(huán)境、工廠設(shè)備以及產(chǎn)品造成嚴(yán)重影響的情況。不適用于正常運(yùn)行時(shí)期。 Emergency MOC are only to be used when del

44、aying a change could result in adverse impacts on the safety of persons, the environment, plant systems, equipment, and productivity issues. This not to be used during normal business hours. 一旦確定為緊急變更，變更申請人將執(zhí)行“快速變更流程”見附件2的表E部分，并在得到所在區(qū)域負(fù)責(zé)人或其授權(quán)人員批準(zhǔn)后執(zhí)行變更。 Once the emergency change has been identified,

45、the change originator will go through the Quick MOC process refer to the part E of attachment 2 and the change shall be approved by the area responsible or delegate for implementation. 變更管理協(xié)調(diào)人應(yīng)協(xié)助確保在緊急變更批準(zhǔn)實(shí)施后的第二個(gè)工作日重新開始進(jìn)行完整的變更管理流程（包括正式的風(fēng)險(xiǎn)評估）。 The MOC Coordinator will assist to insure the complete MOC process (former risk assessment included) is followed the next working day of emergency change approved to be carried out. 每個(gè)區(qū)域都應(yīng)定義出當(dāng)區(qū)