Attachment 1 - PWS Short Term Intergrated Security Systems Support.pdf

PDF 496 KB Posted

Attached to
Presolicitation Notice of Government's Intent to Sole Source/Sources Sought for Integrated Security System Support Services
Solicitation number
HT940827QE017
Issued by

About this file

This is a Performance Work Statement (PWS) for Integrated Security System Sustainment Support at Brooke Army Medical Center (BAMC), issued by the Defense Health Agency (DHA) under the Department of Defense.

The contractor shall provide continuous 24/7/365 sustainment, maintenance, technical support, and lifecycle services for BAMC's integrated security systems, including Electronic Security System (ESS) with approximately 3,500 proximity readers and 500 duress buttons; CCTV/Qognify video surveillance systems with fixed and PTZ cameras; NICE Vision Pro digital recorders; and HUGS Infant/Pediatric Protection System with tamper-detecting bands and monitoring stations. Work shall be performed at BAMC Hospital, Fort Sam Houston Clinic, and other designated facilities. The contractor must maintain 95% system operational availability (99.9% for HUGS), respond to emergency events within two hours with restoration within 24 hours, and respond to non-emergency events within 24 hours with restoration within 72 hours. The base period runs December 1–31, 2026, with one option period January 1–31, 2027. All contractor personnel must hold OEM certifications (CEM Access 2000, NICE Vision Pro/Qognify, HUGS), pass background investigations, and comply with DoD cybersecurity requirements including HIPAA and Personnel Security Program standards. Key deliverables include annual work plans, quarterly MEVA testing reports, monthly performance reports, system documentation, spare hard disk maintenance with current backups, and CEM user training (maximum 24 hours annually). The estimated workload includes eight positions at 1,912 hours each: System Engineer, Access Control Engineer I, System Administrator II, Senior Network Engineer II, Master Locksmith, Locksmith, and two Security Access CEMs.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

DHA PWS Template V13 November 16, 2021

Department of Defense

Defense Health Agency

Performance Work Statement

Integrated Security System Sustainment Support

Office of Security Branch

Solicitation Number:

Version: 1

Date: 02 November 2027

November 16, 2021

PART 1

1.0 GENERAL INFORMATION

1.1 This is a non-personal services contract to provide Integrated Security System Sustainment Support

1.2 Description of services/introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform Integrated Security System Sustainment Support as defined in this Performance Work Statement (PWS) except for those items specified as government furnished property and services. The contractor shall perform to the standards in this PWS.

1.3 Background: BAMC relies on an integrated security architecture to protect patients, staff, visitors, controlled areas, mission-essential assets, and pediatric populations. The ESS, CCTV/Qognify, NICE Vision Pro, and HUGS systems support life-safety, patient protection, and force protection missions. Continuous sustainment is required to ensure uninterrupted operation of access control, video surveillance, duress alarms, infant protection systems, and associated network components.

1.4 Objectives:

● Maintain full operational capability of all ESS, CCTV/Qognify, NICE Vision Pro, and

HUGS components.

● Provide 24/7/365 emergency and non-emergency support.

● Ensure OEM-certified technicians perform all work.

● Maintain system uptime no less than 95% of the time.

● Provide rapid response and restoration for critical alarms and failures.

● Maintain accurate system documentation, drawings, inventories, and reports.

● Ensure seamless integration between ESS, CCTV, and HUGS systems.

● Support BAMC's mission-critical security and patient-safety requirements.

1.5 Scope: The contractor shall provide continuous sustainment, maintenance, technical support, lifecycle services, and subject matter expertise for BAMC's Integrated Security System, consisting of: Services include

• Electronic Security System (ESS)

• CEM Access 2000 and Lenel access control systems

• CCTV/Qognify video systems

• NICE Vision Pro digital recorders

• HUGS Infant/Pediatric Protection System

November 16, 2021

• Associated servers, workstations, network infrastructure, and field devices

The contractor shall maintain all systems at 95% operational availability, excluding scheduled maintenance and Government-directed outages. All contractor personnel shall be trained, experienced, and certified on the systems they service.

1.6 Period of Performance (PoP): The Government is ordering services for a base period of 1-month, and one (1) one-month option period as detailed below.

1.7 Administrative specifications

1.7.1 Place of performance: The work shall be performed at the following locations:

• Brooke Army Medical Center (BAMC)

• Fort Sam Houston Clinic

• BAMC outlying facilities

• Government designated secure areas for spares.

1.7.2 Recognized Federal holidays: The Contractor is not required to perform routine services on federally recognized holidays. However, the Contractor remains fully responsible for responding to and performing all emergency or urgent contractor service calls that occur on these holidays, in accordance with the response times established within this PWS.

New Year’s Day Labor Day

Martin Luther King Jr.’s Birthday Columbus Day

President’s Day Veteran’s Day Memorial Day Thanksgiving Day

Juneteenth Day Christmas Day

Independence Day

1.7.3 Hours of operation: The contractor is responsible for conducting business Monday thru

Friday, 0730 – 1630, with a one-hour uncompensated lunch break, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The contractor must 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.

1.7.4 Emergency Services: Emergency support may be required outside normal duty hours. The contractor shall respond onsite within two (2) hours for all emergency events. Emergency support is required 24/7/365.

