W9113M-13-C-0009_S4_DRAFT_PWS.pdf

PRODUCT MANAGEMENT

ELECTRO-OPTIC/INFRARED PAYLOADS-

FORCE PROTECTION

(PM EO/IR-FP)

SURVEILLANCE SYSTEM SUPPLY and SUPPORT

(S4)

PERFORMANCE WORK STATEMENT

(PWS)

for the Rapid Aerostat Initial Deployment (RAID) Configurations

19 May 2017

DRAFT

1.0 INTRODUCTION

2.0 OBJECTIVE

3.0 SCOPE

4.0 APPLICABLE DOCUMENTS

4.1 Specifications, Standards and Army Regulations

4.2 Commercial Standards

5.0 REQUIREMENTS

5.1 Program Management Support of Contractor Requirements

5.1.1 Oversight

5.1.2 Team Participation, Meetings and Data Management

5.1.3 Risk Management Plan

5.1.4 Funding Reports

5.2 Integrated Logistics Support (ILS) Program

5.2.1 Spares

5.2.1.1 Spares Management

5. 2.1.2 Spares Inventories

5. 2.1.3 Limited Life Items

5. 2.1.4 Long Lead (LL) Items

5. 2.1.5 Component Obsolescence

5. 2.1.6 Repair and Return Management

5.2.1.7 Supply Support

5.2.1.8 Storage, Packaging, Shipment of Spare/Consumables for CONUS/OCONUS

5.2.2 Asset Visibility

5.2.2.1 Website

5.2.3 Level of Repair Analysis (LORA)

5.2.4 Provisioning (RESERVED)

5.2.5 Maintenance Allocation Chart (MAC)

5.2.6 Selected Essential-Items Stockage to Availability Method (SESAME) (RESERVED) .. 80

5.2.7 System Support Package (SSP)

5.2.8 Manpower and Personnel Integration (MANPRINT)/Human Factor Engineering (HFE)81

5.2.9 Unique Identification (UID) Descriptive Marking

5.2.10 Training Support

5.2.10.1 Requirements for Operator, Maintenance, and Maintainer Training Courses

5.2.11 TMs

5.2.11.1 TM Verification

5.2.11.2 Requirements for RPSTL

5.3 Engineering and Technical Support

5.3.1 Configuration Management (CM)

5.3.1.1 TDP, Documentation, and Maintenance

5.3.1.2 Configuration Documentation (CD) Numbering

5.3.1.3 Engineering Release of Documentation

5.3.1.4 Engineering Data

5.3.1.5 Change Requests

5.3.1.6 Engineering Change Proposals (ECPs)

5.3.1.7 Commercial Off-the-Shelf/Government Off-the-Shelf (COTS/GOTS) Hardware/Software and Non-Development Items (NDIs)

5.3.2 Quality Assurance (QA)

5.3.2.1 Test and Evaluation

5.3.2.1.1 Product Acceptance Test Plan

5.3.2.2 Reliability, Availability, and Maintainability Program

5.3.2.3 Failure Reporting and Corrective Actions (FRACAS)

5.3.3 System Safety

5.3.3.1 System Safety Program Plan

5.3.3.2 Safety Assessment

5.3.3.3 Hazardous Materials and Environmental Impact

5.3.3.4 Accident /Incident Report

5.4 Security

5.4.1 Operations Security

5.4.2 Information Protection

5.4.3 Information Assurance (IA)

5.5 SME Support

5.6 RESET Actions-RESERVED

5.7 Vehicles…………………………………………………………………………………………… 14

6.0 Government Furnished Property, Equipment or Material (GFP/GFE/GFM) … …………...14

ATTACHMENT A CURRENT RAID SYSTEM CONFIGURATIONS

A. Legacy RAID

1. RAID 09

2. Mobile Eagle Eye II (MEE II)

3. Aerostat Plug & Play Star SAFIRE III (SS III) or Aerostat Plug & Play High Definition 15

B. BETSS-C/RAID

ATTACHMENT B GOVERNMENT-FURNISHED INFORMATION………..…………………….16

1.0 INTRODUCTION

