SIMULATION SUPPORT PLAN

1
SIMULATION SUPPORT PLAN MODELLING SIMULATION
REPOSITORY
Bob Elliott Pierre Gauvin SECO
JSMARTS VISION WORKSHOP
2
(No Transcript)
3
SimulationSupportPlan
4
Whats a Simulation Support Plan?

• Planning document
• Updated throughout life of project
• How and why MS will be used in project
• What are the requirements for MS resources?
• How will the simulations be supported?
• How will VVA done?

5
Principles

• Evolutionary document
• Becomes more detailed as the project matures
• Does not duplicate information found elsewhere
• Document must be value added

6
SSP Call up Deliverables

• Deliverables
• SSP Guideline and Template
• SSP Guideline and Template Use Case ADDNS
• SSP for ADDNS

7
13 SSP Template

• Simulation Support Plan
• Introduction
• References
• Project Overview
• MS Strategy
• MS Application
• MS Studies
• MS Management
• MS Resources and Facilities
• MS Acquisition
• MS Technology Support
• Funding Considerations
• MS VVA
• Appendices

8
(No Transcript)
9
Test case - ADDNS

• Advanced Deployable Day/Night Simulation
• The objective of this project is aid operational
  readiness by advancing the visual simulation
  capabilities of training simulators so that they
  can be better used for mission rehearsal.

10
1 Annex C and 13 Annex A - ADDNS
Visualization of the Advanced Deployable
Day/Night Simulation Facility
11
13 SSP Findings

• Value to the planning process for use of
  modelling and simulation
• Applicable to all phases of project
• Updated with project plan
• avoid repetition of material in other plans
• SECO extended call-up to proceed with
  coordination with DFPPC and ADM (Mat)

12
Advocacy

• SSP was briefed to
• DMASP
• DRDC
• DFPPC

13
Results

• Consensus emerging there is a need for some form
  of SSP as part of project documentation.
• Stand alone document or part of existing
  document?
• Work ongoing to adapt the template to the TDP
  Project Manager guidebook Pilot

14
MSRR
15
Where does it fit?
ENTERPRISE
ENTERPRISE MS
MSRR
16
Progressive Capability
repository
1
sim space
repository
repository
sim space
sim space
3
2
17
The Value Added

• Awareness
• Evaluation
• Decision on Use
• Determine changes and support
• Document Changes
• Feedback / Deposit

18
Basics

• Consistent, compatible, connected
• Phased Approach
• 80 / 20 Expectation
• Visibility
• Ease of Use
• Library Concept
• User Input / Contractor Support

19
Basics (2)

• Distributed (organizational or geographical)
• Security / Access
• Content Quality
• Meta Data
• Configuration Control
• Use Current Activities to Evaluate
• Use project structure to execute

20
MSRRFUNCTIONAL REPRESENTATION
Resources
Tech framework
Meta data
Models / simulations
Applications
Information
Support data bases
Common tools
Time change
1
Separate Entities
2
Consolidated catalogue Separate sources
3
Unconnected Nodes
PHASE 1
Distributed Connected nodes
4
PHASE 2
Fully integrated simulation space
5
PHASE 3
Levels content detail connection
A
B
C
E
D
Query Find Locate
Manage ment
Input Populate
Retrieve
Access
MSRR Basic Functions
21
PHASE 1OBJECTIVE

• Implement to level 3
• Level 1 Activity (Present Situation)
• Produce overall PIP
• Level 2 Activity (Catalogue, DND users models)
• Develop Search Strategy of DND Developers, Users,
  Models.
• Establish basic meta data for catalogue
  catalogue locations
• Establish Catalogue sites, collect Info, populate
  catalogue, implement process for continued
  updates
• Level 3 Activity
• Develop Meta Data for full up content, Each Org
  develops node at their rate, develop management
  and access processes
• Implementation spec for Phase 2
• Produce requirements definition
• Develop the interconnection spec and additional
  management processes for access, security etc.
• Produce implementation plan
• Definition for Phase 3
• Produce requirements definition
• Investigate and propose architecture, meta data,
  management processes for fully integrated on line
  simulation space

22
PHASE 1

• Develop Implementation Plan (SECO)
• Who are the stakeholders
• ( Organisational search by SEWG members assisted
  by SECO contractor )
• Structure resource search
• What do we want (level 2 meta data)
• (very basic, take what is available, SECO
  establish )
• What do we want (level 3 meta data)
• (developed by contract or by SEWG members MSECO,
  FFSE, )
• How will we get it
• (contractor assisted search )

23
PHASE 1 Level 2

• Compile catalogue (level 2 Meta Data)
• Sustain updates
• Develop node performance spec
• Define Node Implementation Metrics
• Finalize Level 3 Implementation Spec

24
Phase 1Level 3

• Each Node Implementation
• Provide Node map
• Provide current content status
• Continuous Process Managed by Node Owner

25
Phase 2

• Level 4 Activity
• Implement required interconnection links
• Implement required security and access controls
• Provide continued management functions
• Introduce additional nodes as required
• Level 5 Activity
• Finalize development of performance spec
• Produce draft management processes
• Produce Implementation Plan

26
Phase 3

• Level 5 Activity
• Implement integrated simulation space
• Implement Management processes
• Implement sustaining resources

27
(No Transcript)
28
Issues

• What are the essential requirements to support
  our MS goals
• Is project centrally driven or user driven
• Who supplies resources
• How do we integrate schedules