Attachment_1_-_PWS_Flightline_CCTV.pdf

NETCENTS-2 SOLUTIONS

NetOps and Infrastructure Solutions – Full and Open

Installation of Thermal/CCTV Services Buildings 2510, 18015, 51104 & 51109

Andersen AFB, Guam

Task Order Performance Work Statement

Name: Joseph P. Abarca

Organization: 36 SFS/S5

Address: DODAAC: FB5240

36 SFS/S5

Chicago Ave, Bldg. 23020 Unit 14003

APO AP 96543-4003

Request for Information Submit to darrin.davis.3@us.af.mil or ian.larsson@us.af.mil

PWS Date: 21 Dec 2017

Executive Summary

This Performance Work Statement (PWS) defines the requirements for the Contractor to engineer, furnish, install, and test (EFI&T). This request is to procure, install, train, and test CCTV assessment and protection of the assets at the flight line area on Andersen Air Force Base. New work includes installing the Thermal/CCTV cameras at these locations; buildings 2510, 18015, 51104 & 51109 to include routing all Thermal/CCTV video assessment & control to a central hub at 23020. The Contractor shall provide all equipment, tools, materials, supplies, transportation, labor, supervision, management, and other incidentals necessary to meet the requirements as stated in this PWS. All equipment, supplies, or materials provided shall be new and not refurbished. No equipment, supplies, or material will be provided by the government. The Contractor shall supply Commercial-Off-the-Shelf (COTS) end-item system components required for contract performance wherever possible. The Contractor shall identify all materials or equipment required for the project in the Proposal. The Contractor shall list the manufacturer and part number of the proposed material in the Proposal. Unless otherwise specified, the Contractor shall provide copies of existing COTS technical or equipment manuals and warranty documentation and procedures for Contractor-furnished end-item system equipment maintenance. The Contractor shall identify and conduct system familiarization for Government personnel to ensure proper operation and maintenance of the system(s).

mailto:darrin.davis.3@us.af.mil mailto:ian.larsson@us.af.mil

The period of performance for this Task Order the contractor shall have 120 days from contract award to complete all facets of the project including final walk thru with the government representative. The contractor shall provide a work schedule IAW CDRL A315.

The Contractor shall routinely work during normal operating hours of the site. Monday through Friday (0730-1630 hours), excluding federal holidays. Any site work requested by the Contractor to be performed outside of normal duty hours shall be coordinated with the Base POC at least 10 working days in advance.

NETCENTS-2 NetOps and Infrastructure

TO PWS

Installation of Thermal/CCTV installation services, Buildings 2510, 18015, 51104 & 51109 at Andersen AFB, Guam

1. Purpose The Contractor shall provide a turn-key installation of Thermal/CCTV installation services, Buildings 2510, 18015, 51104 and 51109.

2. Scope This Performance Work Statement (PWS) defines the requirements for the Contractor to engineer, furnish, install, and test (EFI&T). This request is to procure, install, train, and test CCTV assessment and protection of the assets in the flight line area on Andersen Air Force Base.

New work includes installing The Thermal/CCTV cameras at these locations; building 2510, 18015, 51104 & 51109 to include routing all Thermal/CCTV to central hub at building 23020.

The Contractor shall provide all equipment, tools, materials, supplies, transportation, labor, supervision, management, and other incidentals necessary to meet the requirements as stated in this PWS. All equipment, supplies, or materials provided shall be new and not refurbished. No equipment, supplies, or material will be provided by the government.

3. Requirement/Description of Services The Contractor shall provide all management, personnel, equipment, tools, transportation, supplies, materials, supervision, and other incidentals necessary to engineer, furnish, install, and test (EFI&T).

Install CCTV cameras at these locations, buildings 2510, 18015, 51104 and 51109. All feeds will be routed to the centrally located 36 SFS BDOC in buildings 23020, 20001 and 23028. All Thermal/CCTV cameras at building 2510, 18015, 51104 and 51109 require camera coverage of the flight line area. CCTV cameras will be mounted on a three inch diameter aluminum pole, five feet in length, secured on the building roof, quick removable of the camera when severe tropical storms and/ or typhoons conditions are expected. Provide conduit for COMM and power to each camera location into the designated building that it is installed at so that it will connect to the building 23020 (Primary BDOC), 20001 (Alternate BDOC) and 23028 (Command Post for viewing). At each Thermal/CCTV Camera location a dedicated power circuit going to a circuit breaker panel in the building for the camera and COMM line to the demarcation point in the building. Install a Command Center, NVR and Monitors at the Primary BDOC (Bldg. 23020), Alternate BDOC (Bldg. 20001) and Command Post (Bldg. 23028) that will receive the video feed. Each CCTV camera requires backup battery power to allow for a minimum of 8 hours coverage, in the event of power loss.

The Contractor shall provide all equipment, tools, materials, supplies, transportation, labor, supervision, management, and other incidentals necessary to meet the requirements as stated in this PWS. The Contractor shall comply with the current TIA (Telecommunications Industry Association) telecommunication installation and testing commercial standard and base installation standards. All equipment, supplies, and materials provided shall be new and not refurbished.

N/A

3.1 Singularly Managed Infrastructure with Enterprise Level Security (SMI-ELS) Infrastructure Implementation and Operation N/A

3.1.1 Singularly Managed Infrastructure (SMI)

N/A

3.1.1.1 Core Enterprise Services

N/A

3.1.1.2 Enclaves

