W2V2 Systems Engineering Value, Lifecycle Management, and Core Frameworks

Systems Engineering Perspectives, Processes, and Value

Systems engineering is understood through three primary dimensions: as a perspective, as a process, and as a profession.

  • Systems Engineering as a Perspective:
    • An interdisciplinary approach and means to enable the realization of successful systems.
    • Focuses early in the development cycle on defining customer needs, required functionality, and documenting requirements.
    • Proceeds with design synthesis and system validation while considering the total problem, including operations, cost and schedule, performance, training, support, testing, manufacturing, and disposal.
    • Integrates all disciplines and specialty groups into a team, forming a structured development process from concept to production to operation.
    • Considers both business and technical needs of all customers to provide a quality product meeting user needs (INCOSE 2004 / Blanchard).
  • Systems Engineering as a Process:
    • An iterative process of top-down synthesis, development, and operation of a real-world system that satisfies the full range of system requirements in a near-optimal manner (Eisner 2008).
  • Systems Engineering as a Profession:
    • A discipline concentrating on the design and application of the whole as distinct from the individual parts.
    • Examines problems in their entirety, accounting for all facets and variables while relating social aspects to technical aspects (Federal Aviation Administration [FAA] 2006).
  • Engineering Paradigm Shift:
    • Unlike traditional undergraduate engineering disciplines (e.g., Electrical, Mechanical, Civil, Chemical) that operate on rigid, legalistic rules (such as Ohm's Law),
    • Systems engineering represents a mindset and process paradigm shift—a flexible yet holistic framework applying engineering discipline using knowledge and wisdom/discernment across the entire cradle-to-grave system life cycle.

Life Cycle Cost, Defect Extraction, and Risk

Early application of systems engineering principles significantly impacts life cycle cost (LCC) commitment and error mitigation.

  • Life Cycle Cost Accrual Stages:
    • Concept Phase: Accrues approximately 8%8\% of total LCC.
    • Design Phase: Accrues approximately 15%15\% of total LCC.
    • Development, Production, and Testing: Accumulates progressively higher costs up to 100%100\% through Operations and Disposal.
  • The 20/80 Cost Commitment Rule:
    • By the time 20%20\% of system life cycle costs are actually accrued, at least 80%80\% of the total life cycle costs have already been committed through program planning and budgeting.
    • Requires early understanding of the full system concept before dollars are locked in.
  • Cost Multipliers for Defect Extraction:
    • Early Definition Phase: Baseline cost (1×1\times).
    • Developmental Phase: Cost to extract defects increases to 100×100\times–200×200\times.
    • Production Phase: Cost to extract defects increases to 500×500\times–100×100\times.
    • Defects addressed during production cost approximately 1,0001,000 times more to resolve than during initial early definition. Systems engineering mitigates the risk of hasty commitments made without study.
  • The Stool vs. Table Metaphor:
    • Three-Legged Stool (Program Management): Focuses on Budget, Schedule, and Technical Performance. These elements represent raw program facts (Knowledge).
    • Four-Legged Table (Systems Engineering / Technical Leadership): Retains Budget, Schedule, and Performance, but adds Risk as the fourth leg. Calculating and mitigating uncertainties across budget, schedule, and performance using program knowledge represents Wisdom.

The Four D's and System Complexity

Systems engineering spans four core operational phases, known as the Four D's:

  • Definition: Creation of requirements, specifications, mission views, operational views, user need statements, and detailed "shall" statements.
  • Development: Commences with the system specification and concludes with the delivery of a fully developed system.
  • Deployment: Begins upon delivery of the system into an operational theater or user environment.
  • Disposal: Covers system retirement and final disposal at end-of-life.
Evolution of System Complexity
  • Historically, early mechanical systems like the Ford Model T were considered complex for their era.
  • Modern systems display exponential complexity growth: a single modern subsystem, such as a modern automobile's GPS system (down to its circuit board controls), possesses vastly higher internal complexity than an entire historical automobile.

Systems Engineering V-Model and Life Cycle Activities

The Systems Engineering V-Model (SE V) has been the dominant framework in systems engineering since the 1980s.

  • Top-Down Decomposition (Left Side of V):
    • Proceeds from initial user needs down to detailed design and construction.
    • Primary focus is Analysis and Decomposition.
  • Bottom-Up Integration (Right Side of V):
    • Proceeds from realization, integration, verification, and validation up through operational deployment and final disposal.
    • Primary focus is Synthesis and Realization.
  • Life Cycle Activities Across Phases:
    • Conceptual Design: System-level design, requirements analysis, functional decomposition, synthesis, evaluation, writing performance specifications, and system-level design reviews.
    • Preliminary Design (System/Subsystem Level): Refined functional analysis, multiple synthesis events with active feedback loops, and preliminary design reviews.
    • Detailed Design & Development: Deep technical engagement with design teams, evaluation of prototype models, laboratory bench testing, and initial Test & Evaluation (T&E).
    • Production & Construction: Change management, configuration control, prototype modifications, and Configuration Control Boards (CCBs).
    • Operational Use Through Retirement: Incremental software updates, live-fire testing, field assessments, and feeding operational data back into design improvements.
  • Cross-Domain Application: Systems engineering principles apply continuously across the Hardware life cycle, Software life cycle, and Human System Integration (HSI) life cycle.

Hierarchy of Knowledge: Data to Wisdom

Decision-making in systems engineering relies on a defined hierarchy of knowledge assets:

  • Data: Raw uninterpreted elements.
  • Perception: Observing patterns within data.
  • Information: Contextual understanding of data relations.
  • Knowledge: Ideas and understood relationships that form the foundation for intelligent action and decisions.
  • Wisdom: The application of knowledge with discernment. Wisdom bridges the chasm beyond knowledge by anticipating future effects of current actions and enabling wise engineering choices.

Core Systems Engineering Processes, Maintenance, and Logistics

Key Systems Engineering Processes
  • Requirements Management
  • Risk Management
  • Configuration Management
  • Change Control
  • Decision Analysis
  • Interface Management
  • Implementation
  • Integration
  • Verification
  • Validation
Verification vs. Validation
  • Verification: Confirms whether the system was built right (i.e., built according to specification). Verification is demonstrated via four methods: Demonstration, Examination, Analysis, and Testing.
  • Validation: Confirms whether the right system was built (i.e., whether the delivered system fulfills actual user needs).
Maintenance Levels (O-I-D Philosophy)
  • Organizational Maintenance (O): On-site corrective and preventive maintenance performed directly on the operational asset (e.g., shipboard, flight line, or facility).
  • Intermediate Maintenance (I): Field shop maintenance, intermediate facilities, or mobile flyaway support teams.
  • Depot Maintenance (D): OEM (Original Equipment Manufacturer) factory-level repair and advanced test equipment facilities.
Military Logistics Framework (DOTMLPF-P)
  • D: Doctrine
  • O: Organization
  • T: Training
  • M: Materiel (specifically military equipment and weapons system delivery, distinguished from physical building material)
  • L: Leadership and Education
  • P: Personnel
  • F: Facilities
  • P: Policy

Analysis versus Synthesis

Analysis and synthesis represent opposite, complementary operational approaches within the systems engineering process:

  • Analysis:
    • Etymology: Derived from the Greek meaning "to loosen up" or "break apart".
    • Definition: The process of separating a complex topic, entity, or whole into its constituent component parts to gain detailed understanding (Blanchard, p. 26).
    • Lifecycle Context: Represents the left-hand side of the SE V-Model (Decomposition).
  • Synthesis:
    • Etymology: Derived from the Greek meaning "to put together".
    • Definition: Combining separate, independent constituent elements or abstract entities into a single, unified system.
    • Lifecycle Context: Represents the right-hand side of the SE V-Model (Realization/Integration).
Standard SE Process Models
  • Waterfall Model: Serial development flow incorporating feedback loops.
  • V-Model: Structural top-down analysis and bottom-up synthesis with explicit feedback links.
  • Spiral Model: Iterative development structure commonly applied in prototyping environments where final requirements are not yet fully established.
  • Standards & Frameworks: IEEE 1220, ANSI/EIA-632, and modern Model-Based Systems Engineering (MBSE).

Course Discussion Assignments

  • Discussion Board 3: Document and describe your home environment as a system of systems.
  • Discussion Board 4: Describe your selected course system project as a system of systems, and formalize this context inside your Systems Engineering Plan (SEP).