| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Excerpt |
|---|
This task will work on service categories in support ofof: 009 . 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
Information domains as mentioned in the Information Service Overview in PANS-IM, ICAO
No service category or value has this status at the moment.
Candidates for service category schemes
CodeStakeholderType
| Status | ||||
|---|---|---|---|---|
|
Add a new value to CodeStakeholderType.
Service Category | Value | Definition |
|---|
The EATMA Service Overview organises the services by ATM Capability. The first level is reflected in CodeBusinessActivityType. It is possible to add more levels:
- Aerodrome Operations
Aerodrome Operations Management
Airport Situational Awareness Provision
Surface Guidance & Routing
Airspace Organisation and Management
Airspace Design
Airspace Management
Airspace User Operations
Flight prioritisation
Execute Trajectory
Conflict Management
Separation Management
Collision Avoidance
CNS
Communication
Navigation
Surveillance
Demand and Capacity Balancing
Demand and Capacity Balancing (airport)
Demand and Capacity Balancing (airspace)
Information Management
Aeronautical and Meteorological Information Management
Information Infrastructure Management
Information to/from Other Essential Services
ATM Data Management
Service Delivery Management
ATM Service Management
Trajectory Management
ATC Team Resource Management
- Traffic Synchronisation
Sequencing & Merging
Tasks
SWIM-SERV-009 will be updated to allow more flexible service categorisation.
URL |
|---|
http://reference.swim.aero/information-services/service-categories/CodeInformationDomainType
Flight information
(FLIGHT_INFORMATION)
#FLIGHT_INFORMATIONAeronautical information
(AERONAUTICAL_INFORMATION)
#AERONAUTICAL_INFORMATIONMeteorological information
(METEOROLOGICAL_INFORMATION)
#METEOROLOGICAL_INFORMATIONEnvironment information
(ENVIRONMENT_INFORMATION)
#ENVIRONMENT_INFORMATIONCapacity, demand and flow information
(CAPACITY_DEMAND_AND_FLOW_INFORMATION)
#CAPACITY_DEMAND_AND_FLOW_INFORMATIONSurveillance information
(SURVEILLANCE_INFORMATION)
#SURVEILLANCE_INFORMATIONOther information
(OTHER_INFORMATION)
#OTHER_INFORMATIONCandidates for service category schemes
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.
- RouteAndProcedure
- AerodromeInfrastructure
CodeStakeholderType | |||
OVERSIGHT_AUTHORITY | An entity or body responsible for monitoring, regulating, and ensuring compliance with laws, policies and standards within a particular field or organisation. |
ICAO regulated
| Status | ||||
|---|---|---|---|---|
|
Service Category | Value | Definition | URL |
|---|---|---|---|
CodeICAORegulationStatusType -> CodeICAOPublicationType | A categorisation of services based on the level of ICAO regulation. -> A categorisation of services based on the type of ICAO publication from which the operational need for the service can be derived. | ||
ANNEX | The service is aligned with statements found in an ICAO Annex. -> The operational need for the service is derived from an ICAO Annex. | ||
PANS | The operational need for the service is derived from an ICAO PANS. | ||
GUIDANCE | The operational need for the service is derived from an ICAO guidance document. |
lifecycle stage
| Status | ||||
|---|---|---|---|---|
|
This will build upon https://reference.swim.aero/
The schemes will be published in HTML format with a URL/URI.
We will also look to publish the schemes in an ontology language such as RDF.
We will write a "knowledge article" for the swim reference website. It will cover
- what they are,
- how to use them - These schemes can then be used in a service description, service definition or service overview.
- and why - show the application of the categories.
It should also make it clear that they categorisation schemes are separate from e.g. governance and compliance processes. It will explain how to use other sources of categorisation schemes e.g. semantics.aero.
The schemes will be evolved using SSCONE as the discussion forum.
to cover other lifecycle stages e.g. draft and experimental.
Service Category | Value | Definition | URL |
|---|---|---|---|
CodeLifeCycleStageType | |||
DRAFT | The status indicating that the service is... | ||
EXPERIMENTAL | The status indicating that the service uses new ideas or methods, and might be modified later if it is unsuccessful. It is made available in order to be assessed for future development. |
some values in different categories need to be logically explained
e.g. can you have a PROSPECTIVE SERVICE_DEFINITION or not? A matrix showing these sorts of business rules would be good to have.
provide examples of the typical exchanges that can be mapped to a given category e.g. what falls under “Capacity, demand and flow information”