QSP-09 MANAGEMENT OF CHANGE

Date of Issue: 30/05/2014 QSP / 09 Rev 0 Date of Print: 18/06/2014 30/05/2014

Page 1 of 4

Q.S.P-09

MANAGEMENT OF CHANGE

Rev Issued To Title Date Signed By

0 Management Team 30/05/14

DATE SECTIONS REVIEWED PREPARED APPROVED BY

30/05/14 First Issue

QSP-09 MANAGEMENT OF CHANGE

Date of Issue: 30/05/2014 QSP / 09 Rev 0 Date of Print: 18/06/2014 30/05/2014

Page 2 of 4

Procedure No. QSP - 09 MANAGEMENT OF CHANGE

1. PURPOSE AND SCOPE

This procedure defines the controls and processes for defining, assessing, approving and implementing changeswhichmayaffect######QualityManagementSystem.ThisensurestheintegrityoftheQualityManagementSystemismaintainedwhenchangesareplannedandimplemented.

2.REFERENCES MOC/01ChangeRegister

MOC/02RequestforChange(RFC)Form

3.DEFINITIONS ChangeTheaddition,modificationorremovalofapprovedand/orsupportedresources,proceduresand/orinfrastructureRequestforChange(RFC)FormAformusedtorecorddetailsofarequestforachangetoanywithinaninfrastructureortoproceduresanditemsassociatedwiththeinfrastructure.ChangeRegisterAregisterofinformationthatrecordsinformationrelatedtospecificchanges,iewhatwasdone,whenitwasdone,bywhomandwhy.

4.PROCEDURE

4.1GENERAL

TheprocedureforManagementofchangeiscarriedoutinthefollowingorder: Initiation

o Identifyandauthorise(orreject)thechange Review Assesstherisksandpotentialimpacts Gainrequiredapprovals Implementation

o Planningo Communicationo Training

Followup/Review/Closeout

TheManagementofChangeProcedure is implementedwhenever the followingchangesareinconsideration:

ChangesintheOrganisationalstructure Changestokeyoressentialpersonnel.(Managers,machinists,welders) Changestocriticalsupplierswhichmayimpactonquality ChangestotheQualityManagementProcedures,includingchangesresultingfrom

CorrectiveandPreventiveactions.

Documentation related toManagementofChange shallbemaintained asperQSP/04

QSP-09 MANAGEMENT OF CHANGE

Date of Issue: 30/05/2014 QSP / 09 Rev 0 Date of Print: 18/06/2014 30/05/2014

Page 3 of 4

4.2INITIATIONANDREVIEW

4.2REVIEW

DocumentControlandRecordsManagement.

Changestocontractsand/orqualityplanswhichoccurafterthetaskhascommencedaredealtwithasperQSP/01sections4.7&4.8

Changes coming under the operational control of ###### may arise from any of thefollowingareas:

Employeerecommendation Customerrequirementorrecommendation ConnectionLicenseerequirementorrecommendation Changestoindustrystandardsand/orspecifications Businessrequirement Correctiveand/orPreventiveActions

TheManagementTeamareresponsibleforreviewingtheproposedchangesandensuringthe Management of Change procedure is adhered to. Ultimate responsibility forauthorisationlieswiththeGeneralmanager.

Ordinarily, requests for changes are reviewed and assessed at the scheduled GeneralManagement Meetings, which are held usually every five to six weeks. However, if aproposed change is required urgently a "SpecialMeeting"may be held to review andassess the change. Minutes and resulting action items of such a meeting shall bedocumentedandmaintainedasperQSP/04DocumentControlandRecordsManagement.

Ifrejected, thepersonwhorecommended thechangeshallbe informedof therejectionand the reasoning behind it. If authorised, the proposed change is initiated throughMOC/02RequestForChangeForm.

EachRFCformisassignedasequentialnumber,andaregisterismaintainedbytheQualityManager of all RFC's and associated data. (Refer toMOC/01 Management of ChangeRegister.TheRFCformalsoallowsforrelateddocumentationasthechangeisprocessed.InitialinformationontheRFCshouldincludethefollowing:

