Attachment_4_-_TO_0001_Draft_PWS.pdf

PEO-STRI

W900KK-16-R-0047

TO 0001

12 AUG 2016

DISTRIBUTION LIST STATEMENT A:

Approved for public release; distribution is unlimited.

Attachment 4 – DRAFT PWS

Performance Work Statement

For Post Deployment Software Support (PDSS) Task Order 0001

Close Combat Tactical Trainer (CCTT)

PWS-2016-044

Contract No. W900KK-16-R-0047

U.S. Army Program Executive Office for

Simulation, Training and Instrumentation (PEO STRI) 12350 Research Parkway Orlando, FL 32826-3726 i

Table of Contents

1. SCOPE

1.1 Background

2. APPLICABLE DOCUMENTS

2.1 Department of Defense Standards

2.2 PEO STRI Documents

2.3 Availability of Department of Defense Standards

2.4 Department of Defense Directives

2.5 Availability of Department of Defense Directives

2.6 Department of Defense Instructions

2.7 Availability of Department of Defense Instructions

2.8 Other Government Documents, Drawings, and Publications

2.9 Non-Government Standards and Other Publications

3. REQUIREMENTS

3.1 Management Requirements

3.1.1 Program Management

3.1.1.1 Technical and Management Work Planning

3.1.1.2 Financial Management and Integrated Master Schedule (IMS)

3.1.2 Classified Requirements

3.1.2.1 Security Requirements Compliance (DD Form 254)

3.1.2.2 Information Assurance/Information Technology (IA/IT)

3.1.2.3 Visitor Log

3.1.3 Lead Integrator

3.1.4 Software Support Agreements

3.1.5 Cybersecurity Program

3.1.5.1 Cybersecurity Vulnerability Management Program

3.1.5.2 Certification and Accreditation (C&A)

3.1.5.3 Continuity of Operations Plan (COOP)

3.1.6 Government Furnished Property (GFP)

3.1.7 Government Purpose Rights (GPR)

3.1.8 Configuration Management (CM)

3.1.8.1 Baseline Configuration Audit (BCA)

3.1.8.2 Hardware Configuration Management Database

3.1.8.3 Program Review Board (PRB)

3.1.8.4 Software Configuration Management

3.1.8.4.1 Software Configuration Control Board

3.1.8.4.2 Software Configuration Management Database

3.1.9 Risk Management

3.1.10 Conferences and Reviews

3.1.10.1 Post Award Conference (PAC)

3.1.10.2 Systems Engineering Technical Reviews

3.1.11 Integrated Project Teams (IPT)

3.2 General Technical Requirements

3.2.1 CCTT Systems Integrator

3.2.2 Enhancements – System Modification Tasks

3.2.3 Systems Engineering

3.2.3.1 Systems Engineering Process

3.2.3.2 Requirements Analysis and Functional Allocation

3.2.3.3 Rapid Prototyping

3.2.3.4 Requirements Analysis and Concept Exploration

3.2.4 System Design

3.2.4.1 Hardware Design and Acquisition

3.2.4.2 Software Design and Development

3.2.4.3 Cybersecurity Engineering

3.2.5 System Test and Evaluation

3.2.5.1 T&E Deficiency Reporting System

3.3 Replication, Distribution, Installation and Training (RDIT)

3.3.1 Installation Team

3.3.2 Courseware Development

3.3.3 Publications, Documentation and Briefings – Reserved

3.3.4 Online Data Library

3.4 PDSS Facility

3.4.1 Communications

3.4.2 Security

3.4.3 Facility Housekeeping

3.4.4 Facility Management

3.4.4.1 Daily Readiness Checks (DRC)

3.4.4.2 Preventive Maintenance (PM)

3.4.4.3 Maintenance Problems

3.4.4.4 Isolate Equipment Faults

3.5 PDSS Administration, Maintenance and Engineering Support

3.5.1 System and Software Engineering Site Support

3.5.2 Software Baseline Management

3.5.2.1 Problem Trouble Report Resolution

3.5.3 Item Unique Identification (IUID)

3.5.4 Technical Data Package (TDP)

3.5.5 Live Virtual Constructive (LVC) and Interoperability Support

3.5.6 CCTT System Exercises

3.5.7 Tours and Demonstrations

3.5.8 System Support

3.5.8.1 Software Support

3.5.9 Systems Management Support

3.5.9.1 Networking

3.5.9.2 Obsolescence and Technology Insertion

3.5.9.3 Hardware Procurement

3.5.9.4 Database Generation

3.6 Transitional Meetings

3.6.1 Transition Phase-in (Transition with current contractor)

3.6.2 Pre-Contract Support Date (CSD) Meeting and Planning

3.6.3 Phase-Out (Transition to Successor) - Reserved

3.7 Travel

3.8 Contractor Manpower

1. SCOPE.

