European ATM Service Description Document for the ... · D65 - European ATM Service Description Document for the Aeronautical Information Feature Service for the Aeronautical Information

European ATM Service Description Document for the Aeronautical Information Feature Service

Document information

Project Title SESAR

Project Number 08.03.10

Project Manager NORACON

Deliverable Name European ATM Service Description Document for the Aeronautical Information Feature Service

Deliverable ID D65

Edition 00.02.00

Template Version 01.00.00

Task contributors

NORACON, Thales

Abstract This service provides aeronautical information features to the stakeholders. This service allows selecting the required aeronautical information by its feature type name and an advanced filter with spatial, temporal and logical operators. The service is compliant to the ISO 19142:2010 Geographic information - Web feature service.

Project Number 08.03.10 Edition 00.02.00 D65 - European ATM Service Description Document for the Aeronautical Information Feature Service for the Aeronautical Information Feature Service

2 of 45

©SESAR JOINT UNDERTAKING, 2011. Created by Thales, NORACON for the SESAR Joint Undertaking within the frame of the SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly acknowledged.

Authoring & Approval Prepared By - Authors of the document. Name & Company Position & Title Date Y. Ernotte (Thales Air Systems) Service architect 12/03/2012

Reviewed By - Reviewers internal to the project. Name & Company Position & Title Date Roger Li (NORACON) 8.3.3 Project Leader 26/03/2012

Reviewed By - Other SESAR projects, Airspace Users, staff association, military, Industrial Support, other organisations. Name & Company Position & Title Date Niklas Häggström (NORACON) WPB.4.3 Member 28/03/2012

Sam Van der Stricht (Eurocontrol) SWP 8.1 Manager 29/03/2012

Y. Ernotte (Thales Air Systems) WP13.2.2 Member 29/03/2012

Approved for submission to the SJU By - Representatives of the company involved in the project. Name & Company Position & Title Date Håkan Fahlgren (NORACON) 8.3.3 Project Leader 29/11/2013

Tord Pola / NORACON P08.03.10 Manager 31/05/2014

Lars Helleblad / NORACON P08.03.10 Deputy Manager 31/05/2014

Rejected By - Representatives of the company involved in the project. Name & Company Position & Title Date

Rational for rejection

Document History Edition Date Status Author Justification 00.00.01 12/03/2012 Draft Y. Ernotte First document version

00.01.00 29/03/2012 Final Y. Ernotte Revision after comments

00.01.01 25/09/2012 Final S. Johnsen Revision after SJU comments

00.01.02 28/09/2012 Final Y. Ernotte Remove spaces in service name

00.01.03 28/11/2013 Final Y. Ernotte Move to last document template according to a SJU decision related to reservations about ISRM 1.0.

00.01.04 23/05/2014 Final Les Folds Update to template and delivery of the ISRM at version 1.1

00.02.00 31/05/2014 Final Tord Pola Minor updates of document properties

00.02.00 02/06/2016 Final Lars Helleblad Changed delivery ID

Intellectual Property Rights (foreground) This deliverable consists of SJU foreground.


3 of 45


Table of Contents EXECUTIVE SUMMARY .................................................................................................................................... 5

1 INTRODUCTION .......................................................................................................................................... 6 1.1 PURPOSE OF THE DOCUMENT ............................................................................................................... 6 1.2 INTENDED READERSHIP......................................................................................................................... 6 1.3 INPUTS FROM OTHER PROJECTS ........................................................................................................... 6 1.4 GLOSSARY OF TERMS ........................................................................................................................... 6 1.5 ACRONYMS AND TERMINOLOGY ........................................................................................................... 6

1.5.1 Acronyms......................................................................................................................................... 6 1.5.2 Terminology .................................................................................................................................... 7

2 SERVICE IDENTIFICATION ...................................................................................................................... 9

3 OPERATIONAL AND BUSINESS CONTEXT ...................................................................................... 10 3.1 INFORMATION EXCHANGE REQUIREMENTS ........................................................................................ 11 3.2 OTHER REQUIREMENTS ...................................................................................................................... 14

3.2.1 Non-Functional Requirements .................................................................................................. 14 3.2.2 Relevant Industrial Standards .................................................................................................... 14 3.2.3 Nodes ............................................................................................................................................. 14

4 SERVICE OVERVIEW .............................................................................................................................. 15

4.1 SERVICE POLICIES (TAXONOMY) ........................................................................................................ 15 4.2 SERVICE ATTRIBUTES (QOS) ............................................................................................................. 17 4.3 SERVICE FUNCTIONS AND CAPABILITIES ............................................................................................ 17 4.4 SERVICE INTERFACES ......................................................................................................................... 18 4.5 SERVICE OPERATIONS ........................................................................................................................ 19

5 SERVICE INTERFACE SPECIFICATIONS .......................................................................................... 21 5.1 SERVICE INTERFACE AERONAUTICALINFORMATIONFEATURE DEFINITION ........................................ 21

5.1.1 Operation getCapabilities ............................................................................................................ 21 5.1.2 Operation getFeatures ................................................................................................................ 23 5.1.3 DescribeStoredQueries Operation ............................................................................................ 31 5.1.4 Operation listStoredQueries ....................................................................................................... 34 5.1.5 GetPropertyValue Operation ...................................................................................................... 35 5.1.6 Operation describeFeatureType ................................................................................................ 37

6 SERVICE DYNAMIC BEHAVIOUR ........................................................................................................ 39 6.1 SERVICE INTERFACE AERONAUTICALINFORMATIONFEATURE ........................................................... 39

7 SERVICE PROVISIONING (OPTIONAL) .............................................................................................. 40

8 VALIDATION AND VERIFICATION ....................................................................................................... 41 8.1 VERIFICATION ...................................................................................................................................... 41 8.2 VALIDATION ......................................................................................................................................... 41

9 REFERENCES ........................................................................................................................................... 42

APPENDIX A PHYSICAL INTERFACES ................................................................................................. 44


4 of 45


List of tables No table of figures entries found.