N/A

3.1.1.3 Federation

N/A

3.1.1.4 Metadata Environments (MDEs)

N/A

3.1.1.4.1 Metadata Components

3.1.1.4.1.

3 Metadata Registry

3.1.1.4.1.

N/A

3 Metadata Catalog

3.1.1.4.1. 3 Service Registry N/A

3.1.1.4.2 Metadata Environment Services

3.1.1.4.2.

3 MDE Infrastructure Services

3.1.1.4.2. 3 Metadata Lifecycle Management N/A

3.1.1.4.2.

N/A

. 3 3 Metacards and Asset Registration

3.1.1.4.2.

N/A

. 3 3 Automated Metadata Population Service

3.1.1.4.2. . 3 3 Versioning

3.1.1.4.2.

. 3 3 Indexing

3.1.1.4.2.

N/A

3 Semantic Discovery Services

3.1.1.4.2. 3 Federation of MDEs

3.1.2 Enterprise Level Security (ELS)

3.1.2.1 Cyber Security Architecture

3.1.2.1.1 Confidentiality

The contractor shall provide confidentiality security services that prevent unauthorized disclosure of data, both while stored and during transit.

3.1.2.1.2 Integrity

The contractor shall provide integrity security services that prevent unauthorized modification of data, both while stored and in transit, and detection and notification of unauthorized modification of data.

3.1.2.1.3 Availability

The contractor shall provide availability services that ensure timely, reliable access to data and information services for authorized users.

3.1.2.1.4 Authenticity

The contractor shall provide authenticity services that ensure the identity of a subject or resource is the one claimed. The contractor shall ensure that authenticity applies to entities such as users, processes, systems and information.

3.1.2.1.5 Non-Repudiation

The contractor shall provide non-repudiation services that ensure actions within the AF, DoD or IC SOA service invocations, information queries, etc., are attributable to the entity that invokes them.

3.1.2.2 Cyber Security Services

N/A

3.1.2.2.1 Identity Management

N/A

3.1.2.2.2 Threat Analysis

3.1.2.2.3 Certification and Accreditation

3.1.2.3 Enabling Security Capabilities

3.1.3 Enterprise Service Management

N/A

3.1.4 SMI-ELS Architecture Documentation

N/A

3.2 Network Services and Solutions

N/A

3.2.1 Network Operations

N/A

3.2.1.1 DoDIN Enterprise Management (EM)

N/A

3.2.1.1.1 Enterprise Messaging and Directory Services

N/A

3.2.1.1.2 Enterprise Application Services and Service Management N/A

3.2.1.1.3 Enterprise Information Management

N/A

3.2.1.2 DoDIN Network Defense (ND)

N/A

3.2.1.3 DoDIN Web Content Management

N/A

3.2.1.4 Network Operations Enabling Capabilities

N/A

3.2.1.5 Network Command and Control

N/A

3.2.1.6 Network Management and Enterprise Services

N/A

3.2.2 Network Infrastructure

N/A

3.2.2.1 Messaging

3.2.2.2 Site Preparation and Installation Services

The contractor shall perform site preparation and installation activities to support implementation of required services and solutions under this contract at any AF, DoD or other Federal Agency location.

3.2.2.2.1 Requirements Analysis and Conceptual Design

The contractor shall perform requirements analyses and conceptual designs at required locations.

During this process, the contractor shall collect all the information to complete a requirements analysis and conceptual design.

2510.pdf

18015.pdf

51104.pdf

51109.pdf

The Thermal/CCTV will be equal to or better than the Thermal/CCTV system parameters listed below.

SYSTEM

• All weather high performance universal sensor HD CCTV Thermal Uncooled Long Wave Infrared imaging PTZ day/night vision camera system.

• Open Architecture Analog, IP/Ethernet, Remote and Custom Configuration.

• Full 360 degree Pan, 90 degrees Tilt, Precision Gold Plated Pass Through Circuitry.

• Automatic/Manual User Selectable.

IR THERMAL IMAGER SPECS

• Array Format: Auto Calibrating Uncooled FPS Detector QVGA/VGA/XGA Optional.

• Detector Type: 4th Generation High Sensitivity Sensors with 0.1 Sensitivity.

• Spectral Range: 7-14 Um, Uncooled Focal Plane Array, 200 G Anti Shock/Vibe II

Axis.

• Lens: Athermalized/Hard Carbon HD High Transmission LWIR Germanium

Precision Optical Elements Fixed & Continuous Optical Telephoto Zoom F/1.0 – F/1.2

• Field of View: Dependent on Lens from 90 degrees WFOV to 1.2 Degree NFOV/Fixed or CZ.

• Image Stabilization: Yes.

• Electronic Zoom: Yes.

• Detection Ranges: Vessels at 19.9 Km / Human at 10.4 Km

• Status Symbology: On Screen on/off

• Image Processing: Auto image correction/enhancement anti-glare and bloom via

DSP and FPGA

• Noise Equivalent Temperature: 30 mK/imaging range from -42C to +560C, 14Bit

Digital, Enhanced Dynamic Range.

HD COLOR EO IMAGER

• Image Sensor: HD CMOS BSI CCTV COLOR IMAGER/NIR 400-1100nm

Imager.

• Imager Features: Backlight Compensation, Sync, High Sensitivity Mode, AWB, Auto Iris/EV/AE/AF

• Video: High Definition 1080P

• Noise Reduction: Yes

