Product-based Systems Engineering RequirementsProduct-based Systems Engineering Requirements Brian...

NDIA9th Annual

Systems Engineering Conference

Product-basedSystems Engineering

Requirements

Brian Shaw, The Aerospace CorporationLarry Pennell, Sparta, Inc.

Dave Davis, USAF SMC/EAE

25 October 2006

2

Agenda

• Background– Space System Acquisition Challenges– SMC Specifications and Standards Program

• SMC Approaches to Systems Engineering (SE)– SE Processes and Requirements Vision– Development of “SE Products and Requirements”

• SE Products and Requirements– Sample Products and Requirements

• Summary and Conclusions

3

Agenda





4

Space Systems Acquisition Challenges

• Space capabilities are essential for successful military operations– Requires:

• high reliability• assured delivery of mission data

• Many new space programs exist; success hampered by– Industry-wide shortage of systems engineers– Serious lack of acquisition experience at SMC

• Congressional confidence in space systems acquisition is low• Space programs are more complex than ever…

– Hardware/software, including COTS infusion– System integration– System-of-system/Family-of-systems interoperability

5

Government Prime Contractor

A&AS

Sub-Ktrs

SEP SEMPEngineering Engineering InteractionInteraction

Specs & Standards

Systems Engineering Framework

• Defines SE Relationship

• Levels playing field in bidding process

• Establishes what Govt considers to be an acceptable level of quality

• Requires Government control/oversight

Standards set expectations for

Contractor technical and management

activities

ContractContractContract:

6

New SMC S&S Policy

• Issued by Lt. Gen. Michael Hamel11 July 2006

• Establishes specifications and standards as an integral element of SMC acquisition processes

• Applies to all new development, acquisition and sustainment contracts, including new contracts for legacy programs

• Contractual compliance through the supplier chain, as appropriate

7

SMC Specs & Standards Initiative

• SMC Specs & Standards Initiative– SMC initiative to apply specs & standards as key

element of acquisition practices and toolset• Prior to acquisition reform, SMC used military

specifications & standards to specify contractual and prescriptive requirements

• Re-institute standards responsible for mission assurance– Select group of military and industry space standards – Define government’s expectations and specify proven

technical practices

8

S&S Status

• Revised SMC S&S List published 8/9/2006:65 essential documents– Military, international, and industry

standards, and Aerospace Corp reports – Updated to reflect current best practice

• Example standard:Systems EngineeringRequirements and ProductsThe Aerospace Corporation Report, TOR-2005(8583)-3, Rev A

- Contractually binding requirements defined in terms of required SE products and required attributes of those products

- Consistent with existing industry standards (ANSI/EIA 632 and IEEE 1220)

– Additional updates to current document versions

Compliance Documents for SMC Acquisitions

Approved 9 August 2006

Col James HorejsiUSAF SMC/EA

9

Collaboration Ensures Consistency

Space Industrial Base Council

Specs & Standards Working Group

Mission Assurance Improvement Task

Force

Specs & Standards Working Group

National Security Space Integration

SMC / NROCollaboration

“Bring Senior-Level Attention toSpace Industrial Base Issues on a Recurring Basis

and Develop ‘Actionable’ Recommendations to

Industrial Base Issues.”

“Identify and implement areaswhere a common SMC / NRO approach

provides benefit.”

Co-Chaired by DoD EA Space & DNRO

Co-Chaired by NRO DDSE & SMC/EA

• Ensure sound technical practices applied on NSS programs

• Ensure NSS community takes a consistent approach in the application of specs & standards

• SMC; NSSO; NRO; Navy; NASA; MDA; NOAA

• Establish a common set of preferred specifications and standards

• Quarterly interchange meetings• Joint insight into formal standards rationale

and approval processes• SMC; NRO

10

SMC Specifications and Standards Functional Areas

MANAGEMENT• Configuration Management• Design Reviews• Manufacturing Management /

Producibility• Parts Management• Product Assurance• Program Management• Risk Management• Systems Engineering• Safety • Subcontract Management

TECHNICAL• Electrical Power, Batteries• Electrical Power, Solar• EMI / EMC• Environmental Eng & Cleanliness• Human Factors• Interoperability• Logistics• Maintainability• Mass Properties• Moving Mechanical Assemblies• Ordnance • Pressure Vessels• Parts, Materials & Processes• Reliability • Security• Software Development• Structures• Survivability• Test, Ground• Test, Space

11

Agenda





12

SMC’s Vision and Perspective

• Compliance document for contractor– Requirements for contractor’s SE program– Characteristics for technical areas important to SMC– Industry standards for guidance, not direction

• Requires associated handbook and tools

• Assumes a knowledgeable and intelligent audience

• Must be priceable – concise without redundancy