Thereason/businessjustificationforthechange Why the change is needed in particular giving detailed information on

implicationsofnotimplementingthechangei.e.securityrisksetc. Knownrisksorimpacttothebusinessofimplementingthechange Anestimationofrequiredresourcesincludingpeople,timeandinvestment/costs

Responsibility isassigned toan individual to"own" thechange.Thispersonshouldhaveexperienceintheparticularnatureofthechange.The"owner"shallensurethechangeisprogressed,utilizingtheskillsandknowledgeoftherestoftheManagementTeam.

ReviewtheRFCforcontentdetailandidentify: Anyadditionalinformationand/orapprovalsthatmaybenecessarytoprocessthe

request. Documentationchangesthatwillberequired Additionaltrainingthatwillberequired Whoisinvolved.(Employees,customers,connectionlicensors,etc) Costsinvolved Risksinvolved Necessaryresourcestoimplement

If required,discuss thechangeswithappropriategoverningbodies,connection licensorsandcustomers.

Apreliminarytimeframeforthecompletionofimplementationshouldbedecideduponatthisstageoftheprocess.

QSP-09 MANAGEMENT OF CHANGE

Date of Issue: 30/05/2014 QSP / 09 Rev 0 Date of Print: 18/06/2014 30/05/2014

Page 4 of 4

4.3RISKASSESSMENT

4.4APPROVALS

4.5IMPLEMENTATION

4.6CLOSEOUT

HighlightsofthereviewshallbedocumentedandmaintainedwiththeRFC.

Changesshallbeevaluatedandmanaged toensurerisksarising fromchangesremainatacceptablelevels.considerationshouldalsobegiventotheriskandimpacttothebusinessofnotimplementingthechange.Risk assessment for the change shall be carried out as per QSP/08 Risk Assessment,ManagementandContingencyPlanning.

Whererequiredbycontract,customersand/orconnection licenseesshallbe informedofneworresidualriskwhichareduetothechanges.

ResultsofriskassessmentshallbemaintainedwiththeRFC.

External:Allrelevantstakeholdersandassociatedgoverningbodiesshouldbeapproachedfor the necessary approvals. Time frames related to approvals may necessitate theadjustmentof the completiondate.Evidenceofapprovals shallbemaintainedwith theRFC.

Internal: The General manager is ultimately responsible for internal approval of anychangesassociatedwithManagementofChange.

Implementation of the change shall be planned by the Management Team, either atGeneral Management meetings, or at "Special Meetings" scheduled for this specificpurpose. Informal meetings may take place to discuss individual issues. Minutes andresulting action items of such meetings and/or discussions shall be documented andmaintainedwiththeRFC.An implementationplanshallbedevelopedtoprovideguidancetoallManagement.Theimplementationplanshallinclude,butisnotlimitedto:

Communicationdetailsforemployees Customernotificationwhenrequiredbycontract ConnectionLicensornotificationwhenrequiredbycontract Trainingdetails Documentchangedetails Necessaryresources Responsibilitiesassignedforeachoftheabove

Note:Customernotificationshouldincludenotonlythechangeitself,butalsoanyneworresidualriskduetothechange.

Theimplementationplanshallbereviewedonaregularbasis.ThereviewsmaytakeplaceatGeneralManagementMeetingsor "SpecialMeetings" scheduled for such apurpose.ResultsshallbedocumentedandmaintainedwiththeRFC.

When the implementation plan has been completed, a final reviewmeeting shall takeplacetoensureallaspectsoftheManagementofChangehavebeenadheredto.WhentheManagementTeam is satisfied the changehasbeen implemented correctly theGeneralManager has the authorisation to declare the change complete and close it out. TheclosureisnotedontheRFCandsignedoffbytheManagerspresent.

Ongoingmonitoring of related processes or activities should take place to identify anyadverse side effects which may not have been identified during the Management ofChange process. If found, these should be reported to the Management Team forcorrection.

AllrecordsrelatedtoManagementofChangeshouldbeanalysedasperQSP/05,(SystemMonitoringandImprovement), and theresultstabledatManagementReviewMeetingsfordiscussion.