UNCLASSIFIED

UNCLASSIFIED1

Working Group

Brief-backs

UNCLASSIFIED

UNCLASSIFIED

• On 13 Mar 12, the Defense Security Accreditation Working Group (DSAWG) approved 24x7x365 connectivity of the ACGU enclave to Australia culminating a six year effort to fundamentally change the way information is shared among trusted mission partners.

• Working group will consider technical solutions to include non-ACGU nations, based on a validated operational requirement.

• The WG recommends closure of the WJTSC issue 11-011, Sustainment of ACGU Enclave. USPACOM, USEUCOM, USNORTHCOM, JMETC, Australia, Canada and Great Britain validated the operational need.

• Australia proposed that the four nations jointly fund the ACGU Enclave, which would be operated by JCW.

ACGU WG Brief-back

UNCLASSIFIED

UNCLASSIFIED

• Identified most “Troublesome” issues affecting JTS implementation as well as candidate solutions

• Uneven CSA leadership involvement/support for JTS; will request JS J7 briefing to CSA leadership

• CSA JTS resources remain limited, or are at risk, jeopardizing current level of JTS support

• CSAs need to be more aggressive in inserting their training needs into CCMD exercises

Combat Support Agency WG Brief-back

UNCLASSIFIED

UNCLASSIFIED

•Detail Cyberspace Range Strategy; identify lead proponent for Range Strategy implementation

•Support JCT&CS implementation activities for cyberspace workforce development

•Design an adversarial cyberspace TTP repository to inform Red Teaming and support scenario development

•Continue to utilize the JS J7 Joint Live Virtual Constructive (JLVC) development process to codify M&S requirements, development, perform gap analysis, and integrate additional capabilities into the joint manning environment to support cyberspace training

Cyber Training Initiative WG Brief-back

UNCLASSIFIED

UNCLASSIFIED5

• Deconflict competing GCC Exercise Requirements in May Timeframe

•GCCs Exercise Linkage With Alternating Annual Focus; e.g., Supported & Supporting Relationship

•Re-evaluate JTIMS Exercise RFF Business Rules

Joint Exercise Synch WG Brief-back

UNCLASSIFIED

UNCLASSIFIED

• Provided JKO system migration challenges from USJFCOM networks to Joint Staff mandated networks & the resulting significant operational ramifications.

• JKO Stakeholders provided input into changing PGO/PEP development processes.

•JKO content development/maintenance focal points:* CCMD exercise online training support (CoL)* JSO 101* Joint training enterprise mandatory training (i.e.; SERE100,

USFK Theater Specific Training, etc)

• Concluded CCMD discussion on integration of universal, interoperable JKO Learning Management System.

Joint Knowledge Online (JKO) WG Brief-back

UNCLASSIFIED

UNCLASSIFIED

• Discussed Joint Lessons Learned Program (JLLP) process improvements, integration of the JLLP across the joint force development enterprise and initiatives to track performance, program efficiency and compliance.

• Reinforced the 45-day deliberate observation validation timeline to transition exercise observations into the lessons learned process.

• Provided information on the Chairman’s lessons learned (LL) tasking to include current studies, Decade of War initiative, and identification of strategic themes.

• Reviewed current collaboration processes and capabilities, and identified additional requirements for effective information sharing across the JLLP.

• Developed the standard for JLL training and identified the key attributes of a successful LL program.

Joint Lessons Learned WG Brief-back

UNCLASSIFIED

UNCLASSIFIED

• Starting in FY 13 and across the FYDP, there are only sufficient JCW JNTC resources to buy, field, and sustain 35 JTEN 2.0 sites. Currently, there are 51 JTEN 1.0 sites supporting Service and CCMD programs.

Outcome of POM planning and provided as info to stakeholders.

CCMD and Service Reps question internal DDJ7 JCW resource allocations.

• Future of Joint Staff program centric approach for interaction with Service training programs.

Consensus that A/C/M needs to change based on strategic guidance.

– Desire to formalize “how” and intended end state.

