REG NASA-LLIS-0611-1999 Lessons Learned Evaluate Launch Vehicle and Services Requirements (1997).pdf

1、Lessons Learned Entry: 0611Lesson Info:a71 Lesson Number: 0611a71 Lesson Date: 1999-02-19a71 Submitting Organization: JPLa71 Submitted by: R. Baisley/L. Shaw Jr./D. OberhettingerSubject: Evaluate Launch Vehicle and Services Requirements (1997) Abstract: Careful planning for the acquisition of launch

2、 services and interface definition and control is an important success factor for cost and schedule constrained flight projects. Tailor the launch services contract to meet project-specific needs, and consider other elements that historically accompany this type contract, prior to finalizing the agr

3、eement. Make minimal or no changes to the basic launch vehicle after the spacecraft interfaces with the launch vehicle have been established.Description of Driving Event: Careful planning for the acquisition of launch services and interface definition and control is an important success factor for c

4、ost and schedule constrained flight projects:1. Launch service contract stipulations are sometimes retained in a subsequent contract without adequate consideration of their suitability to the applicable flight project. “Unnecessary baggage“ is a likely consequence of a rush to arrange flight service

5、s. In contracting for launch services, the Cassini project accepted the launch service contractors standard arrangement. This contract retained launch service contractor responsibility for total launch vehicle/space vehicle (LV/SV) compatibility and performance. The level of contractor involvement w

6、ith the spacecraft side of the interface, with an absence of clear decision making authority, was perceived to result in a duplication of effort, negatively influencing project morale. Independently, NASA subsequently directed JPL flight project offices to lead all efforts to ensure mission success.

7、 2. Once the launch services contract is finalized, changes that affect the hardware configuration will likely result in increased program costs. For example, Cassini launch safety analyses Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-indicated th

8、e need for changes to LV/SV hardware and interfaces.Additional Keyword(s): Configuration Management, Configuration Control, Mechanical Interface, Control Drawing, MICD, Spacecraft IntegrationReference(s): Cassini Spacecraft Assembly, Test, and Launch Operations (ATLO) Final Report, Volume I, JPL Doc

9、ument D-15701, May 15, 1998, pages 153-4.Lesson(s) Learned: 1. Determine the need for all elements that historically accompany a launch services contract prior to finalizing the agreement. Tailor the launch services contract to meet project-specific needs.2. Make minimal or no changes to the basic l

10、aunch vehicle after the spacecraft interfaces with the launch vehicle have been established. Early analyses and identification of unique requirements may preclude significant cost growth.Recommendation(s): See lesson(s) learnedEvidence of Recurrence Control Effectiveness: N/ADocuments Related to Les

11、son: N/AMission Directorate(s): N/AAdditional Key Phrase(s): a71 Configuration Managementa71 Launch Vehiclea71 Procurement Small Business & Industrial Relationsa71 SpacecraftAdditional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval Info: a71 Approval Date: 1999-03-01a71 Approval Name: Carol Dumaina71 Approval Organization: 125-204a71 Approval Phone Number: 818-354-8242Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-