PWS - Sources Sought Balboa Navy Medical RFID.docx

DOCX document 81 KB Posted

Attached to
Notice of Intent to Sole Source - Balboa Navy Medical San Diego, CA RFID
Solicitation number
PANHES-26-P-029793
Issued by

About this file

This is a Performance Work Statement (PWS) for the procurement, installation, maintenance, and service of an integrated Radio Frequency Identification (RFID) Tracking System at Balboa Navy Medical Facility in San Diego, California. The system is designed to track medical equipment across a large medical complex comprising multiple buildings that provide inpatient and outpatient services, including surgical centers, pharmacy services, behavioral health, and neonatal care, with support extending to 11 outpost facilities and multiagency users including USMC training camps. The existing RFID system for the Bio-Med office is non-operational with abandoned equipment remaining on site.

The contractor must plan, procure, and install a complete integrated RFID system capable of supporting approximately 35,000 tags (mix of active and passive) with real-time locating capability for high-value/critical devices. The system shall include fixed RFID readers at designated paths and choke points, handheld/mobile readers, a commercial off-the-shelf software platform utilizing a single database, graphical monitoring displays (minimum four 24-inch monitors at two workstations), 4-hour UPS backup power, and bi-directional interface capability with Defense Medical Logistics Standard Support (DMLSS) and future LogiCole migration. All work must comply with extensive cybersecurity requirements including DoD-approved operating systems, DoDIN Approved Products List compliance for network hardware, FIPS 140 encryption for external communications, DISA STIG/SRG application to 100% compliance, ACAS vulnerability scanning, and completion of all hardening activities prior to installation. The contractor shall deliver design activities including site survey report, shop drawings, product data, and design data; perform pre-acceptance and system acceptance testing with 72-hour burn-in requirements; provide one year of warranty covering parts and labor upon Government acceptance; conduct administrator and operator training for 5 personnel each across multiple sessions; and deliver comprehensive operation and maintenance manuals, as-built drawings in AutoCAD format, and cybersecurity documentation. Maintenance and service tasks include preventative maintenance, corrective maintenance, and cybersecurity maintenance and sustainment for multiple one-year periods during and following the warranty period. The contractor must comply with Army Corps of Engineers safety standards, provide bi-weekly status reports and meeting minutes, maintain a Quality Control Plan, and coordinate work with the On-Site Representative including infection control requirements for the medical facility environment.

View the file

Other files

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

Performance Work Statement Revision 00, September 2025 Procurement, Installation, Maintenance and Service of Radio Frequency Identification (RFID) Tracking System at Balboa Navy Medical San Diego, CA

1.0 SYNOPSIS. The objective of this Performance Work Statement (PWS) is for the planning, procurement, installation, maintenance, and service of an integrated Radio Frequency Identification (RFID) Tracking System for DHA Balbo Navy Medical Facility San Diego, CA.

1.1 Existing Conditions. DHA Balbo Navy Medical Facility San Diego, CA, is a large medical complex comprised of multiple buildings that offer both in-patient and out-patient service to include surgical centers, pharmacy services, Behavior Health, neonatal, physical therapy and much more. The hospital is the main medical facility for the greater San Diego area to include 11 out-post facilities service multi-agencies to include the USMC training camp. The Balbo Medical facility currently has a RFID Tracking System for the Bio-Med office but is non-operational with the existing equipment abended in place, to include wall mounted devices and rack mounted servers.

1.2 Revisions to the Performance Work Statement. Changes are identified in bold italics text. Deletions are indicated with a strikethrough and then removed in the following revision.

1.2.1 Revision 00. Revision 00 is for the Request for Proposal (RFP) of this Task Order.

2.0 SCOPE and PERFORMANCE REQUIREMENTS.

2.1 Contractor shall plan, procure, and install RFID Tracking System to include Maintenance and Service (M&S) as described in this PWS.

2.1.1 In conjunction with the requirements outlined in this PWS, reference Attachment 8 for a concept design of the RFID Tracking System.

2.2 Contractor shall provide a complete and integrated RFID Tracking System that meets the requirements of the PWS and attachments, to include all equipment, materials, documentation, and labor to implement the RFID Tracking System. The RFID Tracking System shall be compatible with the Installation's central monitoring system and monitored at Bldg. 1 Room C-14F1 and C-14G1.

2.2.1 Medical Facility Systems (RFID Tracking System). The RFID Tracking System shall be passive or active depended on the area of coverage, refer to Attachment 8. The tags must store unique IDs Linked to a central system, fixed RFID readers along designated paths and choke points (i.e. entrances, storage rooms, labs, ORs, and loading docks), Handheld/mobile readers for staff to scan equipment on demand, and real-time locating capability for high value/critical devices. The tags shall have the capability to detail equipment (i.e. type, model, serial number), Maintenance schedule/calibration status, sterilization/cleaning records, assigned department/location, and with stand temperature/humidity fluctuations in medical environments, and sterilization processes. The system shall support a large record of tags the estimated tag count around 35,000 tags, mix of active and passive tags, with the potential of future growth. The system shall operate over a network-based infrastructure, secure VLAN for RFID devices, and Wi-Fi/Bluetooth Low Energy (for hybrid solutions). The RFID tracking system shall have the ability capable of a bi-directional interface to Defense Medical Logistics Standard Support (DMLSS) (and future migration to LogiCole) via authorized ports

