Lec_1_Intro_Sys_Eng_2024

Page 1: Introduction

Lecture Details

• Course: ENG PHYS 3SP3 - Space Systems Engineering

• Date: Wednesday, Sept 4th, 2024

• Institution: McMaster University, Engineering Physics

Page 2: Instructor Introduction

Instructor Background

• Name: Liam Flannigan

• Position: Ph.D. Candidate, McMaster University

• Research Work: Ground-to-satellite transmitter and receiver development using nonlinear optics

• Experience: Affinite Instruments, Canadian Space Agency, Canadian Nuclear Laboratories, worked on McMaster’s first CubeSat.

Page 3: Course Introduction

Overview of Course Purpose

• Prior experience lacked exposure to 'real' engineering.

• Doctorate experience with CSA and MDA led to interest in Systems Engineering.

• ENG PHYS 3SP3 serves as an introduction to space systems engineering and essential topics for complete space missions.

Page 4: Course Introduction

Stakeholder Interaction

• Worked on PRISMA satellite at CSA focused on hyperspectral imaging.

• Noteworthy interaction with various stakeholders such as government bodies, academia, and taxpayers.

Page 5: Technical Requirements

Project Management Insight

• Managed technical requirements for a subsystem amidst larger projects.

• Importance of meeting strict requirements and validation at each step.

Page 6: Lessons from Undergrad

Key Takeaways

1. Big Picture Awareness: Your work contributes to a larger solution.

2. Requirements Importance: Requirements guide engineering processes.

3. Verification Necessity: Prove functionality from the beginning, not as an afterthought.

Page 7: Course Topics

Included Topics

• Systems Engineering Introduction

• Requirements Engineering, Verification, and Validation

• Launch Environment/Thermal

• Satellite Systems and Interfaces

• Orbital Mechanics

• Satellite Communications

• Spacecraft Dynamics

• Satellite Attitude and Orbit Control Systems

• Earth Observation/Remote Sensing

• James Webb Space Telescope

Page 8: Course Goals

Learning Objectives

• Grasp key concepts in systems engineering for space systems.

• Understand the process from stakeholder needs to functioning system.

• Valuable for future capstone projects and satellite operation knowledge.

Page 9: Textbook and References

Recommended Resources

• NASA Systems Engineering Handbook Rev2 - Available online.

• NASA Systems Engineering Course Material - Additional online materials to be posted.

Page 10: Additional Textbooks

Useful References

1. Applied Space Systems Engineering (2009)

2. Spacecraft Systems Engineering (2011)

3. Orbital Mechanics for Engineering Students (2013)

4. Space Mission Engineering: The New SMAD (2011)

Page 11: Course Structure

Format

• One lecture weekly: Wednesdays 7:00 - 10:00 PM.

• In-person only, no recorded sessions; materials posted on A2L.

• Regular assignments are the primary assessment metric.

Page 12: Homework and Exam Structure

Assessment Overview

• Homework: 65% - Weekly, dropped lowest score for grading.

• Final Exam: 35% - In-person, specific contents reviewed in advance.

Page 13: Missed Work Policy

MSAF Guidelines

• MSAF for homework counts as one ungraded assignment.

• Other missed work without valid reasons results in a grade of 0%.

• Contact faculty for long-term absence considerations.

Page 14: Lecture Overview

Key Topics

• What is a System?

• What is Systems Engineering?

• Overview of NASA Project Life Cycle.

Page 15: Lecture Highlights

Lecture Continuation

• Delves into various concepts and definitions related to systems and engineering.

Page 16: What is a System?

System Types

• Focus on open, man-made physical systems including:

  • Power Systems

  • Transportation Systems

  • Communications Systems

  • Space Systems

Page 17: Definition of a System

System Components

• Definition: Combination of interacting elements to achieve a purpose.

• System Boundary: Separates system of interest from external environment.

Page 18: Purpose of a System

Mission Focus

• Provides solutions to defined problems or needs.

• Starts with a clearly defined mission by the customer.

