JTLS-GO PWS for RFI.pdf

PDF 272 KB Posted Apr 4, 2025

Attached to: Joint Theater Level Simulation-Global Operations Support Federal contract opportunity
Solicitation number: N0018925RZ042
Issued by: Department of the Navy Naval Supply Systems Command

About this file

Written by GovTribe AI · Apr 4, 2025

This Performance Work Statement (PWS) details requirements for Joint Staff J-7 support services for the Joint Theater Level Simulation - Global Operations (JTLS-GO) software. The objective is to provide warfighters with joint simulations and tools that enhance joint training across military services, combatant commands, agencies, and coalition partners. Key technical requirements include conducting research, development, operations, sustainment, and maintenance of the JTLS-GO software, with a focus on improving cybersecurity, adapting to shifting training priorities, and ensuring C4I interoperability.

The contract will primarily be performed at VALKYRIE Enterprises in California and the JS J-7 facility in Suffolk, Virginia, with potential work at other government sites. The base period runs from September 1, 2025 to August 31, 2026, with two optional additional one-year periods. Contractor personnel will require security clearances ranging from Unclassified to Top Secret, with approximately 10% unclassified work, 70% requiring Secret clearance, and 20% requiring TS/SCI clearances. The PWS emphasizes developing advanced capabilities like machine learning/AI for wargaming, automated operational order generation, and extended simulation scenarios.

View the file

Other files for this federal contract opportunity

Other files attached to Joint Theater Level Simulation-Global Operations Support, newest first.
File	Type	Posted
JTLS-GO RFI.pdf	PDF	Apr 4, 2025

On GovTribe

Work with this file on GovTribe

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

PERFORMANCE WORK STATEMENT

FOR

Joint Staff J-7 JTLS-GO Support Services

This is a DRAFT version of the PWS and may be significantly revised prior to issuance of a solicitation.

C.1 INTRODUCTION

The objective of this Performance Work Statement (PWS) is to support the Joint Staff J-7

(JS J-7), Deputy Director for Joint Training (DD JT) in providing warfighters with joint simulations and tools that enhance and enable Joint training across Services, Combatant

Commands (CCMDs), Agencies and Coalition partners. The joint simulations and tools provided by DD JT are critical enablers that support the delivery of trained, capable, and interoperable Joint Forces.

C.2 BACKGROUND

The purpose of this PWS is to conduct research development, operations, sustainment, and maintenance for the Joint Theater Level Simulation – Global Operations (JTLS-GO) software in support of JS J-7/DD JT, Joint Live Virtual Constructive Modernization (JLVC MOD) and Joint

Training, Exercise, and Evaluation Program’s (JTEEP) joint training mission areas.

C2.2 Intellectual Property Rights Background

The basic Joint Theater Level Simulation (JTLS) product (circa 1984) was a Department of

Defense product. Since that time, it has been developed and has been continually improved with mixed, US Government and ROLANDS & ASSOCIATES (R&A) funding. . R&A funding was either direct or through its developments with independent customers. In 2016, JTLS was renamed JTLS—Global Operations (JTLS-GO) after moving away from legacy hex-based terrain to a new unique variable grid-based format using Standard Database

(SDB) terrain format with the ability to model the entire globe. R&A has since been acquired by Valkyrie, and Valkyrie maintains all ownership rights in JTLS-GO and all its associated documentation and technical data sufficient and necessary to commercialize the JTLS-GO product by providing the software and related operations and maintenance services to commercial, U.S. government, and non-U.S. government (subject to any applicable export control regulations) customers.

The US Government generally has had at a minimum, “Government Purpose Rights” in

JTLS-GO as described at DFARS 252.227-7013 RIGHTS IN TECHNICAL DATA—Other

Than Commercial Products and Commercial Services (JAN 2025) and DFARS 252.227-

7014 RIGHTS IN Other Than Commercial Computer Software and Other Than Commercial

Computer Software Documentation (Jan 2025). The provisions set forth that a Government

Purpose Rights license applies for a 5-year period after which the Government obtains

“Unlimited Rights the US Government maintains the following license rights under versions of JTLS/JTLS-GO (as such license rights are defined in the foregoing provisions) released prior to the effective date of this contract:

Current JTLS/JTLS-GO

Versions

Government License Rights

JTLS/JTLS-GO Versions 1.0 –

5.0.8.0

Unlimited Rights

JTLS-GO Versions 5.0.9.0 -

6.0.4.0

Government Purpose Rights *

JTLS-GO Versions 6.0.4.1 –

6.1.7.0

Government Purpose Rights*

JTLS-GO Versions 6.1.7.1 –

6.3.4

Government Purpose Rights

*The government's current Government Purpose Rights for these software versions, originally granted under Contract No. N0018917DZ058 (dated September 30, 2017), are now governed by Contract No. N0018922CZ025, effective through September 29, 2025. A new contract, anticipated to be awarded around August 1, 2025, will extend these rights until

September 1, 2028. Upon expiration of this new contract, the government will acquire

Unlimited Rights to these versions.

C2.2.1 New Intellectual Property Rights Under This Contract: Notwithstanding anything to the contrary herein, the US Government shall have license rights in all JTLS-GO technical data and software delivered on or after the effective date of this contract as set forth in this section below.

