CJT PWS - Deliverables.pdf

PDF 309 KB Posted

Attached to
Collective Joint Training
Solicitation number
N0018926QD026
Issued by

About this file

This is Attachment I to a Performance Work Statement for the Joint Staff J7 Deputy Directorate for Joint Training (DDJT) Collective Joint Training program. It is a comprehensive deliverables table containing 143 tasks organized across multiple functional areas required to support joint training exercises, events, and academic seminars throughout a period of performance (PoP).

The deliverables span exercise planning and design, operational environment development, technical infrastructure, intelligence support, security compliance, administrative functions, and lessons learned documentation. Key planning deliverables include Collection Management Plans due 14 working days before exercises, Exercise Plans with draft submission 7 calendar days prior to Initial Planning Conference (IPC), Plans of Action & Milestones (POA&M), and various scenario development products (Road to Crisis, In-Exercise Scenarios, Master Scenario Event Lists) due 5 days prior to IPC and updated throughout the Joint Exercise Life Cycle (JELC). Operational environment deliverables encompass concept briefings, synchronization matrices, adversary campaign plans, OPFOR concept of operations, and supporting reference materials updated quarterly. Technical support includes manning documents for modeling and simulation (M&S), Command Control Communications and Intelligence (C4I), order of battle development, network operations center watch bills, and cybersecurity incident reporting. Intelligence deliverables require Intelligence POA&Ms, manning rosters, consolidated intelligence support requests, and target packages. Exercise execution support includes After Action Reviews due 30 calendar days post-Facilitated After Action Review, Post Exercise Reports due 45 calendar days post-event, and lessons learned documentation produced approximately 6 times annually. Additional deliverables address administrative requirements including monthly financial and status reports, weekly activity reports, standard operating procedures, quality control plans, and conference support materials. Points of contact vary by functional area, with responsibilities distributed among DDJT Desk Officers, Event Planners, Branch Chiefs, and technical teams. Due dates range from daily reporting requirements to quarterly and annual submissions, with many deliverables requiring updates throughout the JELC timeline and exercise execution.

View the file

Other files

File Type Posted
N0018926QD026 - A003 Q-A.pdf PDF
N0018926QD026 A003.pdf PDF
CJT_DD 254 Block 13 Addendum.pdf PDF
Amendment 0002 -N0018926QD026 Q-A.pdf PDF
Conformed RFQ N0018926QD026 (As of Amd 0002).pdf PDF
Amendment 0002 - N0018926QD026.pdf PDF
Amendment N0018926QD026 0001.pdf PDF
Past Performance Information Form.docx DOCX document
QASP.pdf PDF
CJT PWS Acronyms.docx DOCX document
CJT PWS.docx DOCX document
CJT PWS Minimum Labor Category Requirements.pdf PDF
Solicitation - N0018926QD026.pdf PDF
DD 254 - CJT.pdf PDF
Contract Administrative Plan.pdf PDF
Show all 15

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Joint Staff J7 Deputy Directorate for Joint Training (DDJT) Collective Joint Training

Performance Work Statement

Attachment I – Deliverables Table

# Task Ref Deliverable Name Description Due Date POC

1 5.3.1, 5.11.2.10, Collection Management Plan

(CMP)

Captures the compilation of research, analysis, and lessons learned for a specific training event tailored to the training audience.

Due 14 working days prior to the exercise

Chief A/T

2 5.3.2-5.3.5, 5.6.4, 5.7.34.4 5.11.2.14, 5.11.4.2

Analytical Research and Planning Documentation

Addresses research, analysis, summaries and inputs; includes reports, doctrinally based documents, executable policy, guidance, instructions, analytical input throughout the entire PWS.

IAW SOPs, guidance, the JELC and written correspondence and POA&M timelines.

DDJT Desk Officers, Government Leads across Branch POCs

3 5.5.2, 5.5.2.2, 5.5.2.7

JTT Documentation JExD JTT SOP, business rules adapted to each exercise, Monthly Newsletter, JTT training syllabus, identifies trends, battle rhythms, reoccurring themes, noted points of the exercise and lessons learned

JTT products, plan events, create and manage storylines, MSELs, timelines, presentations, OOB, military graphics and symbols that operate throughout all JELC events

DDJT Desk Officers, Government

4 5.6.1 Exercise Plan Exercise plan identifies the purpose, overview, dates and exercise objectives

Draft NLT 7 calendar days prior to IPC IAW JELC.

Final due 14 calendar days after the MPC IAW JELC

DDJT Desk Officers Event Planner or Government Lead

5 5.6.2 Plan of Action & Milestones

(POA&M)

Toot that identifies tasks that need to be accomplished, resources required to accomplish the plan, milestones for meeting the tasks, and the scheduled completion dates for the milestones.

IAW SOPs, policy, guidance, the JELC and written correspondence.

DDJT Desk Officers, Government

6 5.6.3 Event In-Progress Review (IPRs) Presentations