The RAID systems provide a highly effective and efficient 360 degree field of view to in-theater combatant commanders. The various configurations are defined in Attachment A. The RAID systems allow combatant commanders to respond to force protection threats on forward operating bases or other designated areas deemed as an increased threat from improvised explosive device attacks. The RAID systems can be operated in a stand-alone mode, but may be integrated to interface with other sensors and communications and control technologies in order to enhance their protective capabilities for soldiers. These RAID systems fulfill the requirement for an elevated 24/7 persistent surveillance system to provide base security cells with unique, 360°, high-resolution, day and night visual surveillance capability for enhanced target recognition and situational awareness which enables timely and appropriate response options (direct air attack, indirect fire, and ground attack). Within sixty days from award, the contractor shall fully implement their transition plan and be responsible for conducting mission, logistics support of all RAID systems, except for the RAID sensor, standard ground station, and generator components. The contractor shall also provide for program management, engineering, and logistic support for system availability, training, and cost support. The contractor shall perform all engineering, programmatic support, system support activities and analyses. The applicable specifications and standards documents included in the Performance Work Statement (PWS) are specifically the IEEE-1220 standard and engineering/contractor logistics support requirements. The contractor shall support all current and future fielded RAID system configurations deployed in either the Continental United States (CONUS) or Outside Continental United States (OCONUS).

2.0 OBJECTIVE

At a minimum, the contractor shall provide all necessary services in this PWS, spare parts, material, equipment, and personnel in support of RAID systems configurations.

3.0 SCOPE

As further detailed in the PWS and this contract, the contractor shall be responsible for program management support of contractor requirements, integrated logistics support program, systems engineering support, security, and reset actions.

The contractor shall provide all necessary services, spare parts, material, equipment, and personnel to assist management in the support of CONUS/OCONUS supply hubs and maintain sufficient spare parts at a CONUS location(s) for expedited shipping to OCONUS. There are several RAID configurations (see Attachment A) for which the contractor shall be responsible. A conceptual diagram of the system hierarchies for the tower and aerostat based configurations is shown in Figures 1 and 2.

The contractor shall be responsible for maintaining an asset visibility database that tracks all spare parts and maintenance actions, and for providing analysis and reports.

The contractor shall recommend engineering change proposals as data suggests changing parts. When the Government concurs with a part change, the contractor shall update the technical data package, training documents, technical manuals, and other documentation.

The contractor shall provide Subject Matter Experts (SMEs) to maintain systems. The contractor shall assist Field Service Representatives (FSR) at CONUS and OCONUS locations.

Figure 1 RAID: Tower System Hierarchy RAID System

Platform

Tower

Conex

80 Ft

107 Ft

Sensors

Communications

Power

C2 A1, A2, A3

TFU

LCU

ECU

MSTAR Radar

Wired

Wireless Radio

TQGs

UPS

Shore

Computers Operator Controls

Displays

Messaging

Map Software

Radar Software

Sensor Controls

LCU

Strobes

Map

Video

SS III

AHA

MEA

All Items Color Coded Gray are not part of this Contract

(SGS-no)

RAID AEROSTAT

System

Platform

Mooring Station

20’ Conex

Trailer

Tether

Payload

Communications

Power

C2 A1, A2, A3

IRU

ECU

Wired

Wireless Radio

TQGs

UPS

Shore

Computers Operator Controls

Displays

Messaging

Map Software

Radar Software

Sensor Controls

LCU (SS III)

Strobes

Map

Video

14’ C2 Shelter

AEROSTAT Bag

Journey Video

TFU

LCU

ECU

SS III

All Items Color Coded Gray are not part of this Contract

(SGS-no)

RAID AEROSTAT

System

Platform

Mooring Station

20’ Conex

Trailer

Tether

Payload

Communications

Power

C2 A1, A2, A3

IRU

ECU

Wired

Wireless Radio

TQGs

UPS

Shore

Computers Operator Controls

Displays

Messaging

Map Software

Radar Software

Sensor Controls

LCU (SS III)

Strobes

Map

Video

14’ C2 Shelter

AEROSTAT Bag

Journey Video

TFU

LCU

ECU

SS III

APTU

Figure 2: Aerostat System Hierarchy

4.0 APPLICABLE DOCUMENTS

The following specifications and standards form a part of this document to the extent specified herein. Unless otherwise specified, the versions of these documents will be applicable, in effect at the time of contract award;

however, the contractor shall be responsible for monitoring all applicable specifications and standards and to inform the procuring contracting officer for possible contract change. Army Regulation 25-2, DoDD 8500.1, and DoDD

8500.2. A list of Government-Furnished Information (GFI) is provided in Attachment B.

4.1 Specifications, Standards and Army Regulations

The following Specifications and Standards are applicable.