List of figures Figure 1 NAV IER Service to Requirements Traceability Diagram 1 .................................................... 11 Figure 2 NAV IER Service to Requirements Traceability Diagram 2 .................................................... 12 Figure 3 NOV-2 Node Realisation to Service Interface ........................................................................ 14 Figure 4 Part of the NSOV-1 service taxonomy diagram ...................................................................... 17 Figure 5 NSOV-1 Service Levels .......................................................................................................... 17 Figure 6 NSOV-4 Service to Operational Activities Mapping ................................................................ 18 Figure 7: NSOV-2 Service Interface Definition Diagram ....................................................................... 19 Figure 8 NSOV-2 Service Interface Overview ...................................................................................... 20 Figure 9: NSOV-2 Service Definition GetCapabilities Request ............................................................ 22 Figure 10: NSOV-2 Service Definition GetCapabilitiesResponse......................................................... 23 Figure 11: NSOV-2 Service Definition GetFeature Request ................................................................. 26 Figure 12: NSOV-2 Feature Collection ................................................................................................. 26 Figure 13 NSOV-2 Aeronautical Feature Structure 1 ........................................................................... 27 Figure 14 NSOV-2 Aeronautical Feature Structure 2 ........................................................................... 28 Figure 15 NSOV-2 Aeronautical Feature Structure 3 ........................................................................... 29 Figure 16 NSOV-2 Aeronautical Feature Structure 4 ........................................................................... 30 Figure 17 NSOV-2 Aeronautical Feature Structure 5 ........................................................................... 31 Figure 18 NSOV-2 Describe Stored Queries Request ......................................................................... 32 Figure 19 NSOV-2 Describe Stored Queries Response ....................................................................... 34 Figure 20: NSOV-2 Service Definition List Stored Queries Request .................................................... 34 Figure 21: NSOV-2 Service Definition List Stored Queries Response ................................................. 35 Figure 22 NSOV-2 Get Property Value Request .................................................................................. 37 Figure 23 NSOV-2 Value Collection ..................................................................................................... 37 Figure 24: NSOV-2 Service Definition Describe Feature Type Request .............................................. 38 Figure 25: NSOV-2 Service Definition Describe Feature Type Response ........................................... 38 Figure 26: NSOV-5 Service Event Trace Description ........................................................................... 39 Figure 27: Artefacts ............................................................................................................................... 44


5 of 45


Executive summary This service provides aeronautical information features to the stakeholders.

This service allows selecting the required aeronautical information by its feature type name and an advanced filter with spatial, temporal and logical operators.

This document has been produced by the fast track 4.


6 of 45


1 Introduction

1.1 Purpose of the document The purpose of this Service description is to provide a holistic overview of a particular service and its building blocks. It services as a complement to a model based description and supports the configuration management process by providing well-defined baselines.

The service description document is also the foundation material for the standardisation process.

1.2 Intended readership This service description is intended to be read by Enterprise Architects, Service Architects, Information Architects, System Engineers and Developers in pursuing architecting, design and development activities.

1.3 Inputs from other projects This service has been designed according to the following documents:

• 13.2.2 D01 OSED for Step 1 [10]

• 08.03.03 D01 Identification of operational requirements for Step 1 [11]

1.4 Glossary of terms

1.5 Acronyms and Terminology

1.5.1 Acronyms Term Definition

ADD Architecture Description Document

AIM Aeronautical Information Management

ATM Air Traffic Management

E-ATMS European Air Traffic Management System

FAA Federal Aviation Administration

IER Information Exchange Requirement

ISRM Information Services Reference Model

NAF NATO Architecture Framework

NSOV NAF Service Oriented View

NOV NAF Operational View


7 of 45


Term Definition

NSV NAF System View

OSED Operational Service and Environment Definition

QoS Quality of Service

SESAR Single European Sky ATM Research Programme

SESAR Programme The programme which defines the Research and Development activities and Projects for the SJU.

SJU SESAR Joint Undertaking (Agency of the European Commission)

SJU Work Programme The programme which addresses all activities of the SESAR Joint Undertaking Agency.

SoaML Service Oriented Architecture Modelling Language

SWIM System Wide Information Management

UML Unified Modelling Language

V&V Validation and Verification

WFS Web Feature Service

WSDL Web Services Definition Language

XSD XML Schema Definition

1.5.2 Terminology Term Definition Source

Capability The collective ability to deliver a specified type of effect or a specified course of action. Within the context of the SESAR Programme a capability is therefore the ability to support the delivery of a specific operational concept to an agreed level of performance.

Common working meeting between B41 EA study and B43 T5

Capability Configuration

A combination of organisational aspects (with their competencies) and equipment that combine to provide a capability. A Capability Configuration represents a recognisable set of resources (technical systems, human roles, and physical assets) derived from a generic stakeholder organisation.

Note: Capability Configuration is a term used in NAF. The equivalent SoaML stereotype to be used is Participant. Also see note in Node term definition.

B43 ADD

Node A logical entity that performs Operational Activities specified independently of any physical realisation e.g. a stakeholder

Common working meeting between


8 of 45


Term Definition Source type providing and/or consuming operational information within a network of others.

Note: Node is a term used in NAF. The equivalent SoaML stereotype to be used is Participant. Be aware that the original intention of SoaML is that Participants are physical items and not logical constructs. Service architects must indicate whether the Participant is a logical (Node) or a physical (Capability Configuration) construct.

B41 EA study and B43 T5

Service The contractual provision of something (a non-physical object), by one, for the use of one or more others. Services involve interactions between providers and consumers, which may be performed in a digital form (data exchanges) or through voice communication or written processes and procedures.

B43 T5 study

Service attribute A Service Attribute defines a property of a service. Examples: Response time, Frequency of invocation, Message Exchange Pattern.

B43 T5 study

Service contract A service contract represents an agreement between the stakeholders involved for how a service is to be provided and consumed.

B43 T5 study

Service function A Service function describes what functionality is needed to provide or consume a service; it is the trigger for or is triggered by the Service interactions. A Service function can be automated to different extents depending on the context e.g. a Service function supporting a complex activity may need more automation than a Service function for a simple activity.

Note: The equivalent SoaML stereotype is Capability, in WP8 Foundation documentation referred to as Service Capability.

B43 T5 study

Service interaction

A Service interaction is a description of an information exchange between ATM stakeholders’ systems which can potentially be automated; phone calls / voice exchanges are considered as non-automated service interactions.

In considering automated interactions, a service interaction is described by several modelling artefacts depicting the static and dynamic behaviour of a service. This includes service operations, data messages model and interaction behaviour.

B43 T5 study

Service interface The mechanism by which a service communicates.

Service providers and consumers need to implement service interfaces to be able to collaborate. A service interface includes service operations that enable access to the functionality of the services identified, as well as the data used in the service interaction.

B43 T5 study


9 of 45


2 Service identification

Name AeronauticalInformationFeatureService

ID {4C1CABAB-E8AF-45f6-9199-1932F95FC16F}

Version 1.0

Keywords AIM, WFS, Fast Track 4

Architect(s) Y. Ernotte (Thales Air System)

Lifecycle status

Date Link

Identified 30/3/2012 8.3.10.D06_Consolidation_Report

Allocated 30/3/2012 European ATM Service Description Document

Designed 30/3/2012 8.3.10.D06_Consolidation_Report

Validated

IOC 31/12/2016 AIMS-14 enabler of the ATM master plan [12]

FOC AIMS-14 enabler of the ATM master plan [12]


10 of 45


3 Operational and Business context At the time of writing there are no business level capabilities provided from the Business Architect (WPB4.1). The description of what business level capabilities the service aims to achieve will be added once these are available.

