Attachment 01a IDIQ PWS.pdf

Controlled Unclassified Information (CUI)

PERFORMANCE WORK STATEMENT (PWS)

Pentagon Force Protection Agency (PFPA)

Integrated Security Services Contract 4 (ISSC)

PART 1

GENERAL INFORMATION

1. GENERAL: This is a non-personal services contract to provide Integrated Security Services. The

Government shall not exercise any supervision or control over contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Prime Contractor who, in turn is responsible to the Government.

1.1. Description of Services/Introduction: The Pentagon Force Protection Agency (PFPA) Integrated

Security Services Contract (ISSC) is a total system approach for providing integrated electronic and physical security systems for the Pentagon Reservation, Mark Center, Defense Health Headquarters

(DHHQ), DoD leased facilities, and Raven Rock Mountain Complex (RRMC) in Adams County, PA.1.

1.2. Background: Previous contracts for this requirement, awarded in 2007, 2012, and 2016 provided comprehensive security integrator services to PFPA. Since inception, contract scope has expanded to include additional facilities, new systems, and increased security capabilities. This contract provides baseline support (system support, maintenance, repair, and logistics) to security applications to the multiple facilities above. That support will be issued and funded with task order one. Subsequent task orders will be for ordering hardware and installation of security systems and components in those facilities.

1.3. Objectives: The Government’s four, inter-related high-level objectives for the ISSC are:

Scalability and Interoperability – Systems shall be capable of scaling to accommodate additional users, sensors, capabilities, and facilities. Similarly, systems shall be able to adjust down as facilities are closed, suites are decommissioned, or requirements adjusted. Systems and their components shall to the maximum extent possible, utilize open standards and commercial-off-the-shelf (COTS) technology. Standard network protocols shall be used to traverse the Government’s network. Wherever computers are required, they shall be widely available models based on open systems architecture. Standard operating systems shall be used, such as but not limited to Microsoft Windows, Linux, and UNIX for the computer-based systems provided under ISSC.

Availability and Resiliency – The Government has a goal of operating ISSC systems at or near a 100% operational level. Systems shall be designed and implemented to be resilient to failure such that a failure of a single component should not incapacitate the entire system. To achieve this goal, the Contractor shall leverage industry best practices for assuring resiliency and availability, including but not limited to:

Built-in redundancy

Automatic failover

Fault tolerance

Virtual environments

Data backup

Data archiving

Automatic updates of operating systems (OS) and applications

Notification of software/hardware approaching end of life

Power-on replacement i.e. hot swapping components or peripherals

Power

Continuous i.e., uninterruptible power supplies (UPSs)

Backup power i.e. batteries and generators

Surge suppressors

For the purposes of this contract, system reliability is defined as the probability that a system or subsystem, including all hardware, firmware, and software will satisfactorily perform the intended function(s) for which it was designed, during the duration for which it is in operation, and in the operational environment.

The Contractor shall maintain system reliability at a level equal to, or higher than, the systems documented percentage or failure rate provided by the manufacture and/or as required by regulatory requirements for classified areas.

For the purposes of this contract, system availability is defined as the ratio of time a system, subsystem, or component is functional to the total time it is required or expected to function.

For the purposes of this contract, system serviceability is defined as the ease with which a component, device, or system can be maintained and repaired. All precautions should be taken to maintain and repair systems to cause as little downtime or disruption as possible and within the expected reliability and availability standards stated in this contract. The Contractor shall notify the government of any potential problems or recommended actions critical to systems operations that can be addressed by maintenance and repair, as far in advance as possible to minimize downtime or failure.

Factors that do not impact contractual requirements for system reliability, availability, or serviceability are where root cause of problems are as a result of network, power, or other external factors outside the scope of this contract and maintained by OGAs or Other Government Contractors (OGC). Outages caused by external factors shall not count against the availability or reliability statistic until the network, power, or other external factor has been restored, but may require support for the application or equipment impacted.

Reliability and Cost Sustainability – Systems and services shall be affordable across the full lifecycle while meeting the Government’s requirements, minimize the use of custom and proprietary solutions, and remove systems, hardware, and software before they incur excessive sustainment costs or reach end of service.