STANDARD TITLE

MIL-STD-40051-2 Department of Defense Standard Practice: Preparation of Digital Technical

Information for Page-Based Technical Manuals MIL-STD-130 DOD Standard Practice Identification Marking of US Military Property MIL-STD-882 System Safety MIL-HDBK-61 Configuration Management Guide MIL-HDBK-217 Reliability Prediction of Electronic Equipment MIS-STD-52406-IS Interface Specification for System Interface Requirements for

Engineering Data AR 700-127 Integrated Logistics Support Army Regulation 25-2 Information Assurance DOD 5220.22 National Industrial Security Program (NISP) DODD 8500.1 Information Assurance DODD 8500.2 Information Assurance Implementation PL 91-190 National Environmental Policy Act RAID SCG (20081223) RAID Security Classification Guide Army Pamphlet 700-56 Logistics Supportability Planning and Procedures in Army Acquisition National Industrial Security Program Operating Manual (NISPOM)

4.2 Commercial Standards

The most recent versions of these documents apply. The contractor shall obtain these documents from commercial sources:

IEEE-1220 Application and Management of the Systems Engineering Process ANSI/GEIA-STD-0009 Reliability Program Standard for Systems Design, Development and

Manufacturing ISO 9000 Quality Management Systems

5.0 REQUIREMENTS

The contractor shall provide the capability to perform a wide variety of tasks as defined in this PWS. The contractor shall be capable of providing flexible, responsive management, systems analysis, technical support, necessary personnel, and Other Direct Costs (ODC) such as, but not limited to travel, material, equipment, supplies, ancillary services, and other OCONUS expenses relating to the requirements set forth in this PWS.

5.1 Program Management Support of Contractor Requirements

5.1.1 Oversight

The contractor shall perform program management to ensure all activities are planned, coordinated, controlled, scheduled, monitored, managed, and reported. The contractor shall support and attend meetings, review documents, and make recommendations.

5.1.2 Team Participation, Meetings and Data Management

The contractor shall hold a program kick-off event with Government participation thirty (30) days after contract award.

The contractor shall provide SMEs to participate in Integrated Product Process Development (IPPD) and Integrated Product Teams (IPTs) in support of all engineering, logistics, and programmatic requirements. The contractor shall host/ participate in the quarterly Sustainment IPT (SIPT) meeting, monthly Failure Reporting, Analysis, and Corrective Action System (FRACAS) IPT meeting, and others as determined by the program/delivery schedule.

The contractor shall provide recommendations to the Government to ensure the accurate and successful completion of system support objectives and other engineering, technical, and configuration requirements. The contractor shall provide minutes of meeting for all sponsored IPPD/IPT meetings NLT 5 days after meeting close-out. In all cases, the contractor shall furnish a copy of minutes of meetings IAW DI-MISC-80508B (CDRL A001). The contractor shall participate in telecoms, briefings, and meetings as required. The contractor shall prepare and maintain a program/delivery schedule DI-MGMT-81650 (CDRL A002) that includes key milestone transitioning dates.

5.1.3 Risk Management Plan

The contractor shall submit and implement a Risk Management Plan IAW DI-MGMT-81808 (CDRL A003). At a minimum, the contractor shall support, implement, and maintain a cost, technical and schedule risk management process that includes risk detection and identification, assignment of risk categories, corrective action, tracking of compliance, reporting of status, and planning for risk abatement. The contractor shall participate in a monthly telephonic Risk Management IPT that includes participation from the contractor and government personnel to ensure all risks and issues are categorized, communicated, and addressed in the most expeditious and efficient manner. In the event that risks arise that cannot be dealt with in a timely fashion, either the Government or the contractor can request additional IPT meetings.

5.1.4 Funding Reports

The contractor shall prepare a Contract Performance Report (CPR) and a Contract Funds Status Report (CFSR) and submit monthly IAW DI -MGMT-81466 and DI-MGMT-81468, respectively (CDRL A004) (CDRL A005). The CPR and the CFSR will identify, maintain and report separate lines for all RAID configurations. The CPR shall consist of five formats containing data for measuring contractor cost and schedule performance. The contractor shall provide a validated Earned Value Management System. The contractor shall maintain costs at the component level for each RAID configuration and provide cost reporting at level four of the WBS and lower levels selected for high-cost and risk areas.

5.2 Integrated Logistics Support (ILS) Program