With regards to technical data, the US Government possesses such rights as follows:

With regards to Software, the US Government possesses such rights as follows:

Technical Data to be furnished with

Restrictions

Basis for

Assertion

Asserted Rights

Category

Name of Person

Asserting

Restriction

JTLS-GO Developed partially at private expense

Government

Purpose Rights

VALKYRIE

C.3 SCOPE

The contractor will conduct Operations & Maintenance (O&M) and Research, Development, Test and Evaluation (RDT&E) non-personal support services in the performance of this PWS. To the maximum extent possible the Government will define what needs to be accomplished initially via this contract (i.e. the desired end state and deliverables; quantity, quality, and schedules) and then as requirements and funding are available. The contractor will be responsible for determining how the tasks are to be accomplished and execution of tasks within the limitations of available resources and

Government guidelines. The contractor’s efforts are expected to be managed and limited to those necessary to accomplish the task order deliverables necessary to conduct an event, develop a product, or enable the JS J-7 to complete a mission objective.

C.4 APPLICABLE DOCUMENTS.

C4.1 CJCS 3500 (series), "Joint Training Policy and Guidance for the Armed Forces of the

United States”

C4.2 DoDI 8320.02 (series), "Sharing Data, Information and IT Services in DoD."

C4.3 DISA Application Development Security Technical Implementation Guide.

C4.4 National Institute of Standards and Technology, Special Publication N0. 800-53

C4.5 Intelligence Community Directive (ICD) No. 503, Intelligence Community Information

Technology Systems Security Risk Management, Certification and Accreditation

C4.6 DoD Manual 5200.01, DoD Information Security Program, Vol. 3 Alternative

Compensatory Control Measures (ACCMs)

C4.7 DoDI 5015.02, DoD Records Management Program, 2017 44 U.S.C. Chapters 21, 29, 31 and 33

C4.8 Freedom of Information Act (5 U.S.C. 552)

C4.9 Privacy Act (5 U.S.C. 552a)

C4.10 DoDM 8140.01, Cybersecurity Workforce Management

C4.11 DoDM 8140.02, Identification, Tracking, and Reporting of Cyberspace Workforce

Requirements

C4.12 DoDM 8140.03, Cybersecurity Workforce Qualifications

C4.13 DoDI 8500.01, DoD Cybersecurity Program

C4.14 DoDI 8510.01 Rick Management Framework

C4.15 DoDD 8570.01 Informational Assurance Workforce Improvement Program

C4.16 NIST 800-53, Rev. 5 Security and Privacy Controls for Information Systems

C4.17 DoD Zero Trust Strategy, Oct 21, 2022

C4.18 White House Memo M-22-09, Federal Zero Trust Strategy

C4.19 DoD Software Acquisition Pathway Subpart 227.72

C.5 REQUIRMENTS

The Contractor shall provide the technical expertise to meet the program mission of providing an operational level, interactive, web-enabled simulation that models multi-sided air, ground, and naval civil-military operations with logistical, Special Operation Force (SOF), and intelligence support. JTLS-GO operates on DoD networks and shares information with other DoD Automated

Information Systems (AIS) but is an independent software program that is designed solely to support the

Joint Staff J-7 and the DOD Joint Training Enterprise. The contractor will receive requirements from the government and provide their own recommendations for enhancements to improve operation and sustainability. The contractor shall provide subject matter expertise to assist the government in prioritizing requirements, the allocation of resources and to choose between suggested courses of action.

The contractor shall manage the technical environment performing all required Security Technical

Implementation Guides (STIGS), tests and analysis and operate the JTLS-GO software on the DoD

Joint Training & Experimentation Network (JTEN) Non-classified Internet Protocol Router & Secret

Internet Protocol Route (NIPR and SIPR) without interruption immediately upon award of the contract without interruptions to the quality of service. JTLS-GO requirements shall be reviewed, validated, prioritized, and documented by the appropriate Joint Staff requirements management entity and/or

Configuration Control Boards before the Contractor begins work to ensure compliance with all guidance, policies, procedures, and directives. JTLS-GO is technical system with a joint training customer base used in various exercise and events. The contractor shall operate the JTLS-GO technical environments immediately upon award without interruptions to the quality of service.

C.5.1 Monthly Status Report. Prepare and provide the Contracting Officer (COR) and

Technical Assistant (TA) with an electronic Monthly Status Report (MSR) detailing all work accomplished under each task, planned activities and funding status. The MSR will include the following (A001):

C.5.1.1 Summary of progress made, specific accomplishments, impediments, schedule status, meetings attended, deliverables, next reporting period planned activities, and excesses, issues, recommendations, and any anticipated changes in schedule resultant either from accelerations or delays in the work. Any risk or problem areas will be reported with recommendations for remedy.

C.5.1.2 Summary of actual and projected scheduled and executed costs for labor hours and travel for the entire period of performance. Projecting a minimum of 6 calendar months into the future. Summarize labor hours and travel fund expenditures by resource band, to include total billed hours, burdened cost, travel, planned activities, any key personnel changes, and any shortfalls, issues, or problems.

C.5.1.3 The MSR will also identify any material Other Direct Costs (ODC) items purchased.