The PDSS contract will provide the following services: Software (SW) maintenance such as corrective, perfective, adaptive and preventive maintenance; Sustaining Engineering to sustain the CCTT SW release in the field; Product support, to maintain the integrity and quality of the processes, products and supplier networks employed during the operations and maintenance phase; Facility Support to maintain a development and test facility ready to support and sustain the software in the field; Cybersecurity to maintain the system and protect the information protected as per Government mandates; Operational Support to maintain the current and plan for future SW releases while assessing and maintaining system performance, database maintenance, Configuration Management, rapid prototyping, hardware analysis and qualification, and maintaining the Technical Data Package (TDP).

For the purpose of this PWS, Software Maintenance include activities for preparing new block releases; Perfective maintenance in support of concurrency modification to the simulators;

Adaptive maintenance to support the close affiliation with the One Semi-Automated Forces (OneSAF), Synthetic Environment Core (SE Core), and the Live, Virtual and Constructive Integrated Architecture (LVC-IA) programs; and Corrective maintenance to support fielded software baselines. CCTT refers to the CCTT program, software and hardware, and the support of those programs which use the CCTT software or that interact with CCTT as an integral part of the system. These specifically include the CCTT, Reconfigurable Vehicle Tactical Trainer (RVTT), Dismounted Soldier Training Systems (DSTS), and programs the CCTT software has been distributed to over the life of the program.

Unless otherwise noted in this PWS, the requirements for this Task Order (TO) are defined in the Technical Support Services for PDSS APM CCTT, PWS-2016-043 herein called the Basic PWS.

In case of a conflict between the requirements and documents cited herein and the Basic PWS, this Task Order PWS takes precedence.

1.1 Background.

CCTT is a collective training device composed of three separate, but integrated systems (CCTT, RVTT and DSTS). CCTT collectively trains Armor, Cavalry, Infantry, Mechanized Infantry, and Armored Reconnaissance units from Squad through Battalion/Squadron level, to include their staffs to increase and sustain readiness. The primary training audience operates from immersive full-crew simulators, mock-up command posts, and live battalion command posts to train in combined arms maneuver and wide area security tactical missions, conduct mission rehearsal, and enhance live training.

PDSS for CCTT provides all aspects of systems engineering and software support to CCTT to maintain its mission of providing a virtual collective training capability.

This PWS describes a performance based work requirements in terms of “what” the required service outputs are rather than “how” to perform the work. The service provider is encouraged to strive for constant improvement and innovation in the performance of this contract as long as the performance objectives are being achieved at the desired levels of performance. Successfully identifying and applying best business and scientific practices can reduce business expenses and improve customer satisfaction. The service provider is required to manage the quality of the services delivered using their internal management structure. This PWS attempts to create a Government-service provider relationship that promotes achievement of mutually beneficial goals, and promotes a partnership environment. The success of this contract is dependent upon free and open communication between the Government and the service provider.

2. APPLICABLE DOCUMENTS.

The following documents of issue shown on the document summary list form a part of this PWS to the extent specified herein. In the event of a conflict between documents referenced herein (section 2.) and the contents of this PWS (section 3.), the contents of the PWS shall be the governing requirement.

2.1 Department of Defense Standards.

MIL-STD-130 N w/Change 1 Identification Marking of U.S. Military Property MIL-STD-31000A Technical Data Packages MIL-STD-40051-2C Page-Based Technical Manuals

2.2 PEO STRI Documents

PRF-PT-00024 System Specification for Close Combat Tactical Trainer CRISD Computer Resources Integrated Support Document for CCTT N/A Technical Data Package (TDP) for CCTT

Software Requirements Specification (SRS) Product Definition Data (PDD) Interface Design Description (IDD) Prime Item Development Specification (PIDS) Hardware Baseline Document (HBD) Software Baseline Document (SBD) Site Layout Diagram

2.3 Availability of Department of Defense Standards.

Copies are available on the WWW at URL: http://quicksearch.dla.mil/

2.4 Department of Defense Directives.

DoD 8570.01-M Information Assurance (IA) Training, Certification, and Workforce Improvement Management

2.5 Availability of Department of Defense Directives.

Copies are available on the WWW at URL: http://www.dtic.mil/whs/directives/

2.6 Department of Defense Instructions.

DoDI 8500.01 Cybersecurity DoDI 8510.01 Risk Management Framework (RMF) for DoD Information

Technology (IT), 12 Mar 2014

2.7 Availability of Department of Defense Instructions.

Copies are available on the WWW at URL: http://www.dtic.mil/whs/directives/

2.8 Other Government Documents, Drawings, and Publications.

DoD 5220.22-M National Industrial Security Program Operating Manual CNSSI No. 1253 Security Categorization and Control Selection for National

Security Systems Army Regulation (AR) 25-1 Army Information Technology AR 25-2 Information Assurance AR 525-13 Anti-Terrorism

Copies are available on the WWW at:

http://ciog6.army.mil/PolicyLegislation/tabid/64/Default.aspx

Applicable Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) http://iase.disa.mil/stigs/Pages/index.aspx

MIL-PRF-32216A Evaluation of Commercial Off-The-Shelf (COTS) Manuals and