2.2.1.1 The RFID Tracking System software shall be commercial off-the-shelf that utilizes a single database for the subsystem integrations provided under a single operating environment. The system shall archive all events on a networked database server. The software shall support configuration and simultaneous monitoring of all subsystems.

2.2.1.2 Display graphical maps and text associated with the RFID Tracking System to include zone and device status integrated into the display.

2.2.1.3 Desk and wall space are available to desk mount up to six 24-inch monitors. At a minimum, two workstations, and four 24-inch monitors are required at each workstation location.

2.2.1.4 Contractor shall provide backup copies of all systems in their fully configured state upon successful System Acceptance Testing (SAT). Backups shall be sufficient to restore all components to their successful SAT state. The intent is to be able to rapidly restore the system in situations such as hardware failure or system corruption. Contractor shall demonstrate the backup copies restore the system(s) to the correct state.

2.2.2 Backup Power. RFID Tracking System workstations and network equipment shall be provided with 4-hour UPS backup.

2.2.3 Surge Suppression Devices. Contractor shall install appropriate surge protection devices in accordance with applicable Unified Facility Guide Specifications (UFGS) and manufacturers recommendations.

2.2.4 Component Enclosure. Shall be suitably rated for its environment, shall not have knockouts, and shall be lockable.

2.2.5 Equipment Rack. Shall be enclosed and lockable.

2.2.6 Infrastructure (conduit and cabling). Contractor shall install new cabling within each building. Contractor may use existing conduit and raceway for installing new cabling within buildings.

2.2.7 Software Support Agreement (SSA). Contractor shall provide any manufacturers’ SSA that are required to maintain, troubleshoot, and/or seek help on system issues. Furthermore, if a SSA is required beyond the warranty period or Period of Performance, Contractor shall notify the Government of such requirements.

2.2.8 Hot Cutover. Coordinate with the designated On-Site Representative to obtain approval and schedule any temporary outages and hot cutover. During the hot cutover, contractor shall ensure any affected system to include the existing RFID system is functional at the end of each workday.

2.2.9 Growth Capability. Growth capability is not to be limited by the provided products.

2.2.10 Finish/Esthetic. Contractor shall return all areas worked to the original fit and finish with matching paint and trim.

2.3 Execution of work shall be in accordance with (IAW) the base contract except as amended herein, and IAW the applicable documents.

2.4 Contractor shall submit a site-specific Quality Control Plan (QCP) and maintain an effective quality control program to ensure services are performed IAW this PWS.

2.5 The disposition of any equipment or material removed through this task order shall be determined by the site to either be turned over to the Government at the completion of work or properly disposed of IAW regulation and/or local codes.

2.6 Contractor shall make no public disclosures of work being performed under this task order.

2.7 Video and photographs shall only be taken while in possession of written authorization from the site. Any geotagging features such as Global Positioning System (GPS) or location recording shall be disabled prior to use. Contractor shall surrender any photographic equipment to the site security manager for review prior to departing the site. The Government reserves the right to delete photos deemed to contain sensitive data or images. Conversations and meetings shall not be recorded without expressed consent from all parties involved. Prior to completion of this task order, all video and photos taken shall be turned over to the Government with their associated negatives and all image files shall be deleted from the contractor’s records. Digital photographs shall be submitted to the Government on compact discs or encrypted transmission in Joint Photographic Experts Group (JPEG) format.

3.0 APPLICABLE DOCUMENTS. Technical criteria for the work described herein shall be as defined in the base contract and any site-specific requirements by the user. In the result of a conflict, the more stringent requirement applies. The following criteria (latest version at award of task order, unless otherwise noted) shall be applied during the execution of all work performed:

a. UFGS 01 78 23 Operation and Maintenance Data

b. UFGS 27 10 00 Building Telecommunications Cabling System

c. UFGS 28 31 76 Interior Fire Alarm and Mass Notification System

d. UFGS 01355 Environmental Protection

e. UFGS 01572 Construction and Demolition Waste Management

f. UFGS 0220 Earthwork

g. UFC 4-010-01 DoD Minimum Antiterrorism Standards for Buildings

h. UFC 4-010-06 Cybersecurity of Facility-Related Control Systems

i. UFC 4-021-01 Design and O&M: Mass Notification Systems (MNS)

j. UFC 4-510-01 Design: Military Medical Facilities

k. UFC 1-200-01 DOD Building Code

l. UL 1069 Standard for Hospital Signaling and Nurse Call Equipment

m. UL 2560 Standard for Emergency Call Systems for Assisted Living and Independent Living Facilities

n. DHA-AI 6040.02 Military Health Systems

o. HNC-PR-ED-2000.10 USAESCH Engineering Guidance Design Manual.

