TACP_CASS_145_Draft_RFP_Attachments_20121205.pdf

FA8307-12-R-0014

Tactical Air Control Party Modernization (TACP-M) Close Air Support System (CASS)

Software Version 1.4.5

RFP ATTACHMENTS

DRAFT

FA8307-12-R-0014 TACP CASS Software v1.4.5 CDRL 15 October 2012

Exhibit A

CONTRACT DATA REQUIREMENTS LIST (CDRL)

15 October 2012 v2

Air Force Life Cycle Management Center Battle Management Directorate

Theater Battle Control Division (AFLCMC/HBD) Hanscom Air Force Base, Massachusetts 01731

TABLE OF CONTENTS

General Instructions

Detailed Explanation of DD Form 1423

Mailing Addresses

Index of CDRL Items

DD Forms 1423

GENERAL INSTRUCTIONS

1. The CDRL identifies the data deliverable for the related Contract Line Item Numbers (CLINs) pursuant to the tasks defined in the Statement of Work (SOW). The Contractor shall deliver all data items in accordance with the SOW, paragraph 3.1.4.8b, by posting the data to the program’s on-line library, with email notification to the TACP CASS Data Manager and the Contracting Officer.

2. Contractually binding instructions for data content and format preparation are in Block 10, “Preparation Instructions,” of the applicable Data Item Description (DID), and permit the easy segregation of content related to specific efforts. Tailored instructions are on the CDRL or backup sheets. In such cases, “/T” (tailored) is suffixed to the DID number. The Contractor shall not deviate from the requirements of the DID, tailored or untailored, without receiving prior approval of the Government Contracting Officer. If Contractor format is permitted, all DID content must be addressed, unless the DID content is specifically tailored.

a. The Contractor shall submit data electronically in Microsoft Office compatible format, e.g., Microsoft Word, Microsoft Excel, Microsoft PowerPoint, Microsoft Project, etc., and when requested by the Government, in Adobe PDF format.

b. The Contractor shall deliver data not originally created in Microsoft Office format in its source file format when directed by the Government.

3. The CDRL was prepared using the following documents for guidance and information:

a. DoD 5010.12-M, Procedures for the Acquisition and Management of Technical Data, dated May 1993.

b. DoD Directive 5230.24, Distribution Statements of Technical Documents.

4. Unless otherwise specified, the submittal dates for the CDRL items are based on the effective date of the contract. Submittal dates falling on non-working days (Saturday, Sunday, legal holidays) shall be construed to mean the first working day following such non-working days. All submittal time periods (e.g., “60 days after contract award (DAC),” “30 days prior (DP) to test,” “10 days after (DA) FCA,” etc.) shall be calendar counted days. Data that is dependent on events that may not occur during the performance of the contract will be submitted on an “as required” basis.

5. Unless otherwise specified, the submittal date is the date the data item is required at the office specified in Block 6 of the CDRL. Distribution to other recipients of the data shall be made on or about the same date. In the event data is delivered electronically receipt confirmation is required and may be made on line.

6. The Data Transmittal Form (DTF) shall contain the contract number, the CLIN, the CDRL sequence number, the date of transmittal, and the Contractor’s reference number. The DTF will identify the data by title and document number, as well as the type of submission (e.g., draft, final, resubmission of draft, change pages, etc.). The DTF shall also include a list showing addressees, distributions made, and number of copies distributed. One information copy of all DTFs shall be forwarded to AFLCMC/HBDC (TACP CASS Data Manager) and AFLCMC/HBDK (TACP CASS Contracting Officer). Receipt acknowledgement by means of endorsement and return of the DTF to the Contractor is required for classified documents only.

7. All correspondence relating to data items shall reference the contract number, CLIN, CDRL sequence number, and DID number.

8. Unless otherwise specified, an “A” in Block 8 of the DD Form1423 indicates written approval by the Contracting Officer shall be provided before distribution of the final data. The Government will respond within 45 days of receipt of the data, unless a different time period is specified on the DD1423. (NOTE: ECPs, RFDs, and NORs are exempt from this approval cycle.) However, Government failure to respond to the Contractor within this 45-day period does not constitute Government approval of data deliveries and does not constitute approval of the initiation of an effort. Government written responses for data items submitted for approval will be provided in one of two categories only: (1) Approved as written; or (2) Disapproved with comments.

