1、Lessons Learned Entry: 1504Lesson Info:a71 Lesson Number: 1504a71 Lesson Date: 2003-07-01a71 Submitting Organization: MSFCa71 Submitted by: Lisa CarrSubject: Orbital Space Plane - Technical Rigor & Integrity Abstract: The Orbital Space Plane (OSP) Program technical content and review standards were
2、diluted as the program accelerated and budgets adjusted. Altered plans produce altered results. Address technical excellence and the increase in program risk when modifying the program to meet revisions to schedules and budgets. Description of Driving Event: Technical products were compromised by ab
3、andoning established processes, tools, and standards of performance.Lesson(s) Learned: The OSP Program technical content and review standards were diluted as the program accelerated and budgets adjusted. Technical products were compromised by abandoning established processes, tools, and standards of
4、 performance. The intent was to catch up later, but the bow wave was growing.Additionally: a. Milestone Review Deliverables OSP milestone review deliverables did not effectively communicate the work performed by the contractors to the reviewers. Contractor requirements traceability matrices did not
5、fully address the issues of requirement rationale and allocation. The number of documents delivered and the lack of clear organization for traceability of requirements hampered the milestone (SRR, SDR) review process.b. Life Cycle Cost (LCC) Estimate Requirements OSP requirements for LCC estimates w
6、ere not clearly defined. Contractors were asked to minimize LCC, but were constrained by a lack of Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-information on government facilities and government touch labor. Additionally, launch vehicle informati
7、on was provided at the “service” level in order to maintain dual vehicle compatibility.c. Synchronize Development Requirement development, analyses, and system design activities were not synchronized. No system design activity was integrating size, weight, volume, surface area, power, cabling, tubin
8、g, line layout, acoustic noise, induced environments, maintainability, life-cycle cost, etc.d. Review Integrity The System Requirements Review (SRR) was successfully held according to the schedule, yet a large part of the contractor submitted documentation was de-emphasized by the Program, and there
9、 was little or no feedback to the initiators on the comments and Review Item Discrepancies (RIDs) submitted on the documents that were reviewed. Only Program (government) developed documentation was reviewed for the success criteria. Recommendation(s): Altered plans produce altered results. Address
10、technical excellence and the increase in program risk when modifying the program to meet revisions to schedules and budgets. A fully defined requirements rationale table should provide information during a review to determine if the top level system design meets the system requirements. NASA should
11、specify contractor document formats such that the information will allow for a timely, efficient and thorough review process.It is apparent that the greater the schedule pressure, the more important it is to establish, follow, and enforce NASA and contractor Systems Engineering Management Plans. Pla
12、ns should be developed to catch-up to normally accepted review levels through the use of Interim Design Reviews. Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): a71 Exploration Systemsa71 Space Operationsa71 Aeronautics ResearchAdditional Key
13、Phrase(s): Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-a71 Administration/Organizationa71 Policy & Planninga71 Program and Project ManagementAdditional Info: Approval Info: a71 Approval Date: 2005-04-01a71 Approval Name: Lisa Carra71 Approval Organization: MSFCa71 Approval Phone Number: 256-544-2544Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
