service definitions

Reference requirements from CP1 and SDP

Owned by FERNANDEZ SANCHO Pedro

Last updated: 2022 May 30

<style></style><div class="cells-worksheet" data-sheet-number="0" data-sheet-name="Sheet1"><table border="0" cellpadding="0" cellspacing="0" style="border-collapse:collapse;table-layout:fixed;width:890pt"> <colgroup> <col class="x16" style="mso-width-source:userset;background:none;width:93px"></col> <col class="x16" style="mso-width-source:userset;background:none;width:81px"></col> <col class="x16" style="mso-width-source:userset;background:none;width:82px"></col> <col class="x16" style="mso-width-source:userset;background:none;width:330px"></col> <col class="x16" style="mso-width-source:userset;background:none;width:601px"></col> </colgroup> <tbody> <tr style="mso-height-source:userset;height:15pt" id="r0"> <td class="x18" style="height:13.5pt;width:69.75pt"><a name="_FilterDatabase"><span style="font-size:11pt;color:#000000;font-weight:700;text-decoration:none;text-line-through:none;font-family:"Calibri"">Req#</span></a></td> <td class="x18" style="width:60.75pt">Source</td> <td class="x18" style="width:61.5pt">Topic</td> <td class="x18" style="width:247.5pt">Title</td> <td class="x18" style="width:450.75pt">Text</td> </tr> <tr style="mso-height-source:userset;height:90pt" id="r1"> <td class="x17" style="height:88.5pt">A3SG-REF-001</td> <td class="x17">CP1/AF3</td> <td class="x17">AIM SWIM</td> <td class="x17">EAD R/T Aeronautical SWIM Services</td> <td class="x17">Centralised aeronautical information services (‘AIS’) systems, such as the European AIS Database (‘EAD’), must provide environment data for European FRA and for flexible airspace structures to all involved operational stakeholders in a timely manner - with the exception of ad hoc structures due to short-term requests/reservations – enabling planning based on accurate information relevant to the time of the planned operations. The information must be made available using available SWIM services set out in point 5.1.3.</td> </tr> <tr style="mso-height-source:userset;height:60pt" id="r2"> <td class="x17" style="height:58.5pt">A3SG-REF-002</td> <td class="x17">CP1/AF5.1.3</td> <td class="x17">AIFS</td> <td class="x17">Operational stakeholders R/T<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>AIFS</td> <td class="x17">Operational stakeholders must implement aeronautical information feature on request; filtering possible by feature type, name and an advanced filter with spatial, temporal and logical operators … that support the exchange of the aeronautical information… as described in the deployment programme</td> </tr> <tr style="mso-height-source:userset;height:30pt" id="r3"> <td class="x17" style="height:28.5pt">A3SG-REF-003</td> <td class="x17">CP1/AF5.1.3</td> <td class="x17">DNOTAM</td> <td class="x17">Operational stakeholders R/T digital NOTAM</td> <td class="x17">Operational stakeholders must implement... digital NOTAM… that support the exchange of the aeronautical information… as described in the deployment programme</td> </tr> <tr style="mso-height-source:userset;height:30pt" id="r4"> <td class="x17" style="height:28.5pt">A3SG-REF-004</td> <td class="x17">CP1/AF5.1.3</td> <td class="x17">Aero-Map</td> <td class="x17">Operational stakeholders R/T<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>aerodrome dig. charts</td> <td class="x17">Operational stakeholders must implement... digital aerodrome charts service… that support the exchange of the aeronautical information… as described in the deployment programme</td> </tr> <tr style="mso-height-source:userset;height:30pt" id="r5"> <td class="x17" style="height:28.5pt">A3SG-REF-005</td> <td class="x17">CP1/AF5.1.3</td> <td class="x17">AIM SWIM</td> <td class="x17">AIM services R/T SWIM Specs</td> <td class="x17">All the services listed in point 5.1.3 (AIM Services) must comply with applicable SWIM specifications</td> </tr> <tr style="mso-height-source:userset;height:30pt" id="r6"> <td class="x17" style="height:28.5pt">A3SG-REF-006</td> <td class="x17">CP1/AF5.1.3</td> <td class="x17">AIM SWIM</td> <td class="x17">AIM services R/T<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>Yellow Profile</td> <td class="x17">Operational stakeholders must implement (services listed in point 5.1.3)... using the SWIM yellow profile technical infrastructure </td> </tr> <tr style="mso-height-source:userset;height:45pt" id="r7"> <td class="x17" style="height:43.5pt">A3SG-REF-007</td> <td class="x17">CP1/AF5.1.3</td> <td class="x17">AIM SWIM</td> <td class="x17">ATM Systems R/T AIM Services</td> <td class="x17">ATM systems operated by stakeholders referred to in point 5.3 must have the capacity to use the aeronautical information exchange services including digital NOTAM. <br /></td> </tr> <tr style="mso-height-source:userset;height:45pt" id="r8"> <td class="x17" style="height:43.5pt">A3SG-REF-008</td> <td class="x17">CP1/AF5.1.3</td> <td class="x17">DNOTAM</td> <td class="x17">AIS Systems<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>R/T digital NOTAM</td> <td class="x17">AIS systems operated by the stakeholders referred to in point 5.2 must have the capacity to provide digital NOTAM in accordance with the Eurocontrol specification for improving the pre-flight information bulletins (PIB) services for the airports referred to in point 5.2.</td> </tr> <tr style="mso-height-source:userset;height:45pt" id="r9"> <td class="x17" style="height:43.5pt">A3SG-REF-009</td> <td class="x17">CP1/AF5.2</td> <td class="x17">AIM SWIM</td> <td class="x17">Stakeholders R/T AIM Services</td> <td class="x17">All the aeronautical information...exchanges must be implemented by all European area control centres, by the airports referred to in point 1.2, aeronautical information service provider and by the Network Manager</td> </tr> <tr style="mso-height-source:userset;height:15pt" id="r10"> <td class="x17" style="height:13.5pt">A3SG-REF-010</td> <td class="x17">CP1/AF5.3</td> <td class="x17">AIM SWIM</td> <td class="x17">SWIM Services Geographical Scope</td> <td class="x17">SWIM services must be deployed in the EATMN</td> </tr> <tr style="mso-height-source:userset;height:45pt" id="r11"> <td class="x17" style="height:43.5pt">A3SG-REF-011</td> <td class="x17">SDP/AF5</td> <td class="x17">SWIM</td> <td class="x17">SWIM Service Provider R/T CP1 scope</td> <td class="x17">Service Providers are required to deploy information services that ..<br />Enable the exchange of information in alignment with the intended scope, e.g. Scope as<br />identified in CP1 and further elaborated in the Deployment Programme</td> </tr> <tr style="mso-height-source:userset;height:45pt" id="r12"> <td class="x17" style="height:43.5pt">A3SG-REF-012</td> <td class="x17">SDP/AF5</td> <td class="x17">SWIM</td> <td class="x17">SWIM Service Provider R/T Yellow Profile</td> <td class="x17">Service Providers are required to deploy information services that ..<br />.Use communication protocols and implement infrastructure requirements as defined in<br />EUROCONTROL SWIM TI YP specification.</td> </tr> <tr style="mso-height-source:userset;height:30pt" id="r13"> <td class="x17" style="height:28.5pt">A3SG-REF-013</td> <td class="x17">SDP/AF5</td> <td class="x17">SWIM</td> <td class="x17">SWIM Service Provider R/T<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>Digital certificates</td> <td class="x17">Service Providers are required to deploy information services that ..<br />.In case confidentiality, integrity or authenticity is required, use digital certificates</td> </tr> <tr style="mso-height-source:userset;height:60pt" id="r14"> <td class="x17" style="height:58.5pt">A3SG-REF-014</td> <td class="x17">SDP/AF5</td> <td class="x17">SWIM</td> <td class="x17">SWIM Service Provider R/T service description</td> <td class="x17">Service Providers are required to deploy information services that ..<br />.Are described based on<br />o EUROCONTROL Service Description specification<br />o EUROCONTROL Information Definition specification</td> </tr> <tr style="mso-height-source:userset;height:60pt" id="r15"> <td class="x17" style="height:58.5pt">A3SG-REF-015</td> <td class="x17">SDP/AF5</td> <td class="x17">SWIM</td> <td class="x17">SWIM Service Provider R/T service definition</td> <td class="x17">Service Providers are required to deploy information services that ..<br />.Conform to published service definitions (if available and applicable)<br />o The service provider identifies whether applicable service definitions are publicised in<br />the SWIM Registry and adapts its implementation to conform to this if needed.</td> </tr> <tr style="mso-height-source:userset;height:30pt" id="r16"> <td class="x17" style="height:28.5pt">A3SG-REF-016</td> <td class="x17">SDP/AF5</td> <td class="x17">SWIM</td> <td class="x17">SWIM Service Provider R/T service registry</td> <td class="x17">Service Providers are required to deploy information services that ..<br />.Are publicised in the SWIM Service Registry.</td> </tr> <tr style="mso-height-source:userset;height:75pt" id="r17"> <td class="x17" style="height:73.5pt">A3SG-REF-017</td> <td class="x17">SDP/AF5</td> <td class="x17">SWIM</td> <td class="x17">SWIM Service Consumer R/T scope</td> <td class="x17">Service Consumers are required to consume from information services that:<br />• Enable the exchange of information in alignment with the intended scope<br />• e.g. Scope as identified in CP1 and further elaborated in the following sections of Deployment<br />Programme</td> </tr> <tr style="mso-height-source:userset;height:15pt" id="r18"> <td class="x17" style="height:13.5pt">A3SG-REF-018</td> <td class="x17">SDP/AF5.3</td> <td class="x17">AIFS</td> <td class="x17">AIFS purpose</td> <td class="x17">This service supports consumption of published AIP and AIP SUP data</td> </tr> <tr style="mso-height-source:userset;height:60pt" id="r19"> <td class="x17" style="height:58.5pt">A3SG-REF-019</td> <td class="x17">SDP/AF5.3</td> <td class="x17">AIFS</td> <td class="x17">AIFS roles</td> <td class="x17">The aeronautical information feature exchange shall be implemented by:<br />• AISPs that are the primary provider of the service34<br />• Airports when aerodrome information is provided by an Airport<br />• AUs, ANSPs that are the primary consumers of the service and the information it provides</td> </tr> <tr style="mso-height-source:userset;height:90pt" id="r20"> <td class="x17" style="height:88.5pt">A3SG-REF-020</td> <td class="x17">SDP/AF5.3</td> <td class="x17">AIFS</td> <td class="x17">AIFS functionality</td> <td class="x17">The provider of the aeronautical information feature service ensures that systems implementing the service:<br />• Shall allow the retrieval of aeronautical information features.<br />• May enable filtering by feature type and name.<br />• May allow advanced filtering based on spatial, temporal and logical operators.<br /></td> </tr> <tr style="mso-height-source:userset;height:60pt" id="r21"> <td class="x17" style="height:58.5pt">A3SG-REF-021</td> <td class="x17">SDP/AF5.3</td> <td class="x17">AIFS</td> <td class="x17">AIFS technical aspects</td> <td class="x17">The provider of the aeronautical information feature service ensures that systems implementing the service:<br /><br />• Shall provide the output expressed in the applicable version of AIXM.</td> </tr> <tr style="mso-height-source:userset;height:90pt" id="r22"> <td class="x17" style="height:88.5pt">A3SG-REF-022</td> <td class="x17">SDP/AF5.3</td> <td class="x17">Aero-Map</td> <td class="x17">Aerodrome Mapping Service roles</td> <td class="x17">The Aerodrome Mapping information exchange shall be implemented by:<br />•<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>Airports are primary data provider supporting Aerodrome mapping service. <br />•<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>AISPs are the primary provider of the service. (Airport operators providing aeronautical information services qualify as AISP)<br />• AUs that are the recommended primary consumers of the service and the information it<br />provides</td> </tr> <tr style="mso-height-source:userset;height:60pt" id="r23"> <td class="x17" style="height:58.5pt">A3SG-REF-023</td> <td class="x17">SDP/AF5.3</td> <td class="x17">Aero-Map</td> <td class="x17">Aerodrome Mapping Service functionality</td> <td class="x17">The provider of the Aerodrome Mapping Service ensures that systems implementing the service:<br />• Shall allow selecting aerodrome features and maps as GIS layers.<br />• May allow information filtering with spatial, temporal and logical operators.</td> </tr> <tr style="mso-height-source:userset;height:105pt" id="r24"> <td class="x17" style="height:103.5pt">A3SG-REF-024</td> <td class="x17">SDP/AF5.3</td> <td class="x17">Aero-Map</td> <td class="x17">Aerodrome Mapping Service technical aspects</td> <td class="x17">The provider of the Aerodrome Mapping Service ensures that systems implementing the service:<br />• Shall output data in formats which are based on Open Geospatial Consortium standards<br />(e.g. simple GML features, SHAPE files, GeoJSON)<br />• May be based on the AMXM to facilitate GIS integration. Using AMXM will satisfy the related<br />EUROCAE WG-44 Industry standards in terms of data format as referenced in Annex</td> </tr> <tr style="mso-height-source:userset;height:75pt" id="r25"> <td class="x17" style="height:73.5pt">A3SG-REF-025</td> <td class="x17">SDP/AF5.3</td> <td class="x17">DNOTAM</td> <td class="x17">Digital NOTAM Service roles</td> <td class="x17">The Digital NOTAM information exchange shall be implemented by:<br />• AISPs that are the intended provider of the service<br />• Airports that are the originator of the event data<br />• ANSPs (pre-flight bulletin) that are the intended consumers of the service and the information it provides</td> </tr> <tr style="mso-height-source:userset;height:30pt" id="r26"> <td class="x17" style="height:28.5pt">A3SG-REF-026</td> <td class="x17">SDP/AF5.3</td> <td class="x17">DNOTAM</td> <td class="x17">Digital NOTAM Service functionality</td> <td class="x17">The provider of the Digital NOTAM Service ensures that systems implementing the service:<br />• Shall enable the sharing of various event information</td> </tr> <tr style="mso-height-source:userset;height:45pt" id="r27"> <td class="x17" style="height:43.5pt">A3SG-REF-027</td> <td class="x17">SDP/AF5.3</td> <td class="x17">DNOTAM</td> <td class="x17">Digital NOTAM Service technical aspects</td> <td class="x17">The provider of the Digital NOTAM Service ensures that systems implementing the service:<br />• Shall conform to EUROCONTROL Digital NOTAM specification<br />• Shall output event information encoded in AIXM 5.1.1</td> </tr> <tr style="mso-height-source:userset;height:45pt" id="r28"> <td class="x17" style="height:43.5pt">A3SG-REF-028</td> <td class="x17">SDP/AF5.3</td> <td class="x17">Aero-Map</td> <td class="x17">Aerodrome Mapping Service Information</td> <td class="x17"> Digital Aerodrome Map can be used to present actual/real-time information about closure of runway, taxiway, work in progress on aerodrome movement area, temporary erected obstacles.</td> </tr> <tr style="mso-height-source:userset;height:75pt" id="r29"> <td class="x17" style="height:73.5pt">A3SG-REF-029</td> <td class="x17">CP1/AF1.2</td> <td class="x17">Scope</td> <td class="x17">Major airports</td> <td class="x17">Adolfo Suarez Madrid-Barajas; Amsterdam Schiphol; Barcelona El Prat; Berlin Brandenburg Airport; Brussels National; Copenhagen Kastrup; Dublin; Düsseldorf International; Frankfurt International; Milan-Malpensa; Munich Franz Josef Strauss; Nice Cote d’Azur; Palma De Mallorca Son Sant Joan; Paris-CDG;<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>Paris-Orly;<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>Rome-Fiumicino;<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>Stockholm-Arlanda;<span style="mso-spacerun:yes;font-family:"Times New Roman""> </span>Vienna Schwechat;</td> </tr> <tr style="display:none"> <td style="width:69.75pt"></td> <td style="width:60.75pt"></td> <td style="width:61.5pt"></td> <td style="width:247.5pt"></td> <td style="width:450.75pt"></td> </tr> </tbody></table></div>