Basically, aeronautical information needs to be shared between the different stakeholders in order to allow them to exchange operational information based on these data. The stakeholder needs can be very different from those needed by an aircraft, an airport or a general aviation pilot.

The operational context and requirements are not yet available from all operational projects. But some documents already exists like:

• Eurocae ED-151 OPERATIONAL SERVICES AND ENVIRONMENT DEFINITION (OSED) FOR AERONAUTICAL INFORMATION SERVICES (AIS) AND METEOROLOGICAL (MET) DATA LINK SERVICES [13]

• 13.2.2 D01 OSED for Step 1 [10]

• 08.03.03 D01 Identification of operational requirements for Step 1 [11]

The service is expected to be offered by an Aeronautical Information Service Provider at National, FAB or regional level.

All stakeholders can be potential consumers of this service but it is not yet stated if they will used directly or indirectly through other high level services (e.g. AMIS - Aerodrome Mapping Information Service or TSIS – Taxiway Status Information Service).


11 of 45


3.1 Information Exchange Requirements NAV IER NAV IER AeronauticalInformationFeature serv ice requirements traceability

Digital NOTAM - No manual input of baseline

tagsmegaid = ref = REQ-13.2.2-OSED-0201.0009refType = Operational requirementText =

Digital NOTAM - Retrieve baseline data

tagsmegaid = ref = REQ-13.2.2-OSED-0201.0007refType = Operational requirementText =

Provide aeronautical information

tagsmegaid = ref = REQ-08.03.03-ISRM-AIFS.0001refType = Interaction requirementText =

Spatial Data Selection

tagsmegaid = ref = REQ-08.03.03-D01-ARES.0002refType = Operational requirementText =

Selection Using Temporality Filter


Extraction of Airspace Reservation Attribute Data


Taxiway Status Availabil ity

tagsmegaid = ref = REQ-08.03.03-D01-TSIS.0004refType = Operational requirementText =

Taxiway Status Usage by Different Consumers


Taxiway Status Consistency of Key Data


Usage of 4D trajectory in the route validation process

tagsmegaid = ref = refType = Text =

Usage of aircraft performance data in the route validation process


Availabil ity of ATM constraints


Extension of free route areas


Digital NOTAMs


Request Aeronautical Info Data


AeronauticalInformationManagementService

«Service»AeronauticalInformationFeature

Name: NAV IER AeronauticalInformationFeature service requirements traceabilityAuthor: 08.03.03 Y. ErnotteVersion: 1.0Created: 1/27/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«Satisfy»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

Figure 1 NAV IER Service to Requirements Traceability Diagram 1


12 of 45


NAV IER NAV IER AeronauticalInformationFeature serv ice requirements traceability 2

Provide aerodrome mapping features

tagsmegaid = ref = REQ-08.03.03-ISRM-AMIS.0001refType = Interaction requirementText =

(from IER requirements)

Provide spatial fi l ter



Provide temporal fi l ter



Retrieve Aerodrome Map information

tagsmegaid = ref = REQ-08.03.03-D01-AMIS.0001refType = Operational requirementText =


Spatial Filter



Extraction of Features from Map Layers



Supply of Feature Status



Consistency of Feature Data






Extraction of Feature Atrribute Data



Spatial Data Selection






Extraction of Airspace Reservation Attribute Data




«Service»Serv ice::AeronauticalInformationFeature

Name: NAV IER AeronauticalInformationFeature service requirements traceability 2Author: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«Satisfy»

«Satisfy»

«Satisfy»«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

«Refine»

Figure 2 NAV IER Service to Requirements Traceability Diagram 2

The requirements from Project P13.02.02 and P11.01.02 are listed below. Others shown from P08.03.03 are for reference only. Element Name Author Notes Digital NOTAM - No manual input of baseline

08.03.03 Y. Ernotte A requirement.

Element Tagged Value Name Value megaid ref REQ-13.2.2-OSED-0201.0009 refType Operational requirement Text

Element Name Author Notes Digital NOTAM - Retrieve baseline data

08.03.03 Y. Ernotte A requirement.

Element Tagged Value Name Value megaid ref REQ-13.2.2-OSED-0201.0007 refType Operational requirement Text

Element Name Author Notes


13 of 45


Usage of 4D trajectory in the route validation process

08.03.03 Y. Ernotte A requirement

Element Tagged Value Name Value megaid ref refType Text

Element Name Author Notes Usage of aircraft performance data in the route validation process

08.03.03 Y. Ernotte A requirement

Element Tagged Value Name Value megaid ref refType Text

Element Name Author Notes Availability of ATM constraints 08.03.03 Y. Ernotte A requirement Element Tagged Value Name Value megaid ref refType Text

Element Name Author Notes Extension of free route areas 08.03.03 Y. Ernotte A requirement Element Tagged Value Name Value megaid ref refType Text

Element Name Author Notes Digital NOTAMs 08.03.03 Y. Ernotte A requirement Element Tagged Value Name Value megaid ref refType Text

Element Name Author Notes Request Aeronautical Info Data 08.03.03 Y. Ernotte A requirement Element Tagged Value Name Value megaid ref refType Text


14 of 45


3.2 Other Requirements

3.2.1 Non-Functional Requirements There are currently no applicable identified NFR.

3.2.2 Relevant Industrial Standards The service is compliant to the ISO 19142:2010 Geographic information – Web feature service [8].

3.2.3 Nodes The diagram below shows the EATMA nodes involved with providing and consuming the service interfaces.

NOV-2 nrs NOV-2 Node realisation of AeronauticalInformationFeatureServ ice serv ice

Name: NOV-2 Node realisation of AeronauticalInformationFeatureService serviceAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/29/2014 12:00:00 AMUpdated: 5/29/2014 12:00:00 AM

«Node»AeronauticalDataSupplier

«Node»ATS Operations

«Node»En-Route/Approach ATS

«Node»Network Operations

«Node»Regional/sub-regional Network Management

«Node»Flight Deck

«Node»Airspace User Operations

«ServiceInterfaceDefinition»Prov idedAeronauticalInformationFeatureInterfaceDefinition

«ServiceInterfaceOperation»+ DescribeFeatureType(DescribeFeatureTypeRequest) :DescribeFeatureTypeResponse+ DescribeStoredQueries(DescribeStoredQueriesRequest) :DescribeStoredQueriesResponse+ GetCapabilities(GetCapabilitiesRequest) :WFS_Capabilities+ GetFeature(GetFeatureRequest) :FeatureCollection+ GetPropertyValue(GetPropertyValueRequest) :ValueCollection+ ListStoredQueries(ListStoredQueriesRequest) :ListStoredQueriesResponse

«NodeRequiresServiceInterface»

«NodeRequiresServiceInterface» «NodeRequiresServiceInterface»

«NodeRequiresServiceInterface»«NodeRequiresServiceInterface»

«NodeRequiresServiceInterface»

Figure 3 NOV-2 Node Realisation to Service Interface


15 of 45