p. Federal Information Processing Standard (FIPS) 201

q. National Institute of Standards and Technology (NIST) Special Publication (SP) 800-116

r. NIST Special Publication 800-82, Guide to Industrial Control Systems (ICS) Security

s. Architectural Barriers Act (ABA)

t. Homeland Security Presidential Directive (HSPD) 12

u. National Fire Protection Association (NFPA) 70 National Electrical Code

v. NFPA 101 Life Safety Code

w. Safety and Health requirements shall be performed IAW U.S. Army Corps of Engineers EM 385-1-1

x. DHA Procedural Instruction 8400.01 Cybersecurity Logistics (CyberLOG) Medical Devices and Equipment (MDE) Risk Management Framework (RMF)

y. DoD Directive 8140.01 Cyberspace Workforce Management

z. DoD Instruction 8500.01, Cybersecurity

aa. DoD Instruction 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT)

ab. Defense Information Systems Agency (DISA) Secure Technical Implementation Guides (STIGs)

ac. All work shall be IAW industry standards and manufacturer recommendations.

4.0 SUMMARY OF REQUIREMENTS.

4.1 Task 1: Design Activities.

4.1.1 Site Survey. Contractor shall perform a site survey, coordinate with all stakeholders, gather the necessary site data, analyze the site(s) or facilities, perform any required testing of existing equipment, validate communication and power availability and pathways, equipment quantities, and identify any unique site features, characteristics, or operational limitations that affect the recommendations. Prior to visiting the site, and to the best extent possible, Contractor shall identify any existing site data (such as As-Built Drawings) that will be needed. Contractor shall provide the names of all Contractor personnel who will be part of the survey team and a list of data needed to the Project Manager and Project Engineer.

4.1.2 Site Survey Report. Contractor shall deliver a Site Survey Report that includes at a minimum:

a. Cover sheet with contract number, task order number, and date

b. Table of contents

c. Project description

d. List of all regulatory requirements applicable to the specific site

e. List of stakeholders and other key personnel contacted during the on-site assessment

f. Define stated requirements for each task listed in the PWS; description of the task’s existing systems and infrastructure, including the condition at time of survey; assumptions made where information was not available, and alternatives considered; and provide recommendations

g. Site environmental conditions that affect the recommendations

h. Description of existing infrastructure

i. Topography issues (terrain, frost line, trees)

j. List of known future projects that will affect this site

k. Bill of Material for equipment/material affected by the site condition changes and recommendations

l. Drawings per Attachment System Drawing. Or Site and facility layouts which show proposed locations of equipment. Or neither.

m. List of all Government provided equipment, services, or agreements

n. Address cybersecurity to include any current ATO; Government and contractor responsibilities

4.1.2.1 Contractor shall coordinate with the Government prior to documenting vulnerabilities in the Site Survey Report to ensure no classified data is released in an unclassified format.

4.1.3 SD-02 Shop Drawings. Contractor shall deliver shop drawings IAW Attachment 3.

4.1.4 SD-03 Product Data. Contractor shall deliver manufacturers’ data for all materials, equipment, and software required to implement the complete system as required in the SD-02 Shop Drawings. Contractor shall affirm within the submittal that all products, materials, and supplies are Buy American Act compliant. Contracting Officer (KO) granted waivers should be included.

4.1.5 SD-05 Design Data. Contractor shall deliver design data IAW Attachment 3.

4.2 Cybersecurity Requirements. Contractor shall design, develop, and integrate cybersecurity into the RFID Tracking System (to include, but not limited to, all hardware, software and/or equipment) IAW the DoD, Department of the Army (DA), any other applicable Government Agency standards or regulations. This work shall be done IAW all applicable Cybersecurity Regulations and Directives, as provided in this PWS. Contractor shall provide cybersecurity that is IAW current policies, procedures, and statutes, to include (but not limited to) those listed in Paragraph 3.0 Applicable Documents. Contractor is not responsible for the full Risk Management Framework (RMF) process but shall perform the technical hardening and documentation of the system as described in this section.

4.2.1 Contractor is responsible for providing all required software and hardware licenses and maintain their validity for the duration of the contract unless otherwise specifically stated.

4.2.2 Contractor shall utilize the latest DoD approved Operating Systems (OS) for all systems provided. Workstations and servers shall only use OSs as currently approved by the National Information Assurance Partnership. This list of approved OSs is available here: https://www.niap-ccevs.org/

4.2.2.1 When available, the Long-Term Servicing build of an OS shall be used. These builds prioritize stability and security over new features and typically include extended support and patches from the manufacturer.

4.2.3 All network hardware such as routers and switches shall have an active approval on the Department of Defense Information Network Approved Products List (DoDIN APL). The DoDIN APL is available here: https://aplits.disa.mil/

4.2.3.1 Any network connections that utilize commercial circuits or that physically exit government-secured property, to include wireless communications, are required to be encrypted end to end with a Layer 3 Virtual Private Network (VPN) tunnel using approved devices. Encrypted communications must use the most recently published FIPS 140 compliant encryption methods and shall use Digital Certificates where possible.