C.5.2 Software Updates. The contractor will implement and distribute software updates and associated documentation to JTLS-GO. Software updates or changes will include a Version Description Document (VDD). The VDD will contain at a minimum:

scope, list of documentation, new or updated software components, interface compatibility with new or existing capabilities, database changes, installation instructions, list of Engineering Change Proposals (ECP) software change proposals

(SCP), list of software trouble reports (STR) and list of acronyms (A002).

C.5.3 Software Tracking. The contractor will document and track ECP, SCP, and

STR. The contractor will ensure this list can easily be electronically imported into a

DD JT approved centralized database (A003).

C.5.4 Software Delivery. The contractor will deliver all software (including source code) and documentation to the government following final contractor software testing for government evaluation (A003).

C.5.5 Design Documentation. The contractor shall provide design documentation for each major software change in JTLS-GO. The design document will show how the software system will be structured to satisfy the requirements. The design document contains two stages. The first is a preliminary design in which the overall system architecture and data architecture is defined. In the second stage, i.e. the detailed design stage, more detailed data structures are defined, and algorithms are developed for the defined architecture. Design plans will contain a summary of changes (if applicable), design summary and design details translated into a representation of software components, interfaces, and data necessary for the implementation phase. A functional test plan will be included. They must be approved by government program/project lead prior to commencing work (A004).

C.5.6 Minutes & Reports. The contractor will participate in modeling and simulation design conferences, working groups and conferences. The contractor will be required to provide minutes or reports. These will include technical and analytical information on the subject matter discussed, to include recommendations or courses of actions (COA), if applicable. All documents generated will be fully footnoted to show the origin of the information and include a bibliography. All reports and backup research will be delivered electronically via email to the Government TA. On receipt of comments, the Contractor will provide a revised report within 5 business days (A005).

C.5.7 Program Support. The contractor will provide programmatic support related to specific assigned technical efforts, including the development of Program Plans, Plans of

Action and Milestones (POA&M), work breakdown structures, staffing plans, financial documentation, Quality Assurance Plans and Procedures, Configuration Management

Plans, point papers, status reports, Situation Reports, Operations and User Manuals, technical drawings/diagrams, training materials and other written or electronic documentation that describe planned, current or future operations or tasks related to JTLS-

GO required to support the JS J-7 Joint training mission requirements and objectives.

Contractor will provide products within 15 working days after government request.

Contractor will be given 10 days after government review to correct.

C.5.8 Test Plans. The contractor will develop test plans where system or software testing is required in support of the core requirements. The Contractor will develop and submit draft test plans 10 business days prior to each testing event (A006).

C.5.9 Test Reports. The contractor shall develop test reports after system or software testing has been executed. A test report documenting all test results will be submitted within 7 business days after each test event (A007).

C.5.10 Demonstrations, Event Support, Testing and Training. The contractor will support software setup, installation, updates, cybersecurity scans, for government approved demonstrations, event database build, event support, testing and training. This includes new equipment training (NET) for the software being developed IAW this PWS as approved by the government (A008).

C.5.11 Cybersecurity. The Contractor shall provide comprehensive cybersecurity support to the JS J-7 Information Systems Security Manager (ISSM), encompassing both technical and non-technical functions as defined in Department of Defense Instruction (DoDI) 8510.01 and other applicable DoD publications (A009)

C.5.11.1 Contractor will provide all Software Assurance (SwA) prerequisites for validation to the Cybersecurity Assessor and adhere to prescribed software testing methodologies prior to generation of SwA approval and subsequent acceptance as a part of the JS J-7 Evaluated/Approved Products List (E/APL) for the JTE.

C.5.11.2 Contractors with privileged JS Information Systems (IS) accounts are considered part of the JS Information Assurance Workforce (IAWF) and must be certified and qualified either at IAT-I, II, or III in accordance with DoD 8570.01-M. Privileged users shall be certified in a minimum baseline IA certification (e.g., Security+) and certified in their respective primary Operating System (e.g., UNIX) environment. In addition, training and user agreements must be completed and on file with JS J-7 Cybersecurity before privileged access is granted (A010).

C.5.12 The Contractor shall provide comprehensive cybersecurity support to the JS J-7

Information Systems Security Manager (ISSM), encompassing both technical and non-technical functions as defined in Department of Defense Instruction (DoDI) 8510.01 and other applicable DoD publications. This support includes Developing the JTLS-GO system in full compliance with DoDI 8510.01 (Risk Management Framework), achieving and maintaining necessary authorizations (IATO, ATT, ATO) for operation on designated unclassified and classified DoD networks. Ensuring JTLS-GO, designed as a Platform as a

Service (PaaS), supports the secure operation of current and future Joint Live, Virtual, and

Constructive (JLVC) versions, including exercise and development environments.

Delivering comprehensive security documentation, including but not limited to Fortify code scans, STIG scans, Network Risk Vulnerability scan results, waiver requests, and Enterprise

Mission Assurance Support Service (eMASS) documents. Providing timely notification to the ISSM (or designated representative) of any incomplete cybersecurity tasks no less than three business days prior to the suspense date. Utilizing designated web-based portals to track and report the status of all assigned cybersecurity tasks. The Contractor shall maintain a proactive and collaborative approach to cybersecurity, working closely with the ISSM to ensure the secure development, deployment, and operation of the JTLS-GO system in support of JS J-7 mission requirements.

