2. Loran Integrity Performance Panel LORIPP Documentation Tom Gunther, Sherman Lo Second LORIPP Meeting Portland, OR September 23-24, 2002

3. Loran Integrity Performance Panel Documentation KNOWLEDGE IS OUR GOAL! and DOCUMENTATION IS OUR PRODUCT!

4. Loran Integrity Performance Panel Outline Documentation Methodology  Web based  Microsoft Project 2002 Loran Hazard Document  Threat List & Description  Mitigation Algorithms ION/ILA paper Conclusions

5. Loran Integrity Performance Panel Documentation Validity  Reference Material.  Our Results; Algorithm Documents (Cycle Check, HPL), Hazard & Fault Documents, Conference Papers.  Memory – can trace how & why we made decisions. Clarity  Description of Threat, Algorithm, ASF, etc. Reproducibility  Let others use the material we develop. Project tracking  Project status & progress reports.

6. Loran Integrity Performance Panel Current Documents Past papers, reports & references Cycle Check & HPL Calculation Algorithm Preliminary Fault Tree Design Document Threat List (Minimal Descriptions) Proposal: Each team member provide their list of documents they created or use/used as references. Tom and Sherman compile and create library. Library is updated continuously.

7. Loran Integrity Performance Panel Future Documents ASF work Project Plans (Microsoft Project 2002) Updates to Fault Tree Design &Threat List Decision documents Proposal: Each team member provide documents they created or use/used or believe are important. Tom & Sherman add to library. Work List leads status their projects.

8. Loran Integrity Performance Panel Loran Server Public Material  Dissemination of Information to the Public Concerning Loran and LORIPP  Publications Central Storage for Loran Documents  Restricted Access Central Storage for Loran Test Data Project Status Forums & Discussions URL: loran.stanford.edu

9. Loran Integrity Performance Panel Threat Documentation For each threat:  Description  Algorithm Description  Integrity Algorithm Verification  Validation of Algorithm  Assumed Conditions  Dependencies Correspond to Fault Tree

10. Loran Integrity Performance Panel ION/ILA Paper

11. Loran Integrity Performance Panel Conclusions We Need to Document Results & Analysis  Develop a Means of Creating Useful Documents Without Significant Impact on Analysis, etc.  Post Documents on Server  Available for Review & Discussion Amongst LORIPP Members  Helps Generate Documentation for the Program Conference Papers & Presentations  Means Showing the Public What We are Doing  Availability of Current Working Documents Will Aide in Generation

12. Loran Integrity Performance Panel Questions? KNOWLEDGE IS OUR GOAL! and DOCUMENTATION IS OUR PRODUCT!