4.2.4 Contractor shall complete all cybersecurity hardening activities in their own facilities prior to system installation on site. These activities include system patching, updating (applications, OSs, firmware, antivirus, etc.), applying Secure Technical Implementation Guides (STIGs) and Security Requirements Guides (SRGs), and any other secure configuration requirements.

4.2.5 STIGs, SRGs, and SCAP Scans. Contractor shall apply all applicable Defense Information System Agency (DISA) STIGs and SRGs to all system components. This includes all OS, Firmware, Group Policy, Domain, Network, and Application-Specific STIGs/SRGs.

4.2.5.1 The most recent DISA STIGs/SRGs shall be used.

4.2.5.2 All components shall be configured to 100% STIG/SRG compliance. Any required deviations shall be justified, documented with supporting evidence, and submitted to the Government for acceptance and approval. (Acceptance shall not be assumed.)

4.2.5.3 For the purposes of applying STIGs, assume a system categorization of

4.2.5.3.1 Confidentiality: LOW Integrity: LOW Availability: LOW

4.2.5.4 Contractor shall use the automated SCAP, to be provided by the Government at no cost, to evaluate STIG/SRG compliance.

4.2.5.5 Contractor shall provide completed STIG/SRG checklists for each system component. SCAP results shall be imported into the checklists, but any rule not evaluated by the automated tool shall be manually evaluated. All “Open” or “Not Applicable” rules shall include a comment with clear justification.

4.2.6 The system shall incorporate a fully configured automated tool for collecting, reviewing, and reporting audit logs and system events.

4.2.7 Vulnerability Scans. Contractor shall procure and maintain a commercial vulnerability scanner that is compatible with the Assured Compliance Assessment Solution (ACAS).

4.2.7.1 Any vulnerability scans performed shall be credentialed scans and shall use a scan engine that was updated within seven days of the scan.

4.2.7.2 All system components shall be 100% ACAS compliant, with only “Info” findings. Any required deviations shall be fully documented, justified, and submitted to the government for acceptance and approval. (Acceptance shall not be assumed.)

4.2.8 Passwords. All default passwords shall be changed for all components provided under this contract, including, but not limited to hardware, software, BIOS, service accounts, maintenance accounts, administrator accounts, etc.

4.2.8.1 For components that have an applicable STIG/SRG, follow the password requirements of that STIG/SRG, otherwise configure password in accordance with AR-25-2.

4.2.9 Antivirus. All computers shall use the most recent DoD-approved antivirus software with the latest signatures/definitions.

4.2.10 Contractor shall provide, for approval (as outlined by Deliverable and Schedule Requirements), the following artifacts documenting completion of these activities prior to installation at the customer’s facilities:

a. System Description

b. Network Diagram(s)

c. Dataflow Diagram(s)

d. Hardware and Software Lists (IAW the defined eMASS template)

e. Ports, Protocols, and Services (PPS) List

f. System scan summaries and raw scan results (both ACAS Vulnerability and SCAP) no older than 14 days before date of submittal

g. All applicable STIG or SRG Checklists (completed with comments)

h. Network device configuration files.

i. POA&M or deviations document listing and justifying any unresolved vulnerabilities

4.2.11 Post-installation, but prior to final system acceptance, Contractor shall provide an updated set of all cybersecurity documentation and scans listed above.

4.2.11.1 Additionally, Contractor shall submit a comprehensive Account/Password list detailing the username and password for all system and privileged accounts (Device/BIOS, OS, Network, Application, Emergency, Administrator, Service Accounts). This list shall be encrypted using a DoD-approved encryption method and transmitted securely via DoD SAFE, encrypted email, or physical hand-off to the customer’s ISSM, or other Government individual at the direction of the Contracting Officer. Customer ISSM or representative shall sign off on the Account/Password list confirming that it is accurate and working prior to contract close-out.

4.2.12 The customer will be responsible for any accreditation activities once hardening has been completed and the Government accepts the required artifacts listed above.

4.3 Contractor Personnel Requirements. Contractor shall provide a list of the personnel performing the work that meet the following:

4.3.1 Antiterrorism/Operations Security (AT/OPSEC) requirements listed in Attachment 4.

4.3.2 System Administrators, or any contractor personnel making configuration changes to servers, workstations, or network devices, shall meet the requirements of a Cyber Defense Infrastructure Support Specialist (Work Role ID 521) at the “Intermediate” level or higher as defined by DoD Manual 8140 “Cyberspace Workforce Qualification and Management Program. The qualification matrix pertaining to Cybersecurity personnel is found on https://public.cyber.mil/wid/dod8140/qualifications-matrices/.

4.3.3 SD-07 Contractor Qualifications. Contractor shall deliver relevant and current experience and certificates for the specific installers who will perform the work. Installers shall have a minimum of two years of experience successfully installing systems of the same type and similar design within the last five years.

4.3.4 Contractor personnel on duty shall wear identification badges that include, at a minimum, the company’s name, and the name and photograph of the holder.

