# Presentation: 748121

## From Science Goals To Reality: The Role of Systems Engineering

- Carolyn Krebs
- Associate Director for Science Engineering
- Code 601
- May 3, 2005

**MLA**
**(planetary)**

**WFC3**
**(Earth-**
**orbiting)**

**IRMOS**
**(ground-based precursor)**

## How does systems engineering relate to science? 

- A scientist needs a measurement
- Some are primarily interested in the data and less interested in how it is obtained
- Others have excellent concepts in mind for obtaining the measurement and data, but they are content to leave the implementation thereof to engineers
- Still others are highly engaged in all aspects of the measurement from concept through design and final implementation
- The systems engineer serves as a translator to enable all three scenarios

## What does translation mean?

- With a science instrument-driven mission, it is rare that nice, tidy requirements will be handed to you with a red bow on top
- The job probably hasn’t been done before
- The measurement will likely push the edge of what is possible
- Technology readiness of some elements is often not mature
- If a similar measurement has been done before, a new implementation or extension of the heritage can be as challenging as the first time: need to figure out what transfers and innovate where it doesn’t

## What does translation mean? (cont’d)

- A crucial job of the science systems engineer is to thoroughly understand what the scientist is trying to measure and how
- Get involved very early...”glimmer in the eye” stage
- Understand the science being performed, how the scientist intends to take the data, how the data will be used, and what the key drivers are
- Ask a lot of questions that relate to an eventual implementation
- Write the answers down as placeholders for an eventual requirements document/ISAL run
- Encourage the scientist to begin defining a Design Reference Mission (DRM) for how the mission and instrument will be operated, as well as the science requirements - will become the touchstones of trade studies and eventual requirements documents

## What does translation mean? (cont’d)

- As the concept matures, the science systems engineer iterates with the scientist and discipline experts to facilitate and define the possible
- Informal trade tree sessions are key
- Allocation of the largest margins to the riskiest components from the beginning can save a lot of grief later - start “bottoms up!”
- Be prepared to work in a sometimes “unstructured” environment and to accept the translator role of facilitating (not demanding) “chaos” into “order”
- Respect that not everyone in the external world works to the standard GSFC processes: find a way to accommodate that, when necessary, that is consistent with the *intent* of the GSFC processes
- Respect that not everyone within GSFC works to the GSFC processes the same way: consider your team and the job, then tailor the approach to be consistent with them *and* the GSFC processes
- Respect that many scientists bring excellent engineering talents to the table: include them in
- Don’t forget that an instrument flies on a mission: include them in

## What does translation mean? (cont’d)

- Trades involve more than pure engineering
- Sometimes engineering has to yield to science imperatives (systems engineer facilitates with disciplines)
- Sometimes the scientist has to yield to engineering realities (scientist facilitates with science team)
- At some point, a proposal wins, and the more traditional systems engineering processes segue in
- The science systems engineer is crucial to that transition
- Bullets above continue to apply

## The role of the new Code 600 Associate Director for Science Engineering function

- To provide enabling engineering and technology support to Code 600 for instrument and mission concept development, in partnership with AETD
- Performs supervisory and career development function for engineers badged to SED
- 100% matrixed to, and co-located with, SED Divisions/Labs/Branches
- Coordinates externally matrixed engineering support from AETD
- Oversees internal SED engineering processes and practices

*The engagement of systems engineering is crucial to fulfilling this charter*

## What is being done to enhance science systems engineering?

- The “bullpen”
- Early engagement of systems engineering has been posited as crucial to sound concept development
- The scientists have also expressed a desire to have much earlier access to systems and discipline engineering skills when developing a concept
- The ISAL has expressed a desire for more maturity on entering concepts (pre-pre-ISAL)
- A “bullpen” concept, providing ready access to a systems-led team of discipline experts at “first light” of an idea, has been proposed to satisfy these mutually complementary desires
- Planned embedding of a systems engineer in each science division

## Really stories are better than viewgraphs...

- Questions for the panel members:
- Tell one story that you think really illustrates the link between science and systems engineering
- If you had one word of advice for systems engineers, what would it be?