M67854-16-R-0217-0001.docx

M67854-16-R-0217

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

1.0 SCOPE

This Statement of Work (SOW) defines the effort required for the manufacture, assembly and test of the Common Aviation Command and Control System (CAC2S) Air Command and Control Subsystem (AC2S). This SOW also defines the effort required for maintaining the CAC2S operational software. It includes the associated program management, systems engineering, production, software management, testing, and logistics requirements.

The Contractor shall build these items in accordance with the Technical Data Package (TDP) (Attachment 2). The Contractor shall deliver AC2Ss, consisting of manufactured items, Government Furnished Equipment and Commercial Off-the-Shelf (COTS) items. The AC2Ss to be delivered under this contract shall be tested in accordance with Government approved test procedures (Attachment 10). Manufacturing Acceptance and Government System Final Acceptance Testing shall take place at the Contractor’s facility.

The Contractor shall maintain the CAC2S baseline software which includes Information Assurance (IA) updates and software releases containing fixes to software deficiencies and approved system capability upgrades. The Contractor shall maintain a Software Engineering Environment (IEEE 12207) and develop a System Integration Laboratory to accomplish software development, integration and testing. The Contractor shall deliver quarterly IA updates and semi-annual maintenance releases.

2.0 APPLICABLE DOCUMENTS

The following documents, of the exact issue shown, form a part of the SOW to the extent specified herein. In the event of a conflict between the documents referenced herein and the contents of this SOW, the contents of this SOW shall take precedence.

With exception to those documents listed in paragraph 2.1 the Contractor may obtain the specifications, standards, plans, drawings, data item descriptions, and other pertinent documents cited in this statement of work from the on-line Acquisition Streamlining and Standardization Information System (ASSIST). If not available in ASSIST, the specific activity and the address from which to obtain the document will be provided by the Contracting Officer upon request.

2.1 CAC2S Related Documentation

The following documentation is provided in Section J:

Government Furnished Property (GFP) List (Attachment 1) CAC2S Phase 2 Technical Data Package (TDP) (Attachment 2) Allotment of Funds Table (Attachment 3) Initial Issue Spares List (Attachment 4) Retrofit Spares List (Attachment 4A) Wholesale Stock Spares List (Attachment 4B) MCSC Systems Engineering Technical Review Handbook (Attachment 5) AC2SN Risk Management Plan (Attachment 6) Notional CAC2S Cost and Software Data Reporting (CSDR) Plan (Attachment 7A) Notional CAC2S Resource Distribution Table (RDT) (Attachment 7B) CAC2S Configuration Management Plan (Attachment 8) Diminishing Manufacturing Sources and Material Shortages (DMSMS) Plan (Attachment 9) Government Test Procedures, (Attachment 10) CAC2S System Safety Program Plan (Attachment 11) DD 254, Contract Security Classification Specification (Attachment 12) CAC2S Security Classification Guides (Attachment 13) CEC Security Classification Guides (Attachment 14) Reserved (Attachment 15) IUID Management Plan (Attachment 16) Contractor’s IMS (Attachment 17) Contractor’s RMP (Attachment 18) Contractor’s CWBS (Attachment 19) Contractor’s Data Management Plan (Attachment 20) Contractor’s Environment Safety and Occupational Health (ESOH) Implementation Plan (Attachment 21) Contractor’s Security Management Plan (Attachment 22) Contractor’s Manufacturing/Production Plan (Attachment 23) CAC2S Software Development Strategy (Distro D) (Attachment 24) System Integration Lab Configuration (Distro D) (Attachment 25) CAC2S Software Acquisition Management Plan (Distro D) (Attachment 26) AC2 Interface Documentation (Distro F) (Attachment 27) TAOC Radar System Interface Specification (Distro C) (Attachment 28) MINIMPs – J Series (Distro C) (Attachment 29) MINIMPs – K Series (Distro D) (Attachment 30) MINIMPs – M Series (Distro C) (Attachment 31) MIL-STD-1397C (SH) Input/Output Interfaces, Standard Digital Data, Navy Systems (Distro A) (Attachment 32) MIL-STD-3011 Department of Defense Interface Standard Interoperability Standard for the Joint Range Extension Application Protocol (JREAP) (Distro C) (Attachment 33) MIL-STD-6011D Department of Defense Interface Standard Tactical Data Link (TDL) 11/11B Message Standard (Distro C) (Attachment 34) MIL-STD-6016D Department of Defense Interface Standard Tactical Data Link (TDL) 16 Message Standard (Distro C) (Attachment 35) MIL-STD-6017A/B Department of Defense Interface Standard Variable Message Format (VMF) (Distro D) (Attachment 36) MIL-STD-6018 Integrated Broadcast Service (IBS) Common Message Format (CMF) Standard (Classified) (Distro XX) (Attachment 37) MIL-STD-6020B Data Forwarding Between Tactical Data Links (Distro C) (Attachment 38) CAC2S Information Assurance Controls Identification Document (IACID) (Distro D) (Attachment 39) Contractor’s System Engineering Management Plan (SEMP) (Attachment 40) CAC2S System Engineering Plan (SEP) (Attachment 41) Contractor’s Configuration Management Plan (CMP) (Attachment 42) Contractor’s Software Sustainment Plan (SSP) (Attachment 43) Contractor’s Quality Assurance Program Plan (Attachment 44) Contractor’s Program Management Plan (PMP) (Attachment 45) Contractor’s Sub-contractor Management Plan (Attachment 46) Contractor’s Material Management Plan (Attachment 49) Contractor’s Hazardous Material Management Program (HMMP) Plan (Attachment 50)

