Gentry Lee's Systems Engineering When the Canvas Is Blank

Understanding the Role of a Systems Engineer

Introduction to the Discussion

• The speaker introduces the session, emphasizing a blend of fun and learning while sharing diverse viewpoints.

• Reflecting on a previous talk from June 2005, the focus shifts from established engineering attributes to foundational questions in systems engineering.

Key Questions in Systems Engineering

• The primary questions guiding systems engineering are framed as "why," "what," and then "how."

• Acknowledges that being a systems engineer today requires different attributes than previously discussed, particularly focusing on intellectual curiosity.

Attributes of a Systems Engineer

Attribute #1: Science Smart

• The first attribute highlighted is being "science smart," crucial for understanding complex scientific concepts relevant to engineering tasks.

• Emphasizes the importance of staying updated with current scientific inquiries, using examples like Enceladus to illustrate evolving questions in planetary science.

Engaging with Scientists

• Encourages engineers to aspire towards understanding scientific principles rather than expecting scientists to simplify their work for them.

• Stresses that engineers must identify key questions driving missions, which often relate back to fundamental scientific hypotheses.

Importance of Understanding Scientific Context

Merging Science and Engineering

• Highlights that effective systems engineering involves merging science with engineering practices; engineers must engage deeply with scientific queries.

• Discusses how answering these questions leads to designing appropriate measurements and instruments necessary for mission success.

Practical Examples in Mission Planning

• Provides an example related to future missions (e.g., Saturn probe), stressing the need for clarity on what specific scientific questions need addressing.

• Illustrates how understanding atmospheric depth can influence mission design by determining where valuable data can be obtained.

Understanding the Surface of Venus and Engineering Challenges

The Importance of Different Sensing Methods

• The distinction between remote sensing, contact instruments, and sample collection is crucial for understanding Venus's surface. Scientists must clarify their questions to determine which method is most effective.

Prioritization in Scientific Inquiry

• The speaker emphasizes the need for a prioritized list of scientific inquiries but acknowledges that it may not be strictly ordered. Discussions should flow logically from one subject to another.

System Engineering and Cost Considerations

• A systems engineer must understand various "partials," including cost implications, when addressing engineering challenges. This knowledge helps prioritize questions based on available funding.

• Engineers often face budget constraints; they must evaluate which questions can be answered within financial limits, highlighting the importance of cost awareness in project planning.

Intellectual Curiosity in Engineering

• The speaker discusses how different engineers have varying levels of intellectual curiosity. Some thrive in structured environments while others prefer more open-ended challenges.

Panache Coefficient: Engaging Public Interest

• The concept of "panache" refers to how well a mission resonates with the public. Missions lacking this quality are harder to sell or explain to non-experts.

• A modified "Thumper Policy" suggests that if one cannot say something positive about a mission, they should remain silent. This approach encourages constructive communication about projects.

Balancing Vision and Skepticism in Engineering

• The speaker introduces the idea of being a "visionary skeptic," suggesting that successful engineers balance innovative thinking with critical analysis.

Brain Functionality and Its Impact on Engineering Thought Processes

• An overview of brain organization highlights differences between left-brain (logical, mathematical) and right-brain (intuitive, aesthetic) functions, suggesting these traits influence engineering approaches.

• Gender-specific studies suggest women may excel at multitasking due to better interconnectivity between brain hemispheres; however, such claims are met with skepticism by the speaker.

Understanding the Role of a Systems Engineer

The Dual Nature of Engineering Mindsets

• A systems engineer must balance two mindsets: intuitive vision and skeptical analysis. This duality is essential for effective communication and problem-solving.

• An anecdote illustrates this balance, where a young engineer underestimated the complexity of a Venus surface sample return mission, highlighting the need for realistic assessments alongside visionary ideas.

Characteristics of Effective Engineers

• Successful engineers should possess an "infinite initiative coefficient," meaning they proactively seek tasks without needing direction from superiors.

• The speaker praises Leon Alkali as an example of someone who embodies this characteristic, emphasizing that proactive individuals often take risks and act decisively.

Importance of Practical Experience

• Engineers should have hands-on project experience rather than solely theoretical knowledge. This practical exposure is crucial for understanding real-world challenges in engineering projects.

• The speaker discusses a PhD candidate focused on paperwork rather than practical application, stressing the importance of engaging with actual spacecraft testing to gain relevant insights.

Comprehensive Exposure Across Project Phases

• It’s vital for aspiring systems engineers to work across all phases of missions throughout their careers to develop well-rounded expertise.