• Systems engineering translates stakeholder needs into technical language.

Page 19: Vehicle System Example

Car as a System

• A car as a system combines various subsystems for personal transportation.

• Interacts within an established transportation framework.

Page 20: Operational Environment of a Car

Environmental Factors

• Interaction with users, infrastructure, and conditions (traffic, weather, etc.).

Page 21: Different Mission, Different System

Comparison of Cars

• Formula 1 car vs. sedan demonstrates different operational needs and constraints.

Page 22: Functional vs. Physical Description

System Descriptions

• Functional: Describes what the system does.

• Physical: Describes how the system is implemented.

Page 23: System vs. Subsystem

Independence

• A car operates as a complete system; an engine serves as a subsystem that requires others for function.

Page 24: Functional Description of a Car

Functions of Personal Transportation

• Functions include safety, propulsion, and cargo management, among others.

Page 25: Subsystem Breakdown of a Car

Detailed Components

• Breakdown into subsystems and further detail components (e.g., engine, transmission).

Page 26: Implications of Definition

Engineering Perspective

• Systems are engineered to meet imposed constraints.

• Systems engineering expands definition beyond final product to include total operational requirement.

Page 27: Complete System Definition

System Components

• Includes more than hardware/software; also involves development, support, and operational products.

Page 28: Broader Automotive System

Context Consideration

• A car is part of a more comprehensive automotive system for effective production and operation.

Page 29: System Life Cycle

Phases Overview

• Progresses from conception through realization and utilization to retirement.

Page 30: Life Cycle of a Car

Phases Explained

• Conceptualization: Identify market demands.

• Realization: Design and produce.

• Utilization: Sales and maintenance.

• Retirement: End of life considerations.

Page 31: Recap of Systems

Key Points

• Definition, operational environment interaction, mission-focused purpose, lifecycle phases, and interrelated elements.

Page 32: Systems Engineering Overview

Engineering Focus

• Exploration of systems engineering's relevance to comprehensive design management.

Page 33: Definition of Systems Engineering

Understanding Systems Engineering

• Combination of technical problem-solving and management across the system lifecycle.

Page 34: What is Systems Engineering?

Approach and Methodology

• Top-down design approach incorporating stakeholder goals, requirements definition, and iterative evaluation.

Page 35: Difference with Other Disciplines

Comparative Overview

• Systems engineering vs. R&D, design engineering, and product development in focus and scope.

Page 36: Scope of Systems Engineering

Interdisciplinary Aspects

• Overlap with project management aims to deliver quality systems by managing costs and schedules.

Page 37: Value of Systems Engineering

Importance of Planning

• Early decisions influence costs; strong processes mitigate risks and enhance project success.

Page 38: Systems Engineering Benefits

Importance of Structural Guidance

• Reduces waste, ensures cohesive system integration, and enhances project effectiveness.

Page 39: Complexity of Systems

Problem Solving

• Emphasizes difficulty in starting design for complex, large projects without a structured approach.

Page 40: Tailoring Systems Engineering

Contextual Application

• Systems engineering should be adapted to project needs and complexity for effective application.

Page 41: Project Life Cycle Overview

Definition

• Timeline outlining phases, activities, and key decision points.

Page 42: NASA Project Life Cycle

Phases Breakdown

• Overview of each phase from Concept Studies to Operations and Sustainment, including outcomes and reviews.

Page 43: Project Phasing Structure

Key Review Phases

• Importance of reviews and decision gates for project readiness in NASA's lifecycle framework.

Page 44: Systems Engineering Collaboration

Shared Responsibilities

• Collaboration roles throughout lifecycle phases among systems engineering, management, and project management teams.

Page 45: Pre-Phase A Overview

Initial Steps

• Focus on concept studies, stakeholder identification, and formulation of mission requirements.

Page 46: Understanding Stakeholders

Stakeholder Definition

• Define groups interested in or affected by the project, including customers and other involved parties.

Page 47: Expectations of Stakeholders

Capturing Needs

• Importance of elucidating stakeholder expectations for guiding project direction.