Contentious discussion of SE funding status.

– How is expanded/refocused A/C/M accomplished without SEs?

– Services unwilling to commit Service core manpower to tasks in support of JCW activities if SE program is terminated.

• Will Service level exercises be considered for integration into the CCMD exercise program?

JNTC Corporate Board Brief-back

UNCLASSIFIED

UNCLASSIFIED

• Scope and membership of the Operational Technical Baseline Configuration Control Board to tackle sustainment of the baseline – Well understood process to input change request and achieve desired configuration controlled M&S

• Operational Technical Baseline should include exercise operation costs so exercise planners can make informed trade off decisions regarding technical capabilities versus cost

• The M&S strategy to transform from the current unsustainable JLVC federation to cloud-enabled modular services must be briefed and coordinated with the Service material and combat developers and reflect CCMD and other partner training and experimentation requirements

• Briefed JTEN 2.0 fielding plan to working group which will result in reducing the number of JTEN sites from 51 to 35

Joint M&S Capability WG Brief-back

UNCLASSIFIED

UNCLASSIFIED

•Continuum of eLearning concept development status briefed. A demo of a module was shown, as well as the integration of the CoL into PANAMAX 12 in support of USSOUTHCOM’s exercise.

-Questions regarding the costs in money and manpower to the CCMDs were raised and were answered.

•Joint Training System with Individual UJTLS was briefed with discussions regarding new Individual UJTs being developed that can be tied to the JMETs of the exercise.

-Was determined an issue wasn’t needed, only development of the tasks, and a change to the wording in both the Joint Training Policy & the Manual

• Joint Staff Officer 101 course update was presented. A great deal of work had been done the previous day at a sidebar on the course content and discussion of the issue slide.

-The issue slide has been updated. Work will continue with the CCMDs to tailor the program to support their needs. Name changed to “Joint Staff Officer Fundamentals”

• USSTRATCOM’s Onboarding program was briefed incorporating JSO program.

ISJT WG Brief-back

UNCLASSIFIED

UNCLASSIFIED

• Reviewed UJTL Maintenance and UTDT efforts: UJTL Scrub, Task Submission Standards, and NIPR UTDT

• Enforcement of policy: units editing tasks within DRRS violating policy

• Introduced CSA UJTL policy change for action

• Senior Leader UJTL Education continues to be an issue

UJTL UAG Brief-back

UNCLASSIFIED

UNCLASSIFIED

• Provided program update, discussed Force Sourcing business rules, and reviewed major v7.2 capabilities

• JTIMS Joint Master Scenario Events List (JMSEL): Develop a Test

and Validation Plan, based on stakeholder execution criteria

• The community must have J7 DD-JCW support (specifically MSEL managers/Collective Training) for this effort to succeed.

• Business rules: SMEB process and Security Classification issue

JTIMS UAG Brief-back

UNCLASSIFIED

UNCLASSIFIED

WJTSC 12-1Master Issue Deck

WJTSC 12-1 as of: 22 Mar 12

UNCLASSIFIED

UNCLASSIFIED

Issue 07-017: Combatant Commanders require a distributed, integrated, synthetic Integrated Air and Missile Defense (IAMD) training and exercise modeling and simulation (M&S) capability.Discussion: a. Current capability requires duplicative, static, scenario development and does not provide synergistic training capability. b. There is a requirement for a federated joint IAMD simulation capability which will stimulate applicable operational IAMD awareness systems simultaneously to meet all stakeholders missile warning and IAMD simulation requirements. Endstate: A federated Joint IAMD simulation capability which will stimulate applicable operational awareness systems to meet all missile warning and integrated air and missile defense simulation requirements.POA&M: Short Term: Develop a federated IAMD simulation capability that will stimulate applicable operational missile awareness systems for IAMD. Interim solution for training tiers 1-3. Initial distributed capability demonstrated during GL/AC 11. Initial Prototype delivered to USSTRATCOM Nov 11. Prototype testing begins Dec 11.Long Term: Integrate / federate M&S capabilities from tiers 1-4 into a complete end to end IAMD M&S capability 0-5 years.OPR: USSTRATCOM; OCRs: USNORTHCOM, JS J-7 JCW, Missile Defense Agency, CCMDs, Services