Preparation of Supplemental Data Copies are available on the WWW at URL: http://quicksearch.dla.mil/ http://quicksearch.dla.mil/ http://www.dtic.mil/whs/directives/ http://www.dtic.mil/whs/directives/ http://ciog6.army.mil/PolicyLegislation/tabid/64/Default.aspx http://ciog6.army.mil/PolicyLegislation/tabid/64/Default.aspx http://iase.disa.mil/stigs/Pages/index.aspx http://quicksearch.dla.mil/

Joint Travel Regulation - http://www.defensetravel.dod.mil/site/travelreg.cfm

2.9 Non-Government Standards and Other Publications.

GEIA-HB-0007-B Handbook, Logistics Product Data GEIA-STD-0007-B Specification, Logistics Data Products

3. REQUIREMENTS.

3.1 Management Requirements.

3.1.1 Program Management.

The contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The contractor shall organize, coordinate, and control all program activities to ensure compliance with the contract requirements and the timely delivery of the required products and services. The contractor shall provide the necessary program management, systems engineering, design engineering, materials, services, equipment, facilities, testing, technical, logistics, manufacturing, and administrative support for the efforts described in this PWS. The contractor shall monitor the progress of all the work performed and costs incurred under the contract.

3.1.1.1 Technical and Management Work Planning.

The contractor shall develop and maintain a plan to document its management and technical approach to ensure compliance with the contract requirements and the timely delivery of the required products and services. The contractor shall manage all technical and non-technical personnel that will be dedicated in support of the PDSS contract. The contractor shall manage software releases and sustainment engineering activities and conduct risk and metrics analysis.

This shall include, managing the generation and testing of block releases to ensure they meet government requirements and user expectations. The contractor shall be responsible for managing all aspects of sustainment engineering efforts, including managing independent testing, independent verification, acquisition, facility support, operations support and information assurance. The contractor shall be responsible for risk management activities to include identifying risk, mitigation strategies, presenting courses of action in an IPT environment, executing mitigation strategy, capturing progress metrics data and providing results of metric analysis. The contractor shall identify and document events, accomplishments, and criteria http://www.defensetravel.dod.mil/site/travelreg.cfm pursuant to successful completion of the work efforts and report status via the established IPT process.

3.1.1.2 Financial Management and Integrated Master Schedule (IMS).

The contractor shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations, and invoices against each contract line item and sub line item. The contractor shall document and track to levels which represent how they plan to accomplish the entire contract work scope and which are consistent with internal organizations and processes. These documents shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status by Fiscal Year (FY). The contractor shall identify major elements of subcontracted work. The contractor shall prepare the Contract Invoicing and Payment Report.

The contractor shall develop, implement, manage to, update, and maintain the contract IMS that documents schedules, tasks and milestones to meet the requirements of this contract. All contract schedule information delivered or presented at program reviews shall originate from the IMS and shall contain all critical events and exit criteria, accomplishments, predecessors and successors’ events, and their dependencies. The IMS shall address total program activities including activities performed by subcontractors.

The contractor shall document the planning and scheduling effort, related Government responsibilities, and the interaction for the efforts required for development and delivery of the training products. The contractor shall develop and document a tiered scheduling system showing all program milestones and prerequisite events, conferences, reviews, data submittals, and deliveries. The contractor shall construct the IMS to assure that these milestones are met and to assure deliveries as required by the contract. The Contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

(DI-MGMT-81861A) Integrated Program Management Report (IPMR) Format 5

3.1.2 Classified Requirements.

Contractor personnel and subcontractors performing the work tasks associated with this contract shall require access to classified information or facilities that process classified information. All contractor personnel working on this effort shall be U.S. citizens, possess and maintain an active Secret security clearance and a DoD issued Common Access Card (CAC). Any contractor personnel without a clearance must be approved by the Government Contracting Officer Representative.

3.1.2.1 Security Requirements Compliance (DD Form 254).

The contractor shall comply with the security requirements found in the DD Form 254, Contract Security Classification Specifications.

3.1.2.2 Information Assurance/Information Technology (IA/IT).

All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of appointment to IA/IT functions.

Per DoD 8570.01-M , DFARS 252.239.7001 and AR 25-2, the contractor employees supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

3.1.2.3 Visitor Log.

The contractor shall maintain visitor control for the PDSS lab and associated offices. The contractor shall keep a log of all visitors to the PDSS facility and compile a monthly report on visitors to the PDSS facility.

(DI-MGMT-80227) Contractor's Progress, Status and Management Report

3.1.3 Lead Integrator.

The contractor shall support the development of the comprehensive CCTT capability as the overarching lead systems integrator. The contractor shall establish and enforce systems engineering processes to ensure that all development efforts, regardless of source, conform to CCTT’s architecture, DoD standards, cybersecurity, quality, documentation and other associated guidelines. The contractor shall be a primary member of the technical IPTs for all CCTT development efforts regardless of contract or source. The contractor shall support the Government in technical reviews of all systems engineering, requirements, design implementation artifacts and test plans for all CCTT modifications. The contractor shall provide 3rd party developer access to the CCTT development environment (which includes but is not limited to: CM, build tools, test tools and issue tracking tools) to external CCTT developers. The contractor shall integrate third party software and documentation into a common CCTT baseline.