Accountability and Customer Satisfaction – Systems and services shall be designed and implemented, and quality checked (i.e. QA/QC) to be user friendly, mindful of the impact and sensitivities of the customer workspace, high performing, and to meet contractual service requirements

1.4. Scope: This contract shall require the contractor to maintain, repair, install, and support all aspects of electronic security systems, including but not limited to, access control; intrusion detection; visual surveillance and intelligent video analytics; physical security information management; license plate recognition; gunshot detection; under vehicle inspection; identity, credential, and access management; mass notification; biometric and multi-modal authentication; computer aided dispatch and other law enforcement mission applications; chemical, biological, radiological detection and mitigation; and operations center collaboration visualization systems.

In addition, the contract shall support all aspects of physical security, including but not limited to, personnel, vehicle, cargo, and parcel screening systems; ballistic rated glass, booths, kiosks, and mobile shields; blast-resistant waste receptacles, doors (sound-rated and force protection), window film, locks, and door hardware.

The contractor shall support all aspects of passive and active barriers, including but not limited to, turnstiles, fencing, bollards, gates, traffic control gate arms and anti-vehicle barriers. This contract requires support on infrastructure supporting the above systems, including but not limited to, cabling for electrical and information technology, trenching, grading, utilities, conduit placement, and other civil types of work.

All aspects of the scope will be provided in detail through task orders, to include the first task order to maintain, support, repair, and manage all electronic security systems at the Pentagon, RRMC, and other

DoD facilities owned and leased in the National Capital Region (NCR).

To deliver these capabilities, the Contractor shall provide the following services:

a) Full Lifecycle Systems Engineering. The Contractor shall be responsible for providing full lifecycle systems engineering services for upgrades or new electronic and physical security systems. The full lifecycle shall include requirements elicitation and analysis, design, development, testing, installation, configuration, integration, verification and validation, transition, sustainment, and decommissioning.

b) System Support, Sustainment, and Administration. The Contractor shall be responsible for sustainment support of electronic security systems. This support includes system monitoring, troubleshooting, patching and software updates, configuration, and administration.

c) Third Party Software and OGC Support. The Contractor shall provide support to 3rd party software integrations and the OGC installing and maintaining it. This support includes software upgrades, existing or new connections/integrations to ISSC systems, testing, troubleshooting and other areas impacting either

ISSC supported systems or those maintained by OGCs.

d) Preventative Maintenance. The Contractor shall be responsible for performing periodic preventative maintenance on all electronic and physical security systems identified in this Performance Work Statement

(PWS) as well as any components installed during this contract unless specified in the individual task order

PWS. Periodic preventative maintenance shall be performed at minimum in accordance with manufacturer recommendations and may require additional preventative maintenance work due to amount of use or ambient conditions.

e) Repair and Sustain. The Contractor shall be responsible for responding to and repairing damaged, malfunctioning, or inoperable systems and their components as described in this PWS as well as any components installed during this contract unless specified in the individual task order PWS.

f) Configuration Management. The Contractor shall maintain a database of all ISSC electronic and physical security systems characteristics.

g) Logistics Management. The Contractor shall be responsible for procuring, storing, and inventory of materials and supplies to deliver services under this contract.

h) Quality Management. The Contractor shall be responsible for tracking, baselining, and identifying deviations from ISSC and manufacturers standards for quality and performance.

i) Installation, Decommissioning, Hardware, and Alterations. The Contractor shall be responsible for hardware, installation, extension, relocation, and alterations of electronic and physical security systems per

ISSC and manufacturer standards.

j) Design and Technical Evaluation. The Contractor shall be responsible for performing technical evaluations of new and existing electronic and physical security systems to assess their capacity to meet requirements, maturity, and their continued use.

k) Training. The Contractor shall be responsible for delivering initial and reoccurring training on electronic and physical security systems to Government and Contractor personnel.

The Contractor shall be responsible for:

a) Service, maintenance, and performance of existing systems and applications at the time of award of this contract.