• Real-world experience helps ensure that engineers can effectively manage projects and understand the complexities involved in different stages.

Navigating Chaos and Options

• Engineers must be adept at juggling multiple options simultaneously, especially when project baselines frequently change.

• A story about a young engineer highlights the necessity to remain flexible and adaptable amidst shifting project requirements, reinforcing that managing chaos is part of engineering leadership.

Understanding the Challenges of Front-End Engineering

The Importance of Defining the Journey

• Engineers may struggle with ambiguity in front-end tasks, often questioning their direction. Emphasizing that understanding the journey is crucial for defining project goals.

Separating Important Tasks from Unimportant Ones

• It's vital for engineers to prioritize and schedule their time effectively, focusing on what truly matters within limited resources.

Managing Meetings Effectively

• A humorous anecdote highlights the importance of evaluating the necessity and impact of meetings on productivity, suggesting that poor management can waste valuable time.

Multi-Dimensional Risk Analysis

• Project managers must assess various risks associated with missions, including whether a mission will occur and how to allocate resources wisely.

Domains of Risk

1. Mission Occurrence Risk

• The risk that a mission may never happen is critical; engineers must identify factors that could prevent success.

2. Development Risk

• This involves ensuring timely delivery despite challenges; engineers should maintain awareness of new and existing technologies relevant to their projects.

3. Mission Execution Risk

• Even after launch, complications can arise during operations; effective risk reduction processes are essential throughout all phases.

Mastering Margins and Reserves

• Engineers need to be precise in financial estimations while acknowledging uncertainties; an example illustrates how miscommunication about figures can lead to confusion in project planning.

Understanding Science Margin in Mission Planning

The Importance of Initial Perusal

• Emphasizes the significance of understanding the first two perusals in mission planning, suggesting that they are crucial for managing expectations and requirements.

Introducing Science Margin

• Introduces the concept of "science margin," which refers to the additional margin needed beyond basic requirements to ensure scientific quality and integrity in missions like the Europa Orbiter.

Common Pitfalls in Pre-phase A

• Discusses a common oversight among system engineers during pre-phase A: focusing on mass and power margins while neglecting to establish a structure for science margin that quantifies scientific goals.

Consequences of Insufficient Margins

• Warns that starting without adequate science margin can lead to significant drops in scientific quality, potentially jeopardizing mission viability if not addressed early on.

Reserve Allocations and Their Misunderstandings

• Highlights issues with reserve allocations, noting that many responses are based on outdated principles rather than tailored approaches for specific missions or new instruments.

Evaluating Reserves and Instrument Costs

Challenges with New Instruments

• Points out that estimating costs for new science instruments often relies solely on mass and power models, which may not accurately reflect their true complexity or needs.

Understanding Component Heritage

• Discusses the importance of recognizing component heritage when assembling parts for a mission, cautioning against assuming compatibility without thorough testing.

The Role of System Engineering Tools

Toolkit Components

• Describes a toolkit used by system engineers consisting of various models necessary for mission planning, emphasizing their strengths and limitations.

Importance of Model Validation

• Stresses the need for validation of models used in calculations (e.g., radiation dose), highlighting potential gaps in knowledge about model origins and applicability.

Advancements and Gaps in Mission Analysis

Breakthrough Techniques

• Celebrates advancements such as innovative trajectory designs (e.g., "ball of yarn") aimed at improving orbital mechanics around celestial bodies like Ganymede.

Need for Enhanced Analytical Tools

• Concludes with a call to improve tools available for continuous thrusting missions, indicating current inadequacies hinder effective mission analysis.

Why is JPL's Approach Changing?

The Shift in Work Dynamics at JPL

• The speaker introduces the lecture by reflecting on how the world for Jet Propulsion Laboratory (JPL) has changed, emphasizing a nostalgic tone with "once upon a time" to illustrate past ease of work acquisition.

• Acknowledges that competition has intensified; simply showing up and asking for work is no longer sufficient. There’s an urgent need for proactive engagement to secure future projects.

• Highlights that historically, being involved in flight projects was seen as the quickest route to recognition and advancement within JPL, indicating a shift from this traditional view.

• Warns that if talented individuals do not engage in securing new work opportunities, JPL risks becoming obsolete, marking a significant change from its previous status as a leading institution.

• Encourages employees with many years left in their careers to consider their roles beyond just flight projects and emphasizes the importance of contributing to formulation work as well.

Call to Action for Employees

• The speaker expresses confidence in the current team’s capabilities and urges them to embrace new challenges, ensuring they can maintain JPL's historical significance through active participation in all aspects of project development.