13

Author/Team Goals/Vision Consensus

SE Requirements and Product standard should…

• Cover entire life cycle – ‘lust to dust’• Be consistent with DAG*, Mission Assurance initiatives, etc.• Meet SMC’s needs for enforceability on contract

– Consist of a specification plus a suite of tools such as handbook, CDRLs, and DIDs

• Be supportive of 5000.2, Directive 7, and NSS 03-01• Be systems engineering product oriented• Integrate and/or use any existing products, such as those

developed under Mission Assurance initiatives

* Defense Acquisition Guidebook

14

Relationship of SE Process Documents

Defense AcquisitionGuidebookEIA 632/IEEE 1220SE Models and

ProcessesSMC SE

Handbook

MilitaryStandards Mil-Std 499B (Draft)Mil-Std 499A

DoDD 5000.2DoDD5000.1

DODAcquisition Policy NSS 03-01

DraftSE Standard

Mil-Std 499C (Draft)Aerospace TOR

SE Requirementsand Products

Aerospace TORRevision A

NavySE Guidebook INCOSE

EIA 632 Revision

Ever-growingSpace AcquisitionExperience base

Periodic revisionis anticipated

15

Example SE Process

Requirements Analysis- Analyze Missions, Concepts and Environments- Identify Functional Requirements- Define/Refine Performance - Define/Refine Performance Design Constraints

Functional Analysis & Allocation- Decompose to Lower-Level Functions- Allocate Performance and Other Limiting Requirements to All Functional Levels- Define/Refine Functional Inter faces (Internal/External)- Define/Refine/Integrate Functional Architecture

Synthesis- Transform Architectures (Functional to Physical)- Define Alternative System Concepts, Configuration Items and System Elements- Select Preferred Product and Process Solutions- Define/Refine Physical Interfaces (Internal/External)

System Analysis &

Control

Requirements Loop

Design Loop

Trade-Off StudiesEffectiveness AnalysesDesign AnalysisRisk ManagementConfiguration MgtInterface ManagementData ManagementPerformance MeasurementTechnical Reviews

Verify

Process OutputArchitecturesSpecificationsEngineering DesignDecision Database

Process InputCustomer Needs/Objectives/CapabilitiesTechnology BaseSpecifications & Standards RequirementsRequirements from Prior Development EffortProgram Decision Requirements

16

SE Process – Typical Vee depiction

Define Concepts &Architectures AndValidation Plans

Develop & ManageSystem RequirementsAnd Verification Plans

Develop & Manage CIRequirements AndVerification Plans

Perform Design AndPrepare Inspection Plan

Fab And Assemble “CodeTo” And “Build To”

Documentation

Inspect To “Build To”Documentation

Asesemble Cis AndPerform CI Verification To

CI “Design To” Specs

Integrate System AndPerform SystemVerification To

Performance Specs

Demonstrate And ValidateSystem To Validation Plan

Integ

ratio

n &Ve

rifica

tion

Deco

mpos

ition

& De

finitio

n

Validate System

Verify System

Verify CIs

VerifyUnits

Systems EngineeringDomain

Component / S/WUnit EngineeringDomain

17

Requirements Analysis and Validation

Section 4.2.1

Input

Functional Analysis, Allocations and Validation

Section 4.2.2

Synthesis

System Element Design Solution and Validation

Section 4.2.3

Design for Implementation, Deployment, O&S

Section 4.2.4

System Analysis & Control

Tradeoff AnalysesSection 4.2.11

Requirements, Functional, and

Design AnalysesSections 4.2.1 thru 4.2.4

Systems Engineering ManagementSection 4.2.12

Apply Across System LifecycleSection 4.2.13

Detailed RequirementsSection 5

Requirements Baseline

Functional Architecture

Allocated Baseline

Design Release Baseline

Design Verification& Validation

Sections 4.2.7 & 4.2.8

Effectiveness, Cost, Sched, Risk

AssessmentsSection 4.2.10

Implementation(Fab/Code) or Buy

Product Configuration Baseline

Systems EngineeringProgram Foundation

(See Appendix A)

Acquisition Milestone Decisions & Capability Needs

DoDI 5000.2, NSSAP 03-01, CJCSI 3170.01C

Requirements Loop

Design Loop

Verify/Validate Loop

IntegrationSection 4.2.6

Transition/ Deployment

Section 4.2.9

Section 4.2.5

Requirements Analysis and Validation

Section 4.2.1

Input

Functional Analysis, Allocations and Validation

Section 4.2.2

Synthesis

System Element Design Solution and Validation

Section 4.2.3

Design for Implementation, Deployment, O&S

Section 4.2.4

System Analysis & Control

Tradeoff AnalysesSection 4.2.11

Requirements, Functional, and