4.3.5 Any FA/MNS modifications required to provide a complete and useable ESS shall be performed by personnel IAW UFGS 28 31 76 Interior Fire Alarm and Mass Notification System.

4.3.5.1 The fire alarm system designer must be certified as a Level IV (minimum) Technician by National Institute for Certification in Engineering Technologies (NICET) in the Fire Alarm Systems subfield of Fire Protection Engineering Technology or meet the qualifications for a Qualified Fire Protection Engineer (QFPE).

4.3.5.2 A NICET Level IV fire alarm technician must supervise the installation of the FA/MNS.

4.3.5.3 NICET Level II technician to assist in the installation of FA/MNS devices, cabinets, and control units.

4.3.5.4 NICET Level IV technicians utilized in testing and certification of the installation of the FA/MNS devices, cabinets, and control units.

4.4 Procure and Install. Contractor shall procure and install RFID Tracking System, for the Balbo Medical Facility and out-post facilities

Task 2. Balbo Medical Facility.

4.5 Maintenance and Services (M&S). Reference Attachment 5 for M&S.

Task 3. Contractor shall provide Preventative Maintenance (PM) for one year. during the warranty period.

Task 4. Contractor shall provide Cybersecurity Maintenance and Sustainment (CSMS) for one year. during the warranty period.

Task 5. Contractor shall provide Corrective Maintenance (CM) for one year. during the warranty period.

Task 6. Contractor shall provide PM for one year following the warranty period.

Task 7. Contractor shall provide CSMS for one year following the warranty period.

Task 8. Contractor shall provide CM for one year following the warranty period.

Task 9. Contractor shall provide PM for one year.

Task 10. Contractor shall provide CSMS for one year.

Task 11. Contractor shall provide CM for one year.

Task 12. Contractor shall provide PM for one year.

Task 13. Contractor shall provide CSMS for one year.

Task 14. Contractor shall provide CM for one year.

Task 15. Contractor shall provide PM for one year.

Task 16. Contractor shall provide CSMS for one year.

Task 17. Contractor shall provide CM for one year.

4.6 RFID Tracking System Training. Contractor shall, at a minimum, conduct training as defined below. Assume that attendees have a high school education or equivalent and are familiar with RFID Tracking System. The training shall be oriented to the specific systems being installed.

4.6.1 SD-07 Instructor Qualifications. Contractor shall submit instructor's experience and certified qualifications data. Show that the instructor has received a minimum of 24 hours of system training from a technical organization and two years of experience in installing the specified system type.

4.6.2 Training Content. Training content shall include training manuals and audio-visual materials. Contractor shall provide each trainee a training manual. The manuals shall include, at a minimum, an agenda, defined objectives for each lesson, and a detailed subject matter description for each lesson.

4.6.3 Training Plan. Contractor shall submit a training plan for the training phases, including type of training to be provided, outline of training manuals, training course agendas, and a list of reference material.

4.6.4 Training Schedule. Contractor shall submit a training schedule.

4.6.5 RFID Tracking System Administrator Training.

a. RFID Tracking System Administrator Training includes:

(1) Two (one day) eight-hour on-site training sessions for 5 personnel.

(2) Operating system procedures and configuration

(3) Operator functions

(4) Database functions and setup

(5) Card holder input and deletion procedures

(6) Report generation

(7) Applications programs (as applicable)

(8) Graphics generation and manipulation

(9) Items unique to the ACS and IDS interfaces with other systems

(10) System backup and restore

4.6.6 RFID Tracking System Operator Training.

a. RFID Tracking System Operator Training includes:

(1) Four (one-day) eight hour on-site training sessions for 5 personnel.

(2) System operating procedures

(3) System configuration orientation

(4) Alarm acknowledgment

(5) Alarm response logging

(6) Graphics functionality

(7) Items unique to the ACS and IDS interfaces with other systems

4.6.7 Training Survey. Training for each course shall be confirmed through student surveys. Each student of a specific course shall be given a survey to evaluate the training provided. The survey from each course shall be used to determine the successfulness of the training sessions and adjust the curriculum to better equip the students for operation, administration, and maintenance of the system. The survey shall include, at a minimum, the students name, rank, and signature of student, date, time, course, session, and name of instructor, and should ask, at a minimum, the following questions:

a. What portions of training were most helpful?

b. What portions of training were least helpful?

c. What areas should be covered more in depth?

d. Are you satisfied with the level of training you received?

e. How well do you feel the instructor performed in equipping you to support the installed systems?

4.7 RFID Tracking System Testing. Contractor shall demonstrate that, without exception, the completed and integrated RFID Tracking System complies with the contract, task order requirements and approved test plan.

4.7.1 Test Plan and Logs. Contractor shall submit a Test Plan that addresses pre-acceptance and System Acceptance Testing (SAT) to include personnel, equipment, procedures and provide test logs for recording all data from the required testing.

4.7.2 Testing Quality Assurance. Personnel performing the testing shall have at least two years of hands-on RFID Tracking System experience with the specific equipment, hardware and software installed under this task order.