Period Period of Performance

Base Period 1 December 2026 – 31 December 2026

Option Period 1 1 January 2027 – 31 January 2027

November 16, 2021

1.8 Other Direct Costs (ODC): ODCs may include Travel, OEM training, OEM support fees, specialized diagnostic tools, License Subscriptions, Spectrum Accounts, and replacement parts not covered under standard CLINs. All ODCs require prior Contracting Officer Representative

(COR) and Contracting Officer (CO) approval.

1.9 Contractor travel: Contractor Personnel may be required to travel within CONUS for

OEM training, manufacturer support coordination, specialized certification courses and

Government-directed meetings. All travel requires Government approval and notification to the

Contracting Officer’s Representative (COR) and Contracting Officer.

Contractor shall be authorized travel expenses consistent with the cost principles and procedures in Federal Acquisition Regulation (FAR) Part 31.2, Travel Costs and the limitations of funds specified in this contract.

1.10 Quality

1.10.1 Quality Control (QC): The contractor shall develop and maintain an effective QC program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure nonrecurrence of defective services. The contractor’s QC program is the means by which the work complies with stated requirements. A comprehensive written Quality Control Plan (QCP0 shall be submitted to the CO and COR within 30 days after contract award. The contractor shall receive the CO’s written acceptance of any proposed change to the QC system. After acceptance of the Quality Control Plan (QCP) the contractor shall receive the CO’s acceptance in writing of any proposed change to his QC system. See Part 7, Technical Exhibit 1 - CDRL A001.

1.10.2 Quality assurance (QA): The government will evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan provides a systematic method for the Government to evaluate performance and to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.11 Contractor personnel

1.11.1 CAC requirements: For all contractors who will work in Government facilities, the

Facilities Security Officer (FSO)/Company's Security point of contact (POC) will provide the

Government all the required information per the DHA CAC request process current version 2.1, January 2018, or more recent when updated. See process attached at Part 7 Section 7.1.1 of the

PWS. A CAC is the standard identification for eligible DoD contractor personnel.

1.11.1.1 The contractor shall return all CACs to the COR upon the departure of the contractor(s).

1.11.2 Contractor onboarding and training. The contractor shall complete all requirements, training, and forms as prescribed in the following requirements:

November 16, 2021

1.11.2.1 The DHA’s “Onboarding Checklist for Contractor Employees” is located at the DHA

Onboarding and Offboarding Portal at https://info.health.mil/cos/admin/hr/IO/SitePages/Home.aspx

1.11.2.2 The DHA’s contractor training instructions embedded at Part 7 Section 7.1.2.

1.11.2.3 The contractor shall comply with onboarding requirements of the DHA for contractors needing to be issued CAC identification, including DoD- and DHA-directed training and forms submission, prior to network access, as displayed in the In/Out-Processing Portal at:

https://info.health.mil/cos/admin/hr/IO/SitePages/home.aspx (note: Public Key Infrastructure

(PKI)-restricted, printed versions available).

1.11.2.4 Removed.

1.11.3 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.11.4 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 CO.

1.11.4.1 In the event keys, other than master keys, are lost or duplicated, the contractor shall, upon direction of the CO, 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.11.4.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 CO.

1.11.5 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.12 Key personnel (Contractor): The contractor shall provide a contract manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the CO.

The contract manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The contract manager or alternate shall be available between 0730-1630 Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons.

1.13 Removed

1.14 Reporting

1.14.1 Contractor Manpower Reporting (CMR): RESERVED.

1.14.2 Non-Disclosure Agreement (NDA): All contractor personnel who will obtain access to proprietary, classified, or confidential information or any information release of which is protected or governed by law or regulation associated with DHA acquisitions shall be required to complete and sign a DHA contractor NDA (DHA Form 49) prior to beginning work on the subject contract. The contractor shall execute an NDA on behalf of the company and shall ensure that all staff assigned to, including all subcontractors and consultants, or other personnel performing on contract/Task order execute an NDA protecting the procurement sensitive information of the Government and the proprietary information of other contractors. The NDA shall be executed not later than first day of employment and to be renewed upon exercising a contract option period. Assignment of staff who has not executed this statement or failure to adhere to this statement shall constitute default on the part of the contractor. The contractor shall maintain originally signed NDAs of individual employees and provide copy to the COR.

1.14.3 Government’s COR: The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor contractor's performance and notifies both the CO and contractor of any deficiencies; coordinate availability of government furnished property; and provide site entry of contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract.

1.14.4 Post award conference/periodic progress meetings: The contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with FAR Subpart 42.5. The CO, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance.

At these meetings the CO will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.15 Contractor Identification

1.15.1 Contractor personnel performing services in a contractor capacity in a Government facility are required to possess and wear an identification badge that displays his or her name and the name of their company. All contractor personnel shall identify themselves as contractor support personnel in all forms of communication with all entities with whom DHA/Deputy

Assistant Director for Acquisition (DAD-A)/Head of the Contracting Activity (HCA) has business dealings. The contractor shall: Answer all telephone calls and have a personalized voice message with an introductory statement that includes the fact that the person is contractor support personnel. Ensure all those with whom the person interacts in any face-to-face dealings while supporting the DAD-A understands that the person is contractor support personnel.