• Wavelength: 400 Nm to 100 Nanometer with IR detection

• Day Night: Auto Switching

• Lens: Continuous Optical Zoom

• Material: Quartz

• Digital Zoom: Yes

• Aperture: F/1.4

• Image Stabilization, Electronic Shutter & Wide Dynamic Range: Yes

GIMBEL PTZ FEATURES

• Positioning: 360 degrees pan/90 degrees tilt Precision TTD

Tracking/Targeting/Detecting

• Velocity: <0.001 to 90 Degree Pan / <0.001 to 90 Degree Tilt

• Type: 3D Titanium Direct Drive close Loop

• Built in Protocols: Pelco-D, Universal analog/Digital Protocols Available

• Image Stabilization: Yes / <80 Micro radians Per Axis / Tower

• Acceleration: 200 degrees/S2 in Pan and Tilt

• Resolution: 19 Bits

• Type: Absolute/100% Duty Cycle/Zero Backlash precision positioning, Pressure movement variable velocity horizontal/Vertical speed control

• Presets: 130

• Accuracy: 0.0006 Degrees

• Motors: Direct Drive

• Baud Rate: 2400/4800/9600/19200 bps

ELECTRICAL

• Video Out: Analog/Digital

• Connectors: Military Style Twist Lock all in one/Sealed

• MIL-Std 810E: Rain, sand/dust, shock & vibration

• Input Voltage: 12VDC / Options available

• Protection: Grounded/Shielded

• Power Consumption: <30W

3.2.2.2.2 Site Survey

The contractor shall perform site surveys at required locations. The findings of the site survey and any actions required in preparation for system installation shall be documented.

3.2.2.2.3 Systems Engineering

The contractor shall provide systems engineering solutions for the analysis, design, integration, installation, testing and life-cycle support of new and upgraded systems associated with delivery of infrastructure capabilities as defined by the AF enterprise architecture. The contractor shall employ disciplined systems engineering processes in accomplishing contract tasking, using commercial best practices in accordance with AFI 63-1201, Life Cycle Systems Engineering, for systems engineering processes in planning, architect, requirements development and management, design, technical management and control, technical reviews, technical measurements, integrated risk management, decision analysis, inspections and maintenance, sources of supply maintenance and repair, and test and evaluation, verification and validation.

These systems engineering solutions shall follow industry standard engineering processes. TOs will further refine the systems engineering processes according to MAJCOM or functional policies and practices. The contractor shall employ the principles of open technology development described in the DoD Open Systems Architecture Contract Guidebook for Program Managers and in NetCentric Enterprise Solutions for Interoperability (NESI) body of knowledge, and systems engineering activities used in developing contractor solutions shall adhere to open architecture designs for hardware.

3.2.2.2.2. 3 System Upgrade/Update Support

3.2.2.2.2.

Post-Cutover Support

Each solution shall include a warranty as specified in Section I, Clause 52.246-17. In addition to FAR Clause 52.246-17, the following additional requirements apply: Users shall have highly reliable and maintainable telephony products and system solutions to interoperate with the described environment. Components shall be maintainable and expandable by the user without voiding the warranty coverage.

In addition to any OEM warranty coverage, three types of post cutover operation and maintenance support shall be provided: System Support, Workmanship Support and Construction Support. The contractor shall provide for restoration of the system and repair of equipment in a timeframe specified as required by this contract, unless stated otherwise in the TO. The means to transport equipment and repair personnel both to and from the government site is the responsibility of the contractor. The contractor shall provide technical support, software support and hardware replacement for failed components, engineering support and maintenance services necessary to ensure active management, reliable operations and rapid restoration. These technical support services shall include Tier II to Original Equipment Manufacturer (OEM) level support as required based on the need to achieve problem resolution. All technical support shall be provided by certified technical personnel fluent in the English language. If the Offeror is alerted to a degradation or failure, the Offeror shall provide immediate support to the operational user to identify, troubleshoot and remedy the problem. The Offeror shall execute all hardware repair actions necessary to return the affected system to full operational capability. If the failed equipment is no longer under any alternative warranty support, the Offeror shall provide replacement equipment. Technical support shall be provided on a continuous, as-needed basis twenty-four (24) hours per day, 365 days per year for systems, peripherals, applications and devices deployed. The contractor shall provide toll free, email, DSN and PSTN access capabilities to contact requesting support for support issues.

3.2.2.2.3 Design/Integration Reviews

The contractor shall conduct design and integration reviews if required in the TO and in compliance with disciplined system engineer processes. These may be formal or informal preliminary and final design reviews.

The contractor shall identify technical issues and document the opportunities for resolving the issues. The contractor shall report impacts of the issues such as costs, and schedule dependencies and recommend solutions.

3.2.2.2.3. 3 Prototypes

3.2.2.2.3.

Preliminary Design/Integration Review (PDR)

During the PDR, the contractor shall present initial draft system design associated with delivery of infrastructure capabilities for government review.

The draft documents to be reviewed shall include those specified in the TO. Examples may include the system requirements, the final Site Survey Report, System Design, Installation Specification (IS), Engineering Drawings and Installation Plan.

36 CS will review final design for acceptance or non-acceptance of preliminary design. 36 CS will provide comments if final design is declined.

3.2.2.2.2.3 Final Design/Integration Review (FDR)

