Digital Engineering /

Systems Engineering (DE/SE)

MODEL-BASED ACQUISITION:
INCREASING CLARITY, COMPLIANCE AND UNDERSTANDING IN
PRODUCT ACQUISITION
Matthew C Hause Laura E Hart
OMG UAF Chair OMG UAF Chair
Systems Strategy Inc Lockheed Martin Corporation

8/1/2022
Agenda Digital Engineering /
Systems Engineering (DE/SE)

• The Digital Engineering Strategy

• The Object Management Group (OMG) MBAcq Activity
• MBAcq and GVSC
• Conclusion
• Questions?

8/1/2022
Government Leading the Way – The DES
DoD released their Digital Engineering Strategy
June 2018 signed off by DoD, Under Secretary
of Defense for Research and Engineering,
Michael D. Griffin
• Transforms DoD contract data
requirements document-based to model-
based
• Promote the use of digital representation
as technical means of communication with
diverse set of stakeholders
• Addresses acquisition and procurement
and innovations in the way we build, test,
field and sustain.
• Guides detailed implementation for current
development within the services
• Recent Major Acquisitions Already
Implementing

LOCKHEED MARTIN PROPRIETARY INFORMATION 3

 Digital Engineering /
The Authoritative Source of Truth Systems Engineering (DE/SE)

• Throughout the development lifecycle

8/1/2022
 Digital Engineering /
Systems Engineering (DE/SE)

8/1/2022
UAF MBAcq User Group
SlideStatement:
Problem Subject Title
Industry is seeing an increase in the number of
RFPs requiring the use of MBSE as well as the use of models during the
acquisition process. The challenge to both the supplier and provider is
the lack of standardization in the approach resulting in a learning curve
for every proposal as well as every response further complicating
compliance with DOD governance.
MBAcq UG Mission: To address this concern, the UAF MBAcq User
Group was formed to survey the current landscape with participation
from government, industry and academia. The UG will assess and
recommend updates to SE and Architecture standards such as SysML
and UAF including the associated process guidance for both
engineering and acquisition professionals. The UG will provide
prioritized MBAcq requirements to the OMG UAF RTF for
consideration. (OMG UAF MOU tbd).

® 2022 Object Management Group. All Rights Reserved.

 |7|

Technical Approach Unified Architecture Framework (UAF)

Grid Overview (Domain /View )
Taxonomy Structure Connectivity Processes States Interaction Information Parameters Constraints Roadmap Traceability
Tx Sr Cn Pr St Scenarios Is If Pm Ct Rm Tr

Metadata
Architecture Metadata Metadata Metadata Metadata
Metadata Taxonomy
Viewpoints a Connectivity Processes a - - Constraints a Traceability
Md Md-Tx
Md-Sr Md-Cn Md-Pr Md-Ct Md-Tr

Interaction between the Capability Requirement Strategic

St
Strategic
Taxonomy
Strategic Structure
St-Sr
Strategic
Connectivity -
Strategic States
St-St
-
Strategic
Constraints
Strategic
Deployment,
St-Rm
Strategic
Traceability
St-Tx St-Cn St-Ct St-Tr
Strategic Phasing

Process and the Acquisition Process Operational Operational Operational Operational Operational
Operational
Operational
St-Rm

Operational
Operational Interaction
Taxonomy Structure Connectivity Processes States Constraints - Traceability
0p Scenarios
Op-Tx Op-Sr Op-Cn Op-Pr Op-St Op-Ct Op-Tr
Op-Is

Service
Service Service Service Service Service
Services Service Structure Service States Interaction Service Roadmap
Taxonomy Connectivity Processes Conceptual Data Constraints Traceability
Sv Sv-Sr Sv-St Scenarios Environment Sv-Rm
Sv-Tx Sv-Cn Sv-Pr Model, Sv-Ct Sv-Tr
Sv-Is Pm-En

Evaluation Personnel Personnel Personnel Personnel

Personnel Competence,
Personnel
Availability,
Personnel
Personnel Personnel States Interaction Drivers,
Taxonomy Structure Connectivity Processes Personnel Evolution, Traceability
Pr Pr-St Scenarios Logical Data Model, Performance
Pr-Tx Pr-Sr Pr-Cn Pr-Pr Pr-Tr