Integrated Air and Missile Defense (IAMD) Systems Training Capability

Briefer: Mr. McVay Updated 6 Mar 12

NOV 11

Initial Prototype delivered to

STRATCOM

Prototype testing at STRATCOM

DEC 11 GT 14

ATM First Use

JAN 12

Prototype User

Feedback

APR 12 AUG 12

Fund Prototype Enhancements

JLVC 7.0 CDC

MAR -JUN 13

JLVC 7.0 Integration

UNCLASSIFIED

UNCLASSIFIED

Issue 10-011: CCMDs require a focused approach to cyberspace training that enables Joint Force Commanders to train cyberspace forces, integrates joint training efforts, and sustains cyber user awareness.

Discussion:

a. Refine M&S roadmap, finalize M&S Issue Description, initiate Mission Capability Analysis

b. Detail Cyber Range strategy; Expand Cyber Flag network configuration to integrate into CCMD exercises

c. Joint Cyberspace Training and Certification Standards (JCT&CS) implementation

Endstate: IAW CJCS Memo for DPPG for Cyber Education and Training, dtd 06 Jan 2012, provide an integrated cyberspace training approach that incorporates user awareness, joint cyber education and training, cyber range, and simulation capabilities for the DoD Community of Interest (COI).

POA&M:

Short Term: Conduct Cyber-planner MTT, Execute Cyber Flag, Integrate CCMD Cyber-exercise, Template Cyber scenario design, conduct User Awareness Pilot program, and analyze M&S requirements.

Long Term: Identify JCT&CS implementation, Refine Cyberspace Workforce Development, Coordinate CTI with NICE, Project unique future requirements and tools for distributed Cyberspace training environment, Engage existing DoD assessment activities for Cyberspace training.

OPR: USSTRATCOM; OCRs: USCYBERCOM, JS J-7, CCMDs, Services, CSAs, OSD P/R, DISA, NII/CIO

Cyberspace Training Initiative (CTI)

Briefer: Mr Kemper Updated 21 Mar 12

APR 12 MAY 12 OCT 12SEP 12MAR 12

Cyber MTT –USPACOM, NICE Conf

JCT&CS Implement

Cyber Flag 13-1Cyber MTT-USSTRATCOM

TF 12, GL12, Cyber MTT-

USAFRICOM

JUN 12

Cyber MTT- USCENTCOM

UNCLASSIFIED

UNCLASSIFIED

Issue 11-001: Combatant Commanders and services require distributed, integrated, synthetic space training and exercise capability for space forces to conduct realistic operational training in a synthetic environment and provide simulated space data for joint warfighter exercises and training.Discussion: a. Current capability requires duplicative, static, scenario development and “white carding” and does not provide synergistic training capability. b. There is a requirement for a federated joint space simulation capability which will stimulate all applicable space awareness systems simultaneously to meet all stakeholders simulation requirements. Endstate: The Joint Space Training Federation will create the ability for space forces to conduct realistic operational training in a synthetic environment and provide simulated space data for joint warfighter exercises and training.POA&M: Develop capabilities that allow commanders, battle staffs and operators to train and exercise using their real-world C4 devices (or a realistic replication) in response to realistic stimuli via JCIDS process. Results of Analysis of Alternatives (AoA) report will lead to determination of further milestones.OPR: USSTRATCOM; OCRs: AFSPC, Services

NOV 11

• JROC-approved Initial Capabilities

Document

MAR 12

Material Development

Decision

JAN 13

• AoA Complete• Milestone A

APR 12

Begin Material Solution Analysis

Phase/AoA

Joint Space Training Federation (JSTF) Space Training Capability

Briefer: Mr. McVay Updated 6 Mar 12

UNCLASSIFIED