A review of POAM, action items, deliverables, and timelines for next major event

Throughout the JELC and throughout the PoP

DDJT Desk Officers, Government

7 5.6.6.1 Exercise Portals Identifies the information exchange requirements within the JECG and between the JECG and the training audience.

Daily Desk Officer, OE Branch Chief, Event Planner or Specified Branch POC

8 5.6.6.2 Exercise Control Group IM/KM Plan

Identifies the information exchange requirements within the JECG and between the JECG and the training audience.

Daily Desk Officer, OE Branch Chief, Event Planner or

9 5.7.1 Exercise Support Manning Document

(ESMD).

Record of manning requirements, including training audience, and the ECG

Draft due NLT 10 working days prior to IPC Refined due NLT 10 working days prior to MPC Final 10 working days prior to FPC. Deliverable is published 5 days prior to CCMD TPFDD validation date and updated through event execution.

Desk Officer, OE Branch Chief, Event Planner or

10 5.7.3 Room Build and Floor Plan

Plan depicts seating chart and equipment of exercise billets based from ESMD requirements.

Draft due NLT 10 working days prior to each JELC event.

Deliverable is published 5 days prior to ESMD validation date.

Desk Officer, OE Branch Chief, Event Planner or

11 5.7.4 Event Systems Identification

Identifies the type of systems required and the associated locations, number of systems, and classifications of the systems and how the systems connect.

Draft due NLT 10 working days after MPC Final matrix due 10 working days after FPC.

OE Branch Chief, Tech Event Planner and Tech Team Branch Chief

12 5.7.5 Exercise Watch Bill Depicts personnel assigned to operate M&S and C4I systems during an event

Draft due NLT 10 working days before an event

OE Branch Chief, Tech Event Planner and Tech Team

13 5.7.6 Exercise Control Plan (ECP)

Defines how the exercise will be conducted

IAW JELC timeline Desk Officer, OE Branch Chief, Event Planner or

14 5.7.7 Training Annex Identifies training for the

JECG.

Draft due NLT 10 days after FPC, Final annex due 10 working days prior to Execution

OE Branch Chief, Desk Officer, Event Planner or

15 5.7.8 Mini-Exercise (MINIEX) Annex

Details how the ECG will participate in the preparatory event or rehearsal to ensure the ECG is ready for exercise execution.

Draft due NLT 10 days after FPC, Final annex due 10 working days prior to Execution.

OE Branch Chief, Event Planner or

16 5.7.8.1, MINIEX checklist Identifies tasks required to establish the control of response cells and its interaction with the training audience.

Draft due NLT 10 days after FPC, Final annex due 10 working days prior to Execution.

Desk Officer, Event Planner or Specified

17 5.7.9 Communication Exercise (COMMEX) Annex

Identifies communication and exchange of information prior to exercise execution.

Draft due NLT 10 days after FPC, Final annex due 10 working days prior to Execution. To be conducted in conjunction with the

"MINIEX".

Event Planner

18 5.7.9.1 COMMEX checklist A tool utilized by the ECG to identify the critical task details to be accomplished during an event.

Draft due NLT 10 days after FPC, Final annex due 10 working days prior to Execution.

Event Planner

19 5.7.10 Information Management (IM)/Knowledge Management (KM) Annex.

Details what information is exchanged within the

ECG

and between the ECG and the training audience.

Draft due NLT 10 days after FPC, Final annex due 10 working days prior to Execution days prior to the FPC Final plan 10 working days after FPC; update through exercise execution.

Desk Officer, Event Planner

20 5.3.8.7 5.7.14 5.7.15

Concept Briefing Addresses the actors using the DIME construct and describes activities using the Joint Functions and Domains (Command and Control (C2), Intelligence, Fires, Movement and Maneuver, Protection, Sustainment, Information, Cyber, Space, and the Electromagnetic Spectrum).

Draft due 5 days prior to IPC, updated throughout the JELC and the PoP.

OE Branch Chief, Desk Officer, Event Planner or

21 5.7.16 OE Synchronization Matrix

Addresses the activities of friendly, neutral, allied, partner, US Whole-Of- Government, and Adversary actions using the elements of national power, Joint Functions, and Joint Domains.

Draft due IAW prescribed

POA&M

OE Branch Chief

22 5.7.17 OE Event Matrix. Matrix used during planning and execution that outlines key events, effects, and actions that occur within the OE at a specific time. The event matrix enables the design and control of deliverables such as the RTC, scenario, and storylines.

Draft due IAW prescribed

POA&M

23 5.7.18 Orientation Brief Based off of the Exercise OE Concept Brief

Due 15 days prior to JECG training.

Lead planner and OE Branch

24 5.7.18, 5.7.20 Scenario Encompasses the overarching setting and series of events occurring within the OE and contains a coherent and engaging chronological “story” describing the changes occurring from the DIME and PMESII- PT perspectives.