a. In the event that a data submission is disapproved, the Contracting Officer will advise the Contractor of the reason(s) for disapproval and provide any specific comments. Disapproved data items shall be revised to address/include the comments, and shall be resubmitted (or change pages provided) to the Government within 30 days. These re-submittals, or change pages, shall not be regarded as subsequent submittals as specified in Block 13 of the DD1423, unless the next submittal of the CDRL item is scheduled such that this would be a duplication of effort. (For example, an item submitted 90 DP to test, which is disapproved and is due again 30 DP to test, would be revised to address/include the comments in the next scheduled submittal.) The Government will review the changes the Contractor has made to the data addressing Government comments/disapproval and will limit subsequent review(s) to address only those changes (with the exception of those instances where comments are incorporated in the next scheduled submittal).

b. The Government will normally provide a comments resolution matrix (CRM) that lists each comment. When re-submitting a data item, the Contractor shall indicate on the CRM whether each comment was incorporated and if not, the rationale for not incorporating the comment. For complex documents and comments, the Government may require that the Contractor conduct a telecon and/or submit sample change pages prior to re-submittal of the document, to clarify and set expectations for the data item re-submittal and provide higher confidence that the re-submitted data item will be approved.

c. Even in the absence of an “A” in Block 8 of the DD1423, the Government has the inherent right to approve/disapprove any data submittal which does not meet the contractual requirements of the DID, tailored or untailored.

9. The Contractor will take care not to unnecessarily duplicate data previously procured by the Government, except to provide required copies to newly established recipients under this contract. Instances of unnecessary duplications should be identified to the TACP CASS Data Manager. The Contractor is encouraged to recommend deletions, additions, substitutions, consolidations, and use of existing Contractor formats for data when such actions will aid the Government in obtaining minimum essential data in a timely and cost effective manner.

10. CDRL items that have codes DD, DS, SD or SS in Block 7 of the DD1423 require the processing of a DD Form 250, Material Inspection and Receiving Report. If none of these codes are present in Block 7 then a DD Form 250 is not required for that data item. The code letter “S” indicates “Source” and refers to the Contractor’s facility; the code letter “D” indicates “Destination.” The first code letter indicates the point of preliminary inspection (for count, style, format, legibility, reproducibility, etc.). The second code letter indicates the point of formal acceptance (on DD Form 250). In cases where draft copies are required, the draft copies shall be provided by a DTF. A DD250 is required only for transmittal of the final copies to the office identified in Block 6 of the DD1423. In addition a final DD250 shall be provided at the completion of all final CDRL deliveries against applicable CLINs. Send the final DD250 directly to the TACP CASS Contracting Officer with a copy to the TACP CASS Data Manager.

11. Change pages are normally acceptable for revisions to data items. The Government will notify the Contractor if the entire revised data item must be submitted. Requirements for periodic revisions to data, where no changes have occurred since the date of last submission, may be satisfied by a DTF stating that “No changes have occurred since the last submission.”

Requirements for submittal of data “if changed,” where no change has occurred prior to the submittal requirement, may be satisfied by a DTF stating that “No change has been made to the data to date.” In such cases, the Contractor will identify the data in question, and the reporting period.

12. The Contractor shall establish a document revision scheme to assure proper configuration control and clear traceability between the revision approved by the Government and the revision found on the document, so there is no question which is the baseline version of the document. The Contractor shall coordinate the revision scheme with the TACP CASS Data Manager prior to submittal of any data items.

13. Distribution statement requirements are specified in Block 9 of the DD1423. The code letter corresponds to the distribution statement to be marked on the technical data item by the Contractor. See Block 9 in the detailed DD1423 instructions.

14. The Contractor will be notified in writing of any of the following changes to Block 14 of the CDRL: (a) place of delivery, (b) technical office symbol, (c) increase or decrease in addressees, or (d) increase or decrease in the number of copies specified for any addressee.