Include a title block in all emails that states the fact that the person is contractor support personnel. Ensure all those with whom the person interacts in any face-to-face dealings while supporting DHA/DAD-A/HCA understands that the person is contractor support personnel.

1.15.2 Contractor personnel will be required to attend meetings or otherwise communicate with

Government and/or other contract representatives to meet the requirements of this order.

Contractor personnel shall make their contractor status known during introductions.

1.15.3 Contractor personnel, while performing in a contractor capacity, are prohibited from using their retired or reserve component military rank or title in any written or verbal communications associated with the contracts in which they provide services.

1.16 Contractor Access to Health Affairs (HA)/DHA Network(s)

1.16.1 FSO/Company's Security POC shall notify the DHA Personnel Security Office after being awarded a contract that requires access to a DoD system (If applicable, if not delete 1.16.1 and 1.16.2 and replace to 1.16 Reserved). Contractor personnel requiring access to the HA/DHA networks for performance of their tasks require a background investigation and the security awareness training. The contractor shall be prepared for this process as it could take two (2) or more weeks. The FSO/Security POC shall submit a Standard Form (SF) 85/86 to DHA's

Personnel Security Office for a background investigation.

1.16.2 Company's FSO/Security POC must notify the Personnel Security Office when the contractor has submitted the SF-85/86. The FSO/Security POC, or the COR must notify the

DHA Personnel Security Office in writing of a contractor's termination from the contract, including the termination date.

1.17 Personnel Security

1.17.1 The contractor shall comply with DoD 8570.01-M, “Information Assurance Workforce

Improvement Program, CH4” November 10, 2015 as amended; 8500.01, “Cybersecurity”, dated

March 14, 2014; DoD Manual (DoDM) 6025.18, “Implementation of the Health Insurance

Portability and Accountability Act (HIPAA) Privacy Rule Compliance in DoD Health Care

Programs” dated March 3, 2019, Department of Defense Instruction (DoDI) 6025.18 “HIPAA

Privacy Rule Compliance in DoD Health Care Programs”, dated March 13, 2019; and DoDM

5200.02 “Procedures for the DoD Personnel Security Program (PSP),” incorporation change 3, effective September 24, 2020. Contractor responsibilities for ensuring personnel security include, but are not limited to, meeting the following requirements:

1.17.1.1 Follow the DHA Personnel Security Office guidelines for submittal of security clearances. Contact the DHA Personnel Security Office for guidance on the appropriate background investigation required for personnel on the contract. The DHA Personnel Security

Office can be reached at (703) 275-6038.

1.17.1.2 Initiate, maintain, and document personnel security investigations appropriate to the individual’s responsibilities and required access to Controlled Unclassified Information (CUI).

1.17.1.3 DHA Personnel Security Office does not deny any access to any automated information system (AIS), network, or Controlled Unclassified Information (CUI). If a contractor receives an unfavorable background investigation, the request for access will be sent back to the FSO for further action. Any unfavorable adjudication will result in DHA Personnel Security Office not signing off on any access request.

PART 2

2.0 DEFINITIONS, ACRONYMS, AND APPLICABLE

PUBLICATIONS/INSTRUCTIONS

2.1 Definitions:

2.1.1 Category D: Information Technology (IT) and Telecommunications Services (called D-

Services)

2.1.2 Category R: Support (Professional/Administrative/Management) Services (called R-

Services)

2.1.3 Contracting Officer (CO): A person with the authority to enter into, administer, and/or terminate contracts and make related determinations and findings.

2.1.4 Contracting Officer’s Representative (COR): An individual, including a contracting officer’s technical representative (COTR), designated and authorized in writing by the CO to perform specific technical or administrative functions. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.5 Nonpersonal services contract: a contract under which the personnel rendering the services are not subject, either by the contract’s terms or by the manner of its administration, to the supervision and control usually prevailing in relationships between the Government and its employees.

2.1.6 Quality Assurance Surveillance Plan (QASP): An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance. The

Government may either prepare the QASP or require the offerors to submit a proposed quality assurance surveillance plan for the Government’s consideration in development of the

Government’s plan.

2.2 Acronyms:

AAMI - Association for the Advancement of Medical Instrumentation

AEM - Alternate Equipment Maintenance

AIS -- Automated Information System

ANSI - American National Standards Institute

APL -- Approved Products List APL

AQL -- Acceptable Quality Level

ARRT -- Acquisition Requirements Roadmap Tool

ATO -- Authority to Operate

B2B -- Business-2-Business

BAA - Business Associate Agreement

BAMC - Brooke Army Medical Center

BLS - Basic Life Support

CAC -- Common Access Card

CAP -- Cloud Access Point

CBET - Certified Biomedical Equipment Technician

CBMH - Community Based Medical Home

CCEVS -- Common Criteria Cybersecurity Evaluation and Validation Scheme

CDI -- Covered Defense Information

CE -- Computer Environment

CDRL -- Contract Data Requirement List

CIO -- Chief Information Officer

CJCSM -- Chairman of the Joint Chiefs of Staff Manual

CM - Corrective Maintenance

CMMC -- Cybersecurity Maturity Model Certification

