Attachment 0001-PWS FINAL_4Feb21.pdf

Attachment 0001-PWS

PERFORMANCE WORK STATEMENT

FOR

SECURITY SURVEILLANCE SYSTEM (SSS)

PRODUCTION, MAINTENANCE AND SUPPORT

4 February 2021

Prepared by:

Product Manager Force Protection Systems

5900 Putnam Rd, Bldg. 365 Ft Belvoir, VA 22060

US Army Force Protection Systems Security Surveillance Systems

UNCLASSIFIED//FOUO – ACQUISITION SENSITIVE

Table of Contents

1.0 BACKGROUND

1.1 OBJECTIVES

2.0 SCOPE OF WORK

3.0 PERIOD OF PERFORMANCE

4.0 PLACE OF PERFORMANCE

5.0 SPECIFIC TASKS/REQUIREMENTS

5.1 PROGRAM MANAGEMENT

5.1.1 KEY PERSONNEL

5.1.2 PROGRAM MEETINGS

5.1.3 CONTRACT KICKOFF MEETINGS

5.1.4 TECHNICAL INTERCHANGE MEETINGS

5.2 QUALITY ASSURANCE

5.2.1 TEST SUPPORT

5.2.2 INTEGRATION/REGRESSION TEST SUPPORT

5.2.3 GOVERNMENT ACCEPTANCE TEST SUPPORT

5.2.4 FIRST ARTICLE TEST

5.3 ENGINEERING SUPPORT

5.3.1 INTERFACE CONTROL DOCUMENT (ICD)

5.4 OTHER SERVICES

5.4.1 CONFIGURATION MANAGEMENT

5.4.2 PRODUCTION PROCEDURES

5.4.3 PRODUCT DATA

5.4.4 DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES

(DMSMS)

5.4.5 FAILURE REPORTING, ANALYSIS AND CORRECTIVE ACTION SYSTEM

(FRACAS)

5.4.6 PRODUCT SUPPORT ANALYSIS (PSA)

5.4.7 CUSTOMER WAIT TIME

5.4.8 RELIABILITY, AVAILABILITY AND MAINTAINABILITY (RAM) PROGRAM

5.4.9 PROVISIONING

5.4.10 REACH-BACK SUPPORT

5.4.11 ASSET VISIBILITY

5.4.12 DEPOT MAINTENANCE STUDY/ORGANIC DEPOT ASSESSMENT DATA .. 10

5.4.13 HUMAN SYSTEM INTEGRATION (HSI)

5.4.14 TRAINING

5.4.15 TECHNICAL MANUAL UPDATES

5.4.16 PROGRAM PROTECTION PLANNING

5.4.17 TRAVEL

6.0 PRODUCTION MATERIALS AND EQUIPMENT

6.1 GOVERNMENT PROPERTY / EQUIPMENT

6.1.1 SSS EQUIPMENT

6.1.2 BAR-CODING, SERIALIZATION, AND LABELING

6.1.3 PACKING, HANDLING, STORAGE, TRANSPORTATION, AND MARKING

6.1.7 FIELD SERVICE REPRESENTATIVE SUPPORT

6.1.8 READINESS SUSTAINMENT

6.1.9 REPAIR, INSPECTION, EVALUATION OF NON-WARRANTY ITEMS

6.1.10 INSTALLATION

6.1.11 SITE SURVEY

6.2 CYBERSECURITY

6.4.1 CLASS I MAJOR ECPS

6.4.3 CLASS II ADMINISTRATIVE ECPS

6.4.4 REQUEST FOR VARIANCE (RFV)

7.0 SECURITY REQUIREMENTS

8.0 sPECIAL SECURITY REQUIREMENTS

8.1.1 ANTI-TERRORISM (AT) LEVEL I AWARENESS TRAINING FOR CONTRACTORS

LOCATION IN CONTINENTAL UNITED STATES (CONUS)

8.1.2 AT AWARENESS TRAINING FOR OUTSIDE CONUS (OCONUS)

8.1.3 Access and General Protection/Security Policy and Procedures

8.1.4 CONTRACTORS/SUBCONTRACTORS REQUIRING COMMON ACCESS CARD

(CAC) 23

8.1.5 CONTRACTORS/SUBCONTRACTORS NOT REQUIRING CAC, BUT REQUIRE

ACCESS TO A DOD FACILITY OR INSTALLATION

8.1.6 iWATCH Training

8.1.7 Army Training Certification Tracking System (ATCTS)

8.1.9 OPSEC Training

8.1.10 Information Assurance (IA)/IT Training

8.1.11 IA/ IT Certification

8.1.12 Threat Awareness Reporting Program (TARP) Training

8.1.13 CONUS Replacement Center (CRC) Training

8.1.14 Contractor Personnel Supporting U.S. Armed Forces Deployed OCONUS

8.1.15 International Trafficking in Arms Regulations Compliance Program

9.0 CONTRACTOR MANPOWER REPORTING

10.0 GOVERNMENT’S RIGHTS TO TECHNICAL DATA AND COMPUTER

SOFTWARE

11.0 GENERAL INFORMATION

11.1.1 INSPECTION AND ACCEPTANCE

11.1.2 QUALITY ASSURANCE

List of Tables/Attachments

Table 1 – Application of Software Assurance Countermeasures (sample) Table 2 – Maintenance Category Descriptions Table 3 – Military Standards (MIL-STD) Table 4 – Military Handbooks (MIL-HDBK) Table 5 – Other Government Documents Table 6 – Non-Government Documents Table 7 – Program Reference Documents Table 8 – Program Compliance Documents

1.0 BACKGROUND