The contractor shall test and validate the integrated CCTT baseline. The contractor shall ensure that resources are appropriately applied across internal and external development efforts.

The contractor shall create and deliver complete software baselines to 3rd party contractors who are either developing new CCTT capabilities or modifying the baseline. The deliverable shall include all software necessary to build a software load to include source code, load build instructions, software version description (SVD), and other documentation.

3.1.4 Software Support Agreements.

The contractor shall track and maintain the current software licensing and support agreements for the operating systems, development environment and any other licensed software to facilitate the support and maintenance of all CCTT PDSS and fielded systems software. The contractor shall purchase license renewals to ensure that all licenses are kept up to date and that no licenses are allowed to expire either in the field or in the PDSS environment.

3.1.5 Cybersecurity Program.

The contractor shall develop and maintain cybersecurity processes for the CCTT program. The contractor shall establish an overarching framework which ensures that cybersecurity is a core part of the systems engineering process for all CCTT requirements, designs, development, integration, test, fielding, documentation, interoperability and support. The cybersecurity program shall be based upon the Risk Management Framework (RMF) and shall transition to any alternate process as required by the Army.

3.1.5.1 Cybersecurity Vulnerability Management Program.

As part of the Cybersecurity Vulnerability Management Program, the contractor shall document the incorporated and unincorporated Cybersecurity Vulnerability Alerts, Cybersecurity Vulnerability Bulletins, and Cybersecurity Vulnerability Technical Advisories. The Cybersecurity Vulnerability Management plan shall include but is not limited to identifying and assessing potential threats to determine risks. It also involves developing and implementing controls, countermeasures, or solutions. The contractor shall monitor the system for compliance and success, while evaluating and refining the Cybersecurity Vulnerability Management Program as necessary. The contractor shall incorporate all applicable DOD and Department of the Army (DA) Cybersecurity Vulnerability Management messages issued on behalf of the Department of Army G3, CIO/G6 and Joint Task Force-Global Network Operations. The contractor shall provide justification for each unincorporated Cybersecurity Vulnerability Management Program message (i.e., describe the specific negative impact the Cybersecurity Vulnerability Management Program message incorporation would have on the system operation).

The contractor shall report all Cybersecurity Vulnerability Assessments, STIGs and Bulletins within a system Plan of Action and Milestone (POA&M) at least monthly and provide a list outlining which were implemented, those not implemented and why they were not and how mitigated if mitigation required. All non-implemented Cybersecurity Vulnerability Assessments and STIGs shall require Government concurrence. The contractor shall provide a comprehensive and up to date software scan using current Army Best Business Practices for scanning and remediation every month. The contractor shall provide the data to the Government that will be rolled up to the ASAALT Cyber and the PEO to ensure the basic mission assurance techniques are implemented uniformly with the portfolio.

Contractor shall implement STIGs within 30 days from release of a new DISA STIG. Where an update cannot be technically applied due to system functionality, that STIG item shall be documented in the system POA&M with appropriate mitigations. If an update cannot be applied within 30 days the contractor shall provide a milestone schedule in the POA&M item for application for Government approval.

The contractor shall perform manual scans and provide to the Government at least monthly to ensure the system is Federal Information Security Management Act (FISMA) and Security Technical Implementation Guide (STIG) compliant. The contractor shall create and field four times a year a fully integrated and tested vulnerability patches, which minimize installation and system downtime, to all CCTT systems.

3.1.5.2 Certification and Accreditation (C&A).

The contractor shall comply with the Cybersecurity process In Accordance With (IAW) DOD

8510.01 (RMF). The contractor shall support Government Cybersecurity, Certification and Accreditation (C&A), and Connectivity or Interconnectivity activities as required, including providing C&A documentation, upon request, in a format acceptable to DoD Cybersecurity and C&A activities.

The contractor shall produce all components of the RMF package necessary to deliver and operate a fully accredited CCTT system. The contractor shall ensure that security requirements and procedures set forth for the system under RMF meet the standards for a Medium (Confidentiality), Low (Integrity), and Low (Availability) system with a classified security overlay IAW applicable DoD and Army IA regulations.

The contractor shall ensure compliance with the policies and procedures for Certification and Accreditation IAW AR 25-2, paragraphs 5-1 through 5-10 for any system or software application that touches the Army Network directly or indirectly or has the capability to connect. The contractor shall follow the activities in the RMF and all applicable Cybersecurity controls must be met either by incorporation, inheritance, waiver, or exception.

The contractor shall meet accreditation with each operational environment of the system. The contractor shall clearly establish procedures between standalone mode and connection to a global network at another confidentiality level for the C&A. The concept of operations document shall have a single accreditation that addresses all variations. The contractor shall adhere with type-accreditation guidance for CCTT.

The contractor shall support CCTT System, PDSS Lab and development environment RMF accreditation and shall perform RMF continuous monitoring activities thereafter as required by the RMF process established by the Army. The contractor shall support the Army organizations requirements to prepare a Certification and Accreditation Process (CAP) package to request connection approval.