CMMS - Computerized Maintenance Management System

CMR -- Contractor Manpower Reporting

CNSSI -- Committee on National Security Systems Instruction

CO -- Contracting Officer(s)

CONUS -- Continental United States (excludes Alaska and Hawaii)

COR -- Contracting Officer Representative

COTR -- Contracting Officer's Technical Representative

CSP - Cloud Service Provider

CSSP -- Cyber Security Service Provider

CUI -- Controlled Unclassified Information

DAD-A -- Deputy Assistant Director for Acquisition

DC3 -- DoD Cyber Crime Center

DD Form 254 -- Department of Defense Contract Security Requirement List

DB -- Design-Build

DBB -- Design-Bid-Build

DFARS -- Defense Federal Acquisition Regulation Supplement

DHA -- Defense Health Agency

DISA -- Defense Information System Agency

DoD -- Department of Defense

DoDD -- Department of Defense Directive

DoDI -- Department of Defense Instruction

DSAs -- Data Sharing Agreements

DSAA -- Data Sharing Agreement Application

DMZ -- Demilitarized Zone

DoDM -- Department of Defense Manual

DPCLO -- DHA Privacy and Civil Liberties Office

DUA -- Data Use Agreement

ECN – Equipment Control number

EVS - Environmental Services eMSM -- Enhanced Multi-Service Markets

EULA -- End User License Agreement

EVM -- Earned Value Management

FAR -- Federal Acquisition Regulation

FCI -- Federal contract information

FE -- Facilities Enterprise

FedRAMP -- Federal Risk Authorization and Management Program

FHP – Force Health Protection

FISMA -- Federal Information Security Modernization Act

FRCS -- Facility Related Control Systems

FSO -- Facilities Security Officer

FSR - Field Service Report

HA -- Health Affairs

HIPAA -- Health Insurance Portability and Accountability Act

HCA -- Head of the Contracting Activity

HIT -- Health Information Technology

HTM\S – Healthcare Technology Management Services

IGCE -- Independent Government Cost Estimate

IA -- Information Assurance

IO -- Initial Outfitting

IoT - Internet of Things

I/O -- In/Out Processing Portal

IPv -- Internet Protocol Version

IS -- Information System

ISP -- Internet Service Provider

IT -- Information Technology

ISCM -- Information Security Continuous Monitoring

IV&V -- Independent Verification & Validation

MedCOI -- Medical Community of Interest

MHS -- Military Health System

MIL-STD -- Military Standard

MTFs -- Military Treatment Facilities

NCR -- National Capitol Region

NDA -- Non-Disclosure Agreement

NFPA - National Fire Protection Association

NIAP -- National Information Assurance Partnership

NIST - National Institute of Standards and Technology

OCONUS -- Outside Continental United States (includes Alaska and Hawaii)

ODC -- Other Direct Costs

OEH – Occupational and Environmental Health

OEM - Original Equipment Manufacturer

OPM - Office of Personal Management

OS - Operating System

OSD -- Office of the Secretary of Defense

P-ATO Personal Authorization to Operate

P&R Personnel and Readiness

PGI Procedures, Guidance and Information

PDT Project Delivery Team

PHI Protected Health Information

PII Personally Identifiable Information

PIT Platform Information Technology

PK Public Key

PKI Public Key Infrastructure

PM - Preventive Maintenance

POA&M Plan of Action and Milestones

POC Point of Contact

PMO Program Management Office

PoP Period of Performance

PP Personal Property

PPSM Ports, Protocols, and Services Management

PRS Performance Requirements Summary

PSP Personnel Security Program

PWS Performance Work Statement

QA Quality Assurance

QAP Quality Assurance Program

QASP Quality Assurance Surveillance Plan

QC Quality Control

QCP Quality Control Plan

RFP Request for Proposal

RFQ Request for Quotation

RCA - Root Cause Analysis

RMF Risk Management Framework

SP Special Publication

SPRS Supplier Performance Risk System

SRM Sustainment, Restoration and Modernization

SRG Security Requirements Guides

STIG Security Technical Implementation Guides

TB – Technical Bulletin

TMDE - Test, Measurement, and Diagnostic Equipment

TOS Terms of Service

UDI - Unique Device Identifier

US United States

UFC Unified Facilities Criteria

VPN Virtual Private Network

XML Extensible Markup Language

2.3 Applicable Publications, DHA Administrative Instructions (AI), etc.

• CMS S&C 14-07: Hospital Equipment Maintenance Requirements

• American National Standards Institute (ANSI) / Association for the Advancement of Medical

Instrumentation (AAMI) EQ56: Recommended Practice for a Medical Equipment Management Program

• DHA AI 6430.11, “Healthcare Technology Management Biomedical Equipment Program,” 14 October

• DoD 8510.01, “Risk Management Framework for DoD Information Technology,”12 May 2014

• DoDD 6200.04 Force Health Protection (FHP)

• DoD Financial Management Regulation (FMR) 7000.14-R, Volume 12, Chapter 7, "Financial Liability for

Government Property Lost, Damaged, Destroyed, or Stolen.

• DoD Manual 5200.08, Volume 3, "Physical Security Program: Protection of DoD Assets

• DoDI 4140.01, "DoD Supply Chain Materiel Management Policy