The written notification will include a redlined CDRL. The Contractor may use this written notification as its authority until the issuance of a contract modification incorporating the CDRL change. There is no contract price change for changes (a) or (b). There is no contract price change for changes (c) or (d), provided that either type of increase or decrease for an individual CDRL item is not greater than 50% of what was initially specified.

15. Questions regarding preparation and content of the CDRL items may be directed to the AFLCMC/HBDC TACP CASS Data Manager.

DETAILED EXPLANATION OF DD FORM 1423

Block 1: Data Item Number: Sequential number relating to the CLIN, Block A, under which the data will be delivered.

Block 2: Title of Data Item: The title of the DID cited in Block 4.

Block 3: Subtitle: Subtitle of data item for further definition of data item (optional entry).

Block 4: Authority: The DID number that defines data content and format requirements for the data item listed in Block 2. All MIL-STDs or MIL-Specs referenced in a data item description are for guidance only, unless otherwise directed in the DD1423.

Block 5: Contract Reference: The specific paragraph number(s) of the SOW, specification, standard, or other applicable document that contain the tasking for generating the data requirement.

Block 6: Requiring Office: The technical office responsible for ensuring adequacy of the data item.

Block 7: DD 250 Req: The applicable code, designating the requirement for inspection and acceptance of the data item:

DD250 REQ CODE INSPECTION ACCEPTANCE

SS (1) (2)

DD (3) (4)

SD (1) (4)

DS (3) (5)

LT (6) (7)

NO (8) (8)

XX (9) (9)

(1) Inspection at source.

(2) Acceptance at source.

(3) No inspection performed at source; final inspection performed at destination.

(4) Acceptance at destination.

(5) Acceptance at source; acceptance based on written approval from the Contracting Officer.

(6) Letter of transmittal only.

(7) As specified in Block 16 of the DD1423 or the applicable Data CLIN.

(8) No inspection or acceptance required; no DD250 or LT required.

(9) Inspection and acceptance requirements specified elsewhere in the contract.

Block 8: App Code: Data items requiring specific advance written approval before distribution of the final data item will have “A” in this block. If approval of the data item is not required, an “N/A” will be in this block.

Block 9: Distribution Statement Required: The code letter that corresponds to the distribution statement to be marked on the technical data item by the contractor as shown below. Contact the TACP CASS Data Manager to coordinate the exact distribution statement to be affixed to the data item.

CODE DISTRIBUTION STATEMENT

A Approved for public release; distribution is unlimited.

B Distribution authorized to U.S. Government agencies only (reason) (date). Other requests for this document shall be referred to (requiring office).

C Distribution authorized to U.S. Government agencies and their contractors

(reason) (date). Other requests for this document shall be referred to (requiring office).

D Distribution authorized to the Departments of Defense (DoD) and DoD Contractors only (reason) (date). Other requests for this document shall be referred to (requiring office).

E Distribution authorized to DoD components only (reason) (date). Other requests shall be referred to (requiring office).

F Further dissemination only as directed by (requiring office) (date) or higher DoD authority.

X Distribution authorized to U.S. Government agencies and private individuals or enterprises eligible to obtain export-controlled technical data IAW regulations implementing 10 U.S.C. 140c (date). Other requests shall be referred to (requiring office).

N/A Not applicable. No distribution marking required.

Each data item requiring a distribution statement, except for Distribution Statement A, shall also have the following destruction notice below the distribution statement:

“Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

Notice to accompany release of Export Controlled Data – Unabbreviated Warning Notice:

“WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. 2751 et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401, et seq. Violation of these export-control laws is subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25.”

Block 10: Frequency: The following is a list of typical codes used to specify frequency of submittals:

ABBREVIATION DEFINITION

MTHLY Monthly ASREQ* As required BI-WE Every two weeks BI-MO Every two months DAILY Daily DFDEL Deferred delivery ONE/R One time with revisions OTIME One time QRTLY Quarterly SEMIA Every six months XTIME** Number of times to be submitted

*Further explanation of this code will be in Block 16.

**A number must be inserted in place of the “X” (e.g., 3TIME).