C.5.12 Negligent Discharge of Classified Information (NDCI). Contractor will ensure that only information with sufficient security controls to appropriately protect it is placed on or processed on an information system (e.g., classified data on a classified system). Negligent discharge of classified information or NDCI will be classified as a security violation.

Contractor causing NDCI(s) during their duties under this PWS may be held financially liable for all actual accumulated restoration costs incurred, as described below, but not less than $5,000 per incident. Restoration costs above $5,000 will be itemized. Defense

Information Systems Agency (DISA) has developed a Classified Message Incident

Standard Operating Procedures (SOP) that will be followed in the event of an NDCI.

Personally Identifiable Information (PII) incidents fall under this category. This is not an exclusive remedy (e.g., in the case of PII spillage, identity theft or other insurance may be needed to protect the individuals). NDCI Cleanup actions may include the following actions on multiple IS systems in multiple locations: server destruction, hardware drive wipe and destruction, and containment actions. (A011)

C.5.13 Program Management Reviews. Be prepared to participate in a monthly Program Management

Review, in the form of In-Process Reviews (IPRs). There shall be a minimum of six (6) IPRs during contract execution. Each IPR shall be a maximum of one day in duration, and held at the Customer’s facility, telephonically, collaborative website (Teams), or an alternate site mutually agreed upon by the

Contractor and the Government. IPRs shall provide attendees with information regarding the status and planned activities of the program. All IPRs shall be documented and will include the following topics as a minimum Contractor will ensure that only information with sufficient security controls to appropriately protect it is placed on or processed on an information system (e.g., classified data on a classified system). (A012)

C.5.13.1 Previous Action Items Review of the Government and Contractor action items from the previous conference, using an action item list.

C.5.13.2 Problem Areas that have been problematic or areas requiring Government decision and resolution.

C.5.13.3 Program risks associate with cost, schedule and/or performance and proposed risk mitigation strategy.

C.5.13.4 Side meetings for IPT team members to review areas of the program as required.

C.5.13.5 New Action Items Preparation and finalization of new action items as a result of conference discussions.

C.5.14 Government Furnished Equipment (GFE) Report. The contractor will provide an annual Property

Accountability Report for all GFE. Annual report will contain at a minimum: contract number, location, bar code (if applicable), description, manufacturer, model, and serial number (A013).

C.5.15 Invoicing. Contractor will provide the COR all invoices for approval prior to submission (A014).

C.5.16 Transition Plan. This contract will have a transition period lasting no less than five

(5) business days. This transition will include a phase-in period for the new contract, and a ramp-down or phase-out of the contract. The existing contractors will be provided with written directions to start the transition of in-process efforts to the follow-on team. This will represent a challenge to both teams, to conduct the transition with the minimum duplication of effort. During the phase-in and the phase-out of the existing contract, both will operate in accordance with the transition plan generated by the existing contractors and approved by the Government. The transition from the existing contractors to the follow-on contractor will be performed without a delay in the execution of the planned tasks. The Plan consists of two parts: Phase-In and Phase-Out (A015).

C.5.16.1 The Phase-In will address the ramp-up in numbers of people and the transition of the work. The Phase-In requires the contractor to work with the existing contractors in the transition of work being performed. The plan will address the ramp up of the contract and the process to ensure that the risks associated with the transition plan are mitigated. The level of detail for the plan must be sufficient for each party to understand and be able to execute. The new contract personnel will assist the existing contractors in the performance of the functions with the expectation that as the events continue, the new contractor will take on the responsibility to execute.

C.5.17 Post Award Meeting and Periodic Progress Meetings. Host post award meeting within 15 calendar days after task order award. Discuss proposed task(s) approach with the Government team. The purpose post award meeting is to introduce Contractor and Government personnel, discuss details of the requirements and deliverables of this PWS, and resolve any concerns that arise because of the discussion (A016).

C.5.18 Travel. Contractor will submit travel request to the COR for approval two weeks prior to scheduled travel dates (A017).

C.5.19 Other Direct Costs (ODC). The Contractor may require hardware, software, and other items incidental to the performance of these services and will be considered as

ODCs. These items must be approved by the PWS TA or Contracting Officer’s

Representative (COR) prior to purchase. Items purchased will be considered GFE/GFM and will be added to the Property Accountability Report (A018).

C.5.20 Contractor Personnel Performance Capabilities and Qualifications.

C.5.21 Except where specific qualification standards are identified in the task orders, it is the

Contractor’s responsibility and prerogative to develop their own internal qualification programs and processes to ensure they have sufficient capability and capacity to meet the quality requirements of the task order products and services.

C.5.22 Contractor Personnel Education and Training Requirements. To perform to the standards of this contract, the contractor will provide competent and proficient individuals on the hardware and software applications necessary to perform their responsibilities at the position and level for which they are assigned. The Government will not be responsible to provide initial training on versions of existing production-related hardware and software to meet satisfactory competency and proficiency levels of individuals, such as new hires, or in preparation for the assumption of task order responsibilities.