b) Service, maintenance, and performance of new systems and applications installed and/or upgraded while this contract is in place. These systems may be installed by the ISSC Contractor, or OGCs as part of other non-ISSC construction projects.

The work to be performed on ISSC is divided into five major categories, which are:

a) System Support

b) Logistics

c) Repair

d) Maintenance

e) Installation and Hardware

Capital Improvement (This is a subcategory of Installation for accounting purposes)

Non-Capital Improvement

1.5. Period of Performance: The period of performance shall be for a five-year ordering period.

1.6. General Information:

1.6.1. Quality Control: Quality Control will be addressed at the task order level.

1.6.2. Quality Assurance: Quality Assurance will be addressed at the task order level.

1.6.3. Recognized Holidays: The Contractor is responsible for completing System Support and Repair work required under this contract irrespective of Federal holidays to include any other day designated by

Federal Statute, Executive Order or a Presidential proclamation. When the government grants administrative leave to government employees, or is closed as a result of inclement weather, potentially hazardous conditions, or other special circumstances, contractor personnel working at the specific facility/location granted administrative leave may also be dismissed at the discretion of the On-site

Manager to the extent that the overall performance is not adversely impacted. The contractor shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this

PWS when the government facility is not closed for the above reasons. All other work, including

Installation and Preventative Maintenance, shall be scheduled appropriately to meet required delivery dates.

The contractor is not required to perform service on holidays:

New Year’s Day Independence Day

Martin Luther King Jr.’s Birthday Labor Day

President’s Day Veterans Day

Memorial Day Thanksgiving Day

Juneteenth Independence Day Christmas Day

Columbus Day Inauguration Day

1.6.4. Hours of Operation: Hours of Operation will be addressed at the task order level.

1.6.5. Place of Performance: PFPA provides protection for DoD facilities in the National Capital Region

(NCR) not under a Military Department per DoD Directive 5105.68, 10 USC 2674, and 32 CFR 234.1.

This region extends from Northern Virginia through lower Pennsylvania. The current locations of DoD facilities protected by PFPA will be provided at the task order level. Facilities occupied by the Government change based on multiple factors and may increase or decrease throughout the duration of this contract.

The Contractor is fully responsible for performing work at all facilities protected by PFPA.

1.6.6. Type of Contract: The Government will award a Firm Fixed Price (FFP), Indefinite Delivery

Indefinite Quantity (IDIQ) contract.

1.6.7. Security Requirements: The security requirements are in accordance with the attached DD254.

Contractors are required to report to PFPA any derogatory information that may justify an unfavorable administrative action in a personnel security or building access determination. Derogatory information includes, but is not limited to, criminal conduct, illegal drug involvement, or psychological conditions that impair judgment, reliability or trustworthiness. Derogatory information must be provided to the COR and

Contracting Officer as promptly as possible, but in no event later than three (3) business days after the contractor becomes aware of the information.

PFPA reserves the right and prerogative to deny and/or restrict facility and information access of any

Contractor employee determined by PFPA at any time during performance to be unsuitable for access and/or present a risk of compromising sensitive Government information to which they would have access under this contract.

A determination by PFPA that a person is not suitable to perform work under this contract is not a denial, suspension or revocation of a previously granted security clearance by another agency, nor shall it be interpreted as a direction or recommendation to the Contractor regarding the suitability of an affected individual for employment outside the scope of PFPA.

Due to the sensitive of the scope of the program and task orders and the wide variety of program assignments anticipated under the contract, personnel who have been previously denied or relieved of any security duties or other security-related duties for reasons of security violations, negligence, or nonperformance of duties will not be deemed acceptable unless specifically approved by the Government and an investigation into the circumstances surrounding the denial has been completed and information provided to the KO.

1.6.7.1. Facility Clearance: The Contractor shall possess and maintain a facility clearance at the classification level of "TOP SECRET" throughout the life of the contract.

1.6.7.2. Physical Security: The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.6.7.3. Key Control: The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the

Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the QCP. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the KO.

1.6.7.3.1. In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the KO, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

