REG NASA-LLIS-0919-2000 Lessons Learned Principal Investigator (PI) Mode Contingency Funding.pdf

1、Lessons Learned Entry: 0919Lesson Info:a71 Lesson Number: 0919a71 Lesson Date: 2000-09-13a71 Submitting Organization: GSFCa71 Submitted by: Bill OchsSubject: Principal Investigator (PI) Mode Contingency Funding Description of Driving Event: The Solar Radiation and Climate Experiment (SORCE) Project

2、is a PI Mode cost capped mission. During the formation of the SORCE Mission (which is a combination of the Solar/Stellar Irradiance Comparison Experiment (SOLSTICE) and the Total Solar Irradiance Mission (TSIM), two decisions were made with regards to contingency funding. First, unlike most PI Mode

3、missions in which the PI holds all the contingency funding, it was determined that the GSFC Mission Manager would hold a small amount of contingency. Secondly, as in the past with other PI Mode Missions the total amount of contingency would be approximately 15%. For the SORCE Mission, the PI held ap

4、proximately 13% and the GSFC Mission Manager held about 5%. During the Implementation Phase of the mission, new requirements have been levied on the project with regards to acceptable risk, risk mitigation, and Software Independent Verification and Validation (IV&V). Additionally, potential changes

5、at KSC with regards to commercialization of payload processing facilities and changes to the payload/launch vehicle integration process (driven by concerns of both GSFC project management and the PI) are also forthcoming. The new requirements and changes are threatening to deplete both the contingen

6、cy funds being held by the GSFC Mission Manager and the Mission unique funds held at KSC.Lesson(s) Learned: The first lesson learned from this event is that having the Mission Manager hold a certain amount of contingency funding at the project level and not by the PI is a definite positive. These co

7、ntingency funds can be used to mitigate risks that are beyond the control of the project. Examples of these risks include new requirements that are out of scope of the contract with the PI, provide funding for up to a 30 day launch delay if the launch services providers funds have been expended for

8、other unforeseen circumstances, problems in observatory level Integration and Test (I&T) for which the PI may not be able to support with his/hers contingency, etc. The second lesson learned is that the Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,

9、-amount of contingency funding held by the PI of approximately 15% is sufficient, but given the current environment regarding risk, the amount of contingency held by the GSFC Mission Manager is not enough.Recommendation(s): First, for future PI Mode missions, the GSFC Mission Manager should hold a c

10、ertain amount of contingency reserve at GSFC under his/her control. Second, the amount of contingency held at the beginning of the Implementation Phase by the PI should remain at approximately 15%, but the contingency held by the GSFC Mission Manager should be approximately 10%. This will bring the

11、total amount of contingency funding available to the project to 25%.Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): a71 ScienceAdditional Key Phrase(s): a71 Financial Managementa71 Policy & Planninga71 Procurement, Small Business & Industrial Relationsa71 SpacecraftAdditional Info: Approval Info: a71 Approval Date: 2000-10-23a71 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-,-,-