4.7.3 Pre-Acceptance Testing. Contractor shall perform a Pre-Acceptance testing, based on Unified Facilities Guide Specifications (UFGS) Section 28 08 10 – RFID Tracking System Acceptance Testing. Following the successful completion of the functional testing, the burn-in testing shall commence for a continuous 72-hour period. Contractor shall submit all Draft Test Reports to the Government, and all documentations for each phase of the tests, prior to the SATs.

4.7.4 System Acceptance Testing. Contractor shall notify the Government of system readiness. Contractor shall be liable for costs incurred by the Government to mobilize on-site if Contractor is not ready to start, or the system fails to pass SAT. Costs incurred by the Government shall include costs associated with travel, per-diem, and labor. Contractor shall provide a credit to the task order commensurate to an amount incurred by the Government.

4.7.4.1 Functional Testing. Contractor shall test the RFID Tracking System IAW the approved Test Plan in the presence of the Government Representative(s) to certify acceptable performance. Verify that the total system meets all requirements of the specifications and complies with the specified standards. Place the RFID Tracking System in normal operating mode and evaluate system performance during the testing period.

4.7.4.2 Immediately report any deficiencies observed during testing to the Government Representative(s) and discuss possible causes and corrective measures. Obtain Government approval prior to making any adjustments, repairs, or modifications. The Government retains the right to terminate testing at any time the system is found to be incomplete or fails to perform as specified. Such termination of acceptance testing constitutes a failed SAT.

4.7.4.3 Final Test Report. Contractor shall submit a Final Test Report to address the following topics:

a. Summary – a chronological summary of all testing describing test activities, results to include required corrections (punch list items) and status in narrative form.

b. Personnel - list of Government and Contractor personnel who participated in the testing.

c. Test Logs - provide completed test logs along with a test log verification signed by Contractor and Government representative(s).

d. Punch List Verification – any residual punch list items not affecting system performance as indicated in the test procedures and not completed and witnessed by the Project Engineer shall be thoroughly documented with descriptions and photos in the Final Test Report.

4.8 System Operation and Maintenance Manuals. Contractor shall submit RFID Tracking System components and software operator's manual which fully explain all procedures and instructions for the operation of the system(s). The maintenance manual shall describe maintenance for all equipment including inspection, periodic preventive maintenance, fault diagnosis, and repair or replacement of defective components.

4.9 As-Built Drawings. Maintain a separate set of drawings, elementary diagrams, and wiring diagrams of the system IAW Attachment 3 to be used for As-Built Drawings. Keep this set accurately and neatly up to date with all changes and additions. This set is not to be used for installation purposes. As-built drawings shall be developed and maintained by Contractor and depict actual conditions, including deviations from the Contract Documents. These deviations and additions may result from coordination required by but not limited to contract modifications; official responses to Contractor submitted Requests for Information; direction from the KO; designs which are the responsibility of the Contractor, and differing site conditions. Maintain the As-Builts throughout construction as red-lined PDF files. As-Built Drawings shall be submitted, in AutoCAD X and .pdf format, with the Final Test Report.

4.10 Warranty. Contractor shall provide a one-year warranty to include parts and labor for all components installed during this task order. Warranty shall include all hardware, firmware, software, licenses, and Software Development Kits (SDKs) used for integration or as part of the system(s) installed or modified by Contractor. The warranty will commence upon Government acceptance of the system. Government acceptance is defined as successful completion of the SAT.

4.10.1 Letter of Warranty. Contractor shall provide a Letter of Warranty with the SAT Test Report that includes Contractor Points of Contact (POC) information and phone numbers for warranty calls, terms of warranty, and a list of all equipment installed under this task order. This list shall include vendor, model number, serial number, warranty start date, Contractor’s warranty expiration date, and equipment manufacturer’s warranty expiration date.

4.11 Meetings. Contractor shall attend, at least, a post-award meeting, installation kickoff meeting, and bi-weekly production meetings to ensure that the project is successful. Contractor shall record meeting minutes and provide to the Government within five (5) business days.

4.12 Status Reports. Contractor shall provide bi-weekly status reports. Status reports shall include contract and task order number, project description, work accomplished previous week, work to be accomplished within the next week, teleconference minutes, problems or issues that affect ability of the contractor to perform, whether Contractor is on schedule, and percentage complete.

4.13 Safety Compliance Requirements. Contractor shall comply with FAR 52.236-13 Accident Prevention and execute all work IAW the latest version of Safety Manual EM 385-1-1 per the base contract.

4.13.1 Site Visit Accident Prevention Plan (SVAPP). The SVAPP is required for any site visit not covered by an APP. The SVAPP only allows for visual inspection/observation or office type work. An SVAPP is required if an Accident Prevention Plan (APP) with an Activity Hazard Analysis (AHA) has not been accepted by the Government Safety and Occupational Health Office (SOHO). If work must be performed (i.e., metering, work on equipment), Contractor shall submit an APP.