1.6.7.3.2. The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the KO.

1.6.7.4. Lock Combinations: The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s QCP.

1.6.8. Special Qualifications: Contractor personnel will be required to sign a Non-Disclosure Agreement

(NDA).

1.6.8.1. Personnel Security Clearances: Personnel Security Clearances will be addressed at the task order level.

1.6.9. Post Award Conference/Periodic Progress Meetings: Post Award Conference/Periodic Progress

Meetings will be addressed at the task order level.

1.6.10. Key Personnel: Key personnel will be addressed at the task order level.

1.6.11. Identification of Contractor Employees: Identification of Contractor Employees will be addressed at the task order level.

1.6.12. Contractor Travel: Contractor Travel will be addressed at the task order level.

1.6.15. Other Direct Costs (ODCs): Other Direct Costs will be addressed at the task order level.

1.6.16. Organizational Conflict of Interest (OCI): Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent OCI as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.17. Phase in/Phase out Period: Phase in/Phase out Period will be addressed at the task order level.

1.6.18. Ordering Officer: An Ordering Officer(s) will be assigned to this contract with the authority to make purchases with a credit card. The Ordering Officer will only purchase supplies and services already identified and priced on the contract under the price list. Hardware and installation services within scope and under the micro-purchase limit will be purchased via credit card by the ordering officer. All orders will be coordinated with the COR.

1.6.19. Government Project Officer (PO): The PO will be the contractors point of contact for task orders after receipt of award. The PO will resolve technical differences not involving changes to the task order scope. All unresolved technical questions, proposed alterations or changes to scope, and unresolved differences pertaining to an individual task order must be reported to the KO.

The PO through the COR will initiate in writing to the KO notice of any changes needed in the task order.

1.6.20. Contractor Manpower Reporting:

(a) The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields using the System for Award Management (SAM):

http://www.sam.gov.

(b) The Contractor shall use the “All Other Defense Components” tool unless otherwise directed by the

Contracting Officer’s Representative or Contracting Officer.

(c) Reporting inputs will be for the labor executed during each Government fiscal year (FY), which runs

October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. The Contractor shall completely fill in all required data fields. The Contractor shall enter initial data into SAM to establish the basic contract record no later than 15 business days after receipt of contract award or contract modification incorporating this clause. The

Contractor shall notify the Contracting Officer when the basic contract record has been established in

SAM.

(d) Contractors may direct technical questions to the help desk at http://www.sam.gov.

[Reference: SECDEF memorandum of 16 October 2019, “Revised Department of Defense Contractor

Manpower Reporting”]

1.6.20.1. Telework:

1.6.20.1.1. The Government may permit telecommuting (telework) by contractor employees when determined to be in the best interest of the Government in meeting work requirements (e.g., COOP). The contractor must have an established program subject to review by the Government. All telecommuting agreements must be authorized and approved by the COR and include date, time, and description of the work to be performed.

1.6.20.1.2. The contractor must identify to the COR any task/work requirements that may be performed at an alternate worksite. Telework will be at no additional cost to the Government. Upon approval:

1.6.20.1.3. The Government may provide as Government Furnished Equipment (GFE): Secure laptop with access to the required portals, networks, and business application. Internet connection will not be furnished, therefore, Internet access shall be provided by the Contractor.

1.6.20.1.4. Individual Contractor Personnel shall provide services from their authorized telework worksite location IAW Department of Defense Instructions (DoDI) 1035.01, Telework

Policy: http://www.dtic mil/whs/directives/corres/pdf/103501p

1.6.21. Warranty: The Contractor shall provide all post installation services, vendor service, maintenance, and licensing agreements, and equipment/tools necessary to maintain the installed system equipment and software in an operational state. The warranty period shall begin upon formal, written acceptance of the system by the Government. The warranty period shall last for one year, or for the length of the Original

Equipment Manufacturers (OEM) warranty, whichever is greater. At the conclusion of all warranty periods, the Contractor shall seamlessly transfer systems and components installed under the ISSC task orders into the existing preventative maintenance cycle and assume repair and sustainment responsibility.

