Attachment 1 TACP CASS SW 145 SOW 20120627 DRAFT.pdf

FA8307-12-R-0014 TACP CASS Software v1.4.5 SOW

27 June 2012

FA8307-12-R-0014

Attachment 1

Tactical Air Control Party Modernization (TACP-M)

Close Air Support System (CASS)

Software Version 1.4.5

STATEMENT OF WORK (SOW)

Electronic Systems Center

Airborne Network Division (ESC/HNA)

Hanscom Air Force Base, Massachusetts 01731

DRAFT

This is a draft release intended to solicit comments from potential offerors and is subject to change.

TABLE OF CONTENTS

1 SCOPE

2 APPLICABLE DOCUMENTS

3 REQUIREMENTS

3.1 Software Development, Integration, Test, and Fielding Support

3.1.1 Operational Software Builds

3.1.1.1 CASS Software v1.4.5 Build 1

3.1.1.2 CASS Software v1.4.5 Build 2

3.1.2 Engineering Software Builds

3.1.3 Integration

3.1.3.1 Software Integration

3.1.3.2 Platform/System Integration

3.1.3.3 System Integration Laboratory

3.1.4 System Engineering

3.1.4.1 Technical Reviews

3.1.4.2 Interface Management

3.1.4.3 Software Engineering

3.1.4.4 Software Assurance

3.1.4.5 Human Systems Integration

3.1.4.6 Information Assurance

3.1.4.7 Configuration Management

3.1.4.8 Data Management

3.1.5 Test and Evaluation

3.1.5.1 Contractor Test

3.1.5.2 Support to Government Test

3.1.5.3 Integrated Test Team

3.1.5.4 Test Readiness Reviews

3.1.6 Technical Manuals

3.1.7 Training

3.1.7.1 Training Planning and Development

3.1.7.2 Operator and System Administrator Training

3.1.7.3 Computer-Based Training Courseware

3.1.8 Fielding Support

3.1.9 Exercise Support

3.1.10 Program Management

3.1.10.1 Project Management

3.1.10.2 Schedule Management

3.1.10.3 Budget Management

3.1.10.4 Earned Value Management

3.1.10.5 Travel Management

3.1.10.6 Risk Management

3.1.10.7 Subcontract Management

TABLE OF CONTENTS

3.1.10.8 Business Arrangements

3.1.10.9 Government Meetings and Reviews

3.1.10.10 Facility/Infrastructure/Personnel Management

3.1.10.11 Government Property Management/Asset Management

3.1.10.12 Transition

3.2 Interim Contractor Support/Contractor Logistics Support

3.2.1 Service Pack Releases

3.2.2 ICS/CLS Management

3.2.3 Training

3.2.4 Help Desk

3.2.5 Field and Exercise Support

3.3 Special Projects and Studies

APPENDIX A: CDRL ITEM LIST

APPENDIX B: ENTRY AND EXIT CRITERIA FOR TECHNICAL REVIEWS

APPENDIX C: ACRONYM LIST

STATEMENT OF WORK

1 SCOPE

This Statement of Work (SOW) sets forth the tasks for development and support of the United

States Air Force (USAF) Tactical Air Control Party (TACP) Close Air Support System (CASS)

Software Version 1.4.5. The TACP CASS Software v1.4.5 program is part of a USAF effort to modernize software for communications and command and control (C2) processing systems for multiple TACP echelons at the Air Support Operations Centers (ASOC), Tactical Operation

Centers (TOC), mounted operations, and dismounted operations.

The TACP CASS Software provides a standard communication and processing capability for

TACP ASOC and TOC operations at the Corps, the Division, the Brigade, and the Battalion and below echelons. The TACP CASS Software, hosted on a variety of computers that are integrated with TACP radios, computers, and antennas, a.k.a. Communications and Support (C&S) equipment, provides a complete communication and processing system across the TACP environment. The CASS Software v1.4.5 program enhances and maintains the digitally aided

Close Air Support (CAS) capability for TACP users to interoperate both with ground forces they support and aircraft conducting air operations, as well as with airspace C2 and Intelligence, Surveillance, and Reconnaissance (ISR) systems.

The efforts described in this SOW include the tasks necessary to (1) develop, integrate, test, and field operational software builds (a.k.a. releases), (2) develop engineering builds to support exercises, and (3) provide post-deployment Interim Contractor Support (ICS)/Contractor

Logistics Support (CLS), including release of service packs and patches, until the software is transitioned to a sustainer or follow-on developer. The CASS Software v1.4.5 effort will include all system and software engineering, integration, testing, training, documentation, support, and program management to field this next generation of CASS software on multiple platforms (e.g., mounted, dismounted) within the TACP environment.

2 APPLICABLE DOCUMENTS

The following documents form a part of this SOW to the extent specified herein.

Number/Date Title

Program Documents

HNA-12-085

27 Jun 12 (Draft)

TACP-M CASS v1.4.5 System Requirements Document (SRD)

964-9497-001C

14 Oct 11

Interface Control Document (ICD) for the Tactical Air Control Party

(TACP) Close Air Support System (CASS) Version 1.4.4

945-0261-001A

Rev-001A

16 Aug 10

Concept of Employment (ConEmp) for TACP CASS Feature

Human Machine Interface

1 Mar 12 TACP-M Security Classification Guide

Number/Date Title

DD254

22 Jun 12

TACP-M CASS Contract Security Classification Specification

TBD TACP-M Program Protection Plan (PPP)

Military Standards, Specifications, & Handbooks

MIL-STD-46855A

17 May 99

Human Engineering Program Process and Procedures

MIL-STD-881C

3 Oct 11

Work Breakdown Structures for Defense Materiel Items

MIL-HDBK-61A