Page 48: Problem and Solution Domains

Boundary Definition

• Distinguishing between the organizational needs in the problem domain and potential solutions in the solution domain.

Page 49: Needs, Goals, Objectives

Definitions

• Clear differentiation among need (what the customer wants), goals (what needs to be accomplished), and objectives (specific target outputs that must be measurable).

Page 50: Needs Example: CASMS

Specification Example

• Detailed needs, goals, and objectives for Canadian Arctic Shipping Monitoring System clearly stated.

Page 51: Measures of Effectiveness

Measurement Metrics

• Framework for judging system mission success from stakeholder perspectives, including specific measurable metrics.

Page 52: Constraints Overview

Limitations

• Constraints that shape design and operational boundaries: technical, performance, resources, cost, and regulatory restrictions.

Page 53: Concept of Operations (ConOps)

Operational Strategy Document

• Outlines how a system will be used to achieve its objectives and captures stakeholder expectations.

Page 54: Contents of ConOps

Structure Details

• Organized sections crucial to the document reflect stakeholders and project specifics.

Page 55: ConOps Operating Concept

Interaction Overview

• Visual representation of operational components in system implementation for effective communication.

Page 56: Mission Scope and Boundary

Visual Tools

• Use of charts and timelines to clarify mission and system scope.

Page 57: Operating Environment of ConOps

Interfaces Consideration

• Understanding how the system interacts with its operating environment and other stakeholders.

Page 58: Operations Concept Timeline

Sequencing Overview

• Detailed operation sequence from detection through monitoring and action process.

Page 59: Mission Requirements

Definition Capture

• Formal capturing of mission requirements defining the capabilities and performance parameters needed.

Page 60: CASMS Mission Requirements Examples

Specification List

• Detailed examples that outline specific mission requirements for the CASMS project.

Page 61: Phase A Development

Initial Development Tasks

• Development of system concepts, requirements, project planning, and trade studies.

Page 62: Iterative Process Framework

Requirement Relationships

• Explanation of the iterative process for developing system concepts, architectures, and mission requirements.

Page 63: Functional Decomposition

Task Breakdown

• Logical description of operations through a functional hierarchy.

Page 64: System Architecture

Structural Overview

• Defines the organization of system elements and their functions through top-level structural design.

Page 65: Feasibility Investigations

System Evaluation

• Diverse architectural examinations to ensure effectiveness in terms of feasibility and cost in CASMS.

Page 66: System Requirements Definition

Requirement Specification

• Clearly defined system requirements as foundation for design and evaluation of operational capabilities.

Page 67: Flow-down Process

Requirement Cascading

• System requirements derived from mission requirements through iterative communications with stakeholders.

Page 68: Phase B Focus

Design Development

• Establish system design aligned with requirements and initiate prototyping efforts to mitigate risk.

Page 69: Phase C Requirements

Detailed Design Documentation

• Completion of comprehensive detailed designs, drawing documentation, and addressing outstanding design challenges.

Page 70: Phase D Overview

AIT Process

• Focuses on Assembly, Integration, Testing, and launch; crucial to prove system meeting all specified requirements.

Page 71: Verification and Validation

Distinction

• Differentiates between proving compliance with requirements vs. meeting stakeholder expectations across the life cycle.

Page 72: Phase E Focus

Operational Deployment

• Lifecycle activities focusing on execution, maintenance, and continuous feedback during system operation.

Page 73: Phase F Considerations

Closure Activities

• Completes lifecycle with system retirement, lessons learned, and documentation for future projects.

Page 74: Life Cycle Summary

Critical Lifecycle Phases

• Recap of the necessity for early systems engineering impacts and the value added during project planning stages.

Page 75: Lecture Summary

Key Takeaways

• Systems, engineering approach, stakeholder needs, phases and lifecycle importance highlighted throughout the lecture.

Page 76: Assignment Information

Assignment 1 Details

• Description of system required, due next week via A2L, due September 11th, 11:59 PM. Facilitates understanding of system components and lifecycle.