4 Service overview The aeronautical information feature service is a request / response service that enables exchange of aeronautical information.

The service allows a provider of the service to describe its abilities for potential consumers in terms of:

• feature provided,

• full feature description (name, attributes, …),

• geographical coverage,

• filtering capabilities (spatial, temporal and on attribute values)

The service allows the requester to get aeronautical information feature by providing a list of feature name and a query filter composed of spatial, temporal and on attribute values operators. The service is then able to response to precise request that will return small among of data but can also be used to retrieve all content the provider holds.

The service is also providing predefined queries that the requester can use without knowing the query syntax.

The service is compliant to the ISO 19142:2010 Geographic information – Web feature service [8].

4.1 Service Policies (Taxonomy) The taxonomy diagram below shows the service as a specialisation of an Aeronautical Information Management Service.


16 of 45


NSOV-1 NSOV-1 AeronauticalInformationFeature Serv ice Taxonomy

«Service»ATMinformationManagementService

«Service»AeronauticalInformationManagementService


«Service»IsrmService

{root}

«ServiceAttribute»+ providedAccessControl :AccessControl+ providedAuthenticity :Authentication+ providedAvailabilityInPercent :Integer+ providedContext :ISRMcontext+ providedContextQualification :Qualification+ providedFlightCondition :Integer+ providedIntegrity :Integrity+ providedMaximumMessageReception :Integer+ providedMaximumMessageSize :Integer+ providedMaximumReceptionPerTimeUnit :TimeUnit+ providedMessageSizeUnit :MessageSizeUnit+ providedProcessingThroughput :Integer+ providedProcessingThroughputTimeUnit :TimeUnit+ providedProvisionCapacity :Integer+ providedProvisionPeriod :TimeUnit+ providedRecoverabilityTime :Integer+ providedRecoverabilityTimeUnit :TimeUnit+ providedReportingCondition :ReportingCondition+ providedResponseTime :Integer+ providedResponseTimeUnit :TimeUnit+ providedSafety :Safety+ requiredAccessControl :AccessControl+ requiredAuthenticity :Authentication+ requiredAvailabilityInPercent :Integer+ requiredConfidentiality :Confidentiality+ requiredContext :ISRMcontext+ requiredContextQualification :Qualification+ requiredFlightCondition :Integer+ requiredIntegrity :Integrity+ requiredMaximumMessageReception :Integer+ requiredMaximumMessageSize :Integer+ requiredMaximumReceptionPerTimeUnit :TimeUnit+ requiredMessageSizeUnit :MessageSizeUnit+ requiredProcessingThroughput :Integer+ requiredProcessingThroughputTimeUnit :TimeUnit+ requiredProvisionCapacity :Integer+ requiredProvisionPeriod :TimeUnit+ requiredRecoverabilityTime :Integer+ requiredRecoverabilityTimeUnit :TimeUnit+ requiredReportingCondition :ReportingCondition+ requiredResponseTime :Integer+ requiredResponseTimeUnit :TimeUnit+ requiredSafety :Safety

Name: NSOV-1 AeronauticalInformationFeature Service TaxonomyAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«ServiceGeneralisation»




17 of 45


Figure 4 Part of the NSOV-1 service taxonomy diagram

4.2 Service Attributes (QoS) Two main usage of the service are described in the diagram below:

• Frequent requests to retrieve some limited data size (service used by a human machine interface for example) (level 2).

• Low request rate but requesting lot of data (retrieve all the aeronautical information data of a country each AIRAC cycle for example) (level 1).

NSOV-1 SL NSOV-1 AeronauticalInformationFeature serv ice lev els

«ServiceLevel»aeronauticalInformationFeatureLev el1:

AeronauticalInformationFeatureServ ice :AeronauticalInformationFeature

requiredAvailabil ityInPercent => 99.99requiredContext = Full AIM datarequiredResponseTimeUnit = SecondsrequiredResponseTime = 10requiredMaximumMessageReception = 100requiredMaximumReceptionPerTimeUnit = DayrequiredMaximumMessageSize = 1requiredMessageSizeUnit = Gbyte

«ServiceLevel»aeronauticalInformationFeatureServ iceLev el2 :

AeronauticalInformationFeature

requiredAvailabil ityInPercent => 99.99requiredContext = HMIrequiredResponseTime = 2requiredResponseTimeUnit = SecondsrequiredMaximumMessageReception = 1000requiredMaximumReceptionPerTimeUnit = MinuterequiredMaximumMessageSize = 10requiredMessageSizeUnit = Kbyte

Name: NSOV-1 AeronauticalInformationFeature service levelsAuthor: 08.03.03 Y. ErnotteVersion: 1.0Created: 2/14/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

Figure 5 NSOV-1 Service Levels

4.3 Service Functions and Capabilities The diagram below shows the EATMA Operational Activities supported by the service.


18 of 45


NSOV-4 NSOV-4 Serv iceToOperationalActiv itiesMapping



Name: NSOV-4 ServiceToOperationalActivitiesMappingAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«Node»AeronauticalDataSupplier

«Node»ATS Operations

«Node»En-Route/Approach ATS

«Node»Network Operations

«Node»Regional/sub-regional Network Management

Execute Network Management

Operations

«Node»Flight Deck

«Node»Airspace User Operations

Fly trajectory

Monitor Network Capacity

Plan ATS Operations

Plan AU Operations

«Consumes»

«NodeHasBehaviour»

«Consumes»


«Consumes»

«CapabilityForNode»



«Consumes»



«Consumes»

«Consumes»


«Provides»

«ServiceSupportsActivity»





Figure 6 NSOV-4 Service to Operational Activities Mapping

4.4 Service Interfaces The diagram below shows the service’s single interface.


19 of 45


NSOV-2 NSOV-2 AeronauticalInformationFeature serv ice interface definition

«ServiceInterface»AeronauticalInformationFeatureInterface






«Serv iceConsumer»AeronauticalInformationFeatureConsumer

Name: NSOV-2 AeronauticalInformationFeature service interface definitionAuthor: 08.03.03 Y. ErnotteVersion: 1.0Created: 1/27/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«RequiredServiceInterfaceDefinition»

Figure 7: NSOV-2 Service Interface Definition Diagram

4.5 Service Operations The service supports the set of operations defined by ISO standard 19142:2010. These six operations are shown inside the Interface Definition diagram shown below.


20 of 45


NSOV-2 NSOV-2 AeronauticalInformationFeature serv ice interface definition







«Serv iceConsumer»AeronauticalInformationFeatureConsumer

Name: NSOV-2 AeronauticalInformationFeature service interface definitionAuthor: 08.03.03 Y. ErnotteVersion: 1.0Created: 1/27/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«RequiredServiceInterfaceDefinition»

Figure 8 NSOV-2 Service Interface Overview

The payload dataflows shown as input and output to the service operations are defined in section 5


21 of 45