Draft due 5 days prior to IPC, updated throughout the JELC and the PoP.

Lead planner

25 5.7.21 Road to Crisis

(RTC)

An overarching description of the history and in-exercise series of events that establish conditions for achieving the training audience commander’s objectives.

Draft due 5 days prior to IPC, updated throughout the JELC and the PoP.

Lead planner

26 5.7.22 In-Exercise Scenario Identifies the chronological description of the changes or series of events occurring during exercise execution that incorporates training audience and adversary, allied, partner, and neutral decisions, movements and outcomes

Draft due 5 days prior to IPC, updated throughout the JELC and the PoP.

Lead planner

27 5.7.22.1 RTC and Scenario Briefing

A narrative and slide show Exercise RTC and Scenario Briefing to inform exercise participants, training audiences, and the JECG of the RTC and in-exercise scenario.

Draft due 5 days prior to IPC, updated throughout the JELC and the PoP.

Lead planner

28 5.7.25 Force and Base Lay- Down

Outlines all friendly forces

Due 15 days prior to FPC OE Team, Desk Officer, Event Planner or

29 5.7.26 Access, Basing, and Overflight (ABO) Chart

Depiction of training audience access, basing, and overflight authorities as it relates to applicable countries and in synchronization with the exercise scenario.

Due 15 days prior to FPC. Event Planner

30 5.7.27 Adjudication Procedures

Process to determine the outcomes of kinetic and non- kinetic actions between BLUE and RED forces replicated in the exercise and for activities not reflected or poorly replicated within M&S, such as EMS and information.

Procedures will include outcomes critical to the success of the exercise, Defines activities that are prohibited during the exercise (e.g. Weapons of Mass Destruction (WMD), attacks on specific entities).

Due 15 days prior to FPC. OE Branch Chief, Event Planner or

31 5.7.28.1 Adversary Campaign Plan

Accurately reflects the adversary’s strategy, desired end state, and ways and means of achieving the end state, consistent with the training audience commander’s guidance and exercise construct.

Due 15 days prior to FPC. OE Branch Chief, Desk Officer, Event Planner or

32 5.7.28.3 OPFOR CONOPS a. Describes OPFOR weapons systems, Tactics Techniques and Procedures (TTP), movement, maneuver, Command and Control (C2) and sequence of operations and activities.

b. Identifies OPFOR Air, ground, maritime, space, cyber and EW/ Electro Magnetic Spectrum

(EMS) CONOPS

Due 15 days prior to FPC. OE Branch Chief, Desk Officer, Event Planner or

33 5.7.28.4 Adversary Campaign Overview Brief

Describes the adversary’s strategy, intentions, capabilities, limitations, and Tactics, Techniques, and Procedures (TTPs.)

Draft due 5 days prior to IPC, updated throughout the JELC and the PoP

OE Branch Chief, Desk Officer, Event Planner or

34 5.7.28, 5.7.28.10

Adversary Cyberspace and Influence Capability Analysis Playbooks

Adversary-based, and functionally framed playbook based on real world intelligence and will include the following: Adversary Strategic Objectives and themes; Cyberspace & Influence capabilities, intent and highlighted DIME activity

Initial due during 1st Quarter of start of PoP, then updated quarterly thereafter

IE/Cyber

35 5.7.28.9 Adversary IE Events

Dvelop and maintain visualization products that capture adversary activities, effects, and perceptions in the the information environment.

Draft due 5 days prior to IPC, updated throughout the JELC

IE/Cyber

36 5.7.28.12 OPFOR Reference Books and Catalogues

Contains contemporary Chinese, Russian, Iranian, and North Korean tactics, techniques, procedures, and doctrine to accurately employ air, maritime, ground, space, EW, EMS, and cyber military forces and capabilities at the operational and tactical levels. Contains TTPs and doctrine and is indexed with a searchable storage system.

At the start of the PoP an intial report will be provided and a quaterly update will be provided first month of each quarter s

EOD Branch Chief or

37 5.7.28.13 Friendly Forces Reference Books and Catalogues

Contain the contemporary US, allied, partner, and neutral TTPs and doctrine to accurately employ air, maritime, ground, space, EW, EMS, and cyber military forces and capabilities at the operational and tactical levels including weapons systems, capabilities and limitations.

Contains TTPs and doctrine and is indexed with a searchable storage system.

Initial due during 1st Quarter of start of PoP, then updated quarterly thereafter

EOD Branch Chief or

38 5.5.2.6, 5.7.29 Master Scenario Event List (MSEL)

