1. LORIPP Meeting July 24-25, 2002 1 Implementing a LORIPP-Compliant Option in the Loran-C User Position Software (LUPS) LORIPP Meeting July 24-25, 2002 Jaime Y. Cruz Illgen Simulation Technologies, Inc. jcruz@illgen.com / 805-692-2333 x 222

2. LORIPP Meeting July 24-25, 2002 2 Background LUPS v1 delivered by Illgen to the FAA in May 2001 LUPS v2 to be delivered September 27, 2002 LUPS has been used to process flight test data –June 2001, New Jersey area, PC-104 and DDC receivers (ILA30) –August 2001, Cross-country, SatMate and DDC (Appendix A, Illgen Task 5 Progress Report, June 2002) LUPS algorithm reference: Algorithm Description Document sections of IST2001-R-247, 25 May 2001 (to be updated for v2) Purpose of LORIPP-compliant option in LUPS: To provide software that can be used to exercise LORIPP developed integrity and error models using Loran-C flight test data.

3. LORIPP Meeting July 24-25, 2002 3 LUPS Overview (1) All-in-view: Uses a preliminary solution to align the TOE of the various chains Propagation Delay Model: Millington-Pressey algorithm based on an edited version of the FCC M3 Ground Conductivity Database Fault Detection and Exclusion: –t-test to exclude large residuals –FDE protection level is the maximum single-fault position shift caused by the maximum undetectable error in each measurement –chi-square test to assess goodness-of-fit of the error models against post-adjustment residuals.

4. LORIPP Meeting July 24-25, 2002 4 LUPS Overview (2) Weighted Least Squares: Weight matrix is the inverse of the a- priori covariance matrix of observation residuals. Includes terms for: –SNR-based TOA noise at the receiver –Secondary and Master transmitter timing errors –“Other” error sources –ASF spatial error covariance model –ASF/ED temporal variation covariance model –Reference variance for global scaling of all covariances The following charts discuss the effort needed to implement the LORIPP-compliant error and integrity models

5. LORIPP Meeting July 24-25, 2002 5 Noise at the Receiver

6. LORIPP Meeting July 24-25, 2002 6 Transmitter Jitter

7. LORIPP Meeting July 24-25, 2002 7 Transmitter Offset

8. LORIPP Meeting July 24-25, 2002 8 “Other” Error Sources

9. LORIPP Meeting July 24-25, 2002 9 ASF Prediction Error Model (LORIPP)

10. LORIPP Meeting July 24-25, 2002 10 ASF Prediction Error Model (LUPS)

11. LORIPP Meeting July 24-25, 2002 1 ASF Seasonal Variation Error Model (LORIPP)

12. LORIPP Meeting July 24-25, 2002 12 ASF Seasonal Variation Error Model (LUPS)

13. LORIPP Meeting July 24-25, 2002 13 Weight Matrix

14. LORIPP Meeting July 24-25, 2002 14 RAIM (Cycle-slip Integrity Monitor) (LORIPP)

15. LORIPP Meeting July 24-25, 2002 15 Fault Detection and Exclusion (LUPS)

16. LORIPP Meeting July 24-25, 2002 16 HPL

17. LORIPP Meeting July 24-25, 2002 17 Diagnostic Output

18. LORIPP Meeting July 24-25, 2002 18 Summary Tasks involved in implementing a LORIPP-compliant option in LUPS: –Implement ASF prediction error model LORIPP ASF seasonal-variation error-model LORIPP weight matrix LORIPP RAIM (cycle-slip integrity monitor) LORIPP HPL model LORIPP diagnostic output as part of the LUPS output –Exercise LORIPP-compliant option using flight-test data –Deliver software –Deliver revised Algorithm Description Document –Deliver verification and validation test report.