2.2 Joint Chiefs of Staff, Department of Defense and DoD Services Documents – Guidance Only

2.3 Non-Government and Commercial Standards, Specifications and Other Applicable Publications – Guidance only

2.4 Forms

2.5 Military Standards and Specifications – Mandatory Compliance

3.0 REQUIREMENTS

3.1 Full Deployment Unit (FDU) AC2S Configuration Definitions.

AN/TSQ-297(V)1 Configuration (Tactical Air Operations Center-TAOC) reference TDP (Attachment 2)

AN/TSQ-297(V)2 Configuration (Tactical Air Command Center-TACC) reference TDP (Attachment 2)

AN/TSQ-297(V)3 Configuration (TAOC Trainer) reference TDP (Attachment 2)

3.2 Full Deployment Unit (FDU) Production

3.2.1 Lot 1 CAC2S FDUs (CLINs 0001, 0002, 0003, 0004, 0005, Option CLINs 0010, 0011)

The Contractor shall furnish all labor and materials other than those materials and equipment provided by the Government as set forth on the Government Furnished Property (GFP) List (Attachment 1) to fabricate, assemble, integrate and test FDUs with cybersecurity/IA compliant operational software. FDUs delivered under these CLINs shall be build-to-print in accordance with the Technical Data Package (TDP) (Attachment 2). Delivery and Inspection/Acceptance shall be in accordance with Sections D, E and F of this contract.

3.2.2 Lot 2 CAC2S FDUs (Option CLINs 0101, 0102, 0103, 0109, 0110)

If this option is exercised, the Contractor shall furnish all labor and materials other than those provided by the Government as Government Furnished Property (GFP) List (Attachment 1) to fabricate, assemble, integrate and test FDUs with cybersecurity/IA compliant operational software. FDUs delivered under these CLINs shall be build-to-print in accordance with the Technical Data Package (TDP) (Attachment 2), and approved Engineering Change Proposals (ECPs). If ECPs result in changes to Government provided GFP the Government will provide an updated GFP list at execution of this CLIN. Delivery and Inspection/Acceptance will be in accordance with Sections D, E and F of this contract.

3.2.3 Lot 3 CAC2S FDUs (Option CLINs 0201, 0202, 0207, 0208, 0210)

If option is exercised, the Contractor shall furnish all labor and materials other than those provided by the Government as Government Furnished Property (GFP) List (Attachment 1) to fabricate, assemble, integrate and test FDUs with cybersecurity/IA compliant operational software. FDUs delivered under these CLINs shall be build-to-print in accordance with the Technical Data Package (TDP) (Attachment 2), and approved Engineering Change Proposals (ECPs). If ECPs result in changes to Government provided GFP the Government will provide an updated GFP list at execution of this CLIN. Delivery and Inspection/Acceptance will be in accordance with Sections D, E and F of this contract.

3.2.4 Lot 4 CAC2S FDUs (Option CLINs 0301, 0302, 0306, 0307, 0308, 0309)

If the option is exercised, the Contractor shall furnish all labor and materials other than those provided by the Government as Government Furnished Property (GFP) List (Attachment 1) to fabricate, assemble, integrate and test FDUs with cybersecurity/IA compliant operational software. FDUs delivered under these CLINs shall be build-to-print in accordance with the Technical Data Package (TDP) (Attachment 2) and approved Engineering Change Proposals (ECPs). If ECPs result in changes to Government provided GFP the Government will provide an updated GFP list at execution of this CLIN. Delivery and Inspection/Acceptance will be in accordance with Sections D, E and F of this contract.