• DoDI 4151.18, "Maintenance of Military Materiel

• DoDI 5101.15, DoD Medical Materiel Management

• DoDI 6055.01 & 6055.05 Safety and Occupational Health (SOH) / Occupational and Environmental Health

(OEH)

• DoDI 6200.03, Public Health Emergency Management Within the Department of Defense

• DoDI 6430.02, Defense Medical Logistics Program.

• DoDI 6490.03, Deployment Health

• National Fire Protection Association (NFPA) 99, “Health Care Facilities Code,” 2021 Edition

• SB 8-75-11, “Army Medical Department Supply Information,” 20 November 2018

• Technical Bulletin (TB) 38-750-2, “Maintenance Management Procedures for Medical Equipment,” 12 June

• TB 43-180, “Calibration and Repair Requirements for the Maintenance of Army Materiel,” 1 May 2022

• TB Medical (MED) 750-1, “Operating Guide for Medical Equipment Maintenance,” 1 June 1998

PART 3

3.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

The Requiring Activity Authority has assessed the need for Government Furnished Property, Equipment, and Services and determined:

3.1 Equipment: The Government: WILL provide Equipment in support of this contract/task orders. The

Government provided Equipment is described below:

• ESS Servers

• CCTV/Qognify Servers

• NICE Vision Pro Recorder Servers

• HUGS Servers and Monitoring Stations

• ESS/CCTV/HUGS Workstations

• Network Switches and Associated Network Infrastructure

The Government will provide telephones, facsimile machines, copiers and computer equipment to include laptops for use in performance under this contract/task order. This equipment is authorized for transaction of official Government business only and shall not be used for personal business. Personal long distance calls are not authorized and the cost of all personal long distance calls made by contractor or subcontractor employees may be deducted from the contractor/s invoice payments. Telephones, facsimile machines and computer equipment to include laptops are subject to communications security monitoring at all times. Contractor and subcontract employees may be issued keys signed for at scheduled and unscheduled key control inspections. The contractor shall be required to reimburse the Government for lost keys, or lockset (if lockset is required to be replaced) as a result of lost keys. The cost of replacement of keys/locksets may be deducted from payments to the contractor. Items issued will remain the property of the Government and the contractor will maintain proper accountability of issued equipment. Equipment shall not be removed from the facilities shown in paragraph 3.2 above, unless otherwise specified in the PWS. They are to be used, turned in and/or disposed of as directed by the COR or CO.

3.2 Materials: The Government:

Will provide Materials in support of this contract/task order. The government shall furnish all materials required for installation, repair, and maintenance, including: cabling, connectors, and termination hardware; mounting hardware for cameras and access control devices; replacement part.

3.3 The Government will provide the following at no cost to the contractor:

● Existing ESS, CCTV, NICE Vision Pro, and HUGS system components and infrastructure

● Existing cabling, infrastructure, and installed hardware

● Existing system documentation, drawings, and configuration baselines

● Temporary identification allowing contractor personnel access to sites

● Vehicular permits allowing contractor vehicles onto the installation

● Access to all areas and spaces where components are located; access will be provided by signing out

Grand Master Key from the BAMC Provost Marshal's Office. The contractor assumes all costs associated with replacement of the key if lost or not returned.

● A copy of technical drawings and system manuals, as available

● Facility access and security badges

● Network access and account provisioning

● Coordination with BAMC security, clinical, and IT personnel

● Escort services when required for restricted areas

PART 4

4.0 CONTRACTOR FURNISHED ITEMS AND SERVICES

4.1 N/A

PART 5

5.0 SPECIFIC TASKS

5.1 General. The contractor shall provide full sustainment, maintenance, lifecycle support, testing, reporting, and OEM coordination for BAMC's Integrated Security System. All tasks are mandatory and shall be performed in accordance with OEM specifications, DHA cybersecurity requirements, BAMC security policies, and the performance standards defined in this PWS. The contractor shall maintain a locally based workforce trained and experienced on all hardware and software listed in this PWS.

5.2 Electronic Security System (ESS) Support

5.2.1 - System Coverage. The contractor shall provide continuous sustainment and support for all ESS components, including:

● Proximity card readers

● Electronic locks, magnetic locks, and strikes

● Request-to-Exit (REX) devices

● Door position switches

● Duress/panic buttons

● Reader interface modules

● Real-Time Computers (RTCs)

● Network Control Nodes (NCNs)

● CEM Field Processors

● ESS servers and workstations

● Cabling, connectors, and termination hardware

● All associated network elements

5.2.2 - Supported Facilities. The contractor shall support ESS operations at:

● BAMC Hospital

● Co-To

● Consolidated Parking Structure

● ISR/BHT

● Central Energy Plants 1 and 2

● Fort Sam Houston Clinic

● Troop billets

● Fisher Houses 1–4

● Center for the Intrepid

● Other Government-designated buildings

5.2.3 System Description. The contractor shall maintain an independent ESS network with:

● Approximately 3,500 proximity readers and control devices

● A graphical monitoring map with approximately 800 secure points

● Approximately 500 duress buttons

● CEM Access 2000 operated on Fedora Core 10 Linux servers

● Windows workstations accessing CEM Access 2000

