Date: Fri, 29 Mar 2024 08:50:52 +0000 (UTC) Message-ID: <904166073.278.1711702252096@pmtpub41.ops.cfmu.eurocontrol.be> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_277_107785028.1711702252096" ------=_Part_277_107785028.1711702252096 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Status
This page is based on draft material and will be updated when ICAO accep= ts the PANS-(SW)IM. This is expected to happen in Q3 2021.
In the context of the anticipated PANS-IM, a requirement is expected for= information about global information services to be made available. For th= e purpose a Service Overview is defined as: =E2=80=9Ca set of information s= ervice metadata intended to promote service discovery and an i= nitial evaluation of the information service characteristics.=
Service providers use Service Overviews to publicise an operational serv= ice or prospective service, the latter announcing its future availability. = This information allows information service consumers to discover informati= on services.
Good to know
The Service Orientation= Process considers the Service Overview as an outcome of the design ste= p (the service has "prospective" status). It is then updated during the imp= lementation step and completed at deployment (the service has "operational"= status).
Field |
Mandatory/ Optional |
Explanation of Field |
---|---|---|
Service Name |
Mandatory |
The Service Name is a piece of= identifying information that gives stakeholders a way to reference or iden= tify a service. |
Service Version |
Mandatory |
The Service Version distinguis= hes which release of the service the information in the overview pertains t= o. |
Provider Organization |
Mandatory |
The name of the organization r= esponsible for provision of the information service. |
Brief Description of the Service
|
Mandatory |
A brief summary of the service= offering. |
Provider Point of Contact |
Mandatory |
A point of contact for the pro= vider organization for the specific service. |
Additional Service Information |
Optional |
Location at which more informa= tion, potentially including more detailed technical information, on a servi= ce may be found. |
Lifecycle Information |
Mandatory |
Indication of which phase of t= he service development lifecycle the service is in as well as lifecycle tim= eline. |
Geographical Extent of Information |
Mandatory |
Details of the geographic cove= rage of the information provided by the service. |
Quality of Service |
Mandatory |
Qualitative and quantitative information pert= aining to the performance characteristics of a service. |
Access Restrictions |
Mandatory |
A description of any constrain= ts on access to the service |
Message Exchange Pattern |
Mandatory |
The Message Exchange Pattern u= sed by the service. |
Exchange Models |
Mandatory |
The exchange models adhered to= by the service. |
Service Functions |
Optional |
A business-level description o= f the service functions. |
Filtering Available |
Optional |
An overview of which filters t= he provider offers to the consumer for the service. |
Sources of Information |
Optional |
A description of the origins o= f information provided by the service along with an indication whether ther= e were any subsequent modifications. |
Support Availability |
Optional |
An overview of whether any ser= vice support may be offered to consumers. |
Service Validation |
Mandatory |
Method of validation used to a= ssess a service. |
Donlon TOBT Setting Service Overview - fictitious example.