During the FDR, the contractor shall present final system design documentation associated with delivery of infrastructure capabilities as defined by the enterprise architecture for government review. The documents shall consist of those identified in the TO. Upon government approval of the FDR documentation, the contractor will be authorized to proceed with the installation. If discrepancies are identified, the contractor shall correct all discrepancies and another FDR may be required at the discretion of the government.

3.2.2.2.4 Site Preparation

As part of an overall system design and installation, the contractor may be required to perform site preparation support as required by the IS and approved by the Government Contracting Officer. The Government may, at its option, perform any portion or all of the requirements documented in the site survey report. Base civil engineering functions (or equivalent) will be used whenever possible. The contractor shall work with the base Quality Assurance Personnel (QAP) to accept civil engineering functions (or equivalent) as being in accordance with the approved implementation plan prior to beginning work. The final IS shall specify what site preparation the Government will perform and what site preparations the contractor will perform.

The Contractor shall designate the Contractor's on-site team leader and alternate(s) as the Site

POC for this project in their Site Visit Request Letter. The Site POC or alternate(s) shall be on site during duty hours until project completion. The Site POC shall be the interface for all work site communications with the Government, including quality, safety, and discrepancy matters. The Project Manager, Site POC, and respective alternate(s) shall be able to read, write, speak, and understand English.

3.2.2.2.4.2 Pre-Installation Briefing

As required by the TO, the contractor shall present pre-installation briefings at the user sites.

These briefings shall include the implementation strategy, installation schedule, verification that all allied support is completed and the site is ready for installation and discussions of any potential problem areas. Additional pre-installation briefings may be held, as required by the government. The Contractor shall conduct an in-brief with the 36th PM or designated representative and other site personnel before the start of site survey or implementation. The in-brief shall familiarize the customer with the purpose of the Contractor's visit and coordinate the project schedule (e.g. arrange for required escorts; Quality Assurance personnel schedule; etc.).

3.2.2.2.4.3 Government Support

The government will furnish facilities and utilities to the contractor, including light, heat, ventilation, electric current and outlets for use by installation personnel as required and stated in TOs. These facilities and utilities will be provided as specified in the Site Survey Report. These facilities will be readied prior to arrival of contractor personnel and be provided at no cost to the contractor. The contractor shall provide required temporary utilities, which are not readily available in the work area. The contractor shall coordinate, through the on-site COR, any requirement before temporary disconnection of a utility. The contractor shall submit a request in writing to the on-site COR fourteen (14) days in advance of the utility disconnection.

3.2.2.2.4.3 Installation

The contractor shall engineer, install, configure, modify, relocate or remove Communication and Information (C&I) systems for operational use. The systems and equipment installations or modifications must comply with established architectures. The contractor shall perform validation and verification testing on the system, assist users in configuring the system to meet their system requirements and provide all applicable operating manuals/system management guides. Further, the contractor shall provide pre-cutover and post-cutover on-site training IAW with TOs.

3.2.2.2.4.

3 Inside Plant

3.2.2.2.4.

N/A

. 3 3 Inside Plant Fiber Optic Distribution Panel Installation

3.2.2.2.4.

. 3 3 Fiber Optic Distribution Panel Marking

3 Outside Plant

3.2.2.2.4.

Installation

Inner-duct installation

N/A

. 3 3 Grounding and Bonding

3.2.2.2.4.

Fiber Optic Cable Installation

3.2.2.2.4. . . 3 3 3 FOC Terminations and Splicing

N/A

3.2.2.2.4. . . 3 3 3 FOC Maintenance Loop

N/A

3.2.2.2.4.

N/A

. . 3 3 3 Identification/Marking

3.2.2.2.4.

. . 3

3 Installation Schedule

. . 3

3 As-Built Drawings

3.2.2.2.4. 3 Tools and Testing Support

The contractor shall provide all tools, installation materials and test equipment required to perform any required product installation and maintenance as called for by the TO. All tools and test equipment shall remain the property of the contractor. Any damage caused by the contractor to existing site facilities or equipment which might occur during site preparation, installation, testing or cutover of the system will be repaired at the expense of the contractor unless otherwise directed by the government. The site shall be restored to the original condition which existed prior to the event unless otherwise directed. The TO will specify testing and inspection requirements. The contractor shall demonstrate that the system design meets the reliability/availability/maintainability requirements of the TO.

The Contractor shall furnish all test equipment and personnel required to conduct testing. The Contractor shall record all inspections and tests as they are accomplished and make all test sheets/results available for 36 SFS/S5 representative as tests are completed. The Contractor shall notify the 36 SFS/S5 at least 5 calendar days prior to any testing. All testing will be IAW accepted telecommunications industry standards for the type of test being conducted. The Contractor shall provide test reports to the government within 10 calendar days of completing the testing. Contractor is required to locate/repair any testing irregularities if caused by the installation.

3.2.2.2.4. . 3 3 Installation Test Plan

The Contractor shall provide a test plan as to how the system shall be pre-tested, in-progress-tested, post-tested and cut-over plan to demonstrate to the Government that the system is fully operational and meets or exceeds the specified requirements and that the system is fully ready to be placed into service. The Contractor shall test the system to demonstrate its proper performance to the Government quality assurance representative. These tests shall be accomplished prior to the system being placed into service (CDRL A326, A020).

3.2.2.2.4. . 3 3 Acceptance/Installation Test Report

The Contractor shall provide an installation test report of the results of the testing accomplished under the installation test plan. The Test Report(s) shall be provided to the Government no later than 10 calendar days after test(s) have been completed (CDRL A326, A020).