4.13.2 Accident Prevention Plan. The APP shall follow the minimum requirements of EM 385-1-1 Chapter 2-7 and this PWS. Contractor shall follow the mandatory ENG Form 6293 (Accident Prevention Plan Worksheet). Contractor shall submit an APP and receive Government acceptance prior to starting any service/construction work.

4.13.2.1 Contractor shall verify with the controlling installation, the applicability, and requirements for emergency procedures, permit required work procedures, waste disposal, and hazardous locations/environments (including but not limited to potential lead and asbestos exposure). These findings shall be incorporated into the APP.

4.13.3 Activity Hazard Analysis. All AHAs shall be written IAW paragraph 6 of each applicable chapter from EM 358-1-1. The identification and proof of qualification for competent/qualified persons (e.g., Confined Space, Electrician, Crane Operator, etc.) and proof of qualification shall be included with the AHA IAW EM 385-1-1 Chapter 2-6.d(4)(g).

4.13.4 Site Specific Addendum. Addendums are required for each site if work will be conducted on two or more sites. The addendums shall receive Government acceptance prior to starting. Each addendum shall contain detailed site-specific information only applicable to a specific location. It shall be attached to the APP as an appendix and be readily available on the jobsite. If work on more than one jobsite is occurring simultaneously, Contractor shall include information on how the prime contractor will ensure safety oversite is adequate on all sites.

4.13.5 Safety document resubmittals shall include the original local SOHO comments with detailed responses. Highlight all changes in the resubmission.

4.13.6 Contractor is responsible to verify that any proposals and/or contract modifications are covered under the current accepted APP. If the pending work effort is not covered under the initial task order APP, then Contractor shall submit, for Government review and acceptance, an addendum to the APP.

4.13.7 Notifications and Reports. All accidents and near misses shall be reported IAW EM 385-1-1, Table 2-1. Most current version of the ENG Form 3394 shall be used for all reporting measures.

4.13.7.1 Contractor shall provide Monthly Exposure Hours Reports. This report is a compilation of employee-hours worked each month for all site workers, both prime and subcontractors. Hours associated with administrative activities such as payroll, human resource, service order managers, etc., are not counted. The information cut-off date will be the last day of each month. Exposure data consists of man-hours expended in direct performance of the work performed on the jobsite. The monthly submission shall be broken down by contract and identify exposure hours for each Task Order. If no hours are worked on the project/task, a report showing zero (0) is required.

4.13.8 Site Safety and Health Officer (SSHO). Refer to Attachment 2 for the minimum SSHO coverage requirements. An SSHO shall be onsite whenever active work is occurring. Triple or more hatting is not allowed. During the install phase, on-site work shall not be conducted until a minimum of an SSHO L2 is present as described in EM 385-1-1 Chapter 2-8.b.

4.13.9 Prime Contractor Corporate Safety Official. This contract requires a minimum of one Corporate Safety Official to manage and oversee the implementation of the Prime Contractor’s Safety Program and work with the on-site SSHO’s to ensure compliance with the APP’s guidance. The Corporate Safety Official shall follow the roles and responsibilities listed in EM 385-1-1 Chapter 2-4.f. This individual is not required to physically be on the project site.

4.14 Coordination of Work.

4.14.1 The site will provide the contractor and its subcontractor(s) with access to the site five (5) days a week, 0800 to 1600, as a minimum, excluding U.S. Federal holidays. The site may also provide access at other times to include weekends and after duty hours after receipt of a trouble call.

4.14.2 Contractor shall give ample time 72-hours to the OSR when coordination events are required.

4.14.3 Digging and Trenching. Contractor shall mark proposed locations of all trenching/underground work and be responsible for obtaining all permits and coordinating with the On-Site Representative, Environmental, and Department of Public Works (DPW) organizations for determination of potential underground installation interference prior to the planned start of the trenching/underground work. Appropriate installation personnel shall ensure the location of already existing underground utilities are identified and marked. Contractor shall have written authorization from the On-Site Representative prior to performing any digging or trenching.

4.14.4 Permits, Licenses, and Fees. Contractor is responsible for all permits and licenses required by regulating agencies. Contractor shall pay all duties, fees, taxes, and other charges necessary and incidental to the due and lawful execution of the work.

4.14.5 Contractor Deliveries. To avoid schedule conflicts and delays, all deliveries shall be coordinated in advance with the On-Site Representative.

4.14.6 Contractor Parking. Parking spaces for company vehicles may be assigned to the contractor as coordinated with the On-Site Representative. Contractor employees shall comply with parking regulations.

4.14.7 Contractor Field Office. Space is available so the contractor may be permitted to establish a temporary office at the project site at the contractor’s own cost. Contractor shall make this request to the COR for review, approval, and coordination with the On-Site Representative.

4.14.8 Staging, Storage, and Work Areas. If requested, Contractor may be permitted to establish a temporary area designated for the storage of materials. Contractor shall make this request through the COR for review, approval, and coordination with the coordination with the On-Site Representative. Contractor shall remove all company equipment and assets from the Government premises at the end of the contract.