5.2.4 Software Requirements. Technicians supporting CEM Access 2000 shall have a minimum of one (1) year experience supporting similarly sized systems and be capable of interfacing

CCTV/Qognify AMS Server with CEM Access 2000 to enable video switch salvos, tours, and preset video shots triggered by alarm strings. Technicians shall have experience with Fedora

Core 10 on Linux servers and Windows Professional/Windows Server workstations, and experience using PcAnywhere and Crystal Reports.

5.2.5 - Upgrades and Support. The contractor shall provide OEM-recommended support, updates, and upgrades for: CEM Access 2000; Lenel components; Windows Professional workstations; Windows Server; Crystal Reports; and Fedora Core 10 Linux systems.

5.2.6 - Hardware Experience. Hardware technicians shall have a minimum of one (1) year experience maintaining Intel-based PC workstations and servers with RAID arrays, monitors, printers, and modems.

5.2.7 Logistics. The contractor shall provide or lease vehicles for technicians and locksmiths to transport tools and parts for offsite maintenance. Contractor personnel must be able to drive Government vehicles when required.

5.3 CCTV / Qognify Support

5.3.1 - System Coverage. The contractor shall sustain and maintain all CCTV/Qognify components, including: fixed and PTZ cameras; encoders and decoders; video switches; NICE

Vision Pro recorders; CCTV servers and CPUs located in room L43-13 and at remote sites;

camera housing, mounts, and lenses; and associated cabling and network components.

5.3.2 - Transmission Links. The contractor shall maintain wired and wireless video transmission links supporting: BAMC main gate; Binz-Engleman gate; Fort Sam Houston Clinic; and other outlying locations.

5.3.3 - Integration with ESS. The contractor shall maintain and program the interface between

CEM Access 2000 and the CCTV video switch/CPU to enable salvos, tours, preset video shots, and alarm-triggered video responses driven by alarm strings from the CEM Access 2000 server.

5.3.4 - The contractor shall maintain personnel with demonstrated technical proficiency in CEM

Access 2000, including configuration management, database recovery, RTC/NCN troubleshooting, alarm processing, and integration with existing CCTV/Qognify and NICE

Vision Pro components.

5.3.5 - Personnel responsible for system-level troubleshooting shall demonstrate the ability to diagnose and restore existing system interfaces without disrupting unrelated access control, surveillance, or patient protection functions.

5.3.6 - Certification Requirement. Contractor and subcontractor personnel performing configuration, administration, troubleshooting, repair, software updates, upgrades, migration, or integration of the NICE Vision Pro/Qognify video management system shall hold OEM-issued certifications applicable to the installed platform and their assigned duties. Certifications shall be current where the OEM maintains a renewal program.

For legacy platforms where certification or renewal is no longer offered, the contractor shall provide written confirmation from Qognify/Octave that the individual’s existing credentials and qualifications remain acceptable for the assigned work. Octave certifications may be accepted only upon written confirmation from Qognify/Octave of their applicability to the installed system or the approved Qognify/Octave target VMS.

Personnel supporting CCTV/Qognify systems shall additionally hold current CEM Access 2000

OEM certification, or written CEM OEM confirmation of acceptable legacy qualifications.

Personnel performing video platform upgrades or migrations shall possess Qognify/Octave-recognized qualifications applicable to the approved Qognify/Octave target VMS and scope of work.

All video platform upgrades, migrations, and replacements shall comply with the PWS restriction limiting the VMS to Qognify or Octave products. Certifications or qualifications issued by another VMS manufacturer shall not satisfy the video platform qualification requirements or authorize substitution of another manufacturer’s VMS.

General CCTV training and company reseller status alone shall not satisfy these personnel qualification requirements. Qualified personnel shall be available by contract commencement and throughout performance. These requirements apply equally to prime contractor, subcontractor, temporary, and replacement personnel.

5.3.7 - The contractor shall demonstrate the capability to troubleshoot, maintain, and validate operational interfaces among CEM Access 2000, CCTV/Qognify, NICE Vision Pro, and HUGS systems.

5.3.8 - Integrated testing shall verify alarm initiation, event transmission, video activation, monitoring station notification, and authorized access control responses.

5.3.9 - Following maintenance or modification of an integrated component, the contractor shall validate that all affected interfaces remain operational.

5.4 HUGS Infant / Pediatric Protection System Support

5.4.1 - System Coverage. The contractor shall sustain and maintain all HUGS components, including: tamper-detecting infant/pediatric bands; HUGS tags; exciters and band sensors;

monitoring stations; HUGS servers and network components; and associated cabling and hardware.

5.4.2 - System Description. The contractor shall ensure HUGS provides tamper detection; infant-to-parent matching; movement monitoring; exit approach detection; and alarm activation for band removal, tampering, or restricted exit proximity.

5.4.3 - Integration. The contractor shall ensure seamless integration of HUGS with ESS and

CCTV/Qognify systems to support coordinated alarm responses, video verification, and access control actions.

Maintenance and Upgrades. The contractor shall provide OEM-recommended software updates, firmware updates, hardware upgrades, and replacement tags and bands.

5.4.4 - Testing and Reporting. The contractor shall incorporate HUGS devices into quarterly