The contractor shall submit an ILS management plan (ILSP) IAW DI-ILSS-80095 (CDRL A006) that describes how the ILS elements as listed in AR 700-127 will be managed. The ILSP shall describe how Logistics Management Information (LMI) will be managed and documented to support requirements.

5.2.1 Spares

5.2.1.1 Spares Management

At a minimum, the contractor shall manage all inventories, warranty considerations, and new technology insertion and replacement factors, including analysis of parts inventories, to support requisitions from field personnel to maintain and forecast required stock levels at the CONUS and OCONUS supply hubs.

5. 2.1.2 Spares Inventories The contractor shall identify and supply the required quantities of spare parts inventories to ensure minimal down time (Non-Mission Capable status) resulting from repair activities. The contractor shall maintain an Order to Ship time by USG designated location of no more than 72 hours for critical spares that are at zero balance, 120 hours for critical spares that reach the reorder point and 240 hours for non-critical spares and consumables. The contractor shall include inventory, warranty considerations, and new technology replacement factors in the forecast analysis of parts inventories.

5. 2.1.3 Limited Life Items The contractor shall update as required a Government provided list of limited life items IAW DI-MISC-80508B

(CDRL A007).

5. 2.1.4 Long Lead (LL) Items The contractor shall identify and maintain a LL Item List for the RAID configurations to facilitate advanced ordering to support future mission requirements IAW DI-MGMT-80797 (CDRL A008). LL items are those items that require a procurement lead time exceeding 90 days. The contractor shall use supply chain response time as a key measure in determining the quantity of each item required in the supply pipeline to minimize weapon system non mission-capable rates.

5. 2.1.5 Component Obsolescence

The contractor shall establish an obsolescence program that identifies, forecasts and manages obsolescent components for all RAID configurations. The contractor shall provide recommendations on component replacements that provide equal or better performance. The contractor shall prepare, maintain and deliver a listing of obsolete items by RAID configurations IAW DI-SESS-81656 (CDRL A009).

5. 2.1.6 Repair and Return Management The contractor shall manage and provide for the repair and return of the following items: Man Portable Surveillance, Targeting, Acquisition Radar (MSTAR) sub-components Main Electronic Assembly (MEA) 599505-1 and Aerial Head Assembly (AHA) 599502-1, Inertial Reference Unit (IRU) GE AVIATION PN - 174350-31-01, Aerostat bag TECOM PN-3D15889G01, Aerostat Power and Telemetry Unit (APTU) TECOM PN-3D15985G01, tether TECOM PN- 3D16151G03, telemetry computer TECOM PN- 3D17291G02, and tensiometer OPTI - Manufacturing Corporation PN- T5-8005-110-00.

5.2.1.7 Supply Support

The contractor shall acquire, receive, store, issue, ship and dispose of spares, repair parts, and supplies for all fielded RAID configurations. The contractor shall track and notify the Government of diminishing manufacturing sources and materiel shortages or loss or impending loss of manufacturing sources, or suppliers of items on items required to repair or build RAID systems.

5.2.1.8 Storage, Packaging, Shipment of Spare/Consumables for CONUS/OCONUS The contractor shall use best commercial practices to provide safe storage, packaging, and transportation of all spares and consumables within CONUS and to OCONUS (OIF and OEF) regional support centers (RSCs). The contractor shall obtain all required Export Licenses. The contractor shall also comply with all applicable U. S.

Government host nation or third country agreements, country clearances, theater business clearances and combatant commander orders, policies, and directions. The contractor shall ship all items utilizing the most expeditious mode of transportation to support in-theater high demand requirements for spares assets.

5.2.2 Asset Visibility

The contractor shall provide an unclassified website that provides asset visibility that will supply Contract Officer Representative (COR) approved Government and contractor users with timely and accurate information on the location, movement, status, and identity of Legacy RAID and BETSS-C family of systems configurations, fielded systems, equipment, materiel, and supplies and re-supply actions/status to include repair and return items. The website shall have a secure log-in (i.e., https:). The website shall be near-real-time scalable architecture (i.e., an architecture that has the ability to grow or expand as the quantity of systems included in the database increases without performance degradation) design that will provide complete, integrated visibility of RAID assets and other logistics data. The PM Electro-Optic/Infrared Payloads-Force Protection (PM EO/IR-FP) Office will be the single POC for authorizing access, read and write permission levels and website configuration changes. The contractor shall be responsible for training government and contractor personnel as needed to enable them to interface with the database website.

