1. Building SWIM B2B web services
using Open Standards
Debbie Wilson
Snowflake Software

2. The Problem
• Development of SWIM is going to be complex and time
consuming
• To realise the benefits, organisations need to freely
exchange ATM data in a interoperable manner
– Both within and outside the industry
• The AIRM and ISRM provide the conceptual blueprint
– Data exchange models (AIRM)
– Service operations (ISRM)
• SWIM must be developing using Open Standards:
– OGC/ISO
– W3C

3. Prototype Primary Goals
• Reduce costs of creating and consuming SWIM services
– Replicate the NOP B2B Airspace Activation services
• OGC web services backbone
• Provide flexible, open API
• Chain tailored services for specific ATM application
• Pave the way for „model driven‟ service creation from the ISRM
• Encourage a dynamic eco-system around ATM data
– Demonstrate multiple ways of deploying NOP services
• One logical service, many implementations
• Implementations designed for communities consuming them
• Demonstrate the benefits of existing open standards

4. Data Maintenance Data Publication
SESAR SWIM
B2B Airspace
Service
Airspace Airspace Flight ATM
Management Design Planning Viewer
SWIM
Master Class EAUP CDR/RSA
Download Java Request/Response
Client
RESTful SWIM NOP
Services Services
WFS Filter
WFS Stored Queries
Query
EAUP CDR/RSA OGC WFS 2.0
AIXM 5.1 Response
Oracle 11g
Express Edition

5. Data Maintenance Architecture
SESAR SWIM • The prototype connected to the EAUP
B2B Airspace
Service Condition Routes (CDR) and Restricted
Airspace (RSA) web services
SWIM
Master Class • A custom Java client was developed to
Download Java connect to the B2B Services
Client
• An AIXM 5.1 extension was developed to store
EAUP Change Date and Sequence Number
EAUP CDR/RSA
• GO Loader was configured to load BASELINEs
& TEMPDELTAs into Oracle

6. Loading data using GO Loader
Configure database
schema mapping from
AIXM 5.1 Schema
AIXM 5.1 Extension to support
• chainDate
• sequenceNumber

7. Data Publication Architecture
Airspace Airspace Flight ATM
Management Design Planning Viewer
EAUP CDR/RSA
Request/Response
• Two tier web services RESTful
Services
SWIM NOP
Services
architecture
WFS Filter
WFS Stored Queries
Query
OGC WFS 2.0
Oracle 11g
Express Edition

8. OGC Web Feature Service (WFS)
• An OGC WFS is a generic web service that allows users to submit
requests to retrieve and maintain features or properties using
queries that contain XPath and filter expressions:
Logical Comparison Identifier
Spatial Temporal
Example Retrieval Requests:
•Get all CDR for the EAUP Chain 2012-04-25”, sequence number = 2
•Get all active FIR airspaces that are valid between 2012-04-12 to 2012-04-22
that intersect Route “abc1234”

9. WFS Stored Queries
• Stored queries can be used to limit or tailor the request
for specific applications
• Stored queries were developed to replicate the EAUP
requests:
– EAUPCDR
– EAUPRSA
• Stored queries defined using the CreateStoredQuery
operation containing a standard wfs:Query and fes:Filter

10. CreateStoredQuery
Request
Each Stored
query has an
identifier and title
and contains request
parameters:
• chainDate
• sequenceNumber

11. Swim EAUPCDR request
• HTTP Get - KVP request
http://demo.snowflakesoftware.com:8081/SwimEAUPCDR/GOPublisherWFS?
service=WFS&
version=2.0.0&
request=GetFeature&
STOREDQUERY_ID=EAUPCDR&
chainDate=2012-04-25&
sequenceNumber=4

12. SwimEAUPCDR WFS
response

13. Data Publication Architecture
Airspace Airspace Flight ATM
Management Design Planning Viewer
EAUP CDR/RSA
Request/Response
• Stored queries are used by RESTful SWIM NOP
Services Services
the RESTful API and SWIM
SOAP Wrapper WFS Filter
Query
WFS Stored Queries
OGC WFS 2.0
Oracle 11g
Express Edition

14. RESTful API
• REST is a lightweight, loosely couple API
• Requests are simply URIs
• EAUP RESTful URI Design
– /SwimEAUPCDR/{chainDate}/{sequenceNumber}
– /SwimEAUPRSA/{chainDate}/{sequenceNumber}
• RESTful URI pattern was designed toreturn all EAUPs for
ensure it is
"hackable up the tree": specified chainDate
• /SwimEAUPCDR/2012-04-22/

15. SWIM SOAP Wrapper
Transform request into a WFS HTTP Get request
(stored query) and submit
• Designed to replicate
SWIM B2B Airspace Receive WFS Response
SOAP Service
If response contains a set of If response contains no
features, extract feature and insert into features, generate relevant response
relevant SWIM response document document
(EAUPCDRReply or EAUPRSAReply)

16. SWIM SOAP Wrapper
Transform request into a WFS HTTP Get request
(stored query) and submit
Receive WFS Response
If response contains a set of If response contains no features,
features, extract feature and insert into generate relevant response document
relevant SWIM response document
(EAUPCDRReply or EAUPRSAReply)

17. SWIM SOAP Wrapper
Transform request into a WFS HTTP Get request
(stored query) and submit
Receive WFS Response
If response contains a set of If response contains no
features, extract feature and insert into features, generate relevant response
relevant SWIM response document document
(EAUPCDRReply or EAUPRSAReply)

18. Visualising data using ATM Viewer
• EAUP CDR & RSA

19. Visualising data using ATM Viewer
• Baseline Points

20. Technology Benefits
• Single Conceptual service deployed in many styles:
SOAP Services, RESTful Services, OGC Services
– One logical service, many types of end-point to encourage an eco-
system around ATM data
– Fit for purpose services removing barriers for data consumers
– Standards based services enabling off the shelf clients
– Richer services for finer grained access
• All deployed through standards based configuration
– Minimal software development required
– Reduced costs and timeframe of implementing SWIM Web Services
– Proving the way towards model driven service generation directly
from the ISRM

21. Experiment with the Services
http://wiki.snowflakesoftware.com/dis
play/LAB/Resources
Download the viewer
http://www.snowflakesoftware.com/20
12/10/atm-viewer-for-aixm/
Contact:
Ian Painter : ian.painter@snowflakesoftware.com
Debbie Wilson : debbie.wilson@snowflakesoftware.com