Contractor Personnel Performance Capabilities and Qualifications. It is the Contractor’s responsibility and prerogative to develop their own internal qualification programs and processes to ensure they have sufficient capability and capacity to meet the quality requirements of the task order products and services.

C.6 RESEARCH, DEVELOPMENT, TEST AND EVALUATION (RDT&E) WORK AREA

C.6.1 This effort is focused on enhancing the capabilities resident within JTLS-GO and the contract will design, develop, prototype, and operationalize this software. This includes conducting RDT&E on existing JTLS-GO software and the integration of these capabilities with other simulations, devices, programs, and processes (A019).

C.6.2 The contractor will conduct fundamental research and development directed to advancing the state-of-the- art or increasing knowledge and understanding of JTLS-GO and components. This includes research, requirements definition, analysis of technical concepts, technology trade-offs, and investigation of operational concepts.

C.6.3 The contractor will conduct RDT&E on existing JTLS-GO software to improve cybersecurity; adjust to shifting training priorities; address current and emerging training gaps; and ensure C4I interoperability. This overall effort requires access to Top Secret/Sensitive Compartmented Information (TS/SCI) documents and information.

C.6.4 The contractor will determine capability, limitations, and vulnerability of weapon systems representation within the JTLS-GO and design, develop and test state-of-the-art and emerging weapon systems. This applies to, but not limited to, air, ground, maritime, cyber, Electronic Warfare (EW), and space domains, including the effects on potential targets and potential countermeasures of these effects. Associated databases and repositories will be updated with any new changes.

C.6.5 The contractor shall perform fundamental research and development to support the extraction and utilization of data from the Joint Staff J-7 Data Repository This effort will involve importing an Order of Battle Service (OBS) file and creating a JTLS-GO scenario from that file. The contractor will then run JTLS-GO with the created scenario, enabling the loss or damage of systems (Platforms) and the task reorganization of entities within the constraints of the OBS file. Additionally, the contractor may reorganize entities into new units outside the hierarchy specified by the OBS file, based on user input. Finally, the contractor will write the resulting OBS file back into the Joint

Staff J-7 Data Repository, ensuring that entity IDs and Joint Live Virtual, and

Constructive (JLVC) IDs are preserved so the file can be imported and used by the

JLVC Federation. In addition to these tasks, the contractor will conduct research, define requirements, analyze technical concepts, evaluate technology trade-offs, and investigate operational concepts to support the successful execution of these activities.

C.6.6 Intel. The contractor shall ensure Intelligence Surveillance and Reconnaissance

(ISR) and national level intelligence collections and reporting functions are updated and publishes to the National Reconnaissance Office (NRO) National War Gaming System

(NWARS) and the US Air Force Air Space, AFERS-MUSE Air and Space Constructive

Environment- Command and Control (C2)/ Simulation Interface and Cyberspace

Constructive Environment Information Operations Suite Modeling and Simulation

(ACE-IOS).

C.6.7 The contractor will perform JTLS-GO software setup, installation, demonstrations, event support, database builds and training. This includes new equipment training (NET) for the software supported by this PWS. This overall effort requires access to TS/SCI documents and information.

C.6.7 The contractor will support JS J-7’s overall force readiness Joint Training mission as it applies to NATO, Allies, and Coalition in which the Department of

Defense (DoD) has a partnership and/or support agreement.

C.6.8 Develop new enhancements for JS J-7/DDJT’s Wargaming requirements in order to comply with JLVC Modernization Program technical requirements. Provide JS

J-7 a more robust Computer Aided Exercise and Wargaming Tool that can be used to support wargaming efforts, “run-ups” or “risk reduction events” with the staff TA, prior to the stand up or use of large JLVC infrastructure, that will enable exercise planners to determine if the scenario meets the intended objective outcomes with low overhead.

Provide a MPE that is compatible with NATO and other INDOPACOM bi-lateral partners simulation environments. The development of the new enhancement is dependent on the completion of C.6.5 (A020)

C.6.9 Develop new enhancements for JS J-7/DDJT’s Wargaming requirements in order to comply with JLVC Modernization Program technical requirements by providing

Computer Assisted Wargaming and Analysis: Provide the Joint Staff Wargaming Team a capability that meets requirement to conduct 30-day wargame turns and specific AAR outcome details needed to inform the training audience and proceed to the next 30 day turn. The development of the new enhancement is dependent on the completion of C.6.5

(A021).

C.7 OPERATIONS AND MAINTENANCE (O&M) WORK AREA

C.7.1 The contractor will conduct operational enhancements, functional improvements, responsive software code fixes, repairs, and ongoing maintenance to deliver of an operational, secure, stable, and reliable version of JTLS-GO software. The contractor will also execute changes and modifications, as well as provide the technical support and training necessary to successfully satisfy the requirements and objectives of this

PWS (A022).

C.7.2 The contractor will implement changes, modifications, and updates in the JTLS-

GO Standard Database and repository to maintain relevance and ensure accuracy of data.

C.7.3 The contractor will implement JTLS-GO changes, modifications and/or functional improvements to upgrade federation and integration capabilities with other simulations, devices, programs, and processes.