7 Feb 01

Configuration Management Guidance

DoD and USAF Publications

DoDD 8500.1

24 Oct 02 (Certified as of 23 Apr 07)

Information Assurance (IA)

DoDI 8500.2

6 Feb 03

Information Assurance (IA) Implementation

DoDI 8510.01

28 Nov 07

DoD Information Assurance Certification and Accreditation Process

(DIACAP)

DoDI 8580.1

9 Jul 04

Information Assurance (IA) in the Defense Acquisition System

AFPD 33-2

3 Aug 11

Information Assurance (IA) Program

Technical Publications

TO 00-35D-54

1 Oct 09

USAF Deficiency Reporting, Investigation, and Resolution

TO-00-5-16

1 Jan 09

Software Managers and Users Manual for the USAF Automated

Computer Program Identification Number System (ACPINS)

Industry Publications

ANSI/EIA-649 (Rev B)

1 Apr 11

National Consensus Standard for Configuration Management

ANSI/EIA-748-A

1 Jun 98

Standard for Earned Value Management Systems

3 REQUIREMENTS

This section describes the requirements for the TACP CASS Software v1.4.5 development, integration, test, fielding, and support. Contract Data Requirements List (CDRL) deliverables are listed after each applicable SOW task and in Appendix A.

3.1 Software Development, Integration, Test, and Fielding Support

The Contractor shall develop, integrate, test, and support fielding of operational TACP CASS

Software v1.4.5 in accordance with the requirements stated in the TACP CASS Software v1.4.5

Systems Requirements Document (SRD) and this SOW. Upon contract award, the Government will provide the Contractor with the TACP CASS Software Version 1.4.4 object and source code and existing engineering code as Government Furnished Property (GFP), as described in the GFP list (Attachment 5 to the contract).

3.1.1 Operational Software Builds

The Contractor shall design, code, document, and integrate software to modify, add, or delete

CASS computer software configuration items (CSCIs) to meet the capabilities required by the

SRD. The Contractor shall deliver the operational CASS v1.4.5 software as two releases, herein referred to as Build 1 and Build 2.

CDRL A001 – Software Design Description (SDD)

CDRL A002 – Software Product Specification (SPS)

CDRL A003 – Software Version Description (SVD)

3.1.1.1 CASS Software v1.4.5 Build 1

The Contractor shall deliver Build 1 with all CASS Software legacy v1.4.4 capabilities and the additional capabilities defined in the SRD for Build 1.

a. The Contractor shall ensure discrepancies from outstanding TACP CASS test problem reports (TPRs) are not present in the delivered Build 1 software.

b. The Contractor shall include in Build 1 the radio firmware upgrades, aircraft

Operational Flight Program (OFP) interface upgrades, other external interface changes, and security updates that are available for integration into Build 1.

3.1.1.2 CASS Software v1.4.5 Build 2

The Contractor shall deliver Build 2 with all CASS Software v1.4.5 capabilities in accordance with the SRD.

a. The Contractor shall ensure discrepancies from outstanding TACP CASS Build 1

TPRs are not present in the delivered Build 2 software.

b. The Contractor shall include in Build 2 the radio firmware upgrades, aircraft OFP interface upgrades, other external interface changes, and security updates that are available for integration into Build 2.

3.1.2 Engineering Software Builds

The Contractor shall develop, document, demonstrate, and deliver engineering software builds to include Beta 1.4.5 software as well as non-operational “prototype software functionality” in support of Government exercises, risk reduction events (of future CASS capabilities and interfaces), and software certification/accreditation activities. The Contractor shall interact with the TACP-M Program Office and other cognizant Government program offices to define the prototype software interfaces and functionality. The expected engineering build content is described below. The Contractor shall describe the detailed, planned content of each engineering build in the Government-approved SDP (see paragraph 3.1.4.3).

a. The Contractor shall develop prototype software in support of reducing the risk associated with integration of TACP CASS operational software with the Small Diameter Bomb

II (SDB-II) being developed by the SDB-II Program Office. The SDB-II engineering software shall include both J11.x series message exchange and a prototype of the TACP CASS software user interface for control of the SDB-II weapon. The SDB-II engineering software shall provide support for the following SDB-II capabilities: (1) acceptance and control of the weapon, (2) periodic processing of Weapon In-Flight Track (WIFT) messages, (3) weapon cueing/re-targeting, (4) weapon abort/override, and (5) generation of a post-mission bomb report.

b. The Contractor shall develop prototype software in support of reducing the risk associated with integration of TACP CASS operational software with the Joint Automated Deep

Operations Coordination System (JADOCS) capabilities being developed by the U.S. Army.

CDRL A003 – Software Version Description (SVD)

3.1.3 Integration

The Contractor shall establish processes and facilities to integrate the TACP CASS Software

CSCIs and components and to integrate the software with TACP hardware platforms and external systems.

3.1.3.1 Software Integration

The Contractor shall integrate all TACP CASS CSCIs and software components for each operational software build to ensure all SRD requirements and TACP CASS Interface Control

Document (ICD) interfaces are met.

3.1.3.2 Platform/System Integration

The Contractor shall integrate each TACP CASS software v1.4.5 operational build on all TACP hardware platforms designated by the Government, except for those platforms integrated by

Naval Surface Warfare Center, Crane, IN (NSWC Crane), such as Gateway, Gateway Lite, and

Stryker. The Contractor shall support integration of each operational build on the TACP hardware platforms integrated by NSWC Crane. The Contractor shall integrate each TACP

CASS software v1.4.5 operational build with any new hardware required by the Government as upgrades to legacy platforms, including hardware to support the SIE capability. The Contractor shall integrate each operational build with aircraft OFPs, Army platforms, and adjacent systems currently used or interfaced with the TACP-M program, as specified in the SRD and ICD.

