REG NASA-LLIS-0691--2000 Lessons Learned Spacecraft Orbital Anomaly Report System.pdf

1、Best Practices Entry: Best Practice Info:a71 Committee Approval Date: 2000-03-13a71 Center Point of Contact: GSFCa71 Submitted by: Wil HarkinsSubject: Spacecraft Orbital Anomaly Report System Practice: Implement a positive feedback system for reporting, documenting, collecting, analyzing, and closin

2、g orbital anomaly (A departure from normal operation. An abnormality in the mission operations of a spacecraft (in orbit) information on spacecraft. An example of such a system is currently managed by Goddard Space Flight Center.Programs that Certify Usage: This practice has been used on Sampex, COB

3、E instruments and electronic boxes, ISTP instruments, etc.Center to Contact for Information: GSFCImplementation Method: This Lesson Learned is based on Reliability Practice Number PD-ED-1232 from NASA Technical Memorandum 4322A, NASA Reliability Preferred Practices for Design and Test.Benefit:The Sp

4、acecraft Orbital Anomaly Report (SOAR) System provides a single uniform, effective, and efficient computer data base for in-orbit reliability studies to identify performance trends for use in design reviews, flight readiness reviews, and in the evaluation of test, reliability, and quality assurance

5、policies.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Implementation Method:Anomaly Reporting - Immediately after the occurrence of an anomaly, the orbiting spacecrafts control center initiates the procedure shown on the SOAR Flow Diagram, Figure

6、1, by notifying the cognizant Project Operations Director (POD) or other cognizant NASA/government representative. The originator then enters all known information onto a SOAR reporting form (GSFC Form 4-29), Figure 2 and sends it to the POD. The POD assigns a person to be responsible for determinin

7、g the cause of the anomaly, corrective actions to be taken, etc. The responsible person conducts an anomaly investigation and analysis with the help, as required, of control center personnel, the system or instrument representative, the system integration contractor, the subsystem fabricator, and th

8、e Flight Assurance Manager (FAM) or the SOAR System Manager. The cause of the anomaly is determined, if possible, and corrective action is proposed, agreed to and approved by project and Center management, as appropriate. This information is entered onto the SOAR form by the responsible person. The

9、FAM or SOAR System Manager assures that the agreed-to corrective action indicated on the SOAR form takes place. When all the SOAR corrective actions have been completed, the FAM or SOAR System Manager is responsible for entering the information onto the SOAR reporting form and closing out the SOAR.

10、The completed SOAR form is distributed to the appropriate project, Flight Assurance, and other interested personnel by the SOAR System Manager. The SOAR System Manager enters information from the SOAR report into the SOAR computer data base and distributes a printout.Provided by IHSNot for ResaleNo

11、reproduction or networking permitted without license from IHS-,-,-refer to D descriptionD Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-refer to D descriptionD Yearly Summary Reports - These reports present a summary of the in-orbit reliability and

12、 performance of active spacecraft built under the management of the Goddard Space Flight Center and collectively form a continuous, published record of this performance. These reports provide a variety of statistical summaries including the total number of anomalies, the number of spacecraft over wh

13、ich the anomalies were distributed and a comparison with the anomalies of the previous year. A brief discussion is included of the condition and performance of each active spacecraft. The yearly Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SOAR re

14、ports contain a complete list of all anomalies that occurred during the year, each with the subsystem identified that caused each anomaly, the criticality, effect, and a description of the anomaly, and any corrective action that was taken. In addition, graphics show the distribution of anomalies amo

15、ng spacecraft and subsystems and comparisons of levels of criticality, effects, failure categories, and types of anomalies. Anomalies are classified and described in these summaries, lists, graphics, etc. as shown below. These classification categories are defined on the SOAR Form along with instruc

16、tions for their use.Subsystems - The spacecraft is divided into the following nine subsystems:1. Attitude Control & Stabilization2. Power3. Propulsion4. Structure5. Telemetry & Data Handling6. Thermal7. Timing, Control & Command8. Instrument (Payload)9. OtherMission Effect (Criticality) - The follow

17、ing schedule describes the impact of the anomaly on the mission:1. Negligible2. Non-negligible but Small (minor)3. 1/3 - 2/3 Mission Loss (Substantial)4. 2/3 to Nearly Total Loss (Major)5. Essentially Total Loss (Catastrophic)0 - 5% loss 5 - 33% 33 - 66% 66 - 95% 95 - 100% Anomaly Effect -Provided b

18、y IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-1. Spacecraft Failed2. Subsystem/Instrument Failed3. Component Failed4. Assembly Failed5. Part Failed6. Subsystem/Instrument Degraded7. Indeterminate8. Loss of Redundancy9. NoneFailure Category -1. Design Problem

19、2. Workmanship Problem3. Part Problem6. Environmental Problem7. Other (w/explanation)8. UnknownType of Anomaly -1. Systematic (would occur if identical equipment were operated under identical circumstances)2. Random3. Wearout (a special case of systematic)4. Indeterminate5. IntermittentAn appendix o

20、f the yearly SOAR report also presents a table of spacecraft lifetime data. Table 1. is a sample sheet of spacecraft lifetime data from a yearly SOAR report.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-refer to D descriptionD Technical Rationale:T

21、he SOAR System provides a positive feedback system for reporting, documenting, collecting, analyzing, and closing orbital anomaly information. The timely recognition and analysis of anomalies can lead to corrective measures that can restore performance and, in some cases, protect the safety of the s

22、pacecraft and its payload instruments.The yearly SOAR reports provide GSFC management, spacecraft projects and designers, as well as flight assurance personnel with both short term and long term in-orbit performance and reliability trends which can indicate areas where design improvements should be

23、made on follow-on spacecraft programs. They also can be used to evaluate the effectiveness of the prelaunch integration and environmental test programs.References:1. Procedure for the Spacecraft Orbital Anomaly Report (SOAR) System GSFC Report No. 303-PROC-013 (Rev C)2. Individual Yearly Reports - “

24、Orbital Anomalies In Goddard Spacecraft“Impact of Non-Practice: If the practice is not followed, in-orbit anomalies may not be recognized, analyzed, and possibly Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-corrected in a timely manner leading to

25、continued degraded performance and possible damage to the spacecraft. Additionally, deficiencies in designs may not be recognized and corrected in new or follow-on flight missions.Related Practices: N/AAdditional Info: Approval Info: a71 Approval Date: 2000-03-13a71 Approval Name: Eric Raynora71 Approval Organization: QSa71 Approval Phone Number: 202-358-4738Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-