C.7.4 The contractor will implement code changes, modifications and/or functional improvements to ensure JTLS-GO interfaces can properly support C4I systems and/or devices. In most cases, this support will be directed based on the results of design conferences, control groups, working groups and requirements boards. This effort includes not only software for JTLS-GO core components but also, those components, programs, processes, graphical user interfaces, C4I interfaces, tools and other devices associated with JTLS-GO for which the source code is maintained by the contractor.

(Requires access to TS/SCI documents and information)

C.7.5 The contractor will perform JTLS-GO software setup, installation, demonstrations, operations event support, database builds and training. This includes new equipment training (NET) for the software supported by this PWS. This overall effort requires access to TS/SCI documents and information.

C.7.6 The contractor shall perform help desk operations for those sites designated by DD

JT. The Help Desk will normally be by telephone or e-mail and covering duty hours of 8:00 o’clock a.m. to 5:00 o’clock p.m., Pacific Standard Time. However, support outside these hours may be required to support on-going training events in different time zones.

These shall be coordinated with the TA.

C.7.7 The contractor shall conduct O&M on existing JTLS-GO software to improve cybersecurity; adjust to shifting training priorities; address current and emerging training gaps; and ensure C4I interoperability. The contractor will provide software updates to ensure cybersecurity is maintained.

C.7.8 The contractor will support JS J-7’s overall force readiness Joint Training mission as it applies to NATO, Allies, and Coalition in which DoD has a partnership and/or support agreement.

C.8 DELIVERABLES

Deliver all required products in electronic format. Deliverables will be delivered in accordance with the below schedule for comments in a government-approved Contractor format. Deliverables are subject to Government review by a quality review board and, if warranted, may be returned to the Contractor for revision. The Government has the right to inspect the goods and/or services being provided prior to product delivered (FAR part

46). The contractor shall deliver all required documentation and software to the government following final testing by the contractor. The table below outlines the deliverables schedule.

CDRL Para

Ref #

Deliverable Deliverable Description Due Date POCs

A001 C.5.1 Monthly

Status Report

(MSR)

Monthly snapshot in time of contract cost, schedule, and performance

15th of month COR, TA

A002 C.5.2

Software

Updates

Distribute software updates and associated documentation.

Software updates or changes will include a Version

Description

Document (VDD)

With each interim or Minor/Major releases

COR,

A003 C.5.3-

C.54

Software tracking and Software delivery

Document and deliver changes to the software

15th of month COR, TA

A004 C.5.5 Design Documentation

Develop software enhancements based upon the design, cost, schedule approved by government

15th of month COR, A005 C.5.6

Minutes, Reports or Logs

Contractor will provide information of interest to the government unable to attend

Within 5 business days of end of event

COR,

A006 C.5.8

Test Plans Develop test plans where system or software testing is required in support of the core requirements

Submit draft test plans 10 business days prior to each test event

COR,

A007

C.5.9

Test Reports Test report documenting test results after system or software testing has been executed

Within 1-2 business days after each test event

COR,

A008 C.5.10 Demonstrations, databases, events, tests, training

Support government approved events

As required COR, A009 C.5.11

Cybersecurity Contractors provide comprehensive cybersecurity support to

JS J-7

10 Business days prior to all minor and major release dates

Cyber

Branch

Chief

A010 C.5.11.

Cybersecurity workforce certifications

Contractors with privileged JS

Information Systems

(IS) accounts must be certified and qualified either at IAT-I, II, or III in accordance with DoD

8570.01- M. In addition, training and user agreements must be completed and on file with JS J-7

Training and user agreements must be completed and on file with JS J-7

Cybersecurity before privileged access is granted

Cyber

Branch

Chief

A011 C.5.12 Negligent

Discharge of

Classified

Information

(NDCI)

Contractor causing

NDCI(s) during the course of their duties under this PWS may be held financially liable for all actual accumulated restoration costs incurred

Notify government personnel immediately if a suspected NDCI has occurred.

COR,

A012 C.5.13 Program

Management

Reviews

Review of Monthly

Status Report with contract leadership

20th of month COR, A013 C.5.14 Governme nt

Furnished

Equipmen t (GFE)

Report

Annual list of Gov’t property by location.

Within 30 days after Award and

30 prior to the end of the contract

COR,

A014 C.5.15 Invoicing Provide invoices to

COR prior to submission

Invoices shall be submitted monthly prior to official submission in

WAWF.

COR,

A015 C.5.16 Transition

Plan

Will support the activities of the current incumbent

This contact will have a transition period lasting no more than five (5) business days, COR, TA

A016 C.5.17 Post

Award

Meeting

Host post award meeting, discuss proposed tasks approach with the government team.

Within 15 calendar days after task order award

COR,

A017 C.5.18 Travel All travel billed against the contract will be approved prior to travel by the

COR

Submit travel request two weeks prior to planned travel

COR,

A018 C.5.19 ODCs All ODCs will be requested and approved by the

COR prior to purchase.

Five business days prior

COR,

A019 C.6.1 Conduct

RDT&E

work on

JTLS-GO

software

Software that enhances the capabilities resident within

JTLS-GO per specification

Annually COR, A020 C.6.8 Wargamin g capability

The effort will involve importing an Order of

Battle Service (OBS) file and creating a JTLS-GO scenario from that file, run

JTLS-GO with the created scenario, enabling the loss or damage of systems

