What should the competent authority check when approving change management procedures for functional systems according to AMC1 ATM/ANS.AR.C.030(b)?

The competent authority should check several aspects, including that the procedures cover the life cycle of a change, use the compliance matrix, make mandatory provisions for required actions and evidence, identify roles and responsibilities, and state that new procedures cannot be used until approval is granted.

What is the applicability date for DAT Providers according to the document?

The applicability date for DAT Providers is 1 January 2019.

According to AMC1 ATM/ANS.AR.C.030(b), what should the competent authority do with the compliance matrix provided by the service provider?

The competent authority should use the compliance matrix provided by the service provider when reviewing the content of the procedures, modifications, and/or deviations referred to in ATM/ANS.AR.C.030(a).

AMC1 ATM/ANS.AR.C.030(b) Approval of change management procedures for functional systems

Q: What does AMC1 ATM/ANS.AR.C.030(b) state regarding the use of new, modified, or deviating change management procedures?

The procedures should state that it is not allowed to use new, modified, or deviating change management procedures until approval is granted.

Q: As per AMC1 ATM/ANS.AR.C.030(b), what should the competent authority ensure regarding changes selected for review?

The competent authority should check that any change selected for review must not enter into operational service before the approval is granted.

Navigate / EASA

Ask question Discover more Add to collection

AMC1 ATM/ANS.AR.C.030(b) Approval of change management procedures for functional systems

ED Decision 2017/001/R

APPROVAL OF PROCEDURES

(a) When approving the change management procedures for functional systems as per ATM/ANS.OR.B.010, the competent authority should perform the following:

(1) check that the procedures used by a service provider to manage changes cover the life cycle of a change as defined in ATM/ANS.OR.C.005(a)(1) or ATS.OR.205(a)(1);

(2) use the compliance matrix provided by the service provider (referred to in AMC1 ATM/ANS.OR.B.010(a)), when reviewing the content of the procedures, modifications and/or deviations referred to in ATM/ANS.AR.C.030(a); as part of the oversight activity, the competent authority should check that the compliance matrix covers all the aforementioned requirements.

(3) check that the procedures make mandatory provisions that require actions to be undertaken and all required evidence to be produced to comply with requirements laid down in ATM/ANS.OR.A.045, ATM/ANS.OR.C.005, ATS.OR.205 and ATS.OR.210;

(4) check that the procedures identify the roles and responsibilities of the service provider in the change management processes;

(5) check that the procedures state that it is not allowed to use new, modified or deviating change management procedures until approval is granted; and

(6) check that the procedures state that any change selected for review must not enter into operational service before the approval is granted.

(b) The competent authority should provide a response to the service provider’s notification of change referred to in ATM/ANS.OR.A.045(a) without undue delay.

Details

Source-Title: AMC1 ATM/ANS.AR.C.030(b) Approval of change management procedures for functional systems View latest amendments

Erulesid: ERULES-1963177438-3145 Compare versions

Domain: Air traffic management/Air navigation services

Activitytype: Oversight, Authority management system, Air navigation services (ANS), Air traffic management (ATM), Air traffic services (ATS), Air traffic control services (ATC), Flight information services (FIS), Aerodrome flight information services (AFIS), Meteorological services (MET), Aeronautical information services (AIS), Data services (DAT), Communication services (COM), Navigation services (NAV), Surveillance services (SUR), Air traffic flow management (ATFM), Airspace management (ASM), Network functions (NF), European route network design (ERND), Radio frequency function (RFF), Transponder code function (TCF), Central air traffic flow management (central ATFM)

Amendedby: Initial issue

Applicabilitydate: 1 January, 2019 (DAT Providers)

Entryintoforcedate: 9 March, 2017

Icaoreference: Annex 19

Keywords: NAA, NSA, CAA

Regulatedentity: Competent authority

Regulatorysource: ED Decision 2017/001/R Navigate

Regulatorysubject: Part-ATM/ANS.AR

Typeofcontent: AMC to IR (Acceptable means of compliance to implementing rule)

Parentir: ATM/ANS.AR.C.030 Approval of change management procedures for functional systems

Origin: EASA

Category: EAR