SESAR AIRM/ISRM overview and relation with AIXM/WXXM/FIXM
description
Transcript of SESAR AIRM/ISRM overview and relation with AIXM/WXXM/FIXM
SESAR AIRM/ISRM overview and relation with AIXM/WXXM/FIXM
2
Objective today
• Highlight full scope of interoperability
• Raise awareness about the role of the AIRM• Raise awareness about the role of the ISRM
• Explain relationship with AIXM/WXXM/FIXM• Introduce compliance
3
There’s a lot in the names…
ATM InformationReferenceModel
Information ServiceReferenceModel
4
Interoperability - Full Scope
Information SystemInformation System
Real World System Real World System
Organisation A Organisation B
Organisational Alignment
Semantic Alignment
Process Alignment
Syntax (XML,…)
Transport (HTTP, TCP/IP,…)
Interaction (SOAP,REST, OGC…)
5
Compliant PhysicalModels
« solution »
Compliant PhysicalModels
« solution »
Reference Model« language »
Reference Model« language »
Interoperability – Information Models
Information SystemInformation System
Real World System Real World System
Organisation A Organisation B
Logical Interoperability
Technical Interoperability
6
Interoperability – Information Models
Information SystemInformation System
Real World System Real World System
Organisation A Organisation B
WXXMWXXM
AIRMAIRM
AIXMAIXM FIXMFIXM ……
NOV-7 / NSV-11a
NSV-11b
7
Service
From data interoperability to SWIM Services interoperability!
• Service -> My name is AMIS “Aerodrome Map Information Service”
• My Interfaces are:• GetCapabilities• DescribeFeaturetype• GetFeature
• My message provided by my GetFeature interface conforms the AMDB.XSD
• There is a conform instance of me for Stockholm Arlanda Airport, Toulouse Aiport, …
• My instances talk OGC WFS over HTTP
Service Description
Policy
SLA
8
Fictitious example for AMIS GetFeature requesthttp://prisme-websrv.hq.corp.eurocontrol.int/geoaeronet/fua/wfs/lflc?service=WFS&version=1.0.0&request=GetFeature&TypeName=AM_RunwayElement
9
Consolidated Logical Data Model
Flight::Flight
+ airborneStatus: CodeAirborneStatusType+ releaseKind: CodeFlightKindType+ pointingRole: CodePointingRoleType+ nextSSRCodeState: CodeNextSSRCodeStateType
Trajectory
Negotiating4DTrajectories
Executed4DTrajectory
Desired4DTrajectory
TrajectoryDescription
Points::TrajectoryPoint
+ airspeed: ValSpeedType+ designator: CharacterString+ flightPhase: CodeFlightPhaseType+ groundSpeed: ValSpeedType+ heading: MagneticAngleType+ mass: Weight+ overflown: Boolean+ refIdDesignator: ExpandedRoutePoint+ rocd: ValSpeedType+ track: MagneticAngleType
Trajectory4DData
+ rejectReason: CharacterString+ requestReference: CharacterString+ status: Code4DTrajectoryStatusType
Ranked4DTrajectory UncertaintyQualifications
FlightAirspace
+ activated: Boolean+ firstEntryDistance: Distance+ firstEntryFlightLevel: ValFLType+ firstEntryTime: DateTime+ firstEntryTrend: CodeFlightTrendType+ lastExitDistance: Distance+ lastExitTime: DateTime+ lastExitTrend: CodeFlightTrendType+ occupancyDuration: TM_Duration+ occupancyDistance: Distance
+trajectoryPoints
+trajectory
+point
+predictionUncertainty
+preferredTrajectories
+rankedTrajectory
+alternativeProposal
+trajectory
+trajectoryDescription
+requestedTrajectory
+flight
+crossedFlightAirspace
+flight
+trajectory
+clearedTrajectory
10
Consolidated Logical Data Model
Adapting the AIRM to a Specific Use
Runwaydesignator: CharacterString
nominalLength: Distance
Aerodromedesignator: CharacterString
name: CharacterString
locationIndicatorICAO: CharacterString
runway associatedAirport
A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft/helicopters.
Physical Data Model
Runwaydesignator: CharacterString 0..1
AirportHeliportdesignator: CharacterString
name: CharacterString
locationIndicatorICAO: CharacterString [4]
0..1 associatedAirport
A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft/helicopters.
Derivation rules, constraints
11
SESAR context: Services and existing XMs
AIXM
SDM
WXXM
Trace
Trace
Trace
AIM Service Message
MET Service Message
Trajectory Service Message
Trace
Trace
Trace
NSV-11a NSV-11b NSOV-2
AIRM CLDM
The CLDM provides the integration of the Domain Specific Languages at the logical level (shared semantics)
Physical Models provide the technical representation of the Messages in a relevant standard, that may be domain specific
Service Descriptions express the messages required for information exchange at the logical level and indicate the relevant physical standard
Domain specific standards
DCB Service Message
ACDM Service Message
Trace
Trace
Trace
Trace
12
Thank you for your attention!Thank you for your attention!