Live-Virtual-Constructive (LVC) Technologies – Introduction

Slides:



Advertisements
Similar presentations
Walt Okon Senior Architect Engineer
Advertisements

MDI 2010, Oslo, Norway Behavioural Interoperability to Support Model-Driven Systems Integration Alek Radjenovic, Richard Paige The University of York,
ANSI/ASQ E Overview Gary L. Johnson U.S. EPA
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
Software Engineering Techniques for the Development of System of Systems Seminar of “Component Base Software Engineering” course By : Marzieh Khalouzadeh.
Introduction and Overview “the grid” – a proposed distributed computing infrastructure for advanced science and engineering. Purpose: grid concept is motivated.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Introduction to Systems Analysis and Design
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Bina Nusantara 2 C H A P T E R INFORMATION SYSTEM BUILDING BLOCKS.
Understanding Data Warehousing
NDIA SE Division Meeting February 13, Developmental Test and Evaluation Committee Beth Wilson, Raytheon Steve Scukanec, Northrop Grumman Industry.
9/11/ SUPPORT THE WARFIGHTER DoD CIO 1 Sample Template Community of Interest (COI) Steering Committee Kick-off Date: POC: V1.0.
Solution Architecture
UNCLASSIFIED Joint and Coalition Warfighting Mr. John Vinett March 2012 Technical Baseline Capability.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
JAUS Architecture Overview. Why did we need JAUS? “Stove-Pipe” Design Subsystems common to all Unmanned Systems (US) were previously built from scratch.
Software Requirements Engineering CSE 305 Lecture-2.
High Level Architecture Overview and Rules Thanks to: Dr. Judith Dahmann, and others from: Defense Modeling and Simulation Office phone: (703)
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
Enterprise Architecture, Enterprise Data Management, and Data Standardization Efforts at the U.S. Department of Education May 2006 Joe Rose, Chief Architect.
The High Level Architecture Introduction. Outline High Level Architecture (HLA): Background Rules Interface Specification –Overview –Class Based Subscription.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Draft GEO Framework, Chapter 6 “Architecture” Architecture Subgroup / Group on Earth Observations Presented by Ivan DeLoatch (US) Subgroup Co-Chair Earth.
EPA Geospatial Segment United States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Segment Architecture.
United States Department of Justice Achieving Information Interoperability and Business Agility The Justice Reference Architecture:
A Net-Centric DoD NII/CIO 1 Sample Template Community of Interest (COI) Steering Committee Kick-off Date: POC:
OVERVIEW OF RESEARCH METHODS Dr. Kimaro. INTRODUCTION Why Research; Increase body of knowledge Explain social phenomena Test theoretical hypothesis Explain.
1 / x CMMI Technical Solution Rob Vanden Meersche Dieter Van den Bulcke.
Issues in Ontology-based Information integration By Zhan Cui, Dean Jones and Paul O’Brien.
Service Oriented Approach JAFE: a Joint architecture federation environment Howard cohen (Booz Allen Hamilton) Matthew Sutton (Booz.
0 Enabling Strategic Acquisition in DoD Small Business Opportunities in eGov Transformation May 7, 2004 York, PA Mark E. Krzysko Defense Procurement and.
Live-Virtual-Constructive (LVC) Federation Engineering Marine Corps M&S Management Office (MCMSMO) Presented by Katherine L. Morse, PhD JHU/APL 27 August.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Behavioral Framework Background & Terminology. Behavioral Framework: Introduction  Background..  What was the goal..
JNTC Joint Management Office
California Department of Public Health / 1 CALIFORNIA DEPARTMENT OF PUBLIC HEALTH Standards and Guidelines for Healthcare Surge during Emergencies How.
UNCLASSIFIED 1 United States Joint Forces Command Joint Warfighting Center United States Joint Forces Command Joint Warfighting Center LTC John Janiszewski.
Representing nursing in SNOMED CT Proposal for TR or Guideline.
Tools And Resources. Group Make Up OrganizationQuantity NAVY3 USMC9* USAF5 Army2 DoD3 Other3* *=Election Tampering Evident.
IPDA Architecture Project International Planetary Data Alliance IPDA Architecture Project Report.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
VA Internal Use Only 1 Product Architecture Recommendation Briefing Template.
Introduction To Modeling and Simulation 1. A simulation: A simulation is the imitation of the operation of real-world process or system over time. A Representation.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
Dr. Ir. Yeffry Handoko Putra
Live-Virtual-Constructive (LVC) Overview
Live-Virtual-Constructive (LVC) Federation Engineering
AIM Operational Concept
Introducing Statistical Standards -GAMSO
Chapter 6 System Engineering
Overview of System Engineering
13 November 2018.
Technical Management Processes
Systems Analysis and Design in a Changing World, 6th Edition
CS 8532: Advanced Software Engineering
GPP Training Toolkit An Introduction European Commission
, editor October 8, 2011 DRAFT-D
16: Program and Project Evaluation
Systems Architecture & Design Lecture 3 Architecture Frameworks
Agenda Purpose for Project Goals & Objectives Project Process & Status Common Themes Outcomes & Deliverables Next steps.
Geospatial-Intelligence Standards: The Basics Introduction
MSDI training courses feedback MSDIWG10 March 2019 Busan
Interoperable Communications Technical Assistance Program
Perspectives on Transforming DT and OT Industry-Government Roundtable
Recent Standardization Activities on Cloud Computing
Module 1.1 Overview of Master Facility Lists in Nigeria
Presentation transcript:

Live-Virtual-Constructive (LVC) Technologies – Introduction Katherine L. Morse, PhD JHU/APL 5 November 2015 These slides are the introduction to the live virtual constructive (LVC) technologies class. They provide the framework for the individual LVC technology classes that follow.

Class Outline Training goal and objectives Template LVC technologies Architecture Management Integration Environment (AMIE) Navy Continuous Training Environment (NCTE) Distributed Interactive Simulation (DIS) High Level Architecture (HLA) As with the other classes in this series, the LVC Technologies class begins with the training goal and objectives. This is followed by a template for the subsequent classes on individual LVC technologies. These subsequent classes are on standards-based technologies such as HLA and DIS, and two architectures prominent in the DON for integrating simulations. These integration architectures are focused on different domains that are supported by LVC simulations, as we will see in subsequent classes. One focuses on system of systems testing and the other focuses on training. The current version of the course covers these 4 technologies. This only represents a few of the LVC technologies relevant to USMC LVC development and integration. Future versions of the course will cover additional technologies.

Training Goal Problem - the possibility exists that many disparate and isolated LVC related efforts occurring within the Department of the Navy (DoN) may produce incompatible solutions (both amongst themselves and with other Joint solutions) which will: Create duplicative capabilities, Consume limited DoN resources, and Introduce unnecessary technical and operational risks. Solution - educate LVC users to make informed decisions based on knowledge of LVC: Overview LVC Federation Engineering Technologies Policy and guidance The purpose of this training is to address the problem of many disparate and isolated LVC related efforts within the Department of Navy that may and do produce incompatible solutions both amongst themselves and with other joint solutions. This problem results in duplicative capabilities that consume limited Department of Navy resources, and introduce unnecessary technical and operational risks. The solution to this problem is to educate LVC procurers to make informed decisions based on knowledge of LVC. This particular class focuses on technologies. Terminology, LVC federation engineering, and policy and guidance are covered in other classes in this course.

Training Objectives Learn to make informed decisions based on knowledge of LVC ELO 1: Identify LVC technologies applicable to Navy and USMC missions ELO 2: Differentiate capabilities and applications of LVC technologies The primary training objective for this class is to learn to make more informed decisions based on knowledge of LVC. The two enabling learning objectives for this are: to identify LVC technologies applicable to Navy and USMC missions, and to differentiate capabilities and applications of LVC technologies.

LVC Technology Description Template Purpose Technical overview Architecture Capabilities Components Previous uses / applications Training (individual, collective / unit, staff) Testing (DT&E, OT&E) Acquisition (engineering / design, human factors, cost modeling) Analysis Experimentation Planning Education & Formal Training Limitations Individual Interoperability Supporting technologies POCs References Because there are several LVC technologies to review, we have developed a template for the individual classes. Each technology is described in terms of its purpose, a technical overview, previous uses and applications, limitations both individual and interoperability, and supporting technologies such as hardware, operating systems, compilers, and protocols and architectures. Individual limitations describe a technology’s inability to represent some phenomena that the student might expect to be in scope. Interoperability limitations describe the inability to interoperate with other technologies, e.g. lack of support for the most current version of an architecture or protocol. Each class concludes with points of contact and references for the student to seek additional information relevant to their specific mission. Where such information is available, we provide OV-1 and architecture graphics. We also describe each technology’s capabilities at a high level and any constituent components. Not all technologies are equally applicable to the domains supported by LVC listed on the slide, so we specifically identify where the technologies can and have been applied.