M&S as a Service: Emerging Approach and Standards Activities1. www.aditerna.de
© 2015 aditerna GmbH
Dr. Robert Siegfried
M&S as a Service: Emerging Approach
and Standards Activities
2015 SISO Fall SIW, Orlando, USA
01 September 2015
2. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Credits
MSG-131
August 2013 – August 2014
MSG-136
September 2014 – September 2017
01 September 2015 2M&S as a Service (MSaaS)
3. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
NATO MSG-136
• MSG-136 “Modelling and Simulation (M&S) as a Service
(MSaaS) – Rapid deployment of interoperable and credible
simulation environments”
• Tasked to investigate technical services and necessary
organizational aspects
• M&S Services (e.g., Synthetic Environment Service (SES),
Route Planning Service)
• Organizational M&S Services Perspective
• Term: Oct 2014 – Oct 2017
01 September 2015 M&S as a Service (MSaaS) 3
4. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
From stove-piped systems to
service-based M&S
01 September 2015 M&S as a Service (MSaaS) 4
What is
MSaaS?
Standards
Landscape
MSaaS
Standards
5. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
“M&S as a Service” vs.
“in the Cloud”
• Cloud = …
– … provisioning of services
– … by one (or more) suppliers
– … for customers
– … based on a pay-per-use principle
– …
01 September 2015 M&S as a Service (MSaaS) 5
“M&S as a Service (MSaaS)
is a means of delivering
modelling and simulation (M&S)
applications, capabilities and associated data
on demand by providers to consumers.”
[MSG-131/136]
6. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
MSaaS in a Nutshell
• Decomposition of
M&S applications into
functional pieces
(= services)
• Exchangeability and
flexibility as central
design paradigm
• Individual deployment
of all services
01 September 2015 M&S as a Service (MSaaS) 6
7. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
“Cloud-based simulation is NOT
EQUAL to M&S as a Service”[Sanders]
01 September 2015 M&S as a Service (MSaaS) 7
Server A Server B
Service
A1
Service
A2
Service
B1
Service
B2
“Traditional” Data Center (SOA)
• User needs to know specific server instance that
executes a service
• No transparent elasticity
Server A Server B
Service
A1
Service
A2
Service
B1
Service
B2
Cloud Computing
• User does not know specific server instance that
executes a service
• Transparent elasticity and scalability
Cloud Middleware
Service
A1
A1 B1
8. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Illustration of a Future
Service-Based M&S Eco-System
01 September 2015 M&S as a Service (MSaaS) 8
WES SES
SimSys A
User
SimSys C
User
SimSys D
SimSys B
WES
Service Contracts
(Interface specifications, …)
9. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
MSaaS from the user perspective
01 September 2015 M&S as a Service (MSaaS) 9
10. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
From stove-piped systems to
service-based M&S
01 September 2015 M&S as a Service (MSaaS) 10
What is
MSaaS?
Standards
Landscape
MSaaS
Standards
11. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Major conclusion of MSG-086: gaps are
on higher levels of interoperability!
LCIM
Level 5
Dynamic Interoperability
Level 4
Pragmatic Interoperability
Level 3
Semantic Interoperability
Level 2
Syntactic Interoperability
Level 0
No Interoperability
Level 1
Technical Interoperability
Level 6
Conceptional Interoperability
increasingqualityofInteroperability
Model building /
Abstraction
Simulation /
Implementation
Network /
Connectivity
Standards available
(e.g., TCP/IP, HLA, DIS, RPR
FOM)
Many interoperability
problems, but
- only partial solutions and
- standards are missing!
A. Tolk et al., “Ontology Driven Interoperability – M&S Applications”, Whitepaper for I/ITSEC 2006.
01 September 2015 M&S as a Service (MSaaS) 11
12. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Standards landscape
• Generic standards (not service/MSaaS-specific)
– See next slide
• MSaaS-specific standards
– Service contracts (interfaces etc.)
– Service security
– Service identification
• Service orchestration
– HLA, DIS, Web Services
01 September 2015 M&S as a Service (MSaaS) 12
13. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Non service-specific standards
landscape (see AMSP-01)
01 September 2015 M&S as a Service (MSaaS) 13
MSDL
HLA,
DIS C-BML,
FOMs
SEDRIS, DTED,
GeoTIFF, …,
STF, GML, …
empty
NAF, DSEEP,
V&V, RIEDP
14. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Open issues (examples!)
• Scenario-related standards
– MSDL currently Army-centric, need to broaden scope
– Link required between MSDL and C-BML
• V&V-related standards
– Introduce risk-based assessment (see MSG-139)
– Add V&V to DSEEP (adapt FEDEP V&V-Overlay, tailor GM-VV)
See AMSP-01 or MSG-086 Final Report for more detailed
gap analysis.
01 September 2015 M&S as a Service (MSaaS) 14
15. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
From stove-piped systems to
service-based M&S
01 September 2015 M&S as a Service (MSaaS) 15
What is
MSaaS?
Standards
Landscape
MSaaS
Standards
16. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
WHY do we need additional
standards for MSaaS?
• Automation is key requirement for realizing the full
potential of cloud-based M&S
– Enable rapid usability and permanent availability
– Enable flexible workload management
– Cross-cutting requirement along whole simulation lifecycle
(deployment, initialization, execution, analysis)
• Automation = Minimization of manual interaction
– Less personnel required for operations
– More efforts required upfront
01 September 2015 M&S as a Service (MSaaS) 16
17. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Service/MSaaS-specific standards
requirements
Service
Specification
Service
Discovery
Service
Orchestration
Service
Initialization
Service
results/
outputs
01 September 2015 M&S as a Service (MSaaS) 17
• Standards are required along the whole lifecycle
– Service specifications, Service discovery, Service
initialization, Service orchestration, Service results, …
• Standards must come with additional guidance
– Recommended Practices Guides, Examples, etc.
– Support Tools, etc.
18. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Specification of service contracts
is critical issue
• Service contracts (across all levels of interoperability!)
– Functional specification of a service (I/O, …)
– Non-functional specification of a service (assumptions, constraints,
accessibility(!), …)
• Interface: Use standard modeling languages and set of models to
specify a service, e.g. UML, SysML, WSDL, …
• Open: How to specify non-functional properties?
– e.g., accessibility (=> security constraints, IdAM)
– e.g., assumptions/constraints (=> cp. conceptual modeling)
01 September 2015 M&S as a Service (MSaaS) 18
Service
Specification
Service
Discovery
Service
Orchestration
Service
Initialization
Service
results/
outputs
19. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
How to define appropriate services?
• How to decompose functionalities into services?
– i.e. how large/small should a service be?
• Document best practices
– E.g. prefer functional decomposition over object-oriented
decomposition
01 September 2015 M&S as a Service (MSaaS) 19
Service
Specification
Service
Discovery
Service
Orchestration
Service
Initialization
Service
results/
outputs
Service
Identification
20. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
How to interconnect services?
(“behind the scenes”)
• Re-use established architectures and technologies
– HLA, DIS, DDS
– Web Services (e.g., OGC WFS etc.)
– Enterprise Service Bus (e.g., RUDi, see MSG-131 Final
Report)
• Same challenges as today (data exchange model,
latency, bandwidth, …)
01 September 2015 M&S as a Service (MSaaS) 20
Service
Specification
Service
Discovery
Service
Orchestration
Service
Initialization
Service
results/
outputs
21. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
How to initialize services without
manual interaction?
• Simulation-specific initialization
– Terrain: WFS? WMS? … (OGC suite of standards) … STF?
– Performance data?
– Scenario, Units, Course of Action, 3d-models, …
• Simulation-independent initialization
– Identity and Access Management
– Configuration files (e.g., for automated deployment)
01 September 2015 M&S as a Service (MSaaS) 21
Service
Specification
Service
Discovery
Service
Orchestration
Service
Initialization
Service
results/
outputs
22. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Example: Need to create link between
scenario and simulation environment
01 September 2015 M&S as a Service (MSaaS) 22
Scenario data set
Initial state
(e.g., MSDL)
Course of events
(e.g., C-BML)
Termination
conditions
Simulation Environment
Execution Data Set
Execution-
specific data
Scenario data set
?
?
• Relationships between systems/services
and units
• Date, Host machine(s), …
?
Container
file format?
See also: Siegfried, et al., 12F-SIW-046
23. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Missing overarching standards
(examples!)
• Reference architecture for MSaaS and cloud simulation
– Technical Framework
– Cloud Management (“remote control”)
– Recommended practice(s) for creating simulation cloud
computing environments
• DSEEP SOA Overlay (see 14F-SIW-048)
• FEAT MSaaS Integration
• Identity and Access Management / Security
– e.g., use Labelling Mechanisms (STANAG 4774)
01 September 2015 M&S as a Service (MSaaS) 23
Service
Specification
Service
Discovery
Service
Orchestration
Service
Initialization
Service
results/
outputs
24. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Conclusions
• M&S will follow trend to more and more cloud
computing and on-demand capabilities
– Flexibly combine smaller (fine-grained) services rather
than (statically) deploy large monolithic applications
– Benefit from current developments in public IT sector
01 September 2015 M&S as a Service (MSaaS) 24
25. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
A Matter of Scale
01 September 2015 M&S as a Service (MSaaS) 25
20M
40M 183M
Active Military
Worldwide
Reserve Military
Worldwide
iPhone
Sales
Q1-Q3 2015
26. © 2015 aditerna GmbH – Reproduction, distribution and utilization of this document without express authorization is prohibited.
Conclusions
• M&S will follow trend to more and more cloud
computing and on-demand capabilities
– Flexibly combine smaller (fine-grained) services rather
than (statically) deploy large monolithic applications
– Benefit from current developments in public IT sector
• Missing standards and recommended practices
• MSG-136 attempts to fill in some of the gaps
01 September 2015 M&S as a Service (MSaaS) 26
27. www.aditerna.de
© 2015 aditerna GmbH
aditerna GmbH
Otto-Hahn-Str. 13 B
85521 Riemerling/Munich
Germany
Dr. Robert Siegfried
Managing Director, Lead M&S Expert
robert.siegfried@aditerna.de
+49 160 736 73 29