3.2.2.2.4. . 3 3 Final Acceptance

The Contractor shall schedule a final project walk-through with the Base POC. This should be scheduled 10 calendar days prior to acceptance.

3.2.2.2.4. 3 Site Restoration/Debris Removal

The Contractor shall be responsible for surface restoration. Restoration at each location shall be subject to final inspection and approval by the Base Civil Engineer (BCE) IAW guidelines set forth by the BCE. The Contractor shall remove and dispose all cutout/abandoned cables associated with this requirement. The Contractor shall dispose of all residues from this project off base and in accordance with (IAW) local and base environmental laws and regulations.

3.2.2.2.4. 3 Service Outages The Contractor shall be responsible for preventing any unscheduled (i.e. cutting or disabling any in-service cables or equipment.), Contractor-caused, interruptions of communications capabilities that are properly identified. The Contractor shall coordinate planned outages with the site POC at least 10 calendar days in advance of the outage if the implementation necessitates disruption of service, (e.g., communications, electrical, or other utilities).

3.2.2.2.4. 3 National Pollution Discharge Elimination System (NPDES) If required by Base Civil Engineer (BCE), the Contractor shall obtain approvals for NPDES at State and/or Federal level [in some locations this may be called the Storm Water Pollution Prevention Plan (SWPPP)]. The storm water/environmental plan is the sole responsibility of the Contractor. Base Civil Engineering/CEV will review and advise to ensure minimum standards and storm water controls/BMPs are in place to ensure compliance; this is a compulsory item in the SOO and contract. The Contractor shall implement storm water controls/BMPs to ensure sediment, as a result of storm water runoff, does not enter storm drainage channels and/or inlets.

The Contractor shall conduct an initial meeting within 10 days of the Contractor site survey with the base environmental office to identify NPDES preparations and/or the storm water/environmental plan.

The Contractor shall review the NPDES requirements applicable to the base; develop a plan to comply with the NPDES; obtain approval of the NPDES plan from all appropriate government agencies; and comply with any other applicable state requirements for construction.

The Contractor shall implement, monitor and manage the NPDES Plan.

3.3 Dynamic Test Environment

N/A

3.3.1 Design

N/A

3.3.2 Implementation

N/A

3.3.3 Operation

N/A

3.4 Communication Operations and Maintenance (O&M)

N/A

3.5 General Requirements

3.5.1 Contractors Use of NETCENTS-2 Products Contract

The contractor shall obtain all products and associated peripheral equipment required by each individual TO from the NETCENTS-2 Products contract.

3.5.2 Enterprise Software Initiative

See DFARS 208.7402 regarding use of the DoD’s Enterprise Software Initiative (ESI)

Blanket Purchase Agreements (BPAs) for software license purchases.

3.5.3 Software License Management

3.5.4 Hardware

All hardware provided in support of solutions under this contract shall include all software and associated hardware required for operations (such as controllers, connectors, cables, drivers, adapters, etc.) as provided by the OEM.

3.5.5 Software Support

N/A

3.5.6 Government Furnished Equipment (GFE)

N/A

3.5.7 Host Nation Installations

N/A

3.5.8 Tools and Test Equipment SHOULD BE INCLUDED IN TOOLS AND TESTING

PLAN ABOVE

Unless specified otherwise in the TO, the contractor shall provide all tools and test equipment required to perform any required product installation and maintenance as called for by the TO.

All tools and test equipment shall remain the property of the contractor.

3.5.9 Warranty

Each product shall include a warranty as specified in Section I, Clause 52.246-17. In addition to FAR Clause 52.246-17, the following additional requirements apply: Users shall have highly reliable and maintainable network-centric products and system solutions to interoperate with the described environment. Components shall be maintainable by the user without voiding the warranty coverage. Components, which are expandable, shall be expandable by the user without voiding the warranty coverage provided the government adheres to standard commercial practices in accomplishing the additions. Three types of warranty shall be provided:

1. System Warranty

2. Workmanship Warranty

3. Equipment Warranty

The warranty program shall provide for restoration of the system and repair of equipment in a timeframe specified in this contract, unless stated otherwise in the TO. The contractor shall provide means to transport equipment and bear transportation charges and responsibility for equipment and repair personnel under warranty while in transit both to and from the government site.

3.5.9.1 System Warranty

Unless specified otherwise in the TO, the contractor shall provide a minimum 1-year system warranty (some customers may require 2 or more years of warranty) to include coverage of all equipment supplied, installed and integrated by the contractor associated with delivery of infrastructure capabilities as defined by the AF EA. The system warranty shall ensure the full operational use of the system (CFE and GFE). The contractor shall provide to the government a 24-hour a day, 7-day a week point of contact for the system warranty. The system warranty shall begin at the time the final system DD Form 250 is signed by an authorized government representative. The system warranty shall provide fault diagnosis, hardware and software repair, replacement or redesign. The contractor shall be responsible for diagnosing any problems, identifying malfunctioning equipment and removing the equipment for repair. Prior approval shall be obtained from the authorized government site representative before any GFE is removed from the system. Actual repair of malfunctioning GFE will be the responsibility of the government, unless stated otherwise in the TO. The system warranty shall include transportation for both contractor personnel and equipment to and from the specific site. The system warranty shall provide for a return to service any malfunctioning CFE component or applications within 48 clock hours CONUS, 96 clock hours OCONUS, after notification by the authorized government site representative unless stated otherwise by the TO. Costs for system warranty will be included within each TO proposal provided by the contractor as required by the TO.