5 Service interface specifications The service supports a single interface.

5.1 Service Interface AeronauticalInformationFeature Definition

The set of operations and their input and output payloads are shown in the following sections. Because the payload of the getFeature operations is a set of AIXM 5.1 features these are not described in detail as they are defined in the AIXM 5.1 standard.

5.1.1 Operation getCapabilities This R/R operation returns the capabilities of the user specified service. In compliance with the OGC standards for a WFS the main output is the set of feature types the service supports.

5.1.1.1 Operation Functionality The GetCapabilities operation generates a service metadata document describing a WFS service provided by a server.

The capabilities response document contains the following sections:

1) WSDL section (optional)

This section allows a server to reference an optional WSDL document that describes the operations that the service offers. This section may be included in addition to the OperationsMetadata section for tools that know how to use the WSDL.

2) FeatureType list section (mandatory)

This section defines the list of feature types that are offered by a web feature service. Lightweight metadata is provided about each feature type.

3) Filter capabilities section (mandatory) The schema of the Filter Capabilities Section is defined in ISO 19143:2010 Geographic information – Filter encoding [9] and is used to advertise the expressions that may be used to form query predicates.

The operation has a single parameter which supplies the name of the service and other minor parameters (defined in the WFS standard defined by the OGC). It returns the capabilities of the WFS that allow the user to request them in subsequent calls to the service using the getFeature operation.

The response is a message structure also defined in the WFS standard that contains the feature types that the service can provide to the getFeature operation.

5.1.1.2 Operation Parameter The input parameter is called GetCapabilitiesRequest and is shown below:


22 of 45


NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Get Capabilities R...

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Get Capabilities RequestAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«EntityItem»Entity items::GetCapabilitiesRequest

«EntityItemAttribute»+ format[0..1] :CharacterString+ operationalName[1] :CharacterString = GetCapabilities+ service[1] :CharacterString = WFS+ updateSequence[0..1] :Integer+ version[0..1] :CharacterString = 1.2.0

Figure 9: NSOV-2 Service Definition GetCapabilities Request

Element Name Author Notes GetCapabilitiesRequest 08.03.03 Les Folds Get the capabilities of the WFS service. Element Tagged Value Name Value encoding Attribute Name Type Notes format[0..1] CharacterString The format to be used for the response. Tagged Value Name Value Attribute Name Type Notes operationalName[1] CharacterString The name of the operation to use. Tagged Value Name Value Attribute Name Type Notes service[1] CharacterString The name of the service to use. Tagged Value Name Value Attribute Name Type Notes updateSequence[0..1] Integer The sequence number of the last request. Tagged Value Name Value Attribute Name Type Notes version[0..1] CharacterString The version of the service to use. Tagged Value Name Value

The output returned by the operation is called WFS_Capabilities and is shown below:


23 of 45


.NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Get Capabilities Response

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Get Capabilities ResponseAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«EntityItem»ISO 19142 WFS::WFS_Capabilities

«EntityItemAttribute»- WSDL [0..1]

«EntityItem»ISO 19142 WFS::FeatureTypeList

«EntityItem»ISO 19142 WFS::FeatureType

«EntityItemAttribute»- abstract :CharacterString [0..*]- envelope :GM_Envelope [0..*]- keywords :CharacterString [0..*]- metadata :Metadata [0..*]- name :ScopedName- outputFormats :OutputFormatList- title :CharacterString [0..*]

«EntityItem»ISO 19143 Filter::FilterCapabilities

«EntityItem»ISO 19142 WFS::

Metadata

«EntityItemAttri...- about :Any- value :Any

«EntityItem»ISO 19142 WFS::OutputFormatList

«EntityItem»ISO 19142 WFS::ScopedName

«EntityItemAttribute»- name :CharacterString- namespace :CharacterString

+name«EntityItemAttribute»

1

«EntityItemAttributeRelationship»

+outputFormats«EntityItemAttribute»

1


+metadata«EntityItemAttribute»

0..*


+filterCapabilities«EntityItemAttribute»

1..*


+featureType«EntityItemAttribute»

1..*


+featureTypes«EntityItemAttribute»

0..1«EntityItemAttributeRelationship»

Figure 10: NSOV-2 Service Definition GetCapabilitiesResponse

The mapping of the EntityItems to the AIRM is not possible as the structures used are taken from ISO 19142 and ISO 19143 standards and are thus not part of the AIRM nor are they in scope.

5.1.2 Operation getFeatures The GetFeature operation returns a selection of features from a data store. A WFS processes a GetFeature request and returns a response document to the client that contains zero or more feature instances that satisfy the query expressions specified in the request.

Multiple query expressions may be encoded into a single GetFeature request.

A query expression can be a “stored query” (predefined queries stored in the server) or an adhoc query build by the service user. The queries use the spatial, temporal and property values filter capabilities defined in ISO 19143:2010 Geographic information – Filter encoding [9] and published in the GetCapabilities response.

The GetFeature response is a list of AIXM 5.1 features.

.


24 of 45


5.1.2.1 Operation Functionality The user supplies the operation has a single parameter which supplies the name of the service, the list of feature types to return, the spatial dimension filter and other minor parameters (defined in the WFS standard defined by the OGC). It returns the set of features that meet the specified criteria from the set of feature types selected.

5.1.2.2 Operation Parameter The input parameter is called GetFeatureRequest and is shown below:


25 of 45


NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Get Feature Request

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Get Feature RequestAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM


GetFeatureRequest

«EntityItem»ISO 19143 Filter::

AdhocQueryExpression

«EntityItemAttribute»- projection :Any [0..1]

«EntityItem»ISO 19143 Filter::QueryExpression

«EntityItem»ISO 19142 WFS::StoredQuery

«EntityItemAttribute»- id :CharacterString

«EntityItem»ISO 19142 WFS::Query

«EntityItemAttribute»- projection :PropertyName [0..1]

«EntityItem»ISO 19142 WFS::Parameter

«EntityItemAttribute»- name :CharacterString- value :Any

+parameter«EntityItemAttribute» 0..*

«EntityItemAttributeRelationship»«SubtypeRelationship»

«SubtypeRelationship»

+query«EntityItemAttribute» 1..*




26 of 45


Figure 11: NSOV-2 Service Definition GetFeature Request

The output returned by the operation is called FeatureCollection and is shown below:

NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Get Feature Response

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Get Feature ResponseAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«EntityItem»ISO 19142 WFS::FeatureCollection

«EntityItemAttribute»- additionalObjects :Feature [0..*]- member :Feature [0..*]

«EntityItem»ISO 19142 WFS::Feature

«EntityItem»Entity items::

AeronauticalInformationFeature


+member«EntityItemAttribute»0..*


+additionalObjects«EntityItemAttribute» 0..*


Figure 12: NSOV-2 Feature Collection

The complete set of EntityItems making up the different types of features are shown in the following diagrams. All the feature types shown are defined in AIXM 5.1 and as such are outside the AIRM and are not mapped to AIRM attributes.