Develop, plan, manage, operate and provide training in the selected MSEL Tool (e.g., Joint Training Tool (JTT), Joint Master Scenario Event List (JMSEL), North Atlantic Treaty Organization Joint Exercise Management (NATO-JEMM), or the Joint Training Tool

(JTT).

Initial draft due 5 days prior to IPC, updated throughout the JELC and the PoP

Desk Officer, Event Planner

39 5.7.32.3 Strategic Messaging Identifies messages, e.g., White House Statements, Department of State (DoS), Public Diplomacy, OSD PA guidance to CCMDs.

IAW event JELC Interagency

40 5.3.8.1, 5.7.29.1

CJCS Level Orders Evaluate and develop higher headquarters orders and directives (e.g., CJCS PLANORD, EXORD, SDOB

IAW event JELC Desk Officers, 41 5.7.29.7 Modify Rules of Engagement (ROE)

Identifies consonance with interagency activities for an event

IAW event JELC Interagency

42 5.7.31.2 Scenario Events

Shows the Sustainment Cell storylines and injects that the Sustainment Cell could use to develop the scenario.

Due NLT the end of MSEL I conference. Updated through the end of execution IAW exercise battle

Sustainment Cell Lead and/or EOD

43 5.7.31.5 Sustainment Database/STARTEX Data Requirements List

Identifies data requirements and assign responsibility and due dates for information and products.

Draft delivered NLT 15 calendar days prior to IPE Refined versions are completed within 3 working days after receiving comments.

Final delivered NLT 15 calendar days

Sustainment

44 5.7.31.6 Sustainment Annex for Exercise Order

Identifies all Sustainment Cell exercise requirements, such as references, STARTEX products, supplies, and relevant sustainment materials Per JP 5-0.

Prior to the Final Planning Event (FPE)

45 5.7.31.7 Sustainment Cell Movement and Logistics Plan

Identifies all Sustainment Cell requirements needed to support the exercise such as reference materials, STARTEX products, office supplies, etc. If required, prepare all items for shipment to the execution site.

Draft plan delivered NLT 15 calendar days prior to the FPE.

Final plan delivered NLT 15 calendar days after the FPE.

46 5.7.31.8 Sustainment Exercise Planners Seminar

Seminar targeted to CCMD sustainment planners

Twice annually Sustainment

47 5.7.32.1 Interagency inputs to scenario (activities or events)

Develop interagency inputs to scenario products portraying pre-crisis interagency activities or events

IAW JELC timeline IA Branch Chief and JS J7 Desk Officer and/or Event Planner

48 5.7.33 Missile Defense Master IAMD Training Plan

A schedule and plan of action that addresses specific training required to understand missile defense.

Quarterly Space and Missile Defense

49 5.7.33.1 Air Defense Annex Exercise Word document for scenarios and MSEL injects.

IAW JELC timeline Lead Missile Defense Planner for exercise and/or JS J7 Desk Officer and/or Event Planner

50 5.7.33.2 IAMD Operation Orders

Operation Orders includes the Area Air Defense Plan (AADP), Air Defense Designs, Special Instructions (SPINS), Airspace Control Plans (ACP), Joint Air Operations Plan (JAOP), Critical Asset List (CAL)/Defended Asset List (DAL) and STARTEX data for execution.

IAW JELC

timeline and Battle Rhythm for specific exercises

Space and Missile Defense Branch Chief and/or Lead Missile Defense Planner for exercise and/or JS J7 Desk Officer and/or Event Planner

51 5.7.33.9 BMD Analysis Input to BMD doctrine writer to ensure accuracy and real world application

IAW JELC and event schedule Doctrine Writer

52 5.7.33.10 Missile Defense Materiel Solutions

Addresses capability gaps from each CCMD and Service.

IAW JELC timeline Space and

53 5.7.33.11 IAMD Safety Risk Assessments

Assessment that ensures training is in place to prevent a simulated track being displayed on a live network.

Throughout training event Space and

54 5.7.33.12 Progress Results Identifies results of the creation of a US Space Command

IAW JELC and event schedule Lead Space operations Planner and Chief of Space and Missile Defense Branch

55 5.7.34.1 Space Operations Input

Review and provide input to the shot plans, Damage Control Cell (DCC) and Space architectures

IAW JELC timeline Space and Missile Defense Branch Chief and/or Lead Missile Defense Planner for exercise and/or JS J7 Desk Officer and/or Event Planner

56 5.7.35 EW/EMSO activities and effects

Coordinate and script products; script EW/JEMSO activities and effects, coordinating with other functional planners to ensure scenario consistency, and provide advice to Information Environment lead/exercise control on the strategic, operational and tactical level impacts of friendly, adversary and third-party EW/JEMSO in the Operational Environment

Throughout JELC Lead IE Planner and IE Branch

57 5.7.35.3 ELINT parametric data

Coordinate and script products; verify and update ELINT parametric data and characteristics of emitter EA Systems in model databases

Throughout JELC IE / Cyber Branch Chief and Technical Teams Branch

58 5.7.36.1 Information Environment (IE) Material

IE related material to include copies of real world web material, altered real world web material, fictitious, scripted web material, and fictitious video and audio products

Planning and production required throughout the JELC.

Production of the synthetic information environment required during execution

Chief, Synthetic Environment Development (SED)/Desk Officer

59 5.7.36.5 Replicated Media Tailored media to replicate the information and exercise operational environments

Developed throughout JELC and delivered during execution or IAW JELC timeline.

Chief, Synthetic Environment Development

60 5.7.36.7 Road to Crisis (RTC) Video

Broadcast news for exercise media environment planning during the Master Scenario Event List (MSEL) development conference or scenario development

Script due prior to the end of the ISC or IAW JELC timeline.

Chief, Synthetic Environment Development

61 5.7.36.8 News Report Provides a mixture of fact, speculation, and RED information operations. This product simulates a civilian news broadcast. The WNN News Report is used to support MSEL injects, focus a training audience on some situation, or contribute to the fog and friction of war.

Script due prior to the end of the ISC or IAW JELC timeline.

Chief, Synthetic Environment Development

62 5.7.36.9 Special Report Shorter version of the WNN News Report. The Special Report usually focuses on a specific MSEL or scenario event in order to highlight a time sensitive action required of the TA.

Up to 2 videos per day or based on exercise requirements

Chief, Synthetic Environment Development

63 5.7.36.10 Documentary Report Special report, focused on the exercise OE ground truth and exercise construct with no media-bias.

IAW JELC schedule Chief, Synthetic Environment Development

64 5.7.36.11 Media and Video Support Plan

Based on exercise and training objectives developed for exercise execution in coordination with Desk Officers and Event Planners.

Due by the end of the FPC Chief, Synthetic Environment Development

65 5.7.36.14 Video Library A collection of all media organized systematically

Updated as new media is produced

Chief, Synthetic Environment Development

66 5.7.37.1 Intel POA&M Track all tasks assigned to Intelligence including planning, intel product development, Intel models & simulation requirements, points of contact, and mandatory report submission status.

Initiation at start of Concept Development Event (CDE).

Document updated and maintained throughout the

JELC.

Intel Branch Chief, Lead Cyber Planner and IE / Cyber branch

67 5.7.37.2 Intel Manning Roster

A roster of Intelligence joint exercise control group personnel, contact information, functional area assignment, and unfilled requirements.

Initiation at Initial Planning Event (IPE). Updated and maintained throughout the JELC.

Intel Branch

68 5.7.37.3 Consolidated Intelligence Support Request (CISR)

Intel requirements Initiation at Initial Planning Event (IPE). The final document provided to JS J27 no later than the start of the end of the Intelligence Scripting

69 5.7.37.4 Intel Scripting Working Group

(ISWG)

Documentation

Identifies the agenda, schedule of briefings, facilitation of external JS J7 organizations and outcomes

IAW JELC schedule Intel Branch

70 5.7.37.6 5.7.37.10

Target packages Depicts targeting information

Planning initiated at conclusion of the Initial Planning Event (IPE). ISWG executed IAW JELC

71 5.7.37.8 Intel Collection Plan Research and update calls related to Intelligence, Surveillance, and Reconnaissance (ISR) and Collection Management (CM) and represent ISR/CM equities in all JELC events and forums. The Contractor replicates national-level CM functions and facilitates any CM related aspect of exercise design and execution that will enable a realistic CM experience for the training audience

IAW JELC schedule Intel Branch

72 5.7.38.1 PAI / OIE plan

Support development SOPs, event guidance/ business rules, training, and distribution of PAI (Red, Blue, Green across DIME), coordinating with other functional planners to ensure scenario consistency, and provide advice to IE lead

IAW JELC schedule IE / Cyber

73 5.8.1.2 NOSC Watch Bill Identifies personnel scheduled for all NOSC positions.

First day of each m onth and as updates occur

Tech Event Planner and Tech Team

74 5.8.1.3 Security Incident Report

Documentation on each cybersecurity incident identifying when, how, and who was involved with the incident

Immediately notifcation or 2 hours within incident

EOD Cyber Team

75 5.8.1.4 JTEN Network Outage Report

Report detailing the J7 network performance and impacts of scheduled and unplanned network outages and Authorized Service Interruptions (ASI).

Required within 1 hour of when incident exceeds 30 minutes of outage

Engineering Chief Tech Event Planner and Tech

76 5.8.1.5 Usage and Availability Statistics

JTEN status, usage, and availability

First working day of each month

Tech Teams

77 5.8.1.6 JTEN Master Operations Schedule

Identifies JTEN operations schedule based on Event Technical Support Requests (ETSRs) and Technical Resource Requests (TRRs) approved by EOD

First working day of each month

Tech Event Planner and

78 5.8.1.7 Level I and II Help Desk Support

Provide continuous help desk support across the various Joint Staff systems and applications including but not limited to JKO, JTP, JTT, JLLIS and troubleshoot user account issues, application errors and access problems

Daily Tech Teams

79 5.8.1.10 Trouble Ticket System

Captures input, and reports all trouble tickets to include, initial action, completion and trends

Weekly Tech Teams

80 5.8.11 Event Weekly Status

Identifies weekly status report of upcoming events requiring cybersecurity and/or planner input. See 5.8.11 for specified examples.

Weekly Tech Teams

81 5.8.12 JTEN NOSC Pass-down Report

NOSC activities and status of upcoming events.

For example:

End of Life Software Analysis Reporting, CVMT POA&M

Analysis, Vulnerability Monitoring and Reporting, FMC IPDS Event Monitoring

Daily IAW NOSC meeting schedule

82 5.8.20 M&S, C4I, Intel Operators, Integrators, and Analysts Manning and Support Plan

Outlines the operator manning and training requirements for the M&S, C4I, Intel Operators, Integrators, and Analysts manning and training requirements

Initial draft due 10 days after the IPC, updated throughout

Desk Officer, Event Planner

83 5.8.3 COP Management and C2 Architecture

Lead the design, development, and implementation of complex Joint and Coalition COPs, oversee the management and maintenance of COP systems and architectures, and ensure COP data accuracy, integrity, and accessibility.

Throughout the JELC schedule Tech Teams Branch Planner

84 5.8.4 Joint Interface Control Officer Duties and Responsibilities

Lead the design, implementation, and maintenance of joint data networks, resolving interface issues, monitoring and managing Tactical Data Link networks.

Throughout the JELC schedule Tech Teams

85 5.8.8 Operational Task Order Common Operational Picture (OPTASKCOP) and Operational Task Order Tactical Link

(OPTASKLINK)

Reports

Details events that JS designates as primary simulation to stimulation inject point and documents how C2 systems will interoperate

Draft due14 calendar days after MPC. Final due 14 calendar days after FPC.

86 5.8.10,5.8.21

M&S, C4I, and Intel Operator Manning and Support Plan

Outlines the M&S operator manning and training requirements for the M&S and C4I systems

Initial draft due 10 days after the IPC, updated throughout the JELC and the PoP

Desk Officer, Event Planner

87 5.8.26 I/C Manning and Support Plan

Outlines the I/C manning and training requirements including OPFOR, US (training audience), allied, partner, and SITFOR for each exercise or event.

Initial draft due 10 days after the IPC, updated throughout the JELC and the PoP

Desk Officer, Event Planner

88 5.8.27 Training Audience Order of Battle

(OOB)

Excel format depicting the friendly forces Order of Battle (OOB) to be included in the M&S systems and Joint Training Data Services

(JTDS).

NLT 14 days before EFT/EOT or as OOB data becomes available.

OE Branch Chief and Technical

89 5.8.28 M&S, C4I, Intel and I/C Scheduling Documents

Projects all requirements for the next 12-months

Monthly EOD Branch Chief and/or Technical

90 5.8.28.2 M&S User’s Course Program of Instruction (POI)

Identifies learning objectives, curriculum, resources, facilities, simulations, automation, classrooms and other resources needed to complete the course.

NLT 30 days prior to class execution for approval

EOD Branch Chief and/or Technical

91 5.8.29 M&S User’s Course Memorandum of Instruction (MOI)

Describes the M&S class, time and location of execution, schedule, instructor requirements, and attendee requirements for students attending the M&S operator class.

NLT 30 days prior to class execution for approval

EOD Branch Chief and/or Technical

92 5.5.2.6, 5.8.31 Order of Battle

(OOB)

The organization, disposition and parametric data of the forces, equipment, weapons, munitions, and systems are input in the M&S system and JTDS

NLT 14 days before EFT/EOT or as OOB data becomes available.

EOD Branch Chief and/or Technical

93 5.8.31.2 OOB Change Log A continuously updated log of order of battle database items changed

Due after each testing event and after execution.

EOD Branch Chief and/or Technical

94 5.9.1 Operational Environment Synchronization Matrix

Illustrates the friendly, neutral, allied, partner, US Whole-Of- Government, and Adversary actions, MSEL events and changes to the OE during execution based on the In- Exercise scenario.

Update during exercise execution

Desk Officer, Event Planner and EOD

95 5.9.5.1 Facilitated After Action Review

(FAAR)

Seminar between the training audience commander and their key staff.

IAW JELC DTD Team and IAW schedule

96 5.11.2.11, 5.11.3.18

After Action Reviews (AAR)

Identifies exercise and event observations, training audience responses, and lessons learned

Due NLT 30 calendar days post FAAR

Chief A/T

97 5.11.2.13, 5.11.3.18.3

Post Exercise Report A summary of the exercise to include exercise objectives, the scenario, and a description of the training audience, document Joint Force Development initiatives, report shall be in sufficient detail to inform process improvement initiatives.

Due NLT 45 calendar days post FAAR

Chief A/T

98 5.11.1 - 5.11.5, 5.11.6.2, 5.11.8.1

DTD, DTT & SLE

Training, academic, reference materials, guides, periodicals, articles, coordination and planning documents.

Identifies attendance rosters, graphic materials, seating charts, small group breakout assignments, room reservations and preparation, audiovisual support, security, and facility arrangements.

Each SLE event DTD, DTT and SLE Division

POC

99 5.11.4.11 Academic Seminar Summaries and Recordings

Historical academic information

Each academic event SLE Support

100 5.11.4.13 Post Event Products Mailed training materials to NDU or the participant

Each academic event SLE Support

101 5.11.6.3, 5.11.9.1, 5.11.10.3, 5.11.10.4, 5.11.10.5

Lessons Learned Tailored Reports and Documentation

The analysis, assessment, collection, documentation production

Once per collection event (~6/year) plus biannual assessment summary (2/year)

JLLD POC

102 5.11.6.1, 5.11.9.2

Lessons Learned and Assessment Resolution and Documentation Dissemination

Products to support the execution of resolution actions

On-going dissemination and tracking plus quarterly summary report (4/year)

JLLD POC

103 5.11.10.4 JLLIS

Documentation

Documents relative to JLLIS function and operation

1. Annually

2. Monthly

3. Once per major/minor version release (~4/year)

4. Up to 24 times per year, including on-site travel (~6 per year)

JLLD POC

104 5.12.2 SCIF Access Roster Identifies personnel with permanent TB1 and TB14 and other SCIFs with access.

Monthly Intel Branch

105 5.12.3 SCIF Audit Log Documents unauthorized personnel in the SCIF

Review weekly Intel Branch

106 5.12.4 SCIF Opening and Closing Letter

Lists personnel approved for opening and closing TB1 and TB14 SCIFs;

and other SCIFs

Within 10 days of new personnel arrival; Quarterly Refresher training

107 5.12.6 SCIF Inspection Book

IAW applicable directives, manuals and regulations

Report deficiencies NLT 3 hours after weekly inspections

108 5.12.8 SCIF Inspection Deficiency Report

Documentation of inspection findings and deficiencies

Deficiencies reported within one day of inspection

Intel Branch Chief and Joint Staff SSO

109 5.12.10 Training Roster A roster of all personnel who have received training and their training date.

Updated after completion of training

110 5.12.11 Security Incident

Provide documentation on each cybersecurity incident identifying when, how, and who was involved with the incident

Within 2 hours after each incident

Cybersecurity Branch Lead

111 5.12.12 SCIF Combination Control Document

Record SCIF combination changes based upon DIA SCIF policy regulation.

IAW SCIF policy regulation Intel Branch

112 5.12.15 COMSEC Annual Inspection Checklist

Inspection findings Annual Intel Branch

113 5.12.16 COMSEC Training Documentation

Notes the completion of training.

Immediately upon addition of new team members; Refresher

114 5.12.17 COMSEC

Emergency Action Plan

Documents COMSEC emergency action plans IAW COMSEC security directives.

Review and update annually or when changes to situation necessitate.

115 5.12.18 COMSEC Access Roster

Identifies personnel with access to COMSEC restricted space and safe.

Review annually; Update immediately when changes to roster occur.

116 5.12.19 Defense Reutilization Management Office (DRMO) Inspection Report

Identifies the inspection of all SCIF equipment prior to leaving the SCIF for disposal.

Prior to movement of equipment from the SCIF with zero deficiencies.

117 5.13.1 Staffing Plan and Operating Strategy

Ramp up and ramp down, surge labor plan and labor plan

Due within 15 working days of notice

Task Order TA, or

118 5.13.2, 5.11.8.2 Portal and Shared Drives

IM/KM portal pages to permit information sharing

Daily throughout all DDJT divisions

Each DDJT Division Chief

119 5.13.2.1/2/3/4/5 5.3.8.6

Portal, Collaboration Platforms, and Shared Drives

IM/KM /Records management support and optimization to include training, metrics and visual structure representations

Continuous Ops Branch Chief, Plans & Ops Division

120 5.13.3.1.1 Post Award Kick-off Meeting Brief

Identifies contract team, reviews quality control plan, risks, issues, high level tasks, resources, costs and schedules and services throughout PoP to eliminate misunderstandings and program risk.

Identifies agenda, major issues decisions, action items, due dates, POA&M schedules

Task Order COR, and TA

121 5.13.4, 5.11.4.3, 5.11.5.2

Standard Operating Procedures (SOP).

Identifies routine, repetitive processes within DDJT resulting in clearly identifiable, efficient work processes.

Newly developed SOPs will be completed within 3 calendar months after award of the PoP start date. Existing SOPs will be updated within 3 calendar months after award of the PoP start date. All SOPs will be revised monthly when processes change.

Each DDJT

122 5.13.6, 5.13.6.1 5.13.6.2, 5.3.8.3, 5.3.8.5

Joint Staff Taskings/Tasker Log; Repository.

Training

Responses pertaining DDJT operations.

Download and post Tasker Log and maintain Tasker repository.

Deliver ETMS2/Action Officer Training.

Within timeline of each tasker.

Tasker Log – Weekly; ETMS2 Training - Quarterly

Operations Branch Chief, Plans & Ops Division

123 5.13.7 Joint Training Assessment

Summary Report of customer feedback.

Quarterly and annually Each DDJT

124 5.13.8 DDJTE Long Range Calendar

12-month long range calendar

Weekly Deputy, Plans & Ops Division

125 5.13.10.1, 5.13.10.4

Event Space Scheduling

24-month schedule of all managed spaces by day and by hour; 18-month space utilization and de-confliction spreadsheet;

space utilization log of all managed spaces (Microsoft Excel and Word)

Respond within 48 hours of request to complete the scheduling and space coordination within 72 hours of request. Updated weekly and maintained real time daily on the portal

Operations Branch Chief, 126 5.13.11, 5.11.10.2

Joint Training Handbook and Academic Instruction

Reflect current processes and procedures for exercise design and execution

Annually Deputy, Plans

127 5.13.12 Out-of-Cycle (OoCR) Summary

Out –of Cycle Summary Slide with notes for Weekly Update

Weekly Deputy, Plans

128 5.13.13 Phased Transition Plan

Phase-in and phase-out of services

Within 2 working days after task order award; within 60 calendar days prior to the end of the PoP.

COR and TA

129 5.13.14.1 Quality Control Plan Procedures to identify, prevent, and ensure non-recurrence of defective services

Within 30 calendar days at the beginning of the PoP

COR and TA

130 5.14.1.1 Monthly Financial

Identifies hours, funding, product deliverables, expenditures by tasks, personnel changes, issue identification and contractor personnel roster.

Within 15 calendar days of each month

Task Order COR, Technical Assistant (TA)

131 5.14.2 Monthly Status Report (MSR).

Identifies the progress and status of accomplishments

Within 15 calendar days of each month

Task Order COR, Technical Assistant (TA)

132 5.15.1 Weekly Activity Report (WAR) Submission

Coordinate with all Divisions to gather and consolidate input and ensure adherence to required WAR format and guidelines.

Weekly Policy & Programs Branch Chief, 133 5.15.2 Conference checklists standardized checklist with administrative guidance for individual working group leads

6 months prior to conference start date

Policy & Programs Branch Chief, 134 5.15.2 Visitor Information Booklet

Consolidated conference schedule and administrative instructions for attendees in PDF format

Draft booklet due NLT 45 days prior to conference start, final version NLT 30 days prior to conference start

Policy & Programs Branch Chief, 135 5.15.2 Conference website or web portal

Updated unclassified and classified CAC-enabled web pages able to function as a repository for conference messages, agendas, and working group slides, at no cost to the U.S. government, using existing Intelink or similar capability

Initial sites developed NLT 45 days prior to conference start, populated with conference products NLT 15 days prior to conference start

Policy & Programs Branch Chief, 136 5.15.2 Working Group minutes and due-outs coordinate with all Working Group leads for a summary of discussion topics and agreed upon due-outs for each WG, in electronic format and posted to the conference web page

NLT 15 days after the final day of the conference

Policy & Programs Branch Chief, 138 5.9.6.7 NKE Status Report NSEs)

JLVC NKE capability provided during the foundation for integrating new all-domain expert models plus exercise control management of NKEs

Monthly JLVC - MOD

139 5.9.6.9 Weekly Status

Reports shall contain the development and modernization efforts that align to the Joint Training Synthetic Environment (JTSE)

First Tuesday of every week JLVC - MOD Team, TA, and

COR

140 5.9.6.10 After Action Reports Provide training capability reports focused on interoperability standards and architectures. Document Service and Combat Support Agency LVC capabilities IAW JVLC program partners technical requirements.

Provided two business days after the conclusion of EC/JLVC events

JLVC - MOD

141 5.9.6.4 Power BI Reports In an effort to facilitate better data analysis, visualization, and sharing, use of Power BI ultimately leading to more informed decision-making. Power BI provides a platform for integrating JLVC-MOD data.

As requested by government program leads

JLVC - MOD

142 5.9.6.9 JLVC MOD

Exercise Reports

Integrate and document global all-domain exercises across the spectrum of conflicts through scalable, complex, and robust

Daily IAW JLVC defined battle rhythm schedule (i.e., emails, teams, and telcons)

JLVC - MOD

training scenarios supporting EC and

LSGE.

143 5.9.6.10 AI Integration Report

Continuously monitor joint training exercise and events trends, to integrate emerging AI technologies, and best practices into joint training events, exercise and support activities and develop and submit a report that outlines potential JT activities that can leverage AI and provide.

60 days from the start of the PoP, Quartey reports that would advance the use of AI .

JLVC - MOD

Team, TA, and

COR

TA, COR and

DDJTE

Division Chiefs

File details come from the government source that posted it. Updated .