Code D Overview

1. Code D Overview Richard Weinstein Presented to Technical Standards Working Group March 9, 2004

2. CODE D RE-ORGANIZATION • Re-organization formally approved but not fully implemented • Re-badged IPAO to HQ • Moved APPL and NET training programs from Code F to Code D • Moved Inventions and Contributions Board from Code R to Code D • Position announcements pending • Budget consolidation delayed until FY05

3. OFFICE OF THE CHIEF ENGINEER Independent Program Assessment Division System Engineering Division Program and Project Management Policy and Support Division Advanced Planning, Integration, and Engineering Support Division CODE D RE-ORGANIZATION

4. Near Term Priorities • Define the relationship of Code D to Center engineering organizations • Relation to Center management, programs • Formal process for funding/evaluating work • Relation to Systems Management Offices • Standardize SMO policy, operating functions • Funding responsibility of Code D vs Center • Functional relationship with IPAO • NESC Engineering Assessments • Process for identifying issues • Priorities, coordination with other reviews

5. Near Term Priorities • Improvements in Lessons Learned System • Consolidation of separate systems • Improved identification and reporting of LL • Applying Lessons Learned pro-actively, including links to standards • Independent Trend Analysis • Process for identifying critical attributes • Process for acting on trends • Oversight of Contractors • Risk weighting of NASA requirements • Guidelines for degree of autonomy • More detailed definition of requirements

6. Near Term Priorities • Improvements to Technical Standards System • Establish Mandatory Standards • Pass down of requirements to contractors and subcontractors • Coordination of NASA Technical Standards with other agencies and industries • Revise Program/Project Management Guidelines (NPR 7120.5) • Tailored approaches for all program types • More detailed and integrated process

7. Technical Standards Issues* • Clarify role of standards • Relative to NODIS • Relative to project functional requirements • Flow-down of standards to contractors • Expand guidance for use of standards • Selection: Where required? What’s mandatory? • When to use as requirements vs guidelines • Use of equivalents? • Sources of Standards • Order of Precedence • Mandatory use of NASA Technical Standards System. Control use of Center standards? * Some issues already being addressed by Technical Standards Program

8. Technical Standards Issues* Technical Standards Selection: Engineering director Concurrence: Project Director Project Requirements Selection: Project Manager and Engineering Directorate Concurrence: Program Manager and Program Director • Controls: Standards vs Project Requirements • Standards application guidelines, processes • Integrated Project documentation of standards use • Tailoring processes: formats, criteria, limits • Independent Technical Authority for approving tailoring, waivers. Risk basis for waivers • Required consistency with Project requirements • Verify/certify that latest version of standard used

9. Technical Standards Issues* • Standards Program thrusts • Identification of core, mandatory standards • Migrate Center standards to NASA standards • Broaden consensus on NASA standards; program input, industry? • Improved technical oversight of NASA Standards. NESC role? • Assessing the financial impact of standards • Re-certifying standards on current programs and documenting deviations. Impact of migrating to NASA Preferred Standards?