Required Navigation Performance Area Navigation Test and Certification Process

航空论坛

游客，如果您要查看本帖隐藏内容请回复

航空论坛

PMA209 champions development, integration and
cradle-to-grave support for common avionics solutions
in safety, connectivity, mission computing & interoperability
Required Navigation Performance (RNP) Area Navigation (RNAV) Test and Certification Process for Naval Aircraft
Briefer: Steve Adrian
Date: 14 April 2010
PMA209 champions development, integration and
cradle-to-grave support for common avionics solutions
in safety, connectivity, mission computing & interoperability
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 2
•
Test and Certification Background
•
Test and Certification Process
•
Requirements
•
Systems Engineering Design
•
Testing
–
Laboratory / Ground
–
Flight
•
Reporting
•
Certification Package
•
Certification Review Process
•
Certification Approval
•
Fleet Introduction
•
Conclusion
Overview
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 3
Test & Certification Background
•
Navy aircraft require access to performance based civil airspace to achieve effective/efficient mission accomplishment
•
Navy is working towards ensuring its aircraft are compliant with CNS/ATM standards
•
Navy is a self-certifying agency for each of the CNS/ATM Functionalities
–
RNP RNAV -8.33 kHz Channel Separation
–
Mode Select-RVSM
•
CNO Designated PMA 209 as Central Management Activity for all Naval CNS/ATM Efforts
–
Assists in identifying/defining all future CNS/ATM Requirements
–
Issues Platform Certification upon successful validation of integration
–
Maintains a “Center of Technical Excellence” for Navy/Marine and Coast Guard
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 4
Test & Certification Process
Establish
Requirements
Survey the
Platform
Meets
Requirements
Identify
Missing
Capability
DT for New
Functionality
OT New
Functionality
Effective/
Suitable
for New
Functionality
Identify
Funding
YES
YES
NO
NO
Develop
System Design
Determine
Test
Strategy
USN Director, Air Warfare
COMOPTEVFOR
Platform PMA
PMA 209
CNO
DT Test Team
Platform PMA & PMA 209
Authorizes Capability for Fleet Use
Certify
RNP RNAV Compliance
Review Data
Submission
Prepare
Data
Package for
Review
*CRT –Certification Review Team *CNO –Chief of Naval Operations
Meets
Requirements
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 5
Requirements
•
Requirements Traceability Chain
–
CNO Functional Requirements Document (FRD) for each CNS/ATM Functionality
􀂾
Defines requirements
􀂾
Reference civil standards but modified for unique requirements of Navy Aircraft
–
Test Point Matrix (TPM) for each CNS/ATM Functionality developed by PMA 209
􀂾
Derived from applicable FRD
􀂾
Tailored for platforms
􀂾
Included in platform Test and Evaluation Master Plans (TEMPs) and test plans
􀂾
Populated and included in test reports
CNO
RNP RNAV FRD
P-3C RNP RNAV TPM
P-3C
TEMP
P-3C RNP RNAV Report of Test Results
P-3C RNP RNAV
Test Plan
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 6
Requirements
•
RNP RNAV FRD (RNP 0.3 RNAV)
–
Navigation requirements
􀂾
Primary navigation sensor shall be the Precise Positioning Service (PPS) GPS (crypto keys required)
􀂾
Integrity of GPS and the data base
–
Performance Requirements
􀂾
Lateral Accuracy 95% per flight hour for RNP Type in use
􀂾
Containment Integrity 10-5per flight hour
􀂾
Continuity 10-4/10-3per flight hour
•
RNP RNAV TPM
–
Broken down into over 160 Test Points (TPs)
􀂾
Each traced to “Shalls” in FRD
􀂾
Each evaluated and/or tested individually
􀂾
Tracked throughout the System Engineering/testing process
􀂾
Matrix contains Metric Thresholds and Recommended Test Methods
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 7
Requirements
•
RNP RNAV FRD Excerpts
–
3.2.3 Containment Continuity -The probability of annunciated loss of RNP RNAV capability (for a given RNP RNAV type) shall be less than 10-4per flight hour. The continuity due to failure of the airborne system, not the signal in space, shall be reduced to 10-3per flight hour for aircraft already approved to utilize single-thread avionics systems for navigation.
–
3.2.11 Loss of Integrity Caution -The navigation system displays a loss of integrity caution when the Horizontal Protection Level (HPL) computed by the equipment exceeds the Horizontal Alert Limit (HAL) for the current operation.
–
3.2.6 Path Steering Requirement -During the certification process, the ability of the crew to operate the aircraft within the specified Path Steering Error (PSE) shall be demonstrated.
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 8
Requirements
•
RNP RNAV TPM Excerpts
FRD Reference Paragraph
Test Point #
Test Point
Metric Threshold
Test Method
Met/ Not Met
Remarks
3.2.3
Containment Continuity
006
Dual-thread navigation system probability of annunciated loss of RNP RNAV capability.
< 10-4per flight hour
Qualitative Test/ Analysis
Analysis only due to test duration.
007
Single-thread navigation system probability of annunciated loss of RNP RNAV capability.
< 10-3per flight hour
Qualitative Test/ Analysis
Analysis only due to test duration.
3.2.11
Loss of Integrity Caution
120
The navigation system displays a loss of integrity caution when the HPL computed by the equipment exceeds HAL for the current operation.
True or False
Laboratory/ Ground
Test
3.2.6
Path Steering Requirement
059
During the certification process, the ability of the crew to operate the aircraft within the specified PSE is demonstrated.
Demonstrated PSE <= specified value.
Flight
Test
A measured value of PSE may be used to monitor system compliance to RNP RNAV requirements. For operation on all leg types, the measured value is the distance to defined path.
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 9
•
Survey and determine current Platform configuration and capabilities
•
Work w/Platforms to determine Platform end state requirements to achieve functionality defined by FRDs
•
Address Platform unique issues
•
Choose appropriate hardware for System Design
•
Modify and integrate military/COTS/NDI systems to meet functionality requirements
System Engineering Design
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 10
System Engineering Design
•
•
System Engineering Design Example –P-3C Aircraft
–
RNP RNAV System Solution
􀂾
Dual legacy Replacement Inertial Navigation Unit-GPS (RINU-G)s w/GPS Embedded Module (GEM)-V Cards
􀂾
Dual CDU-7000 Flight Management Computers (FMCs)
􀂾
Air Data Display Unit (ADDU)
􀂾
Electronic Flight Display System (EFDS)
􀂾
GPS Antenna
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 11
−
Test Points (TPs) 006 and 007 Containment Continuity
􀂾
Survey determined legacy RINU-Gs had potential to satisfy requirement but needed documentation of analysis
􀂾
Rockwell Collins as System Integrator conducted an analysis and produced “Preliminary RNP Analysis for P-3C/EP-3 CNS/ATM”
􀂾
Results of analysis shown
System Engineering Design
Summary of Continuity Values GPS Modes
Flight
Phase
Required
RNP (nm)
Enroute/Term Legs
HOLD Legs
Path
Transition
Offset Path
Approach
0.3
6.79E-06
6.79E-06
6.79E-06
6.79E-06
Terminal
1
6.79E-06
6.79E-06
6.79E-06
6.79E-06
Enroute
2
6.79E-06
6.79E-06
6.79E-06
6.79E-06
Oceanic
4
6.79E-06
6.79E-06
6.79E-06
6.79E-06
Summary of Continuity Values INU/GPS Modes
Flight
Phase
Required
RNP (nm)
Enroute/Term Legs
HOLD Legs
Path
Transition
Offset Path
Approach
0.3
6.93E-06
6.92E-06
6.93E-06
6.97E-06
Terminal
1
6.89E-06
6.89E-06
6.89E-06
6.90E-06
Enroute
2
6.89E-06
6.89E-06
6.89E-06
6.89E-06
Oceanic
4
6.89E-06
6.89E-06
6.89E-06
6.89E-06
•
System Engineering Design Example –P-3C Aircraft
Probability of annunciated loss of RNP RNAV Capability (per flight hour)
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 12
•
System Engineering Design Example –P-3C Aircraft
–
TPs 006 and 007 –Containment Continuity
􀂾
Tables show that continuity requirements are met for RNP-4 through RNP-0.3 modes and all leg types
􀂾
TP 007 was not applicable as P-3C is a dual thread system
􀂾
PMA 209 CNS/ATM Navigation and Test and Certification Teams reviewed analysis and methods used to generate results
􀂾
Updated TPM and proceeded with integration/modification effort
System Engineering Design
FRD Reference Paragraph
Test Point #
Test Point
Metric Threshold
Test Method
Met/ Not Met
Remarks
3.2.3
Containment Continuity
006
Dual-thread navigation system probability of annunciated loss of RNP RNAV capability.
< 10-4per flight hour
Qualitative Test/ Analysis
Met
Established by the Preliminary RNP Analysis for P-3C/EP-3 CNS/ATM.
007
Single-thread navigation system probability of annunciated loss of RNP RNAV capability.
< 10-3per flight hour
Qualitative Test/ Analysis
N/A
The P-3C is a dual-thread system.
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 13
Laboratory/Ground Testing
•
In-Depth Tiered Testing –Contractor and Government
–
Progressive System/Test Maturity and Complexity
–
System Integrator Lab Testing
􀂾
Manufacturer quality assurance testing
–
Platform Specific Lab Testing
􀂾
Platform unique mission/weapon systems integration testing
–
Aircraft Ground Testing
􀂾
Fully integrated system testing prior to first flight
–
Common Systems Integration (CSIL) Lab Testing
􀂾
CNS/ATM functionality/integration testing
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 14
Laboratory/Ground Testing
•
System Integrator Lab Testing -Manufacturer
–
Environmental qualification testing
–
Functional Qualification Testing (FQT)
–
Procedures reviewed and approved by PMA209 CNS/ATM Team
•
CSIL Testing -Government
–
Common lab to support all CNS/ATM integration test efforts
–
Utilize lab subject matter experts for test plan and procedures development
–
RNP/RNAV TPM compliance/integration testing
􀂾
Receiver Autonomous Integrity Monitoring (RAIM) Fault Detection Exclusion (FDE) testing
􀂾
Mission planning functionality and data integrity testing
􀂾
Full simulated motion INS/GPS testing using Spirent GPS simulator
􀂾
Regression testing
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 15
Laboratory/Ground Testing
•
Platform Specific Lab Testing -Government
–
Integration/regression testing for new system components and mission/weapon system equipment
•
Aircraft Ground Testing -Government
–
Various types of testing to ensure safety of aircraft configuration prior to first flight/military specification compliance
􀂾
Electromagnetic Compatibility/Electromagnetic Interference
􀂾
TEMPEST
􀂾
Precipitation Static
􀂾
Human Systems Integration
–
Further RNP RNAV TPM compliance/integration testing
•
All Laboratory/Ground Testing contributes to risk reduction
–
Deficiencies identified, documented and reported back to software manufacturer earlier in test cycle
–
Software manufacturer rolls corrections back into development cycle reducing the number of unplanned software builds
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 16
Laboratory/Ground Testing
•
Laboratory/Ground Test Example –P-3C Aircraft
–
TP 120 –Loss of Integrity Caution
􀂾
Flight testing of this TP not practical
􀂾
RAIM FDE testing conducted in CSIL and during Aircraft Ground Testing addressed this TP
􀂾
Used Spirent GPS Simulator to develop several scenarios that cause RINU-G’s HPL to exceed HAL
􀂾
Aircraft Ground Test sample plot shown
􀂾
Used Spirent GPS Simulator to imitate a constellation that contained satellites with pseudo-range ramp errors
􀂾
Time when HPL exceeded HAL corresponded with display of “NO RAIM” alert on CDU 7000 and “RAIM” on alert on Electronic Horizontal Situation Indicator
*HEL –Horizontal Error Limit
*HUL –Horizontal Uncertainty Limit
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 17
Laboratory/Ground Testing
•
Laboratory/Ground Test Example –P-3C Aircraft
–
TP 120 –Loss of Integrity Caution
􀂾
Results of both CSIL Testing and Aircraft Ground Testing verified that the system displays a “Loss of Integrity Caution” when HPL exceeds HAL
􀂾
Updated TPM and Proceeded with Testing Effort
FRD Reference Paragraph
Test Point #
Test Point
Metric Threshold
Test Method
Met/ Not Met
Remarks
3.2.11
Loss of Integrity Caution
120
The navigation system displays a loss of integrity caution when the HPL computed by the equipment exceeds the HAL for the current operation.
True or False
Laboratory/Ground
Test
Met
As demonstrated in the laboratory and aircraft using a Spirent GPS Simulator.
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 18
•
RNP RNAV Flight Testing
–
Approximately 70 hours of flight testing needed to fulfill RNP RNAV TPM requirements
􀂾
~20 hours dedicated to RNP RNAV profiles
􀂾
Rest of the hours can be shared w/other testing i.e. COMM, IFF
–
Measure navigation sensor accuracy
–
Measure Flight Technical Error for all RNP values
–
Evaluate enroute and terminal operations
–
Conduct GPS and RNAV non-precisionapproaches
–
Instrumentation
􀂾
Ashtech differential GPS receiver –GPS “truth data”
􀂾
Discrete Bus Formatter (DBF) II –collect MIL-STD-1553B and ARINC 429 data from RINU-Gs and CDU
Flight Testing
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 19
Flight Testing
•
Flight Test Example –P-3C Aircraft
–
TP 059 –Path Steering Requirement
􀂾
The dominant term in PSE is Flight Technical Error (FTE)
􀂾
The CDU-7000 uses fixed values for FTE based on phase of flight, which are designated as the FTE budgets
􀂾
Flight test data was analyzed to determine actual FTE (95thPercentile) values for each RNP level
􀂾
Resulting data shown below
Budgeted
Actual (95thPercentile)
RNP 0.3 FTE
0.25 nmi
0.20 nmi
RNP 1.0 FTE
0.8 nmi
0.52 nmi
RNP 2.0 FTE
1.0 nmi
0.59 nmi
RNP 4.0 FTE
2.0 nmi
1.02 nmi
Summary of FTE Values
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 20
FlightTesting
•
Flight Test Example –P-3C Aircraft
–
TP 059 –Path Steering Requirement
􀂾
All values of measured FTE < values of budgeted FTE for each respective RNP value
􀂾
Results of flight tests validated the use of the budgeted FTE values in the PSE equation
􀂾
Hence measured PSE was demonstrated to be less than the specified values for each phase of flight
􀂾
Updated TPM and Proceeded with Reporting Effort
FRD Reference Paragraph
Test Point #
Test Point
Metric Threshold
Test Method
Met/ Not Met
Remarks
3.2.6
Path Steering Requirement
059
During the certification process, the ability of the crew to operate the aircraft within the specified PSE is demonstrated.
Demonstrated PSE <= specified value.
Flight
Test
Met
Measured PSE values
were demonstrated to be
less than the budgeted
PSE values.
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 21
•
Developmental Test Results documented in a Report of Test Results (RTR)
–
Developed according to RDT&E Report Writing Handbook for Naval Air Warfare Center Aircraft Division and Training Systems Division
–
Includes populated TPM
–
Includes results and evaluation, supporting data, conclusions and recommendations
–
May be used for official programmatic decision making
•
Operational Test Results documented in COMOPTEVFOR Test Report (if applicable)
Reporting
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 22
Cert Binder Tab # Primary Document Item / Category Document Sub-Item / Category Platform Applicability􀀻 Document Availability Date (MM/DD/YYYY) 1 NAVAIR Routing Sheet RNP/RNAV 8.33kHz Channel Separation Mode S 2 PMA 209 Certification Letters RVSM Engineering Change Proposals (ECPs) Airframe Changes (AFCs) 3 Applicable Platform/ Functionality Integration Documentation Avionics Changes (AVCs) Reports of Test Results (RTRs) Developmental Test (DT) Report 4 Applicable Platform Test Reports Operational Test (OT) Report RNP/RNAV 8.33kHz Channel Separation Mode S 5 Applicable Completed Test Point Matrices (TPMs) RVSM RNP/RNAV 8.33kHz Channel Separation Mode S 6 Vendor Functionality Analysis Reports RVSM ILS Certification ILA Summary NATOPS Inputs/(DRAFT) NATOPS Maintainer Publications/(DRAFT) Navy Technical Manuals (TMs) 7 Logistical Documentation Training Inputs RNP/RNAV 8.33kHz Channel Separation Mode S 8 Applicable Functional Requirements Documents (FRDs) RVSM DD form 1494s Submitted for Approval Spectrum Allocation Documentation National Telecommunications and Information Administration (NTIA) Operational Documentation Submitted for Approval Box Level AIMS Certifications Submitted for Approval Platform Level AIMS Certifications Submitted for Approval 9 RNP/RNAV, Mode S, 8.33kHz CH Separation Only Mode S Only Applicable Certifications Joint Interoperability Test Command (JITC) Certification Submitted for Approval
•
PMA 209 CNS/ATM Test and Certification Team assemble package
•
Certification Package contents
􀂉
Platform Functionality / Integration Documentation
􀂉
Applicable Test Reports
􀂉
Applicable populated TPMs
􀂉
Vendor Functionality Analysis Reports
􀂉
Logistical Documentation
􀂉
Applicable FRDs
􀂉
Other documentation / certifications
􀂉
NAVAIR Routing Sheet
􀂉
PMA 209 Certification Letters
Certification Package
P-3C RNP RNAV Certification Package Checklist
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
√
√
√
12 Jan 07
28 Dec 06
28 Dec 06
√
√
√
2 Aug 06
18 Jul 06
25 Jul 07
√
√
√
23 Jul 07
23 Jul 07
17 Apr 06
√
√
25 Jul 07
25 Jul 07
√
25 Jul 07
√
19 Mar 07
N/A
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 23
•
Certification Review Team
–
PMA-209 Team Participation
􀂾
CNS/ATM Program Management Lead
􀂾
CNS/ATM Assistant Program Manager System Engineering
􀂾
CNS/ATM Test & Certification Team Lead
􀂾
CNS/ATM Assistant Program Manager Logistics
–
Platform Team Participation
􀂾
Platform Flight Test Lead
􀂾
Platform Logistics Point of Contact
􀂾
Platform Assistant Program Manager System Engineering
–
Other Team Participation
􀂾
Commodity Lead (Radio Program Manager (PM), Navigation Product PM, Surveillance Product PM, etc as applicable)
􀂾
Platform Integration Manager (PMA-209)
Certification Review Process
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 24
Certification Review Process
1 day
Test and Certification Lead approved Certification Package
Platform PMA Review
Review / Incorporate Comments
PMA 209CNS/ATM Leadership Review
Review / Incorporate Comments
PMA 209 Senior Leadership Review
Review / Incorporate Comments
PMA 209 Senior Leadership Approval
PMA 209 Program Manager Review
Review / Incorporate Comments
10 days
3 days
1 day
1 day
1 day
10 days
1 day
5 days
1 day
PMA 209 Program Manager Approval of Certification
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 25
Certification Approval
•
Content of Certification Letter
–
Reference to FRD
–
Reference to completed TPM
–
Reference to DT and/or OT Report (as applicable)
–
Reference to proposed NATOPS changes
–
Reference to Platform Engineering Change Proposal(s)
–
Discussion related to aircraft configuration with equipment
–
Discussion of capabilities and restrictions as applicable
–
Platform has “successfully achieved the FRD functional requirements and is hereby certified as RNP-0.3 and RNAV compliant”
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 26
•
Platform PMA receives a copy of the completed Certification Package with signed Certification Letter
•
Platform PMA issues airworthiness certification
•
Platform PMA issues the Fleet Release Letter
–
Authorizes use of functionality by Fleet
•
Platform PMA develops training requirements
Fleet Introduction
•
Platform PMA develop Concept of Operations (CONOPS) for functionality (if applicable)
•
Platform PMA develops new logistics support structure
•
PMA 209 assists as needed with Fleet introductionissues
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 27
Conclusion
•
Navy aircraft require access to performance based civil airspace to achieve effective/efficient mission accomplishment
•
Navy is a self-certifying agency for each of the CNS/ATM Functionalities
•
Navy RNP RNAV Certification Process
–
Establish RNP RNAV requirements
–
Identify platform capability shortfalls
–
Design and implement materiel solutions
–
Perform comprehensive testing of those solutions
–
Document the test results
–
Issue certification
•
Aircraft RNP/RNAV certified to date
−
P-3C/EP-3
−
C-2A
•
Several other Naval Aircraft are on the road to certification!
UNCLASSIFIED
Brief: Filename .ppt
Date: DDMMMYY
Approved for public release; distribution is unlimited.
Page # 28
Questions

gcjcdn-007

多谢多谢，支持支持

thunderland

中国民航卫星导航应用及未来发展考虑