Light
Dark
System
Log In
Loading...
Compare / EASA/
Incorporated Amendments
/
Compare & Highlight Differences
AMC1 ATM/ANS.OR.B.010(a) Change management procedures
Available versions for ERULES-1963177438-3221
ED Decision 2017/001/R
found in: ATM/ANS Provision of Services (2017/373) (Mar 2025)
From
ATM/ANS Provision ... (Mar 2025)
ATM/ANS Provision ... (Feb 2023)
From section
To
ATM/ANS Provision ... (Mar 2025)
ATM/ANS Provision ... (Feb 2023)
To section
No visible text changes
0 removals
0 additions
View
Rich
Plain
Sync scrolling
Share
From
Show details
Hide details
To
Show details
Hide details
Version
Show side by side
AMC1 ATM/ANS.OR.B.010(a) Change management procedures ED Decision 2017/001/R GENERAL (a) The procedures, and the change of the procedures, used by a service provider to manage changes should cover the complete lifecycle of a change. (b) The service provider should show that the procedures address all the actions and all the evidence needed in order to comply with the requirements laid down in [ATM/ANS.OR.A.045](#_DxCrossRefBm647742061), [ATS.OR.205](#_DxCrossRefBm647742066), [ATS.OR.210](#_DxCrossRefBm647742092), and [ATM/ANS.OR.C.005](#_DxCrossRefBm647742065), as appropriate. For that purpose, the service provider should use a compliance matrix, which shows: (1) which part of a procedure addresses which part of the Regulation (i.e. the requirement of the implementing rule); and (2) the rationale explaining how the procedures demonstrate compliance with the Regulation. (c) The service provider should ensure that the roles and responsibilities for the change management processes are identified in the procedures. (d) Procedures should be submitted in a manner agreed between the service provider and the competent authority. Until an agreement is reached, the competent authority will prescribe the means of submission. (e) The procedure that defines the notification process for changes includes: (1) the point of contact in charge of the notification of changes, e.g. person, or part of the organisation and the role; (2) the means used for notification, e.g. fax, email, mail, use of database or others. (f) The management of change procedures should include a change identification procedure. This procedure, which is a precursor of the change notification process, should seek out potential changes, confirm that there is a real intent to implement them (propose the change) and, if so, initiate the notification process.
AMC1 ATM/ANS.OR.B.010(a) Change management procedures ED Decision 2017/001/R GENERAL (a) The procedures, and the change of the procedures, used by a service provider to manage changes should cover the complete lifecycle of a change. (b) The service provider should show that the procedures address all the actions and all the evidence needed in order to comply with the requirements laid down in [ATM/ANS.OR.A.045](#_DxCrossRefBm1726554913), [ATS.OR.205](#_DxCrossRefBm1726554911), [ATS.OR.210](#_DxCrossRefBm1726554937), and [ATM/ANS.OR.C.005](#_DxCrossRefBm1726554910), as appropriate. For that purpose, the service provider should use a compliance matrix, which shows: (1) which part of a procedure addresses which part of the Regulation (i.e. the requirement of the implementing rule); and (2) the rationale explaining how the procedures demonstrate compliance with the Regulation. (c) The service provider should ensure that the roles and responsibilities for the change management processes are identified in the procedures. (d) Procedures should be submitted in a manner agreed between the service provider and the competent authority. Until an agreement is reached, the competent authority will prescribe the means of submission. (e) The procedure that defines the notification process for changes includes: (1) the point of contact in charge of the notification of changes, e.g. person, or part of the organisation and the role; (2) the means used for notification, e.g. fax, email, mail, use of database or others. (f) The management of change procedures should include a change identification procedure. This procedure, which is a precursor of the change notification process, should seek out potential changes, confirm that there is a real intent to implement them (propose the change) and, if so, initiate the notification process.