Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Excerpt |
---|
This task will work on service categories in support of SWIM-SERV-009 Service categories. It will reflect the more flexible approach that will be adopted. |
Table of Contents |
---|
Published service category schemes
The current published service categories are at: https://reference.swim.aero/information-services/service-categories.html
Mature and can be published
-
Candidates for service category schemes
Potential service category | Notes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | service providers / organisation | See New: Best practices to harmonise content of service description fields
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 | quality of service | See New: Best practices to harmonise content of service description fields A classification of quality characteristics will be taken into account when evaluating the properties of a software product based on ISO/IEC 25010. See: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 for overview.
| Example performance includes:
|
performance efficiency - Capacity of a service | Degree to which the maximum limits of a product or system parameter meet requirements. | |
performance efficiency - Time behaviour of a service |
Example reliability includes:
Degree to which the response and processing times and throughput rates of a product or system, when performing its functions, meet requirements. | ||
reliability - Availability of a service | Degree to which a system, product or component is operational and accessible when required for use. | |
reliability - Recoverability of a service |
Example security includes:
Degree to which, in the event of an interruption or a failure, a product or system can recover the data directly affected and re-establish the desired state of the system. | ||
security - Confidentiality of a service | Degree to which a product or system ensures that data are accessible only to those authorized to have access. | |
security - Integrity of a service | Degree to which a system, product or component prevents unauthorized access to, or modification of, computer programs or data. |
See New: Best practices to harmonise content of service description fields
Service Category | Value | Definition |
---|---|---|
Information Exchange Model | ||
Aeronautical Information Exchange Model (AIXM) | ||
ICAO Meteorological Information Exchange Model (IWXXM) | ||
Flight Information Exchange Model (FIXM) | ||
Aerodrome Mapping Exchange Model (AMXM) |
See New: Best practices to harmonise content of service description fields
Service Category | Value | Definition |
---|---|---|
Data Format | ||
XML | ||
JSON | https://json-spec.readthedocs.io/reference.html | |
GRIB2 | https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/ | |
Protocol buffer | ||
HDF5 | http://codes.wmo.int/wmdr/DataFormat/hdf5 | |
ASN.1/XML |
This comes from the final version of the Information Service Overview fields - see Information Service Overviews Handbook v1.1.
Service Category | Value | Definition |
---|---|---|
Information security category | ||
None | ||
Basic | ||
Intermediate | ||
Advanced |
AIRM subjects (the packages within the AIRM also have URIs
This was raised in the context of datasets but is applicable to information service payloads in general and, e.g. tools like semantic NOTAM in particular. At the moment the packages are not published but should be. An AIRM change request has been raised.
The following table is an extract to show the potential result.
Service Category | Value | Definition |
---|---|---|
AIRM subject | Fields of specific knowledge. | |
AirspaceInfrastructure | Information about airspace volumes and infrastructure. | |
| Information about the routes and procedures designed for channelling the flow of traffic en-route and while departing and landing. | |
BaseInfrastructure | Information about the identity, location, description, and configuration of the infrastructure assets including physical facilities and systems, and obstacles. | |
| The aerodrome including any installations and equipment. |
This will build upon https://reference.swim.aero/information-services/service-categories/CodeLifeCycleStageType.html to cover other lifecycle stages e.g. draft and experimental.
Service Category | Value | Definition |
---|---|---|
Lifecycle Stage | ||
draft | ||
experimental |
The EATMA Service Overview organises the services by ATM Capability.
The first level is reflected in CodeBusinessActivityType. It is possible to add more levels from the ATM Capability Model. The table below includes the second level. Definitions are taken from https://www.eatmportal.eu/working/data/capabilities.
Service Category | Value | Definition |
---|---|---|
Aerodrome Operations | ||
| The provision of information to/or reception of information from airport landside with which airport airside interacts. | |
| The ability to know about the current state of airport facilities, traffic situation (vehicles, aircraft) and events at airport, and anticipate future changes and developments that may impact on aerodrome ATM operations. | |
| The ability to provide guidance and routing to aircraft and other vehicles moving on the surface of an aerodrome. | |
Airspace Organisation and Management | ||
| The ability to design airspace structures to accommodate the different types of air activity, volume of traffic, and differing levels of service and rules of conduct. | |
| The ability to maximise the use of a volume of airspace against the differing demands of users. | |
Airspace User Operations | ||
| The ability to determine and allocate priorities in which flights will be handled by the ATC system. | |
| The ability to execute Trajectory from TTA at origin or entry into ECAC Airspace to On Blocks at airport or exit from ECAC airspace. | |
Conflict Management | ||
| Separation of Airborne Aircraft from other Aircraft, Airspace Infringements, Weather, Terrain. | |
| The avoidance of collisions due to loss of separation of aircraft | |
CNS | ||
| The ability to make CNS assets/resources available in support of the ATM network, ensure scarce resources are equitably shared among stakeholders, and rationalise / optimise infrastructure (e.g. number of assets) and/or its usage when network performance is at stake. | |
| The ability to monitor and report on the performance of CNS infrastructure. | |
| The ability to combine and integrate Communication/Navigation/Surveillance techniques to deliver performance-based CNS services with required availability, integrity, safety, security requirements. | |
| - | |
| - | |
| - | |
Demand and Capacity Balancing | ||
| The ability to evaluate airport demand and adjust airport assets to allow airspace users to meet the needs of their operating schedules. | |
| The ability to evaluate traffic flows and adjust airspace resources to allow airspace users to meet the needs of their operating schedules. | |
Information Management | ||
| The ability to provide accredited, quality assured and timely aeronautical information in support of ATM operations. | |
| The ability to provide an information infrastructure (incl. support/utility services) which enables information exchanges through services. | |
| The provision of information to, or reception of information from other essential activities with which the ATM system interacts (e.g. search and rescue). | |
| The ability to provide accredited, quality assured and timely aeronautical information in support of ATM operations. | |
Service Delivery Management | ||
| The ability for all parties to collaborate and agree a flight trajectory based upon the users wishes, constraints and opportunities, and to manage conformance to trajectory agreement. | |
| The ability for all parties to collaborate and agree a flight trajectory based upon the users wishes, constraints and opportunities, and to manage conformance to trajectory agreement. | |
| The ability to set ATM performance requirements, and measure/monitor performance outcomes. | |
Traffic Synchronisation | ||
| The ability to sequence and merge traffic. |