Design AnalysesSections 4.2.1 thru 4.2.4

Systems Engineering ManagementSection 4.2.12

Apply Across System LifecycleSection 4.2.13

Detailed RequirementsSection 5

Requirements Baseline

Functional Architecture

Allocated Baseline


Design Verification& Validation

Sections 4.2.7 & 4.2.8

Effectiveness, Cost, Sched, Risk

AssessmentsSection 4.2.10

Implementation(Fab/Code) or Buy


Systems EngineeringProgram Foundation

(See Appendix A)

Acquisition Milestone Decisions & Capability Needs

DoDI 5000.2, NSSAP 03-01, CJCSI 3170.01C

Requirements Loop

Design Loop

Verify/Validate Loop

IntegrationSection 4.2.6

Transition/ Deployment

Section 4.2.9

Section 4.2.5

SE Process, Requirementand Baseline Flow

Requirements BaselineRequirements Baseline

Functional ArchitectureFunctional Architecture

Allocated BaselineAllocated Baseline





18

Agenda




• Summary and Conclusion

19

Table of Contents (1 of 2)

4. GENERAL REQUIREMENTS4.1 SYSTEM ENGINEERING PROCESS APPLICATION

4.1.1 SUPPORT TO THE CAPABILITY NEEDS PROCESS4.1.2 SYSTEM LEVEL CONSTRAINTS, CONCEPTS AND ARCHITECTURES

4.2 SYSTEMS ENGINEERING REQUIREMENTS4.2.1 REQUIREMENTS ANALYSIS AND VALIDATION4.2.2 FUNCTIONAL (LOGICAL) ANALYSIS4.2.3 SYSTEM ELEMENT DESIGN SOLUTION AND VALIDATION4.2.4 DESIGN FOR IMPLEMENTATION, DEPLOYMENT, OPERATIONS, AND SUPPORT4.2.5 IMPLEMENTATION4.2.6 INTEGRATION4.2.7 DESIGN SOLUTION VERIFICATION4.2.8 DESIGN SOLUTION VALIDATION4.2.9 TRANSITION (DEPLOYMENT) ANALYSIS AND ASSESSMENT4.2.10 ASSESSMENTS OF SYSTEM EFFECTIVENESS, COST, SCHEDULE, AND RISK4.2.11 TRADEOFF ANALYSES4.2.12 MANAGEMENT OF THE SYSTEMS ENGINEERING PROCESS

4.2.12.1 PLANNING4.2.12.2 MONITORING4.2.12.3 DECISION ANALYSIS4.2.12.4 RISK MANAGEMENT4.2.12.5 CONFIGURATION MANAGEMENT4.2.12.6 INTERFACE MANAGEMENT4.2.12.7 DATA MANAGEMENT4.2.12.8 TECHNICAL MANAGEMENT OF SUBCONTRACTORS/ VENDORS

4.2.13 APPLICATION ACROSS THE LIFE CYCLE

20

Table of Contents (2 of 2)

5. DETAILED REQUIREMENTS5.1 SPECIALTY ENGINEERING ACTIVITIES

5.1.1 PARTS, MATERIALS AND PROCESSES (PMP)5.1.2 STRUCTURES5.1.3 MANUFACTURING5.1.4 QUALITY ENGINEERING5.1.5 TEST5.1.6 SURVIVABILITY5.1.7 ENVIRONMENTAL, SAFETY AND HEALTH (ESOH)5.1.8 CONTAMINATION5.1.9 MASS PROPERTIES5.1.10 LOGISTICS5.1.11 HUMAN SYSTEMS INTEGRATION5.1.12 PROGRAM SECURITY5.1.13 RELIABILITY5.1.14 ELECTROMAGNETIC INTERFERENCE AND COMPATIBILITY (EMI/EMC)5.1.15 SYSTEM SAFETY

5.2 SYSTEM/COST EFFECTIVENESS5.2.1 OPERATIONAL ANALYSIS AND ASSESSMENT5.2.2 SUPPORTABILITY ANALYSIS AND ASSESSMENT5.2.3 TRAINING ANALYSIS AND ASSESSMENT5.2.4 DISPOSAL ANALYSIS AND ASSESSMENT5.2.5 ENVIRONMENTAL ANALYSIS AND IMPACT ASSESSMENT

21

4.2.3 System Element Design Solution and ValidationThe Contractor SHALL determine the design solution, support validation of the design solution, anddevelop the associated required systems engineering products with the product attributesspecified in this document.

4.2.3.1 Required System Engineering Productsa. The validated, approved, and maintained allocated (design-to) baseline in specifications andinterface documents or their electronic equivalent grouped by each system element such assegment, subsystem, component (hardware and software), computer software unit, and part