3.1.3.3 System Integration Laboratory

The Contractor shall establish a system integration laboratory (SIL) for development and contractor test of TACP CASS Software v1.4.5. The Contractor shall include in the SIL all necessary contractor-developed, commercial-off-the-shelf (COTS), and GFP hardware and software (see the GFP list, Attachment 5 to the contract) needed to integrate the CASS Software components. The Contractor shall fully document the SIL configuration (including hardware and software versions) and procedures so that Contractor and Government test activities can be coordinated across multiple baselines during development. At the end of development of the operational software builds, the Contractor shall deliver the entire contents of the SIL to the

Government, along with an updated version of the SIL documentation. The Government will formally inventory and baseline the SIL configuration, then return the SIL to the Contractor as

GFP to support the ICS/CLS of TACP CASS Software v1.4.5, if that option is exercised.

3.1.4 System Engineering

The Contractor shall perform all necessary system engineering activities to ensure the TACP

CASS software builds meet contractual requirements. The Contractor shall execute all systems engineering processes to a level of process proficiency equivalent with the Capability Maturity

Model Integration for Development (CMMI-DEV V1.2) Level 3 or higher.

3.1.4.1 Technical Reviews

For each operational software build, the Contractor shall conduct with the Government a

Software Requirements Review (SRR), Preliminary Design Review (PDR), and Critical Design

Review (CDR) in accordance with the entry and exit criteria in Appendix B.

CDRL A004 – Briefing Material

CDRL A005 – Report, Record of Meeting/Minutes

3.1.4.2 Interface Management

The Contractor shall define all external interfaces to the TACP CASS Software v1.4.5 in an

Interface Control Document (ICD).

CDRL A006 – Interface Control Document (ICD)

3.1.4.3 Software Engineering

The Contractor shall implement and utilize robust software engineering processes for design, development, integration engineering, test, accreditation, and fielding support of the TACP

CASS Software v1.4.5.

a. The Contractor shall provide an SDP that defines the detailed content of and the processes and organization to be used for each software build.

CDRL A007 – Software Development Plan (SDP)

b. The Contractor shall develop a software system design and architecture that meets the requirements of the SRD.

CDRL A008 – System/Subsystem Design Description (SSDD)

c. The Contractor shall define the allocated and derived requirements in a Software

Requirements Specification (SRS) for each CSCI and provide a trace of those requirements to the SRD with rationale.

CDRL A009 – Software Requirements Specification (SRS)

d. The Contractor shall define software metrics in the SDP and shall report those metrics at all technical and management reviews.

3.1.4.4 Software Assurance

The Contractor shall perform software assurance activities in accordance with the Government-approved SDP. The Contractor shall design and test each operational software build to assure protection of critical functionality and Critical Program Information (CPI), as identified in the

TACP-M Program Protection Plan (PPP). The Contractor shall evaluate software architectures, environments, designs, and code with respect to Common Vulnerabilities and Exposures (CVE), Common Attack Pattern Enumeration and Classification (CAPEC), and Common Weakness

Enumeration (CWE) as defined below:

CVE Used to identify and coordinate SW vulnerabilities that enable various types of attacks

CAPEC Used for the analysis of common destructive attack patterns

CWE Used to examine software architecture/design and source code for weaknesses

a. The Contractor shall protect and test/verify all COTS software and software of unknown pedigree (i.e., software from sources buried in the supply chain).

b. The Contractor shall implement counterfeit prevention measures and define the processes to be used. The Contractor shall mitigate any identified risk of counterfeit insertion during operations and maintenance and define the processes to be used.

c. The Contractor shall protect the development environment and will define procedures to keep the environment secure. The Contractor shall maintain a list of the development environment tools. The Contractor shall restrict access to the development environment and maintain a list of personnel with access.

d. The Contractor shall maintain a list of cleared U.S. citizens, as well as foreign nations/nationals, that have access to TACP CASS information and facilities. The Contractor shall identify where this access list be stored, and how often will it be updated.

e. The Contractor shall: (1) maintain a list of all subcontractors and vendors and what software they are supplying, (2) identify the subcontractors’ and vendors’ processes on how they protect the software from malicious functions (e.g., kill switch, code).

3.1.4.5 Human Systems Integration

The Contractor shall incorporate HSI principles and practices into the TACP CASS Software design, development, integration, test, and planning for support in accordance with

MIL-STD-46855A, as tailored by the Contractor in the Government-approved HSI Program

Plan. The Contractor shall meet the HMI requirements in the SRD and shall use the CASS

Software v1.4.4 user interface (reference v1.4.4 HMI CONEMP) as the starting point for the v1.4.5 human machine interface (HMI) design. The Contractor shall implement an HMI which is configurable/adaptable for each TACP echelon in accordance with the SRD, including a

Simplified Interface Environment (SIE) for TACP Dismounted operations.

CDRL A010 – Human Systems Integration Program Plan

a. The Contractor shall co-chair with the Government and conduct TACP CASS HSI

Working Group meetings, beginning no later than 60 days after contract award. The Contractor and Government will jointly develop an HSI Working Group charter to define the objectives, scope, membership, key stakeholders, authority, roles and responsibilities, schedule, and interactions with other program teams. The HSI Working Group will serve as the primary venue to identify and refine user requirements, resolve conflicts, develop and refine usability performance requirements, set usability goals, and verify the design approach taken by the

Contractor. The HSI Working Group will include TACP user and test representatives and will provide a forum for reviewing and assessing progress in the HMI design, development and test, and for controlling the CASS Software HMI evolution during development. The HSI Working

Group will review HMI feedback from the TACP users and test personnel and will propose HMI changes to address that feedback.

