Blzzrd5's List: DAG Chapter 4 - Systems Engineering

• enables the development of engineered resilient systems that are trusted, assured, and easily modified (agile)
• knowledge supplants risk over time
• Provides the end-to-end, integrated perspective
• methodical and disciplined approach for the specification, design, development, realization, technical management, operations, and retirement of a system
• • Genesis of the Work Breakdown Structure (WBS)
• The System
• SE applies critical thinking to the acquisition of a capability
• a holistic, integrative discipline
• SE activities begin before a program is officially established
• development planning to lay the technical foundation
• Development planning is initiated prior to the Materiel Development Decision review, continues throughout the Materiel Solution Analysis phase, and transitions the knowledge (documents, tools, and related data) to the designated program
• Systems Engineer contributes to defining, establishing, and achieving affordability targets throughout the life cycle
• used as design constraints
• Technology Development
• refine requirements and to ensure affordability is designed in to the desired capability
• The Program Manager, with support from the Systems Engineer, develops program office cost estimates reflecting should cost opportunities and plans
• should cost estimate as a tool to
• Influence design trades
• Manage all costs
• Manage the product’s final unit and sustainment cost
• Provide incentives for both of the parties
• 16 processes: eight technical processes and eight technical management processes
• Stakeholder Requirements Definition
• Requirements Analysis
• Architecture Design
• Implementation
• Integration
• Verification
• Validation
• Transition

28 more annotations...

• Understanding the use and value of SE specifications and standards is fundamental to establishing, executing, and maintaining disciplined SE processes
• there is no one-size-fits-all optimal program structure
• The Systems Engineer leads or is a key enabler in the planning and execution of the program's technical approach
• proactively seek experience from similar past and current programs

2 more annotations...

• help Program Managers develop, communicate, and manage the overall systems engineering (SE) approach
• For Major Defense Acquisition Programs (MDAPs), the Program Manager should formally charter a SE Working-Level Integrated Product Team (WIPT), led by the Systems Engineer, to assist in developing and monitoring SE activities as documented in the program SEP
• draft formal SEP be available for the pre-Engineering and Manufacturing Development (pre-EMD) review
• describes the integration of SE activities with other program management and control efforts
• (IMS)
• (IMP)
• (WBS)
• (TPMs)
• (RMP)
• Government SEP should accompany the Request for Proposal (RFP) as guidance to the offerors
• Systems Engineering Management Plan (SEMP), which is the contractor-developed plan for the conduct, management, and control of the integrated engineering effort
• SEP should define the “who, what, when, why, and how” of the SE approach
• program organization with roles and responsibilities,
• key activities, resources, tools, and events that support execution of the SE technical processes and technical management processes
• event-driven technical review approach
• Key design considerations and criteria (see DAG section 4.3.18. Design Considerations) should be listed in the mandatory table as applicable
• SE tools and other enablers

15 more annotations...

• actively pursue Memoranda of Agreement or Memoranda of Understanding (MOA/MOU) with companion programs
• enterprise
• the organization or cross-organizational entity supporting a defined business scope and mission
• The Systems Engineer can also assist with enterprise strategic planning and enterprise investment analysis
• shared with the organization’s senior line management, and tend to be more entrepreneurial, business-driven, and economic in nature in comparison to the more technical nature of classical systems engineering
• In some cases, enterprise considerations have been articulated as standards and certification requirements
• systems of systems (SoS)
• a set or arrangement of systems that results when independent and useful systems are integrated into a larger system that delivers unique capabilities
• Comparing Systems and Systems of Systems
• the aggregation of the independent and useful systems
• management
• management
• levels of complexity
• funding
• integrated capabilities
• Multiple system life cycles
• asynchronous life cycles
• enabling flow of data, control, and functionality
• Four Types of Systems of Systems
• Four Types of Systems of Systems
• Directed
• SoS is engineered and managed to fulfill specific purposes
• centrally managed
• recognized objectives, a designated manager, and resources
• Acknowledged
• constituent systems retain their independent ownership, objectives, funding, development, and sustainment
• cooperative agreements
• Collaborative
• interact more or less voluntarily
• Collaborative
• lacks a central management authority
• Virtual
• Large-scale behavior emerges
• relatively invisible, self-organizing mechanisms

32 more annotations...

• actual system performance is verified to meet the requirements in the system performance specification and is documented in the system functional baseline
• System Verification Review (SVR)
• FCA can be found in MIL-HDBK-61A
• SVR and FCA are sometimes used synonymously when the FCA is at the system level
• SVR/FCA is used to
• • Assess whether system development is satisfactorily completed
   
  • Prepare the system for OT&E (see DAG Chapter 9 Test and Evaluation)
   
  • Confirm that the product baseline meets the requirements of the functional baseline and therefore has a high likelihood of meeting the warfighter requirements documented in the Capability Development Document (CDD) and/or Capability Production Document (CPD)
   
   
• Program Manager responsibilities
• Systems Engineer responsibilities
• suggested SVR/FCA products and associated review criteria.
• readiness assessment tool for SVR preparation is the DoD SVR Checklist.
• Documented achievement of functional and/or allocated baseline requirements through the appropriate documented verification method
• reviewed and verified
• Assessment that the documented system product baseline for the initial production system has a low risk of operational test failure during OT&E
• risks (including ESOH) have been accepted at the appropriate management level
• established and sufficiently resourced
• plan/schedule

14 more annotations...