3.2.5 CAC2S FDU Initial Spares (CLINs 0104, 0105, 0203)

The Contractor shall deliver each lot of spares blocks listed in (Attachment 4, 4A, 4B). Spares blocks shall be delivered as a complete set which includes every item on the list and in the total quantity specified on the applicable attachment. Delivery and Inspection/Acceptance will be in accordance with Sections D, E and F of this contract.

3.2.6 CAC2S Data (CLINs 0005, 0103, 0210, 0302)

The Contractor shall provide data items in accordance with the DD1423s, Contract Data Requirements Lists (CDRLs), identified in Section J of this contract.

3.3 Program and Data Management

3.3.1 Program Management (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall establish and maintain program management practices throughout the life of this contract. Program management practices shall include but not be limited to, visibility into the Contractors’ organization and techniques used in managing the program, including subcontractor and data management. The Contractor shall plan and monitor the execution of all program tasks and shall maintain regular communications to keep the Government apprised of all program issues and status. Additionally, requirements that are specified within the terms and conditions of this contract shall apply to subcontractor performance. The Contractor shall be accountable for ensuring all subcontractors are compliant with the terms and conditions of this contract. The Program Manager (PM) assigned to this contract shall be assigned as full time to this task. The Contractor shall submit Monthly Status Reports (MSR) to the Government in accordance with CDRL B001.

CDRL B001, Monthly Status Report

3.3.1.1 Assignment of Responsibility and Authority (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall identify the organizational elements responsible for the conduct of the activities required under this contract. Responsibilities shall be assigned and clear lines of authority defined for determining and controlling the resources necessary to deliver the requirements of this contract. The Contractor shall notify the Contracting Officer of any substitution of Key Personnel in accordance with section G.7 of this contract.

3.3.1.2 Post Award Conference (CLINs 0001, 0005)

The Contractor shall host a Post Award Conference (PAC) at the Contractor's facility no later than 30 calendar days after contract award. The purpose of the PAC is to achieve a clear and mutual understanding of all contract requirements and identify and resolve potential problems. As part of the PAC, the Contractor shall introduce key personnel and present program implementation processes to be utilized under this contract. The Contractor shall provide IAW CDRL B004 an overview of their Risk Management process and discuss key risks to include dependencies and mitigation for each risk. The Contractor shall also present the IMS and brief the Critical Path, the near Critical Path, and the Driving Path to First Article Test; provide an overview of their schedule change management and schedule baseline management processes; and present the results of the Schedule Risk Assessment. The Contractor shall provide the PAC agenda IAW CDRL B003.

CDRL B003, Conference Agenda CDRL B004, Briefing Material The Post Award Conference shall include a discussion of the Contractor’s standard Cost and Software Data Report (CSDR) process that satisfies the guidelines contained in the DoD 5000.04-M-1, CSDR Manual, and the requirements in the Government-approved CSDR plan (Attachment 7) for the contract, DD Form 2794, and related Resource Distribution Table. The Contractor shall provide meeting minutes in accordance with CDRL B002.

CDRL B002, Meeting Minutes

3.3.1.3 Monthly Contract Reviews (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall host a Monthly Contract Review (MCR), via telephone conference call, to allow the Government to assess the efforts being performed under this contract in support of the CAC2S program and resolve issues real-time. The MCR will be held within five days of monthly closeout unless agreed to in advance by the Government. The Contractor is required to provide all conference dial in information for the MCR. This MCR shall include, but not be limited to, review of all contract issues/action items, both open and new, related to the execution of the contract and other issues having direct impact on cost, schedule, and performance. The Contractor shall provide meeting minutes in accordance with CDRL B002. The Contractor shall include action items captured during the MCRs in the submission of the MSR and submit to the Government in accordance with CDRL B001.

CDRL B001, Monthly Status Report CDRL B002, Meeting Minutes

3.3.1.4 Meetings, Formal Reviews, Conferences, and Audits (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall plan, host, attend, coordinate, support and conduct meetings, formal reviews, conferences, and audits (hereinafter called "reviews") in conjunction with the Government. These reviews shall consist of In Process Reviews (IPRs), Production Readiness Reviews and others as defined in this contract. The Government anticipates 5 reviews of two day duration per contract year. The reviews will be conducted at Contractor and/or Government facilities. Reviews requiring demonstration and/or examination of equipment will be conducted at a Government approved location. All reviews under this contract shall be included in the program Integrated Master Schedule, CDRL B005. Multiple reviews may be held concurrently with the Contracting Officer’s advance written approval via informal email. The Contractor shall prepare agendas in accordance with CDRL B003. The Contractor shall prepare briefing materials and minutes in accordance with CDRLs B002 and B004.

The Government reserves the right to cancel any review or require additional reviews be scheduled at critical points during the performance of this contract. Action item documentation, including assignment of responsibility and due dates, shall be established prior to adjournment of all reviews and included as part of the review minutes. Action items shall be tracked in the Monthly Status Reports in accordance with B001.

CDRL B001, Monthly Status Report CDRL B002, Meeting Minutes CDRL B003, Conference Agenda CDRL B004, Briefing Material CDRL B005, Integrated Master Schedule (IMS)

3.3.1.5 In-Process Review (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

In Process Reviews (IPR) shall be held quarterly at dates and locations agreed to in advance by the Government. The Government reserves the unilateral right to cancel or postpone any IPR for any reason. The initial IPR shall be conducted at the Contractor’s facility and held no earlier than 70 calendar days after the Post Award Conference and no later than 100 calendar days after contract award. Subsequent IPRs shall be conducted twice yearly at the Contractor’s facility and twice yearly at the Government’s location of choice at or near Quantico, Virginia. Areas addressed at the IPR shall include, but are not limited to, outstanding management issues, risk (cost, performance and schedule) identification and resolutions, actual versus expected performance of each area and other items in accordance with the agenda agreed to in advance by the Government. Action items shall be tracked in the Monthly Status Reports in accordance with B001. The Contractor shall provide an agenda, briefing materials, and written minutes for each IPR in accordance with CDRLs B002, B003, and B004.

CDRL B001, Monthly Status Report CDRL B002, Meeting Minutes CDRL B003, Conference Agenda CDRL B004, Briefing Material

3.3.1.6 Production Readiness Review (PRR) (CLINs 0001, 0005, 0101, 0201, 0301)

The Contractor shall complete a Production Readiness Review (PRR) prior to beginning the manufacture of the first FDU (CLIN 0001) and a delta PRR for subsequent Production Lots (CLINs 0101, 0201) if necessary. The Contractor shall identify existing and projected manufacturing problems and areas of risk and shall assess the Contractor's planning to achieve production rates required under the delivery schedule. The Contractor shall host the PRR and it shall be conducted in accordance with Marine Corps Systems Command (MCSC) Systems Engineering Technical Review Handbook (Attachment 5) and shall address the following areas:

The Contractor shall provide an agenda, briefing materials, and written minutes for each PRR in accordance with CDRLs B002, B003, and B004. Action items shall be tracked in the MSR.

CDRL B001, Monthly Status Report CDRL B002, Meeting Minutes CDRL B003, Conference Agenda CDRL B004, Briefing Material

3.3.1.7 Technical Interchange Meetings (TIMs) (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0305, 0306, 0307, 0308, 0309, 0310)

The Government or the Contractor may request TIMs. The Contractor or the Contracting Officer’s Representative (COR) shall provide a list of topics to be discussed at the TIM no later than five business days prior to the requested date. The Contractor should anticipate three TIMs per quarter with a planned duration of 8 hours per TIM. Meetings may be held at either Contractor or Government designated facilities or may be conducted by telephone. The purpose of a TIM is to discuss specific technical activities, including action items, test plans, test results, design issues, technical decisions, and implementation concerns to ensure continual visibility into technical progress. The Contractor shall provide minutes following the TIM and briefing materials for the TIM (when topic of discussion is of a complex technical nature). Action items shall be tracked in the Monthly Status Reports in accordance with B001.

CDRL B001, Monthly Status Report CDRL B002, Meeting Minutes CDRL B003, Conference Agenda CDRL B004, Briefing Material

3.3.1.8 Integrated Product Teams (IPT) (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall participate in the Government established AC2SN System Engineering & Integration and Supportability IPTs. Each IPT shall be held quarterly and the Contractor can participate remotely via appropriate communications. The Contractor shall respond to action items.

3.3.1.9 Integrated Master Schedule (IMS) (CLINs 0001, 0002, 0003, 0004, 0005, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0108, 0109, 0110, 0201, 0202, 0203, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0305, 0306, 0310)

The Contractor shall develop, maintain, status, and publish a contract level Integrated Master Schedule (IMS) for all efforts to be performed under Contract Line Item Numbers (CLIN) 0001, 0002, 0003, 0004, 0005, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0108, 0109, 0110, 0201, 0202, 0203, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0305, 0306, and 0310. The Contractor shall identify and include milestones and/or schedule visibility tasks to track and report the acquisition, handoff, and receipt of critical subassemblies, schedule-significant subassemblies, fixture-critical items, and software configure items from subcontractors. The Contractor will also identify and report the Critical Path and Near Critical Path. The Near Critical Path will include discrete tasks that have 10 days or less total slack. Additionally, the Contractor will identify and report the Driving Path to, at a minimum, First Article Test, Windows 10 migration, and final delivery of each lot of Full Deployment Units included in CLINs 0002, 0003, 0004, 0101, 0102, and 0201. The Contractor IMS shall be provided to the Government for review and approval in accordance with CDRL B005.

CDRL B005, Integrated Master Schedule (IMS)

3.3.1.10 Risk Management (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

For the life of this contract, the Contractor shall maintain a risk management program in accordance with the Contractors’ Risk Management Plan (RMP) (Attachment 18). The contactor shall participate in the Government’s risk program as described in the AC2SN Risk Management Plan (Attachment 6), including the CAC2S monthly Risk Review Team (RRT) and quarterly Risk Management Board (RMB). The Contractor shall input their identified risks (cost, schedule and performance) into the Government Risk Exchange database to support the RRT and RMB. The Government will provide the Contractor’s risk management team appropriate access to the Government Risk Exchange database.

3.3.1.11 Contractor Performance Measurement

3.3.1.11.1 Contract Work Breakdown Structure (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall develop a Contract Work Breakdown Structure (CWBS) (Attachment 19) and dictionary using the WBS structure contained in the Cost and Software Data Reporting (CSDR) Plan (Attachment 7). The CWBS and dictionary shall be updated in accordance with CDRL B012 to incorporate changes agreed upon at the Post Award Conference. The Contractor shall extend the CWBS to a minimum of level three and provide additional levels as required to provide adequate internal management, surveillance, and performance measurement, regardless of the reporting level stipulated in the contract for Government visibility. The Contractor shall maintain and use the CWBS as the primary framework for contract planning, budgeting, and reporting the status of cost, schedule and technical performance to the Government.

CDRL B012, CWBS Index and Dictionary

3.3.1.11.2 Performance Measurement System (CLINs 0007, 0008, 0009, 0106, 0107, 0108, 0204, 0205, 0206, 0209, 0303, 0304, 0305, 0310)

The Contractor shall utilize their existing, internal performance management system to plan, schedule, budget, monitor, manage, and report cost, schedule, and technical status/updates applicable to the contract. The Contractor's internal performance management system shall serve as the single, formal, integrated system that meets both the Contractor's internal management requirements and the requirements of the Government for timely, reliable, and auditable performance information.

3.3.1.11.2.1 Over Target Schedule (OTS) Restructuring Action (CLINs 0001, 0002, 0003, 0004, 0005, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0108, 0109, 0110, 0201, 0202, 0203, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor may conclude that existing approved schedule baseline no longer represent a realistic plan in terms of budget/schedule execution. In the event the Contractor realizes an OTS restructuring action is necessary, the Contractor shall follow OUSD AT&L OTB and OTS Guide dated 5 Dec 2012 procedures. The Contractor shall not implement any OTS restructuring action prior to receiving written approval from the Contracting Officer.

3.3.1.11.2.2 Contract Funds Status Reporting (CLINs 0007, 0008, 0009, 0106, 0107, 0108, 0204, 0205, 0206, 0209, 0303, 0304, 0305, 0310)

The Contractor shall submit Contract Funds Status Report (CFSR) in accordance with CDRL B006.

CDRL B006, Contract Funds Status Report (CFSR)

3.3.1.11.2.3 Contractor Cost Data Reporting (CCDR) (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall collect and report actual contract costs to provide DoD cost analysts with needed data to estimate future costs. Contractor reports shall be prepared in accordance with CDRLs B007, B008, B009, B010 and B013. DD form 2794 Contract Plan will show proposed reporting forms for this contract.

In the performance of this contract, the Contractor shall use:

CDRL B007, Cost Data Summary Report (CDSR), (DD Form 1921) CDRL B008, Functional Cost-Hour Report (FCHR) (DD Form 1921-1) CDRL B009, Progress Curve Report (PCR) (DD Form 1921-2) CDRL B010, Contractor Business Data Report (DD Form 1921-3) CDRL B013, Sustainment Functional Cost-Hour Report (DD Form 1921-5)

3.3.1.11.2.4 Software Resources Data Reporting (SRDR) (0009, 0108, 0206, 0305)

The Contractor shall submit a completed SRDR Initial Developer Report for the entire software product in accordance with CDRL B011 for each Software Maintenance CLIN. The Contractor shall submit a completed SRDR Final Developer Report for the entire software product in accordance with CDRL B011 for each Software Maintenance CLIN.

CDRL B011, Software Resources Data Reporting (SRDR): Software Maintenance Report and Data Dictionary

3.3.1.12 Government Furnished Property (GFP) (CLINs 0001, 0002, 0003, 0004, 0005, 0009, 0101, 0102, 0103, 0107, 0109, 0110, 0201, 0202, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0305, 0306, 0307, 0308, 0309, 0310)

GFP consists of Government Furnished Equipment, Government Furnished Material and Government Furnished Information (Attachment 1) of this contract. As part of the Monthly Status Report delivered under CDRL B001, the Contractor shall provide updates to the Government on all received, installed in prime equipment, held and returned GFP. In accordance with the GFP clause of this contract, the Contractor shall inspect and inventory all GFP received and identify and report any discrepancies/deficiencies to the Government. Any changes to the status of GFP shall be updated in the Monthly Status Report. Each contract line item of Contractor-acquired property shall include the information contained in PGI 245.402-71(2).

The Contractor's responsibility extends from the initial acquisition and receipt of property, through stewardship, custody, and use until formally relieved of responsibility by authorized means, including delivery, consumption, expending, disposition, or via a completed investigation, evaluation, and final determination for lost, damaged, destroyed, or stolen property. This requirement applies to all Government property, either furnished or acquired under this contract, under the Contractor's accountability, stewardship, possession or control, including its vendors and subcontractors.

The Contractor shall include these requirements in all subcontracts under which Government property is acquired or furnished for subcontract performance.

The Contractor shall use Government property, either furnished or acquired under this contract, only for performing this contract, unless otherwise provided for in this contract or approved by the Contracting Officer. The Contractor shall not modify, cannibalize, or make alterations to Government property unless this contract specifically identifies the modifications, alterations or improvements as work is to be performed.

The Contractor shall maintain all Government property in accordance with the FAR and DFARS. The Contractor shall perform preventative maintenance and servicing to maintain the GFP in a ready for use condition in order to carry out the tasking covered in this SOW. The Contractor shall provide repair support (corrective maintenance) for the Government property used in conjunction with and in support of this SOW. Unless otherwise noted, the Government does not authorize the Contractor to enter bailment agreements for Government Property under this contract with external parties.

CDRL B001, Monthly Status Report

3.3.1.12.1 Corrective Maintenance (CLINs 0008, 0107, 0205, 0304)

The Contractor shall include a review of all GFE actions submitted under the Monthly Status Report in accordance with CDRL B001. The procedures listed below shall be used to induct items for corrective maintenance. The Contractor shall inform the Government of any instances where the Contractor is unable to meet the times called out in the procedures listed below where circumstances are beyond the control of the Contractor. (i.e., arose out of causes beyond the control and without the fault or negligence of the Contractor pursuant to FAR 49.401(b))

CDRL B001, Monthly Status Report

3.3.1.13 Data Management (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall establish and maintain a single, centralized, unclassified Data Management System (DMS) for management of all data to include all necessary technical data (e.g. requirements, specifications, product design drawings, engineering notebooks, parts lists, First Article Test (FAT) Procedures, assembly cards, production readiness results/reviews, physical configuration audits, etc.), management plans and updates thereto, and historical archives and updates of minutes of meetings and reviews and contract data deliverables. Tracking of Action Items resulting from various program reviews, IPRs and IPT meetings shall be accomplished and displayed in the DMS as well as reported in the MSR. The Contractor, in developing information that will be furnished to the Government, shall make the maximum use of existing data and provide maximum multiple use of technical information. Specific data management functions shall include schedule control for deliverables, maintenance of deliverables, approval of deliverable format, and distribution of data products. The DMS shall also serve as the Data Accession List to be delivered in accordance with CDRL B014. The system shall include facilities for storage of all data developed or utilized for this contract, and shall provide equal access to data by the Government. The DMS shall use Microsoft® Office or compatible products unless agreed to in advance by the Government. The Government reserves the right to review all data associated with and developed for the CAC2S program under this contract.

This data management program, including Integrated Data Environment (IDE) structure, format, processes, and procedures, shall be documented and identified in the Contractor’s Data Management Plan (Attachment 20). To support data management, the Contractor shall establish and maintain a secure IDE for hosting all data used on or produced in support of this contract, including cost, schedule, and technical data and deliverables. All data deliveries, unless specifically agreed to in advance by the Contracting Officer, shall be delivered via the IDE. The purpose of the IDE is to create a seamless, collaborative data environment for the Contractor and Government team that contains all pertinent data about the project throughout its development and delivery. Data shall be protected in accordance with the Security Classification Guides (Attachments 13-15) and Information Assurance guidelines per NIST SP 800-162. The Government shall have unlimited data rights. Should the Contractor require the use of proprietary data, documents, or other contractor information during the execution of this contract, the Contractor shall prepare and deliver a Contractor Technical Study (CDRL A006). The contractor technical study shall demonstrate to the Government that the use of proprietary elements does not preclude or hinder other component or modules from interfacing with or otherwise replacing or upgrading open parts of the system. All proprietary or vendor-unique elements that become part of the design require advance written approval of the Government.

Classified material shall be transmitted via one hard copy and one CD/DVD to MARCORSYSCOM, and the In-Service Engineering Activity classified mailing addresses and shipped in accordance with Section D-6. Prior to shipping of classified material, the Contractor shall coordinate with the Contracting Officer Representative (COR) to identify the associated Government POC. After shipping of classified material, the associated tracking number shall be forwarded to the COR and the Government POC at the receiving activity.

CDRL B001, Monthly Status Report CDRL B014, Data Accession List

3.3.1.14 Government Work Area (CLINs 0001, 0002, 0003, 0004, 0009, 0010, 0011, 0101, 0102, 0108, 0109, 0110, 0201, 0202, 0206, 0207, 0208, 0209, 0301, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall provide a separate room with Government controlled access at the Contractor’s facility to accommodate four (4) Government (non-DCMA) individuals during Program Management Reviews (PMRs), Technical Interchange Meetings (TIMs), Government Tests, and serve as office space for the Government Production Manager. The room shall have a lockable door, one (1) telephone line capable of conference calling and shall have internet access (firewalled) to accommodate 4 individual hookups.

3.3.1.15 Sub-Contractor Management (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall be responsible for the performance and quality of Sub-Contractor work under this contract. The Contractor shall flow down the requirements of this entire SOW to all Sub-Contractors, regardless of contract value. The Contractor shall monitor and control performance, quality, cost, and schedule according to the Contractor’s established subcontract management techniques to ensure that CAC2S program is not adversely impacted. Subcontractor performance shall be addressed in the Monthly Status Report, CDRL B001.

CDRL B001, Monthly Status Report

3.3.2 Documents Incorporated By Reference (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0008, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0107, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310)

Upon award of this contract, the following documents shall be accepted by the Government and incorporated by reference into the contract: Contract Work Breakdown Structure, Integrated Master Schedule, ESOH Implementation Plan, Program Management Plan, Data Management Plan, Sub-Contractor Management Plan, Manufacturing/Production Plan, Material Management Plan, Systems Engineering Management Plan, Software Sustainment Plan, Security Management Plan and Risk Management Plan. Any required updates under this contract, shall be made against these documents.

3.4 Systems Engineering (CLINs 0001, 0002, 0003, 0004, 0005, 0009, 0010, 0011,0101, 0102, 0103, 0104, 0105, 0108, 0109, 0110, 0201, 0202, 0203, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0305, 0306, 0307, 0308, 0309, 0310)

The Contractor shall establish and maintain systems engineering practices in accordance with the Contractors’ Systems Engineering Management Plan (SEMP) (Attachment 40) throughout the life of this contract. The Contractor shall utilize the CAC2S System Engineering Plan (SEP) (Attachment 41) to establish engineering policies and procedures in the SEMP. The system engineering practices shall provide visibility into the Contractors’ organization and techniques used in providing systems engineering throughout the development, integration, testing, and delivery of the CAC2S under this contract. The Contractor shall plan and monitor the execution of all systems engineering tasks and shall maintain regular communications to keep the Government apprised of all systems engineering issues and status. The Contractor’s SEMP shall flow down to all subcontractors. The Contractor shall be accountable for subcontractors’ compliance with the SEMP and is responsible for ensuring all deliverable products comply with the terms and conditions of this contract. Changes to the SEMP shall be submitted to the Government for review and approval in accordance with CDRL A001.

CDRL A001, Systems Engineering Management Plan (SEMP)

3.4.1 Configuration Management Process (CLINs 0001, 0002, 0003, 0004, 0005, 0009, 0010, 0011,0101, 0102, 0103, 0104, 0105, , 0108, 0109, 0110, 0201, 0202, 0203, 0206, 0207, 0208, 0209, 0210, 0301, 0302, 0305, 0306, 0307, 0308, 0309, 0310)

The Government owns and controls the baseline for the CAC2S. The Contractor shall maintain a Configuration Management (CM) process for the hardware and software configuration documentation and media necessary for control of the AC2S production process. The principles contained in ANSI EIA-649-B and MIL-HDBK-61A may be used for guidance. The Contractor’s CM Process shall be implemented in accordance with the Contractor’s CM Plan (Attachment 42) submitted as part of their proposal and approved by the Government. The Contractor’s CM Process shall reflect integration with the processes described in the CAC2S Configuration Management Plan (Attachment 8) and shall consist of configuration identification, configuration control, configuration status accounting, and configuration audits. The Contractor shall designate a CM representative to serve as a primary point of contact to the Government for all CM matters. Changes to established baselines shall only be made after the Government approval of Engineering Change Proposals (ECPs) and Requests for Variation (RFV) through the processed described in the CAC2S CMP. The Contractor shall be responsible for any subcontractor's CM efforts. The Contractor shall notify the Government of any changes, which affect the Contractor's established CM process in a revision to the CM Plan in accordance with CDRL A002. The Contractor shall participate in Government AC2SN Configuration Control Boards (CCBs) that only impact CAC2S Phase 2 production and software maintenance.

CDRL A002, Supplier’s Configuration Management Plan

3.4.1.1 Engineering Change and Requests for Variation (RFV) (CLINs 0001, 0002, 0003, 0004, 0005, 0007, 0009, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0106, 0108, 0109, 0110, 0201, 0202, 0203, 0204, 0206, 0207, 0208, 0301, 0302, 0303, 0305, 0306, 0307, 0308, 0309)

The Contractor shall provide notification to the Government for any proposed changes to the product baseline (hardware or software) in accordance with CDRL A003. The Government will evaluate the request and process an Engineering Change Proposal when required. The Contractor shall support the Government evaluation of the proposed change. In the event the need for RFV occurs, the Contractor shall provide a RFV, in accordance with CDRL A004. Any approved RFVs shall be implemented through a contract modification.

CDRL A003, Technical Report-Studies/Services –Engineering Changes CDRL A004, Request for Variance (RFV)

3.4.1.2 As-Built Configuration (CLINs 0001, 0002, 0003, 0004, 0005, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0109, 0110, 0201, 0202, 0203, 0207, 0208, 0210, 0301, 0302, 0306, 0307, 0308, 0309)

The Contractor shall develop an, As-Built Configuration List in accordance with CDRL A005 for each delivered item. The as-built list shall extend down to the lowest serialized item level and be recorded in a Configuration Status Accounting database that shall be developed and maintained by the Contractor. The Contractor shall ensure that all data is accessible for Government review.

CDRL A005, As-Built Configuration List

3.4.1.3 CAC2S Engineering Studies (CLINs 0005, 0007, 0103, 0106, 0204, 0210, 0302, 0303) The Contractor shall perform engineering studies, analysis, and engineering technical assistance, as directed by the COR, in support of the production and integration of the AN/TSQ-297 systems. The engineering studies, analysis and engineering technical assistance will include unplanned, ad hoc engineering studies in support of this production effort. The engineering studies, analysis and engineering technical assistance shall address, but not be limited to, efficiencies in the production process, interfaces between subsystems and or components. All engineering studies, analyses and engineering technical assistance shall be coordinated with the Government prior to start. The Contractor shall deliver the results of engineering studies, analysis, and technical engineering assistance in accordance with CDRL A006.

CDRL A006, Technical Report – Study/Services – Engineering Studies

3.4.2 Item Unique Identification (IUID) (CLINs 0001, 0002, 0003, 0004, 0005, 0010, 0011, 0101, 0102, 0103, 0104, 0105, 0109, 0110, 0201, 0202, 0203, 0207, 0208, 0210, 0301, 0302, 0306, 0307, 0308, 0309)

The Contractor shall apply DoD Item Unique Identification (IUID) marking to the Unit level assemblies, and their associated Line Replaceable Units (LRU) procured under this contract as required by DFARS 252.211-7003 and Unit/LRU lists provided in the IUID Implementation Plan (Attachment 16). IUID pedigree data for LRUs embedded in Unit level assemblies shall be entered into the IUID Registry as children to the parent Unit. LRUs procured as spares shall not have a parent-child relationship. The Contractor shall utilize MIL-STD-130N for Item Unique Identification marking. The description of change in approved ECPs shall include applicable Unique Item Identifier (UII) marking method and location recommendations.

The Contractor shall maintain marking and verification records for all IUID qualifying items…