b. The Contractor shall develop and maintain an HMI Style Guide that provides HMI design guidelines and standards to the CASS Software developers. The Contractor shall ensure that the CASS Software HMI complies with the Government-approved HMI Style Guide.

CDRL A011 – Technical Report – Study/Service (HMI Style Guide)

c. The Contractor shall conduct functional and task analyses in accordance with

MIL-STD-46855A, paragraphs 4.2.1 and 4.2.1.3, within 120 days of contract award. The

Contractor shall use the analysis findings to define the user interface functional capabilities necessary to accomplish the mission and to define the discrete new or modified operator tasks necessary to execute the mission.

CDRL A012 – Human Systems Integration Report

d. The Contractor shall conduct iterative HMI prototyping and usability testing with

TACP user participation during the CASS Software design and development. The Contractor shall develop and evaluate user interface prototypes prior to CDR, beginning with low-fidelity prototypes and evolving to high-fidelity prototypes suitable for usability testing. The Contractor may use low-fidelity prototypes (e.g., non-interactive, static “screen shots”) to collect feedback from the users on early design concepts for the required user interface functions, including screen designs and control layouts. The Contractor shall develop high-fidelity prototypes prior to CDR to illustrate detailed design and behaviors of critical components of the user interface.

The Contractor shall develop a minimum of four user interface prototype iterations (with at least two high-fidelity iterations) and present the prototypes to the Government and user community for evaluation.

e. The Contractor shall allow for a minimum of three iterations of assessment and refinement of the proposed HMI design based on the results of at least two Government-conducted heuristic evaluations and at least one Government-witnessed usability evaluation with

TACP user representatives. The Contractor shall use operational scenarios prepared by the HSI

Working Group during usability evaluations.

f. The Contractor shall document the overall HMI display design philosophy and the detailed design of the user interface in an annex to the System/Subsystem Design Description

(SSDD). The Contractor shall update the HMI annex of the SSDD prior to each technical review and for HSI Working Group meetings whenever significant HMI changes have been proposed and approved.

CDRL A008 – System/Subsystem Design Description (SSDD)

g. The Contractor shall define HMI metrics for each CASS Software critical function that allows measurement of user actions, errors, and timeliness. The Contractor shall baseline the v1.4.4 software against the HMI metrics. The Contractor shall report the metrics for the v1.4.5 software vs. the v1.4.4 baseline at each HSI Working Group meeting, technical review, PMR, and test readiness review. The Contractor shall define HMI metrics for the following critical functions, as a minimum:

(1) Create the Joint Tactical Air Strike Request (JTASR) (DD Form 1972) and conduct dialog with ASOC over the Joint Air Request Net (JARN).

(2) Create the 9-Line and Transmit to CAS aircraft over the Tactical Data

Network (TDN).

(3) Plot ownship position at the center of a moving map that also contains tracks and battlefield geometries.

(4) Ingest Pocket Laser Range Finder (PLRF) data and associate automatically with ownship and target position location data.

(5) Provide critical alerts, e.g., Troops in Contact (TIC).

3.1.4.6 Information Assurance

The Contractor shall support the Government as required to meet the DoD Information

Assurance Certification and Accreditation Process (DIACAP) guidelines for information assurance as applicable to the TACP CASS Software v1.4.5 program, to assure all Information

Assurance (IA) requirements are fulfilled for all builds of TACP CASS Software v1.4.5 across all hardware configurations. The Contractor shall include and treat all DIACAP guidelines defined in DoDD 8500.1, DoDI 8500.2, DoDI 8510.01, DoDI 8580.1, and AFPD 33-2 as TACP

CASS IA requirements in the design, development, integration, testing, and fielding support of

TACP CASS deliverables.

a. The Contractor shall perform a TACP CASS DIACAP Security Assessment.

CDRL A013 – Scientific and Technical Reports (DIACAP Security Assessment)

b. The Contractor shall provide IA technical support to the Government to support

TACP CASS IA certifications and accreditations. The Contractor shall support Government IA

Certification and Accreditation (C&A) test activities with I-Flight, 46th Test Squadron (TS), Eglin AFB, FL. The Contractor shall support IA activities conducted by NSWC Crane for those

TACP-M hardware programs where NSWC Crane is the integrator.

c. The Contractor shall support and participate in monthly Government IA Working

Group meetings.

3.1.4.7 Configuration Management

The Contractor shall implement configuration management processes, procedures. and systems to ensure that all TACP CASS configurations are properly planned, identified, documented, maintained, and controlled. The Contractor should use MIL-HDBK-61A and ANSI/EIA-649B as guidance.

a. For each operational software build, the Contractor shall establish its functional baseline based on the SRD, its allocated baseline using the CSCI SRSs, and its product baseline using the SPSs. The Contractor shall serve as the configuration control authority for the allocated and product baseline candidates until Government baseline establishment upon Product

Configuration Audit (PCA) closure.

b. The Contractor shall support all Government TACP CASS Technical Review Board

(TRB) and Configuration Control Board (CCB) activities and meetings. The Government will establish its baselines using the TRB/CCB processes.

c. When directed by the Government, the Contractor shall prepare Engineering Change

Proposals (ECPs), Specification Change Notices (SCNs), Notices of Revision (NORs), and

Requests for Deviation (RFDs). The Contractor shall commence ECP-defined work only upon direction by the Government Contracting Officer.

CDRL A014 – Engineering Change Proposal (ECP)

CDRL A015 – Specification Change Notice (SCN)

CDRL A016 – Notice of Revision (NOR)

CDRL A017 – Request for Deviation (RFD)

d. The Contractor shall maintain and report the status of proposed changes and deviations to the configuration, as well as the implementation status of approved changes.