MEVA testing and include tests of: band removal alarms; band tamper alarms; exit approach alarms; tag mismatch alarms; tag low battery alerts; and monitoring station failover tests.

5.4.5 - Training. Technicians shall be trained and certified in HUGS operation, maintenance, and troubleshooting. Certification documentation shall be submitted to the COR.

5.4.6 - Performance Requirement. Maintain HUGS operational availability at 99.9% uptime, excluding scheduled maintenance and Government-directed outages.

5.5 Program Management and Personnel

5.5.1 - Project Manager. The contractor shall designate a Project Manager for the contract duration as the principal point of contact. The Project Manager may be a working supervisor.

Minimum qualifications include: minimum five (5) years of specialized Department of Defense project experience managing related Government projects; supervisory experience; and strong written and oral communication skills. The Project Manager shall supervise contractor personnel, allocate resources, establish and monitor milestones and schedules, and coordinate with Government representatives. The Project Manager shall be available during normal

Government duty hours and able to meet with Government personnel within eight (8) hours when requested.

5.5.2 - The contractor shall demonstrate the technical capability and organizational experience necessary to sustain integrated electronic security systems in continuously operating medical facilities, including experience supporting access control, video surveillance, emergency notification, and patient protection systems.

5.5.3 - The contractor shall provide evidence of successfully performing comparable services involving mission-critical systems, multiple integrated technologies, and continuous operational availability. Comparable experience may be demonstrated through prime contractor, subcontractor, or qualifying team-member performance.

The contractor shall demonstrate successful performance sustaining NICE Vision Pro/Qognify video management systems in environments comparable to BAMC in system complexity, integration requirements, and operational criticality. Relevant experience shall include system administration, troubleshooting, recording and storage management, backup and recovery, and maintenance or validation of interfaces with access control or other security systems.

Where the scope includes video platform upgrades or migration, the contractor shall also demonstrate successful experience upgrading NICE Vision Pro/Qognify systems or migrating those systems to a Qognify or Octave VMS through a migration path supported by

Qognify/Octave. Experience migrating to or installing another manufacturer’s VMS shall not satisfy this platform-specific upgrade or migration requirement.

Qualifying experience may be demonstrated through the prime contractor, proposed subcontractor, or qualifying team member. The entity whose experience is relied upon shall be identified and committed to performing the corresponding video platform scope. General CCTV installation experience alone shall not satisfy this requirement.

5.5.4 - Technician Qualifications. Technicians shall be trained, experienced, and OEM-certified for CEM, NICE/Qognify, and HUGS systems; capable of meeting emergency response requirements; able to work in clinical environments including NICU and Pediatrics; and able to drive Government vehicles. The Government reserves the right to request a resume for any employee at any time during contract performance. Any employee who does not meet minimum requirements shall be replaced with a properly qualified individual.

Personnel assigned to NICE Vision Pro/Qognify or Octave VMS work shall meet Section 5.3.6 and demonstrate qualifications applicable to their assigned platform and duties. The contractor shall maintain sufficient qualified personnel to meet scheduled maintenance and emergency response requirements. Replacement personnel shall satisfy the same qualification and verification requirements before assuming technical duties.

5.5.5 - The contractor shall establish operational readiness by the contract start date, including qualified personnel, required system access, emergency response procedures, diagnostic equipment, and established manufacturer support arrangements.

5.5.6 - The contractor shall submit an Initial Operational Readiness Plan identifying assigned personnel, qualifications, manufacturer support arrangements, escalation procedures, and contingency staffing.

5.5.7 - The contractor shall demonstrate its ability to maintain required service levels during transition without interruption to mission-essential security functions.

5.5.8 - Staffing Continuity. The contractor shall maintain sufficient staffing to meet all scheduled maintenance and unscheduled response requirements at all times.

5.6 - Service, Materials, and Spares

5.6.1 - Service Requirements.

The contractor shall provide all service labor to repair or replace parts required to maintain systems at full performance. Software technical support and software upgrades shall be provided at no additional cost to the Government. When a covered VMS software upgrade requires replacement or expansion of existing hardware to meet documented OEM support and compatibility requirements, the Contractor shall identify those prerequisites before implementation. Required servers, storage, operating systems, and supporting infrastructure shall be itemized separately from covered software upgrade services and submitted for Government review and authorization under Section 5.6.2. Software upgrades shall not be deployed on infrastructure that fails to meet the applicable OEM requirements.

5.6.2 - Materials and Billing.

Materials for repairs, replacements, upgrades, shipping, and transportation shall be billed separately under repair and replacement contract line items. Security hardware, CCTV equipment, HUGS tags and bands, lock supplies, and failed computer hardware and software shall be billed as specified in the contract. There shall be no additional charges to the

Government for transportation or shipment of parts or components provided for repairs, or for disposal of parts replaced during service, unless otherwise specified in the contract.

Hardware eligible for separately authorized procurement under the applicable repair, replacement, or modernization CLINs shall include VMS recording and management servers, storage systems, and supporting infrastructure necessary to replace equipment documented as end-of-life, end-of-support, or incompatible with the approved VMS software version. Before procurement, the Contractor shall submit an OEM-supported technical justification, an itemized bill of materials, pricing, and an implementation plan. Procurement shall proceed only upon written authorization by the Contracting Officer and identification of the applicable funded