The Security Surveillance System (SSS) formerly known as the Tactical Security System (TSS) mission is to support short and long term security, surveillance and detection missions. These missions include but are not limited to: Theater Detention Facility (TDF) operations; perimeter security; internal security areas within base camps or installations;

outside the perimeter, border or boundary, primary and high priority routes; route clearance; homeland security missions, and any named areas of interest (NAI).

The SSS is a modular, scalable, lightweight, rapidly deployable, ground based security and surveillance system of systems. SSS includes a variety of short and long range Electro-Optic (EO) and Infrared (IR) cameras along with radar and seismic detection systems to provide situation awareness to the commander through wireless and wired networking capabilities. SSS supports various mounting options including tripods, masts, walls, and poles. SSS and its components are designed to be employed as a stand-alone system, in a layered effort, or integrated with additional FP systems. SSS is intended to be packaged in a single container for transportation and storage with a built-in organization system allowing for gaining units to custom select components needed for the mission.

SSS was designed to use the Integrated Ground Security Surveillance Response Capability (IGSSR-C) Command and Control (C2) software and hardware for its Operator Station. Due to delays in the IGSSR-C schedule, SSS will initially be fielded with legacy, Government-owned C2 software and hardware.

All sensor components are COTS or NDI with custom data and power interface boxes and Government provided software providing the networking and C2 capabilities. As part of the EMD phase, a production-level Technical Data Package (TDP), initial operator and maintainer manuals, supplemental manuals, and training materials were developed. The TDP and manuals will be maintained by the Contractor based on the Government provided configuration management plan and all system updates will be made in conjunction with the Government through Configuration Control Boards (CCBs).

1.1 OBJECTIVES

This requirement is to meet The Army’s need to provide perimeter security for theater Base Camps and Detention Facilities, through the procurement of new Security Surveillance System equipment (SSS). The SSS is a new Force Protection Program of Record replacing the existing Force Protection (FP) Suite and Rapid Deployment Integrated Surveillance System (RDISS) Quick Reaction Capabilities (QRCs).

2.0 SCOPE OF WORK

The Contractor shall provide all personnel, equipment, supplies, facilities transportation, tools, materials, supervision, and other items and non-personal services necessary in accordance with (IAW) the requirements identified in this PWS and the SSS TDP, except for those items specified as Government Furnished Property (GFP) and services.

Requirements identified in this PWS may be delineated in individual TO/DO issued during the Period of Performance (POP).

The Army’s SSS is a new Force Protection Program of Record replacing the existing Force Protection (FP) Suite and Rapid Deployment Integrated Surveillance System (RDISS) Quick Reaction Capabilities (QRCs). SSS is designed to provide perimeter security for theater Base Camps and Detention Facilities and meets the requirements set forward in the SSS Capability Development Document (CDD). SSS is currently in the Engineering and Manufacturing Development (EMD) phase of the Acquisition cycle where a production level Technical Data Package (TDP) will be developed and tested along with supporting technical manuals and training. The Government will have Unlimited Rights to the TDP, and the TDP and supporting specifications will be included in the solicitation package. This Production contract will support the post-Milestone C, Production and Deployment phase of the program providing procurement, integration, and sustainment services. Initial quantities of 39 systems have been set by Army Procurement Objectives but additional units are expected to be procured to replace aging QRCs already in theater. Support for systems Outside Continental United States (OCONUS) are intended to be provided through other PM FPS contracts but language has been added to this PWS to allow for direct Field Service Representative (FSR) support, if needed. All software will be maintained through existing contracts with the current developers and will be provided to this contract as Government Furnished Information (GFI). This contract, however, will require regression testing of all delivered software to ensure system functionality is maintained. Production, integration and sustainment efforts will be detailed through individual Task Orders/ Delivery Orders (TO/DOs) written against the based Indefinitely Delivery Indefinite Quantity Contract.

3.0 PERIOD OF PERFORMANCE

The Period of Performance (PoP) in support of the Security Surveillance System is a five year base contract from award date with a single three year option.

4.0 PLACE OF PERFORMANCE

Performance of the contract will take place at the contractor facilities as well as the potential for FSR support at both CONUS and OCONUS locations as directed by the Government.

5.0 SPECIFIC TASKS/REQUIREMENTS

As part of this requirement the Contractor shall be responsible for providing the following support, described in the subsections below. Additional information can be found in the following Appendices:

Appendix 1: Contract Data Requirements List Appendix 2: Acceptance Test Requirements Matrix Appendix 3: Acronyms

5.1 PROGRAM MANAGEMENT

The Contractor shall provide Program Management Services to include, but not limited to:

The Contractor shall perform all program management activities necessary to successfully engineer, produce, test, repair, and support SSS throughout the POP. The Contractor shall identify a Program Manager (PM) who is responsible for the oversight of all efforts under each individual TO/DO. The PM shall address all programmatic issues directly with the Government Contracting Officer Representative (COR). The Contractor shall prepare and deliver monthly reports IAW CDRL A001 – Contractor’s Progress, Status and Management Report. The reports shall include all significant contract activities critical to contract performance, including cost, schedule, manpower, technical status, testing, quality metrics, issues and risk mitigation plan if applicable.

5.1.1 KEY PERSONNEL

The Contractor shall assign to this contract the following key personnel with the stated qualifications:

Program Manager: A minimum ten (10) years’ experience managing government programs is required of which one (1) year must be supervisory. Bachelor’s degree. Four (4) additional years of related experience will substitute for bachelor’s degree. Experience in project management, engineering management, DoD acquisition, or another related subject of comparable complexity and responsibility.