5.2.2.1 Website

The contractor shall provide and maintain a website that is fully accessible to individuals authorized by PM EO/IR- FP. Website support personnel shall be available to provide flexibility to modify and tailor the system to support evolving requirements. The website shall have multi level access capabilities.

At a minimum, the contractor shall provide a website that tracks at the system level the following: operational and maintenance status, configuration, location, current system deficiencies, maintenance actions, and a list of components installed per serial number. The website shall have a capability to track helium inventory and track helium trailers by their serial number at each Aerostat site in order to monitor stock levels and Defense Logistics Agency (DLA) trailer turn-ins. The FSR, provided by means of a separate contract, will be responsible for ensuring the website is kept up-to-date with helium and trailer information for OCONUS.

The website shall provide capability to maintain spare parts inventories for numerous supply hub locations in both OCONUS and CONUS. The website shall provide search and filter capability for all supply hub locations. The website shall retain reorder points for each Line Replacable Unit (LRU), repair part, consumable, and Repair Parts and Special Tools List (RPSTL) IAW the system Technical Manual (TM). The website shall retain reorder points and automatically report parts at or below the reorder point. The website shall track LRU replenishment from purchase orders to receipt at the supply hub locations. The website shall track repairable LRUs through each step of the repair and return process. The website shall document each step of the repair and return process in days for each

LRU.

The website shall provide a host to upload shared files and allow the FSRs to maintain a point of contact list for systems to include names, phone numbers and emails. The website shall provide a means to extract FRACAS data and system performance factors, such as system status trends and Operational Readiness (OR) trends.

The database shall also provide the following capabilities:

Tiered levels of maintenance instruction and corresponding reference documentation Ease of software updates and system back-up.

Database robustness with at least 50% growth margin expandable to meet future RAID missions.

Track maintenance actions, provide status from the time a maintenance action is received until it is closed out, and maintain history of those actions.

Conform to OPSEC regulations.

Build custom reports via Microsoft Excel Exportable data via Microsoft Excel (e.g., CSV and Tab-Delimited. ) Maintain a 95% website operational availability with 24/7 IT support

5.2.3 Level of Repair Analysis (LORA)

The contractor shall maintain, update, and submit a LORA IAW DI-ALSS-81530 (CDRL A010), as the system configurations or spare parts change. The contractor shall recommend the most cost-effective repair strategy.

Contractor shall provide data in a format that is compatible with Government-approved model Customized Optimization Model for Predicting and Analyzing Support Structure (COMPASS).

5.2.4 Provisioning (RESERVED)

5.2.5 Maintenance Allocation Chart (MAC)

The contractor shall maintain, update, and submit the MAC, or MACs, IAW MIL-STD-40051-2, and deliver IAW DI-MISC-80711A (CDRL A011), as configuration and/or maintenance concepts changes. The MAC(s) shall identify the maintenance functions that must be performed, the maintenance levels responsible for the functions, and the active repair time, tools, and test equipment necessary to perform the functions for each repairable assembly and subassembly of the end item affected.

5.2.6 Selected Essential-Items Stockage to Availability Method (SESAME) (RESERVED)

5.2.7 System Support Package (SSP)

The contractor shall maintain, update, and submit the SSP Component List (SSPCL) IAW DI-ALSS-81530 (CDRL A012), as the system configuration or spare parts change. The SSPCL shall be worked through the IPT process and shall be made available at program reviews and validation/verifications.

5.2.8 Manpower and Personnel Integration (MANPRINT)/Human Factor Engineering (HFE)

RESERVED.

5.2.9 Unique Identification (UID) Descriptive Marking

The contractor shall provide UID markings or DOD recognized unique identification equivalent, for all items delivered with an acquisition cost of $5000 or more. UID markings shall be IAW the latest MIL-STD-130 and IAW

DI-MGMT-80177B (CDRL A014).

5.2.10 Training Support

The contractor shall update Government provided training packages and deliver updated training packages IAW DI- SESS-81521B (CDRL A015) for the asset visibility website and all current and future fielded RAID system configurations to include components of these systems that are required by an approved ECP/Modification Work Order process.

5.2.10.1 Requirements for Operator, Maintenance, and Maintainer Training Courses

The contractor shall provide new equipment training for Operator and Maintenance, and Maintainer Training Courses materiel for approved ECP/Modification Work Order process IAW DI-ILSS-80872 (CDRL A016) and training program structure document IAW DI-SESS-81521B (CDRL A017). The courses shall be conducted at Government facilities unless otherwise directed by the Contracting Officer.