4.2.3.2 Required Product Attributesa. The allocated baseline:

(1) Identifies all system products and establishes the interactions of the system.(2) Documents the assessment of alternative solutions; identifies and quantifies decision criteria;

and analyzes decision uncertainties.(3) Includes the design-to technical functional and performance requirements and design

constraints for each product.(4) Includes all derived design-to requirements and design constraints for each product.(5) Includes all interfaces and addresses how the interface will be implemented, as well as

the logical issues such as data formats, data semantics, etc.(6) Includes the verification method(s) selected for each requirement.

ContractorRequirement

Perform activity; produce product

SE Requirement and Product Sample

22









Product Description

23









Product content/quality

metrics

24

Specialty Engineering Requirement and ProductSample

5.1.13 Reliabilitya. Space system specific reliability requirements are defined, allocated, baselined,

and traceable to system requirements.(1) Parameters and limits defined and provided within the System Specification(2) Reliability requirements reviewed against functional requirements, customary

design practicesb. Applicable specific design tasks and analyses conducted, including:

(1) Failure Reporting Analysis, Corrective Action System (FRACAS)(2) Source selection and vendor control procedures(3) Failure Modes Effects and Criticality Analysis (FMECA)(4) Derating and margins of safety(5) Fault coverage(6) Single point failure(7) Redundancy/single string

c. Reliability Program Plan and Risk Management Plan developed for final top-level space system

d. Items in development that have impact on support resources identified, including time, people, money, parts, tools, storage, and transportation assets.

25

TORProducts

&Requirements

Specialty AreaProducts

&Requirements

EIA 632SE

Requirements

SE Requirements and Products and EIA 632 Mapping

• Systems Engineering Requirements and Products ExceedsEIA 632Requirements

• Basic SERequirements

PLUS

• SpecialtyEngineeringProductIntegration

26

Agenda





27

Summary

• Systems Engineering is critical to overall mission success

– Baselines are the product of SE process

– Control of baselines is key to SE success

• SE products facilitates SE verification

– Verification requires products with known attributes

• Contracting (buying) SE must be done differently

– Products must be contractually required (purchased)

28

Conclusion

• Systems Engineering (SE) Requirements and Products

– Supports government and industry SE initiatives

– Provides clear SE tasking and evaluation criteria

– Being integrated with Mil-Std-1521 C (Technical Reviews)

– Is coordinated with national security space community

– Has become the SE Compliance document for SMC

Back-up Charts

30

Contributors to theSE Requirements & Products Report

• The author acknowledges the contributions of:

Mr. Frank Knight• The Aerospace Corporation, Systems Director

Corporate Chief Architect/Engineer Division

Mr. Barry Portner• Innovative Space Engineering Services, Inc.

… and a large number of subject matter experts fromThe Aerospace Corporation

• Systems Engineering Division; Engineering and Technology Division• National Systems Division

31

Increased Space System Complexity

• Increased complexity also results in:– More latent defects (increased late build-cycle and orbital failures)– Greater test challenges related to changes in technology,

manufacturing and materials• Increasing electronic part or device complexity (e.g., ASIC, FPGA)• Increased use and complexity of software • Increased system design and subsystem complexity• Lack of robust testing

- Ability and willingness to “test like you fly” - Inclusion of off-nominal test regimes

Flt S/W SLOC CountFlt S/W SLOC Count

00

10k10k

100k100k

1000k1000k

19751975 19951995 20152015

100k100k

200k200k

300k300k

400k400k

500k500k

Electronic Parts / SVElectronic Parts / SV

19801980 19901990 2000

32

SMC Compliance Documents

33

SMC Compliance List

34

SMC Compliance List

35

SMC Compliance List

36

Space Quality Improvement Council

Sponsors MembershipLt Gen Michael A. HamelCommander, Space and Missile Systems CenterUSAF Space Command

Lt Gen Henry A. “Trey” Lt Gen Henry A. “Trey” OberingObering, III, IIIDirectorDirectorMissile Defense AgencyMissile Defense Agency

Maj Gen Robert H. LatiffMaj Gen Robert H. LatiffDeputy Director for Systems EngineeringDeputy Director for Systems EngineeringNational Reconnaissance OfficeNational Reconnaissance Office

Maj Gen James B. Armor, JrMaj Gen James B. Armor, Jr..DirectorDirectorNational Security Space OfficeNational Security Space Office

Mr. Bryan D. O’ConnorMr. Bryan D. O’ConnorChief Safety and Mission Assurance OfficerChief Safety and Mission Assurance OfficerNASANASA

Product-based Systems Engineering RequirementsProduct-based Systems Engineering Requirements Brian...

Documents

Transcript of Product-based Systems Engineering RequirementsProduct-based Systems Engineering Requirements Brian...