Lead System Engineer: Bachelor’s degree in Engineering or related field and a minimum of ten (10) years of Systems Engineering experience. Four (4) additional years of related experience will substitute for bachelor’s degree. Experience with programmatic and program system engineering technical support. Experience providing all labor and services necessary to perform programmatic support in monitoring, assessing, coordinating, analyzing and integrating component programs/activities, including briefings/presentations and agendas for the total life cycle of the above programs/systems.

Product Support Manager: Bachelor's degree or equivalent in Logistics, Engineering, Supply Chain Management, Business Management, or a related discipline, as well as eight (8) years of general experience and five (5) years of relevant experience. Specialized skills include ILS documentation, Manpower/Personnel Integration (MANPRINT), technical manuals, training and training materials, materiel fielding, provisioning, and configuration audits.

Knowledge of logistics management concepts, theories, practices and methods to develop and analyze requirement needs and operational plans and to determine logistic objectives and goals, to identify support requirements, and to establish the relationship between the support system and the material system. An understanding of maintenance requirements in order to identify potential support problems. A working knowledge of the management and coordination of the overall Reliability, Availability, and Maintainability/Integrated Logistic Support (RAM/ILS) data acquisition, quality control, organization, and dissemination.

Configuration Manager: Bachelor’s degree. A minimum of six (6) years of related

Configuration Management and/or Logistics work experience. Ability to develop, implement, and audit the configuration management process and associated documentation to ensure that the organizational configuration management policy is being followed.

During the first 90 days of performance, the Contractor shall notify the Contracting Officer of any changes to key personnel and provide documentation for a replacement with the qualifications provided in this section within 48hrs,. If there are key personnel changes after the initial 90-day period, the Contractor shall submit the information required by this section to the Contracting Officer at least 15 days prior to making any permanent substitutions.

The Contractor shall provide a detailed explanation of the circumstances necessitating the proposed substitutions, complete resumes for the proposed substitutes, and any additional information requested by the Contracting Officer. Proposed substitutes should have comparable qualifications to those of the persons being replaced.

5.1.2 PROGRAM MEETINGS

5.1.3 CONTRACT KICKOFF MEETINGS

The Contractor shall host post-award Kickoff Meetings within 10 business days after award of the base contract and each individually awarded TO/DO. Draft briefing materials, including the meeting agenda, will be provided to the Government no later than five business days prior to the meeting and final briefing materials three business days prior to the meeting IAW CDRL A002 – Briefing Material. Meeting minutes shall be submitted after the meeting IAW CDRL A003 – Report, Record of Meeting/Minutes.

5.1.4 TECHNICAL INTERCHANGE MEETINGS

The Contractor shall conduct a minimum of one and a maximum of six TIMs per year at either the Contractor location or Fort Belvoir, VA. These meetings will be scheduled to discuss technology refresh efforts, critical path items, obsolescence issues, and other Government directed items, as needed; this does not include informal technical working groups. Briefing material shall be coordinated with the Government IAW CDRL A002 – Briefing Material. After completion of a TIM, the Contractor shall submit meeting minutes and action items IAW CDRL A003 – Report, Record of Meeting/Minutes. The Government will notify the Contractor within 30 calendar days of a required TIM.

5.2 QUALITY ASSURANCE

The Contractor shall implement, a quality ISO 9001-2015 or equivalent system and have a quality management system that monitors and controls critical processes; continuously improves processes; establishes mechanisms for performance feedback; and maintains an effective root cause analysis and corrective action system, the terms and conditions of the contract, and FAR Part 46. Any deviation to the Contractor’s quality management system shall be agreed upon, in writing, between the Contractor and the Government.

The contractor shall deliver a Quality Assurance Program Plan (QAPP) IAW CDRL A004

– Quality Assurance Program Plan. The Contractor shall develop and implement a performance management system with processes to assess and report its performance to the designated Government representative. The report shall be included in the monthly progress report IAW CDRL A001. The Government may audit products and processes as well as the quality control system at any stage of contract performance.

5.2.1 TEST SUPPORT

The Contractor shall provide support to SSS test and evaluation events. Support may include developing test plans, test support analysis and coordination, conducting site surveys, and pre-assessment activities. Additional support may include test planning, test execution, data collection, data analysis, test reporting, and on-site support.

5.2.2 INTEGRATION/REGRESSION TEST SUPPORT

The contractor shall support integration and regression testing from changes directed by the Government to include but not limited to:

Testing RMF patching and updating GFE software updates approved ECPs IGSSR-C integration

Changes to requirements, as required. Support shall include but not limited to:

Purchase/fabrication of support equipment as required Develop and execute regression test plans for the activities and system under test Verify/validate that the resolution fixed the problem and did not cause any other defects Verify that the system still complies with the SSS Performance Specifications as previously verified by Government test and evaluation and identify any discrepancies not previously identified

Update supporting documentation such as Operator manual as required

5.2.3 GOVERNMENT ACCEPTANCE TEST SUPPORT

The contractor shall plan, develop, implement, and maintain a product acceptance system that demonstrates compliance with the technical and contractual requirements identified in this PWS, P-Spec, and the TDP. The Government will have the final decision on acceptance of all product, system requirements, and test plans for each article delivered and shall be documented IAW CDRL A006 – Acceptance Test Plan. The product acceptance test shall address system and subsystem component requirement verification, in-process inspection, and final acceptance testing at all levels, including lower tier subcontractors and suppliers to include new production, repair, and spares. The product acceptance system shall identify all end items that require individual Acceptance Test Procedures (ATPs) based on the criticality of the item IAW CDRL A006. The product acceptance system shall be approved by the Government prior to testing.

