Page 46 - UK ATM ANS Regulations (Consolidated) 201121

Part ATM/ANS.OR - ANNEX III - Common Requirements for Service Providers

request, then no update of the notification is required.
(f) For air traffic services (ATS) providers, the consequences of the change specified in (b)
(6), should be expressed in terms of the harmful effects of the change, i.e. the effects of
the hazards associated with safety risks. These could be the result of a preliminary safety
assessment, if available, or an early hazard analysis that concentrates on the service
level effects. For service providers other than air traffic services providers, the
consequences should be expressed in terms of what aspects of the performance of the
service are impacted by the change.
(g) The point of contact, as required in point (j) in AMC1 ATM/ANS.OR.A.045(a), provides a
focal point for the competent authority to contact when seeking complementary
information about the change when required. The aim is to improve communications
between the provider and the competent authority about the change.
(h) All notified changes should be unambiguously identified. The service provider and its
competent authority should agree on a means of referencing so as to associate a unique
identifier to a given notified change.
(i) For routine changes, the notification to the competent authority may be done in a simpler
manner, e.g. using forms less detailed than those specified in AMC1
ATM/ANS.OR.A.045(a) or notifying these changes collectively after being implemented at
regular periods of times agreed between the provider and the competent authority. A
service provider and its competent authority should coordinate so as to reach a common
agreement on these types of changes that may not be reviewed by the competent
authority. The list of such changes should be documented and formalised. The formalised
agreement becomes part of the change management procedures identified in
ATM/ANS.OR.B.010. Consequently, the list will be reviewed by the competent authority as
part of the audits it performs that are described in ATM/ANS.AR.C.010(a). The relevant
audit activity is detailed in AMC1 ATM/ANS.AR.C.010(a)(a)(2).
ATM/ANS.OR.A.045(a) GM2 Changes to a functional system
NOTIFICATION — SOFTWARE CRITICALITY
Depending on the complexity of the change to the functional system and the criticality of the software,
the depth of the evaluation may vary. The service provider should coordinate as soon as possible
with the competent authority in order to define a software oversight strategy as part of the change
review activities, if a decision for change review is taken.
ATM/ANS.OR.A.045(a)(3) AMC1 Changes to a functional system
NOTIFICATION TO USERS OF THE SERVICE
Having notified a change, the service provider should:
(a) individually inform all known service providers potentially affected by the notified change;
and
(b) inform all aviation undertakings potentially affected by the change either individually or via
a representative body of aviation undertakings or by publishing details of the planned
change in a dedicated publication of the service provider or aeronautical information
publications such as an aeronautical information circular (AIC).
ATM/ANS.OR.A.045(a)(3) GM1 Changes to a functional system
DEDICATED PUBLICATION FOR PROPOSED CHANGES
The final users of services potentially affected by a change to a functional system may not be known
by the service provider proposing the change. However, this should not prevent the service provider
from using other means for notification than direct communication with the interested parties. In that
case, the changes may be published in a dedicated website where the users of the service can
periodically check for current proposed changes to the functional system that may affect them.
ATM/ANS.OR.A.045(b) AMC1 Changes to a functional system
MODIFICATION OF A NOTIFIED CHANGE
(a) The service provider should inform the competent authority that was initially notified about
any update in the notification data when the information provided in a previous notification
about the same change is no longer valid or when information previously missing
becomes available. The other service providers and aviation undertakings should also be
informed, when they are affected by the new data.
(b) The cancellation of a previously notified change should be considered as a modification of
a notified change. Therefore, the service provider should inform about this update the
competent authority, and inform other service providers and aviation undertakings that
were initially informed about the change.
ATM/ANS.OR.A.045(c);(d) AMC1 Changes to a functional system
ENTRY INTO OPERATIONAL SERVICE OF A CHANGE SELECTED FOR REVIEW
The service provider should not start the implementation of any part of the change that has the
potential to affect the safety of the services currently being provided until a valid safety (support)
assessment for that part of the change exists and, if the change is subject to competent authority
review, it has been approved by the competent authority.
ATM/ANS.OR.A.045(c);(d) GM1 Changes to a functional system
TRANSITION INTO SERVICE
(a) No matter whether the competent authority has decided to review the notified change or
not, the service provider should not start the implementation of any part of the change that
has the potential to affect the safety of any of the services it provides, e.g. the functions
performed or the performance of the services, until it has produced a valid argument in
accordance with ATS.OR.205(2) or/and ATM/ANS.OR.C.005(2), as appropriate.
(b) Implementation of the change, which means the creation and installation of the items to
be used in the changed operational system may or may not affect the performance of the
20th November 2021 46 of 238