1 / 22

AP23 briefing on D4: Draft Proposal for a second set of GS/AS Applications

AP23 briefing on D4: Draft Proposal for a second set of GS/AS Applications. ASAS-GN Seminar 13 Nov 08, Rome By Brian Baxley, NASA Ben Stanley, Helios. Objective of this presentation. To outline a methodology for developing future, long-term ASAS applications based on ADS-B

winola
Download Presentation

AP23 briefing on D4: Draft Proposal for a second set of GS/AS Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AP23 briefing on D4:Draft Proposal for a second set of GS/AS Applications ASAS-GN Seminar 13 Nov 08, Rome By Brian Baxley, NASA Ben Stanley, Helios

  2. Objective of this presentation • To outline a methodology for developing future, long-term ASAS applications based on ADS-B • To show how and why AP23 has developed the work • To highlight how to use the document and next steps to be taken

  3. AP23 Overview: Deliverables Five deliverables from AP23: • D1 – General data exchange • D2 – Methodology to prioritize applications for AP23 • D3 – Operational Role of Airborne Surveillance in Separating Traffic • D4 – Draft proposal for a second set of ADS-B/ASAS applications • D5 – Draft White Paper on Issues Surrounding Airborne Separation

  4. AP23 D4: GS/AS Applications (V0.3, Oct 08)List of Chapters and Appendices • 1. Introduction • 2. Future Application Definition Process • 3. Application Elements and Functions • 4. Examples of Applications • 5. Transition from “Package 1” to Future Applications • 6. Way Forward • Appendix A: Application Template • Appendix B: Input from Stakeholders • Appendix C: Application Element Mapping • Appendix D: Element and Function Mapping • Appendix E: Submitted Applications and Element Mapping

  5. D4, Chapter 1Introduction • AP23 is focused on long-term ground and airborne surveillance (GS and AS) applications of common interest between FAA and Eurocontrol, and beyond those already covered by RFG • It looks to NextGen and SESAR to set the scope and direction • AP23 developed and documented a process to prioritize applications and functions Ideas (including SESAR + NextGen) Feasibility Possible applications Down-selection

  6. D4, Chapter 1Introduction: Objectives • D4 is not currently a list of proposed applications as per “Package 2” • D4: • Is a draft proposal for advanced ASAS elements and functions • Shows how AP23 organised the applications, and enhanced understanding of advanced applications • Includes “functional decomposition” of applications into building blocks • Is a work in progress, represents “snapshot” of current work

  7. D4, Chapter 1Introduction: Objectives • Why? • Elements and functions are used to streamline standardisation • rather than many applications in many environments, some standardised elements and functions may be used • leads to economical development and implementation • There is however an aim to highlight key applications • such that all required elements and functions have their requirements derived in the most demanding context • beneficial, or necessary in terms of meeting the performance goals of the future system • way of showing that elements/functions can be put together and that the approach works

  8. D4, Chapter 2Future Application Definition Process • 4000 people solicited over 3 months (07/2007 – 09/2007) for ideas of future ASAS applications • Over 100 inputs received, with significant overlap in objective, operational use, requirements, and functions • Triggered new approach to find set of functions common to all ASAS applications regardless of environment • Resulted in grouping of: • ATSA: Situational Awareness • ASPA: Spacing • ASEP: Separation • SSEP: Self Separation • Surface: Surface • GS: Ground Surveillance This briefing

  9. D4, Chapter 3Application Elements and Functions Operational Requirements Applicability Area/Conditions • Process to build an application: • Elements + Functions + Environment = Application • Application elements - A basic ASAS-enabled (operational) capability of the subject aircraft that cannot easily be subdivided further into more basic elements. • ASAS functions - the processes, calculations, and monitoring tasks that must be supplied by the ASAS avionics system to enable the application element. • Environments - en-route, procedural, terminal, and surface. Use AP23 D4 Application elements ASAS Functions Environment description Candidate application description Safety Requirements Performance Requirements Interoperability Requirements

  10. Contingency Procedures Identify Designated Aircraft Transfer Separation Responsibility D4, Chapter 3Application Elements (1 of 5) • Objective: - Enabling Applications • Identify Designated Aircraft • Transfer Separation Responsibility • Contingency Procedures

  11. Pair-Wise Interval Achievement Target Point Merge Target Track Merge Dynamic Path Merge D4, Chapter 3Application Elements (2 of 5) • Objective: Achieve Relative Position • Target Point Merge • Target Track Merge • Dynamic Path Merge • Pair-Wise Interval Achievement

  12. Dynamic Path Follow Pair-Wise Interval Maintenance Target Follow D4, Chapter 3Application Elements (3 of 5) • Objective: - Maintain Relative Position • Pair-Wise Interval Maintenance • Track Follow • Dynamic Path Follow

  13. Lateral Passing & Crossing Vertical Passing & Crossing Manoeuvre w/o Conflict Conflict Management Delegated Encounter User Request D4, Chapter 3Application Elements (4 of 5) • Objective: - Maximize Use of Desired Trajectory • Vertical Passing & Crossing • Lateral Passing & Crossing • Delegated Encounter • User Request Manoeuvre • Conflict Management • Manoeuvre w/o Conflict

  14. Runway Crossing Taxi Follow Taxi Merge D4, Chapter 3Application Elements (5 of 5) • Example surface application elements (draft) • Runway crossing • Runway incursion detection (and resolution) • Taxi follow • Taxi merge • Autonomous take-off (in TM environment)

  15. D4, Chapter 3ASAS Functions • ASAS functions - the processes, calculations, and monitoring tasks to enable the application element. There are: • Traffic Data: identify & track aircraft, provide reference aircraft trajectory, assess initiation/continuation/termination criteria • Merge: compute manoeuvre to the merge, compute merge location • Follow: compute dependant following trajectory • Manage Interval: compute speed to achieve and maintain interval, monitor interval conformance • Separation Maintenance: monitor and maintain separation between reference and subject aircraft • Conflict Detection: probe trajectory for conflicts, alert crew to conflicts • Conflict Resolution: vertical, lateral, or user-preferred trajectory to ensure traffic separation • Trajectory Optimization: compute conflict-free user-preferred trajectory, compute manoeuvring flexibility

  16. D4, Chapter 4Example of Application Two examples to put together process, elements, and functions. • #1): Merging and Spacing with Separation • ASEP M&S (PO-ASAS 3) • Objectives: • Achieve Relative Position • Maintain Relative Position • #2): Self-Separation Airborne Trajectory Management • SSEP-AirTM (PO-ASAS 4) • Objective: • Maximize Use of Desired Trajectory

  17. Crew receives clearance, selects lead aircraft, enters assigned spacing interval. Crew verifies acceptable speed, then follows speed guidance Crew follows speed guidance while merging the aircraft D4, Chapter 4Example #1 of Application: ASEP M&S (1 of 2) • NAME: ASEP M&S • Ground Set-Up • Aircraft Operation

  18. P2 P3 Identify Designated Aircraft Transfer Separation Authority P1: Set Up P2 P3 Track reference aircraft Identify reference aircraft P4 Target Point Merge P2: Aircraft ID and Procedure Feasibility Assessing initiation criteria Provide reference aircraft trajectory P4 Compute maneuvers to merge Pair wise Interval Achievement Compute guidance to maintain separation P3: Clearance & Transfer of Responsibility Track Follow Monitor maintenance of separation Compute speeds to achieve and maintain interval P4: ASEP M&S Procedure Pair wise Interval Maintenance Assessing continuation criteria P5: Procedure Complete Compute dependent following trajectory P5 Transfer Separation Authority P5 Assessing termination criteria P6: Exceptions P6 Contingency Procedures D4, Chapter 4Example #1 of Application: ASEP M&S (2 of 2) • Functions: • Elements: • Objectives: • Achieve Relative Position • Maintain Relative Position

  19. En Route Airspace Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Self-Separating Q Ground managed Q Q Q Q Q Q Q Q D4, Chapter 4Example #2 of Application: SSEP AirTM (1 of 2) • NAME: SSEP AirTM • Ground Operations • Manage Airspace Resources • Generate Flow Constraints • Manage Unequipped Aircraft • Airborne Operations • Broadcast State and Intent Data • Self-Separate from Traffic, Weather, and Airspace • Conform to Ground-Generated Constraints (RTAs, etc) • Optimize Trajectory Next briefing, “NASA ASAS” covers more detail

  20. P1: Set Up Trajectory P1 P2 User requested maneuver P2: Responsibility Transfer Transfer Separation Authority AC continues along trajectory P1 P2 Track reference aircraft Probe trajectory for conflicts P3 P6 Conflict detection And resolution P3: Separation Prediction P3 P6 Alert crew for conflicts Probe trajectory for conflicts Assessing initiation criteria Provide reference aircraft trajectory Maneuver without conflict Monitor maintenance of separation P4: Performance Monitor P6: Trajectory Revision Compute guidance to maintain separation Trajectory change required P5: RBT Change Monitor Compute maneuvering flexibility Compute user-preferred trajectory to provide separation Current trajectory is acceptable Compute aircraft performances P7: Termination AC approaches transfer point P7 Compute traffic-constrained user-preferred trajectory Transfer Separation Authority Assessing continuation criteria P8: Exceptions P8 Contingency Procedures P5 Assessing termination criteria D4, Chapter 4Example #2 of Application: SSEP AirTM (2 of 2) • Functions: • Elements: • NAME: SSEP-AirTM • Objectives: • Maximize Use of Desired Trajectory

  21. D4: Way Forward • AP23 is proposing • a set of ASAS elements and functions, • a method to build applications, and • how to apply this in a practical manner for NextGen and SESAR. • D4 stops short of proposing a firm set of applications for “Package 2” • Engage with larger community to build key applications • Cost benefit analyses to be performed by stakeholder in specified scope and operational environment • Lots of validation now needed – to be identified in the next AP23 deliverable (D5 – issues for ASEP) • D4 is a work in progress, represents “snapshot” of current work

  22. Thank you brian.t.baxley@nasa.gov ben.stanley@askhelios.com

More Related