The test plan for all remaining deliveries shall include at a minimum, the requirements marked in Appendix 2 under the Government Acceptance Test column. All items provided shall successfully complete acceptance testing prior to delivery to the Government and prior to use of the item in any test activity. End item ATPs and equipment, including Special Inspection Equipment (SIE) and Special Test Equipment (STE) IAW CDRL A006, shall be validated prior to use for delivery of hardware. The Government shall be given the opportunity to participate in the validation test. The contractor shall prepare validation plans. Changes to acceptance test procedures and/or associated equipment, vendor changes, line relocations, production disruptions, or production downtime shall be reviewed by the Government for determination of re-validation requirements. Acceptance test reports shall be delivered coincident with each SSS delivery IAW CDRL A007 – Acceptance Test Report (ATR).

5.2.4 FIRST ARTICLE TEST

The contractor shall conduct a First Article Test (FAT) of the first unit produced and shall cover, at a minimum, the requirements marked for the FAT in Appendix 2 - Acceptance Test Requirements Matrix and provide the information in CDRL A007 – Acceptance Test Report (ATR).

5.3 ENGINEERING SUPPORT

The contractor shall provide engineering expertise, knowledge, and understanding of the SSS architecture as well as emerging technologies that will directly impact the design, testing, deployment, and implementation of SSS. The Contractor shall provide lifecycle planning and support, system engineering, system integration, system design and development support, and test and evaluation services IAW sections 5.2.1, 5.2.2, 5.2.3,

5.2.4 and 5.4.1 of this PWS.

The applicable delivery documents to the Government shall be specified in the individual

TO/DOs. Applicable documents may include: updates to the TDP, test plans and reports (IAW section 5.2.3), engineering analyses, and task schedules. Efforts under this program may require support in the areas of integrating new sensors, software, or hardware; testing firmware updates and security patches; updating fixtures and cables;

and other miscellaneous equipment or material to accomplish the specific support effort.

The Contractor shall also be required to integrate SSS with IGSSR-C as the C2 node once IGSSR-C is ready to be tested and fielded. This involves using Government provided IGSSR-C hardware and software to ensure that SSS performance requirements will continue to be met. This will also require an evaluation of the Portable Control Station design and a potential upgrade.

5.3.1 INTERFACE CONTROL DOCUMENT (ICD)

When required, the Contractor shall update and deliver all electrical, mechanical, and software ICDs IAW CDRL A008 – Interface Control Document (ICD). Once the Government accepts the ICD, the ICD will be placed under Government Configuration Management (CM) control and can only be changed through Engineering Change Proposals (ECPs).

5.4 OTHER SERVICES

5.4.1 CONFIGURATION MANAGEMENT

The Contractor shall comply with the PM FPS CMP v3.0 and shall maintain a CM Process of which the Government reserves the right to review and approve. The process shall be documented as a Supplier’s Configuration Management Plan, IAW CDRL A009. The SSS TDP, Technical Manuals, and Training Materials will remain under Government CM control and updated through ECPs.

IAW the Contractor’s proposed Configuration Audit Plan, the Contractor shall support a Government led Physical Configuration Audit (PCA) to verify the configuration is in compliance with the product item baselines in order to support production decisions. All drawings, schematics, inter-connect diagrams, operating procedures, and any other associated documentation required to support a successful PCA shall be provided to the Government IAW CDRL A010 – Configuration Audit Plan.

5.4.2 PRODUCTION PROCEDURES

The Contractor shall maintain detailed production assembly procedures and documentation to include assembly instructions in a baseline description IAW CDRL A011– Baseline Description Document.

5.4.3 PRODUCT DATA

The Contractor shall update and maintain Product Data (PD) that accurately reflects the historical and current description of each Configuration Item (CI) in the product baseline, as detailed in the TDP, for the entire length of the contract. A CI is a component of a system that is treated as a self-contained unit for the purposes of identification and change control. PD encompasses all the information necessary for a complete definition of each CI in the product baseline including its design, testing, manufacture, operation, repair, and life cycle support. For all data developed under this contract using Computer-aided Design/Manufacturing/Engineering (CAD/CAM/CAE) software packages, the CAD/CAM/CAE database shall contain the appropriate library parts files, assembly files, three dimensional solid models, drawings, and text files IAW MIL-STD-31000B. The Contractor shall maintain drawings within the TDP for the system IAW ASME Y 14.24 and ASME Y14.100 or other mutually agreed upon format. The drawings shall be consistent with a Production Level TDP IAW CDRL A012 – Technical Data Package and be sufficient to support the procurement, manufacturing, integration, test, and logistics provisioning for SSS.

The Contractor shall also update and deliver to the Government Logistics Product Data to support the updating of Technical Manuals and cataloging of components for life-cycle sustainment IAW CDRL A013 – Logistics Product Data.

Upon request of the Government, the Contractor shall make available all documentation and media generated in the performance of this contract. A data accession list (DAL) shall be delivered IAW CDRL A014 – DAL that identifies internal data generated by the Contractor in compliance with the work effort described in the PWS.

5.4.4 DIMINISHING MANUFACTURING SOURCES AND MATERIAL

SHORTAGES (DMSMS)

The Contractor shall be responsible for minimizing materiel readiness risks and managing obsolescence during the POP to ensure compliance with all performance and contract requirements by providing the Government a Bill of Materials (BOM) and a DMSMS IAW CDRL A015 – BOM for Logistics and Supply Chain Risk Management. The BOM will be delivered with the First Articles. First delivery of the BOM shall be coincident with the first SSS delivery. The Contractor’s responsibility shall include all costs associated with locating part replacements, vendor interface, and engineering efforts.

