Attachment_2_-_FPS3_PWS_05_Dec_13.docx

ATTACHMENT 2

PERFORMANCE WORK STATEMENT (PWS)

FOR

FORCE PROTECTION SITE SECURITY SYSTEM (FPS3)

5 DECEMBER 2013

i

TABLE OF CONTENTS

Section Page

1.0 INTRODUCTION 1

2.0 PURPOSE 1

4.0 ACRONYM LISTING 9

FOR OFFICIAL USE ONLY

1.0 INTRODUCTION

The Force Protection Site Security Systems (FPS3) contract provides for acquisition, upgrade and sustainment of a family of Integrated Base Defense Security Systems (IBDSS). These systems provide electronic capabilities to support and enhance security and assist Security Forces (SF) in protecting assets and personnel at nuclear and non-nuclear fixed and tactical sites around the world. The goal is to provide SF with the capability to "See First, Understand First, and Act First."

2.0 PURPOSE

This PWS supplements the FPS3 Statement of Work (SOW) and describes the scope of effort for services that may be required by the Contractor via Delivery Orders (DOs) issued under the FPS3 contract. The scope of this PWS effort is to acquire a broad range of Performance Based Logistics support provided by the contractor including, but not limited to, Interim Contractor Support and Contractor Logistics Support. The contractor shall provide logistics support and sustainment tasks necessary to repair sustain and maintain operationally fielded IDS systems at fixed and tactical installations worldwide. The contractor shall maintain/sustain fielded IDS systems/equipment/software, associated ancillary equipment, and infrastructure required by the DO. Sustainment support shall include but not be limited to maintenance, repair and/or replacement of equipment, management of OEM depot repair of equipment, technical support, sparing to support CLS/ICS activity, training, warehouse and inventory management, preventive maintenance inspection, and other sustainment and maintenance services as may be required by the specific Delivery Order.

3.0 CONTRACTOR PERFORMANCE REQUIREMENTS

3.1 Sustainment Support: As required by the Government, the contractor shall provide sustainment support including Interim Contractor Support (ICS) or Contractor Logistics Support (CLS) as part of a project DO or a separate DO. If ICS/CLS is required, the level of support and performance objectives will be identified in the applicable Delivery Order PWS. If ordered, the Contractor shall establish and maintain a sustainment support activity to sustain fielded systems located at CONUS and overseas locations in accordance with the requirements of the specific DO. The Contractor shall maximize the use of automated systems in order to track and report all sustainment and logistics support activity. These systems shall allow rapid query of fielded configurations and sustainment activities to facilitate field support, asset accountability, and technical support activities. Specific sustainment functions shall consist of, but not be limited to:

· Supply chain, inventory management, and sparing

· Technical or commercial manuals, data, and troubleshooting guides

· Organizational Level Maintenance (i.e., on-site)

· Organizational level training and training materials (operations, maintenance and system administration)

· Preventative maintenance and inspection

· Management depot level activity to repair or replace failed items through the Original Equipment Manufacturer (OEM) or the government organic depot (as applicable)

· Management of warranties

· Technical support

· Software support

· Engineering analysis for security systems and equipment when requested, to include, but not limited to, the identification and resolution of reliability, availability, maintainability and technology obsolescence issues

· Resident field engineering, maintenance and/or operations system administration support

· Help Desk

· Warehouse management

3.2 Sustainment Services Performance Levels:

If ICS/CLS is required on a particular DO, the level of support and performance objectives will be identified in the DO SOW/PWS, and may include the following:

The contractor shall provide tailored, cost effective ICS/CLS. Contractor personnel supporting the Help Desk and on-site maintenance activity must have appropriate certifications required by OEMs to repair/replace/reprogram/reconfigure system equipment and shall provide verification of certifications to the government. The contractor shall report in accordance with applicable CDRLs.

The contractor shall implement ICS/CLS in a manner that ensures response and repair times IAW Maintenance Response Time Thresholds (Table 1) and Maintenance Repair Time Thresholds (Table 2) identified below.

The contractor shall also assist in and coordinate transition of system sustainment responsibility to the applicable base IDS sustainment contractor to facilitate seamless transfer of system sustainment/maintenance support at the conclusion of the ICS/CLS period of performance.

The contractor shall furnish all required services, labor, tools, material, and equipment necessary to provide Organizational Level ICS/CLS for the installed system (the installed system includes all contractor furnished and installed equipment and systems, integrated GFE and contractor provided infrastructure).

3.2.1 Organizational Level. Organizational level maintenance consists of equipment fault determination/fault isolation to the Line Replaceable Unit (LRU), removal and replacement of the failed LRU, and performing scheduled on-equipment preventive maintenance. The contractor shall identify and conduct preventive maintenance recommended by the product manufacturers to enable the most efficient continuous operation. Malfunctioned components beyond the organizational level capability to repair shall be returned for depot repair.

3.2.2 Help Desk. The contractor shall provide telephonic and onsite support. The contractor shall return Government telephone calls for assistance within one hour of Government notification to assess system failures as catastrophic, major malfunction, or partial failures, and to begin the resolution of the problem(s). The base will identify the category of failure. The contractor shall have up to a maximum of four (4) hours to resolve the problem via telecom. If the contractor is unable to resolve the problem within this four hour period, the contractor shall respond with on-site assistance in accordance with the response and repair time identified below to restore the system to operations.

3.2.3 On-Site Repair/Maintenance. When the failure persists, and cannot be resolved via telephonic means, the contractor shall be on-site to resolve the problem within maintenance response time thresholds (Table 1) below and shall restore the system to operations within the maintenance repair thresholds (Table 2) identified below.

TABLE 1. Maintenance Response Time Thresholds

The contractor shall restore the system/equipment to operational status within repair times identified below. The repair time threshold (Table 2) shall be calculated from the time of the initial telephonic contact with the Government in response to a Government call for assistance.

TABLE 2. Maintenance Repair Time Thresholds

3.2.4 Depot Level. The contractor shall manage Depot Level ICS/CLS repair activity and shall furnish all required services, labor, tools, material, and equipment necessary to manage and provide Depot Level ICS/CLS for all contractor furnished and installed equipment and systems, integrated GFE, and contractor provided infrastructure. Depot level maintenance shall consist of the activities described below:

a. The contractor shall return failed investment items (e.g., equipment, line replaceable units (LRU), and system replaceable units (SRU)) to the OEM or the Government organic depot for repair or replacement as appropriate.

b. The contractor shall maintain a list of original equipment manufacturer (OEM) vendors to supply replacement parts and equipment.

c. The contractor shall track Return Material Authorization (RMA) on equipment sent to vendors or organic depot for repair or replacement.

d. The contractor shall provide status reports in accordance with applicable DO CDRL requirements.

e. The contractor shall recommend substitute components for any COTS hardware/software items that become obsolete and, with Government approval, integrate them into the system.

f. The contractor shall maintain commercial manuals for all COTS equipment.

g. The contractor shall maintain configuration control for all delivered and installed equipment.

h. The contractor shall prepare engineering change proposals (ECP’s) and secure Government approval for all proposed changes to the configuration baseline as applicable.

i. The contractor shall serve as a repository for all drawings, software configurations, and other data, providing updates as required.

j. The contractor shall maintain the currency of stored configuration data.

k. The contractor shall track, manage and enforce equipment warranties on all failed equipment, spares and repair parts.

l. The contractor shall provide packaging, handling, storage and transportation services for all assets being returned to a vendor or original equipment manufacturer for repair.

3.2.5 ICS/CLS Spares and Repair Parts

The contractor shall provide all spare and repair parts required to replace failed items identified during fault isolation and restore the system to operational status as required in the approved configuration. To prevent excessive down time, the contractor shall store and maintain a sufficient quantity of spares at location(s) determined by the contractor to be necessary to restore systems to operations in accordance with maintenance repair times identified above. The contractor shall turn over all unused spares/repair parts to the Government at the end of the ICS/CLS period of performance.

3.3 Contractor Manpower Reporting: “The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for ICS/CLS via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.”

*Reporting Period: Contractors are required to input CMRA data by 31 October of each year.

Uses and Safeguarding of Information: Information from the secure CMRA web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any CMRA data be released to the public with the contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

3.4 Applicable Documents

The following specifications, standards, and handbooks (and all subsequent revisions thereto) are representative of the types of documents that may be cited in a DO. Where not specifically cited below, contractors are responsible for following applicable federal, state, host nation, local and base codes and regulations, as well as applicable architectural and construction standards during performance of DOs.

3.4.1 Government Specifications and Security Documents

· Headquarters Air Force (HAF)/A7S Non-Nuclear IDS Equipment Approval list, current version at time of DO award

· HAF/A7S Nuclear IDS Equipment Approval list, current version at time of DO award

· Standardized Electronic Security Equipment Siting and Design Guidance for Permanent Installations, (ESE-SIT-0001), dated 1 Mar 2013

· Performance Specification, Segment Specification for the Alarm Monitor Set, AN/USQ-139, Tactical Automated Security System, (BISS-SEG-27000B), dated 17 May 2010

· AFI 31-101, Integrated Defense, dated 8 Oct 2009, Incorporating Change 2, dated 7 Mar 2013

· Nuclear Weapon Security Manual: The DoD Nuclear Weapon Security Program and theater directives. DoD S-5210.41M, AFMAN 31-108. Dated 1 Feb 2010

· Air Force Global Strike Command (AFGSC) Supplement to Air Force Manual (AFMAN) 31-108, dated 23 Jan 2012

· DoD Instruction (DoDI) 5210.83 USD (I), DoD Unclassified Controlled Nuclear Information (UCNI) Dated July 12, 2012

· Nuclear Weapon Security Program Classification Guide, dated 17 June 2013

· AFI 63-1201, Life Cycle Systems Engineering, as incorporated into AFI 63-101/20-101, Integrated Life Cycle Management, dated 7 March 2013

· Integrated Base Defense Security System/Electronic Security Equipment (IBDSS/ESE) Security Classification Guide, dated 15 June 2011

· DoD 5220.22M, National Industrial Security Program Operating Manual (NISPOM), dated 28 Feb 2006

· DoDI 8510.01, Department of Defense Information Assurance Certification and Accreditation Process (DIACAP), dated 28 Nov 2007

· DoDI 8910.1, Information Collecting and reporting, dated 6 March 2007, incorporating Change 1, dated 17 Jan 2013

· DoD Standard Operating Procedure; Acquisition Procurement Guide for Unique Item Traceability Data Integrity, V1.0, dated 25 Feb 2011

· DCID 6/9, Physical Security Standards for Sensitive Compartmented Information Facilities, dated 18 Nov 2002

· AFI 33-210, Air Force C&A Program (AFCAP), 23 Dec 2008 (with Guidance Memo dated 21 Mar 2013)

· International Traffic in Arms Regulation (ITAR) and/or the Export Administration Regulation (EAR)

· IA Platform Information Technology (PIT) Guidebook, dated 20 Dec 2012

· T.O. 00-35D-54, USAF Deficiency Reporting and Investigation System, 1 Oct 2009

· AFPAM 63-113, Program Protection Planning for Life Cycle Management, 17 October 2013

· AFI 33-118, Electromagnetic Spectrum Management

3.4.2 Commercial Standards and Specifications

· EIA/ECA-310, Cabinets, Racks, Panels, and Associated Equipment, Rev E, dated Dec 2005

· IEEE C62.36, Standard Test Methods for Surge Protectors Used in Low Voltage Data, Communications, and Signaling Circuits, dated 2006

· IEEE C62.41.2, Recommended Practice on Characterization of Surges in Low-Voltage (1000 V And Less) AC Power Circuits, dated Nov 2002

· IEEE/EIA 12207.1, Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data, dated Apr 1998

· IEEE/EIA 12207.2, Guide for Information Technology - Software Life Cycle Processes - Implementations Considerations, dated Apr 1998

· IEEE 1100, Powering and Grounding Sensitive Electronic Equipment, dated 9 Dec 2005

· IEEE-SRD-142 Recommended Practice for Grounding of Industrial and Commercial Power Systems, dated 30 Nov 2007

· NEMA ICS 6-1993 Enclosures for Electrical Equipment, dated 2004

· NFPA 70, National Electrical Code, dated 2011

· NFPA 101, Life Safety Code, dated 2012

· UL 913, Intrinsically Safe Apparatus and Associated Apparatus for Use in Class I, II, III, Division 1, Hazardous (Classified) Locations, 7th Edition, dated 31 Jul 2006

· UL 96, Lightning Protection Components, 5th Edition, dated 12 May 2005

· UL 96A, Installation Requirements for Lightning Protection Systems, 12th Edition, dated 23 May 2007

· ASME Y14.100-2004, Engineering Drawing Practices, dated 2004

· ASME Y14.24-1999, Types and Applications of Engineering Drawings, dated 1999

· ASME Y14.35M-1997, Revision of Engineering Drawings and Associated Documents, dated 1997

· EIA-649B, National Consensus Standard for Configuration Management, dated 1 Apr 2011 (Adopted by DoD 01 Feb 1999)

· SAE Aerospace Standard AS5553, Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition, April 2009

3.4.3 Other Government Documents

· MIL-STD-461F, Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment, dated 10 Dec 2007

· MIL-STD-130N, DoD Standard Practice, Identification Marking of US Military Property, dated 16 Nov 2012

· MIL-STD-882E, System Safety, dated 11 May 2012

· MIL-STD-1472F, Human Engineering, dated 11 Jan 2012

· MIL-HDBK-881C, Work Breakdown Structures for Defense Materiel Items, dated 3 Oct 2011

· MIL-HDBK-61A, Configuration Management Guidance, dated 7 Feb 2001

· MIL-STD-810F, Environmental Engineering Considerations and Laboratory Tests, dated 1 Jan 2000, Notice 1, dated 1 Nov 2000, Notice 2, dated 30 Aug 2002, and Notice 3, dated 5 May 2003

· CADD/GIS Technology Center R4.0 A/E/C CADD Standard, dated Jul 2009

· UFC 3-301-01, Structural Engineering, dated 31 Jan 2011

· UFC 3-400-02 Design, Engineering Weather Data, dated 28 Feb 2003

· UFC 3-260-01, Airport and Heliport Planning and Design, 1 Nov 2001, Change 1 dated 19 May 2006

· UFC 4-021-02NF, Security Engineering Electronic Security Systems, dated 27 September 2006, incorporating Change 1, 23 October 2006

· UFGS - 32 31 13.53 Unified Facilities Guide Specifications High Security Chain Link Fences and Gates, dated Apr 2008

· UFGS Unified Facilities Guide Specifications – various

· NTIA “Red Book” ,Chapter 10, Manual of Regulations and Procedures for Federal Radio Frequency, dated May 2011

· Occupational Safety and Health 1910, Safety and Health Regulations for General Industry, current version available at http://www.osha.gov/

· Occupational Safety and Health 1926, Safety and Health Regulations for Construction, current version available at http://www.osha.gov/

· National Institute of Standards and Technology (NIST) Special Publication 800-53, Revision 4, Recommended Security Controls for Federal Information Systems and Organizations, Information Security, SA-12, April 30, 2013

4.0 ACRONYM LISTING