the digital thread in shipbuilding vision or reality? - nsrp · the digital thread in shipbuilding...
TRANSCRIPT
The Digital Thread in Shipbuilding – Vision or Reality?
Kevin RichardProduct Manager
aras.com© 2017 Aras
Doug MacdonaldProduct Marketing Director
One of the first “CAD Boats”
aras.com© 2017 Aras
…and one of the latest
© 2017 Aras aras.com
Agenda
Vision vs reality
Underlying causes
PLM Platform
Open technology approach
aras.com© 2017 Aras
Digital ThreadVision?
B
C
FE
D
G
IH
K
M
O
L
A
J
P1
C
F
D
P2
IH
J
K
O
L
G
Q
A A
C
F
D
I
J
K
O
L
G
Q
SN #6
SN #89
SN #44
A
C
F
D
H
J
K
O
L
G
Q
SN #6
SN #97
SN #44
R2
R7
R3
R8
R5
R6
R4
R9
R10
R11
R1
R12
Concept Development Manufacturing Service
Requirements As Designed As Planned As Built As Maintained
D I G I T A L T H R E A D
DI
GI
TA
LT
WI
N
aras.com© 2017 Aras
Digital ThreadWhat’s the reality?
Configuration knowledge (and control) is repeatedly lost and regained through every stage of the product lifecycle
As-Designed
• Engineering changes
As-Planned
• Manufacturing restructuring
• Supplier parts
ERP
As-Built
• Concessions• Serialized parts• Batches/lots
MES
As-Maintained
• Maintenance• Modifications• Repairs
MRO
aras.com© 2017 Aras
X XX
Too hard to fix?
Many initiatives today are focused around regaining short-term control, not fixing the problem
20 years from now we may be in exactly the same situation
aras.com© 2017 Aras
What are the causes?
Long lifecycles
Multiple stakeholders with conflicting motivations / contractual obligations
Increasing product complexity
Fragmented systems at every lifecycle stage
Legacy/Cultural tendencies
Technology
Open/Richness of data
aras.com© 2017 Aras
Integrated Product Data Environment (IDE/IPDE) as the single source of data
▫ Direct use of engineering and model data within the IDE to support simulation and analysis
▫ Explicit definition of interdependencies among systems / subsystems E.g., Conduit connectivity
And other less tangible design aspects
▫ E.g., Survivability
IDE ~ PLM
We thought we could solve the problemSmart Product Model (SPM)
© 2017 Aras aras.com
IDE
Sim. Data
Eng. Data
CAD Data
Program Data
Mis
sio
n
Rec
ove
rab
ility
Seak
eep
ing
Int.
Po
wer
Sy
stem
Ad
van
ced
Gu
n
Syst
em
Au
ton
om
ic
Fire
Su
pp
.
Knowledge Mgmt
Web PortalThe SPM includes the connections
Adapted from: Aerospace & Defense Industry PLM Value Gap Survey, CIMdata, March 2013
But legacy PLM failed to meet the vision
Cap
abili
ty /
Val
ue
1990 2000 2010 2020 2030
Implementations
Technology
Vision
aras.com© 2017 Aras
Years Using Current Generation PLM SolutionYears To Complete Implementation Of Current Generation PLM Solution
“Over a third of current PLM (PDM) solutions are more than 5 years old”
“Over a third of current PLM (PDM) implementations have more than 3 years
of development remaining”
Aerospace & Defense Industry PLM Value Gap Survey, CIMdata, March 2013
Hard to Implement, Difficult to Upgrade
aras.com© 2017 Aras
Focused on the Science of Engineering
MCAD PDM
aras.com© 2017 Aras
Failing to support the Business of Engineering
Concept Development Manufacturing Service
Software
Mechanical
Electrical
Electronic
MCAD PDM
Product
System Requirements, MBSE, Systems Engineering, Verification & Validation
Configuration and Change Management – EBOM/MBOM/SBOM
Electrical DesignElectronic Design
Component Engineering
Software Development
Manuf. Planning
Work Instructions
Quality Planning & Systems
User Manuals
Service Manuals
Catalogs
Modeling, Simulation
IOT Analytics
aras.com© 2017 Aras
Leaving engineers working like thisPLM Underground
aras.com© 2017 Aras
Poor cross-discipline communication compromises design integrity
Lack of an integrated product configuration creating confusion at critical hand-offs
Fragmented data and processes making it hard to support new business opportunities
Impacting the ability to do business
aras.com© 2017 Aras
What are our requirements?
Concept Development Manufacturing Field
aras.com© 2017 Aras
PLM Redux – the PLM Platform?
MBSE Maint.Mgmt.
PLM Platform
Configuration & Change Management
IOT
Integrated Applications
Collaboration Business Process Workflow
Concept Development Manufacturing Service
ERPMCADPDM
ECADALM
Simulation Suppliers
Access Management
MES
aras.com© 2017 Aras
Look or sound familiar?
NSRP: Navy Product Data Initiative, Integrated Product Data Environment Specification, Version 1.0 dated 30 June 2008http://www.nsrp.org/wp-content/uploads/2016/01/NPDI_IPDE_Spec_Initial_2008_06_30_Vers1_FINAL.pdf
aras.com© 2017 Aras
Overview
NAVSEA tasked NSRP to specify the requirements for and drive the implementation of product data systems
▫ based on an open architecture
▫ having suitable functionality and
▫ enterprise-wide interoperability
to support affordable
▫ Navy vessel design,
▫ construction and
▫ service life supportaras.com© 2017 Aras
Technology requirements for PLM Platform
Resilient technology that is:
▫ Flexible
Meets the unique, evolving needs of the organization
▫ Scalable
Supports users across the extended enterprise
▫ Upgradable
Upgrade to new releases in a timely and economical manner
Open business model
Innovative deployment approach
aras.com© 2017 Aras
Model-based technology
Flexible, common services▫ Item management
▫ Configuration and change
▫ Lifecycles and workflow
▫ Visual collaboration
▫ Vault management
▫ Search, etc.
Scalable - tested to 250k concurrent users
Adaptive Client
Modeling EngineFlexible data and process model
RepositoryModel and data
Services LayerStandard PLM services
Services LayerStandard PLM services
aras.com© 2017 Aras
Model-based technology
Modeling EngineFlexible data and process model
Services LayerStandard PLM services
Adaptive Client
RepositoryModel and data
aras.com© 2017 Aras
Model-based technology
Adaptive Client
Modeling EngineFlexible data and process model
Services LayerStandard PLM services
RepositoryModel and data
Adaptive Client
aras.com© 2017 Aras
Applications are built and modified using the Modeling Engine
Models "subscribe" to the services that they need
Models dynamically update the client
Model-based technology
Applications are built and modified using the Modeling Engine
Adaptive Client
Modeling EngineFlexible data and process model
Services LayerStandard PLM services
Models "subscribe" to the services that they need
Models dynamically update the client
Models are stored in the repositoryRepository
Model and data
RepositoryModel and data
aras.com© 2017 Aras
Model-based technology
Separation of Models allows the Services Layer to be upgraded quickly and easily
Customized Models are fully preserved during upgrades
Lets you stay current and benefit from innovation
Adaptive Client
Modeling EngineFlexible data and process model
RepositoryModel and data
Services LayerStandard PLM services
Services LayerStandard PLM services
aras.com© 2017 Aras
Open business model
Enterprise open source
▫ Open access to evaluate, test and deploy
Open interfaces: gives you options
▫ To authoring tools and enterprise systems
Open community: puts you in control
▫ Users and partners
▫ Guides the roadmap
▫ Collaborative open-source development
aras.com© 2017 Aras
Innovative deployment approach
On-site, cloud or hybrid
▫ Flexibility to be deployed on-site, in a public or private cloud, or in hybrid configurations
Agile implementation
▫ Architecture enables a flexible, agile deployment approach that demonstrates tangible business results quickly at lower risk
aras.com© 2017 Aras
Deployed as PLM Platform
Platform deployment connectsthe extended enterprise
▫ Single data and process model
▫ Integrated applications
▫ Through-life configuration management
▫ Connected to authoring tools and integrated to enterprise systems
Overlay or replace legacy PDM environments
aras.com© 2017 Aras
AS PLANNED
P1
C
F
D
P2
IH
J
K
O
L
G
T
Q
R
S
A
AS ORDERED
B
C
F
D
G
IH
J
K
O
L
Q
R
S
A
AS DESIGNED
B
C
FE
D
G
IH
K
M
O
L
J
Q
R
S
A
AS DELIVERED
C
F
D
H
J
K
O
L
G
T
SN #89
SN #44
R
S
Q
A SN #6
SN #71
AS SERVICED
C
F
D
H
J
K
O
L
G
T
SN #97
SN #44
A SN #6
Q SN #71
R
S
FUNCTIONAL
F2
F8
F6
F4
F11
F10
F12
F9
F5
F7
F3
F13
F15
F14
F16
F1
LOGICAL
L2
L7
L3
L8
L5
L6
L4
L9
L10
L11
L1
REQUIRED
R2
R7
R3
R8
R5
R6
R4
R9
R10
R11
R14
R13
R1
R12
AS BUILT
C
F
D
I
J
K
O
L
G
T
SN #89
SN #44
Q
R
S
SN #53
AA SN #6
Through life configuration management
aras.com© 2017 Aras
Creating the Digital Thread
aras.com© 2017 Aras
Conclusions
The NSRP study identified the need for and the benefits of an IPDE nearly 10 years ago
Key challenges have been
▫ Spanning the product lifecycle – especially configuration management
▫ Integrating engineering domains (hardware and software)
▫ Availability of an open solution
A proven, open solution is available now
aras.com© 2017 Aras
Next Steps
Propose a series of pilots to further develop technology and best practices
Focused on key lifecycle stages and interfaces:
▫ Planning to Construction
▫ Construction
▫ Construction to Service
▫ In-Service
Multi-year effort but lessons learned can be applied quickly
Will require high level of stakeholder sponsorship for viability
aras.com© 2017 Aras