In lieu of a system proposal that includes a traditional warranty, the customer and contractor may agree to a basic system proposal plus a block of hours for contractor Maintenance Support Services. For many contractors and customers, this strategy has proven advantageous since traditional system warranties can be voided by today's dynamically changing networks forcing the customer to maintain the network in a static environment during the warranty period. In addition, support is limited to a much narrower scope with a traditional system warranty whereas a contractor Support Services contract is much more flexible in solving problems as they arise within the entire Network-Centric environment.

3.5.9.2 Workmanship Warranty

Unless specified otherwise in the TO, the contractor shall provide a minimum 1-year workmanship warranty (some customers may require 2 or more years of warranty) on all work provided or integrated under this contract. The warranty shall ensure the full operational use of the system (CFE and GFE). The contractor shall provide to the government a 24-hour a day, 7-day a week point of contact for the workmanship warranty. The workmanship warranty shall begin at the time the final system DD Form 250 is signed by an authorized government representative. The workmanship warranty shall provide fault diagnosis, hardware and software repair, replacement or redesign. The contractor shall be responsible for diagnosing and fault isolation of any problems, identifying the poor workmanship causing the problem and affecting an acceptable industry standard repair. Prior approval shall be obtained from the authorized government site representative before any GFE is removed from the system. Actual repair of malfunctioning GFE will be the responsibility of the government. The workmanship system warranty shall include transportation for both contractor personnel and bits, pieces and parts to and from the specific site and the actual repair. The workmanship warranty shall provide for a return to service any malfunctioning CFE component or applications within 48 clock hours CONUS, 96 clock hours OCONUS, after notification by the authorized Government site representative unless stated otherwise by the TO.

3.5.9.3 Construction Warranty

3.5.9.4 Equipment Warranty

Unless specified otherwise in the TO, the contractor shall provide standard, OEM pass through, extended or otherwise warranties for the periods specified in the TO for all hardware and software products, for both CONUS and OCONUS government sites located worldwide.

Repairs shall be accomplished within 48-clock hours CONUS, 96-clock hours OCONUS, of receipt of the equipment warranty trouble call, unless stated otherwise by the TO, when the contractor is performing the warranty repair. The warranty shall also provide for repair or replacement of equipment and repair and distribution of updated software to all users who purchased the software from this contract. ,Warranty coverage commences on the date of acceptance in block 21B of the DD Form 250, Commercial Invoice dated and signed or SF 1449 dated and signed.

The contractor shall provide a worldwide warranty repair solution capability for systems with qualified maintenance repair personnel and leverage existing OEM support infrastructures to the greatest extent possible. Repairs shall be performed at a time required by the Task/Delivery Order/Delivery Order or as coordinated by the government COR. The contractor shall provide a 24-hour, 7-day a week warranty repair point of contact to receive calls from the government. The contractor shall provide the capability for toll-free telephone access for obtaining technical warranty repair support assistance from worldwide locations. The contractor shall provide the tools, equipment and consumables required for personnel to complete their duties. The contractor shall not invalidate the warranty provided on components purchased under this contract when the government elects to perform user self-maintenance and/or self-installation during the warranty period. Note: The government will perform routine user-maintenance for all equipment both during and after the warranty period using separately orderable spare parts and/or repaired parts from this contract. The government will only be liable for any damage to the equipment that results from government maintenance or additions to equipment that did not adhere to stand commercial practice. At no additional charge to the government, the contractor shall furnish, for hardware purchased under this contract, all repairs (labor and parts) for the duration of the warranty period. At a minimum, repair during the warranty period shall be equivalent to standard per-call maintenance during the Principal Period of Maintenance (PPM) as specified in this PWS. The government, at its option, may order additional repair coverage during the warranty period. The government’s purchase of additional repair coverage will be specified in details by the TO.

All parts replaced during the warranty period, in an unclassified environment, shall become the property of the contractor. However, in classified environments the government will maintain title of certain items. These items typically will be broken storage devices/mediums. All other parts may be returned to the contractor and the government will have up to 30 days to relinquish possession of the part.

The warranty shall not apply to maintenance required due to the fault or negligence of the government. If government negligence results in a repair call (either for equipment under warranty or per call maintenance), the maximum repair time shall not apply and the government will pay the price per hour specified in the contract for the hours rendered to complete the repair.

Only new or reconditioned parts shall be provided for repairs. If reconditioned parts are provided, the reconditioned parts shall carry the same warranty provisions as originally provided by the contractor for new parts.

The contractor guarantees to repair at no charge any malfunction which reoccurs within 90 calendar days of the initial repair. Warranty of Repair is a separate warranty from those described elsewhere in the contract.

If the contractor elects to replace the malfunctioning hardware, the contractor shall either provide the government with a permanent replacement which shall contain a unique serial number or shall provide the government with a temporary replacement with a unique serial number. If the contractor elects to repair the malfunctioning hardware, the contractor shall repair and return the repaired hardware to the government at which time the temporary replacement shall be surrendered to the contractor at the contractor’s expense.

3.6 Maintenance

N/A

3.6.1 Per-Call Maintenance/Standard Per-Call Maintenance (SPCM) N/A

3.6.2 Contractor Provided Non-Cable Plant, Non-Switching System SPCM N/A