(DI-MGMT-82001) DOD Risk Management Framework (RMF) Package Deliverables

3.1.5.3 Continuity of Operations Plan (COOP).

The contractor shall establish a process to enable the continuity of operations of the PDSS lab in the event of the loss of access or use of the facility, destruction of critical program data or other event which reduces the capability to meet the requirements outlined in this PWS.

3.1.6 Government Furnished Property (GFP).

Upon contract award, the contractor shall inventory and provide status and supply condition of all GFP, to include GFE and GFI, and subsequently, maintain records of all GFP. The contractor shall submit annual inventory reports to the Government, on the anniversary of the contract award. The contractor shall be responsible for the maintenance, custody, control, movement, disposal and storage of all GFP. The contractor shall maintain the equipment in the same functional and physical state as received except for the normal wear and tear. The contractor shall support any Government audit or inventory control actions.

The contractor shall perform the following to ensure positive control and safety of Government furnished items:

a. Examine upon receipt, consistent with practicality, to detect damage

b. Provide storage that precludes deterioration

c. Examine prior to installation, consistent with practicality, to detect damage

d. Identify and protect from improper use

e. Maintain IAW technical documentation

f. Dispose properly when authorized by the Government

g. Transport/ship when authorized by the Government

h. Verify and audit quantity periodically

(DI-ILSS-81251) Equipment Inventory Records (EIRS)

(DI-MGMT-80269) Status of Government Furnished Equipment (GFE) Report

3.1.7 Government Purpose Rights (GPR).

All technical data and software shall be provided with a minimum of GPR; however, if software cannot be provided with GPR it shall be provided with a license at no cost and allow distribution, modification and use for any CCTT PDSS purpose. Any 3rd party licensed software shall be provided with a transferable license that allows distribution and use for any CCTT PDSS purpose by any DoD contractor.

When the addition of new software or hardware is proposed for the system or developed under this contract with Government funding or partial Government funding, the contractor shall ensure that sufficient rights in technical data, both software and hardware, are procured such that the Government can maintain and modify the system using Government personnel and third party contractors. Government approval is required for other than government purpose rights.

3.1.8 Configuration Management (CM).

The contractor shall use an automated internal CM process to monitor, and control all configuration documentation, physical media, and physical parts representing or comprising the system Configuration Items (CIs). The contractor shall plan and implement an automated CM function to perform configuration control, configuration identification, audits, and status accounting in a system-engineering environment. The contractor shall develop, maintain, and execute CM procedures and processes for control of all software baselines. Hardware configuration management shall be conducted on the Lab assets and fielded assets.

(DI-CMAN-80858B) Contractor's Configuration Management Plan

The contractor shall track and update all software licenses with restricted rights and warranty information. The contractor shall identify and update obsolete CCTT, COTS and third party application software and tools necessary to ensure continued operations and support of CCTT and Lab resources. The contractor shall maintain a configuration managed listing of all software baselines, down to the individual patch level, for all fielded instances of CCTT.

For the CCTT PDSS lab, the contractor shall maintain configuration management for all system hardware, warranty information, technical documentation, training materials and manuals. The contractor shall perform quality assurance (QA) and configuration and data management (CM/DM) for all lab and first article hardware designed, developed, manufactured, integrated and tested under PDSS and separately contracted Engineering Change proposal (ECP) performed by other contractors.

3.1.8.1 Baseline Configuration Audit (BCA).

Upon contract award, the contractor shall perform a BCA. The purpose of the BCA is to establish a baseline configuration and performance of the system in the lab at the time of Task Order (TO) award.

3.1.8.2 Hardware Configuration Management Database.

The contractor shall maintain a database of all fielded system hardware configurations and maintain the content of the database as configurations change, whether those changes occur through PDSS or any other means. This database shall include, but not be limited to, the hardware configurations at all CCTT fielded locations. The database shall have a graphical user interface with automated queries and return the results in a human readable, printable format.

The current PDSS fielded hardware database will be provided as GFI and can be maintained for this effort or the contractor can transition the GFI content to a tool of their choice.

3.1.8.3 Program Review Board (PRB).

The contractor shall review all proposed changes to the controlled CCTT system baselines. The contractor shall prepare recommendations on the proposed changes that will clearly state the technical merits, whether an alternate approach is recommended, and the necessity of the proposed change, cost estimate, and impact on the schedule. The contractor shall serve as the recorder for the PRB. All PRB activities shall be executed with Government approval after review in normal IPTs.

3.1.8.4 Software Configuration Management.

The contractor shall establish and document a software configuration management process. The contractor’s software configuration management plan may be incorporated into the software development process plans or may be a separate configuration management plan.

3.1.8.4.1 Software Configuration Control Board.

The contractor shall establish and maintain a software configuration control board or equivalent responsible for configuration control of all CCTT software configuration items and related software products. The software configuration control board shall be responsible for COTS (including open source) management including obsolescence or IA driven updates, product and version identification. The contractor shall obtain Government approval of any changes to the system software or its COTS/GOTS third party components. The contractor shall ensure that all COTS products included in the system deliverable configuration are commercially supported and IA compliant.

