SNL SAND No: SAND2019-3978 C
Aras Innovator as Enabler of Digital Engineering at Sandia LabsStephen Denman
April 16, 2019
Sandia National Laboratories is a multimission Federally Funded Researchand Development Center managed and operated by National Technologyand Engineering Solutions of Sandia, LLC., a wholly owned subsidiary ofHoneywell International, Inc., for the U.S. Department of Energy NationalNuclear Security Administration under contract DE-NA-0003525.
© 2019 Aras2
SNL SAND No: SAND2019-3978 C
Sandia National Laboratories
Federally Funded Research and Development Center (FFRDC)
Operated by NTESS, subsidiary of Honeywell International, Inc.
For U.S. Department of Energy (DOE), National Nuclear Security Administration (NNSA)
Multi-mission Science and Engineering Laboratory (3.6B USD Budget FY18)
Nuclear Deterrence Mission
Nuclear weapons and related programs
Cradle-to-grave system lifecycle
responsibility
shared with other design agencies
& production agencies
Other missions
Global
Security
Defense
Systems
National
Security…
Cradle-to-grave system lifecycle responsibility
for many first-of-a-kind and one-of-a-kind systems
…Non-
federal
entities
Energy
© 2019 Aras3
SNL SAND No: SAND2019-3978 C
My Background and Role at Sandia
▪ Background
▪ Sandia, Rational, IBM, RESPEC, the Emphasys group, MKS, PTC, IBM, consulting, Sandia: 35 yrs
▪ Systems and software engineering
▪ Engineering processes, methods, and tools
▪ PLM, ALM, RE/RM, Systems/SW modeling, SW dev, CM, Test/QA, PPM, …
▪ Role
▪ Vision and roadmap for the Aras Engineering Management System (AEMS)
Images: Freepick.com
© 2019 Aras4
SNL SAND No: SAND2019-3978 C
Assembly
Test & Qualification
Mission
System
Sub-system
Validation
Verification
Integration & Test
Integration & Test
Specification
Architecture
Requirements
Requirements
Technical Development
Concept Development
Operations & Support
Retire-ment
Fabrication & Sourcing
Unit Test Build &
Production & Deployment
Sandia Product/System Delivery Lifecycle
Mechanical & ElectricalAssemblyPart
ElectronicsBoardPart
Software & FirmwareModuleUnit
“As-Architected”
“As-Required”
“As-Released”
As-Planned
“As-Specified”
“As-Planned-for-Fab”
As-Designed “As-Built-for-Qual”
“As-Built-for-SSTest”
“As-Built-for-SysTest”
“As-Built-for-SysVer”
“As-Built-for-SysVal”
As-Built
As-Delivered
As-Maintained
Traditional BOMs
Phase Handoff
“Additional BOMs”
“?”
“?”
“?”
Analysis & Design
Planning
Compo-nent
© 2019 Aras5
SNL SAND No: SAND2019-3978 C
Standalone
System
Data
Work
-flow
Config
EPM
PPM
ERP
MRP
SCM
MPP
MES
QMS
Test
V&V
Dev
ALM
ECAD
EDA
Product Lifecycle ManagementChallenges at Sandia
MCAD
PDM
Product data,
processes, and
configurations• Spread among
standalone, domain-
specific, phase-specific
systems and tools
• Data is silo’ed,
independent,
inaccessible
• Data is duplicated, out-
of-sync
Considerable
effort required to
develop holistic:• Visibility
• Control
• Product/System
Configuration
RM
Sim-
ulation
MS Office
Most widely used
engineering
practitioner tools
in the world
Word Doc • Requirements
management
• Sharing &
collaboration
• Data container
• Configuration item
• “Track changes” =
Change management
Excel
Spreadsheet• Data container
• Configuration item
• Data analysis
PowerPoint• Reporting tool
Excel
Spreadsheet• Data
Exchange
Mod-
eling
© 2019 Aras6
SNL SAND No: SAND2019-3978 C
Product Lifecycle ManagementChallenges at Sandia
Assembly
Test & Qualification
Mission
System
Sub-system
Validation
Verification
Integration & Test
Integration & Test
Specification
Architecture
Requirements
Requirements
Technical Development
Concept Development
Operations & Support
Retire-ment
Fabrication & Sourcing
Analysis & Design
Planning
Production & Deployment
Unit Test Build &
Compo-nent
Office Sim-
ulationMod-
eling
Office
Office
Office
Office
Sim-
ulationMod-
eling
RM
MCAD
PDM
ECAD
EDA
Sim-
ulationMod-
eling
Dev
ALM
ERP
MRP
SCMMPP
MES
Test
V&V
Test
V&V
ERP
MRP
SCMMPP
MES
QMSThis is
what the
challenge
looks like
across
the
lifecycle.
EPM
PPM
© 2019 Aras7
SNL SAND No: SAND2019-3978 C
Aras Engineering Management System (AEMS)
▪ Highly-customized PLM solution
▪ Supporting multiple engineering processes for multiple programs across multiple
missions
▪ Built on Aras Innovator platform
▪ Why Innovator?
▪ More flexible, customizable
▪ More open
▪ Lower cost (licensing and TCO)
▪ Current Innovator out-of-the-box configuration
▪ Platform
▪ Product Engineering
© 2019 Aras8
SNL SAND No: SAND2019-3978 C
Current AEMS Capabilities
Assembly
Test & Qualification
Mission
System
Sub-system
Validation
Verification
Integration & Test
Integration & Test
Specification
Architecture
Requirements
Requirements
Technical Development
Concept Development
Operations & Support
Retire-ment
Fabrication & Sourcing
Compo-nent
Analysis & Design
Planning
Production & Deployment
“As-Built-for-Qual”
Supporting
Capabilities
Reporting
Workflow
Management
Data Management
Security
Federation
Unit Test Build &
“As-Planned-for-Fab”
As-Designed
Document
Management
BOM
Management
Manufacturing
Development
Quality
Management
Change
Management
Configuration
Management
ERP MRP SCM
Process
Planning
Execution
Inventory
Oracle
© 2019 Aras9
SNL SAND No: SAND2019-3978 C
Vision
AEMS is the digital engineering backbone that unifies
teams, disciplines, processes, and tools across the entire
product delivery lifecycle.
© 2019 Aras10
SNL SAND No: SAND2019-3978 C
Digital Engineering
▪ A definition
▪ Adapted from the US Office of the Secretary of Defense (OSD) digital engineering initiative
▪ The transformation of the way we design, develop, deliver, operate, and sustain systems
▪ An integrated digital approach
▪ Using authoritative sources of system data and models as a continuum across disciplines
▪ To support lifecycle activities from concept through disposal
▪ Inclusive of Digital Twin and Digital Thread
▪ Inclusive of the entire product definition
▪ All product information assets from concept to disposal
© 2019 Aras11
SNL SAND No: SAND2019-3978 C
▪ What’s wrong with a single source of truth?
▪ “One tool to rule them all” has been tried time-and-again and success stories are few and far between
▪ An authoritative source of truth (ASOT) system maintains metadata about all product data across the
lifecycle, including:
▪ Location, change status, and configuration, from concept to disposal
▪ Other metadata needed to provide ASOT system functions
▪ At any point in the lifecycle, product data may reside in:
▪ The ASOT system
▪ a practitioner system
▪ an enterprise system (e.g., ERP, MRP, SCM)
▪ a product data management (PDM) system
NOT the SINGLE Source of Truth
The Authoritative Source of Truth
© 2019 Aras12
SNL SAND No: SAND2019-3978 C
Assembly
Test & Qualification
Mission
System
Sub-system
Validation
Verification
Integration & Test
Integration & Test
Specification
Architecture
Requirements
Requirements
Technical Development
Concept Development
Operations & Support
Retire-ment
Fabrication & Sourcing
Unit Test Build &
Production & Deployment
Future AEMS Capabilities
“As-Architected”
“As-Required”
“As-Released”
As-Planned
“As-Specified”
“As-Planned-for-Fab”
As-Designed “As-Built-for-Qual”
“As-Built-for-SSTest”
“As-Built-for-SysTest”
“As-Built-for-SysVer”
“As-Built-for-SysVal”
As-Built
As-Delivered
As-Maintained
“?”
“?”
“?”
Analysis & Design
Planning
Compo-nent
Reporting,
Metrics,
Dashboards
Document
Management
BOM
Management
Manufacturing
Development
Quality
Management
Change
Management
Configuration
Management
Variability
Management
Software
Management
Workflow
Management
Data
Management
Enhanced
Security
Federation,
Data Linking,
Data Exchange
© 2019 Aras13
SNL SAND No: SAND2019-3978 C
AEMS Vision: A Digital Engineering Backbone
AEMS Digital Engineering BackboneAn Authoritative Source of Truth About the System Across the Lifecycle
Practitioner Tools Product
Data
Management
Systems
Enterprise Systems
PDMMCAD
Modeling &
SimulationQM, Test,
Qual, V&V
Reqs
Mgt
Dev
ALM
EPM
PPM
ECAD/EDA
ERP
MRPMPP
MES
SCM
© 2019 Aras14
SNL SAND No: SAND2019-3978 C
Open Questions
▪ Federation is on the critical path to success
▪ Will Innovator Federation capabilities keep up?
▪ Will Innovator continue growing and maturing at present rate?
▪ Conclusion
Regardless of which technology/product we choose today,
we must prepare to replace the underlying platform of the digital engineering backbone
when/if current technology/product fall behind our roadmap and needs
▪ How?
▪ Reliance on proven standards, pushing them forward where they do not or will not meet the need
▪ AEMS solution architecture is critical
▪ Can the AEMS team scale to meet growing (and changing) demand?
▪ Yes, but… Must streamline and scale our processes (analysis, dev, onboarding, support, …): SAFe