Diminishing manufacturing sources and material shortage (DMSMS) shall be tracked by the Contractor and the Contractor shall notify the Government of DMSMS loss or impending loss of support, manufacturing sources, or suppliers of items. The Contractor shall establish an obsolescence program that identifies, forecasts, and manages obsolescent parts and deliver a DMSMS implementation plan and management plan IAW CDRL A016 – Diminishing Manufacturing Sources and Material Shortages (DMSMS) Implementation Plan and CDRL A017 - Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan. The delivery of the DMSMS implementation plan and management plan shall coincide with the first SSS delivery. The Contractor shall participate in the Government’s CM Integrated Product Team (IPT) as required. The Contractor shall notify the Government of DMSMS issues via an Obsolescence Alert

Notice IAW CDRL A018.

5.4.5 FAILURE REPORTING, ANALYSIS AND CORRECTIVE ACTION

SYSTEM (FRACAS)

The Contractor shall be responsible for analyzing and correcting failures of the product.

The Contractor shall collect and analyze failure data to determine the cause of equipment failures. The Contractor shall implement a FRACAS for tracking of failures during production, testing, and sustainment. As part of the FRACAS process, the Contractor shall analyze and identify potential patterns or trends of failures and provide corrective actions to the Government IAW CDRL A019 – Failure Reporting, Analysis and Corrective Action Taken.

The Contractor shall submit the Analysis of Defects, Test Plan, Test Report, and supporting documentation IAW CDRL A005 - Failure Analysis and Corrective Action Report.

5.4.6 PRODUCT SUPPORT ANALYSIS (PSA)

To meet DoD program supportability objectives, the Contractor shall assist the Government with PSA efforts as outlined in CDRL A020 - Product Support Analysis. PSA support shall allow the Government to maintain a Life Cycle Sustainment Plan (LCSP) and related logistics support summaries (e.g. repair parts and special tools lists, maintenance allocation charts, provisioning technical documentation, and bill of materials).

5.4.7 CUSTOMER WAIT TIME

Per DoDI 4140.61, the Contractor shall work with the Government to establish acceptable customer wait times (CWT) to support each phase of the contract and TO/DOs. CWT is defined as a measurement of the total elapsed time between the issuance of a customer order and satisfaction of that order. This will include both component repairs and replacement units. Wait times may also be established for surge production requirements at the TO/DO level. The CWT should not exceed 20 work days (four calendar weeks) not including work stop-time variables.

5.4.8 RELIABILITY, AVAILABILITY AND MAINTAINABILITY (RAM)

PROGRAM.

The Contractor shall support the SSS RAM program that encompasses a reliability centered maintenance analysis. The Contractor shall document all depot and field maintenance efforts in Catalog Ordering Logistics Tracking System (COLTS) or other Government directed Integrated Data Environment (IDE) that tracks systems issued/installed, spare parts and maintenance actions. The Contractor shall provide a reliability predictions report IAW CDRL A021, Reliability and Maintainability Predictions

Report; CDRL A022 Reliability-Centered Maintenance (RCM) Analysis Report; DoD 4151.22M These actions shall be negotiated at the TO/DO level.

5.4.9 PROVISIONING

The Contractor shall submit Provisioning Parts Data, IAW CDRL A023, The Contractor shall provide updates to any provisioning data due to design changes.

5.4.10 REACH-BACK SUPPORT

The Contractor shall provide on-call technical services and reach-back SSS support for deployed systems. The Contractor shall provide a central point of contact for all technical support services. The Contractor shall be able to receive support requests 24/7 online such as a web page/chat, email, text messages, or by phone. The service provided shall include, but is not limited to: operations, maintenance, troubleshooting, and hardware support IAW individual TO/DO. Level of effort and response time will be negotiated at the individual TO/DO.

5.4.11 ASSET VISIBILITY

The Contractor shall utilize the COLTS program management suite for providing asset visibility to supply users with timely and accurate information on the location, movement, status, and identity of SSS configurations, fielded systems, equipment, materiel, and supplies. The FPS Program Office will be the single POC for authorizing access, read/write permission levels. The Contractor shall input operational/maintenance status, configuration, location, current system deficiencies, maintenance actions, and a list of components installed per serial number. Spare parts inventories shall also be maintained within COLTS including reorder points for each line replaceable unit (LRU) and tracking of the repair and return process for each LRU. The Field Service Representative (FSR), provided via this contract will be responsible for ensuring COLTS is kept up-to-date with close to real-time information for OCONUS assets.

5.4.12 DEPOT MAINTENANCE STUDY/ORGANIC DEPOT ASSESSMENT

DATA

In accordance with DoD 4151.18-H and DoDI 5000.02, the Contractor shall provide a Depot Maintenance Study with Organic Depot Assessment Data IAW CDRL A024 Depot Maintenance Study. This data will permit the Government to establish complete organic depot-level repair capability for a system, assembly, subassembly, or Depot Level Repairable (DLR). The study shall include the current repair procedures and documentation that the Contractor employs in the factory repair process. The Organic Depot Assessment Data shall contain the depot support elements (i.e. support equipment, facilities, spare parts, software, and training) that are required to implement a depot-level repair program at an organic depot.

5.4.13 HUMAN SYSTEM INTEGRATION (HSI)

As changes to SSS are made, and as required by individual TO/DO, the Contractor shall update the Safety Assessment Report (SAR) that documents the safety risk being assumed prior to test or operation of SSS and identifies all safety features of the hardware design prior to any event where Government personnel/Soldiers operate or maintain the equipment IAW CDRL A025 – Safety Assessment Report (SAR). In order to ensure that SSS presents no uncontrolled safety hazards to personnel, specific controls or precautions to be followed shall be identified that eliminate or reduce hazards to an acceptable level.