3.1.8.4.2 Software Configuration Management Database.

The contractor shall establish and maintain a software configuration management database in accordance with the software development process plan. A schema shall be developed for identification of software items and their versions. The contractor shall perform the following:

identification and recording of change request, analysis and evaluation of the changes; approval or disapproval of the request, and implementation, verification, and release of the modified software item. The database shall contain an audit trail whereby each modification, the reason for the modification, and authorization of the modification can be traced.

3.1.9 Risk Management.

The contractor shall conduct risk management to systematically control the uncertainty in the project’s ability to meet cost, schedule, and performance objectives. The contractor shall conduct that part of risk management that directly impacts the technical effort and involves risk-management preparation, risk identification, risk assessment, risk-handling option assessment, risk analysis, risk mitigation and risk control. Risk management to product requirement objectives shall be covered at all program and technical reviews. The contractor shall provide Government insight into the contractor’s tools, assessment, mitigation, and control techniques.

The contractor shall document risk management as part of the Contractor Progress, Status, and Management Report.

3.1.10 Conferences and Reviews.

The contractor shall conduct, attend, and participate in conferences, meetings and reviews to be held at both contractor and Government facilities. Conducted conferences and reviews will be co-chaired by a Government and contractor representative. The contractor shall explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by this effort. The contractor shall provide minutes for conferences, reviews and meetings that are initiated and conducted by the contractor. The contractor shall have key personnel and support available to conduct the conference. The contractor shall make available facilities for Government only meetings during all conferences and reviews. The contractor and subcontractors shall attend conferences, meetings and reviews when required to address key elements.

(DI-ADMN-81250A) Conference Minutes

3.1.10.1 Post Award Conference (PAC).

The first conference will be the PAC; it shall also be the first conference to be held after each TO Award. The purpose of the conference shall be to establish the framework of contractor and Government interaction during the performance period of the contract. The PAC shall include the presentation, discussion of information and data relating to:

a. Introduction and contract overview

b. Discussion and clarification of requirements

c. CDRL delivery schedule and status

d. CM approach

e. Software development approach

f. System integration and test approach

g. QA and management approach

h. Updated team contact list (names, IPT memberships, phone numbers, and email addresses)

i. Lab facility status

j. Transition plan from current contractor

3.1.10.2 Systems Engineering Technical Reviews.

The contractor shall conduct technical reviews associated with the phases of the systems engineering process as required throughout the contract. This shall include (but is not limited to) requirement reviews, design reviews, in progress reviews and test readiness reviews. The contractor shall conduct and participate in technical reviews in support of the system engineering process for third party system development. Entry and exit criteria shall be established for all formal reviews in a joint IPT with development stakeholders prior to the execution of all formal reviews. All results from formal reviews shall be presented in an IPT setting with all stakeholders.

The contractor shall plan to support two formal technical reviews with 3rd party contractors that will be identified after TO award. The contractor shall also plan for any technical reviews necessary for the internal development efforts identified within this PWS.

3.1.11 Integrated Project Teams (IPT).

The contractor shall lead, attend and participate in IPT meetings to be conducted throughout the contract. IPT meetings shall provide a forum suitable for maintaining a continuous interchange of ideas, issues, and to identify and resolve potential problem areas. A PDSS IPT meeting shall be held on a weekly basis to discuss all efforts under this contract. The contractor shall also participate, upon Government request, in other IPT meetings that include or affect CCTT. These include but are not limited to:

• Synthetic Environment Core (SE Core) IPTs: weekly Database Review Board (DRB)/PRB, biweekly Confederate Coordination Meetings (CCMs), and database IPT.

• Monthly Live Virtual Constructive-Integrating Architecture (LVC-IA) IPTs.

• Yearly Technology Refreshment IPTs

• Weekly One Semi-Automated Forces (OneSAF) IPTs

• Daily OneSAF Engineering Integration Reviews

• Weekly CCTT Concurrency Engineering and Production IPTs

• Weekly CCTT Image Generator (IG) IPTs

The contractor shall schedule and participate in the IPT meetings as requested. Upon Government request the contractor shall prepare agendas and comprehensive/accurate minutes for meetings they conduct and reports for meetings they participate or attend.

3.2 General Technical Requirements.

3.2.1 CCTT Systems Integrator.

The contractor shall integrate all development efforts that are performed under this contract into the CCTT baseline. The contractor shall maintain system level requirements; create and review designs; maintain the CCTT architecture; establish and enforce processes and controls to ensure design and quality standards; establish a development/production environment and associated infrastructure; integrate, validate and test all software into a common maintained CCTT baseline.

Computer programs and computer data system shall be fully integrated IAW the CCTT system specification (PRF-PT-00024).

3.2.2 Enhancements – System Modification Tasks.

The contractor shall design, develop, integrate, deliver, install, and test CCTT Simulator and Simulation system enhancements and upgrades. The contractor shall design, develop, integrate, deliver, install, and test CCTT modifications that improve the lifecycle cost of CCTT. For all system enhancements performed under this contract, the contractor shall update existing requirements, design, interface, test, training, and operator and maintainer documentation as required to reflect all modifications to the CCTT system.

