IP Based Public Address, Intercom and Bell Systems

The Vendor is required to provide IP based public address, intercom and bell systems system shall clear and intelligible audio coverage in all areas of each campus, including but not limited to classrooms, hallways, offices, front office area, cafeteria, gymnasiums, library, interior and exterior gathering areas, and other instructional or operational spaces as required.
- Solution shall include all required headend equipment, servers or appliances, software, licensing, amplifiers, controllers, digital signal processor, paging stations, speakers, mounts, back boxes, cables, terminations, accessories, labeling, configuration, testing, commissioning, documentation, and training required for a complete and functional installation.
- System requirements
1. General requirements
•    The system shall be fully IP based and designed for operation in a k-12 environment. 
•    The system shall provide even, clear, and intelligible audio coverage throughout. 
•    The system shall support call paging, group paging, zone paging, and targeted paging.
•    The system shall support live paging, prerecorded announcements, scheduled tones, scheduled bells, and emergency notification functions. 
•    The system shall be scalable for additions, building modifications, and zone expansion. 
•    The system shall be designed for long-term supportability, maintainability, and ease of use and administration.
2. Headend, server and software requirements
•    The system headend shall include all required controllers, amplifiers, software, licenses, and related hardware required for a complete and fully operational installation. 
•    Identify whether the proposed system uses: a. A physical server or appliance located in an equipment cabinet, or b. A virtual machine hosted in the district’s server environment. 
•    Identify any virtual server option and provide all server, storage, operating system, database, and hypervisor requirements. 
•    Virtual deployment is preferred, as district current server environment is primarily virtualized and runs on VMware vSphere. 
•    Indicate whether their proposed solution is supported in a VMware vSphere environment and note any limitations or special requirements. 
•    Identify all required software, subscriptions, user licensing, feature licensing, and support licensing. 
•    Identify required third-party software or operating system dependencies.
3. Integration and networking
•    The system shall support integration with the district’s current fort voice phone system for paging and announcements, including sip or other supported integration methods. 
•    Clearly describe the level of fort voice integration proposed, required licenses, gateways, hardware, and any limitations. 
•    The system shall support current bell scheduling needs and provide flexibility for future clock and bell integration or replacement. 
•    The district is interested in possible future integration with a fire alarm and emergency notification system, if available through the proposed platform. 
•    Any available interface options, required hardware, software, licensing, programming, code limitations, AHJ considerations, and whether such integration is native, third-party, or future capable only. 
•    This should be line itemed separately in the pricing page. 
•    Identify all network requirements, including bandwidth considerations, switch requirements, VLAN recommendations, QOS recommendations, POE requirements, and any multicast or broadcast considerations. 
•    SIP/VoIP PBX compatibility and clock/bell integration.