Decision Pr-Is Pr-Ct Personnel Forecast

Pr-Rm
Resource
Resource Resource Resource Resource Resource Resource evolution, Resource
Resources Resource States Interaction
Taxonomy Structure Connectivity Processes Constraints Resource forecast Traceability
Rs Rs-St Scenarios Physical schema, Measurements
Rs-Tx Rs-Sr Rs-Cn Rs-Pr Rs-Ct Rs-Rm Rs-Tr
Rs-Is real world results Pm-Me

Security Security Security Security Security

Security Security Structure Processes Constraints
Taxonomy Connectivity - - - Traceability
Sc Sc-Sr
Sc-Tx Sc-Cn Sc-Pr Sc-Ct Sc-Tr

Project Project Project

Projects Project Structure Project Roadmap
Taxonomy Connectivity - - - - Traceability
Pj Pj-Sr Pj-Rm
Pj-Tx Pj-Cn Pj-Tr
Standard Standards Standards
Standards Standards Roadmap
Taxonomy Structure - - - - - Traceability
Sd Sd-Rm
Sd-Tx Sd-Sr Sd-Tr
Actual
Actuals Actual Resources Parametric
Resources
Resources Structure, Simulation b Execution/ - -
Connectivity,
Ar Ar-Sr Evaluation b
Ar-Cn

Dictionary * Dc
Summary & Overview Sm-Ov
Requirements Req

Copyright © 2016,
Object Management
Group, Inc.

Generated
Response with
RFP Package
Updated Model

Approved for Public Release;

© 2017 The MITRE Corporation. All Rights Reserved.
Distribution Unlimited: 17-1179. Page-7
What’s in the System Architecture Model
• A System Architecture Model is an
Integrated Structured Representation of
the Requirements, Behaviors, Structure,
Properties, and Interoperability

– Requirements
• What are the mission operations, stakeholders
goals, purposes, and success conditions for the
system?
– Behavior
• What the system needs to do to meet
requirements
• Transformation of inputs to outputs
• Responses to External stimulus
– Structure
• The parts of the system that are responsible for
the behaviors
• The component hierarchy, elements and stores
– Properties
• The performance, physical characteristics and
governing rules that constrain the structure and
behaviors
– Interconnections System Model
• The ability of the structured elements to
exchange information and achieve their
required behaviors
Document
Specifications
Primary use of the system model is to enable the design of a system
that satisfies its requirements
8 ©2018 The MITRE Corporation. ALL RIGHTS RESERVED. Approved for public release. Distribution unlimited 18-2496-1.
What’s the Acquisition Reference
Model (ARM)
ARM is a set of reusable model templates, and
Slide Subject Title
guidance used to augment a model-based RFP
based on the UAF standard to support data
driven decisions beginning with acquisition
which can be maintained throughout the
complete lifecycle of program.

Use Cases:
• Create Precise RFP
GOV
• Respond to RFP
• Evaluate RFP Response
– Contractor Self Evaluation
– Government Evaluation
• Maintain Technical Baseline
– Model evolves over time and Focus on Unified SOURCE: Laura Hart,

represents the technical baseline Contract Format: MITRE 2017

Sections K, L, & M
® 2022 Object Management Group. All Rights Reserved.
 Model-Based Acquisition Overview
Model-Based Acquisition
1. Acquisition Reference Model (ARM)Template 2. Government Reference Model (GRM) 3. Model-based RFP Package

ARM Template
+
GRM Template Populated with Program
& contract Data Supports
 4. Unified Architecture Framework (UAF) Process Guide for Acquisition → DoDAF