For this task order the contractor shall perform the following enhancements:

1. Replace legacy Plan View Display (PVD) with OneSAF PVD at the Master Control Computer and the After Action Review workstation. Further information regarding this requirement is found in the GFI portion of this solicitation.

2. Replace Digital Army USMTF/ VMF Stimulator (DAUVS) with OneSAF’s Mission Command Adapter (MCA) Web Service.

3. Replace the Operations Center (OC) with an Operations (Ops) Workstation that shall provide training command staff the means to participate in a CCTT exercise by interacting with trainees through tactical mission command devices and voice communication in the CCTT radio infrastructure.

a. The Ops Workstation shall allow the Battalion (BN) or Brigade (BDE) command staff to observe and interact with exercise participants using a digital mission command system that matches the version of the system currently fielded to the CCTT modules at that location (FBCB2, JCR, JBC-P, etc.) to provide BN/BDE level situational awareness and command and control.

b. The system shall support the creation, viewing, transmission and receipt of tactical overlays and the full set of digital messages supported by CCTT.

c. The Ops workstation shall be fully integrated into the CCTT architecture and shall be configurable and assignable to a training exercise by the CCTT Master Control Console.

d. An Ops workstation shall be assigned a specific digital role and configurable by exercise.

e. The Ops Workstation shall also be capable of radio communications with any other properly configured simulation workstation or module.

4. Develop the capability for Mission Command Data Products to be distributed without having to be coupled to a CCTT software version. This requires removing the static tie of URNs to CCTT bumper numbers unit compositions and scenarios.

(DI-ADMIN-80925) Revisions to Existing Government Documents – CCTT

Requirements, Design, Interface and Test Documentation

3.2.3 Systems Engineering.

The contractor shall plan, document, implement, and control an integrated technical effort to develop all system modifications that meet the requirements of this PWS. The contractor shall perform the following System Engineering functions as follows, when applicable.

3.2.3.1 Systems Engineering Process.

The contractor shall apply a system engineering approach to produce the supportable and affordable design baselines that are verifiable from functional baselines for all CCTT training products, as described in this PWS. The contractor shall document, implement, control, and maintain a collection of technical plans, processes, and schedules necessary to guide the project toward accomplishment of its objectives. The contractor shall establish a System Engineering Management Plan (SEMP) that details the technical planning of the IMS and the relationship and activities associated with the development, integration and test of third party products. The SEMP shall be the planning document for all technical efforts and shall describe the tailored application of your system engineering process. The SEMP policies and procedures shall specify requirements for the planning, implementation, and control of product and process development and human/systems integration. The contractor’s policies and procedures shall address the following:

a. The application of the systems engineering process throughout the modified system life cycle.

b. The preparation and acceptance of the IMS.

c. The preparation and acceptance of data deliveries.

d. Monitoring and reporting technical progress of the program.

e. The preparation for, and conduct of, technical reviews.

f. The contents and maintenance of an integrated data library.

g. The implementation of a test and evaluation program.

h. The preparation for, and conduct of the creation of final software baselines for fielding.

(DI-SESS-81785A) Systems Engineering Management Plan (SEMP)

3.2.3.2 Requirements Analysis and Functional Allocation.

The contractor shall perform and document an analysis to verify that all requirements from the PWS and derived requirements are met and are traceable to each configuration item and subsequent lower level units of decomposition. The contractor shall develop a Requirements Traceability/Verification Matrix (RTVM) to document the results of this task. The contractor shall present an updated RTVM as a part of any System Requirements Review/System Functional Review (SRR/SFR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR) or In-Process Reviews (IPRs) regardless of the level of formality of the review. The contractor shall ensure that there is forward and backward traceability between all requirements (PWS, specifications, test procedures, and associated design documentation). The contractor shall ensure that the requirements are traceable to the lowest level practicable and that the sources of all requirements are identified (e.g., PWS, derived). The contractor shall integrate modifications to the RTVM created by third parties into the CCTT baseline RTVM and ensure that traceability and associated test materials are compliant with CCTT standards.

3.2.3.3 Rapid Prototyping.

The contractor shall provide for the planning, developing, and integrating effort necessary to conduct various types of rapid and quick reaction prototyping of systems and/or subsystems, as approved the by the Government. These efforts shall leverage existing software models and hardware infrastructure. Examples of rapid prototyping applications shall include, but not be limited to the following:

a. Simulation system functional enhancements.

b. Minor modifications and quick reaction fixes to systems.

c. System interoperability.

d. New technology insertion and integration.

e. Hardware and software upgrades associated with new capabilities.

f. Verification and Validation (V&V) of hardware and software upgrades.

g. Interoperability improvement efforts.

h. Database generation efforts that provide innovative capabilities.

i. Virtualization

3.2.3.4 Requirements Analysis and Concept Exploration.