CDRL A018 – Configuration Status Accounting Information

e. The Contractor shall support a Government-conducted Functional Configuration Audit

(FCA) for each operational software build to verify each CSCI has achieved the requirements specified in the SRD and SRSs. The Contractor shall correct all discrepancies resulting from the

FCA.

f. The Contractor shall support a Government-conducted Physical Configuration Audit

(PCA) for each operational software build using a formal examination of the “as-built” configuration of each CSCI against its technical documentation to establish and verify the

CSCI’s product baseline. The Contractor shall correct all discrepancies resulting from the PCA.

3.1.4.8 Data Management

The Contractor shall manage all data generated on the contract to ensure it is complete, accurate, and up to date. The Contractor shall prepare and deliver data in accordance with the Contract

Data Requirements List (CDRL) (Exhibit A to the contract).

a. The Contractor shall list all data generated under this contract on the Data Accession

List (DAL), except for those items already listed in the CDRL.

CDRL A019 – Data Accession List (DAL)

b. The Contractor shall establish and maintain an on-line library, which shall be accessible via the Internet by Government and support contractor personnel designated by the

TACP-M Program Office. The Contractor shall post to the library all versions of TACP CASS technical documentation, contract data, and deliverables, including all CDRL deliverables and all data listed on the DAL. The Contractor shall segregate all management, financial, and other sensitive data and restrict its access to those individuals designated by the TACP-M Program

Office. The Contractor shall post an index of all data items contained within the library, showing a unique identification number for each data item and including its Government approval status.

The Contractor shall post the most recent version of each data item to the library within 24 hours after its publication.

3.1.5 Test and Evaluation

The Contractor shall implement a comprehensive test and evaluation program that includes contractor tests, support to Government tests, participation in and support to the TACP CASS

Integrated Test Team (ITT), and Test Readiness Reviews (TRRs).

3.1.5.1 Contractor Test

The Contractor shall conduct contractor test (CT) for each operational software build in accordance with Section 4 of the SRD, to verify TACP CASS Software compliance with the

SRD, including unit tests, system tests, stress tests, load tests, HMI tests, network tests, database tests, disk input/output tests, memory tests, and test-to-break events. The Contractor shall notify the Government no later than two weeks prior to each test event so that Government personnel may attend as witnesses or observers.

a. The Contractor shall utilize the SIL (see paragraph 3.1.3.2) as the primary facility to conduct CT. The Contractor may request use of Government test facilities for CT. The

Government will notify the Contractor if those requested facilities are available.

b. The Contractor shall conduct end-to-end testing to verify software/hardware/firmware integration at the component and system level, including all TACP platforms and aircraft OFPs.

c. The Contractor shall dry-run all testing that will be performed by the Government (see paragraph 3.1.5.2). The Contractor shall include protocol testing (e.g., VMF and Link-16) and interface testing in the dry runs.

d. The Contractor shall develop test plans test descriptions for the execution of all formal

CT, formal contractor integration, and fielding test activities. The Contractor shall report the results of all CT formal test events.

e. The Contractor shall provide the Government with written certification that requirements for each build were successfully tested during CT. The Contractor shall identify, document, and track all problems and discrepancies identified and discovered during CT in the

Software Test Report (STR). The Contractor shall propose corrective action for each problem/discrepancy, to include a recommendation of whether corrective action should be required prior to delivery. The Contractor shall update the STR to include CT regression test results.

CDRL A020 – Software Test Plan (STP)

CDRL A021 – Software Test Description (STD)

CDRL A022 – Software Test Report (STR)

3.1.5.2 Support to Government Test

The Contractor shall support TACP CASS software Government testing activities at

Government-designated test facilities and locations to include Developmental Testing (DT), IA testing, certification testing, Air Force System Interoperability Test (AFSIT), Joint

Interoperability Test Command (JITC) testing, Army Central Technical Support Facility (CTSF) testing/Army Interoperability Certification (AIC) testing, Operational Testing (OT)/Force

Development Evaluation (FDE), and other Government testing as required, including all required regression testing. The Contractor shall provide the following support: (1) delivery of the

System Install Disk for Government tests, (2) install and check-out of the software, (3) support of the performance of all tests, (4) correction of deficiencies in TPRs identified by the

Government, and (5) support of regression tests to verify deficiencies have been corrected.

3.1.5.3 Integrated Test Team

The Contractor shall participate in and support the Government-chartered ITT established to assist the Government TACP CASS Software Program Manager (PM) in planning, managing, and executing all CASS Software testing. The TACP CASS ITT acts as a forum for all CASS test-related activities. The CASS ITT assists the PM in establishing test objectives and evaluation baselines; defining organizational responsibilities; estimating test costs and schedules;

conducting Test Readiness Reviews (TRRs) and identifying necessary test resources and sites for

CT and support to certification testing, DT, and OT/FDE.

a. The Contractor shall support ITT teleconferences bi-weekly or as required. The

Contractor shall participate in and support TACP CASS Combined Test Force (CTF) meetings and activities monthly or as required.

b. The Contractor shall participate in and support TACP CASS Deficiency Review Board

(DRB) meetings. The DRB will grade deficiencies in accordance with TO 00-35D-54.

3.1.5.4 Test Readiness Reviews

The Contractor shall conduct a TRR prior to CT for each operational software build, to demonstrate readiness for CT. The Contractor shall conduct a TRR at the conclusion of CT for each operational software build, to demonstrate readiness for Government test in accordance with the entry and exit criteria in Appendix B. The Contractor shall support Government TRRs as required.

3.1.6 Technical Manuals

The Contractor shall develop a Software User Manual (SUM), a System Administration and

Maintenance Manual (SAMM), a Software Programmer’s Guide (SPG), and a Quick Reference