(Platforms) and the task reorganization of entities within the constraints of the OBS file. Reorganize entities into new units outside the hierarchy specified by the OBS file, based on user input. Write the resulting OBS file back into the Joint Staff J-

7 Data Repository, ensuring that entity IDs and Joint Live Virtual, and

Constructive (JLVC) IDs are preserved so the file can be imported and used by the JLVC Federation

Provide updates to using agile development scrum schedule.

COR,

TA,

JLVC

Mod

Team

A021 C.6.9 JTLS-GO

Machine

Learning/

Artificial

Intelligenc e ISO of

Wargamin g and

Analysis

Develop and implement an

ML/AI capability within

JTLS-Go to automate translation of Commander’s intent into Operational orders for assignment to constructive wargame entities. ML/AI will be used to generate automated behaviors of Blue and

OPFOR forces, and to provide increased processing power of the platform extending wargames for a minimum of 30 continuous days without requiring additional Operational orders. ML/AI will also be employed to analyze JTLS-

GO event data and generate automated after-action reports (AAR).

As required or as directed by the

Government

COR,

TA,

JLVC

Mod

Team

A022 C.7.1 Fully operationa l and relevant

JTLS-GO

software

Operational enhancements, functional improvements, responsive software code fixes, repairs, and ongoing maintenance to deliver an operational, secure, stable, and reliable version of

JTLS-GO software.

Prior to next

JTLS-GO update

(within 6 mos.) of receipt of funds

COR,

All deliverables and products shall be provided to the following mailing addresses:

Reserved

C.9 QUALITY ASSURANCE (QA) METRICS

The following table details metrics that shall be used to measure satisfactory performance in meeting task order objectives and requirements.

Performance

Element Performance Requirement

Surveillance Method

Frequency Acceptable Quality Level

Contractor

Quality Control

Plan

QC activities, inspections, and corrective actions completed as required by the plan.

Inspection by the TA and

Task Order

COR

Quarterly for overall QC activities.

As Required for corrective actions.

100%

Compliance with the contractor plan.

Contract

Deliverables

Contract deliverables as prescribed in the PWS Task

Order.

Conduct inspection of all contract deliverables to verify compliance.

100% inspection of all contract deliverables monthly.

>95% of deliverables submitted timely and without rework required.

Overall

Contract

Performance

Overall contract performance of sufficient quality to earn a

Satisfactory (or higher) rating in the COR’s annual report on

Contractor

Performance

Assessment by the TA and

Task Order

COR

Monthly All performance elements rated

Satisfactory

(or higher)

Invoicing Monthly invoices per contract procedures are timely and accurate

Review & acceptance of the invoice

Monthly 100% accuracy

C.10 SECURITY

C.10.1 Work under this PWS will include access up to, and including, TS/SCI data/information. The contractor must support CLASSIFIED events with qualified personnel possessing appropriate security clearances. All personnel assigned to work under this PWS shall have the minimum-security clearance commensurate with the software being developed and/or tested and the level of security classification associated with the database being used. Certain subject matter experts supporting the above tasks will be required to maintain a TS/SCI clearance. Security requirements are essentially 10% Unclassified work, 70% requiring a Secret Clearance and 20% requiring TS/SCI clearances. Specific clearance requirements will vary among tasks.

C.10.2 Submission of TS/SCI Clearance Requests. Requests for those personnel requiring

TS/SCI clearance will be submitted to and approved by the TA on a case-by-case basis with appropriate justification prior to the Contractor submitting the required documentation to the COR for submission to Joint Staff Security Office (JSSO) for clearance nomination. Classified Material Controls. Mark, safeguard, manage and protect all classified information IAW guidance provided in the DD Form 254

(Contract Security Classification Specification).

C.10.3 Unclassified Material Controls. Mark, safeguard, manage, and protect all controlled unclassified and personally identifiable information.

C.10.4 Classified Marking Guidance. Comply with the guidance published in DoD

5200.01, Volume 2, dated 24 Feb 2012.

C.10.5 Safeguarding Government Property. The Contractor is responsible for safeguarding all Government equipment, information and other property provided for Contractor use.

C.11 GOVERNMENT FURNISHED EQUIPMENT (GFE) AND MATERIAL (GFM)

C11.1 Government Furnished Equipment (GFE)/Government Furnished Material

(GFM): The Government shall provide specific hardware and software configurations as required by this PWS, if needed. The Government, when possible and appropriate, shall provide relevant equipment, facilities, or locations and point of contact information (e.g., laboratory network, computers, encryption equipment or any other equipment required) to support this effort. Government provided GFE and/or GFM for use at off-site Government and contractor sites shall be listed in an Attachment. The Government shall provide routine and fair wear and tear replacement parts for the GFE. The contractor is responsible for installation of the spare parts and for performing routine care and maintenance of the

GFE. Consumable materials for equipment provided at the Government site shall be provided at no cost for work performed in direct support of this PWS. The contractor shall provide an annual status report for all GFE.

C.11.2 Government-Furnished Information (GFI): The Contractor shall be provided existing documentation and information required to perform the tasks identified in this

PWS. If additional GFI items are required by the Contractor for the performance of these tasks they shall be identified to the TA when the requirement is recognized and shall be provided on a case-by-case basis.

C.12 PLACE OF PERFORMANCE

