mvas and aixm
DESCRIPTION
MVAs and AIXM. AIXM5 in the Real World. Dr. Navin Vembar The CNA Corporation. Outline. What are MVAs and MIAs? Modernizing the MVA and MIA Process The MVA/MIA Model Moving Forward. Outline. What are MVAs and MIAs? Modernizing the MVA and MIA Process The MVA/MIA Model Moving Forward. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/1.jpg)
MVAs and AIXM
Dr. Navin Vembar
The CNA Corporation
AIXM5 in the Real World
![Page 2: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/2.jpg)
Outline
• What are MVAs and MIAs?
• Modernizing the MVA and MIA Process
• The MVA/MIA Model
• Moving Forward
![Page 3: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/3.jpg)
Outline
• What are MVAs and MIAs?
• Modernizing the MVA and MIA Process
• The MVA/MIA Model
• Moving Forward
![Page 4: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/4.jpg)
What are MVAs and MIAs?
• Minimum Vectoring Altitudes and Minimum Instrument Altitudes– Used to ensure that aircraft avoid obstacles and
terrain
• MVA used by TRACONs with ARSR radar– Each radar has its own MVA chart
• MIAs used by facilities with ASR radars– Usually ARTCCs or large TRACONs
• Need to automate for safety reasons
![Page 5: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/5.jpg)
How Areas are Built
• Each MVA or MIA area is constructed from polygon “modules”– Many areas have
holes in them to avoid particular obstacles or terrain points
• Picture on the right is from the SDAT tool
![Page 6: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/6.jpg)
Outline
• What are MVAs and MIAs?
• Modernizing the MVA and MIA Process
• The MVA/MIA Model
• Moving Forward
![Page 7: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/7.jpg)
The Process, As-Is
• Facilities design their charts– Use sectional charts for obstacle and terrain
information
• They submit the chart by paper to the National Flight Procedures Office– Fill out relevant forms including information about
the controlling obstacles or terrain for each area
– NFPO can reject or accept the chart
– Done yearly
![Page 8: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/8.jpg)
The Modern MVA Lifecycle
RVM, ACES
Design (SDAT) Submit
Flight Procedures (NFPO) Validation
Implement
New obstacle review (using
NASR and OE/AAA)
Concept of Operations
RVMACES
RVMACES
Store (NASR)
![Page 9: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/9.jpg)
SDAT For Automation
• The Sector Design and Analysis Tool (SDAT) is the cornerstone of MVA/MIA modernization
• SDAT allows designers to create MVA and MIA areas– Validates against digitized obstacles– Validates against USGS NED data for terrain– Computes necessary polygon mathematics
(buffering, adding, subtracting)
![Page 10: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/10.jpg)
SDAT For Automation
• SDAT is a tool that has existed since 1998– Currently version 5.12
• Uses AIXM 3.3 for representation of MVA and MIA data– But, we’re talking about AIXM5!
• After approval, the SDAT backend will– Convert to AIXM 5 – Submit to the National Airspace Resources
(NASR) Repository
![Page 11: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/11.jpg)
Outline
• What are MVAs and MIAs?
• Modernizing the MVA and MIA Process
• The MVA/MIA Model
• Moving Forward
![Page 12: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/12.jpg)
Data Model for MVAs
Airspace(from Airspace)
<<feature>>
Unit(from Organisation)
<<feature>>ResponsibleParty
<<datatype>>M
MinimumAlti tudeAreas<<feature>>
Point(from Geometry)
<<object>>
MinimumInstrumentAlti tudeAreas<<feature>>
MinimumVectorAlti tudeAreas<<feature>>
MinimumAltitudeAreaList<<object>>
VerticalStructure(from Obstacle)
<<feature>>
ElevatedPoint(from Geometry)
<<object>>MinimumAltitudeArea
<<feature>>
1
hasUnit
1
1hasDesigner
1
0..*hasApprover 0..*
1
hasRadarLocation
1
1
hasAreas
1 1
hasAreas
1
0..n0..n
1
hasControll ingObstacle
1
hasHighTerrainPointNoBuffer
hasHighTerrainPoint
![Page 13: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/13.jpg)
What Are We Leveraging?
• AIXM 5 Features & Objects– Feature Collections– Airspace– Unit– (Upcoming) Services– ResponsibleParty
![Page 14: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/14.jpg)
Feature Collections
• Key to the whole process
• MVA Charts are features which contain MVA Areas, which are again features
• Solution: Feature Collections
• Features can be aggregated into a larger feature known as a feature collection
![Page 15: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/15.jpg)
Other Features
• Unit – Representing facility information
• Service– Representing facility radar
• The key is reuse– Why model something already done for you?– Attributes and elements are optional, only fill
in what you need
![Page 16: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/16.jpg)
Conversion
• Problem: SDAT creates data in AIXM 3.3
• We want to move to AIXM 5 for new web service and exchange communications– Tool of choice: XSLT– Difficulties
• Different GML models for representing geometries• Converting between DMS and decimal degrees
![Page 17: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/17.jpg)
Implementation Choices
• Now that we have the model, what about implementation?– How to represent aggregate geometries within
an Airspace?• GML+xlink is very flexible and thus brings up this
question
– How much of the dependent feature and object data do we need?
![Page 18: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/18.jpg)
Implementation Questions
• How to implement model while storing and disseminating?– What will be efficient?– What will be useful?
• Model and implementation are separate issues– Consider users and the level of flexibility required
• Persistence Web Server– MVA/MIA: Only one “user”, so specification of implementation
can be limited
• General consumers– Can use any implementation that meets the model
requirements
![Page 19: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/19.jpg)
Implementation - Storage
• Efficient?– As we may reuse modules across different areas,
store those once• Provides spatial value as when the AIXM is moved to Oracle
SDO, these may be indexed separately
• Useful?– We are reusing nodes, but we never manipulate them
• Implementation– Consists of a list modules– Areas use xlink and Airspace aggregation to refer to
the modules
![Page 20: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/20.jpg)
Implementation - Editing
• Efficient?– Again, use shared modules
• Useful?– Now, a user may move a single node and have it
affect multiple areas– Requires node-level data
• Implementation– Consists of a list of nodes– Build modules from nodes using xlink references– Areas use xlink and Airspace aggregation to refer to
the modules
![Page 21: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/21.jpg)
Outline
• What are MVAs and MIAs?
• Modernizing the MVA and MIA Process
• The MVA/MIA Model
• Moving Forward
![Page 22: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/22.jpg)
Plans
• Using Web Services– “Black Boxing” MVA and MIA data
• Achieved decoupling
– Will be used in obstacle proposal process
• Persistence of AIXM data– Using Oracle 11’s GML handling to convert
directly to SDO
![Page 23: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/23.jpg)
Conclusion
• AIXM 5 is contributing to a successful implementation of MVA and MIA storage and dissemination
• Gaining leverage from its components– AIXM 5 features– GML– XML
![Page 24: MVAs and AIXM](https://reader033.vdocuments.site/reader033/viewer/2022061617/56815862550346895dc5bee9/html5/thumbnails/24.jpg)
Questions?