5.2.11 TMs

The contractor shall update Government provided TMs and deliver updated operator and maintenance manuals for RAID configurations including COTS items and GFE, IAW DI-TMSS-81677A (CDRL A018).

5.2.11.1 TM Verification

The contractor shall perform TM validation and provide technical support during the Government TM Verification Process and provide a sufficient number of copies for each technical manual validation and verification.

5.2.11.2 Requirements for RPSTL

The contractor shall update Government provided RPSTLs and deliver updated RPSTLs and update as configurations change and/or spares are replaced IAW DI-MISC-80711A (CDRL A019).

5.3 Engineering and Technical Support

The contractor shall provide engineering expertise and technical support necessary to maintain the asset visibility website and parts/component obsolescence. At a minimum, the contractor shall maintain Technical Data Packages (TDPs), and as necessary redesign of components to ensure continued functioning of the system. This effort shall include support to the Government in the allocation of system specification/interfaces, design, development, fabrication, qualification, acceptance testing, verification, anomaly resolution, risk management, system analysis, trade studies, maintenance and support using IEEE-1220 as a guide. The contractor shall submit and implement a systems engineering management plan IAW DI-SESS-81785 (CDRL A020).

5.3.1 Configuration Management (CM)

The contractor shall develop, implement and maintain a CM program using MIL-HDBK-61A as a guide and submitted IAW DI-CMAN-80858B (CDRL A021). The CM program shall maintain and update Government provided Technical Data Packages (TDPs). The contractor’s CM plan shall address the topics described below.

5.3.1.1 TDP, Documentation, and Maintenance

The contractor shall maintain the TDP, including technical writing, drafting, checking and verifying. The contractor shall provide technical assistance in performing TDP reviews and configuration audits.

5.3.1.2 Configuration Documentation (CD) Numbering

The contractor shall provide configuration documents with the AMCOM CAGE Code (18876). The Government will provide the drawing and ECP numbers. The contractor shall furnish the Notices of Change (NOC) or Engineering Change Notices (ECN) numbers.

5.3.1.3 Engineering Release of Documentation

The contractor shall prepare an Engineering Release Record (ERR) IAW DI-CMAN-80463C (CDRL A022).

5.3.1.4 Engineering Data

The contractor shall prepare and deliver all engineering data, drawings, associated lists, specifications, classified data and all other deliverable data IAW DI-SESS-81000C (CDRL A023). At a minimum, the contractor shall deliver engineering data, drawings, associated lists, specifications, calibration procedures, and other data that define the RAID system hardware IAW MIS-STD-52406-IS. The contractor shall mark and control all documentation containing classified documentation IAW DOD 5220.22-M. Classified documentation shall not be transmitted electronically.

5.3.1.5 Change Requests

The contractor shall submit Class I change requests for approval. A Class I change is defined as a change that affects form, fit and function or incurs a cost impact that exceeds $25,000.00. The contractor shall implement Class II changes with no additional cost to the contract. A Class II change is defined as a change that does not affect form, fit and function. Class II changes shall be submitted to Government to verify the classification.

5.3.1.6 Engineering Change Proposals (ECPs)

The contractor shall prepare and submit ECPs and Notices of Revision (NORs) IAW DI-CMAN-80639C and DI- CMAN-80642C, respectively (CDRL A024) (CDRL A025). The contractor shall prepare ECPs on DD Forms 1692 thru 1692-7. The contractor shall prepare NORs on DD Form 1695. The contractor shall submit Request for Deviation/Waivers IAW DI-CMAN-80640C (CDRL A026). The contractor shall obtain approval prior to implementation. The contractor shall initiate separate change proposals for common documentation (i.e., documentation used by other systems, commands, or services).

5.3.1.7 Commercial Off-the-Shelf/Government Off-the-Shelf (COTS/GOTS) Hardware/Software and Non- Development Items (NDIs) The contractor shall maintain the COTS and GOTS/NDI baseline configurations for all systems. The contractor shall maintain Commercial Items Descriptions (CIDs) which define the requirements by form, fit, function, and interface and that duplicates the supplier data sheet information.

5.3.2 Quality Assurance (QA)

The contractor shall implement aquality program plan that extends to subcontractors/ suppliers/vendors. The contractor shall submit the Quality Program Plan (QPP) IAW DI-QCIC-81722 (CDRL A027).

5.3.2.1 Test and Evaluation

The contractor shall conduct system, subsystem or component level testing including hardware and software functional verification testing, acceptance testing, qualification/re-qualification testing, and regression testing. The contractor shall submit test plans and procedures IAW DI-SESS-81704 (CDRL A028). The contractor shall identify the Government assets required to support internal testing not later than thirty (30) days prior to testing. The contractor shall deliver and maintain a master listing of all equipment selected for acceptance inspection and tests IAW DI-MISC-80711A (CDRL A029). At a minimum, the listing shall include: (1) equipment description (brand, model and serial number); (2) the corresponding product characteristic(s) the equipment measures or tests; and (3) a crosswalk between each piece of inspection and test equipment and the corresponding product specification.

5.3.2.1.1 Product Acceptance Test Plan

The contractor shall submit and implement a product acceptance test plan that demonstrates compliance with the system requirements IAW DI-NDTI-80603 (CDRL A030).

5.3.2.2 Reliability, Availability, and Maintainability Program The contractor shall develop, implement, and deliver a Reliability, Availability, and Maintainability (RAM) plan IAW DI-SESS-81613 (CDRL A031). The contractor shall submit all RAM support data IAW DI-RELI-81497 (CDRL A032). At a minimum, the following shall be part of the contractor’s RAM effort:

System and subsystem reliability assessments and projections based on Original Equipment Manufacturer (OEM) information, and field reports Reliability predictions based on MIL-HBK-217F Ground Mobile Environment Results of current problems, failure investigations, and engineering analysis Preventive and corrective action recommendations based on production and field failures addressing reliability drivers Potential design problems based on the preventive and corrective action.

Recommendations for reliability improvements to the production baseline Mean Time Between Failures analysis Mean Time To Repair analysis Mean Turn Around Time from fault device failure to return to stock

5.3.2.3 Failure Reporting and Corrective Actions (FRACAS)

The contractor shall establish and implement, or continue to comply with existing, proactive closed loop FRACAS for managing failure reporting, failure trends, failure analyses, corrective action implementation, review, and closure processes. The FRACAS system shall be applied to both hardware and software. The FRACAS system shall be documented in the Quality Program Plan. The contractor shall present a status summary of reliability FRACAS activity at all Failure Review Boards (FRBs), FRACAS meetings, RAM IPTs, and other Government reviews as required. The contractor shall prepare and deliver Reliability Failed Item Analysis Reports and/or Failure Summary and Analysis Reports IAW DI-RELI-80255 (CDRL A033).

5.3.3 System Safety

5.3.3.1 System Safety Program Plan

The contractor shall develop, submit, and implement a System Safety Program Plan IAW DI-SAFT-81626 (CDRL A034) MIL-STD-882, as a guide.

5.3.3.2 Safety Assessment

The contractor shall identify, classify and document safety, health, and environmental hazards in a Safety Assessment Report (SAR) DI-SAFT-80102B (CDRL A035). The contractor shall evaluate all Engineering Change Proposals (ECP), Request for Deviations (RFD) and Request for Waivers (RFW) for safety, health and environmental impacts.

5.3.3.3 Hazardous Materials and Environmental Impact

The contractor shall perform an Environmental, Safety, and Occupational Health (ESOH) analyses to evaluate the requirements in the areas of National Environmental Policy Act (NEPA)(PL 91-190); Environmental Compliance, System Safety, and Health; Hazardous Materials, Pollution Prevention and Explosive Safety. The ESOH analyses shall be used to integrate environmental considerations into the production engineering process. All contractor and subcontractor activities shall be in compliance with applicable Federal, State, and local environmental laws and regulations. The contractor shall ensure that design, maintenance, operation, manufacturing, programmatic decisions, and trade-off studies strive to eliminate or reduce hazardous materials and wastes. The contractor shall prepare a Hazardous Materials Management Program (HMMP) Plan in accordance with DI-MGMT-81398A (CDRL A036). The contractor shall not use substances listed in Emergency Planning and Community Right-to-Know Act (EPCRA) Section 313 "toxic chemicals" and EPCRA Section 302, "extremely hazardous substances", or products containing such substances, without Government approval. The contractor shall request approval to use substances identified in the Environmental Protection Agency 17 - list only if there is no other viable material. The contractor shall not use any Class I Ozone Depleting Chemical/Ozone Depleting Substance (ODC/ODS) in the manufacture of items required by this SOW, unless a waiver is obtained from the Government. The contractor shall provide immediate notification of any proposed hazardous material mitigation/elimination efforts that may adversely impact schedules and/or cost, or performance. The contractor shall prepare and deliver an annual HMMP Progress Reports