3.6.3 Government Owned Equipment Non-Cable Plant, Non-Switching System SPCM N/A

3.6.4 Switching System SPCM

N/A

3.6.5 Cable Plant Maintenance

N/A

3.6.6 Rapid Response Per-Call Maintenance (RRPCM)

N/A

3.6.7 System Maintenance

N/A

3.6.8 Maintenance Charges

N/A

3.6.9 Maintenance Alternative

N/A

3.6.10 Relocation and Removal

3.7 Surge Requirements

3.8 Unified Capabilities Requirements (UCR)

N/A

3.9 Special Asset Tagging

See DFARS 252.245-7001 regarding Special Asset Tagging requirements.

4. Contractual Requirements

The period of performance for this Task Order the contractor shall have 120 days from contract award to complete all facets of the project including final walk thru with the government representative. The contractor shall provide a work schedule IAW CDRL A315.

The Contractor shall routinely work during normal operating hours of the site. Monday through Friday (0730-1630 hrs), excluding federal holidays. Any site work requested by the Contractor to be performed outside of normal duty hours shall be coordinated with the Base POC at least 10 working days in advance.

4.1 Performance Reporting

The contractor’s performance will be monitored by the government and reported in Contractor Performance Assessment Reporting (CPARs). Performance standards shall include the contractor’s ability to:

1. Provide quality products, incidentals and customer support.

2. Meet customer’s agreed-upon timelines for scheduled delivery of items, warranty, and/or incidental services: Emergency/critical, Maintenance/Warranty – 24 x 7 x 365, and remote OCONUS, OCONUS vs. CONUS response times.

3. Provide satisfactory product repairs or advance replacement, as appropriate.

4. Provide timely and accurate reports.

5. Respond to the customer’s requests for proposals and configuration assistance as identified in each delivery order.

6. Meet subcontracting goals.

4.1.1 Weekly Status Reports

The Contractor shall prepare a Weekly Status Report and distribute to IPT members. The purpose of the report is to inform IPT members of project progress, problems being encountered, and other topics necessary/beneficial to ensure success and timely completion of the contract requirements. The Status Report and meeting agenda may be combined as long as the resulting report contains all the required elements and contains sufficient detail to serve as project record

(CDRL A035, A287).

4.2 Program Management

The contractor shall identify a Program Manager who shall be the primary representative responsible for all work awarded under this contract, participating in Program Management Reviews and ensuring all standards referenced herein are adhered to.

4.2.1 Services Delivery Summary

All deliverables are subject to Government acceptance and approval. They shall meet professional standards and the requirements set forth in this Task Order. All deliverables shall be produced using recommended software tools/versions as accepted by the Government.

CDRL Data Item Title

A020 Installation and Acceptance Test Plan (IATP)

A035 Contractor's Progress, Status and Management Report

A287 Report, Record of Meeting/Minutes

A315 Integrated Master Schedule (IMS) (Replaces DI-MISC-81183)

A326 Test Plans/Test Procedures

4.2.2 TO Management

The contractor shall establish and provide a qualified workforce capable of performing the required tasks. The workforce may include a project/TO manager who will oversee all aspects of the TO. The contractor shall use key performance parameters to monitor work performance, measure results, ensure delivery of contracted product deliverables and services, support management and decision-making and facilitate communications. The contractor shall identify risks, resolve problems and verify effectiveness of corrective actions. The contractor shall institute and maintain a process that ensures problems and action items discussed with the government are tracked through resolution and shall provide timely status reporting. Results of contractor actions taken to improve performance should be tracked and lessons learned incorporated into applicable processes. The contractor shall establish and maintain a documented set of disciplined, mature and continuously improving processes for administering all contract and TO efforts with an emphasis on cost-efficiency, schedule, performance, responsiveness and consistently high-quality delivery. The Contractor shall provide the latest system installed as provided by the original manufacturer with all new equipment. These will be provided to 36 SFS/S5 PM.

The contractor shall chair a weekly IPT meeting consisting of contractor representatives, the Contracting Officer, Program Manager, Engineer, and representatives of the 36 CS, and other base personnel as requested. The Contractor shall provide a United States wide “Meet Me” teleconference capability for the duration of the project. The purpose of this meeting is to discuss project progress, problems being encountered, and other discussions necessary/beneficial to ensure success and timely completion of the Task Order. The Contractor shall record and distribute meeting minutes within two workdays of each meeting (CDRL A035, A287).

4.2.3 Configuration and Data Management

The contractor shall establish, maintain and administer an integrated data management system for collection, control, publishing and delivery of all program documents. The data management system shall include but not be limited to the following types of documents: CDRLs, White Papers, Status Reports, Audit Reports, Agendas, Presentation Materials, Minutes, Contract Letters and TO Proposals. The contractor shall provide the government with electronic access to this data, including access to printable reports. The contractor shall have an approved property control system IAW FAR 45, DFARS 245 and approved procedures to document and track all GFM and GFE. The contractor shall provide as-built documentation including, but not limited to, drawings and diagrams of the solution provided under each TO identifying specific cards in a chassis/shelf. The as-built documentation shall also include layout drawings, power drawings/specifications, floor plans and engineering specifications generated in support of the installation of the system. Documentation shall also include equipment listing with serial/model numbers and manufacturer specifications.

4.2.4 Records, Files and Documents

