Implementation

Sam's content acceptance:

Level

Score

unit test

started 8 October 2020

comments issued 12 October requiring work for acceptance

19 October

comments issued 1requiring work for acceptance
reviewed first scenario; please see proposed changes in pages and apply to scenario 2 and 3, cfr use of AMDB to be avoided

accepted 27 October 2020

integration test

Started 02 November 2020

02 November, comments in line

~~points for integration:~~

~~The State approach diagram has still a comment attached → to be checked for integration, possibly remove "distribution channel setup" from diagram~~

Regarding DPS (not tied to Ch3) but I capture it here:

Release of https://www.easa.europa.eu/document-library/easy-access-rules/easy-access-rules-air-traffic-managementair-navigation-services
- clarifies what a Data Product Specification is
- GM1 AIS.TR.335(b) General — Digital data sets → DPS
  - (a) ISO Standard 19131 specifies the requirements and outline of data product specifications for geographic information. This is intended to facilitate and support the use and exchange of digital data sets between data providers and data users.
    (b) The data product specification enables air navigation users to evaluate the products and determine whether they fulfil the requirements for their intended use (application).
    (c) This may include an overview, specification scope, data product identification, data content and structure, reference system, data quality, data capture, data maintenance, data portrayal, data product delivery, additional information, and metadata.
- So this means that DPS is driven by ISO19131, which in turn means that the ED119C holds an example. So in principle the DPS is another MD set, which we could work from the MD we created.

accepted 06 November 2020

DPS related for backlog. Principles: AMD can be provided as AMD set for which DPS is applicable. AMD can also be provided in SWIM as an information service for which an information service definition is applicable. The DPS transition to Information Service Definition is the transition from data product to data over SWIM.
DPS is other set of MD and Service Definition MD is still being worked in the Eurocontrol SSCONE/SITCOM context.

final draft

updated DPS part to capture current high level understanding

accepted 08 December 2020

Introduction

This chapter is divided into three sections. The first section 'Approaches of implementation' introduces the viewpoints covered: State, Aerodrome and ANSP. The second section 'Stepwise implementation' provides information about the steps to be taken. The third section 'Other considerations' points at additional topics that require attention during implementation.

Note: This chapter is following the requirements and recommended practices contained in the publications listed in Chapter 2.

SWIM

SWIM plays an important role to realize the future vision according to the European ATM Masterplan (EATM). Indeed, the EATM sets the evolutionary goal towards the future Digital European Sky and introduces the “digital transformation” notion for the transition. This means building upon the recommendations provided in the SJU study: “A proposal for the future architecture of the European airspace.” In this study the emphasis is put on the decoupling of data service provision from local infrastructure and the progressive increase of collaboration and automation levels.

With the implementation of data services a more connected and collaborative environment emerges. This environment is based on the standards, requirements and principles of SWIM as confirmed by the SESAR deployment programme. Applying SWIM to the use case of aerodrome mapping data will lead to increased collaborative situational awareness.

More information on SWIM: https://reference.swim.aero/