PART 2

DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.6. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.8. QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.9. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.10. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.11. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.12. WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.12. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2. ACRONYMS:

ACC Access Control Center

ACS Access Control System

ACOR Alternate Contracting Officer Representative

AMAG American Magnetics

ANSI/EIA American National Standards Institute/ Electronic Industries Alliance

CFR Code of Federal Regulations

COTS Commercial off the Shelf

CO Contracting Office

KO Contracting Officer

COR Contracting Officer Representative

DHHQ Defense Health Headquarters

DoD Department of Defense

ESS Electronic Security System

GSA General Services Administration

GFE Government Furnished Equipment

GFI Government Furnished Information

IDIQ Indefinite Delivery Indefinite Quantity

ISSC Integrated Security Services Contract

NCR National Capital Region

OS Operating System

OGA Other Government Agencies

OGC Other Government Contractors

PFPA Pentagon Force Protection Agency

PWS Performance Work Statement

POP Period of Performance

QA Quality Assurance

QC Quality Control

RRMC Raven Rock Mountain Complex

SCI Secure Compartmentalized Information

SSD Security Services Directorate

TS Top Secret

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED PROPERTY (GFP) AND SERVICES:

3.1. SERVICES: The Government will provide project leads, for all installation projects. The Government will also provide available drawings for facilities and office spaces.

3.2. FACILITIES: The Government will provide limited office space. Office space will be limited to the access control center and network control center. The Government cannot guarantee office or storage space for technicians, key personnel or administrative personnel.

3.3. MATERIALS: The Government will provide the Standard Operating Procedures (SOP) for the Access

Control Center. If GFP is provided, the Government will notify the contractor at the task order level.

Contractor will provide all other materials for installation task orders as outlined in individual task orders.

3.4. PARKING: The Government shall provide the Contractor with limited parking at the Pentagon

Reservation, Mark Center, and Raven Rock Mountain Complex on a space available basis. There is no

Government provided parking at leased facilities. Parking is limited on the Pentagon reservation and restricted to only company labeled vehicles. The Contractor shall be fully responsible for procuring parking at all locations to perform work required under this Contract.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1. GENERAL: The Contractor shall furnish all supplies, equipment, facilities and services required to perform task orders under this contract that are not listed under Section 3 of this PWS.

4.2. TOP SECRET FACILITY CLEARANCE: The contractor shall possess and maintain a TOP SECRET facility clearance from the Defense Security Service. The DD 254 is provided as Attachment 13 with the solicitation. Specific security requirements will be identified at the task order level.

4.3. MATERIAL: The Contractor shall provide, maintain, and be fully accountable for all tools necessary to safely and effectively perform the services required in this contract. The contractor will also provide all necessary safety equipment (glasses, hearing and head and foot protection) for use onsite.

4.4. EQUIPMENT: The Contractor shall provide lifts, ladders and any equipment needed to perform the tasks described in this PWS. Some work is performed on roofs, light posts, in confined areas and other locations in multiple Government facilities.

4.5 UTILITIES: The Contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the water faucets or valves after using the required amount to accomplish cleaning vehicles and equipment.

PART 5

SPECIFIC TASKS

5. SPECIFIC TASKS:

5.1. BASIC SERVICES: The contractor shall provide services for this contract at the task order level. Each task order will have a PWS describing all the requirements for materials, installation, or support for security of the Pentagon or other PFPA supported facility.

The work to be performed on ISSC is divided into five major categories, which are:

a) System Support: The Contractor shall be responsible for sustainment support of electronic security systems. This support includes system monitoring, troubleshooting, patching and software updates, configuration, and administration.

b) Logistics: The Contractor shall be responsible for procuring, storing, and inventory of materials and supplies to deliver services under this contract.

c) Repair: The Contractor shall be responsible for responding to and repairing damaged, malfunctioning, or inoperable systems and their components as described in this PWS as well as any components installed during this contract unless specified in the individual task order PWS.