2. The GRM is a descriptive model containing the 3. The Model-based RFP model contains the
1. The Acquisition Ref Model Template provides populated GRM and ARM template providing RFP
program requirements, & constraints
model structure for RFP content and evaluation evaluation content, CDRL definitions for
• High-level Capabilities, mapped to Operational
tools: documentation generation and scoring tools for
scenarios, traced to requirements (e.g., CDD,
• Modeling Patterns solution validation and evaluation
SRD, Conops)
• AVO Profiles (i.e.. MOSA, Data Rights, cert)
• Technical performance measures (i.e., KPPs,
• Interface & Analysis Definitions
KSAs, MOEs..)
• Templates & Schemas 4. UAF Process Guide provides the Acquisition
• Any required architectural partitioning including
• Evaluation Criteria & Scoring (Section K, L, Guidance for using the UAF Framework for GRM
structural and functional and ARM template to create, respond and
M)
(Based on UAF acquisition process guide and
• Reports & CDRLS evaluate a Model-based RFP. 10
template) SOURCE: Laura Hart, MITRE 2017
® 2021 Object Management Group. All Rights Reserved.
Acquisition Reference Model (ARM)
1. The Acquisition Ref Model (ARM) provides model
structure for RFP content and evaluation tools:
Modeling Patterns
Analytic Viewpoint Overlays (i.e., MOSA, Data Rights, certs )
Interface & Analysis Definitions
Templates & Schemas
Evaluation Criteria & Scoring (Section K, L, M)
Reports & CDRLS
Additional Contractual Data

Organization and Modularity is key to reuse and

standardization

® 2021 Object Management Group. All Rights Reserved.

 Gov Reference Model
2. The GRM is a descriptive model
containing the program requirements, &
constraints for the system to be acquired as
defined by the Acq Reference Architecture. Government Reference Model (GRM)
• High-level Capabilities, mapped to
Operational scenarios, traced to
requirements (e.g. CDD, SRD, Conops)
• Technical performance measures (i.e.
KPPs, KSAs, MOEs..)
• Any required architectural partitioning
including structural and functional
(Based on UAF acquisition process guide
and template)

® 2021 Object Management Group. All Rights Reserved.

Analytic Viewpoint Overlays (AVOs)
Analytic Viewpoint Overlay (AVO) Description: A collection of constructs needed
to support analysis for a domain specific concern using a standardized approach.
Typical construct elements include:
• A set of regulations, constraints, rules…. driving the analysis (i.e. MOSA,
safety, certification, airworthiness, Space …)
• A set of Data/Metadata required to address or support analysis, compliance
or fit-for-purpose. Implementation example (Domain model/profile)
• Logic/algorithm needed to perform analysis using the metadata and
regulations

Characteristics
• Usually has associated regulations, governance that can be treated as pseudo
requirements or constraints
• Cross-cutting both viewpoints/rows & aspects/columns
• Supports specific analysis associated with a Domain-Specific concern
• Can be created independent of a specific solution architecture description
• Can be applied or removed from a specific architecture description without
impacting the AD, hence an overlay
Based on NDIA Actionable Architecture Using Aspect Modeling, L Hart 2018

® 2021 Object Management Group. All Rights Reserved.

 Model-Based RFP Package
The Model-based 3. Model-based RFP Model
RFP Package
contains the
populated GRM and
ARM template
providing RFP system
requirements,
evaluation content,
CDRL definitions for
documentation
generation, scoring
tools for solution
validation and
evaluation.
® 2021 Object Management Group. All Rights Reserved.
UAF MBAcq Process Guide

4. UAF MBAcq Process Guide provides the Acquisition Guidance for

applying the UAFML to create, respond and evaluate a Model-
based RFP including the creation of the GRM and ARM. It will
address various roles (acquisition, engineering, supplier, acquirer)

Supports
DoDAF
 4. Unified Architecture Framework (UAF) Process Guide for Acquisition →

® 2021 Object Management Group. All Rights Reserved.

 MBAcq DMM
Bringing it all together!
The System Acquirer (government) creates and publishes
the Model Based RFP Package which contains the ARM,
GRM, Non-Model Artifacts and a tailored MBAcq Process
Guidebook that provides role specific guidance on
creating, responding and evaluating a MB RFP.

− The ARM is part of an Acquisition Library that Conforms to

