| Insert excerpt |
|---|
| Task Status |
|---|
| Task Status |
|---|
| nopanel | true |
|---|
|
task will:update the supporting material for page manages activities related to service overviews. |
consider a service overview as a subset of a service description → ensure that the requirements for service overview are covered in the Service Description specification consider what the Registry should implement in terms of service overviews| Info |
|---|
The relationships between service overviews, service definitions and service descriptions is discussed on the |
Service DefinitionsCurrent supporting material
Previously it was agreed to consider a service overview as a subset of a service description. → Consider using a service would map to initial evaluation. Otherwise said a service overview is the part of a service description required by ICAO. It also means that providing a service description would meet the service overview requirement. Another consideration is what the Registry will implement in terms of service overviews. For SSCONE the target should be to ensure that the requirements for service overview are covered in the specification.
New supporting material
| Info |
|---|
The following text will form the new supporting material once agreed. |
Introduction
The Service Overview is introduced in ICAO PANS-IM...
Expected content
The following table explains what a service overview contains. It also provided the relevant Service Metadata Schema field that can be used to fulfil the content.
| Field Name | Requirements | Mapping to Service Description | Notes |
|---|
Information service name | Information service providers shall name the information 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 of the information services. 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 lifecycle status | Information service providers shall specify the stage that the information service version is currently in as one of the three phases: Prospective, Operational or Retired. The Lifecyle Information metadata filed may be represented through free-text or a table. | Information service lifecycle date | Information service providers should include the dates for current and future lifecycle stages. 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 lifecycle date metadata field shall specify "NIL".
Note - In the case of prospective stage, the date indicates the date by which 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 to assist information service consumers with a business view of the interactions with the information service, without having to look at the interface details. The description should include the functionality of the service as a list of functions and real-world effects. If an information service provider does not make the information service functions available, the 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; and/or
b) Aeronautical information; and/or
c) Meteorological information; and/or
d) Environement information; and/or
e) Capacity, demand & flow information; and/or
f) Surveillance information; and/or
g) Other information | Brief description of the information service | Information service providers shall provide a brief summary description of the information service to assist the information service consumers on whether the described service is suitable for use in a particular situation. The brief summary 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. | Additional information of the information service | 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. The location should be provided as a link to where an information service consumer can find more information. If an information service provider does not make the additional information available on the information service overview, the Additional Service Information metadata field shall specify "NIL". | Quality of the service | Information service providers shall provide a description on the qualitative and quantitative information pertaining to the characteristics of the information service to allow information service consumers 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 parameter (or other applicable parameter):
Performance parameters (quantitative)
- Capacity of a service
- Time behaviour of a service
Reliability parameters (quantitative)
- Availability of a service
- Recoverability of a service
Security parameters (qualitative)
- Confidentiality of a service
- Integrity of a service
Note - Examples of applicable parameters related to performance, reliability and security is provided in the Manual om Implementation of System-wide Information Management (Doc...) | Information service validation type | Information service providers shall ensure that the information service is validated. The 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 intitial 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 re-validated. | Information service validation description | Information service providers shall provide a description of the validation method applied to assist information service consumers assess the confidence level of the information service. By sharing the validation results, information service providers reassure information service consumers that the information service and its provider have the ability to deliver the declared capabilities and quality of service. The description should include a brief statement on the validation results, and how the information service consumers may obtain the validation evidence. | Filtering available | Information service providers should provide information on the availability of filtering capability to allow the information service consumers to narrow the content of the information that they consume. The capability of filtering information should describe the filters information service providers offer for an information service. If an information service provider does not offer filtering or does not make the filtering information available on the service overview, the Filtering Available metadata field shall specify "NIL". | Access restrictions | Information service providers shall provide a description of any constraints on the access to the information service to assist information service consumers in understanding whether they may be legible to access the information service. These constraints should specify the requirements and/or restrictions on information service consumers for accessing the information exchanged by the information services that are considered to be sensitive. | Message exchange pattern | Information service providers shall indicate the message exchange pattern used by the information service to assist information service consumers understand relationships of multiple message exchanges with the information service providers. The message exchange pattern shall be expressed as one of the following:
a. request/reply or
b. one way or
c. publish/subscribe | Information exchange model | 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. If information service providers do not use the domain-specific information exchange models for their information service payloads, then information service providers shall describe the alignment to the AIRM and indicate the exchange schema used. | Geographical extent of information | Information service providers shall provide a description of the geographical coverage of the information exchanged to allow information service consumers understand the geographical coverage of the information being provided.
Note: The geographical coverage may be expressed in terms such as of ICAO region, FIR, Aerodrome or polygon. More granular information such as coverage at Airport X, FIR Y may be provided as it may facilitate search responses.Source of information | Information service providers should specify the sources of information exchanged. Information service providers should also provide information on any subsequent modifications applied in order to provide information service consumers with background on information sources and modifications. If an information service provider does not make the source of information available, the Source of Information metadata field shall specify "NIL". | Provider organization | Information service providers shall provide the name of their organization to assist information service consumers in identifying and gaining context on the information service. The name of the organization shall be followed by any abbreviated name, if any, by which the organisation is known. | Support Availability | 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 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". | Provider Point of Contact | 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 as an email or website where a potential service consumer can direct additional questions regarding the information service. | Example
Here is an example...
Note that no schema is provided by ICAO. The service overview is a presentation of information