5.4.14 TRAINING

A Program of Instruction (POI) along with supplemental training materials was developed during the EMD phase. The Contractor shall maintain and update the POI and any additional training materials after approved CCB changes and as directed not to exceed annually. These updates shall be provided to the appropriate Army Training Center (to be determined (TBD)) along with initial in-person training of the instructors.

The Contractor shall provide any updates to both Operator and Maintainer training material packages for SSS to be delivered with each system IAW CDRL A026– Training Support Package and Training Materials and the TR 350-70 pamphlet. All training materiel shall be provided to the Government and not have any restrictive markings (e.g.

proprietary) to preclude Government distribution.

The Contractor shall identify, plan and implement an integrated strategy to train personnel to effectively operate and maintain the SSS throughout the life cycle. Training and training resources shall encompass the processes, procedures, techniques, equipment and materials used to train personnel in the following roles: (a) System Administrator, (b) Operator (c) Maintainer and (d) Depot Level (Software and Hardware).

The Contractor shall identify training support requirements, obtain or develop training programs for platforms, systems, subsystems or items, and provide training personnel to perform such training, as required by applicable TO/DOs. The Contractor shall develop training manuals and other exercise and training documentation or training aids as required. Electronic training applications such as video teleconferencing and computer-based training shall be employed to enhance the effectiveness of training materials and courses when cost-effective. The Contractor may conduct training for Government personnel to ensure proper operation, repair, maintenance, and testing of platforms, systems, subsystems or items.

5.4.15 TECHNICAL MANUAL UPDATES

The Contractor shall provide any updated technical manuals necessary to support system changes made throughout the life of the contract IAW CDRL A027 – System Technical Manual and MIL-STD 40051. Updates to these documents are required each time there is a change to the form, fit, or function of SSS hardware or software. This includes incorporating changes to operator manuals for GFP hardware and software into the SSS system level manuals.

5.4.16 PROGRAM PROTECTION PLANNING

The tasks listed below shall be performed by the Contractor and will flow down to any subcontractors engaged by the Contractor.

The Contractor shall assist and support the Government in performing a Critical Functional Analysis (CFA) and Critical Program Information (CPI) Assessment on the SSS in order to identify Critical Components (CCs) and CPI. The Government shall provide the Contractor with written guidance referencing implementation of countermeasures to protect CPI, if any is identified. Additionally, the Contractor shall implement Government specified Supply Chain Risk Management Countermeasures to safeguard Government identified CC. The Contractor shall provide a Program Protection Implementation Plan (PPIP) to the Government within 30 days after receiving countermeasures and provide periodic PPIP status reports to the Government IAW CDRL A028 – PPIP. The Contractor shall provide periodic PPIP updates IAW to DI-ADMN- 81306, The Contractor shall support Government execution of Program Protection Surveys.

The Contractor shall provide technical support to the Government PPP process IAW DoDI 5000.02, DoDI 5200.39, DoDI 5200.44, Defense Acquisition Guidebook, Chapter 13, Program Protection Plan, and Key Practices and Implementation Guide for the DoD Comprehensive National Cyber Security Initiative 11 Supply Chain Risk Management.

The Contractor shall demonstrate visibility into the supply chain for CC, understands how supply chain risk can be introduced through those CC, and has implemented or plans to implement countermeasures to mitigate such risks. This requirement shall flow down to all subcontractors.

The Contractor shall develop, document, and update software assurance countermeasures Table 1 below after the Government identifies CPI and CC (Note: P is for planned and A is for actual).

Common Vulnerabilities and Exposures (CVE) information is used to identify, track, and coordinate mitigation activities of the publicly known vulnerabilities in commercial off the shelf (COTS). Programs should use tools during incremental software testing of their commercial and open source packages to scan operational components and the tool can provide an indication of risk.

Common Weakness Enumeration (CWE) catalog captures more than 700 types of weaknesses in code, design, architecture, and implementation.

Common Attack Pattern Enumeration and Classification (CAPEC) is used for the analysis of common patterns of attacks against systems, whether for understanding how attacks are committed, scoping of relevant threats, templates for malicious testing, or as a foil for thinking about the susceptibility of system’s architecture, design, and technical implementation to specific attacks.

CAPEC is a powerful mechanism to capture and communicate the attacker’s perspective, organize the analysis of a system with respect to attacks, and prioritize weaknesses (CWEs) based on the anticipated attack patterns.

Development Process – assurance activities conducted during the development process to mitigate and minimize attacks (For example, threat assessment and modeling, attack surface analysis, architecture and design reviews, application of static and dynamic code assessment tools and services, penetration testing, and red teaming) that the developed system is likely to face when deployed into operation.

Operational System – attack countermeasures and other assurance activities applied within the operational environment (e.g., failover, fault isolation, encryption, application firewalls, least privilege, and secure exception handling) to mitigate attacks against the delivered system and software interfaces, which may include COTS, Government off-the-shelf (GOTS), open source, and other off-the-shelf software.

Development Environment – assurance activities and controls (e.g., access controls, configuration management, and release testing) applied to tools and activities (e.g., compilers, linkers, integrated development environments, run-time libraries, and test harnesses) used to develop and sustain software to mitigate attacks.

Table 1 – Application of Software Assurance Countermeasures (sample) Development Process

Software (CPI & Critical Component)

Static Analysis p/a (%)

Design Inspect

