36C24427R0001.pdf

PAGE 1 OF 1. REQUISITION NO.

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NO. 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

a. NAME b. TELEPHONE NO. (No Collect Calls) 8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY CODE 10. THIS ACQUISITION IS UNRESTRICTED OR SET ASIDE: % FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ IFB RFP

15. DELIVER TO CODE 16. ADMINISTERED BY CODE

17a. CONTRACTOR/OFFEROR CODE FACILITY CODE 18a. PAYMENT WILL BE MADE BY CODE

TELEPHONE NO. UEI: EFT:

PHONE: FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19. 20. 21. 22. 23. 24.

ITEM NO. SCHEDULE OF SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA ARE ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________ 29. AWARD OF CONTRACT: REF. ___________________________________ OFFER COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DATED ________________________________. YOUR OFFER ON SOLICITATION DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY (BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION (REV. NOV 2021)

PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

AWARDED:

EFFECTIVE:

36C24427R0001 10-09-2026

Kevin Rodgers 267-207-9835 11-09-2026

1:00PM EST

36C460 Department of Veterans Affairs Network Contracting Office 4 Wilmington VAMC 1601 Kirkwood Highway Wilmington DE 19805

X 100

X

541519

$34M

N/A

N/A

36C460

Department of Veterans Affairs

Wilmington VAMC 1601 Kirkwood Highway Wilmington DE 19805

36C460

Department of Veterans Affairs Network Contracting Office 4 Wilmington VAMC 1601 Kirkwood Highway Wilmington DE 19805

Austin Payment Center Department of Veterans Affairs

PO Box 149971 Austin TX 78714-9971

(877) 353-9791 (512) 460-5429

See CONTINUATION Page

Wilmington VA Medical Center Patient Elopement System Proposals due by: 1:00PM EST on 11-09-2026

The Contractor shall provide the required labor, equipment, materials, and supervision to complete all performance requirements identified in the Performance Work Statement.

Interested parties are encouraged to attend the pre-bid site visit. The site visit will be held at 1:00PM EST on 10/21/26 Participants are to meet at Building 10 Conference Room 003.

RFI's are due in writing via email to Kevin.Rodgers2@va.gov by 1:00PM EST on 10-27-2026. Late questions will NOT be d Accepted. Answers will be provided via an amendment posted publicly to htts://sam.gov/ The Contractor shall be responsible for the correct title classification of workers and compliance with all applicable wage and hour laws associated with this location of service.

Refer to https://www.sam.gov for SCA WD.

SCA WD No.: 2015-4215 (Rev. 33), Dated: 08/17/2026, is applicable.

See CONTINUATION Page

X X

X 1

Cheryl Roberts Contracting Officer

36C24427R0001

Table of Contents

SECTION A

A.1 SF 1449 SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS

AND COMMERCIAL SERVICES

A.2 PRICE/COST SCHEDULE

ITEM INFORMATION

A.3 DELIVERY SCHEDULE

ADDITIONAL SIMPLIFIED ACQUISITION TERMS AND CONDITIONS

A.4 52.212-2 EVALUATION—COMMERCIAL PRODUCTS AND COMMERCIAL

SERVICES (NOV 2021) (DEVIATION)

A.5 52.216-1 TYPE OF CONTRACT (NOV 2025) (DEVIATION)

A.6 52.219-1 SMALL BUSINESS PROGRAM REPRESENTATIONS (NOV 2025)

(DEVIATION)

A.7 52.233-2 SERVICE OF PROTEST (SEP 2006)

A.8 52.222-90 ADDRESSING DEI DISCRIMINATION BY FEDERAL CONTRACTORS

(DEVIATION APR 2026)

A.9 52.225-6 TRADE AGREEMENTS CERTIFICATE (FEB 2021)

A.10 52.240-90 SECURITY PROHIBITIONS AND EXCLUSIONS

REPRESENTATIONS AND CERTIFICATIONS (NOV 2025) (DEVIATION)

A.11 52.240-91 SECURITY PROHIBITIONS AND EXCLUSIONS (NOV 2025)

(DEVIATION)

A.12 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE

(FEB 1998)

A.13 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

A.14 52.252-5 AUTHORIZED DEVIATIONS IN PROVISIONS (NOV 2020)

A.15 52.252-6 AUTHORIZED DEVIATIONS IN CLAUSES (NOV 2020)

A.16 VAAR 852.219-75 VA NOTICE OF LIMITATIONS ON SUBCONTRACTING—

CERTIFICATE OF COMPLIANCE FOR SERVICES AND CONSTRUCTION (JAN 2023)

(DEVIATION)

A.17 VAAR 852.252-70 SOLICITATION PROVISIONS OR CLAUSES

INCORPORATED BY REFERENCE (JAN 2008)

A.18 SUPPLEMENTAL INSURANCE REQUIREMENTS

Wilmington, DE VA Medical Center

Wilmington, DE 19805

Performance Work Statement

For

CLC & Fourth floor Patient Elopement Upgrade Project No. 460-24-009

-- Project Scope --

GENERAL:

This project is located in Building 17, in the CLC, and Building 1, on the 4th floor at the Wilmington VA Medical Center. This project involves all demo and replacement of existing Stanley WanderGuard system with upgraded and improved Patient elopement technology. This platform must be portable (worn by the patient) and provide nurse staff with the location of the patient if an elopement event is triggered.

o The project boundaries for Building 17 include but not limited to building 17 starting at the entrances and exits of the CLC where the existing WanderGuard systems bounds are.

Other items required to be installed outside of these project boundaries to meet the goals of the project are acceptable.

o The project boundaries for Building 1 include but not limited to the 4th floor starting at the entrances and exits of the floor where the existing WanderGuard systems bounds are.

Other items required to be installed outside of these project boundaries to meet the goals of the project are acceptable.

1.0 SCOPE OF WORK:

The Contractor shall provide the professional services, hardware, and software required for the maintenance, expansion, and integration of patient elopement and wandering (PEW) prevention systems across our HCS(s). The scope includes the following:

• Technology and Project Management: The Contractor shall develop and maintain a master project plan, coordinate stakeholder engagement, provide reporting, and track key performance indicators (KPIs) such as location accuracy, alarm response times, and system uptime.

• Requirements and System Design: The Contractor shall conduct workflow discovery and produce architecture for the PEW prevention systems, including coverage maps, geofencing zones, and per-patient security profiles.

• Delivery and Staging: The Contractor shall manage hardware/software staging, perform pre-configuration, and validate interoperability among components.

• Installation and Deployment: The Contractor shall ensure site readiness and perform hardware installation (e.g., readers, gateways, LF chokepoints, Wi-Fi tags, BLE beacons), patient tagging, and zone configuration.

• Integration with Enterprise Systems: The Contractor shall configure integrations with enterprise platforms such as the fire alarm systems, elevator controls and physical access control systems to enable event-driven alerts and secure workflows.

• BLE Enablement: The Contractor shall implement beacon placement strategies, calibrate for accuracy, integrate gateways, and enable mobile app functionality (if applicable) for real-time notifications.

• Data Governance and Cybersecurity: The Contractor shall ensure HIPAA compliance, encryption, adherence to VA security standards, and support VA Enterprise Risk Analysis (ERA) processes.

• Testing and Validation: The Contractor shall perform factory and site acceptance tests, verify accuracy and alarm detection, conduct performance and failover testing, and validate data integrity.

• Training and Change Management: The Contractor shall deliver role-based training, provide Standard Operating Procedures (SOPs) and job aids, ensure

Section 508 compliance, and implement adoption strategies with OEM clinical educator support.

• Operations and Sustainment: The Contractor shall implement a tiered support model with SLAs, provide preventive and corrective maintenance, monitor system health, and conduct optimization reviews.

• Documentation and Deliverables: The Contractor shall provide design diagrams, configuration baselines, test reports, operational manuals, and disaster recovery plans.

• System Health and Analytics: The Contractor shall deploy dashboards for device uptime, tag battery status, location accuracy, alarm metrics, utilization trends, and predictive analytics for workflow optimization.

1.1 PERFORMANCE OBJECTIVES:

• Objective 1: The Contractor shall deliver a unified PEW enterprise architecture that addresses Wilmington VAMC operational, clinical, and technical requirements. This objective includes conducting comprehensive workflow discovery, facility assessments, and technical analyses to document current-state conditions. In addition, the resulting architecture must incorporate standardized clinical workflows, common geofencing strategies, uniform alarm routing rules. The enterprise architecture shall be scalable, support modern RTLS/BLE capabilities, comply with VA infrastructure standards, and provide a foundation for long-term modernization and future enhancements.

• Objective 2: The Contractor shall provide a comprehensive transition pathway from all existing PEW systems currently deployed at Wilmington VAMC (Table 1) to the proposed solution. This shall include a detailed migration strategy, risk mitigation approach, interoperability plan, and schedule that ensures continuity of operations and prevents disruption to patient safety workflows. The Contractor must identify required technical adaptations, data migration steps, integration changes, and interim support measures needed to maintain full functionality of legacy systems throughout the transition. The pathway shall enable a controlled, phased, and fully supported migration that preserves operational readiness while achieving alignment with the proposed enterprise PEW prevention platform.

• Objective 3: Implement, configure, and validate the standardized enterprise solution once designed, ensuring installations are aligned with VISN requirements and tailored to site-specific operational environments. This includes deployment and calibration of hardware components such as readers, gateways, exciters, beacons, and controllers; configuration of software platforms, user interfaces, and alarm logic; execution of facility-specific tuning for accuracy and zone detection; and system optimization to ensure performance expectations are met. The objective also includes comprehensive acceptance testing—such as performance testing, interference checks, accuracy validation, and user acceptance testing—to confirm that the system meets clinical, operational, and technical needs.

• Objective 4: Ensure that all system components comply with applicable VA cybersecurity requirements. This objective includes implementing FIPS-validated encryption for data at rest and in transit, ensuring PIV-authenticated access for system users, validating authoritative data source integration requirements, and aligning all applications and hardware with VA Technical Reference Model standards. It also encompasses compliance with VA’s identity and access management frameworks, vulnerability remediation timelines, OS and application patching requirements, and accessibility standards for all user-facing interfaces and documentation.

• Objective 5: Provide comprehensive training, documentation, and transition support to ensure Wilmington VAMC’s staff are prepared to operate and maintain the standardized system long term. This includes developing and delivering role-based training for clinical, security, biomedical engineering, OIT, and administrative staff; preparing user guides, technical manuals, SOPs, and job aids; documenting all system configurations, workflows, and maintenance procedures; and executing a structured transition plan with a clearly defined Responsible, Accountable, Consulted, and Informed (RACI) model. The goal is to establish VISN-wide competency and self-sufficiency, ensuring that each facility can support routine operations, respond effectively to alarms, manage patient tagging workflows, and sustain the enterprise system after the period of performance.

1.2 TEAMING AND RESELLER REQUIREMENTS:

The Contractor shall maintain formal teaming agreements or authorized reseller/distributor status with the Original Equipment Manufacturers (OEM) for all proposed hardware, software, and professional services throughout the entire Ordering Period. Offerors must demonstrate the ability to obtain required OEM agreements prior to performance and must provide proof of OEM authorization during the contract kickoff meeting. The Contractor shall ensure that all OEM partnerships grant full rights to procure, configure, install, integrate, and support the proposed solutions, including access to OEM technical resources, firmware updates, and warranty services. Failure to maintain OEM authorization or teaming agreements during the POP may result in termination for cause.

2.0 PERFORMANCE DETAILS:

The Contractor shall provide and/or acquire the services, hardware, and software required consistent with the general requirements of this PWS.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer Representative (COR).

There are eleven (11) Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, four are set by date:

New Year's Day January 1

Juneteenth June 19

Independence Day July 4

Veterans Day November 11

Christmas Day December 25

If any of the above falls on a Saturday, then Friday shall be observed as a holiday.

Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

Martin Luther King's Birthday Third Monday in January Washington's Birthday Third Monday in February

Memorial Day Last Monday in May

Labor Day First Monday in September

Columbus Day Second Monday in October

Thanksgiving Fourth Thursday in November

2.1 PLACE OF PERFORMANCE:

The list of current Health Care Systems supported this by this requirement, and their addresses, are given in Table 1.

ID Name Address PEW System in Use

460 Wilmington VAMC 1601 Kirkwood Hwy, Wilmington, DE 19805

Stanley WanderGuard

Table 1: Health Care Systems covered under the scope of this contract

2.1.1 TRAVEL:

The Government anticipates travel under this effort to perform the tasks associated with the effort. Travel costs are included in the firm-fixed price line items. These costs will not be directly reimbursed by the Government.

3.0 SPECIFIC TASKS AND DELIVERABLES:

Wilmington may cover multiple functional areas outlined below. These functional area descriptions are provided to offer greater insight into the complexity and uniqueness of potential Wilmington requirements addressed in this Performance Work Statement (PWS). Functional areas are not mutually exclusive.

3.1 TECHNOLOGY AND PROJECT MANAGEMENT:

The Contractor shall implement comprehensive technology and project management practices Responsibilities include developing and maintaining a Master Project Plan (MPP) covering scope, schedule, cost, quality, resources, communications, risks, and delivery, as well as; coordinating multi-disciplinary stakeholders (Nursing, Healthcare Technology Management (HTM), Office of Information Technology (OIT), Supply Chain Management (SCM), Engineering, etc.). The Contractor shall administer formal governance routines (steering committee, change control board) and maintain artifacts (risk/issue/change logs) in a VA-approved repository. The Contractor shall assist with defining, tracking, and continuously refining KPIs aligned to VA objectives including location accuracy, system uptime, and integration success rate, with variance analysis and corrective action plans. Project controls shall include dependency tracking and critical path analysis.

https://www.bing.com/ck/a?!&&p=4b5afaca00a42fe8b90afd88ae3c850275b6d01c6e6c9453c6ab7a9624c012fbJmltdHM9MTc4ODkxMjAwMA&ptn=3&ver=2&hsh=4&fclid=3848f3bc-8ba0-605f-36e2-e4718a1f6129&u=a1L21hcHM_Jm1lcGk9NTd-fkVtYmVkZGVkfkxhcmdlTWFwTGluayZ0eT0xOCZxPTE2MDElMjBLaXJrd29vZCUyMEh3eSUyQyUyMFdpbG1pbmd0b24lMkMlMjBERSUyMDE5ODA1JnBwb2lzPTM5Ljc0MDIxNl8tNzUuNjA2NTExXzE2MDElMjBLaXJrd29vZCUyMEh3eSUyQyUyMFdpbG1pbmd0b24lMkMlMjBERSUyMDE5ODA1X34mY3A9MzkuNzQwMjE2fi03NS42MDY1MTEmdj0yJnNWPTEmRk9STT1NSVJFJnFwdnQ9MTYwMStraXJrd29vZCtoaWdod2F5&ntb=1 https://www.bing.com/ck/a?!&&p=4b5afaca00a42fe8b90afd88ae3c850275b6d01c6e6c9453c6ab7a9624c012fbJmltdHM9MTc4ODkxMjAwMA&ptn=3&ver=2&hsh=4&fclid=3848f3bc-8ba0-605f-36e2-e4718a1f6129&u=a1L21hcHM_Jm1lcGk9NTd-fkVtYmVkZGVkfkxhcmdlTWFwTGluayZ0eT0xOCZxPTE2MDElMjBLaXJrd29vZCUyMEh3eSUyQyUyMFdpbG1pbmd0b24lMkMlMjBERSUyMDE5ODA1JnBwb2lzPTM5Ljc0MDIxNl8tNzUuNjA2NTExXzE2MDElMjBLaXJrd29vZCUyMEh3eSUyQyUyMFdpbG1pbmd0b24lMkMlMjBERSUyMDE5ODA1X34mY3A9MzkuNzQwMjE2fi03NS42MDY1MTEmdj0yJnNWPTEmRk9STT1NSVJFJnFwdnQ9MTYwMStraXJrd29vZCtoaWdod2F5&ntb=1

Deliverables:

• Master Project Plan (MPP) – Microsoft PowerPoint or PDF, baseline within 30 days of award; updated monthly; includes milestones, dependencies, resource plan, and critical path; accepted when dates/logic are consistent and achievable.

• Stakeholder Engagement Plan - PDF; due within 30 days; meeting cadences, roles/RACI, communications channels, escalation paths; accepted when all VA stakeholder groups are identified and engagement commitments scheduled.

• Risk, Issue, and Change Logs - Living spreadsheet or IT service agreement (ITSM) tool export; updated weekly; include probability/impact, owners, target dates, and mitigations; accepted when items have owners and dated actions.

• Status Reports (Monthly) - PDF, MS PowerPoint, or dashboard; schedule performance index (SPI), KPIs, accomplishments/next steps, risks/issues; accepted when variances >±10% include corrective actions.

• KPI Dashboard - Power BI; refreshed at least weekly; displays system uptime, accuracy, retrieval time, interface error rates; accepted when data sources are validated and thresholds codified.

5.0.1 SYSTEM DESIGN AND ARCHITECTURE:

The Contractor shall lead structured discovery activities—including interviews, workshops, and site assessments—to capture clinical workflows, patient movement patterns, staff response requirements, and compliance constraints related to elopement prevention. The Contractor shall conduct design reviews with VA stakeholders and document all decisions and resolutions. Using these inputs, the Contractor shall produce an end-to-end architecture for the PEW prevention platform, including:

o Coverage designs for zonal, room-level, and exit-point accuracy o Geofencing strategies for restricted areas o Capacity plans for tag and device density o Data models for patient profiles, alarm states, and location hierarchies Designs shall specify:

o Accuracy targets (≥99%) o Redundancy and failover strategies o Network and security baselines o Interoperability with VA systems (e.g. access control, fire alarms, elevators)

5.0.2 HARDWARE AND SERVER DESIGN DOCUMENTATION:

The Contractor shall develop and maintain a hardware and server design document for each site, updating it throughout implementation to reflect current design. The design document shall include:

o Proposed changes to VA-provided maps and Engineering Space Files o Hardware installation locations for monitors, chokepoints, and exit controllers o Draft server configuration and architecture optimized for facility needs, including:

Diagrams detailing server requirements

Expected WAN bandwidth utilization

Application latency considerations

Server specifications (power, thermal outputs, network connections)

Supported number of patient tags per server

The Contractor shall ensure all applications synchronize with internal VA site time standard. The synchronization of time on this network is critical in every aspect of managing, securing, planning, and debugging as it involves determining when an event occurred.

• Requirements Specification — PDF; due within 45 days; use-case narratives, non-functional requirements, constraints; accepted when traced to design and test cases.

• System Architecture Diagram — PDF; due within 60 days; logical/physical views, interfaces, data flows, security zones; accepted after VA review sign-off.

• Coverage Maps & Accuracy Models — Floor plans with reader/beacon placements; propagation models; accepted when modeled accuracy meets targets by area.

• Design Review Report — PDF; per review; comments, decisions, action items;

accepted when all critical actions have owners and due dates.

5.0.3 HARDWARE PROVISIONING:

The Contractor shall coordinate delivery schedules with VA stakeholders and obtain written or email concurrence from the Contracting Officer’s Representative (COR) prior to shipment. Upon delivery, the Contractor shall provide the COR with a signed Facility Receiving Report for each site, confirming the order and delivery of components, reconciling any discrepancies, and detailing delivery time, location, and the Government representative who received the shipment.

Categories Of Hardware to Be Provided

• System Components: include but not limited to patient protection tags, exit controllers for doors and elevators, low-frequency (LF) chokepoints for egress detection, patient safety bands with tamper/cut detection, location readers, gateways, and supporting infrastructure.

• Networking and Infrastructure: Cabling and any supplemental wireless hardware required for connectivity (FIPS-compliant).

• Server and Storage Hardware: As specified in the Hardware and Server Design Document (HSDD) for local or centralized processing, including capacity for real-time alerting and reporting.

5.0.4 SOFTWARE PROVISIONING:

The Contractor shall ensure that all software licenses are valid for the entire period of performance (PoP) and include rights for installation, configuration, integration, and ongoing support.

The Contractor shall coordinate with VA stakeholders to schedule software delivery and installation and obtain written or email concurrence from the Contracting Officer’s Representative (COR) prior to deployment. Upon installation, the Contractor shall provide the COR with a signed Software Provisioning Report for each site, confirming delivery, installation, and configuration details, as well as reconciliation of any discrepancies between planned and actual deployment.

CATEGORIES OF SOFTWARE TO BE PROVIDED:

• Application: patient protection platform, location engine, alert management, and device administration tools, and configuration tools for exit controllers and patient tags (if applicable).

• Integration Software: Connectors and APIs for interoperability with VA systems (e.g., elevators, physical access control, and fire alarm).

• Supporting Software: Database components, reporting modules, and analytics tools for alarm history, compliance tracking, and performance dashboards.

5.0.5 STAGING:

The Contractor shall manage delivery of approved hardware/software and accessories, preparing a detailed Bill of Materials (BoM) and delivery schedule aligned to installation waves. Staging shall include firmware standardization, configuration pre-loads, and quality checks. Interoperability validation (firmware compatibility, protocol settings) shall be performed prior to shipment to sites. The Contractor shall document serials, MACs, tag IDs, and association procedures to enable traceability.

• Delivery Schedule — PDF or PowerPoint view; delivery windows, critical dependencies; accepted when aligned to installation plan.

• Pre-Configuration Checklist — PDF; per batch; firmware versions, network settings, tag profiles; accepted when spot-checked devices meet baselines.

• Inventory & Serial Log — Spreadsheet; ongoing; serials/MACs/tag IDs, location, status; accepted when entries reconcile with shipment records.

5.0.6 HARDWARE INSTALLATION AND CONFIGURATION:

The Contractor shall perform complete installation and configuration of all hardware and software components. The Contractor shall ensure that all hardware installation and software configuration are performed strictly in accordance with the Original Equipment Manufacturer (OEM) standards and guidelines. This includes adherence to OEM and VA specifications for mounting, power, network connectivity, calibration, firmware versions, and software setup. The Contractor shall document compliance with these standards in the installation and configuration reports and provide evidence of OEM-approved methods for any deviations. Failure to meet manufacturer standards may result in rejection of work and require corrective action at no additional cost to the Government.

Specific tasks include:

PRE-INSTALLATION PREPARATION:

• Site Assessment — Conduct walkthroughs to identify installation points for readers, exciters, gateways, and beacons; validate power and network availability; and update facility maps with proposed hardware placement.

• Hardware Staging — Verify firmware versions for all devices, pre-configure network settings, and label/inventory all components.

PHYSICAL INSTALLATION:

The Contractor shall coordinate installation schedules with VA stakeholders, minimize clinical disruption, and provide written confirmation of completion.

5.0.7 SOFTWARE INSTALLATION AND CONFIGURATION:

Software configuration shall include deployment of PEW patient protection applications, along with any required integration components for alerting, reporting, and interoperability with VA enterprise systems. All installations shall comply with VA cybersecurity requirements, including FIPS-compliant encryption, and shall be documented with as-built diagrams and configuration baselines. In response to hardware design changes or VA reconfiguration requirements, the Contractor shall update rendered maps and zone configurations within the user interface (UI).

Configuration changes shall be defined during the site assessment at each facility.

PRE-INSTALLATION PREPARATION:

• Software Licensing and Validation: Verify valid licenses for application software;

ensure compliance with VA cybersecurity and FIPS requirements.

• Environment Readiness: Confirm server specifications, network connectivity, and database availability for hosting applications; validate compatibility with VA standard configurations (Windows® 10, Edge, etc.).

SOFTWARE INSTALLATION:

• Install PEW applications: Deploy location engine and alert management modules;

configure device communication and event processing, configure integration with exit controllers and patient tags.

• Deploy UI Components: Install web-based or server-hosted UI for monitoring and alarm management; ensure HTTPS and secure authentication mechanisms are enabled.

CONFIGURATION:

• Software Configuration: Define patient profiles, alarm rules, and location hierarchies;

calibrate IR and LF chokepoints for accurate egress detection, dashboards, alert routing, and geofencing zones; set up per-patient security profiles and transport overrides.

• Integration Configuration: Enable interoperability with VA systems (access control, fire alarms, and elevators); configure APIs and connectors for real-time data exchange.

• UI Configuration: Configure map views, alarm filters, and reporting templates; enable Power BI integration for analytics.

INTEGRATION:

• Data Synchronization: Ensure consistent alarm and location updates across platforms.

• API and Connector Setup: Configure secure APIs for real-time data exchange; test authentication and data integrity.

TESTING AND VALIDATION:

• Functional Testing: Verify UI features such as map rendering, alarm notifications, and reporting; confirm dashboards display accurate patient location and event data.

• Performance Testing: Validate system response times, data refresh intervals, and failover mechanisms.

5.0.8 USER INTERFACE PROVISIONING AND CONFIGURATION:

The proposed User Interface (UI) shall be a secure platform that provides comprehensive patient location monitoring and alarm management capabilities for elopement prevention. The Contractor shall integrate the UI across access controls, fire alarm systems, and elevator controls. At a minimum, the UI must allow users to view individual patient details—including tag ID, location, and alarm status—display facility layouts in both map and list views with search functionality by patient name or tag ID, and configure alarm rules for unauthorized egress, tamper detection, and transport overrides. The UI shall support exporting alarm and event data in Excel format, implementing customizable business rules, generating real-time alerts for elopement events, and producing reporting dashboards. Additionally, the UI must allow user-configurable refresh intervals, accurately reflect space changes and patient status updates, and stop sending location updates for discharged or deactivated patients.

5.0.9 SYSTEM ADMINISTRATION:

The Contractor shall provide Database and System Administration services during implementation and the warranty period, including periodic health checks on servers and databases, monitoring application logs, ensuring security compliance and remediation of vulnerabilities, applying monthly OS security patches from VA OIT, troubleshooting connectivity and server/application startup issues, and implementing software updates and upgrades.

5.0.10 PROFESSIONAL SERVICES HOURS:

The Contractor shall provide service hours as requested by the Government for tasks including system and software configuration and administration, ensuring hardware and software compliance with VA standards, implementing workflow solutions, project planning and management, and delivering analytics and business intelligence.

5.1 Acceptance testing:

The Contractor shall develop an Acceptance Test Plan and obtain VA approval prior to execution. Testing will occur in two phases.

5.1.1 PHASE 1: PERFORMANCE TESTING

The Contractor shall validate system functionality and confirm room-level location accuracy of at least 99%. Testing must ensure compliance with all specifications and verify that no interference occurs with other facility devices. The Contractor shall provide VA with the performance test methodology and results. If the system does not meet requirements, the Contractor shall submit a Facility Remediation Hardware Report detailing additional hardware, software, or services needed. A Final Hardware Deployment Document shall also be provided, listing all installed hardware with unique identifiers and exact locations.

5.1.2 PHASE 2: USER ACCEPTANCE TESTING

The Contractor shall schedule user acceptance testing with 30 days’ notice and provide qualified personnel to assist VA during the process. The COR shall be responsible for the test methodology, and the Contractor shall deliver the results. A Facility Acceptance Test Report shall be submitted in Excel format, showing tag IDs, locations, and whether accuracy requirements were met.

• Performance Test Plan & Results - PDF; includes test steps, accuracy verification, and interference checks; accepted when results meet ≥95% of the requirements.

• Facility Remediation Hardware Report - PDF; lists additional hardware/software/services required for compliance; accepted when all remediation items are documented.

• Final Hardware Deployment Document - PDF and Excel; floor map layout and table of installed hardware with IDs and locations; accepted when reconciled with design documents.

• User Acceptance Test (UAT) Plan - PDF; outlines UAT process, roles, and schedule; accepted when approved by VA and Contractor before testing.

• Facility Acceptance Test Report - Excel; provides tag IDs, locations, and accuracy ratings; accepted when accuracy metrics are clearly reported and validated.

5.1.3 TRANSITION PLANNING:

The Contractor shall prepare a comprehensive Transition Plan to transfer all operational responsibilities for patient elopement prevention systems to VA staff by the end of the contract. The plan must include detailed procedures for hardware management, software configuration, ongoing maintenance, and system administration, organized in a

RACI matrix to clearly define roles and responsibilities. The Contractor shall execute the approved transition plan and provide complete User and Technical Manuals for all PEW system components, including troubleshooting guides, diagnostic tools, and parts lists.

Each facility shall receive two copies of operator manuals and two copies of technical service manuals to ensure continuity of operations and support after contract completion.

• Transition Plan — PDF; details step-by-step transition procedures and RACI matrix; accepted when reviewed and approved by VA.

• User and Technical Manuals — PDF; includes operating instructions, troubleshooting guides, and parts lists; accepted when complete and facility-specific.

5.1.4 TRAINING REQUIREMENTS:

The Contractor shall develop a comprehensive Training Plan and deliver on-site or remote sessions for both technical and non-technical users, including nursing staff, Behavioral Health clinicians, Biomedical Engineering personnel, security teams, and system administrators. The Training Plan must outline schedules, delivery methods, audience profiles, and instructor qualifications. Training shall cover system operation, alarm response workflows, patient tag management, and troubleshooting procedures to ensure staff can effectively prevent and respond to elopement events. Each session shall be documented with attendee lists and completed according to the approved plan, ensuring compliance with VA standards and readiness for go-live.

Training Deliverables:

• Training Plan — PDF; outlines training objectives, schedule, and delivery method;

accepted when approved by VA.

• Training Material and Schedules — PDF; includes content and timing for each session; accepted when aligned with the Training Plan.

• List of Attendees — Excel or PDF; records participants and trainer details; accepted when complete and facility-specific.

5.1.5 WARRANTY SERVICES:

All hardware, software, and services provided under this contract shall include a one-year manufacturer’s warranty covering parts, labor, and technical support for PEW prevention systems. During the warranty period, the Contractor shall provide maintenance and technical assistance, oversee any subcontractor support, and offer extended warranty options upon VA request. The Contractor shall maintain and submit a Warranty Status Report detailing all system components, specifications, and warranty expiration dates. Additionally, the Contractor shall ensure help desk support responds within two hours of initial contact and that any required on-site service is completed within 10 business days to minimize disruption to patient safety operations.

Warranty Deliverable:

• Warranty Status Report — PDF; lists hardware/software specifications and warranty expiration dates; accepted when accurate and reconciled with deployment records.

Evaluation Factors Proposals will be evaluated in accordance with the Evaluation Factors identified below.

Evaluation Factor 1 – Past Performance

Evaluation Factor 2 – Integration & Interoperability

Evaluation Factor 3 – Price

Technical Factors are equal and when combined are significantly more important than Price.

As demonstrated in their proposals, Offerors shall be evaluated in terms of the Offeror’s ability to meet or exceed the project’s requirements as identified in the PWS, and those proposals demonstrating an ability to exceed specified requirements may be rated higher in those areas than proposals demonstrating only the ability to meet requirements. Offerors are reminded to include their best technical and price terms in their initial offer and not automatically assume that they will have an opportunity to participate in discussions or be asked to submit a revised offer. The Government intends to make award to a responsible Offeror submitting a conforming proposal without discussion, if deemed to be in the best interest of the Government. The Government may use corporate knowledge on past and present projects, when evaluating proposals.

Past Performance:

• The Government will evaluate the degree of successful completion of the recent and relevant past performance identified in the proposal, Prime Contractor past performance along with the designated team of subcontractors. Documentation of satisfactory performance of projects similar in size, scope, and dollar value will be considered to have met the minimum requirements of the RFP. Projects that are not determined similar in size, scope and dollar value may not be considered. The Government reserves the right to check any or all cited references to verify supplied information and to assess owner satisfaction as to quality, schedule, cost and management. The Government may use knowledge on past and present projects, when evaluating proposals.

• Past performance is either relevant or non-relevant to the Project. Evaluations may include past performance information regarding predecessor companies, key personnel who have relevant experience or subcontractors that will perform major or critical aspects of the requirement. Offerors without a record of relevant past performance or for whom information on past performance is not available may not be evaluated favorably or unfavorably on past performance and shall receive a neutral rating for Past Performance. Offerors may provide information on problems encountered on the identified contracts and the corrective action taken, if desired.

• The Government may also use other tools including but not limited to CPARS/PPIRS Vet Biz, Dunn & Bradstreet, and Federal Awardee Performance and Integrity Information System (FAPIIS) to gather documentation on past performance.

• Include customer’s point of contact (name, title, and phone number).

• The Government may use corporate knowledge on present and past projects, when evaluating this factor.

Integration & Interoperability:

• The Government will evaluate the proposed system’s demonstrated capability to integrate and exchange data in real-time with physical access controls, fire alarm, elevator controls and other relevant hospital platforms, enabling unified and reliable alerts and workflow coordination across the healthcare environment. The system’s proven and consistently validated ability to deliver ≥99% patient location accuracy at the room level, with comprehensive coverage of required facility areas as confirmed through on-site operational testing.

• Provide a clear, concise narrative not to exceed 10 pages (front and back side use of a single page will count as 2 pages). Company advertising literature shall not be included. The contractor is advised to note in each of these subfactors any elements or aspects exceeding the RFP requirements or betterments provided, including an explanation of how each element or aspect improves upon the basic requirements and how it would benefit the VA.

A.2 PRICE/COST SCHEDULE

ITEM INFORMATION

ITEM

NUMBE

R

DESCRIPTION OF

SUPPLIES/SERVI

CES

QUANTI

TY

UNI

T UNIT PRICE AMOUNT

1.00 JB _______________

CLC and Fourth Floor Patient Elopement System PRINCIPAL NAICS CODE: 541519- Other Computer Related Services PRODUCT/SERVICE CODE: 7A21- IT and Telecom- Business Application Software (Perpetual License Software)

GRAND TOTAL _______________

A.3 DELIVERY SCHEDULE

ITEM

NUMBER SHIPPING INFORMATION QUANTITY

DELIVERY

DATE

0001 SHIP TO: Wilmington VA Medical Center 1601 Kirkwood Highway Wilmington, DE 19805 4917

USA

1.00 145 days from award

ADDITIONAL SIMPLIFIED ACQUISITION TERMS AND CONDITIONS

A.4 52.212-2 EVALUATION—COMMERCIAL PRODUCTS AND

COMMERCIAL SERVICES (NOV 2021) (DEVIATION OCT 2025)

(a) Evaluation factors. The Government will award a contract resulting from this solicitation to the responsible Offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The following factors will be used to evaluate offers: See Evaluation Factors Section of document.

Evaluation factors other than price when combined are significantly more important than price.

(b) Options (if applicable). The Government will evaluate offers for award purposes by adding the total price for all options to the total price for the basic requirement. The Government may determine that an offer is unacceptable if the option prices are significantly unbalanced. The evaluation of options does not obligate the Government to exercise the option(s).

(c) Notice of award. A written notice of award or acceptance of an offer furnished to the successful Offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer’s specified expiration time, the Government may accept an offer (or part of an offer), whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.

(End of Provision)

A.5 52.216-1 TYPE OF CONTRACT (NOV 2025) (DEVIATION)

The Government contemplates award of a Firm-Fixed-Price contract resulting from this solicitation.

(End of Provision)

A.6 52.219-1 SMALL BUSINESS PROGRAM REPRESENTATIONS (NOV

2025) (DEVIATION)

(a) Definitions. As used in this provision-

Economically disadvantaged women-owned small business (EDWOSB) concern means a small business concern that is at least 51 percent directly and unconditionally owned by, and the management and daily business operations of which are controlled by, one or more women who are citizens of the United States and who are economically disadvantaged in accordance with 13 CFR part 127, and the concern is certified by SBA or an approved third-party certifier in accordance with 13 CFR 127.300. It automatically qualifies as a women-owned small business concern eligible under the WOSB Program.

HUBZone small business concern means a small business concern that meets the requirements described in 13 CFR 126.200, is certified by the Small Business Administration (SBA) and designated by SBA as a HUBZone small business concern in the Small Business Search (SBS) (13 CFR 126.103).

Service-disabled veteran-owned small business (SDVOSB) concern eligible under the SDVOSB Program means an SDVOSB concern that is designated in the System for Award Management (SAM) as certified by the Small Business Administration (SBA) in accordance with

13 CFR 128.300.

Small business concern—

(1) Means a concern, including its affiliates, that is independently owned and operated, not dominant in its field of operation, and qualified as a small business under the criteria in 13 CFR part 121 and the size standard in paragraph (b) of this provision.

(2) Affiliates, as used in this definition, means business concerns, one of whom directly or indirectly controls or has the power to control the others, or a third party or parties control or have the power to control the others. In determining whether affiliation exists, consideration is given to all appropriate factors including common ownership, common management, and contractual relationships. SBA determines affiliation based on the factors set forth at 13 CFR 121.103.

Small disadvantaged business concern, means a small business concern that-

(1) Is at least 51 percent unconditionally and directly owned (as defined at 13 CFR 124.105) by one or more socially disadvantaged (as defined at 13 CFR 124.103) and economically disadvantaged (as defined at 13 CFR 124.104) individuals who are citizens of the United States, and

(2) The management and daily business operations of which are controlled (as defined at 13 CFR 124.106) by individuals who meet the criteria in paragraph (1) of this definition.

Women-owned small business (WOSB) concern eligible under the WOSB Program (in accordance with 13 CFR part 127) means a small business concern that is at least 51 percent directly and unconditionally owned by, and the management and daily business operations of which are controlled by, one or more women who are citizens of the United States, and the concern is certified by SBA or an approved third-party certifier in accordance with 13 CFR 127.300.

(b)(1) The North American Industry Classification System (NAICS) code for this acquisition is 541519.

(2) The small business size standard is 800 Employees.

(3) The small business size standard for a concern that submits an offer, other than on a construction or service acquisition, but proposes to furnish an end item that it did not itself manufacture, process, or produce (i.e., nonmanufacturer), is 500 employees, or 150 employees for information technology value-added resellers under NAICS code 541519, if the acquisition—

(i) Is set aside for small business and has a value above the simplified acquisition threshold;

(ii) Uses the HUBZone price evaluation preference regardless of dollar value, unless the offeror waives the price evaluation preference; or

(iii) Is an 8(a), HUBZone, service-disabled veteran-owned, economically disadvantaged women-owned, or women-owned small business set-aside or sole-source award regardless of dollar value.

(c) Representations.

(1) The offeror represents as part of its offer that—

(i) It [ ] is, [ ] is not a small business concern; or

(ii) It [ ] is, [ ] is not a small business joint venture that complies with the requirements of 13 CFR 121.103(h) and 13 CFR 125.8(a) and (b). [The offeror shall enter the name and unique entity identifier of each party to the joint venture: _________________.]

(2) [Complete only if the offeror represented itself as a small business concern in paragraph (c)(1) of this provision.] The offeror represents that it [ ] is, [ ] is not, a women-owned small disadvantaged business concern.

(3) Women-owned small business (WOSB) joint venture eligible under the WOSB Program.

The offeror represents as part of its offer that it [ ] is, [ ] is not a joint venture that complies with the requirements of 13 CFR 127.506(a) through (c). [The offeror shall enter the name and unique entity identifier of each party to the joint venture: _________________.]

(4) Economically disadvantaged women-owned small business (EDWOSB) joint venture. The offeror represents as part of its offer that it [ ] is, [ ] is not a joint venture that complies with the requirements of 13 CFR 127.506(a) through (c). [The offeror shall enter the name and unique entity identifier of each party to the joint venture: _________________.]

(5) SDVOSB joint venture eligible under the SDVOSB Program. [Complete only if the offeror is certified as a SDVOSB concern.] The offeror represents as part of its offer that it [ ] is, [ ] is not a SDVOSB joint venture eligible under the SDVOSB Program that complies with the requirements of 13 CFR 128.402. [The offeror shall enter the name and unique entity identifier of each party to the joint venture: _________________.]

(6) HUBZone joint venture eligible under the HUBZone Program. [Complete only if the offeror is a HUBZone small business concern.] The offeror represents, as part of its offer, that it [ ] is, [ ] is not a HUBZone joint venture that complies with the requirements of 13 CFR 126.616(a) through (c). [The offeror shall enter the name and unique entity identifier of each party to the joint venture: _________________.] Each HUBZone small business concern participating in the HUBZone joint venture must be certified as a HUBZone concern.

(d) Notice.

Under 15 U.S.C. 645(d), any person who misrepresents a firm's status as a business concern that is small, HUBZone small, small disadvantaged, service-disabled veteran-owned small, economically disadvantaged women-owned small, or women-owned small eligible under the

WOSB Program in order to obtain a contract to be awarded under the preference programs established pursuant to section 8, 9, 15, 31, and 36 of the Small Business Act or any other provision of Federal law that specifically references section 8(d) for a definition of program eligibility, will be—

(1) Punished by imposition of fine, imprisonment, or both;

(2) Subject to administrative remedies, including suspension and debarment; and

(3) Ineligible for participation in programs conducted under the authority of the Act.

(End of Provision)

A.7 52.233-2 SERVICE OF PROTEST (SEP 2006) (DEVIATION NOV 2025)

(a) Protests, (as defined in FAR 33.102), that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), must be served on the Contracting Officer identified in the solicitation by obtaining written and dated acknowledgment of receipt from them.

(b) The copy of any protest must be received in the office designated above within one day of filing a protest with the GAO.

(End of Provision)

A.8 52.222-90 ADDRESSING DEI DISCRIMINATION BY FEDERAL

CONTRACTORS (DEVIATION APR 2026)

(a)Definitions. As used in this clause—

Program participation means membership or participation in, or access or admission to:

training, mentoring, or leadership development programs; educational opportunities; clubs;

associations; or similar opportunities that are sponsored or established by the contractor or subcontractor.

Racially discriminatory diversity,…