various Analytic Viewpoint Overlays (AVOs).
− An AVO addresses a particular domain specific concern by
codifying the concern’s meta data and analysis algorithm for
evaluating the concern against a set of associated
regulations. These AVOs can be used to define compliance
using a standardized approach.
− The ARM contains Templates, Schemas and contractual
information required by the acquirer for the Supplier to
show compliance.
− The GRM is an actual model that conforms to the Acquisition
Reference Architecture Definition that specifies that a GRM
should contain the system specific technical performance
measures, the operation context, high level capabilities and
system requirements required to define a system for
appropriate use.

The Supplier proposes a Solution Architecture that is

appropriate for use using the evaluation criteria and
showing compliance evidence as defined in the ARM and
GRM.

® 2021 Object Management Group. All Rights Reserved.

 Next Steps
Slide Subject Title
Address Uniformed Contract Format (UCF)
PART I - The Schedule
Section A Solicitation/Contract Form
Section B Supplies or Services And Price/Costs
Section C Description/Specification/Statement Of Work
Section D Packaging And Marking
Section E Inspection And Acceptance
Section F Deliveries And Performance
Section G Contract Administration Data
Section H Special Contract Requirements

PART II - Contract Clauses

Section I Contract Clauses

PART III - List of Documents, Exhibits and Other

Attachments
Section J List Of Attachments

PART IV - Representations and Instructions

* Representations, Certifications And Other Statements Of
Section K
Offerors
Section L Instructions, Conditions, And Notices
MITRE 2017 To Offerors
SOURCE: Laura Hart,

Section M Evaluation Factors For Award

® 2022 Object Management Group. All Rights Reserved.
 Digital Engineering /
Systems Engineering (DE/SE)

What Are the Implications for GVSC?

8/1/2022
 Digital Engineering /
The DoD OSD Digital Engineering Strategy Systems Engineering (DE/SE)

8/1/2022
MBACQ and GVSC Digital Engineering /
Systems Engineering (DE/SE)

• 1. Formalize the development, integration, and use of

models to inform enterprise and program decision
making.
– Existing processes will need to be examined to determine
where and how MBSE can be inserted, adopted and
improved.
– Prototype processes to determine which work best, find
issues, and socialize results.

8/1/2022
MBACQ and GVSC Digital Engineering /
Systems Engineering (DE/SE)

• 2. Provide an enduring, authoritative source of truth.

– CM of models maintained throughout the product
development lifecycle to ensure consistent information.
– Support ongoing operations and maintenance with MBSE.
Otherwise, models will be rebuilt from scratch with
corresponding loss of IP and knowledge.
– Harvest and reuse best practices, patterns, components,
libraries.

8/1/2022
MBACQ and GVSC Digital Engineering /
Systems Engineering (DE/SE)

• 3. Incorporate technological innovation to improve

the engineering practice.
– Training at all levels of the organization in accordance with
exposure and use of models.
– Includes influencers, reviewers, and modelers.
– Engagement with standards and industry bodies to share
ideas.

8/1/2022
MBACQ and GVSC Digital Engineering /
Systems Engineering (DE/SE)

• 4. Establish a supporting infrastructure and environment

to perform activities, collaborate and communicate
across stakeholders.
– MBAcq is not just SysML/UAF models. Need a digital thread
across all development tools.
– Includes RM, Product Lifecycle Management (PLM), physics-
based tools, testing tools, CM tools, etc.
– Infrastructure in line with industry, standards bodies, and tool
vendors to ensure interchange, interoperability and
connectivity.

8/1/2022
MBACQ and GVSC Digital Engineering /
Systems Engineering (DE/SE)

• 5. Transform the culture and workforce to adopt and

support digital engineering across the lifecycle.
– Successes and failures shared within the organization to learn
from both good and bad experiences.
– Feedback to processes, standards, modeling techniques,
captured and documented.
– Output from models adapted to the expertise and purpose of
the intended audience.
– Overly technical output should not be presented to high level
decision makers. Otherwise, this risks turning them off.

8/1/2022
 Digital Engineering /
Systems Engineering (DE/SE)

Questions?
Matthew C Hause Laura E Hart
OMG UAF Chair OMG UAF Chair
Systems Strategy Inc Lockheed Martin Corporation
Mhause@SystemXI.com Laura.E.Hart@lmco.com

8/1/2022