d) Maintenance: The Contractor shall be responsible for performing periodic preventative maintenance on all electronic and physical security systems identified in this Performance Work Statement (PWS) as well as any components installed during this contract unless specified in the individual task order PWS.

Periodic preventative maintenance shall be performed at minimum in accordance with manufacturer recommendations and may require additional preventative maintenance work due to amount of use or ambient conditions.

e) Installation and Hardware: The Contractor shall be responsible for the complete requirement analysis, system engineering, detailed design development, programming, configuration, integration, shipment, installation, and testing of systems as outlined in future TOs.

The Contractor shall provide a qualified team of installation professionals with the necessary experience to install equipment properly while having minimal effect on the day-to-day operations responsibilities outlined in preventative maintenance, repair, system support, and logistics sections of this PWS.

All engineers and technicians working on ISSC systems shall have certification and training from

OEM in their area of expertise. The Contractor shall provide best practices and adherence to applicable DoD regulation, industry standards, and local regulation on all installation efforts.

Deviation from applicable regulation should be noted in TO proposals.

Infrastructure installation should adhere to cabling standards ANSI-TIA-EIA 569-A, Unified

Facilities Criteria (UFC) 3-580-01, and the Department of Army ITA Telecommunications

Distribution Design Method SOP00385.

The contractor shall propose solutions in compliance with the Pentagon Exterior Standards

Manual (PESM). Deviation from PESM shall be approved in writing by Government.

Installation TO’s shall be designed and implemented in accordance with all applicable DoD regulations to include, but not limited to, the Office of the Director of National Intelligence, Intelligence Community Directives (ICD) 503, 705.1, DOD 5100.76M - Physical Security of

Sensitive Conventional Arms, Ammunition, and Explosives (AA&E), and ICD 705.2, Protecting

Sensitive Compartmented Information within Information Systems; DoD Manual, 5205.13, Defense Industrial Base (DIB) Cyber Security and Information Assurance (CS/IA) Program

Security Classification Manual; DoD Manual 5220.22M, National Industrial Security Program

Operating Manual (NISPOM); DoD Manual 5200.01, Information Security Program; and Office

Secretary of Defense Supplement to DoD 5200.1R.

Contractor shall provide a performance verification testing plan for each TO that addresses the performance characteristics identified in section 5.5. This plan shall include a burn-in period of no less than 30 calendar days to demonstrate system performance through operational testing and include a testing checklist for Contractor completion and government validation. Procedures shall explain in detail, step-by-step actions and expected results, demonstrating compliance with the requirements specified.

The Contractor shall complete installation of new systems or integrations between the existing systems and other ESS as part of individual TOs. The Contractor shall be responsible for the full lifecycle systems engineering process for these integrations, including requirements elicitation and analysis, detailed design, development, testing, integration, end user training, operationalization and go-live, and sustainment for all systems and sub-systems in this contract.

Task Orders will be noted and awarded as either a Capital Improvement or Non-Capital

Improvement:

o Capital Improvement (This is a subcategory of Installation for accounting purposes):

Capital improvements to general equipment must be noted and awarded as such when a task order performs the following: (1) the improvement increases the asset's useful life by two or more years, or increases the assets capability, or increases its capacity or size, and

(2) the cost of the improvement equals or exceeds the capitalization threshold ($250K).

o Non-Capital Improvement: These will be more common than the capital improvement projects. This includes projects or hardware that do not meet the capital improvement projects.

5.2. Task Order (TO) Management:

The Contractor shall manage all issued TO as outlined in contract requirements. The Installation

Manager shall serve as the focal point for all TOs and PoP Management.

The Contractor shall maintain comprehensive tracking tools to manage TO schedules and to identify Government or Contractor delays to the critical path in advance, along with recommendations/options to mitigate delay in overall project schedule. Examples of these delays include, but are not limited to, network or electrical infrastructure, permits, material procurement, or construction delays.

The Contractor shall provide appropriate staffing to address assigned task orders within the PoP defined on each TO. The Contractor shall identify when TOs may overlap, are duplicative, or conflicting and request clarification by the Government as part of proposal response.

