1、Public Lessons Learned Entry: 5676 Lesson Info: Lesson Number: 5676 Lesson Date: 2011-04-18 Submitting Organization: MSFC Submitted by: Kristen Kehrer Subject: Work Authorization Traceability Abstract: A pilot conducted on the CxP Extravehicular Activity (EVA) Project as part of the Agencys Earned V
2、alue Management Capability Project identified the need to emphasize the work authorization process to ensure traceability of scope, schedule, budget, and funding agreements. Description of Driving Event: NASA focuses on funding changes via the Office of Chief Financial Officer, but doesnt track budg
3、ets via a work authorization or maintain these existing authorization documents. For the Constellation Program (CxP), the initial Program funding was documented in a Formulation Authorization Document (FAD) as the agreement between the Exploration Systems Mission Directorate and the CxP. The FAD doc
4、ument was not maintained or kept current with the funding changes for the CxP. The CxP created a Project Authorization Documents (PAD) to authorize scope, schedule, and budget, and to serve as the agreement between the CxP and each project. After the initial PAD was created, it was not updated with
5、scope changes or changes to fiscal year funding constraints. There was no direct traceability between the PADs and the FAD. The Extravehicular Activity (EVA) Project created Work Authorization Documents (WADs) to delegate the authorization of scope, schedule, and budget from the EVA Project Manager
6、to the Project Control Account Managers (P-CAMs). Since the PAD was not maintained, the WADs were not directly traceable to the PAD. Although the EVA Project used the JSC Internal Task Agreement (ITA) system to authorize work from a Mission Directorate project to the NASA center institutional organi
7、zations to perform the work, the ITA is not recognized as an authorizing document. Projects dont have an “official” authorization document of commitment between the projects and the center institutional organizations, so there is no traceability of scope, schedule, and budget from the institutional
8、organizations to the Project WADs. Also, the existing ITA system considers budget and funding to be the same, thereby creating issues for use by the Earned Value Management System (EVMS). Lesson(s) Learned: Work authorization documents need to be maintained at all levels for traceability of scope, s
9、chedule, budget, and funding agreements between mission directorates, programs, projects, and NASA center institutional organizations. Recommendation(s): Mission directorates, programs, projects, and NASA center institutional organizations need to emphasize the work authorization process to ensure t
10、raceability of scope, schedule, budget, and funding agreements. Authorization documents need to updated when approved changes are made to scope, schedule, budget, or funding to reflect the agreements between the different levels of NASA organizations. Evidence of Recurrence Control Effectiveness: Tr
11、aceability of agreed scope, schedule, budget, and funding from the mission directorate to programs to projects to NASA center institutional organizations. Documents Related to Lesson: NPR 7120.5, NASA Space Flight Program and Project Management Requirements Mission Directorate(s): Aeronautics Resear
12、ch Science Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Space Operations Exploration Systems Additional Key Phrase(s): 1.Program planning, development, and management Additional Info: Project: Extra Vehicular Activity (EVA) Project, Constellation Program Approval Info: Approval Date: 2012-03-22 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