UNCLASSIFIED

Issue 11-006: Joint Staff Joint Concept Development & Experimentation (JCD&E) efforts have not efficiently leveraged joint exercises in order to enhance concept development and experimentation to validate and deliver solutions to the warfighter.

Discussion: Historically, Joint Concepts and Experimentation, and Joint Exercises have not been formally linked in planning and execution over time. JS J-7 desires to investigate integrating potential capability solutions identified in concept development and experimentation plans from the Program of Work, into experimental variations on planned Joint Exercise training objectives.

Endstate: A more efficient means of evaluating potential capability solutions by leveraging planned CCMD and Service exercises. Alignment of Commander’s capability gaps (as identified by JCD&E needs, Integrated Priority Lists, etc…) with potential capability solutions synchronized with exercise and experimentation opportunities equal success.

POA&M: Short Term: Identify the planning cycles for JCD&E and Joint Exercises, identify types of candidate experimentation projects and exercise opportunities, develop the integrating function and events, discuss and develop proposed language changes for CJCSIs 3010 and 3500.

Long Term: Synchronize the planning cycles to increase opportunities for resource efficiency and application leading to potential use of Joint Training and Exercises for embedded experimentation.

OPR: JS J-7 SP; OCRs: OSDAT&L, Joint Staff, CCMDs, Services, NGB, Coast Guard

FEB/MAR 12 APR /MAY 12 JUN 12 JUL 12SEP 11

Brief the Issue; establish

Stakeholders

Initial DRAFT process identified; Incorporate

new Guidance

JSAP recommended process; Brief for

decision

JCDE Integration into Joint Exercise Program

Briefer: COL ParsonsInitiated 30 Aug 11 Updated 21 Mar 12

Update brief to WJTSC Work Group

MAR 12

DRAFT process identified; solicit

feedback

Implement formal process changes-Execute for FY

UNCLASSIFIED

UNCLASSIFIED 18

Issue 12-001: Scheduling resources to support combatant command events is challenging given that there are areas of the calendar that are more desirable to conduct exercises. April/May time frame allows exercises to be completed prior to the summer personnel transfer cycle and August/September allows exercises to complete prior to the end of the fiscal year and holiday season. Competing requirements continue to build in those time frames stretching the limits of enterprise exercise support resources.

Discussion: Constrained enterprise resources preclude the simultaneous support of competing exercises requiring deployable training teams, models and simulation, Command/Control/Communications/ Computers/Intelligence support, Joint Staff and or Department of Defense Subject Matter Experts, and/or Cyber Command and USTRANSCOM assets. There is no process to leverage national strategic guidance, prioritize exercises and force deconfliction of competing requirements.

Endstate: Robust resolution process run by Joint Staff involving all stakeholders that effectively de-conflicts the joint exercise schedule. Conflicting issues to be resolved by the Combatant Commanders Exercise Engagement Stakeholder Leadership Team .

POA&M: Joint Staff institutionalize the criteria for prioritization to assist in adjudication during their exercise scheduling conferences with stakeholder representation (combatant commands, Services).

OPRs: Combatant Commands; OCRs: Joint Staff J-7, Services

De-confliction of Exercises

DEC 11

Presented at CoC VTC for review

MAR 12 MAR 12 SEP 12

Initiated 15 Dec 2011 Briefer: Dr Eaddy Updated 21 Mar 12

CE2 SLT discussion/ recommendations for

Scheduling/Resolution Process

Brief proposed Scheduling/Resolution

Process

CCMD Ex Program Scheduling/Resolution

Process formalized

UNCLASSIFIED

UNCLASSIFIED

Issue 11-008: The USJFCOM disestablishment and fiscal realities have created change that has altered the original mission and intent of the Joint National Training Capability (JNTC). The program should be re-baselined to ensure its effort is appropriately scoped and focused.