The Contractor shall insure that all equipment, configurations, and as-built drawings for the installation are loaded in the MMS.

5.2. Proposal Response to TOs:

The Contractor shall provide a comprehensive proposal identifying the Contractor’s approach and solution.

o The Contractor shall identify how their proposal was shaped by specific Government’s

PWS items and the Contractor’s assumptions.

o The Contractor shall include detailed costs for prime and sub-contractor labor hours and categories, materials, other costs.

o The Contractor is encouraged to identify trade space that may provide quantifiable improvements in cost, schedule, or performance.

o Contractor will provide labor hours and what labor category responsibilities will be to complete the task order

The Contractor shall return proposals within the below response times.

o Routine Proposals: Returned within three (3) business days.

o Surge or Emergency Proposals: Returned within one (1) business day.

o Complex Proposals, such as those involving extensive amounts of integration, construction, multiple stakeholders, or new systems shall be returned within seven (7) business days.

o Deviations from outlined proposal response times should be requested in writing to

Government and are subject to approval.

Proposal responses shall include site survey data including sketches, photographs, survey sheets, and annotated site drawings. The responses shall include details about the current site conditions as well as conditions/considerations that may impact ability of proposed system performance or schedule for consideration by government.

For complex projects, joint scoping sessions may be requested.

5.4 Technical Design Packages: For complex system designs not yet developed, the Government may request as a TO, a Technical Design Package (TDP) that details complete system, design, installation approach, testing, and full lifecycle costs for installation and sustainment. Specific Technical Design

Package requirements will be defined on an individual TO basis.

PART 6

APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS (CURRENT EDITIONS)

6.1. The Contractor must abide by all applicable regulations, publications, manuals, and local policies and procedures. This includes but is not limited to ICD 705, DoD 52001.01 Volume 3, and DoD 5100.76.

PART 7

ATTACHMENT/TECHNICAL EXHIBIT LISTING

7. ATTACHMENT/TECHNICAL EXHIBIT LIST:

7.1 Technical Exhibit 1 – Performance Requirements Summary

7.2 Technical Exhibit 2 – Deliverable Schedule

TECHNICAL EXHIBIT 1

PERFORMANCE REQUIREMENTS SUMMARY

7.1 Performance Requirements Summary

Performance Requirements Summary will vary by task order and will be defined in specific task orders.

TECHNICAL EXHIBIT 2

DELIVERABLE SCHEDULE

7.2 Deliverable Schedule

Additional deliverables may be identified and defined in specific task orders.

All deliverables shall be submitted using Microsoft Office suite of tools (for example, MS Word, MS

Excel, MS PowerPoint), or Adobe PDF format, unless otherwise specified by the COR. Electronic submission shall be made via email, unless otherwise agreed to by the COR.

The COR has the right to reject or require correction of any deficiencies found in the deliverables. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection.

The following table specifies the deliverables for this requirement. The Contractor is expected to adhere to the due dates for reference item. However, schedules for reference items become dependent on a number of factors beyond the Contractor’s control including, but not limited to; force protection constraints, accessibility to Command locations, and availability of key stakeholders. The Contractor shall account for external schedule complications and will adjust staffing, billing and due dates of deliverables accordingly.

Delays in scheduling should not influence the labor hours required to complete a comprehensive strategic evaluation. Before any reimbursable expenses (i.e., travel costs) are incurred by the Contractor as a result of schedule delays shall be reimbursed by the government, provided all reimbursable expenses were previously approved and COR is notified of any increased costs due to external scheduling delays.

Para

Reference Deliverable Frequency # of Copies Medium/Format Submit To

Limitations on

Sub

Contracting

Reporting

Data

FAR Clause

52.219-14

(DEV)

Annually, NLT 5 business days following the

Contractors’ submission to

GSA’s Contract

Payment Module

(CPRM)

1 original

PDF KO & COR

Executive

Compensation

FAR Clause

52.204-10

Annually, NLT 5 business days following the

Contractor’s submission to the

FFATA Sub-Award

Reporting System

(FSRS)

1 original

PDF KO & COR