Code Inspect p/a (%)

CVE

p/a

CAPEC

p/a (%)

CWE

p/a

Pen Tes t

Test Coverage p/a (%)

CPI SW

Level I Critical Component SW

Level II Critical

Operational System

Failover Multiple Supplier

Redundan cy (%)

Fault Isolatio n

Least Privileg e

System Element Isolation

Input checking / validation

SW load key

CPI SW

Level I Critical

Level II Critical

Development Environment

SW Products Source Release Testing

Generated code inspection p/a (%)

OEM or Authorize d dealer

List the COTS products used in the software development environment

Compiler Runtime Libraries Automated Test System

Configuration Management System

Database Development Environment Access

Note: “p” is for planned and “a” is for actual.

5.4.17 TRAVEL

Travel may be required to CONUS and/or OCONUS locations. Contractor travel shall be approved in advance by the COR and costs shall be IAW FAR 31.205-46 (Travel costs).

OCONUS locations will be traveled to by Military Air (MILAIR) if available (i.e., deployment from CRC to theater). Contractors may require a theatre clearance and a country clearance for some OCONUS locations. Reimbursable travel costs shall be reported IAW CDRL A001 – Contractor’s Progress, Status, and Management Report.

Locations for CONUS travel may include but are not limited to Fort Belvoir, VA for programmatic and technical meetings, Redstone Arsenal, AL, and Yuma Proving Ground, AZ for testing, and Fort Leonard Wood, MO for testing and training support. OCONUS locations may include any active theaters of operation for the US Military to include Kuwait, Afghanistan, and the Horn of Africa.

6.0 PRODUCTION MATERIALS AND EQUIPMENT

6.1 GOVERNMENT PROPERTY / EQUIPMENT

GFP will be provided as necessary to support individual efforts on this contract. All GFP shall be managed in accordance with applicable Federal Acquisition Regulation (FAR) and Defense Federal Acquisition Regulation Supplement (DFARS) clauses incorporated into this contract. A Government Property Inventory Report IAW CDRL A029 -

Government Furnished Property (GFP) and Contractor Acquired Property Inventory Report, will be submitted to describe the status and inventory data for all Government property accountable to this contract.

6.1.1 SSS EQUIPMENT

The Contractor shall fabricate, test, and deliver SSS equipment to the Government IAW the SSS TDP and the SSS Performance Specification. Effort specifics, including quantity and schedule, shall be administered through individual TO/DOs. Pricing shall be IAW with Section B of the contract.

6.1.2 BAR-CODING, SERIALIZATION, AND LABELING

Contractor shall comply with the SSS IUID Plan (Table 8). The IUID marking label should be provided on all identified parts by the program office. The contractor shall develop a plan and deliver it to the Government IAW CDRL A030 - IUID Marking Plan. Each SSS shall have a sequential and unique serial number, in ascending order, assigned by the contractor and permanently attached in a clearly visible place to each deliverable meeting the requirements of this contract. The Contractor shall provide and affix marking labels by serial number for each repaired or replaced component as delivered after service. All new SSS’s shall be labeled on the outside of the container. All labeling shall adhere to

MIL-STD-130N.

6.1.3 PACKING, HANDLING, STORAGE, TRANSPORTATION, AND

MARKING

The Contractor shall label and pack all hardware deliverables IAW AR 700-15, chapter 2 or best commercial practices to prevent physical damage during shipment to all destinations. Container markings shall be in accordance with MIL-STD-129R. A packing list containing the contract number, serial numbers, and part number for each system/component shall be enclosed in each container listing all items packed therein. A DD Form 1149 indicating Government initial Inspection signed by DCMA or Government personnel shall also be included in the individual pack. All packed items, whether at the system level or consolidated, shall have serial numbers visible to the human eye as well as scanner readable bar-coded serial number information permanently affixed to the outer wrap, ship to/mark for information and serial numbers to aid in asset tracking. The Contractor shall comply with MIL-STD-130N (1), for all contract deliverables. The Contractor shall establish appropriate export and logistics support to ensure minimized delays in product shipments and or logistics delays due to export.

Unless otherwise directed by the Government, the Contractor shall label all items for delivery to the following shipping address:

PM FPS

Attn: Logistics Support Center

POC, 256-763-3076

7425 Warehouse Rd Redstone Arsenal, AL 35898

6.1.4 WARRANTY

All production units shall be delivered with a standard manufacturer warranty. Any commercial warranties offered by subcontractors at any tier shall be passed on to the Government. The Contractor shall establish and maintain procedures to track the warranty start and end date of all products.

6.1.5 SSS SPARES

The Contractor shall provide a proposed spare parts list to include, spare parts, consumables, component parts, field support tooling, test, diagnostic, support equipment, and secondary items IAW CDRL A031 – Proposed Spare Parts List. Support Equipment shall include standard field support diagnostic equipment IAW TB 43-180 Calibration and Repair Requirements for the Maintenance of Army Materiel.

The contractor shall, store and maintain all purchased equipment as identified by the Government. All spares shall be priced to include delivery, acceptance testing, and delivery of acceptance test report IAW CDRL A007 – Acceptance Test Report.

6.1.6 ENVIRONMENTAL, SAFETY, AND OCCUPATIONAL HEALTH

In support of the Government’s overall SSS Environmental, Safety, and Occupational Health (ESOH) program, the Contractor shall implement an ESOH evaluation Program IAW MIL-STD-882E and MIL-STD-810H that will identify, assess, and mitigate ESOH hazards to an acceptable level for the life of SSS. The ESOH program shall evaluate SSS as well as any hardware and software upgrades that may impact ESOH, and shall ensure that ESOH requirements flow down to subcontractors at all tiers.