Guide (QRG), updated for each operational software build.

CDRL A023 – Software User Manual (SUM)

CDRL A024 – Technical Report – Study/Service (SAMM)

CDRL A025 – Software Programmer’s Guide (SPG)

CDRL A026 – Technical Report – Study/Service (QRG)

3.1.7 Training

The Contractor shall plan for and execute a comprehensive training program to ensure all TACP

CASS operators and administrators are properly trained.

3.1.7.1 Training Planning and Development

The Contractor shall plan for and develop training for each operational software build. The

Contractor shall establish a Training Integrated Product Team (TIPT) with Government participation to: (1) support planning for training events, (2) support fielded system capability and training events, and (3) review TACP CASS Software documentation and training material.

The Contractor shall conduct the initial TIPT meeting within 60 days after contract award.

a. The Contractor shall develop/update operator and system administrator training package(s) for each operational software build. Operator training is intended to be focused on specific system and software component changes that occur between software versions.

b. The Contractor shall provide interim training packages to support pre-release software user evaluation and to address equipment upgrades.

c. The Contractor shall share technical documentation with the Joint Terminal Control

Training and Rehearsal System (JTCTRS) and Joint Theater Air Ground Simulation System

(JTAGSS) program office to ensure the software build(s) will interface and interoperate with the

Joint Terminal Attack Controller (JTAC) and ASOC training simulation systems.

CDRL A027 – Training Program Development and Management Plan

CDRL A028 – Training Materials

3.1.7.2 Operator and System Administrator Training

The Contractor shall conduct CONUS Type I and refresher in-plant or Mobile Training Team

(MTT) operator and system administrator training for each new build/release of the software at least twice per month. The Contractor shall provide OCONUS Type I and refresher Mobile

Training Team (MTT) operator and system administrator training for each new build/release of the software twice per year.

a. The Contractor shall provide MTT support and over-the-shoulder operator and system administrator training at test locations prior to Government DT and OT/FDE, and during military exercises.

b. The Contractor shall implement training progress reports including data collected from student critiques, student surveys, and collected student demographic information. The data collected in the student critique, student survey, and the metrics in the composite training analysis report will be determined at the first TIPT meeting.

CDRL A029 – Technical Report – Study/Service (Composite Training Analysis Report)

3.1.7.3 Computer-Based Training Courseware

The Contractor shall develop operator TACP CASS Software Computer-Based Training (CBT) courseware. The Contractor shall develop Gateway CBT to address all interfaces outlined in the

TACP CASS ICD.

CDRL A028 – Training Materials

3.1.8 Fielding Support

The Contractor shall support the fielding of each TACP CASS v1.4.5 operational software build.

a. For each operational software build, the Contractor shall prepare: (1) a Source Code

Disk with all developed, commented source code and (2) a Software Application Disk with the executable software code and install application. For each operational software build, the

Contractor shall prepare a System Install Disk, containing the executable software, install application, platform drivers, third party software, and security software, for all TACP hardware platforms designated by the Government, except for those platforms integrated by NSWC Crane, such as Gateway, Gateway Lite, and Stryker, where NSWC Crane will generate the System

Install Disk.

b. When directed by the Government, the Contractor shall support the fielding of TACP

CASS versions and shall travel throughout the CONUS and to military facilities overseas to ensure a smooth transition and provide on-site support. The Contractor shall provide reports and logs of fielding events, to include TACP CASS configurations identified at fielding sites.

3.1.9 Exercise Support

The Contractor shall provide TACP CASS Software engineering software builds as stated in paragraph 3.1.2 to support military exercises. Four exercises are expected to occur in each

12-month period. The Contractor shall utilize the MTT during military exercises to train TACP

CASS operators. The Contractor shall assist in assembling equipment at training/exercise sites to ensure proper configuration. The Contractor shall ensure interoperability of CASS Software at exercise locations.

3.1.10 Program Management

The Contractor shall manage the CASS Software v1.4.5 program to meet all contract requirements.

3.1.10.1 Project Management

The Contractor shall establish and maintain project management processes and shall report program progress each month. The Contractor shall host or conduct via teleconference quarterly

Program Management Reviews (PMRs) with the Government.

CDRL A030 – Program Progress Report (PPR)

CDRL A004 – Briefing Materials

a. The Contractor shall identify program performance metrics that provide the

Government with visibility into the Contractor's management and technical performance, including subcontractor and management performance data. The Contractor shall baseline the program performance metrics and report the current status of the metrics in Program Progress

Reports, at PMRs, and during Government management visits.

b. The Contractor shall utilize for management reporting the approved Contract Work

Breakdown Structure (CWBS) (Attachment 11 to the contract).

c. The Contractor shall conduct a Post Award Conference (PAC) with the Government within 30 days after contract award. The Contractor shall coordinate the PAC agenda with the

Government Contracting Officer, Program Manager, and cognizant Defense Contract

Management Agency (DCMA) representative.

3.1.10.2 Schedule Management

The Contractor shall develop and maintain an Integrated Master Schedule (IMS) that is structured according to the CWBS. The Contractor shall report schedule status measured against the Government-approved IMS baseline on a monthly basis. The Contractor shall not change, revise, or alter the Government-approved IMS baseline, but may recommend changes, revisions, and alterations to the Government Program Manager.

CDRL A031 – Integrated Master Schedule (IMS)

3.1.10.3 Budget Management

The Contractor shall implement and maintain processes for budgeting, cost control, and cost reporting. The Contractor shall report contract funds status each month.

CDRL A032 – Contract Funds Status Report (CFSR)

3.1.10.4 Earned Value Management

The Contractor shall implement and report earned value for the CASS Software v1.4.5 program in accordance with ANSI/EIA-748-A. The Contractor shall conduct an Integrated Baseline

