1 / 35

Performance Based Communications and Surveillance (PBCS) An introduction

Performance Based Communications and Surveillance (PBCS) An introduction. PBCS Workshop Bangkok, Thailand, 13-14 May, 2013. APANPIRG/23 – September 2012 Conclusions (1). APANPIRG/23 – September 2012 Conclusions (2). ATM – More Dependency on Comm. and Surv. RLatSM RLonSM. UPR DARP TA

velma-slater
Download Presentation

Performance Based Communications and Surveillance (PBCS) An introduction

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. Performance Based Communications and Surveillance (PBCS)An introduction PBCS Workshop Bangkok, Thailand, 13-14 May, 2013

  2. APANPIRG/23 – September 2012 Conclusions (1)

  3. APANPIRG/23 – September 2012 Conclusions (2)

  4. ATM – More Dependency on Comm. and Surv. RLatSM RLonSM UPR DARP TA ITP CDP 30 NM lateral 30/50 NM longitudinal

  5. A Performance Based Approach • Doc 9883 Manual on Global Performance of the Air Navigation System • Notion of a performance based air navigation system emanated from industry practices that have evolved for many years outside of aviation. • Based on following principles: • Strong focus on desired/required results through adoption of performance objectives and targets • Informed decision making, driven by the desired/required results; and • Reliance on facts and data for decision making. • Assessment is periodically checked through performance review, which requires adequate performance measurement and data collection capabilities. • Performance based approach is a pragmatic tool in • Planning changes • Developing changes • Optimising the System (Continuous Performance Improvement)

  6. ICAO Global Air Navigation Plan and ATM Concept Airspace Concept AirTrafficManagement Surveillance Navigation Communication PBS PBC PBN Performance Based Communication Performance Based Surveillance Performance Based Navigation

  7. PBN – current definition Annex 6 & 11 • Performance-based navigation (PBN). • Area navigation based on performance requirements for aircraft operating along an ATS route, on an instrument approach procedure or in a designated airspace. Note.— Performance requirements are expressed in navigation specifications (RNAV specification, RNP specification) in terms of accuracy, integrity, continuity, availability and functionality needed for the proposed operation in the context of a particular airspace concept.

  8. PBC - ICAO OPLINKP amend Annex 6, 11? • Performance-based communication (PBC). • ATS communication services and capability based on performance requirements for air traffic service provision, aircraft and flight operations along an ATS route, on an instrument approach procedure or in a designated airspace. Note.— Communication performance requirements are allocated to system components in an RCP specification in terms of communication transaction time, continuity, availability, integrity, safety and functionality needed for the proposed operation in the context of a particular airspace

  9. PBS - ICAO OPLINKP amend Annex 6,11? • Performance-based surveillance (PBS). • ATS surveillance services and capability based on performance requirements for air traffic service provision, aircraft and flight operations along an ATS route, on an instrument approach procedure or in a designated airspace. Note.— Surveillance performance requirements are allocated to system components in an RSP specification in terms of surveillance data delivery time, continuity, availability, integrity, accuracy of the surveillance data, safety and functionality needed for the proposed operation in the context of a particular airspace concept.

  10. RNP - ICAO • Navigation specification. A set of aircraft and flight crew requirements needed to support performance-based navigation operations within a defined airspace. There are two kinds of navigation specifications: • Required navigation performance (RNP) specification. A navigation specification based on area navigation that includes the requirement for performance monitoring and alerting, designated by the prefix RNP, e.g. RNP 4, RNP APCH. • Area navigation (RNAV) specification. A navigation specification based on area navigation that does not include the requirement for performance monitoring and alerting, designated by the prefix RNAV, e.g. RNAV 5, RNAV 1.

  11. RCP - ICAO OPLINKP amend Annex 6, 11? • Required communication performance (RCP) specification. • A set of requirements for air traffic service provision, aircraft capability, and operations needed to support performance-based communication within a defined airspace. Note: The term RCP, has been revised to align the concept of PBC with the concept of PBN. The term RCP is now used in the context of a specification that is applicable to the prescription of airspace requirements, qualification of ATS provision, aircraft capability, and operational use, including post-implementation monitoring (e.g. RCP 240 refers to the criteria for various components of the operational system to ensure an acceptable intervention capability for the controller is maintained).

  12. RSP - ICAO OPLINKP amend Annex 6, 11? • Required surveillance performance (RSP) specification. • A set of requirements for air traffic service provision, aircraft capability, and operations needed to support performance-based surveillance within a defined airspace. Note: The term RSP is used in the context of a specification that is applicable to the prescription of airspace requirements, qualification of ATS provision, aircraft capability, and operational use, including post-implementation monitoring (e.g. RSP 180 refers to the criteria for various components of the operational system to ensure an acceptable surveillance capability for the controller is maintained.

  13. PBCS – Prescription of RCP/RSP • Based on RCP and RSP, PBCS will enable: • ICAO to specify communication and surveillance requirements for specific ATS operations (e.g. application of separation minimum); • Regions/States to prescribe RCP and RSP specifications in Regional Supplementary Procedures and Aeronautical Information Publications (AIPs or similar publication)

  14. PBCS – Initial Qualification • Based on RCP and RSP, PBCS will enable • Aircraft systems to be approved in accordance with prescribed RCP and RSP specifications • Operators to be authorized by the State of Registry or State of the Operator, as appropriate, and to file the prescribed performance based designators (e.g. RCP 240, RSP 180) in their flight plans • ANSPs to ensure infrastructure in accordance with prescribed RCP and RSP specifications and assess aircraft capability from flight plan information, to safely apply the appropriate ATS (e.g. reduced separation) to eligible aircraft

  15. Why PBCS? – What is RCP/RSP of these aircraft? VDL2? VHF? POA? RNP4 Inmarsat SBB? RCP240? Inmarsat I3? RCP400? Inmarsat I4? RNP4 SATCOM? Iridium Next? RNP4 RNP4 RSP180? RNP4 Iridium? RSP400? RNP from FPL RNP4 MTSAT? HFDL? RNP4 RCP/RSP from ? SATCOM+HFDL? RNP104

  16. PBCS – Continued Compliance • Based on RCP and RSP, PBCS will enable: • ICAO Regions to conduct post-implementation monitoring of operational performance against RCP and RSP specifications, and initiate corrective action to the appropriate party, as necessary, for continued operational safety • ICAO Regions to exchange performance information in a consistent way • Operators will need to establish programs that support post-implementation monitoring activities

  17. PBCS - RSP/RCP – ICAO FPL • Currently, there is potential for an ATSP to misapply Air Traffic Services to an operator or aircraft type because no specific RCP or RSP definition is available in the FPL. • Specific RCP/RSP definition is needed by ground system automation to enable reliable application of Air Traffic Services to suitably equipped aircraft that meet RCP/RSP specifications.

  18. PBCS - RSP/RCP – ICAO FPL • ICAO Flight Plan makes provision for RCP allocation in Item 10 with reserved designators. • Asia/Pac ICAO 2012 guidance specifically states that ATSP should process reserved RCP designators without error. • No similar provision with reserved designators was made for RSP allocation in Item 10 but does make mention of use of SUR/ in Item 18.

  19. RSP/RCP – OPLINKP amend PANS-ATM Doc4444? • Item 10a • Note 7.— Guidance material on the application of performance-based communication, which prescribes RCP to an air traffic service in a specific area, is contained in the Performance- Based Communication and Surveillance (PBCS) Manual (Doc 9869). • Item 10b • If the descriptor D1 is used, the performance-based surveillance level that can be met are specified in Item 18 following the indicator SUR/. Guidance material on the application of performance-based surveillance, which prescribes RSP to an air traffic service in a specific area, is contained in the Performance-Based Communication and Surveillance (PBCS) Manual (Doc 9869).

  20. RSP/RCP – tactical indication in aircraft • Aircraft provides the flight crew with alerts in case of equipment/capability failures, e.g. • Communication Means failure (e.g. SATCOM FAULT) • Definitive connectivity loss (e.g. VHF3 DATALINK FAULT) • Failure of ATC Data Link (e.g. ATC DATA LINK FAULT) BUT • There is no RCP/RSP indication directly displayed to the flight crew. Note: Appropriate procedures (refer to GOLD) and associated training is required to ensure failure notifications to ATSP.

  21. RSP/RCP – tactical indication to controller • ATM ground system automation provides the controller with alerts in case of equipment/capability failures, e.g. • Communication failure. (e.g. ACARS FAULT) • CPDLC transaction timeouts. (e.g. NO RESPONSE RECEIVED) • ADS-C periodic reports overdue. Note: If ground system provides indication to controller for action then controller can assess suitability of communications and surveillance for continued application of ATS service based on workload BUT • There is no real time monitor of actual performance to indicate “RCP/RSP unable” directly to the controller. Note: Appropriate procedures (refer to GOLD) and associated training is required for equipment/capability failures e.g. aircraft SATCOM failure?

  22. PBCS – an introductory history (1) • In 1991, the 10th ANC endorse the Future Air Navigation System concept. • This becomes known as the communications, navigation, surveillance/air traffic management (CNS/ATM) systems concept. • In 1996, at the 4th meeting of the Aeronautical Mobile Communications Panel (AMCP/4) recognises the absence of objective criteria to evaluate communications performance. • In 2000 AMCP is renamed the Operational Data Link Panel (OPLINKP) • In 1997, the Air Navigation Commission tasks OPLINKP to develop the concept of Required Communications Performance (RCP). • In 2001, OPLINKP completed a concept of RCP and the Air Navigation Commission solicit State comment. • In 2002, OPLINKP were tasked to develop a manual on RCP and as necessary develop SARP’s and procedures relating to the use of RCP in ATS.

  23. PBCS – an introductory history (2) • In 2003, the 11thANC endorse recommendations to : • Confirm development of RCP • Investigate further areas including: • Relationship of RCP to separation studies and interoperability • RCP Types and Allocations • Safety performance monitoring • In 2007, Annex 6 - Operation of Aircraft, • Amended to introduce concept of RCP in the provision of ATS. • In 2007, Annex 11 – Air Traffic Services and Doc 4444 PANS - ATM, • Amended to introduce definitions and associated procedures for RCP.

  24. PBCS – an introductory history (3) • In 2007,RTCA DO-306/EUROCAE ED-122 Safety and Performance Standard for Air Traffic Data Link Services in Oceanic and Remote Airspace (Oceanic SPR Standard) is published. • Provides operational, safety, and performance requirements for data link services that support specific ATS functions in oceanic and remote airspace. • Specifically provides RCP/RSP allocations for reduced separation standards • In 2008, ICAO Doc 9869 Manual on Required Communications Performance is published. • In 2010, ICAO Global Operational Data Link Document (GOLD) is published. • Appendix B – RCP Specifications • Appendix C - RSP Specifications • Appendix D – Post Implementation Monitoring and Corrective Actions

  25. PBCS – an introductory history (3) • In 2011/12, GOLD Edition 2 is developed with planned completion April 2013. • The GOLD, First Edition, Appendix C, refers to “surveillance performance specifications.” The GOLD, Second Edition, will refer specifically to “RSP specifications.” • In 2012/2013,OPLINKP develop proposals to: • Rename ICAO Doc 9869 “Manual on Required Communications Performance” to “Performance Based Communications and Surveillance (PBCS) Manual”. • Move guidance material from GOLD Edition 2 Appendix B – RCP Specifications, Appendix C – RSP Specifications, and Appendix D – Post Implementation Monitoring and Corrective Action into PBCS Manual. • Amend Annex 6 Part I and Annex 11 to include standards associated with PBCS similar to PBN and refer to guidance material in Doc 9869 PBCS Manual. • Amend PANS-ATM Doc 4444 for flight plan provisions concerning PBCS

  26. PBCS – Background in NAT Region • NAT SPG/43 (2007) – Identified communication service problem needing urgent attention (43/29) • Special NAT SPG (2007) – Established RCP Task Force (SP2007/6) • NAT SPG/44 (2008) – Agreed to mandate RCP by 2015 (44/11) • NAT SPG/46 (2010) – Endorsed GOLD (46/8) • NAT SPG/47 (2011) – Endorsed NAT PBCS Implementation Plan (47/5) • NAT SPG/48 (2012) – RCP – RSP Applicability (48/7)

  27. PBCS – NAT PBCS Implementation Plan • 2015 implementation • 17 tasks on track • Key items • PfA for Doc 7030 • Flight plan • ATC automation • Post-implementation monitoring

  28. PBCS – NAT PBCS Workshop • NAT PBCS Workshop • Task 4 of NAT PBCS Implementation Plan • Training and education - Safety communication • Exchange information and promote global harmonization • Held Paris, France 20-22 February 2013

  29. RCP – Required Communications Performance • RCP concept seeks to manage the performance of communications supporting evolving ATM concepts and emerging technologies. This is achieved by: • Determining an RCP type for the communications capabilities supporting an ATM function; then • Prescribing the RCP type(s) related to the communications system(s) supporting the ATM functions within that airspace; and • Complying with the prescribed RCP type(s) through initial qualification, operational assessments, and post implementation monitoring/analysis/corrective action of the communications systems.

  30. RSP – Required Surveillance Performance • RSP concept seeks to manage the performance of surveillance supporting evolving ATM concepts and emerging technologies. This is achieved by: • Determining an RSP type for the surveillance capabilities supporting an ATM function; then • Prescribing the RSP type(s) related to the surveillance system(s) supporting the ATM functions within that airspace; and • Complying with the prescribed RSP type(s) through initial qualification, operational assessments, and post implementation monitoring/analysis/corrective action of the surveillance systems.

  31. FANS1/A - A Performance Based System?

  32. PBCS - Continuous performance improvement

  33. Enabling Benefits with PBCS • Operational improvements (e.g. 30/30NM and 50NM Long) are predicated on certain communications (e.g. CPDLC at RCP240), surveillance (e.g. ADS-C at RSP180), and navigation requirements (e.g. PBN RNP4). • We have an obligation to ensure that aircraft and operators are meeting these requirements. • We have PBN that prescribes navigation specifications (e.g. RNP4 and RNP10) for 30/30NM and 50NM long. • We need to implement PBCS and prescribe appropriate RCP and RSP specifications for the current 30/30NM and 50NM long separation and other functions predicated on communication and surveillance performance.

  34. PBCS – Enabling Benefits with PBCS • In summary, the performance-based approach is seen as a means to: • expedite and maximize operational benefits gained from an existing fleet of data link capable aircraft • to expand the provision and use of data link capabilities, where beneficial, • ensure global harmonization and operational seamlessness of data link implementations. • take into account the overall operational capability and performance needed for the intended operations.

  35. Thank youPaul RadfordManager Oceanic SystemsAirways New Zealandpaul.radford@airways.co.nz

More Related