Discussion: The standup of DDJ7 Joint and Coalition Warfighting changed key elements of organization structure, resources, mission, priorities, processes, and governance, which directly impact the JNTC program as originally envisioned and established 10 years ago. To remain viable and an effective asset in supporting Service and Combatant Command training programs and the joint training environment, the JNTC program’s value, cost, priorities, processes, and governance must be evaluated and redefined.

Endstate: A program that continues to provide joint training programs with a realistic training environment, using a transparent and collaborative business process to identify demand driven requirements, focused and prioritized to meet program goals in a constrained fiscal environment.

POA&M: Short term plan to meet FY 13 goals completed at Oct JNTC Corporate Board, Stage 2 of effort completed 13 Dec, integrated long and short term plans. Added minimum training capabilities to document; schedule pushed to right. Third draft sent to stakeholders for comment. Remaining -- get approval for key strategies, begin to “re-brand” JNTC, execute the plan and strategy, and assess and adjust scope and focus.

OPR: JS J-7 JCW (Service Coordination Branch); OCRs: Services, Combatant Commands

SEP 11 DEC 11OCT 11

Identify Issue

Prepare FY 13 short

term plan

Develop long term

plan

DJ7/OSD approve

key strategies

Begin to execute the

plan

DEC 11 AUG 12

Briefer: Mr LawverInitiated 27 Sep 2011

JNTC Re-Baselining

Begin tore-brand JNTC

APR 12 JUN 12APR 12

Integrate plans

Assess and adjust plan

Updated 21 Mar 2012

UNCLASSIFIED

UNCLASSIFIED

Issue 11-007: The USJFCOM disestablishment resulted in the elimination of the JNTC Opposition Force (OPFOR) program. Service stakeholders consider the JNTC OPFOR program, which provided joint, integrated tactical level OPFOR systems, one of their highest priority programs.

Discussion: During the USJFCOM disestablishment efficiencies discussions, the JNTC OPFOR program was considered redundant to other Service OPFOR programs. OPFOR resources managed by the JNTC program for the joint training environment were subsequently eliminated. Development, procurement, and sustainment of these tactical level joint systems was considered by the Service stakeholders to be a critical element of joint context within their tactical level training programs.

Endstate: A jointly managed OPFOR program that provides a realistic joint training environment at the tactical and operational level, commensurate with clearly identified needs within a resource constrained environment.

POA&M: Clarified requirements at 13 Dec JNTC Corporate Board, selected a course of action, established program management business rules for planning and execution, and submitted requirements for resourcing. Remaining -- approve funding allocations, and execute the plan.

OPR: JS J-7 JCW (Service Coordination Branch); OCR: Services, JS J-7 SP, OSD TRS

SEP 11 FEB 12DEC 11

Identify Issue

Clarify requirements

Select Course of

Action

Establish business

rules

Execute plan

JAN 12 OCT12

Briefer: Mr LawverInitiated 27 Sep 2011

JNTC OPFOR Management Strategy

Submit requirements

into JNTC budget Process

MAR 12

Approve funding

allocations

JUN 12

Updated 27 Feb 12

UNCLASSIFIED

UNCLASSIFIED

Issue 11-009: Delays in receipt of CE2T2 funds at beginning of FY place the CE2T2 enterprise at risk and cause decreased CE2T2 obligation rates

Discussion: Under current fiscal environment, CCMD support agencies are no longer able to cash flow CE2 exercise engagements while CCMDs await CE2 O&M funds. Additionally, the Services are no longer able to cash flow T2 initiatives while the Services await T2 funds. Historically, CE2T2 funds do not get disbursed to JS until mid-November. Having CE2T2 funds disbursed earlier in the fiscal year allows CCMDs and Services to smooth flow exercises and training initiatives throughout the fiscal year.

Endstate: CE2T2 funds disbursed (or spending authority given) NLT first business day of the fiscal year.

POA&M: Determine base line requirements, determine impacts of late funding to CCMD joint exercise plans, develop way ahead with OSD & WHS.

OPR: JS J-7 SP (JETD); OCRs: OSD, CCMDs, Services

MAR 11