27 of 45


NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Feature data 1

Feature

«EntityItem»AeronauticalInformationFeature

«EntityItem»AerialRefuelling

«EntityItem»AeronauticalGroundLight

«EntityItem»AirTrafficControlServ ice

«EntityItem»AirTrafficManagementServ ice

«EntityItem»AircraftGroundServ ice

«EntityItem»AircraftStands

«EntityItem»AirportClearanceServ ice

«EntityItem»AirportGroundService

«EntityItem»AirportHeliport

«EntityItem»AirportHeliportCollocation

«EntityItem»AirportHeliportProtectionArea

«EntityItem»AirportHotSpot

«EntityItem»AirportProtectionAreaMarking

«EntityItem»AirportSuppliesServ ice

«EntityItem»Airspace

«EntityItem»AirspaceBorderCrossing

«EntityItem»AltimeterSource

«EntityItem»AngleIndication

«EntityItem»ApproachLeg

«EntityItem»ApproachLightingSystem

«EntityItem»Apron

«EntityItem»ApronElement

«EntityItem»ApronLightSystem

«EntityItem»ApronMarking

«EntityItem»ArrestingGear

«EntityItem»Arriv alFeederLeg

«EntityItem»Arriv alLeg

«EntityItem»AuthorityForAirspace

«EntityItem»Azimuth

«EntityItem»ChangeOv erPoint




















«SubtypeRelationship»«SubtypeRelationship»










Figure 13 NSOV-2 Aeronautical Feature Structure 1


28 of 45



Feature


tagsCLDMSemanticTrace = urn:x-ses:airm:v310:ConsolidatedLogicalDataModel:Abstract:TemporalEnabledEntity

«EntityItem»InstrumentApproachProcedure

tagspersistence = transient

«EntityItem»CheckpointINS


«EntityItem»CheckpointVOR


«EntityItem»CirclingArea


«EntityItem»DME

tagspersistence = persistent

«EntityItem»DeicingArea


«EntityItem»DeicingAreaMarking


«EntityItem»DepartureLeg


«EntityItem»DesignatedPoint


«EntityItem»DirectionFinder


«EntityItem»DistanceIndication


«EntityItem»Elev ation


«EntityItem»Ev ent

«EntityItem»FinalLeg


«EntityItem»FireFightingServ ice


«EntityItem»FlightFormation


«EntityItem»FlightRestriction


«EntityItem»FloatingDockSite


«EntityItem»GeoBorder


«EntityItem»Glidepath


«EntityItem»GroundLightSystem


«EntityItem»GroundTrafficControlServ ice


«EntityItem»GuidanceLine


«EntityItem»GuidanceLineLightSystem


«EntityItem»GuidanceLineMarking


«EntityItem»HoldingAssessment


«EntityItem»HoldingPattern


«EntityItem»InformationServ ice


«EntityItem»InitialLeg


«EntityItem»IntermediateLeg








«SubtypeRelationship» «SubtypeRelationship»






















29 of 45



Feature


«EntityItem»Localizer

«EntityItem»MarkerBeacon

«EntityItem»Marking

«EntityItem»MarkingBuoy

«EntityItem»MilitaryFleet

«EntityItem»MissedApproachLeg

«EntityItem»Mission

«EntityItem»NDB

«EntityItem»NationalMilitaryActiv ities

«EntityItem»Nav aid

«EntityItem»NavaidEquipment

«EntityItem»Nav igationArea

«EntityItem»Nav igationAreaRestriction

«EntityItem»NavigationSystemCheckpoint

«EntityItem»ObstacleArea

«EntityItem»OptimumAirspace

«EntityItem»OrganisationAuthority

«EntityItem»PassengerLoadingBridge

«EntityItem»PassengerServ ice

«EntityItem»PilotControlledLighting

«EntityItem»PrecisionApproachRadar

«EntityItem»PrimarySurv eillanceRadar

«EntityItem»Procedure

«EntityItem»ProcedureDME

«EntityItem»RadarEquipment

«EntityItem»RadarSystem

«EntityItem»RadioCommunicationChannel

«EntityItem»RadioFrequencyArea

«EntityItem»Road

«EntityItem»Route































30 of 45



Feature


«EntityItem»StandardLev elTable

«EntityItem»RouteDME

«EntityItem»RouteSegment

«EntityItem»RulesProcedures

«EntityItem»Runway

«EntityItem»RunwayBlastPad

«EntityItem»RunwayCentrelinePoint

«EntityItem»RunwayDirection

«EntityItem»RunwayDirectionLightSystem

«EntityItem»RunwayElement

«EntityItem»RunwayMarking

«EntityItem»RunwayProtectArea

«EntityItem»RunwayProtectAreaLightSystem

«EntityItem»RunwayVisualRange

«EntityItem»SDF

«EntityItem»SeaplaneLandingArea

«EntityItem»SeaplaneRampSite

«EntityItem»SearchRescueServ ice

«EntityItem»SecondarySurv eillanceRadar

«EntityItem»SegmentLeg

«EntityItem»Service

«EntityItem»SignificantPointInAirspace

«EntityItem»SpecialDate

«EntityItem»SpecialNav igationStation

«EntityItem»SpecialNav igationSystem

«EntityItem»StandMarking

«EntityItem»StandardInstrumentArriv al

«EntityItem»StandardInstrumentDeparture

«EntityItem»StandardLev elColumn

«EntityItem»StandardLev elSector































31 of 45



Feature


«EntityItem»Surv eillanceGroundStation

«EntityItem»SurveillanceRadar

«EntityItem»Surv eyControlPoint

«EntityItem»TACAN

«EntityItem»TaxiHoldingPosition

«EntityItem»TaxiHoldingPositionLightSystem

«EntityItem»TaxiHoldingPositionMarking

«EntityItem»Taxiway

«EntityItem»TaxiwayElement

«EntityItem»TaxiwayLightSystem

«EntityItem»TaxiwayMarking

«EntityItem»TerminalArriv alArea

«EntityItem»TouchDownLiftOff

«EntityItem»TouchDownLiftOffLightSystem

«EntityItem»TouchDownLiftOffMarking

«EntityItem»TouchDownLiftOffSafeArea

«EntityItem»TrafficSeparationService

«EntityItem»Unit

«EntityItem»UnplannedHolding

«EntityItem»VOR

«EntityItem»VerticalStructure

«EntityItem»VisualGlideSlopeIndicator

«EntityItem»WorkArea





















5.1.3 DescribeStoredQueries Operation

5.1.3.1 Operation Functionality The DescribeStoredQueries operation provides detailed metadata (text of the query, parameters, returned features, …) about each stored query expression that a server offers.

A stored query is identified by an string identifier.


32 of 45


5.1.3.2 Operation Parameter The input parameter is called ListStoredQueriesRequest is defined fully in [10].

NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Describe Stored Queries ...


DescribeStoredQueriesRequest

«EntityItemAttribute»- storedQueryId :CharacterString [0..*]

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Describe Stored Queries RequestAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

Figure 18 NSOV-2 Describe Stored Queries Request

The response to the request is DescribeStoredQueriesResponse and is shown below:


33 of 45


NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Describe Stored Queries R...

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Describe Stored Queries ResponseAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM


DescribeStoredQueriesResponse

«EntityItemAttribute»- query :StoredQueryDescription [0..*]

«EntityItem»ISO 19142 WFS::StoredQueryDescription

«EntityItemAttribute»- abstract :CharacterString [0..*]- id :CharacterString- metadata :Any [0..*]- parameter :ParameterExpression [0..*]- queryExpressionText :QueryExpressionText [0..*]- title :CharacterString [0..*]


ParameterExpression

«EntityItemAttribute»- abstract :CharacterString [0..*]- metadata :Any [0..*]- name :CharacterString- title :CharacterString [0..*]- type :ScopedName

«EntityItem»ISO 19142 WFS::QueryExpressionText

«EntityItemAttribute»- any :Any [0..*]- language :Any- returnFeatureTypes :ScopedName [1..*]



+returnFeatureTypes«EntityItemAttribute»

1..*

+queryExpressionText«EntityItemAttribute»

0..*


+parameter«EntityItemAttribute»

0..*


+query«EntityItemAttribute» 0..*



34 of 45


Figure 19 NSOV-2 Describe Stored Queries Response

5.1.4 Operation listStoredQueries The ListStoredQueries operation lists the stored queries available at a server.

5.1.4.1 Operation Functionality The ListStoredQueries operation provides metadata (text of the query, parameters, returned features, …) about each stored query expression that a server offers.

A stored query is identified by an string identifier.

5.1.4.2 Operation Parameter The input parameter is called ListStoredQueriesRequest is defined fully in [10]. it supplies set of simple parameters requesting the set of pre-defined queries..

The output returned by the operation is called ListStoredQueriesResponse and is also defined fully in [10], it supplies details about each pre-defined query the service interface supports.

The input .parameter structure is shown below:

NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition List Stored Querie...


ListStoredQueriesRequest

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition List Stored Queries RequestAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

Figure 20: NSOV-2 Service Definition List Stored Queries Request

Mapping of this entityitem is not required as it is defined in the standard ISO19142.

The output parameter structure is shown in below:


35 of 45


NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition List Stored Queries Response

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition List Stored Queries ResponseAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«EntityItem»ISO 19142 WFS::ListStoredQueriesResponse

«EntityItemAttribute»- storedQuery :StoredQueryListItem [0..*]

«EntityItem»ISO 19142 WFS::StoredQueryListItem

«EntityItemAttribute»- id :CharacterString- returnFeatureType :ScopedName [1..*]- title :CharacterString [0..*]




StoredQueryId

+id«EntityItemAttribute» 1


+returnFeatureType«EntityItemAttribute»

1..*


+storedQuery«EntityItemAttribute»

0..* «EntityItemAttributeRelationship»

Figure 21: NSOV-2 Service Definition List Stored Queries Response


5.1.5 GetPropertyValue Operation The GetPropertyValue operation allows the value of a feature property or part of the value of a complex feature property to be retrieved from the data store for a set of features identified using a query expression.

5.1.5.1 Operation Functionality Query expressions are the same as in the GetFeature operation.

The GetPropertyValue response is a list of value.

5.1.5.2 Operation Parameter The input parameter is called getPropertyValueRequest is defined fully in [10].


36 of 45


NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Get Property Value R...

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Get Property Value RequestAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

«EntityItem»ISO 19142 WFS::GetPropertyValueRequest

«EntityItemAttribute»- query :QueryExpression- TracevalueReference :ValueReference

«EntityItem»ISO 19143 Filter::QueryExpression


AdhocQueryExpression

«EntityItemAttribute»- projection :Any [0..1]

«EntityItem»ISO 19142 WFS::StoredQuery

«EntityItemAttribute»- id :CharacterString

«EntityItem»ISO 19142 WFS::Query

«EntityItemAttribute»- projection :PropertyName [0..1]

«EntityItem»ISO 19142 WFS::Parameter

«EntityItemAttribute»- name :CharacterString- value :Any


PropertyName



«EntityItem»ISO 19143 Filter::ValueReference


Expression


+valueReference«EntityItemAttribute»

1

+projection

+parameter«EntityItemAttribute» 0..*




+query«EntityItemAttribute» 1



37 of 45


Figure 22 NSOV-2 Get Property Value Request

The response from the operation is the ValueCollection which is shown below:

NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Get Property Value Re...

«EntityItem»ISO 19142 WFS::ValueCollection

«EntityItemAttribute»- member :Any [0..*]

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Get Property Value ResponseAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

Figure 23 NSOV-2 Value Collection

5.1.6 Operation describeFeatureType

5.1.6.1 Operation Functionality The DescribeFeatureType operation returns a schema description of feature types offered by a WFS instance. The schema descriptions define how a WFS expects feature instances to be encoded on output (in response to a GetPropertyValue or GetFeature operation).

The schema use in this service is the AIXM 5.1 schema.

5.1.6.2 Operation Parameter The input parameter is called DescribeFeatureTypeRequest is defined fully in [10]. it supplies the feature type name to be described.

The output returned by the operation is called DescribeFeatureTypeResponse and is also defined fully in [10], it supplies details about each feature type requested, that the service interface supports.

The input .parameter structure is shown below:


38 of 45


NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Describe Feature Type R...

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Describe Feature Type RequestAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM


DescribeFeatureTypeRequest

«EntityItemAttribute»- outputFormat :CharacterString



+typeName«EntityItemAttribute» 0..*


Figure 24: NSOV-2 Service Definition Describe Feature Type Request


The output parameter structure is shown in below:

NSOV 2 SIPD NSOV-2 AeronauticalInformationFeature serv ice parameter type definition Describe Feature Type Re...


DescribeFeatureTypeResponse

«EntityItemAttribute»+ xmlSchema

Name: NSOV-2 AeronauticalInformationFeature service parameter type definition Describe Feature Type ResponseAuthor: 08.03.10 Les FoldsVersion: 1.0Created: 5/22/2014 12:00:00 AMUpdated: 5/22/2014 12:00:00 AM

Figure 25: NSOV-2 Service Definition Describe Feature Type Response



39 of 45


6 Service dynamic behaviour

6.1 Service Interface AeronauticalInformationFeature Include some information about the dynamic aspects of the service interface, each operation should be exposed perhaps involving more than one diagram.

NSOV-5c NSOV-5c AeronauticalInformationFeature serv ice ev ent trace description


«ServiceConsumer»AeronauticalInformationFeatureConsumer AeronauticalInformationFeatureInterface