Block 11: As of Date: If the data will be submitted only once, the “as of date” (the cut-off date) is entered as follows: day/month/year. This is the date for cutting off collection of data. If the data is to be submitted multiple times, the number in the block indicates the number of calendar days before the end of the reporting period, established in Block 10, that data collection will be cut off. For example, “15” would place the “as of date” for the data at 15 days before the end of the month, quarter or year depending on the frequency established in Block 10.

Block 12: Date of First Submission: The initial data submission is entered as follows: day/month/year. If the submittal is constrained by a specific event or milestone, the event of milestone is identified. If the contract start date is not known, the number of days the data is due after contract start is identified (e.g., 30 DAC).

Block 13: Data of Subsequent Submission: For data items being submitted more than once, the date(s) of subsequent submission(s) is identified. If submittal is constrained by a specific event or milestone, this will be explained in Block 16.

Block 14: Distribution: Block 14 provides for the following particulars:

Block 14a: Addressee: A listing of who will receive the data item by their component designator or office symbol and/or codes, or unit identification codes. Complete addresses are in the next section of this CDRL, if applicable.

Block 14b: Copies: The specific number and type of copies to be delivered to each addressee. When the data item requires advance written approval (indicated by an “A” in Block 8), draft copies are required for approval before publication of the final document to the addressees identified. Also included will be digital media details and constraints and non-digital media details and constraints.

Block 15: Total: The total number of draft and final copies required by Block 14.

Block 16: Remarks: This block provides additional or clarifying information for Blocks 1 through 15, e.g., clarification relative to distribution statements, DID tailoring requirements, use of contractor format, and distribution of the data. If additional space is required, backup sheets, which shall be attached to the applicable DD1423, will be used.

MAILING ADDRESSES

The following mailing addresses may be used when email notification or on-line posting of CDRL items is not possible.

AFLCMC/HBDC

Attn: TACP CASS Data Manager 5 Eglin Street, Bldg 1624 Hanscom AFB, MA 01731-2100

AFLCMC/HBDF

Attn: TACP CASS Financial Manager 5 Eglin Street, Bldg 1624 Hanscom AFB, MA 01731-2100

AFLCMC/HBDK

Attn: TACP CASS Contracting Officer 5 Eglin Street, Bldg 1624 Hanscom AFB, MA 01731-2100

INDEX OF DATA ITEMS

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-ADMN-81505/T Report, Record of Meeting/Minutes

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

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

A007 DI-IPSC-81431A/T System/Subsystem Specification (SSS)

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 Report)

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

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

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

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

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

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

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

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

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

A023 DI-MISC-80508B/T Technical Report – Study/Service (System Administration & Maintenance Manual)

A024 DI-IPSC-81633/T Software Programmer’s Guide

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

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

A027 DI-ILSS-80872/T Training Materials

Seq. No. DID Title

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

A029 DI-MGMT-81861/T Integrated Program Management Report (IPMR)

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

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

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

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

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

Attachment 1

STATEMENT OF WORK (SOW)

15 October 2012 v5

Air Force Life Cycle Management Center Battle Management Directorate

Theater Battle Control Division (AFLCMC/HBD) Hanscom Air Force Base, Massachusetts 01731

1 SCOPE

2 APPLICABLE DOCUMENTS

3 REQUIREMENTS

3.1 Software Development, Integration, Test, and Fielding Support

3.1.1 Operational Software Releases

3.1.1.1 CASS Software v1.4.5 Release 1

3.1.1.2 CASS Software v1.4.5 Release 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

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: INFORMATION ASSURANCE REQUIREMENTS/CONTROLS

APPENDIX D: 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 mission areas, i.e., 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 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

15 Oct 12

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

1 Mar 12 Tactical Air Control Party Modernization (TACP-M) Security Classification Guide (SCG)

DD254

28 Aug 12

TACP-M CASS Contract Security Classification Specification

Number/Date Title 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-B

Jun 07

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 SRD and this SOW. Upon contract award, the Government will provide the Contractor with the TACP CASS Software v1.4.4 object code, source code, and existing engineering code and the

TACWIN prototype software for Dismounted operations as Government Furnished Property (GFP), as described in the contract GFP List.

3.1.1 Operational Software Releases

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 Release 1 and Release 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 Release 1