CLIN.

5.6.3 - Spare Hard Disk. The contractor shall maintain a spare hard disk loaded with current software, current configuration files, and current database backups for backup and restoration of automated systems. The spare hard disk shall be stored in the Provost Marshal's safe. The spare hard disk shall be updated within 30 calendar days of any system upgrade.

5.6.4 - System Drawings. The contractor shall maintain and update system drawings and topology diagrams after all additions, deletions, or changes. Updated system drawings shall be provided to the COR quarterly or as otherwise requested. The contractor shall update all documentation within five (5) business days of any system change.

5.7 - Inspections, Testing, and Reporting

5.7.1 - Scheduled Inspections. The contractor shall perform all OEM-recommended periodic services, inspections, and tests to ensure full system capability. All procedures, findings, and corrective actions shall be documented.

5.7.2 - Annual Work Plan. The contractor shall submit an initial annual work plan to the COR for approval that details scheduled testing of alarm points, controlled access points, communication devices, HUGS devices, and other operating components. The work plan shall include test frequency, test procedures, responsible personnel, and reporting timelines.

5.7.3 - Quarterly MEVA Testing. The contractor shall conduct and document quarterly tests of all Mission Essential Vulnerability Areas (MEVA). MEVA devices include but are not limited to: electronic sensors; panic/duress buttons; batteries; uninterruptible power supplies (UPS); card readers; magnetic locks; electric door strikes; reader modules; network communication nodes;

Real-Time Computers (RTCs); Network Control Nodes (NCNs); and all HUGS-specific devices.

5.7.4 - MEVA Locations. The contractor shall test MEVA devices in: pharmacies; cash handling facilities; morgue; radioactive material storage; sensitive materials storage; locations housing highly valued equipment; and all designated pediatric care areas where HUGS is deployed. The

Government may request additional MEVA locations. If additional locations are excessive, the contractor may request a contract modification.

5.7.5 - HUGS Alarm Scenarios. The contractor shall include explicit HUGS alarm scenarios in all test plans and reports, including:

● Band Removal Alarm: Tag removal or band tampering triggers immediate local alarm, notifies the monitoring station, and initiates a CCTV camera preset to verify the event.

● Exit Approach Alarm: Tag movement toward a restricted exit triggers a pre-alarm notification and, if continued, a full alarm with door lockdown and CCTV recording.

● Tag Mismatch Alarm: Incorrect infant-to-parent matching triggers an alert at the monitoring station and locks affected egress points until verified.

● Tag Low Battery Alarm: Low battery on a tag generates a maintenance alert and is recorded in the corrective action log.

● Monitoring Station Failure: Loss of HUGS monitoring station connectivity triggers failover procedures and immediate notification to contractor and Government personnel.

5.7.6 - Reports. The contractor shall deliver quarterly and annual test reports that include: test procedures; pass/fail results for each MEVA device; HUGS alarm scenario results and timelines;

corrective actions taken; parts replaced with serial numbers; root cause analysis for repeated alarms; video verification references; and recommendations for system improvements.

5.8 Response Times and Unscheduled Service

5.8.1 - Availability. The contractor shall provide unlimited on-site service and telephone consultation 24 hours per day, 7 days per week, 365 days per year.

5.8.2 Emergency Response. The contractor shall respond onsite within two (2) hours and restore to manufacturer's specifications within twenty-four (24) hours where applicable.

Emergency examples include: MEVA failures; server failure; badging system failure;

workstation failure; RTC failure; NCN failure; fire-rated door problems; perimeter door problems; CCTV system failures; and HUGS band removal or exit approach alarms indicating immediate risk to patient safety.

5.8.3 Non-Emergency Response. The contractor shall respond onsite within twenty-four

(24) hours and restore to manufacturer's specifications within seventy-two (72) hours where applicable. Non-emergency examples include: individual door problems; low battery notifications; isolated camera issues; and non-critical HUGS maintenance alerts.

5.8.4 Performance Metrics. The contractor shall maintain 99.9% operational availability measured monthly across ESS, CCTV/Qognify, and HUGS systems, excluding scheduled maintenance and

Government-directed outages. The contractor shall track and report response and resolution times monthly. Repeated failure to meet response or resolution times may result in performance deductions or other remedies as specified in the contract.

5.9 Service Request System

5.9.1 - Request System. The Government will use a software program to enter and prioritize requests for service, whether for support or new installations. The contractor shall complete each prioritized task in the software program by entering a description of the action taken and the results achieved. The system will document all work performed and provide the ability for the

Government and contractor to generate reports as required.

5.9.2 - Verbal Assignments. Under emergency circumstances, tasks may be assigned or modified verbally. A written version of any verbal task or modification will be provided to the contractor within two (2) working days. The contractor shall update the software program to reflect the written task or modification upon receipt.

5.10 - Meetings

5.10.1 - The contractor shall participate in regularly scheduled and ad hoc meetings as required to support mission requirements. Meeting attendance, minutes, action items, and responsible parties shall be documented and provided to the COR as requested.

5.11 - CEM User Training

5.11.1 - The contractor shall provide on-site CEM Access 2000 user training as requested by

BAMC, up to a…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .