Attachment_1_-_FPS3_SOW_05_Dec_13.docx

ATTACHMENT 1

STATEMENT OF WORK (SOW)

FOR

FORCE PROTECTION SITE SECURITY SYSTEM (FPS3)

5 DECEMBER 2013

TABLE OF CONTENTS

Page

1.0 INTRODUCTION 3

5.0 ACRONYM LISTING 21

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) including:

· Fixed site Intrusion Detection Systems (IDS)

· Tactical security systems such as the Tactical Automated Security Systems (TASS)

· Delay/denial systems such as the Remote Target Engagement System (RTES)

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

Fixed site IDS projects are driven by unit requirements and are tailored to fit the Protection Level (PL) requirements of assigned resources at each site where they are installed. These projects may be as simple as purchasing equipment to satisfy a user's needs or as complex as providing for design, installation, test, and sustainment of a system of hardware and software to protect an entire base. They provide an electronic means to accomplish area intrusion detection, alarm reporting and display, remote alarm assessment, and alert SF to intrusions to enhance resource and facility protection. Fixed-Site systems are delivered as permanent security systems to protect high priority assets, with a focus on PL 1 (nuclear and non-nuclear), 2, 3, and 4 resources such as aircraft, munitions, command and control centers, etc.

The FPS3 contract also provides for acquisition, upgrade and sustainment of tactical security systems such as TASS, a rapidly deployable, re-locatable and integrated security system designed as a "first-in" capability for a variety of force protection missions. TASS has been fielded and is currently sustained at forward-operating locations worldwide.

The FPS3 contract will also provide for acquisition, upgrade and sustainment of delay/denial systems such as RTES, which provides final access denial to high-value assets at specified nuclear systems locations.

2.0 PURPOSE

This SOW describes the scope of effort that may be required by the Contractor via Delivery Orders (DOs) issued under the FPS3 contract. The intent is to rapidly acquire and provide SF personnel with mission-critical, integrated security systems and equipment that neutralize or mitigate anticipated threats. The SOW also includes other related efforts such as services critical to system sustainment; identification, upgrade, insertion of technology; special studies, analyses and demonstrations; equipment qualification; and other efforts that support the acquisition and sustainment of a family of IBDSS including fixed site IDS, tactical security systems such as TASS, and delay/denial systems such as RTES.

2.1 Scope: The scope of this effort includes all activity and work required to design, procure, install, integrate, test, deliver, and sustain:

· The family of IBDSS including but not limited to:

· Fixed site IDS

· Development, sustainment and/or reconfiguration of tactical systems (such as TASS)

· Remote command and automated activation of delay/denial devices (such as RTES)

This scope also includes, but is not limited to:

· Contractor program management and subcontractor oversight

· Contractor development/implementation of quality assurance/control program

· Systems engineering

· System design, development, test and evaluation

· Purchase of Commercial Off-the-Shelf (COTS) and ancillary equipment

· Necessary installation of, or upgrades to, supporting infrastructure

· Installation and systems integration of Contractor-provided equipment and/or infrastructure and Government Furnished Property/Equipment (GFP/GFE) and infrastructure

· Support (upgrade, repair or replacement) of applicable GFP/GFE

· Preparation of technical orders and/or supplements to COTS equipment manuals

· Contractor Verification Testing (CVT)

· Technical Manual/Technical Order validation

· Equipment qualification testing

· COTS production qualification acceptance testing

· Contractor training of site and support personnel

· Contractor support of Government testing

· Interim Contractor Support (ICS) of installed systems

· Contractor Logistics Support (CLS) and/or operational readiness support of tactical and fixed site systems worldwide

· Special studies, analyses, and demonstrations

· Technical and other effort necessary to support system/project acquisition and/or sustainment

· Technology identification, upgrade, and insertion

· Acquisition of systems and associated support for Foreign Military Sales (FMS) customers and any other Government agency (such as the Department of State [DoS], Department of Energy [DoE]) or other Department of Defense (DoD) agencies/services, if ordered

· Other acquisition and/ or sustainment support as required

Other associated security capabilities such as fencing, lighting, power and ground communications systems, and related infrastructure improvements may also be required. The Contractor shall also improve security capability during the life of the contract through the identification and replacement of obsolete or end-of-life COTS equipment, and/or the development and insertion of technology to meet diverse and emerging security requirements. In doing so, the Contractor shall ensure that state-of-the-art equipment is available for the myriad of force protection missions.

2.2 Objectives: Any DO issued under this contract shall meet any number of the requirements listed below utilizing sound systems engineering principles and management practices.

2.2.1 Design and Integration of Prime Mission Equipment and Systems: The Contractor shall design, acquire, install, integrate, test, deliver, sustain and/or upgrade or reconfigure electronic fixed site IDS, tactical (such as TASS) or delay/denial (such as RTES) systems and equipment that meet the physical security compliance requirements of applicable DOs as defined in the DO SOW, Performance Work Statement (PWS), specification, or any other applicable DO documents and instructions. Related tasks include all design, upgrade, construction, installation and integration of necessary supporting infrastructure, and site cleanup and restoration.

2.2.2 Equipment Purchase, Assembly/Manufacture, Delivery and Test

2.2.2.1 COTS/Government-off-the-Shelf (GOTS) Equipment: The Contractor shall procure non-developmental items (e.g. COTS and GOTS) equipment to support DO requirements. Fixed Site IDS equipment shall consist of already proven COTS equipment from the AF/A7S Approved Equipment List (AEL), or COTS equipment proposed by the Contractor. If the Contractor proposes non-AEL equipment, the Contractor shall qualify (test) the equipment to meet specified performance requirements and shall prove (through test) that the equipment is "certifiable" for use. Although the Government may approve the introduction of new IDS security technologies throughout the life of this contract, Contractor adherence to previously proven and approved technology is highly encouraged. Tactical security system equipment purchases to support TASS shall consist of TASS GOTS equipment and associated COTS ancillary equipment as may be required. System upgrades/modifications for new tactical security systems, new delay/denial systems, TASS, and RTES shall use COTS and/or GOTS or new developmental items if such new items are required to meet Government requirements as specified in a DO solicitation.

2.2.2.2 COTS/GOTS Test: The Contractor shall test subsystems, equipment and components to validate that all systems, subsystems and equipment meet applicable performance specifications.

2.2.2.3 Item Unique Identifiers (IUIDs): The Contractor shall comply with the requirements of DFARS 211.274, Item Identification and Valuation Requirements in the establishment and reporting of applicable IUID equipment.

2.2.2.4 Manufacturing Process Control: The Contractor shall perform manufacturing process control and quality control for any parts or equipment manufactured by the Contractor. The Contractor shall ensure that subcontractors or vendors implement sound manufacturing processes and quality control to ensure that delivered systems, subsystems and components meet specified DO performance and quality requirements.

2.2.2.5 Purchasing: The Contractor shall perform and implement sound material planning, purchasing, expediting, and control processes and activities to purchase or acquire required equipment, components, parts and software infrastructure materials. This includes ancillary components, parts and material that are required to comply with DO performance and schedule requirements.

2.2.2.6 Production Control: The Contractor shall perform production control tasks necessary to fabricate, manufacture, assemble, test and integrate equipment, components, parts and software as applicable. The Contractor shall also accomplish staging, packaging, packing, delivery and Government acceptance of systems and equipment required to satisfy DO requirements.

2.2.3 Systems Engineering: The Contractor shall provide systems engineering and systems engineering management to continually ensure that:

· Applicable DO performance requirements are met

· Applicable designs are feasible and sound

· System integration and installation meet DO requirements

· System reliability, availability and maintainability is evaluated

· Delivered systems/equipment can be supported or sustained

2.2.3.1 System Architecture

2.2.3.1.1 Design: The Contractor shall design security system installations at designated sites in accordance with (IAW) DO requirements. The Contractor shall also ensure that all systems, subsystems, equipment and/or components are designed IAW DoD Architecture Framework (DoDAF) guidance.

2.2.3.1.2 Security Equipment Integration Working Group (SEIWG): The Contractor shall support the DoD SEIWG through performing DoDAF-compliant studies, analyses, and producing architecture products IAW applicable DO requirements.

2.2.3.2 System Design: The Contractor shall develop and prepare applicable system/site designs for Government review and approval. These designs shall include, but not be limited to, system design, infrastructure design, drawings, design/configuration of specific equipment or components, and site design. The Contractor shall also design systems that comply with DoDAF guidance, frequency spectrum requirements and installation siting criteria.

2.2.3.2.1 Design Reviews: The Contractor shall conduct design reviews, which require the preparation of design drawings and any associated documentation. The Contractor shall also accomplish tasks in support of design reviews, such as preparing agendas and recording and distributing meeting minutes.

2.2.3.2.2 Engineering Change Proposals (ECPs): Changes to system equipment that affect form, fit, function, or interface, shall be submitted to the Government as Class I ECPs. Class II ECPs do not affect form, fit, function or interface, and shall be submitted to the Government as advisory ECPs only. Class II ECPs do not require Government approval, unless the Government requests further information or justification.

2.2.3.2.3 Deviations: Contractor requests to deviate from Government standards, requirements, or regulations shall describe which major components are affected and shall include the rationale or justification for the deviation, as well as any impact on cost, schedule, performance or supportability.

2.2.3.2.4 Test: The Contractor shall prepare installation test plans and procedures, conduct CVT, validate technical manuals and support Government test and turnover activities to include documenting and correcting problems that are identified during testing. For new systems development efforts, the contractor shall perform systems development test and evaluation in accordance with DO requirements.

2.2.3.2.5 Turnover: The Contractor shall prepare and deliver “as-built” drawings and documentation that will facilitate future sustainment, maintenance and modification of the system.

2.2.3.2.6 Regulatory Assistance: The Contractor shall assist the Government by providing information that is necessary to prepare Information Assurance (IA) Certification and Accreditation (C&A) packages. In the event that new Radio Frequency (RF) Items are introduced, the Contractor shall support the Air Force Frequency Allocation process by submitting an updated DD Form 1494 within 45 days of DO award. Applicable to all orders requiring frequency authorization. The Contractor must ensure that radio frequencies are available to support electromagnetic radiating devices in their intended environment and that adequate protection from interference can be provided to receiving devices. Accordingly, the Contractor shall submit DD Form 1494, Application for Equipment Frequency Allocation, in triplicate to the buyer at the issuing office indicated on the cover of this document within 45 days after order award. Instructions for preparing the form are contained in AFI 33-118, Electromagnetic Spectrum Management, and on the form itself. The DD Form 1494 will be routed through the Administrative Activity Quality Control Office indicated on the cover of the form in accordance with AFI 33-118. Upon verification of frequency requirements, the Contractor shall submit, if required, information to prepare a "Standard Frequency Action Format (SFAF) Request" to the person and address specified above. Instructions for preparing an SFAF are contained in AFI 33-118. Attention is directed to DFARS 252.235-7003, Frequency Authorization.

2.2.4 Reserved

2.2.5 Developmental Projects, Demonstrations, and Studies

2.2.5.1 Technical Studies: When directed by the Government, the Contractor shall perform system/project development efforts; conduct or support investigations; conduct testing; conduct or perform demonstrations; and conduct special studies and/ or technical analyses including but not limited to analysis of industrial and technological trends, advancements, or limitations, and their impact upon systems that are covered by the FPS3 contract. These efforts may include:

· Engineering analyses and studies

· Demonstrations

· Systems/Project design & development

· System design reviews

· Insertion of hardware and software upgrades (including development and systems retrofit)

· Developing, upgrading, or assistance with the development of systems or interface specifications, architectural views, Government-provided Interface Control Documents, and other engineering documentation

· Systems test and evaluation and deficiency reporting using Deficiency Reporting (DR) system for tracking and resolution of deficiencies that implements processes and methodologies consistent with TO-00-35D-54 (USAF Deficiency Reporting and Investigating System) and allows portability of data into Government Joint Deficiency Reporting System

2.2.5.2 Technology Insertion: When directed by the Government, the Contractor shall:

· Provide, develop and/or integrate various hardware and software upgrades for FPS3 and/or legacy site security systems

· Utilize technology insertion as a means to add new capabilities

· Demonstrate that newly developed or upgraded components are interoperable, interchangeable, and backwards compatible

2.2.5.3 Equipment Qualification: If required, the Contractor will qualify new equipment for integration into the IBDSS, including:

· Providing a testing capability that will be used to plan and perform tests

· Reporting test results

· Supporting and participating in Government Combined Test Force (CTF) activities

· Performing COTS qualification testing (including the development of test plans and procedures)

· Performing engineering analysis, to include market research if required, providing recommendations, and conducting/participating in test efforts to qualify and accept new COTS items either on separate DO or as part of a design/install DO under the FPS3 contract to meet capability needs caused by new User requirements or by non-procurability or obsolescence of items on the HAF/A7S approved IDS equipment list

· Reporting deficiencies using Deficiency Reporting (DR) system for tracking and resolution of deficiencies that implements processes and methodologies consistent with TO-00-35D-54 (USAF Deficiency Reporting and Investigating System) and allows portability of data into Government Joint Deficiency Reporting System

2.2.6 Management

2.2.6.1 Effective Management: The Contractor shall use effective processes to direct and manage DO efforts, including direction and control of subcontractors.

2.2.6.2 Working Relationships: The Contractor shall establish a working relationship with the Government and other applicable contractors that fosters open communication and an atmosphere of cooperation. The Contractor shall also communicate with the Government regarding site status, issues and activities that may impact a project’s operational, cost and schedule requirements.

2.2.6.3 Risk Management: The Contractor shall apply sound risk management principles for the duration of the contract.

2.2.6.4 Personnel Qualification: The Contractor shall provide qualified personnel, and shall also ensure that subcontractor personnel are qualified to perform the work that they are hired to complete.

2.2.6.5 Purchasing: The Contractor shall utilize an ordering process that minimizes buying agency involvement and time to order and receive products.

2.2.6.6 Internal Management: The Contractor shall implement and utilize internal management processes to plan, schedule, budget, and monitor, manage and report cost, schedule, and technical performance.

3.0 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.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.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.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 REQUIREMENTS

4.1 General: The Contractor shall accomplish each DO’s tasks IAW applicable codes, specifications, standards, and security documents as specified therein. DO tasks will typically fall under the general areas outlined in Section 4.2 but may differ depending on specific customer requirements.

4.2 Detailed Tasks: Each DO may require Contractor effort or Contractor support for Government efforts in the following areas:

4.2.1 Design, Installation, and Integration Activities

4.2.1.1 Site Survey: After a DO is awarded, the Contractor shall conduct a thorough and comprehensive “post-award site survey” to gather all information necessary to complete designs, installation plans, and specifications. At a minimum, this survey shall include validation of site conditions and system requirements, identification of potential obstacles that could affect design or construction, and evaluation of the suitability of GFE/GFP for use/integration into IBDSS. The Contractor shall immediately notify the Government of any deficiencies or potential problems that it identifies during the post-award site survey.

4.2.1.2 Pre-Installation Activities / Production Qualification and Acceptance: The contractor shall provide a system design compliant with specified requirements. Fixed Site IDS equipment shall consist of already proven COTS equipment from the AF/A7S Approved Equipment List (AEL) or COTS equipment proposed by the Contractor. Use of already proven AEL equipment is encouraged to the maximum extent possible. When proposing non-AEL COTS equipment, the contractor shall provide COTS equipment that meets Government specified equipment performance requirements. For non-AEL COTS equipment, the Contractor shall conduct production qualification & acceptance testing to verify that the non-AEL equipment performance meets specified requirements. The Government will witness and participate in contractor-conducted production qualification & acceptance testing. The Contractor shall prepare applicable test plans, test procedures and test reports for Government approval, and shall support and participate in a Government-led Combined Test Force (CTF) activity to validate equipment performance. The contractor shall use a Deficiency Reporting (DR) system for tracking and resolution of test deficiencies that implements processes and methodologies consistent with TO-00-35D-54 (USAF Deficiency Reporting and Investigating System) and allows portability of data into the Government Joint Deficiency Reporting System. Any deficiencies that are identified during production qualification acceptance testing shall be corrected and retested or regression tested as applicable to verify deficiency correction. After completion of production qualification testing and correction/verification of all deficiencies, the contractor shall provide the equipment to the government for operational testing (as required) and shall support government-conducted operational testing. Contractor support of operational testing shall include but not be limited to familiarization training of the Government Test team; technical support as requested; and maintenance of the equipment during the government test period. The contractor shall correct any operational test deficiencies identified and shall conduct retesting or regression testing to verify that all identified deficiencies have been corrected. After completion of all required testing, and correction of deficiencies, the contractor shall support a Government conducted functional and physical configuration audit of the equipment and shall provide all data necessary to support the audits, including but not limited to commercial Source Control Drawings (SCD) and other data as required to document the equipment configuration baseline in accordance with the DO Contract Data Requirements List (CDRL).

4.2.1.3 Installation: The Contractor shall perform all tasks necessary to install supportable systems that comply with DO requirements. The installation phase will include work that is required to prepare and install the system as well as site infrastructure to support system installation, including repair/restoration of any associated GFP/GFE. Prior to the start of installation, the Contractor shall be responsible for obtaining all requisite site authorizations/permits (such as airfield access and construction permits, installation permits, base access permits, confined space clearances, etc.) necessary to install the system. The contractor shall perform required installation(s) IAW a Government-approved design. Contractor installation shall include all system equipment, trenching, cabling, wiring, junction boxes, grounding, foundations, infrastructure, communications, power, supports, and ancillary equipment required to provide a complete and usable system. The Contractor shall ensure that installation at the site is accomplished without impact to site operations. Finally, the Contractor shall restore all areas that are disturbed by installation to a condition at least equal to the condition that existed prior to the project.

4.2.1.4 System Test and Turnover: The Contractor shall verify that installed systems comply with all requirements by conducting a comprehensive CVT process for security system installations. The CVT process shall include:

· Preparation of test plans and procedures

· Validation of technical manuals

· Functional, operational and system-level testing of system performance and stability

· Documentation of test results

· On-site support during the Government Acceptance Test (GAT)

The Contractor shall also support Government Functional Configuration Audits (FCAs) and Physical Configuration Audits (PCAs) as directed by the Government.

4.2.2 Quality

4.2.2.1 Quality Control (QC) Process: The Contractor shall establish and maintain a comprehensive QC program, including the development and maintenance of a QC Plan (QCP) that shall document all aspects of QC functions. The Contractor shall conduct inspections during system installation and report its findings to the Government. The Contractor shall ensure the following as part of this process:

· All equipment and/or components have been installed according to the design, Original Equipment Manufacturer (OEM) instructions, system specifications, and government siting criteria

· All supporting infrastructure has been installed IAW applicable UFC and UFGS criteria

· All work and workmanship are compliant with site-specific, local, state and federal construction codes and requirements

4.2.2.2 Vendor and Subcontractor Quality Control Management: The Contractor shall ensure that QC requirements apply to subcontractors and vendors. The Contractor shall monitor supplier activity to ensure adherence to contractual requirements and applicable standards and procedures. The Contractor shall work with vendors and subcontractors to identify root causes of quality deficiencies, and shall take corrective actions for non-conforming items that fail to meet Government requirements or specifications.

4.2.3 DoD Information Assurance Certification and Accreditation Process (DIACAP)

4.2.3.1 DIACAP Support: The Contractor shall support the Government in obtaining certifications required to connect and operate FPS3 equipment using the DIACAP. This support shall include, but not be limited to:

· Providing all required IA artifacts for inclusion in documentation packages, including all DoD Architecture Framework (DoDAF) views and documentation

· Assisting the Government with developing and executing Plans of Actions and Milestones (POA&Ms) to address IA deficiencies

· Reviewing Government-prepared DIACAP Packages for accuracy

4.2.3.2 IA (Contractor Recommended Equipment): The Contractor shall prepare, submit, and update for Government review and approval, C&A documentation for any Contractor-recommended equipment not currently certified and listed on the HAF/A7S IDS Approved Equipment List. Supporting documentation will be specified in the applicable DO and shall include but not be limited to documents such as: System Security Design Specifications (SSDS), Ports, Protocols and Services (PPS) requirements, Functional Requirements Traceability Matrices, Application and Security Requirements Security Technical Implementation checklists, Security Functional Test Plans & Procedures, security design requirements, security requirement Verification and Validation (V&V), sensitivity of the data being processed, identification of system vulnerabilities, and identification of existing and planned countermeasures. Additional documentation will include User Guides, Administrator Reference Guides, Software Description Documents, Interface Control Description Documents, Government approved Training Packages, etc. The Contractor shall also participate in design reviews as required by the Government for review and approval of IA designs. The Contractor shall plan for the provision of Contractor recommended equipment and software to the Government IDS test site to allow for testing of system updates.

4.2.3.2.1 IA Controls: The Contractor shall identify and document the applicable IA controls of the latest versions of DoDI 8500.01 and 8500.2 (Mission Assurance Category III, Sensitive) for the IBDSS Program as called out in the applicable DO. The Contractor shall use the systems engineering process to incorporate the applicable IA controls into the requirements, design, integration, and testing processes.

4.2.4 Reserved

4.2.5 Management

4.2.5.1 FPS3 Post Award Conference: AFLCMC/HBU will organize and host a meeting with FPS3 awardees at Hanscom AFB. The Post Award Conference is a one-time effort to discuss future FPS3 DOs and projected workload over the five-year period of performance, and is intended to meet the contract’s minimum DO requirements. Additional objectives include gaining familiarity with the personnel associated with the FPS3 contract, and gaining an understanding of processes associated with DO development, fair opportunity selection, and DO implementation. At this event, Contractors shall present the Government with their organization structures for FPS3 management, including roles and responsibilities and contact information for key Contractor personnel. Contractors are responsible for their own travel and lodging arrangements.

4.2.5.2 Integrated Program Management: The Contractor shall:

· Use and maintain sound and disciplined integrated program management procedures and processes to plan, organize, staff, control and manage DO efforts

· Assess and report statuses regarding the achievement of contract requirements

· Provide integrated master schedules, contract work breakdown structures (to the lowest practical level), and other management data as required

· Conduct Program Management Reviews (PMRs) with the Government at a period to be determined upon the award of a DO

· Record the minutes of these PMRs, and make a draft of the minutes available to the Government prior to the adjournment of the PMR for mutual agreement between the Government and the Contractor

· Support other program reviews as requested by the Government

· Integrate and coordinate all activity required to execute the FPS3 contract

· Manage the timeliness, completeness, and quality of all deliveries

· Effectively manage subcontractors to ensure contract completion IAW FPS3 and DO requirements

· Provide early and comprehensive risk or issue identification

· Submit corrective action plans and proposals to mitigate risks or issues in a timely manner

4.2.5.3 Government/Contractor Integrated Product Team (IPT): The Contractor shall participate in Government-chaired DO project IPTs. IPT meetings will be weekly teleconferences and may be held in conjunction with other meetings or reviews. The Contractor shall provide program updates and/or information that will be used to determine the statuses of on-going projects or test planning, and to resolve programmatic and technical issues. The Contractor shall respond to action items and shall use the IPT as a forum to propose action items for Government completion.

4.2.5.4 Management of Contracts and Subcontracts: The Contractor shall perform the following functions to facilitate contract and subcontract management:

· Furnish program management, labor, tools, supplies, and materials (except as provided by the Government) necessary to perform the requirements contained in applicable DOs

· Establish processes and assign appropriate resources to effectively administer DO requirements

· Respond to Government requests for contractual actions in a timely fashion

· Establish a single point of contact between the Government and Contractor personnel who are assigned to support DOs

· Implement subcontract management systems, processes and organizations that provide the “best value” in the purchase of goods and/or services under this contract

· Maintain responsibility for subcontractor performance and subcontract management necessary to integrate work performed on DOs

· Distribute work in a way that avoids Organizational Conflict of Interest (OCI) issues. Contractors may add subcontractors to their team after notifying the Procuring Contracting Officer (PCO) or Contracting Officer Representative (COR).

4.2.5.5 Reserved

4.2.5.6 Electronic Data Interchange: Each DO will require electronic data interchange to maximize the provision of program information through electronic media. The Government will distribute relevant information to contractors via electronic methods over the course of the contract.

4.2.5.7 Risk Management: The Contractor shall manage risk throughout the life of the contract to reduce or eliminate problems. The following table defines the risk levels to be used as a guide for identifying technical, schedule and cost risks associated with a DO. Additional guidance can be found in the Risk Management Guide for DoD Acquisition.

Risk Likelihood

Risk Consequence

(<1% of target for FPIF or cost type orders)

(<5% of target for FPIF or cost type orders)

(<10% of target for FPIF or cost type orders)

(>10% of target for FPIF or cost type orders)

Contractors shall address risk in DO proposals and during on-going reviews, to include formal internal reviews and PMRs. Risk statuses shall be reported as directed in individual DOs.

4.2.5.8 Configuration Management (CM): The Contractor shall conduct and maintain CM and change control processes IAW guidelines within EIA-649B and MIL-HDBK-61A for all DO configuration items, including software CPCIs.

4.2.5.9 Data Management: The Contractor shall establish, document and maintain a data management program IAW its internal procedures. The Contractor shall use logical methods to generate, acquire, identify, plan and control all technical data, management data and related information. The Contractor shall also have a method to update the Government on status of this data. The Contractor shall develop a Data Accession List (DAL), which is an index of released, non-deliverable, internal Contractor data that shall be made available for Government review at any time during contract performance. Data management shall include, but not be limited to:

· On-time data delivery

· Identification, marking and control of proprietary and classified data

· Data quality assurance (QA)

· Updates and corrections to submitted data

· Maximum use of electronic data exchange

4.2.5.10 Contractor Essential Services: A written plan for Contractor Essential Services as described by DFARS 237.7602(b) may be required and incorporated at the delivery order level.

4.2.6 Program Security

4.2.6.1 Contractor Security Program: The Contractor shall implement a security program that safeguards classified and sensitive IBDSS information IAW the Contractor’s approved internal security processes. The security program shall be consistent with the National Industrial Security Program Operating Manual (NISPOM, DoD 5220.22M), the IBDSS/ESE Security Classification Guide, the latest version of the Nuclear Weapon Security Program Classification Guide and the DoD Contract Security Classification Specification (DD Form 254) included in the FPS3 contract.

4.2.6.2 Program Protection: The Contractor shall implement requirements as listed in the Government-furnished Program Protection Plan (PPP) to be provided as part of applicable FPS3 DOs. When required by an FPS3 DO, the Contractor shall provide a Program Protection Implementation Plan (PPIP) to address:

· DO-specified PPP requirements

· Contractor support to the Government-led Critical Program Information (CPI)/Critical Component (CC) identification process, criticality analysis and countermeasure development

· Implementation of all countermeasures once they are identified through the CPI/CC identification process and criticality analysis phase

· Verification and Validation (V&V) of countermeasure effectiveness, cost and schedule impacts and oversight of subcontractors' PPP implementation activities

· Contractor support to the Government-led Program Protection IPT

If these activities and documentation are required by a DO, the Contractor shall support a Government inspection of the activities and documentation during a Program Protection survey.

4.2.6.3 Supply Chain Risk Management (SCRM):

The contractor shall establish and implement a supply chain risk management (SCRM) program and when directed under an FPS3 DO, shall develop and deliver a SCRM Plan. The contractor will integrate the SCRM plan with their overall risk management process to ensure that the delivered system, maintenance equipment, and supplies (e.g., spares and repair parts) do not incorporate counterfeit parts, malicious code, or any other elements that would allow adversaries to gain unauthorized access to data, alter data, interrupt communications, or otherwise disrupt operations.

The contractor SCRM program and as required DO SCRM plan, shall incorporate counterfeit prevention methods to describe how they will prevent procurement of counterfeit materials and parts, including mechanical piece/parts and electronics components procured for sustainment of those systems and assemblies. The contractor’s SCRM program and applicable DO plans shall comply with the tenets of AFPAM 63-113, "Program Protection Planning for Life Cycle Management”, SAE Aerospace Standard 5553, Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition, and 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 as guidance. When SCRM Plan is required by DO, the contractor shall include in the plan a description of their processes for reviewing and approving supplier and subcontractor systems for the detection and avoidance of counterfeit electronic parts. In the Plan, the contractor shall also describe how they will flow down such requirements and processes to their subcontractors.

4.2.6.4 Operations Security (OPSEC): OPSEC guidelines are required in an effort to reduce a program’s vulnerability to an adversary’s collection and exploitation of critical information. The Contractor shall apply OPSEC IAW AFI 10-701, Operations Security. The Government will provide the Contractor with a copy of the Critical Information List (CIL) as part of solicitations for FPS3 orders.

4.3 Travel Requirements: Contractor employees may be required to travel to various locations within the Continental United States (CONUS) and Outside of the Continental United States (OCONUS) to perform FPS3 requirements. The Contractor shall be responsible for obtaining all passenger transportation, lodging, and subsistence, both domestically and overseas, required for DO performance. Estimated travel requirements will be included in each DO. Federal Acquisition Regulation (FAR) 31.205-46 describes allowable travel costs. Travel costs not specifically covered at FAR 31.205-46 may be addressed on an as-needed basis. The Joint Travel Regulation (JTR) does not apply to contractors, but may be used to aid the contracting officer in making decisions regarding travel rules and the reasonableness of travel related costs. Contractors shall travel using the lower cost mode of transportation commensurate with mission requirements. If air travel is necessary, the Contractor shall use the economy class, or similar accommodations to the extent they are available and commensurate with the mission requirements. Travel will be paid on a cost reimbursable basis; no profit or fee will be paid.

5.0 ACRONYM LISTING

FA8730-14-R-0004, Attachment 1, Page 1 image1.png