Review (IBR) within 90 days after contract award and when directed by the Government. The

Contractor shall establish the Performance Measurement Baseline (PMB) following Government approval of the IBR.

CDRL A033 – Contract Performance Report (CPR)

CDRL A004 – Briefing Materials

CDRL A005 – Report, Record of Meeting/Minutes

3.1.10.5 Travel Management

Travel to Government and Contractor sites and facilities in CONUS and OCONUS is required in performance of this SOW. The Contractor shall manage all travel for Contractor personnel.

a. The Contractor shall obtain Government TACP-M Program Office approval of all travel prior to the start of each trip. The Contractor shall list and document the results of each month’s travel in the PPR.

b. The Contractor shall utilize the DoD Foreign Clearance Guide for all travel to any

OCONUS locations (https://www.fcg.pentagon.mil/).

3.1.10.6 Risk Management

The Contractor shall utilize risk management processes and procedures that: (1) identify major technical risks and assess the cost and schedule impact of each risk, (2) assess the probability of occurrence and severity of impact of each identified risk, (3) prioritize each identified risk,

(4) identify a risk mitigation strategy and associated mitigation “triggers” for each identified risk, and (5) monitor and report the status and trend of each identified risk and mitigation “trigger.”

The Contractor shall coordinate risk management actions with the Government TACP-M

Program Office. The Contractor shall present the status of each risk at PMRs, technical reviews, and other meetings.

3.1.10.7 Subcontract Management

The Contractor shall manage all subcontract activities and provide the Government TACP-M

Program Office with visibility into subcontractor performance. The Contractor shall establish an overall subcontract management approach to monitor subcontractor cost, schedule, and technical performance progress. The Contractor shall flow down all applicable contract requirements to subcontractors and vendors.

3.1.10.8 Business Arrangements

The Contractor shall establish appropriate business arrangements (e.g., associate contractor agreements) with the TACP CASS Software v1.4.4 ICS contractor and other companies to facilitate transfer of information and cooperation for CASS Software development and support.

The Contractor shall provide a copy of all company-to-company agreements to the Government

Contracting Officer.

3.1.10.9 Government Meetings and Reviews

The Contractor shall support the following Government briefings, meetings, and reviews:

Government PMRs (quarterly and as required)

Management IPT Telecons (weekly)

IPT Meetings (as required)

Technical Interchange Meetings (TIMs) (as required)

Interface Control Working Group (ICWG) Meetings (as required)

CCBs (for each software build baseline and as required) https://www.fcg.pentagon.mil/

3.1.10.10 Facility/Infrastructure/Personnel Management

The Contractor shall provide personnel and properly equipped facilities and infrastructure to perform the management, engineering, development, test, fielding support tasks required by the contract and this SOW.

a. The Contractor shall ensure the personnel, facilities, and infrastructure meet the contract security requirements as specified in the TACP CASS contract DD Form 254, DoD

Contract Security Classification Specification (Attachment 4 to the contract).

b. The Contractor shall provide certification that it has a current, valid facility security clearance issued by the Defense Security Service (DSS) that provides them with a facility and safeguarding level of SECRET. The Contractor shall ensure its personnel have a security clearance of SECRET or higher.

3.1.10.11 Government Property Management/Asset Management

The Contractor shall implement a Government property management system to manage, monitor, and report the status of all GFP provided under this contract. The Contractor shall report the status of all GFP monthly.

CDRL A034 – Status of Government Furnished Equipment (GFE) Report

3.1.10.12 Transition

The Contractor shall plan for transition of TACP CASS Software v1.4.5 to a follow-on sustainer or developer, either Government or contractor. The Contractor shall implement the transition plan upon Government direction.

CDRL A035 – Software Transition Plan (STrP)

3.2 Interim Contractor Support/Contractor Logistics Support

Upon delivery of v1.4.5, the Contractor shall perform ICS and CLS for CASS Software v1.4.5 including service pack releases, ICS/CLS management, training, help desk support, and field and exercise support, security pack updates, help desk assistance, test and test support for service packs and patches, training materials modifications, training assistance, and logistics.

3.2.1 Service Pack Releases

The Contractor shall periodically release service packs for TACP CASS Software v1.4.5. Service packs may include security updates, code maintenance, bug fixes, patches, interface software updates as well as OFP updates and integration of any backwards compatibility software packages generated by the development of future TACP CASS Software versions.

a. The Contractor shall conduct an SRR, PDR, CDR, and TRR for each service pack.

The Contractor shall conduct CT and support Government DT/OT for each service pack.

CDRL A004 – Briefing Material

CDRL A005 – Report, Record of Meeting/Minutes

CDRL A020 – Software Test Plan (STP)

CDRL A021 – Software Test Description (STD)

CDRL A022 – Software Test Report (STR)

b. The Contractor shall update all CASS Software configuration documentation, SIL documentation, security documentation, technical manuals, training documentation and courseware, and software code for each service pack release.

CDRL A001 – Software Design Description (SDD)

CDRL A003 – Software Version Description (SVD)

CDRL A006 – Interface Control Document (ICD)

CDRL A008 – System/Subsystem Design Description (SSDD)

CDRL A009 – Software Requirements Specification (SRS)

CDRL A011 – Technical Report – Study/Service (HMI Style Guide)

CDRL A013 – Scientific and Technical Reports (DIACAP Security Assessment)

CDRL A018 – Configuration Status Accounting Information

CDRL A019 – Data Accession List (DAL)

CDRL A023 – Software User Manual (SUM)

CDRL A024 – Technical Report – Study/Service (SAMM)

CDRL A025 – Software Programmer’s Guide (SPG)

CDRL A026 – Technical Report – Study/Service (QRG)

CDRL A028 – Training Materials

3.2.2 ICS/CLS Management

Under ICS/CLS, the Contractor shall continue the management tasks performed during development in accordance with SOW section 3.1.10.

CDRL A030 – Program Progress Report (PPR)

CDRL A031 – Integrated Master Schedule (IMS)

CDRL A032 – Contract Funds Status Report (CFSR)

CDRL A033 – Contract Performance Report (CPR)

CDRL A034 – Status of Government Furnished Equipment (GFE) Report

CDRL A035 – Software Transition Plan (STrP)

3.2.3 Training

The Contractor shall implement refresher training that encompasses primarily those features that are new or have changed since the previous release.

a. The Contractor shall provide CONUS Type I and refresher in-plant or MTT operator and system administrator training for each new release of the software twice per month. The

Contractor shall provide OCONUS Type I and refresher MTT operator and system administrator training for each new release of the software twice per year.

b. The Contractor shall provide MTT support and over-the-shoulder operator and system administrator training at unit locations prior to Government DT and OT/FDE, and during military exercises.

CDRL A029 – Technical Report – Study/Service (Composite Training Analysis Report)

3.2.4 Help Desk

The Contractor shall provide Tier-2 help desk support and maintain 24-hour telephone and email support for fielded systems for assisting users and resolving issues related to TACP CASS

Software versions. The 24-hour help desk shall provide two (2) hour response time twenty four

(24) hours per days seven (7) days a week. The Contractor shall log all help desk activities and record associated metrics.

3.2.5 Field and Exercise Support

The Contractor shall support the maintenance of fielded TACP CASS Software v1.4.5 to include builds, service packs, emergency fixes, security fixes, and patch releases. The Contractor shall maintain, test, and support interoperability between existing software versions to ensure compatibility with external software and hardware interfaces.

a. When directed by the Government, the Contractor shall support the fielding of TACP

CASS versions and shall travel throughout the CONUS and to military facilities overseas to ensure a smooth transition and provide on-site support. The Contractor shall provide: (1) reports and logs of fielding events, and (2) document TACP CASS configurations discovered at fielding sites.

b. The Contractor shall provide TACP CASS Software interim/maintenance release candidates to support military exercises. Four exercises are expected to occur in each 12-month period. The Contractor shall utilize the MTT during military exercises to train TACP CASS operators. The Contractor shall assist in assembling equipment at training/exercise sites to ensure proper configuration. The Contractor shall ensure interoperability of CASS Software at exercise locations.

3.3 Special Projects and Studies

The Contractor shall perform special projects and studies as directed by the Government.

CDRL A036 – Technical Report – Study/Service

APPENDIX A: CDRL ITEM LIST

Seq. No. DID Title

A001 DI-IPSC-81435A/T Software Design Description (SDD)

A002 DI-IPSC-81441A/T Software Product Specification (SPS)

A003 DI-IPSC-81442A/T Software Version Description (SVD)

A004 DI-MGMT-81605/T Briefing Material

A005 DI-ADMN-81505/T Report, Record of Meeting/Minutes

A006 DI-CMAN-81248A/T Interface Control Document (ICD)

A007 DI-IPSC-81427A/T Software Development Plan (SDP)

A008 DI-IPSC-81432A/T System/Subsystem Design Description (SSDD)

A009 DI-IPSC-81433A/T Software Requirements Specification (SRS)

A010 DI-HFAC-81743A/T Human Systems Integration Program Plan

A011 DI-MISC-80508B/T Technical Report – Study/Service (HMI Style Guide)

A012 DI-HFAC-81833/T Human Systems Integration Report

A013 DI-MISC-80711A/T Scientific and Technical Reports (DIACAP Security Assessment)

A014 DI-CMAN-80639C/T Engineering Change Proposal (ECP)

A015 DI-CMAN-80643C/T Specification Change Notice (SCN)

A016 DI-CMAN-80642C/T Notice of Revision (NOR)

A017 DI-CMAN-80640C/T Request for Deviation (RFD)

A018 DI-CMAN-81253A/T Configuration Status Accounting Information

A019 DI-MGMT-81453A/T Data Accession List (DAL)

A020 DI-IPSC-81438A/T Software Test Plan (STP)

A021 DI-IPSC-81439A/T Software Test Description (STD)

A022 DI-IPSC-81440A/T Software Test Report (STR)

A023 DI-IPSC-81443A/T Software User Manual (SUM)

A024 DI-MISC-80508B/T Technical Report – Study/Service (System Administration &

Maintenance Manual)

A025 DI-IPSC-81633/T Software Programmer’s Guide (SPG)

A026 DI-MISC-80508B/T Technical Report – Study/Service (Quick Reference Guide)

A027 DI-ILSS-81070/T Training Program Development and Management Plan

A028 DI-ILSS-80872/T Training Materials

Seq. No. DID Title

A029 DI-MISC-80508B/T Technical Report – Study/Service (Composite Training Analysis

Report)

A030 DI-MGMT-80555A/T Program Progress Report

A031 DI-MGMT-81650/T Integrated Master Schedule (IMS)

A032 DI-MGMT-81468/T Contract Funds Status Report (CFSR)

A033 DI-MGMT-81466A/T Contract Performance Report (CPR)

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

A035 DI-IPSC-81429A/T Software Transition Plan (STrP)

A036 DI-MISC-80508B/T Technical Report – Study/Service

APPENDIX B: ENTRY AND EXIT CRITERIA FOR TECHNICAL REVIEWS

The table below lists the minimum entry and exit criteria for TACP CASS technical reviews.

Review Entry Criteria Exit Criteria SRR SDP submitted for approval

Draft SSDD submitted for review

Draft…