The document discusses NASA's Systems Engineering Excellence Initiative which aims to improve systems engineering capabilities across the agency. It outlines several needs including consistency in systems engineering approaches, an agency-wide framework of best practices, common terminology, and a basis for assessing capabilities. The response is to establish a Systems Engineering Working Group and Engineering Management Board to develop and implement a common framework. This is expected to enable excellence in systems engineering and foster more effective communication and collaboration.

1. NASA Engineering of Systems
Excellence Initiative
S J Kapurch
Program Executive Officer
Systems Engineering
7 Feb 2007

2. Purpose
Overview
– OCE Initiatives
– Policy in context of other efforts
Multi-Faceted Approach
– Highlight key elements
– Integration of Related Efforts

3. The Environment
Acquisition streamlining of the 90’s
– The Good, the Bad, & the Ugly
Nature abhors a vacuum
– ISO-15288, IEEE-1220, EAI-632=Standards quagmire
Maj. Gen. Craig Cooning, the Air Force's Director of
Space Acquisition at the Pentagon
– "We walked away from some of the things that served us very
well. When you did away with that, you did away with the
common language that engineers spoke. So, what we are trying to
do is to reinstate those processes that served us well--not to go
overboard--but to do it selectively." (21 October 2004)
Like other organizations, NASA tossed out many processes &
procedures during acquisition streamlining.

4. System Engineering Issues
– Failure Review Boards have consistently pointed to lack of SE
CAIB
– “Organizational causes of this accident … cultural traits … detrimental to safety …
allowed to develop including: …reliance on past success as a substitute for sound
engineering practices …” -CAIB, Executive Summary
Other Recent NASA Projects
– “…., the root cause was not caught by the processes implemented by the project
– CDR was too high level to adequately assess design…too little time to perform an
adequate assessment
– ….Although training was widely available, poor requirements are still common
– “… likely cause for the failure of the system was a faulty design …switches …
improperly installed on a circuit board”
– “ the mishap occurred mainly because of failures in SE process….and is known to
be the cause of several recent failures”

5. Complexity is a Major Issue
Integration of systems create a major
problem with complexity
– As more systems are added, the interfaces
grow in a non-linear fashion
– Many of the existing systems were not built
for these interfaces
– Conflicting or missing interface standards
make it hard to define interface interactions
Systems engineering must deal with this
complexity
– End-to-end systems engineering is needed,
including “reengineering” of legacy systems
– Robust M&S, verification and validation testing
are A must

6. Specific Needs
Need: Consistency in basic approach to systems
engineering.
Need: Agency wide framework of recognized best
practices that guides the engineering of program
and project products and capabilities.
Need: Common systems engineering terminology and
definitions to enhance communication and
collaboration among engineering teams across the
Agency and with external partners and customers.
Need: Basis for assessing and continuously improving
systems engineering capabilities.

7. Response: Systems Engineering Excellence
Initiative
• Systems engineering working group (SEWG)
- POC at centers and MD’s for SE efforts
- Plan, develop and execute the Initiative.
- Coordinate project products within members’ centers
• Engineering management board (EMB)
- provide project oversight and approvals.
• Mission directorates & centers
- Provide members of the SEWG.
- Provide needed support for reviews, pilots and assessments.
- Verify suitability for accomplishing programs and projects.
• Customers
• NASA engineering community
• Advanced technology teams
• Payload developers
• OCE
• MD and Center management
• Program and project managers
• External partners

8. Response: The License. . .
TERMS of
SEWG CHARTER REFERENCE
The SEWG:
“… This
Is chartered by EMB, Framework will
in support of Strategic describe the
Plan to develop and requirements for SE
implement a common
processes required
framework for
systems engineering to engineer products
in NASA and capabilities …”

9. Goals
Stimulate and enable the development and advancement of a sound systems
engineering capability necessary for success in fulfilling NASA Mission’s
Ensure continuous improvement of the NASA engineering workforce
through relevant education, training and work experiences.
Ensure sound and effective discipline and systems engineering
Agency-wide.
Provide value-added cross-cutting products and services that enable the
infusion of technology, knowledge, and capabilities to support innovation
in engineering and push the state of the art.
Increase participation, membership, and leadership in recognized
national and international engineering organizations.
Integration of Software.

10. Expected Benefits
Enable and foster excellence in systems engineering
capabilities to:
– Formulate feasible program and project concepts.
– Deliver required products and services to NASA customers.
– Make timely acquisition of enabling products and critical technologies.
– Reduce risk in system development and deployment.
Enable more effective communications and
collaboration within NASA and with external partners
and customers.
Conduct effective assessment and improvement of
systems engineering capabilities.
Change the culture to represent the needs of one NASA,
and not the unique needs of a particular Center.
Develop strategic focus for advanced engineering
environments.

11. What is Systems Engineering
“Common People Separated by a
different language” Winston
Churchill