This is a service / maintenance or supply contract in Fort Worth, Texas. Contact the soliciting agency for additional information.

The District is requesting proposals from qualified vendors to modernize and expand its physical security infrastructure to better support patient safety, regulatory compliance, and operational efficiency across all care environments. This initiative includes upgrading security hardware and software components to support hybrid-cloud architecture, centralized management, and integration with existing or future on-premise or cloud-based platforms. The proposed solution should provide a unified security platform capable of integrating access control, video surveillance, intercom, and intrusion detection into a single software interface. The system must support multi-site healthcare environments with centralized monitoring, role-based access control, and real-time event workflows. The desired solutions must be scalable for enterprise level organizations, non-proprietary, and provide an open architecture for interoperability with both existing security hardware (readers, cabling, cameras) and other JPS systems such as Elevator Control, Nurse Call, Visitor Management, Infant Protection, Staff Safety and Asset Management. The existing access control software presents limitations that hinder the organization's ability to effectively manage and maintain the broader security infrastructure. Key challenges include the complexity of configuring and administering cardholder access levels and group assignments. Furthermore, the system cannot accommodate the expanded digit requirements for employee IDs and keypad PIN codes, exceeding its current capacity. And finally, the current solution provides limited opportunities to support JPS initiatives for cloud-based solutions and integrations with both existing and future ancillary systems. JPS Health designates Infor CloudSuite as the authoritative System of Record for employee workforce identity, employment status, job role, department, and primary work location. Epic shall be treated as a read-only clinical context system and shall not be used as an identity authority. Epic data may be leveraged only to inform clinical area sensitivity, safety controls, and access context, without replication of patient or workforce master data. The proposed solution shall not duplicate or replace HR or clinical master data and must instead integrate via API or event-driven mechanisms.