Addendum 1 Q and A

Description

RFP 26-022 Mass Communications System Question and Answer Addendum 1 1. Quantity of InformaCast Mobile App Users (this will probably be admin/campus security) Approximately 20. 2. Quantity of SMS recipients (this can be the number if all staff/students opt in to notifications, or a best-case estimate of the recipients they’d like to see opt in) ATU it opt out. All members of the community are automatically enrolled into mass notifications. From semester to semester this number changes, but is generally around 10,000. 3. Quantity of Campus PCs or ATU-provided laptops to receive desktop notifications 1599 online desktops at the moment. 4510 total devices, but some may be stale, so the count may be lower. 4. Current PA/horn hardware (IP or analog equipment?) We do not have PA/horn hardware. A. Operational Scope & Campus Environment A.1 Please confirm whether the scope of this RFP includes only the Russellville campus or also includes the Ozark campus and any additional satellite or online locations. It does include the Ozark campus as well as ATCC and other Ozark satellite locations. A.2 Approximately how many students, faculty, staff, and affiliated users are expected to receive notifications under the proposed system? 10,000 A.3 Does ATU envision the platform serving primarily as a mass notification tool, or also as a coordinated incident-response platform supporting real-time operational communication, alert verification/escalation workflows, and collaboration between administrators, campus police, and/or first responders during active events? Mass notification. A.4 Approximately how many administrative users will require system access for alert initiation, approval, or incident management? 10 B. Technical Environment & Integrations B.1 Section 6.1 references ALERTUS beacons and digital signage integration. Please confirm whether an ALERTUS system is currently deployed on campus and whether integration with ALERTUS specifically is required, or whether equivalent integrations via API/CAP-compatible platforms would satisfy the Requirement. Alertus is currently deployed. B.2 Section 6.3 references Student Information System synchronization. Please confirm: a) Current SIS platform/vendor Ellucian Banner b) Preferred integration method (API, SFTP, or other) SFTP file upload preferred, API could be supported c) Desired synchronization frequency Nightly B.3 Section 6.1 references desktop alerting capabilities.