| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Info | |||||
|---|---|---|---|---|---|
The following text will form the new supporting material once agreed.
|
| Table of Contents |
|---|
Introduction
The Information Service Overview is introduced in the ICAO Procedures for Air Navigation Services – Information Management (PANS-IM, Doc 10199).
An information service provider shall provide an information service overview for each version of each information service. The information service overview is "A set of information service metadata intended to promote information service discovery and an initial evaluation of the information service characteristics". As such, it enables information service consumers to compare between different information services.
| Tip | ||
|---|---|---|
| ||
|
Glossary
| Term | Definition |
|---|---|
| Service overview | A set of information service metadata intended to promote service discovery and an initial evaluation of the information service characteristics. |
| Operational (status of a service) | The status indicating that the service is employed in its operational environment. |
| Prospective (status of a service) | The status indicating that the service is being designed, developed, or tested for operational activities and is expected to be available in the future. |
Requirements for information service overviews
PANS-IM states that:
- Information service providers shall provide information service metadata through information service overviews.
- Information service overviews shall be structured using the metadata fields in Table 5-1. This practice facilitates discoverability of information services and enables information service consumers to compare different information services.
- Information service providers shall provide a complete description of all metadata fields in the information service overview for each version of an information service.
- Information service providers shall inform consumers where they can access the information service overviews and the metadata on information services therein.
- The uniform resource locator (URL) where information service overviews are publicized shall be included in the AIP. In case a SWIM registry is used (see 5.4), the URL shall be the one of the registry.
Content of an information service overview
The content of an information service overview is outlined in Table 5-1 of the PANS-IM. Each field must be completed (using "NIL" where allowable and applicable.)
The following table provides supporting material for the content. It:
- details the required content (field) of an information service overview.
- includes the requirements for the field based on the PANS-IM and the field schema.
- provides an example of the expected content based on Donlon.
- provides the relationship to the relevant requirement in the SWIM Service Description Specification. This shows how the content of a service description can be used to create a service overview.
| Information Service Overview Field Name | Information Service Overview Requirements | Relationship of the requirement to EUROCONTROL Specification for SWIM Service Description Edition 2.0 | Field schema | Example Content - Based on Donlon | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Information service name | Information service providers shall name the information service. | Free text | Donlon TargetOffBlockTimeSetting Service | ||||||||
| The name of the information service should enable information service consumers to reference or identify the information service. |
| ||||||||||
| The name should provide an indication of the purpose of the information service. |
| ||||||||||
| Information service version | Information service providers shall provide versioning to the information services. | SWIM-SERV-040 Service identification:
| n.n[.n] | 1.0.0 | |||||||
| The service version shall be provided in numerical format (n.n[.n]). |
| ||||||||||
| The version of the information service shall allow information service consumers to distinguish between versions of an information service. |
| ||||||||||
| Information service life cycle status | Information service providers shall specify the stage that the information service version is currently in as one of three stages: prospective, operational or retired. Note.⸻ For more information on service stages see Doc 10203. | SWIM-SERV-110 Service lifecycle information
The values are available at: https://reference.swim.aero/information-services/service-categories/CodeLifeCycleStageType.html | Prospective or Operational or Retired | OPERATIONAL | |||||||
| Note.⸻ For more information on service stages see Doc 10203. | |||||||||||
| Information service life cycle date | Information service providers should include the dates for current and future lifecycle stages. | YYYY-MM-DD or NIL | 2018-07-31 | ||||||||
| The planned date of retirement should be listed whenever it is known to exist. | |||||||||||
| If an information service provider does not make the date available, the information service life cycle date metadata field shall specify “NIL”. |
| ||||||||||
| Note.⸻ In the case of a prospective stage, the date indicates the date by which the information service provider plans to make the information service operational. | |||||||||||
| Information service functions | Information service providers should provide a description of the business level characteristics of the information service functions. This will provide information service consumers a business view of the interactions with the information service, without having to look at the interface details. | covered by rationale to SWIM-SERV-140 Service functions | Free text or NIL |
| |||||||
| The description should include the functionality of the service as a list of the functions and real world effects. | SWIM-SERV-140 Service functions
| ||||||||||
| If an information service provider does not make the information service functions available, the information service functions metadata field shall specify “NIL”. |
| ||||||||||
| Information category | The information domain(s) covered by the information service shall be listed as one or more of the following: a) flight information; b) aeronautical information; c) meteorological information; d) environment information; e) capacity, demand and flow information; f) surveillance information; and/or g) other information. | SWIM-SERV-100 Service categories allows this to be added in conjunction with https://reference.swim.aero/information-services/service-categories/CodeInformationDomainType.html | Flight information; and/or Aeronautical information and/or Meteorological information and/or Environment information and/or Capacity, demand and flow information and/or Surveillance information and/or Other information | FLIGHT INFORMATION | |||||||
| Brief description of the information service | Information service providers shall provide a brief description of the information service to assist information service consumers on whether the described service is suitable for use in a particular situation. The brief description shall include the information domain(s) covered by the information service, the operational need being addressed by the information service, the intended use of the information service, and the intended consumer audience for the information service. |
| Info |
|---|
The content can be mapped to other parts such as
|
The TargetOffBlockTimeSetting service supports flight information exchange by allowing aircraft operators and ground handlers to set the Target Off-Block Time (TOBT) for their flight departures at Donlon Airport.
The service may be used by the Donlon Tower Controllers in specific circumstances, such as under adverse conditions or other special circumstances.
The service is part of a set of services supporting the Airport Collaborative Decision Making (A-CDM) concept and its implementation by providing the A-CDM partners with common situation awareness about flights at a CDM airport.
--
The TargetOffBlockTimeSetting service supports the Airport Collaborative Decision Making (A-CDM) concept and its implementation by allowing A-CDM Partners, typically aircraft operators and ground handlers, with the capability to set TOBT that indicates the target time for the aircraft to be ready for off-block.
The TargetOffBlockTimeSetting service supports flight information exchange by allowing aircraft operators and ground handlers to set the Target Off-Block Time (TOBT) for their flight departures at Donlon Airport.
The service may be used by the Donlon Tower Controllers in specific circumstances, such as under adverse conditions or other special circumstances.
The service is part of a set of services supporting the Airport Collaborative Decision Making (A-CDM) concept and its implementation by providing the A-CDM partners with common situation awareness about flights at a CDM airport.
- the note to SWIM-SERV-050 Service abstract covers the items that are best practice to include.
| Info |
|---|
The content can be mapped to other parts such as
|
Information service providers should provide a description of the location at which more information, potentially including more detailed technical information on an information service, may be found.
| Info |
|---|
The use of NIL is not outlined in the specification. |
Information service providers shall provide a description on the qualitative and quantitative information pertaining to the characteristics of an information service to allow information service consumers to understand the quality of the information service.
The description should specify parameters based on ISO 25010.
The quality of the information service should be expressed using the following parameters (or other applicable parameters):
a) performance parameters (quantitative);
i) capacity of a service;
ii) time behaviour of a service;
b) reliability parameters (quantitative);
i) availability of a service;
ii) recoverability of a service;
c) security parameters (qualitative);
i) confidentiality of a service; and/or
ii) integrity of a service.
Note.⸻ Examples of applicable parameters related to performance, reliability and security are provided in Doc 10203.SWIM-SERV-180
- the requirement covers the top level parameter
- the notes cover the sub-parameters e.g. capacity...
SWIM-SERV-180 Quality of service
- the requirement covers the top level parameter
- the notes cover the sub-parameters e.g. capacity...
- Availability: 99.95 % outside the planned outages
- Capacity: 2000 service requests per hour
- Time behaviour: 2s delay for 95% of messages
| Info |
|---|
| ISO 25010 is mentioned in the notes. |
- Availability: 99.95 % outside the planned outages
- Capacity: 2000 service requests per hour
- Time behaviour: 2s delay for 95% of messages
--
AVAILABILITY: 99.95 % outside the planned outagesCAPACITY: 2 000 service requests per hour
TIME BEHAVIOUR: 2 s delay for 95 % of messages
The quality of the information service should be expressed using the following parameters (or other applicable parameters):
a) performance parameters (quantitative);
i) capacity of a service;
ii) time behaviour of a service;
b) reliability parameters (quantitative);
i) availability of a service;
ii) recoverability of a service;
c) security parameters (qualitative);
i) confidentiality of a service; and/or
ii) integrity of a service.
Information service providers shall ensure that the information service is validated.
This validation shall include the parameters provided in the quality of service metadata field of the information service overview to assist information service consumers with the initial evaluation of the information service.
Information services shall be validated by at least one of the following validation methods:
a) independent validation;
b) collaborative validation;
c) user validation; or
d) self-validation.
The validation method(s) used and its corresponding result shall be recorded.
Information services may evolve which triggers the need for revalidation. Each new version of an information service should be revalidated.
Note.⸻ For more information on the validation methods see Doc 10203.
SWIM-SERV-200
| Info |
|---|
Obviously the spec does not mandate that services shall be validated as this is a governance/process aspect. Instead the specification requests a description of what was done. |
- quality of service is covered by the requirement
| Info |
|---|
| The spec does not specify what methods to use as this is process related. The methods are given as a best practice in the notes. |
| Info |
|---|
the evolution aspect is not covered by the specification. |
Information service providers shall provide a description of the validation method applied to assist information service consumers in assessing the confidence
level of the information service.
Donlon Airport tested the service in accordance with its quality management system (QMS) based requirements.
The validation was successful.
To obtain the validation evidence, contact the Service desk [24/7]: +693 555 01 service-desk@donlon-airport.com
The description should include a brief statement on the validation results, and it should describe how the information service consumers may obtain the validation evidence.
SWIM-SERV-200
| Info |
|---|
The reassurance is covered in the rationale |
Donlon Airport tested the service in accordance with its quality management system (QMS) based requirements.
The validation was successful.
- validation results
- obtaining evidence
Information service providers should provide information on the availability of filtering to allow information service consumers to narrow the content of information
that they consume.
The service consumer can filter information feed based on time.
Note: the information provided by the service is limited to DONLON (see Geographical extent of information) so there is no need for a geospatial filter in this case.
SWIM-SERV-310
- filter encoding
| Info |
|---|
The use of NIL is not outlined in the specification. |
The service consumer can filter information feed based on time.
Note: the information provided by the service is limited to DONLON (see Geographical extent of information) so there is no need for a geospatial filter in this case| Info |
|---|
The use of NIL is not outlined in the specification. |
Information service providers shall provide a description of any constraints on access
to
the information service
to assist information service consumers
in understanding whether they may be eligible to access the information
service
.
SWIM-SERV-150 and SWIM-SERV-160
The access to the service is subject to authorization. Authorization is dependent on formal arrangements (Service Level Agreement) with the Donlon Airport Operator.
The access to the service is subject to authentication based on the user id and password for authorized users.
Information service providers shall indicate the message exchange pattern used by the information service to assist information service consumers in understanding the relationships of multiple messages exchanged with the information
a) request/reply;
b) one way; and/or
c) publish/subscribe
service providers.
SWIM-SERV-210
| Info |
|---|
| The types are covered in the notes to the requirement. This is a design requirement and not covered in the service description spec, |
a) request/reply;
b) one way; and/or
c) publish/subscribe.
If information service providers use for their information service payloads the domain specific information exchange models, then information service providers shall indicate the domain-specific information exchange models used for their information service payloads, including
the extensions of the information exchange models and their versions.
Information service providers shall provide a description of the geographical coverage of the information exchanged to allow information service consumers to understand the geographical coverage of the information being provided.
SWIM-SERV-090
Information service providers should specify the sources of information exchanged.
SWIM-SERV-190
| Info |
|---|
The use of NIL is not outlined in the specification. |
Information security category
Information service providers shall indicate the information security category
The information security category shall be expressed as one of the following:
a) none;
b) basic;
c) intermediate; or
d) advanced.
to provide information service consumers with an understanding of the level of protection of the information.
Draft PANS -
6.1.3 Organizations shall implement an information security framework to ensure the confidentiality (when needed), integrity and availability of the information and information services.
6.3.5.1 Assessing the impact of information security on safety risk management requires the classification of the information to be exchanged in information security categories. Based on the applicable information security category, information service providers and consumers shall apply the performance-based information security requirements in Appendix A to information systems handling the information.
6.3.5.2 Information service providers shall state the information security category in the Quality of the service metadata field of the information service overview to provide information service consumers with an understanding of the level of protection of the information.
Appendix B 1.3.
Organizations shall categorize information and information systems under their responsibility based on the information security impact on safety risk analysis. Organizations shall also review categories on a periodic basis based on the risk analysis.
Basic - Information and information systems shall be categorized based on the information security impact on safety risk analysis. Information security categories shall be reviewed every (2) years based on the latest risk analysis.Basic
Intermediate - Information and information systems shall be categorized based on the information security impact on safety risk analysis. Information security categories shall be reviewed every (2) years annually based on the latest risk analysis.
Intermediate Advanced - Information and information systems shall be categorized based on the information security impact on safety risk analysis. Information security categories shall be reviewed annually monthly based on the latest risk analysis.
Advanced - Information and information systems shall be categorized based on the information security impact on safety risk analysis. Information security categories shall be reviewed monthly based on the latest risk analysis.
Intermediate
Intermediate
a) none;
b) basic;
c) intermediate; or
d) advanced.
Information service providers shall provide the name of their organization to assist information service consumers in identifying and gaining context on the information service.
Information service providers should provide a description of the support offered to information service consumers on all relevant aspects related to the information service, to allow information service consumers to understand the level of support to expect.
If an information service provider does not make support availability information available, the support availability metadata field shall specify “NO SUPPORT AVAILABLE”.
Information service consumers should have a point of contact to request, if needed, additional information regarding an information service.
Information service providers shall provide a point of contact such as an email or website where a potential information service consumer can direct additional questions regarding the information service.
SWIM-SERV-070
To request access to the service: http://www.donlon-airport.com/swim/service-request
Creating an information service overview
An information service overview can be created:
- using a template based on the table above
- using the Service Metadata Schema
- as the service overview should not rely on a schema, the service metadata schema is only informative.
- from the content an existing service description.