The Contractor shall deliver Release 1 with all CASS Software legacy v1.4.4 capabilities for the ASOC, TOC, and Mounted mission areas and the additional capabilities for the Dismounted mission area, as defined for Release 1 in the SRD.

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

b. The Contractor shall include in Release 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 Release 1.

3.1.1.2 CASS Software v1.4.5 Release 2

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

a. The Contractor shall ensure Government-designated discrepancies from outstanding TACP CASS Release 1 TPRs are not present in the delivered Release 2 software.

b. The Contractor shall include in Release 2 the radio firmware upgrades, aircraft OFP interface upgrades, other external interface changes, and security updates that are available for integration into Release 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 Software Development Plan (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.

c. The Contractor shall continue the engineering build work for the Call for Fires (CFF) capability for interfacing TACPs with the U.S. Army.

CDRL A002 – Software Product Specification (SPS) 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 release to ensure all applicable SRD requirements and TACP CASS ICD interfaces are met.

3.1.3.2 Platform/System Integration

The Contractor shall integrate each TACP CASS Software v1.4.5 operational release 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 release on the TACP hardware platforms integrated by NSWC Crane. The Contractor shall integrate each TACP CASS Software v1.4.5 operational release with any new hardware required by the Government as upgrades to legacy platforms, including hardware to support the Simplified Interface Environment (SIE) capability. The Contractor shall integrate each operational release 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 attached 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 releases, the Contractor shall deliver the entire contents of the SIL to the Government, along with a final version of the SIL documentation in an appendix to the Software Programmer’s Guide (see paragraph 3.1.6). 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 each TACP CASS Software release/build meets 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 release, 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 – 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 ICD.

CDRL A005 – 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 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 release/build. The Contractor shall define software metrics in the SDP and shall report those metrics (including trend analysis) at all technical and management reviews. The Contractor's software metrics shall include performance metrics that allow measurement of software timeliness, errors, and other performance factors.

The Contractor shall establish a performance metrics baseline using v1.4.4 and subsequently report and trend v1.4.5 performance against the v1.4.4 baseline.

CDRL A006 – Software Development Plan (SDP)

b. The Contractor shall specify the CASS Software requirements for each mission area in a System Specification (SSS) derived from the SRD and shall provide a trace of the SSS requirements to the SRD with rationale. The Contractor shall use the approved CASS SSS to document the CASS Software v1.4.5 functional baseline. The Contractor shall develop a software system design and architecture that meets the requirements of the SRD and SSS.

CDRL A007 – System/Subsystem Specification (SSS) 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 SSS with rationale.

CDRL A009 – Software Requirements Specification (SRS)

d. The Contractor shall implement software quality assurance (SQA) processes in accordance with the Government-approved SDP. The Contractor shall run a Contractor-selected SQA tool on the software code and provide the tool’s output reports to the Government at least monthly.

e. The Contractor shall conduct software performance assessments including analysis, modeling, simulation, and testing to identify and characterize the performance limits of the CASS Software under nominal and peak load TACP environments. The Contractor shall utilize the results of the performance assessments to ensure a robust software design and implementation. The Contractor shall incorporate the results of the performance assessments into the appropriate performance metrics reported in accordance with paragraph 3.1.4.3a.

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 release to assure protection of critical functionality and Critical Program Information (CPI), as identified in the TACP-M Program Protection Plan (PPP), to be provided as Government-furnished information (GFI). 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 software 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 run a DoD-approved source code evaluation tool on all developed/reused software to assure no malicious code or security issues are present. The Contractor shall protect and demonstrate/verify all COTS software and software of unknown pedigree (i.e., software from sources buried in the supply chain).

b. The Contractor shall implement anti-tamper and counterfeit prevention measures and define the processes to be used. The Contractor shall, as jointly agreed to by the Government and the Contractor, mitigate any identified risk of tampering and 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 critical program information and sensitive information and facilities. The Contractor shall identify where this access list is 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, and (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 human systems integration (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 implement a human machine interface (HMI) which is configurable/adaptable for each of the four TACP mission areas (i.e., ASOC, TOC, Mounted, Dismounted) in accordance with the SRD, including an 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 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 will propose HMI changes to address that feedback.

CDRL A004 – Report, Record of Meeting/Minutes

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 no later than 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 no later than CDR.

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 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 (including trend analysis) vs. the v1.4.4 baseline at HSI Working Group meetings, technical reviews, management reviews, and test readiness reviews. 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 in meeting the Department of Defense (DoD) Information Assurance Certification and Accreditation Process (DIACAP) in development of the TACP CASS Software v1.4.5 program, as described below. The Contractor shall reference DIACAP guidelines defined in DoDD 8500.1, DoDI 8500.2, DoDI 8510.01, DoDI 8580.1, and AFPD 33-202 for TACP CASS IA guidance.

a. For each system in which the TACP CASS v1.4.5 software will reside, the Contractor shall lock down the system using the Defense Information Systems Agency (DISA) IA Gold Disk process. The Contractor shall provide written confirmation that the system complies with the DoDI 8500.2 IA controls required for Mission Assurance Category (MAC) II/Confidentiality Level (CL): Classified, as identified in Appendix C, with the System Install Disk delivery for Government developmental testing. A “system” as defined herein includes the configuration of both the software and hardware of a TACP computer platform. The current TACP-M systems are defined in the TACP-M v1.4.2 System Security Authorization Agreement (SSAA). The hardware and software are identified in SSAA sections 1.2, System Description, and 3.1, System Architectural Description.

b. The Contractor shall review TACP-M IA documents to update information and procedures for IA compliance. The current documentation is in DoD Information Technology Security Certification and Accreditation Process (DITSCAP) format, and the Government will migrate the documentation to DIACAP format between now and generation of the first TACP-M v1.4.5 System Install Disk. The current key documents consist of the TACP-M v1.4.2 SSAA main document and its appendices E, V, and W, to be provided as GFI. The Contractor shall provide proposed changes and updates to the IA documentation 60 days prior to System Installation Disk delivery for Government developmental testing.

c. The Contractor shall provide in-person IA technical support to the Government to support TACP CASS formal IA test events. The Contractor shall support Government IA Certification and Accreditation (C&A) test activities with 46th Test Squadron (TS)/OGEI, Eglin AFB, FL.

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

Group meetings. The Contractor shall provide responses to assigned action items for issues identified at the IA Working Group meetings.

CDRL A013 – Scientific and Technical Reports (DIACAP Report)

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 release, the Contractor shall establish its functional baseline based on the SSS, its allocated baseline using the CSCI SRSs and SSDD, and its product baseline using the SPSs, SDDs, ICD, and SVD. The Government will establish its functional baseline prior to conclusion of the SRR. The Contractor shall serve as the configuration control authority for the allocated and product baseline candidates until Government baseline establishment upon Physical 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), 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 – Notice of Revision (NOR) CDRL A016 – 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 A017 – Configuration Status Accounting Information

e. The Contractor shall support a Government-conducted Functional Configuration Audit (FCA) for each operational software release to verify each CSCI has achieved the requirements specified in the SRD, SSS, and SRSs. The Contractor shall correct all discrepancies resulting from the FCA.

f. The Contractor shall support a Government-conducted PCA for each operational software release 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.

g. For both FCA and PCA, the Government will hold an audit technical interchange meeting (TIM) with the Contractor 90 days prior to the audit activity to define the audit scope.

The Government will then prepare an audit plan and informally review the plan with the Contractor 45 days prior to audit activity. The Government will conduct an audit readiness review with Contractor participation 30 days and again seven days prior to each audit activity.

h. When directed by and under guidance from the Government and commensurate with the final “as-built” software release, the Contractor shall incorporate the ACPINS scheme in accordance with TO 00-5-16, into the following:

(1) Source code header files and media label(s).

(2) Application code media label(s) and version identification windows

(e.g., Help->About or equivalent).

(3) Title page of the following data items: SSS, SSDD, SRS, SDD, ICD, SPS, HMI Style Guide, SPG, and SVD.

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 CDRL.

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 A018 – Data Accession List (DAL)

b. The Contractor shall establish and maintain an unclassified, 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…