Page Comparison

Clarification on the AIP Dataset scope

A3SG Team – the AIP dataset is in fact a subset of the AI promulgated through the AIP and the additional (dotted line) datasets may be considered

A3SG Team – proposes to address clarification on the AIP Dataset scope in the analysis of the AIFS

Clarification on the purpose of the work and the reporting mechanism, including the decision making process

A3SG Team – clarifies that A3SG is a technical group that analyses the scope and impact of the regulatory requirements and proposes guidance supporting the compliance; if issues are identified, the group will report the concerns to SDM, who may be able to clarify or take the matter further up to the potential review of the Regulation.

Clarification: retrieval vs distribution – does it refer to push / pull types of exchanges?

A3SG Team – in principle yes, however, the terminology will have to be revisited and aligned with the service categorisation (including taxonomy)

AIXM is indicated as the candidate exchange model for the CP1 (A3SG) scope of the services; what about AMXM?

A3SG Team – this is a discussion that needs to take place in order to decide if AIXM (version to be determined) + extensions would be sufficient for the exchanges, in particular for AMDB data or other exchange models, such as AMXM should be considered

A3SG Team - Start with AIFS service definition because of the several intersection points with the other services (AIP Data, obstacles, aerodrome maps, etc) 

A3SG Team proposes modelling of the identified services, considering the definition of the actors as part of the exercise.

Also noted: exchanges between AIS and AISP will be made starting from the identification of the actors as both consumers and providers. Same approach will be considered for airport operators and airport users.   

A3SG Team encourages the audience to volunteer and actively contribute for best understanding the expectations related to face to face and review cycle meetings.