The Contractor shall perform system safety engineering to ensure that the safety requirements specified in the contract are met IAW MIL-STD-882E. To ensure that safety tasks are suitably completed, the Contractor shall provide qualified personnel to accomplish the required safety tasks, establish the authority for implementing safety tasks through all levels of management, allocate appropriate resources, and establish lines of communication between system safety and other functional elements of the program.

The Contractor should identify all safety features of SSS hardware and software design, specific controls or precautions to be followed during the use of the system, and provide verification of compliance with safety requirements identified in the SSS specifications and IAW CDRL A025 - Safety Assessment Report. The Contractor shall provide required information to support the Government safety release process.

Any hazards that cannot be eliminated should be controlled to an acceptable level.

Electrical, mechanical, and other equipment and health hazards should be controlled IAW industry safety standards. Software operation/failure should not contribute to hazards where it controls potentially hazardous hardware components or presents information used to make critical decisions.

6.1.7 FIELD SERVICE REPRESENTATIVE SUPPORT

As needed, the Contractor shall provide field service representative support while on short and long-term assignment at both CONUS and OCONUS sites. The Contractor shall provide on-site installation, repair, management, maintenance, and test activities directly supporting PM FPS customer base. The Contractor shall read and interpret schematic diagrams, system data flow charts, and technical descriptions of the systems.

The Contractor shall be able to effectively use general and specialized test equipment to check-out and troubleshoot systems. The Contractor shall provide assessments and analysis for viable courses of action to site problems. The Contractor shall track and document the progression of the work utilizing COLTS and be responsible for ensuring COLTS is kept up-to-date with close to real-time information for OCONUS assets. This includes failure data to be used for the FRACAS and RAM process.

The Contractor shall provide technical training to customers based on current developed course materials. Training shall be provided to personnel OCONUS during initial installation and to new personnel upon their arrival to the site. The Contractor shall perform other administrative duties associated with the job, including but not limited to:

electronic expense reports, daily time cards, and Contractor Field Service Reports IAW CDRL A032. Support all system customer equipment including ground station computer network operation and maintenance at various customer locations.

6.1.8 READINESS SUSTAINMENT

Sustainment is defined as the required maintenance, repairs, and technical support required to support the effort and covers the entire system including software, hardware, and all associated electronic and safety systems. The Contractor shall perform all activities required to sustain the SSS major end items and components/subcomponents IAW CDRL A033 – Maintenance Support Plan. The Contractor shall maintain an Operational Readiness (OR) rating of 90% or greater using the following formula: Mission Capable divided by Total number of Systems (OR = MC / TS).

6.1.9 REPAIR, INSPECTION, EVALUATION OF NON-WARRANTY ITEMS

The Contractor shall perform a repair proposal of all non-warranty returned assets or components including an analysis report of the failed item IAW CDRL A019 – Failure Reporting, Analysis and Corrective Action Taken. Proposed repairs should be IAW the Maintenance Allocation Chart (MAC). The repair proposal shall consist of an inspection, repair schedule, failure analysis, and cost. This repair proposal will be provided to the Contracting Officer (KO) / Specialist for resolution. Repairs will be authorized by the

Contracting Officer in writing. If denied, the contractor will be provided disposition instruction for the unrepaired asset.

Maintenance levels are defined in Table 2 below. Field level minor repairs are those that involve isolating the fault to a single LRU and determining if a replacement LRU is needed. The two levels are differentiated by whether the diagnostic can be done by visual inspection or requires connecting a maintenance computer to the system (network).

Once the fault is isolated, the spare LRU is installed and tested. A faulty LRU designated in the MAC for Discard will be disposed of via Defense Logistics Agency-Disposition Services (DLA-DS) in the most economical method. A faulty LRU designated for Depot level repair will be sent back to the Contractor’s facility for further processing. Depot level minor and moderate repairs will be determined by the Contractor to be fixed at the Contract’s facility or returned to the OEM for repair or replacement.

Table 2 – Maintenance Category Descriptions

Category Level of Repair Maintenance to be

Performed Maintenance Details

Government Approval Prior to

Repair (Y or N)

Field Minor

Diagnostics not performed through network.

Installation, Inspection or Fault Isolation, Replace or Test

Discard and replace Replace highest % of time N

Field Minor

Diagnostics performed through network.

Installation, Inspection or Fault Isolation, Replace or Test. No repair required.

Replacement is majority of downtime.

May require frequency syncs

N

Depot Minor 1

Diagnostics not performed through network

Installation, Inspection or Fault Isolation, Replace or Test – No repair required.

Common tools N

Depot Minor 2

Diagnostics performed through network

Installation, Inspection or Fault Isolation, Replace or Test – No repair required.

Common tools May have grounding or electrical safety hazards

N

Depot Moderate 3

Diagnostics not performed through network

Installation, Inspection or Fault Isolation, Repair, Replace or Test

Common tools, moderate repairs

N

Depot Moderate 4

Diagnostics performed through network

Installation, Inspection or Fault Isolation, Repair, Replace or Test

Common tools Requires frequency syncs Y

Depot Moderate

Diagnostics performed through all communications network. May require frequency syncs.

Installation, Inspection or Fault Isolation, Repair, Replace or Test – Direct

Support Unit – (DSU)

Repairs more extensive including wiring and assembly.

Human Factors for

Safety(NATO)

Y

Depot Moderate

OEM Repair Only Installation, Inspection or Fault Isolation, Repair, Replace or Test

TTR Repair highest % of downtime

OEM controls RTAT Y

6.1.10…