GetCapabilities(request :GetCapabilitiesRequest) :WFS_Capabilities

DescribeFeatureType(request :DescribeFeatureTypeRequest) :DescribeFeatureTypeResponse

GetFeature(request :GetFeatureRequest) :FeatureCollection

GetPropertyValue(request :GetPropertyValueRequest) :ValueCollection

ListStoredQueries(request :ListStoredQueriesRequest) :ListStoredQueriesResponse

DescribeStoredQueries(request :DescribeStoredQueriesRequest) :DescribeStoredQueriesResponse

Figure 26: NSOV-5 Service Event Trace Description


40 of 45


7 Service provisioning (optional) The aeronautical information feature service is a service that provides the information stored in a AIM system. This system can be dedicated to the management of some aeronautical information only or can be a general purpose information system.

Two kinds of usage of the service have been presented in the Service Attributes (Quality of Service) chapter.

This service will be used by the Digital NOTAM sub-system from the AIM system to produce digital NOTAM that updates aeronautical information provided by the service.


41 of 45


8 Validation and Verification

8.1 Verification The verification based on the verification scripts provided by P8.3.10 has been used iteratively throughout the last part of the service modelling.

The output of the verification is given below: There are no automatic findings and all manual and semi-automatic findings have been checked and signed off.

Designed Services - AeronauticalInformat

8.2 Validation

This service will be validated in the EXE-8.3.3-502 (late 2012/early 2013) and EXE-8.3.3.-599 validation exercise in release 3.


42 of 45


9 References

Nr. Version Location

[1] FAA Web Service Description Document

2008-16-10 http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/techops/atc_comms_services/swim/documentation/media/briefings/WSDD%20FPS%20EXAMPLE%2008-16-10.pdf

[2] NATO Architecture Framework v3.0 & 3.1 http://www.nhqc3s.nato.int/

[3] SoaML 1.0 Beta 09-04-01

http://www.omg.org/spec/SoaML/

[4] SESAR European ATM Service Description Document template

01.00.00 https://extranet.sesarju.eu/Programme%20Library/SESAR%20European%20ATM%20Service%20Description%20Document.dot

[5] WP8 Internal workflow including modelling artefacts

00.00.22 https://extranet.sesarju.eu/WP_08/SWP_08.00/Other%20Documentation/WP8%20Internal%20Workflow/WP8%20Internal%20workflow%20including%20modelling%20artefacts.doc

[6] B 04 03 Working method on services (2nd Edition)

00.03.00 https://extranet.sesarju.eu/WP_B/Project_B.04.03/Project%20Plan/B_04_03-D46_Working_method_on_Services%20(2nd%20edition).doc

[7] B.04.03-D32-ADD Step 1 00.01.04 https://extranet.sesarju.eu/WP_B/Project_B.04.03/Project%20Plan/B.04.03-D32-ADD%20Step%201.doc

[8] ISO 19142:2010 Geographic information – Web feature service

2010 ISO

[9] ISO 19143:2010 Geographic information – Filter encoding

2010 ISO

[10] 13.2.2 D01 OSED for Step 1 01.00.02 https://extranet.sesarju.eu/WP_13/Project_13.02.02/Project%20Plan/Step1/Deliverables/DEL_13.02.02.D01_OSED.doc

[11] 08.03.03 D01 Identification of operational requirements for Step 1

00.02.00 https://extranet.sesarju.eu/WP_08/Project_08.03.03/Project%20Plan/P080303%20D01%20-%20Identification%20of%20Operational%20Requirements%20for%20Step%201%20v00%2002%2000.doc

[12] ATM Master Plan https://www.atmmasterplan.eu/http://prisme-oas.atmmasterplan.eu/atmmasterplan/face

http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/techops/atc_comms_services/swim/documentation/media/briefings/WSDD%20FPS%20EXAMPLE%2008-16-10.pdf





http://www.nhqc3s.nato.int/

http://www.omg.org/spec/SoaML/

https://extranet.sesarju.eu/Programme%20Library/SESAR%20European%20ATM%20Service%20Description%20Document.dot



https://extranet.sesarju.eu/WP_08/SWP_08.00/Other%20Documentation/WP8%20Internal%20Workflow/WP8%20Internal%20workflow%20including%20modelling%20artefacts.doc





https://extranet.sesarju.eu/WP_B/Project_B.04.03/Project%20Plan/B_04_03-D46_Working_method_on_Services%20(2nd%20edition).doc




https://extranet.sesarju.eu/WP_B/Project_B.04.03/Project%20Plan/B.04.03-D32-ADD%20Step%201.doc



https://extranet.sesarju.eu/WP_13/Project_13.02.02/Project%20Plan/Step1/Deliverables/DEL_13.02.02.D01_OSED.doc



https://extranet.sesarju.eu/WP_08/Project_08.03.03/Project%20Plan/P080303%20D01%20-%20Identification%20of%20Operational%20Requirements%20for%20Step%201%20v00%2002%2000.doc






https://www.atmmasterplan.eu/http:/prisme-oas.atmmasterplan.eu/atmmasterplan/faces/public/objectBrowser/browseEnabler.jspx




43 of 45


Nr. Version Location s/public/objectBrowser/browseEnabler.jspx

[13] ED-151 OPERATIONAL SERVICES AND ENVIRONMENT DEFINITION (OSED) FOR AERONAUTICAL INFORMATION SERVICES (AIS) AND METEOROLOGICAL (MET) DATA LINK SERVICES

December 2007

Eurocae

[14] SJU templates & guidelines package, Project deliverables template

03.00.00 https://extranet.sesarju.eu/Programme%20Library/Project%20deliverables%20template.dot

[15] SJU templates & guidelines package, OSED template

03.00.00 https://extranet.sesarju.eu/Programme%20Library/SESAR%20Operational%20Service%20and%20Environment%20Definition.dot

[16] SJU templates & guidelines package, SPR template

03.00.00 https://extranet.sesarju.eu/Programme%20Library/SESAR%20Safety%20and%20Performance%20Requirements.dot


https://extranet.sesarju.eu/Programme%20Library/Project%20deliverables%20template.dot



https://extranet.sesarju.eu/Programme%20Library/SESAR%20Operational%20Service%20and%20Environment%20Definition.dot



https://extranet.sesarju.eu/Programme%20Library/SESAR%20Safety%20and%20Performance%20Requirements.dot




44 of 45


Appendix A Physical interfaces The physical interfaces of this service can be found in those two archived files and is also available in the ISRM.

Figure 27: Artefacts

AIFS-interface.zip

AIXM 5.1-schema.zip

The physical interface has not been generated from the ISRM model because it was already existing as part of the ISO and the AIXM 5.1 standards.


45 of 45


-END OF DOCUMENT-

European ATM Service Description Document for the ... · D65 - European ATM Service Description Document for the Aeronautical Information Feature Service for the Aeronautical Information

Documents