4.14.9 Work Area Requirements. Contractor shall maintain worksite in a reasonably neat appearance. This shall be done by daily cleanups of the worksite. Contractor is responsible to secure all tools and materials at the close of business. Contractor shall protect all materials from exposure to the elements. This requirement applies to all job areas.

4.14.10 Special Requirements. Contractor shall meet the site-specific safety requirements as listed in section 11.0 of the PWS include any notice of work with a 72-hour prior notification to the SOR. Contractor shall meet the onsite requirement of using a HEPA Cart for any and all work within the facilities, the HEPA Cart shall be provided by Contractor.

4.14.11 Infection Control. Contractor shall coordinate with the Government OSR for infection control requirements prior to any work activities taking place. Each space within the medical facilities has different requirements for infection control and vary between less stringent to the most stringent.

5.0 DELIVERABLES. All deliverables shall be marked IAW Attachment 2 with the applicable Controlled Unclassified Information (CUI) category, and protected accordingly. Electronic submittals with multiple pages must be arranged so it can be easily maneuvered with links to index pages. Contractor shall provide the deliverables in Attachment 2, and unless otherwise stated, with an ENG Form 4025. Unless otherwise stated, Government review of deliverables is 30 calendar days. In the event of a resubmittal, Contractor shall resubmit the deliverable with response to changes within 15 calendar days. If Contractor is not able to resubmit within the given period, justification and a resubmittal date shall be provided.

6.0 RESIDENT MANAGEMENT SYSTEM (RMS). This task order will utilize RMS.

7.0 PAYMENT SCHEDULE. Government and Contractor agree that payments to be made for this contract shall be based upon satisfactory completion by Contractor of the milestones established in the following milestone payment schedule.

Item
Description

(Completion and Government Acceptance) Percent

A
SVAPP
100% of Item A CLIN(s)

APP

Site Specific QCP

Initial detailed Project Schedule

Task 1: Design Activities

B
Pre-Installation Cybersecurity Artifacts
10% of Items B thru E
C
Installation and integrations activities. Progress Payments Allowed.
80% of Items B thru E

Final Cybersecurity Artifacts and Activities

Training sessions and Training Surveys

D
SAT and Final Test Report
15% of Items B thru E

SD-11 As-Built Drawings

System Operation and Maintenance Manuals

E
Monthly Man-Hours Report
5% of Items B thru E

After Action Reports (As Required)

Accident Reporting (As Required)

Any other documentation and/or training required

Milestone Event
Payment at Completion of Event
Maintenance & Reports
96% of the maintenance CLIN to be divided by frequency of maintenance requirements
Maintenance Plan, ATOPSEC, Personnel List and Certifications, Initial Spare Parts Recommendation
4% of the maintenance CLIN
Service Orders completed within the prior month with site Government signature of completion
100% of each SO (Progress payments may be allowed based on complexity and size of the service order.)

8.0 POINTS OF CONTACT. POC for this task order are listed in the task order award documents.

9.0 PERIOD OF PERFORMANCE AND PROJECT SCHEDULE.

9.1 Period of Performance (POP). POP dates are stipulated in the appropriate CLINs.

9.2 Project Schedule. Contractor shall provide a detailed Project Schedule. At a minimum, the schedule shall include the requirements in Attachment 2, proposed date for kick-off meeting for site survey, the proposed install mobilization, SAT, and Task Order completion dates. An updated Project Schedule shall be provided after acceptance of the design. Contractor shall notify the Government immediately if the schedule falls more than 30 calendar days behind and provide updated Project Schedule with justification.

10.0 QUALITY ASSURANCE (QA). The Government performs QA of Contractor's performance under this contract using the method of surveillance specified in the Performance Requirements Summary (PRS) in Attachment 1 Quality Assurance Surveillance Plan (QASP). The Government conducts QA inspections on all phases and types of work performed. The Government reserves the right to perform QA inspections at any time.

10.1 Contractor shall provide photographs and/or videos of installation efforts to the Government. The images captured are typically of efforts that are not easily accessible such as backfilled trenches, confined spaces, handholes, and overhead spaces that require ladder or lift. The images should capture enough data to assist with QA efforts such as evaluating conduit fills, terminations, labels, and overall workmanship. Prior to capturing and submitting images, Contractor shall coordinate with the Government on sensitivity areas, permits, and transmission methods.

11.0 LIST OF ATTACHMENTS. All attachments are included with this PWS but are provided under separate cover.

Attachment 1 – Quality Assurance Surveillance Plan Attachment 2 – Deliverables, Schedule, and Minimum SSHO Coverage Requirements Attachment 3 – Drawing Requirements Attachment 4 – Antiterrorism/Operations Security Requirements Attachment 5 – Maintenance and Service Requirements Attachment 6 – Service Log Attachment 7 – Service Order Form Attachment 8 - Site Floor Plans (Marked) Attachment 9 - Infection Control Risk Assessment 2.0 Attachment 10 - Smoke and Fire Barrier Protection Policy

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