Briefer: Lt Col Scherzer Updated 6 Mar 12Initiated 14 Mar 11

Beginning of FY CE2T2 FundsUNCLASSIFIED

Issue identified

SEP 11

Baseline requirements

identified

MAR 12

Develop way ahead with OSD/WHS for

FY13

OCT 12

CE2T2 funds provided to CCMDs/Services early in

FY as required

UNCLASSIFIED

UNCLASSIFIED

Issue 11-010: Lack of a defined technical baseline to support Joint Force Development has resulted in duplication and inefficiency in the community.

Discussion: The current technical baseline supporting Joint Force Development is not formally documented. As a result, development efforts are initiated without reviewing the baseline to determine if capability already exists, if it is planned, or if it is required. In a resource constrained environment we must describe what Joint capabilities we currently have to determine where we are going based on what we need.

Endstate: A collaborative, disciplined process to establish and control the baseline to enable efficient management and effective use of research and technologies in support of Joint Force Development.

POA&M: Identify the scope and membership of the operational technical baseline configuration control board. Execute the first operational technical baseline configuration control board.

OPR: JS J-7 JCW (JOSE); OCRs: CCMDs, Services

MAR 12

Briefer: Mr VinettInitiated 26 Sept 11

Joint Force Development Tech BaselineUNCLASSIFIED

APR 12 MAY 12 JUL 12 AUG 12

Execute Operational Technical Baseline Configuration Control Board

OCT 12

Brief status to M&S WG

JUN 12 SEP 12

Updated 21 Mar 12

ID scope and membership of the Operational Technical Baseline Configuration Control Board

UNCLASSIFIED

UNCLASSIFIED

Issue 11-011: Lack of defined operator need for Australia, Canada, Great Britain, United States (ACGU) Training Enclave has resulted in a technical solution without long term sustainment.

Discussion: ACGU Training Enclave grew out of an Australia Minister of Defence - US Secretary of Defense memorandum of agreement. POTUS directed a fundamental change in the way the US shares information with its trusted mission partners. Technical community built on the Australian DTEN – US JTEN connection to put in place a solution consistent with POTUS intent. Lack of a defined ACGU requirement has resulted in a technical solution without long term sustainment. Detailed operator requirements and wider audience (experimentation, testing and concept development) buy-in is now needed for the project to survive.

Endstate: Full operator buy-in, event scheduling and support for ACGU Training Enclave. ACGU Training Enclave exists because an operator needs it.

POA&M: ACGU countries brief leadership on enclave capabilities, use existing ACGU collaborative forum to document requirement, vet and analyze requirement, propose final technical architecture and resources required to implement and sustain, present to Stakeholder Leadership for approval.

OPR: JS J-7 JCW (JOSE); OCRs: C/S/A, Australia, Canada, United Kingdom

SEP 11 JAN 12OCT 11

Identify issue

ACGU countries brief

leadership

Document draft

requirement

Identify resources

Present to Stakeholders

NOV 11 MAR 12

Briefer: Mr VinettInitiated 28 Sept 11

Sustainment of ACGU Enclave

Vet and analyze

requirement

DEC 11 FEB 12

Proposed final

architecture

Updated 21 Mar 12

UNCLASSIFIED

UNCLASSIFIED

Joint Staff Officer Proficiency

Issue 08-017: The ramp up time to achieve desired proficiency for officers reporting for joint assignment at combatant commands is too long.

Discussion: The results of the Joint Staff Officer (JSO) Study included the desired 15 core competencies for Joint Staff Officers identified by combatant command senior leadership. Lack of competency in identified areas were found to result in extended ramp up time for officers to achieve desired proficiency levels in joint staff officer tasks. Combatant commands expressed interest in the Joint Staff J-7 leading the development of Joint Staff Officer training support resources to close the identified proficiency gap.

Endstate: Establish an individual learning curriculum that leads to the reduction in time for officers to become proficient in joint staff officer duties. By using metrics, assess the implementation of the curriculum to determine if the ramp up time has been decreased.