The work required under this PWS will primarily be accomplished at the VALKYRIE

Enterprises, Inc. facility located in California, and the JS J-7 facility located in Suffolk, Virginia. However, some work will require the contractor to work at various contractor sites, government facilities, and other government approved locations. Normal workdays are

Monday through Friday except US Federal Holidays. Workers typically work eight (8) hours per day, 40 hours per week. Flextime workers start not earlier than 0600 and not later than

0900. Core hours of work are from 0900 to 1500 daily. All employees are expected to be available during core hours. The Contractor will minimize the number of contractor personnel permanently seated within JS J-7 facilities. The Government will provide access to kiosks when required to support tasks outlined in this task order at the JS J-7 Suffolk, Virginia facility. The contractor may also be required to work at other Government sites in

CONUS or OCONUS. Access to the Government’s facilities shall be coordinated with the

Contracting Officer’s Representative (COR) or TA.

C.13 TRAVEL

C.13.1 O&M and RDT&E Associated Travel: These trips are expected to be of short duration and funded by the Government. The Contractor shall travel as required by the above tasks with the approval of the Task Order COR or TA. Expected minimum travel is outlined in accordance with the below table. The contractor shall plan accordingly to obtain approval from COR two weeks prior to planned travel.

O&M Travel (36 Months) Destination # Trips per

POP

# Contractors per

Trip # Days per

Trip Note

Suffolk, Virginia

10 2 10 1 & 2

Suffolk, 8 2 5 1 & 2

RDT&E Travel (36 Months) Destination # Trips per

POP

# Contractors per

Trip # Days per

Trip Note

Suffolk, 2 5 1 & 2

NOTES:

1. Developers may be required to work 10-hrs shifts for these events.

2. Travel time is not included.

C.13.2 Travel Coordination. The Contractor is responsible for all contractor travel arrangements associated with this task order. The Contractor will not decide or take any actions on behalf of government personnel, such as room reservations or setting aside blocks of rooms, which may have the appearance of a contract obligating Government funds.

C.13.3 Travel Regulations. The Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this PWS.

C.13.4 ITAR. The Contractor, including its foreign national employees and subcontractors supporting JS J-7, FJD, will be required to travel outside the U.S. and may be responsible for the temporary import and export of defense articles, including technical data, and for the performance of defense services in support of the PWS. Such activity will be performed pursuant to 22 CFR 126.4(a) of the International Traffic in Arms

Regulations (ITAR). In this instance, the word temporary means that the Contractor will not leave any defense articles, including technical data at the site being supported.

C.14 GOVERNMENT MANAGEMENT

C.14.1 Joint Staff J-7 Contracting Officer’s Representative (COR): Ms. LaTara Kea-Edwards, (757)

203-8661, latara.k.keaedwards.civ@mail.mil. DSN prefix: 668

C.14.2 Technical Assistant (TA): Mr. Mark Dwyer, mark.j.dwyer2.civ@mail.mil (757) 203-6734, DSN prefix: 668

C.15 GENERAL CONTRACTOR INFORMATION

C.15.1 Release of Information. Project-related documentation developed in support of this contract is not considered publicly releasable and will be marked with the appropriate distribution statement as directed by the Government. The Government has the authority to grant the Contractor permission to publicly release project- related documentation.

VALKYRIE ENTERPRISES, INC. holds the intellectual property rights to the simulation and technical data and retains the rights to distribute the software and documentation within these rights. In furtherance of the OSD-OUSD (P&R) mission and under the provisions of 22 CFR 126.4(a) and 125.4(b)(3) & (13), ITAR, the contractor and its subcontractors are authorized to provide JTLS software and technical data to international countries with U.S. State Department approval.

C.15.2 Data Rights. In accordance with DFARS 252.227-7013 Rights in Technical Data-

Noncommercial Items, the Government possesses Government Purpose Rights data rights on all information and material developed or delivered under this contract.

C.15.3 Product Delivery. The Contractor shall deliver all required products in an electronic format, unless otherwise directed. Deliverables and document drafts will be delivered to the TA for comments in a Government/Contractor approved Contractor format. Deliverables are subject to Government review and may be returned to the

Contractor for revision. The Government will have five (5) working days to provide comments. Upon receipt of comments, the Contractor will provide the final report five (5) working days after receipt. Status on all deliverables to include metric adherence will be included in the Monthly Status Report (MSR).

C.15.4 Contractor Situational Awareness. All Contractors assigned to a government workspace and possessing a Joint Staff Information Network account are required to review the Joint Staff NIPR/SIPR homepage daily for situational awareness of DoD and

JS activities.

C.15.5 General Contractor Training. All assigned Contractors will complete mandatory JS training as required by the Government.

C.15.6 Information Assurance Contractor Training and Certification. The contractor shall comply with Joint Staff, J7 Information Assurance Contractor Training. However, any

IA/IT certifications in the performance of task orders will be in accordance with the

“PERSONNEL QUALIFICATIONS”" requirements section of this section. Any exception to training must be approved by the COR.

C. 16 Labor Categories

LABOR CATEGORY: PROGRAM MANAGER

DUTIES: Responsible for the overall management of the specific task order(s) and ensuring that the…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Apr 4, 2025.