IAW DI-MISC-81397A (CDRL A037).

5.3.3.4 Accident /Incident Report

The contractor shall provide Accident/Incident Report IAW DI-SAFT-81563 (CDRL A038).

5.4 Security

The contractor shall be required to have a SECRET facility clearance with SECRET safeguarding capability limited to two cubic feet. The contractor will require access to COMSEC information, Non-SCI Intelligence Information, NATO, and For Official Use Only (FOUO) information. The contractor shall also require access to Security Classification Guide(s) (SCG). In performing this contract, the contractor shall receive and generate classified material. The contractor shall be required to have access to classified U.S. Government information overseas.

5.4.1 Operations Security

The contractor shall submit and implement an Operational Security (OPSEC) Plan IAW DI-MGMT-80934A (CDRL A039).

5.4.2 Information Protection

The contractor shall safeguard information in their custody or under their control IAW the current National Industrial Security Program Operating Manual (NISPOM) and applicable Security Classification Guides.

5.4.3 Information Assurance (IA)

The contractor shall submit and implement a System Security Plan (SSP) IAW DI-MISC-80711A (CDRL A040).

Information Assurance shall be implemented at contractor facilities in accordance with Army Regulation 25-2, DoDD 8500.1, and DoDD 8500.2.

5.5 SME Support

When the Government directs, the contractor shall provide Subject Matter Experts (SMEs) to maintain systems at CONUS and OCONUS locations. The contractor shall provide SMEs to support, at a minimum, test events, training, demonstrations, and augment FSRs.

5.6 RESET ACTIONS RESERVED.

5.7. Vehicles

Under this contract, vehicles are required to support contractor operations at OCONUS locations in order to provide service and/or repair at the individual approved locations/installations. The Government will identify all contractor vehicle requirements during performance of the contract. If the lease or purchase of a vehicle is required, the contractor shall provide the OCONUS COR and the Contracting Officer with a cost estimate that also contains three vendor quotes for OCONUS COR’s review and/or approval. One of the three vendor quotes submitted shall be sourced from the GSA Fleet Management Center. The contractor shall not enter into any leasing agreements until written approval has been provided by the Contracting Officer. Consistent with a lease purchase analysis; and, because of the limited period of performance; the need for flexibility to increase or decrease the number of vehicles in accordance with mission requirements; and the lack of vehicle service centers on the assigned bases, the Government will not entertain an option to purchase vehicles to support the transportation requirements.

For any contractor leased vehicles other than GSA leased, the contactor shall maintain a record of statistical usage data such as fuel, mileage, and any maintenance or repair costs not covered by the contractor’s rental / lease agreement. The contractor and Government will jointly agree to a format for tracking the required data. The Government will provide Government owned vehicles in Afghanistan or allow on-garrison registration of contractor leased vehicles to meet mission requirements at OCONUS COR approved locations where contractors are stationed.

In Afghanistan, fuel and related petroleum products will be provided by the Government at no cost to the contractor.

Contractor’s cost estimates should specifically call out that no fuel costs are included. GSA leased vehicles must follow GSA report guidelines.

The Government’s overall objective is to ensure only the minimum number of vehicles required for mission execution are leased. A planning factor of one leased vehicle for every four contractor personnel assigned is preferred; however, exceptions are allowed for Mission vehicles in Afghanistan, per the approval of the OCONUS COR. For example, the contract originally planned for only three contractor personnel per location, and there could be a need for the individuals to travel simultaneously to different points within the same location or to require different makes / models of vehicle for specific purposes, thus necessitating a higher ratio of vehicles. Leased vehicles shall be used for Mission Requirements only, and shall, under no circumstances, be used for travel between place of duty and abode (on-or-off-installation) unless such use has been approved by the Procurement Contracting Officer.

6.0 Government Furnished Property, Equipment or Material (GFP/GFE/GFM)

Government property is all property owned or leased by the Government and includes both Government-furnished property and contractor-acquired property. Government property includes material, equipment, special tooling, special test equipment, and real property. Contractor shall acquire leased vehicles solely for Mission use. Vehicles leased for mission support other than GSA vehicles are not considered GFP and should not be managed as such.