The contractor shall continuously monitor and asses the overall CCTT System with the goal of identifying improvements to system efficiency, usability and maintainability. The contractor shall develop implementation approaches for selected improvements and conduct Analysis of Alternatives (AoA), new technology concept exploration, market surveys, feasibility studies, specifications, and generation of white papers that address, but are not be limited to the items below. The contractor shall document analyses.

The contractor shall perform analysis in the following areas:

a. Identification of enhancements and modifications to maintain currency with operational systems.

b. Identification of deficiencies and recommend solutions.

c. Maintaining interfaces with applicable weapon system contractors and appropriate government agencies to stay abreast of changes to the weapon systems.

d. Gathering of required data from the weapon system contractors or other sources.

e. Acquiring source design criteria and data necessary to accomplish analyses.

f. Addressing systems concurrency issues.

g. Interfacing with other contractors in pursuit of additional data.

h. Performing data collection and assessment of systems.

i. Planning and execution of experiments.

j. Recommending hardware and software tools which are anticipated to improve efficiency and effectiveness of the systems.

(DI-MISC-80711A) Scientific and Technical Reports

3.2.4 System Design.

The contractor shall perform trade studies; analyze technical impacts to system: functionality, lifecycle management, cybersecurity; and consider up front and long term costs prior to recommending any changes to the system design. The design concept shall incorporate an open systems approach which shall be based on an engineering and business strategy to choose specifications and standards adopted by industry standards bodies or de facto standards (set by the market place) for selected system interfaces, products, practices and tools. Selected designs and specifications shall be based on performance, cost, industry acceptance, long term availability and supportability, and upgrade potential.

3.2.4.1 Hardware Design and Acquisition.

The contractor shall identify, design, integrate, assemble, validate and test system hardware that satisfies the performance requirements provided by the Government. The contractor shall conduct market surveillance and market investigations in order to maximize the use of commercial and non-developmental items when required. The contractor shall, if necessary, manufacture or procure the hardware identified in the formal design reviews for the equipment in the CCTT PDSS Lab. Upon successful integration and test in the PDSS lab environment and formal inclusion in the CCTT baselines, the contractor shall field new or updated system hardware to CCTT sites.

3.2.4.2 Software Design and Development.

The contractor shall design and develop CCTT system software and firmware and shall follow industry best systems and software engineering practices. The contractor shall implement a software development process that enables flexibility and is focused on short iterations that deliver functional software. The software development tasks shall be broken down to their subparts so that they can be well defined, prioritized, planned and tracked and there is full transparency of the progress of efforts and continuous delivery of working software. The contractor shall facilitate cooperation and collaboration between the Government and developers.

The overall development process shall include the Government’s participation in the planning and prioritization of tasks. The contractor shall conduct market surveillance and market investigations, as approved by the Government, in order to maximize the use of open source software, commercial software and non-developmental software.

The design and development process shall incorporate features that:

a. Promote assessment of open source software products

b. Promote ease of operation

c. Promote ease of software maintenance

d. Promote ease and efficiency of software testing

e. Promote ease of future updates and modifications

f. Promote ease of data void work around

g. Facilitate reduction in the amount of required documentation.

The contractor shall analyze, design, code, integrate, install, and test enhanced or modified software to meet the requirements of the applicable development efforts and to support emerging requirements.

The contractor shall update existing System and Software Requirements Specification, Software Product Specification, Software Version Description and any other relevant documentation to reflect the incorporation of the modifications.

(DI-ADMIN-80925) Revisions to Existing Government Documents – CCTT Requirements, Design, Interface and Test Documentation

3.2.4.3 Cybersecurity Engineering.

Cybersecurity shall be part of the overarching systems engineering process. Cybersecurity shall be an integrated, core part of system design, rather than appended. The contractor, as the overarching lead integrator of CCTT capabilities, shall ensure that these actions are applied across all CCTT development activities, regardless of source. All cybersecurity designs shall be approved by the CCTT IPT.

The contractor shall conduct an assessment of the current PDSS representation of a CCTT fielded system environment and the supporting infrastructure for security vulnerabilities and weaknesses. The assessment shall include hardware, software, connected systems, and unconnected systems. The contractor shall continually evaluate the security of the system, both physical and logical, identifying exposures, and providing protective options for reducing security risk. The contractor shall identify assets to be protected, identify vulnerabilities, and develop a set of recommendations to eliminate or mitigate those threats.

3.2.5 System Test and Evaluation.

The contractor shall plan, coordinate, establish, and implement a comprehensive Test and Evaluation (T&E) program that shall be designed to verify that all system modifications meet the applicable technical and operational requirements. The contractor shall be the primary tester of all integrated CCTT baselines, to include newly developed capabilities developed by third parties. The contractor shall maintain, develop and manage test artifacts to perform regression and system level testing. When test artifacts are developed by third parties, the contractor shall validate and incorporate them into the CCTT test baseline. The contractor shall support the Government as the primary technical evaluator of all new capabilities, regardless of source.

3.2.5.1 T&E Deficiency Reporting System.

The contractor shall establish and implement a Deficiency Reporting System for the identification, tracking, and resolution of all hardware and software problems (including tactical subsystem).