All physical records, files, documents and work papers, provided and/or generated by the government and/or generated for the government in performance of this PWS, maintained by the contractor which are to be transferred or released to the government or successor contractor, shall become and remain government property and shall be maintained and disposed of IAW AFMAN 33-363, Management of Records; AFI 33-364, Records Disposition – Procedures and Responsibilities; the Federal Acquisition Regulation, and/or the Defense Federal Acquisition Regulation Supplement, as applicable. Nothing in this section alters the rights of the government or the contractor with respect to patents, data rights, copyrights, or any other intellectual property or proprietary information as set forth in any other part of this PWS or the NetOps and Infrastructure Solutions contract of which this PWS is a part (including all clauses that are or shall be included or incorporated by reference into that contract).

4.3 Security Management

4.3.1 Safeguarding Classified Information

The contractor shall transmit and deliver classified material/reports IAW the National Industrial Security Program Operations Manual (NISPOM) and the National Industrial Security Program Operating Manual (DoD 5220.22-M). These requirements shall be accomplished as specified in the TO. All Classified Contracts must have at a minimum, the Clause 52.204-2 Security Requirement, incorporated into the contract.

Each base will follow its own classified process IAW with the proscribed Federal guidance of the NISPOM and FAR “Subpart 4.4 along with DD Form 254. When transmitting classified information ensure all classified information is properly sanitized and/or degaussed of all sensitive/classified information IAW AFSSI 5020.

For assistance and guidance on submitting Classified TO, the NETCENTS-2 Customer Service can be reached at COMM 334-416-5070 / DSN 312-596-5070 Option 1.

Network infrastructure drawings (MHDS, MH/HH locations, fiber paths, etc.) are on the 36 CS Critical Information List and must be protected. The Contractor shall take appropriate measures to protect detailed information pertaining to the EFI&T effort, to include appropriate marking of documents as “For Official Use Only (FOUO),” and ensuring limited distribution of documents and schematics/drawings to only those individuals with a valid need to know. IAW AFI 10-701, OPSEC Considerations, the contractor shall develop an OPSEC plan to ensure the protection of FOUO data either furnished by the government or produced by the contractor. The contractor’s OPSEC plan provided in the RFP shall be incorporated into the PWS.

4.3.2 Personnel Security

Individuals performing work under these TOs shall comply with applicable program security requirements as stated in the TO. NETCENTS-2 will support the following levels of security:

Unclassified; Unclassified, But Sensitive; Secret (S); Secret Sensitive Compartmented Information (S/SCI); Top Secret (TS) and Top Secret Sensitive Compartmented Information

(TS/SCI).

Certain TOs may require personnel security clearances up to and including Top Secret and certain TOs may require all employees to be United States citizens. The security clearance requirements will depend on the security level required by the proposed TO. The TOs may also require access to Sensitive Compartmented Information (SCI) for which SCI eligibility will be required. Contractors shall be able to obtain adequate security clearances prior to performing services under the TO. The Contract Security Classification Specification (DD Form 254) will be at the basic contract and TO level and will encompass all security requirements. All contractors located on military installations shall also comply with Operations Security (OPSEC) requirements as set forth in DoD Directive 5205.02, Operations Security Program and AFI 10- 701, Operations Security. In accordance with DoD 5200.2-R, Personnel Security Program (Jan 87), DoD military, civilian, consultants and contractor personnel using unclassified automated information systems, including e-mail, shall have, at a minimum, a completed favorable National Agency Check plus Written Inquiries (NACI).

The types of Personnel Security Investigations (PSI) required for the contractor vary in scope of investigative effort depending upon requirements of the government and/or conditions of the contract/TO. In cases where access to systems such as e-mail is a requirement of the government, application/cost for the PSI shall be the responsibility of the government. In cases where access to systems is as a condition of the contract/TO, application/cost for the appropriate

PSI shall be the responsibility of the contractor. In such instances the contractor shall diligently pursue obtaining the appropriate PSI for its employees prior to assigning them to work any active TO. Acquisition planning must consider Antiterrorism (AT) measures when the effort to be contracted could affect the security of operating forces (particularly in-transit forces), information systems and communications systems IAW DoD Instructions 2000.16 Anti- Terrorism Standards.

The Contractor shall process a Site Access Letter (36 CS/SCXP PM). This letter shall identify the names, social security numbers, driver’s license numbers and state of issue, and birth date of the personnel who will performing on this PWS for required background check by Andersen Security Forces.

4.3.3 Protection of System Data

Unless otherwise stated in the TO, the contractor shall protect system design-related documents and operational data whether in written form or in electronic form via a network in accordance with all applicable policies and procedures for such data, including DOD Regulations 5400.7-R and DoDM 5200.01 to include latest changes and applicable service/agency/combatant command policies and procedures. The contractor shall protect system design related documents and operational data at least to the level provided by Secure Sockets Layer (SSL)/Transport Security Layer (TSL)-protected web site connections with certificate and or user id/password-based access controls. In either case, the certificates used by the contractor for these protections shall be DoD or IC approved PKI certificates issued by a DoD or IC approved External Certification Authority (ECA) and shall make use of at least 128-bit encryption.

4.3.4 On-Site Task Approval Process

The contractor shall, for CONUS tasks (7-day notice) and for OCONUS tasks (14-day notice), notify the on-site COR in writing before a requirements analysis/conceptual design visit, site survey and other on-site tasks are to be performed. The following information must be provided:

Names of Employees, SSAN, Security Clearance, Location, Project Number, On/About Date Planned for On-Site Work, Anticipated…