POA&M: Joint Staff J-7, in coordination with the combatant commands: develops joint staff officer training support resources; designs draft JSO individual learning curriculum leveraging existing resources; makes curriculum development decisions and assigns responsibilities; develops draft JSO curriculum, conducts Alpha tests; and delivers JSO materials to CCMDs. CCMDs, with JS J7 support determine and adopt efficient and effective delivery methodology and determine performance measures. CCMDs integrate final JSO curriculum into training programs as desired.

OPR: JS J-7 JCW; OCRs: Combatant Commands, National Guard Bureau

Briefer: Ms Lape

JSO Curriculum Frameworkcomplete

SEP 10 JAN-MAR 12

Handbook 2nd EditionFinalized

AUG 11 SEP-NOV 11

JSO 101Alpha Tests

Updated 20 Mar 12

DeliveryMethodology

Options Identified

JAN-AUG 12

JSO 101 Draft

Curriculum Finalized

AUG 12

JSO materials

delivered to CCMDs

DevelopPerformance Metrics

Assess Issue Status

SEP 12 SEP 13

UNCLASSIFIED

UNCLASSIFIED

Joint Issue Management CapabilityJoint Issue Resolution Tracking Process

Briefer: LtCol Pappas Updated 21 Mar 12

MAR 10

WJTSC10-1

IR WG

SEP 10

WJTSC10-2

CJCSMWG

MAY 10

CJCSMIR WG

MAR 11

CJCSMapproved/WJTSC

11-1

JUN 11

N-Tierdeployment

v2.1complete

FY12

Continue to enhance/ refine JLLIS issue

management capability

Initiated 31 Mar 09

SEP 11

CJCSI3150.25Ereleased

for plannerchop

MAY 12

Change 1to

CJCSM3150.25

OCT 11

JLLISv2.3

deploymentof IMC

JAN 12

JLLISv2.4

EnhancedIMC

MAR 12

CJCSI3150.25Eapproved

UNCLASSIFIED

UNCLASSIFIED

Joint Training Information Management System (JTIMS) Joint Master Scenario Event List (JMSEL)

Issue 10-012: Transition from legacy JMSEL v2.6 to JTIMS JMSEL Enterprise contingent upon system reliability and functionality.Discussion: Transition plan discussed during JTIMS UAG, WJTSC 10-2. Legacy JMSEL v2.6 data migration to JTIMS JMSEL (Enterprise); enhanced system availability and support; and costs associated with maintaining a separate JMSEL standalone environment. All commands and Combat Support Agencies agree that community needs to migrate to JTIMS JMSEL (Enterprise) but some expressed concerns that supporting organizations rely heavily on JMSEL v2.6. Endstate: Complete data migration from legacy JMSEL v2.6 to JTIMS JMSEL (Enterprise); JTIMS failover and backup capabilities deployed, tested and validated; JTIMS JMSEL application enhancements developed and deployed in FY11; and a timeline established, in coordination with commands/agencies, for shut down legacy JMSEL v2.6.POA&M: JS J-7 develop a timeline and plan to import legacy JMSEL v2.6 data into JTIMS JMSEL (Enterprise); complete hardware/architecture improvements, and capture new requirements to support JTIMS JMSEL implementation. Conduct training and develop JTIMS JMSEL test and validation plan with stakeholders.OPR: JS J-7 SP (JETD); OCRs: Combatant Commands, CSAs, Services

Briefer: LTC Ray

Finalized JTIMS JMSEL application requirements with

stakeholders

JTIMS JMSEL version upgrade

and finalize migration

timeline

OCT 10 JUN 11

JTIMS JMSEL Legacy data migration capability fielded

Updated 20 Mar 12Initiated 22 Sep 10

FEB 12

JTIMS JMSEL operational system of

record for MSEL development/execution

MAR 13MAR 12

TransitionPlan way ahead

discussedwith UAG

Develop Test and Validation Plan with

Stakeholders

JUL12 SEP 12

Brief Test and transition update to

UAG.