2-Addenda 1 RFI 003-27 Temple ISD Cloud Calling Unified Communications.pdf
PDF 170 KB Posted
- Solicitation number
- RFI-003-27
- Issued by
- Bell County, Texas
About this file
This is Addendum #1 to a Request for Information (RFI-003-27) issued by Temple Independent School District (TISD) in Texas for a cloud-hosted Unified Communications as a Service (UCaaS) solution. The District is seeking to replace its existing on-premises Cisco Unified Communications Manager (CUCM), Cisco Unity, and Cisco Emergency Responder systems across approximately 18 facilities serving 8,800 students and 1,500 employees. The project requires approximately 1,000 voice endpoints, consisting of 1,000 standard phones (approximately 600 classroom phones and 300-400 administrative phones), 18 receptionist phones with 18 sidecars, and 3 analog telephone adapter (ATA) ports for fax and elevator connections. The addendum confirms that vendors can propose either new hardware or reuse existing Cisco 7800 series phones based on cost-effectiveness. Additional requirements include porting 3,700 DIDs (1,500 currently active), 15 fax numbers to eFax service, potential onsite technician support for up to 1,000 phones, and a turnkey solution encompassing implementation, project management, number porting, system configuration, end-user training, cutover support, and post-deployment services. The implementation timeline is 12 to 18 months with a "Go Live" date to be determined in a future Request for Proposal (RFP). TISD indicated it is in early stages but needs to finalize a solution within the year.
The District currently maintains 3,700 total DIDs with last-mile resiliency but no multiple internet service providers, and may be interested in survivability solutions across 2 data centers and 18 sites, though not currently required. Temple ISD is open to any UCaaS platform and has no preference between Yealink and Poly phones; the vendor should quote phones only if replacement is necessary. TISD's current phone service provider is Cisco, under contract until May 2027, with detailed cost information to be provided during the formal RFP phase. The District does not require call recording, call queue live reporting, headsets, paging integration, or specialized requirements for common areas and emergency locations. No softphone licenses are currently in place, though the District may explore softphone capabilities at a later date. All vendors submitting proposals must sign and return this addendum acknowledging they have reviewed Addendum #1.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 3-Addenda 2 RFI 003-27 Temple ISD Cloud Calling Unified Communications.docx | DOCX document | |
| 1-Temple ISD Cloud Calling RFI 003-27.pdf |
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
P a g e 1 | 5
August 24, 2026 Addendum #1: RFI-003-27 Temple ISD Cloud Calling & Unified Communications.
Q). What is the current model of phones?
A). The current model of phones are Cisco 7800 series.
Q). Are you asking for new hardware or wanting to repurpose existing Phones?
A). We are looking at whichever option is the most cost effective.
Q). How many lines are for end users?
A). 1000
Q). How many lines are for common area devices (breakrooms, conference rooms, etc.)?
A). all lines are treated the same.
Q). How many call queues will be necessary?
A). We don’t really rely on call queue.
Q). How many total DIDs are in current inventory? How many are active, and how many will be reserved? What quantity will need to be ported over?
A). 3700, 1500 active, all ported for now.
Q). Will you need new phones? Can you provide how many phones will be needed by user type?
a) Common Area device (breakroom) A) 0
b) Knowledge Worker A). 1000
c) Receptionist A). 18
d) Sidecars for Receptionist phones A). 18
e) Conference Phone A). 0
f) Executive Phone A). 0
g) WIFI enabled phones by type A). 0
Q). If new phones must be purchased, do you have a preference between Yealink and Poly?
A). No preference between Yealink and Poly.
Q). Do you have multiple internet service providers in your data center? Do you have last mile resiliency?
A). No, we do not have multiple internet service providers, and yes, we have last mile resiliency.
Q). Do you do any paging? If so - what manufacturer and model of your paging system does the proposed solution need to integrate with? How many total paging systems are required?
A). No, we do not do any paging.
Q). How many total ATA ports are required? (fax machines, elevators, etc). Can you give a breakdown of ATA ports by location so we can properly scope the ATA models and quantities.
A). Total ATA ports required is 3.
Q). How many total Fax numbers will need to be ported to an eFax service? Do your Fax services require HIPAA compliance?
A). The total number of Fax numbers is 15.
Q). Do you require survivability at your data center(s)? Or do you require local survivability at each location? If at each location provide the total location count.
A). Not required but may be interested 2 data centers and 18 sites.
Q). How many users will need Call Queue live reporting for time in queue, abandoned calls, overflowed to VM. The proposed solution supports historical reporting without additional licensing.
A). We will have no users requiring call Queue.
Q). Do you want headsets quoted? If so how many wireless and how many wired?
A). No, we will not want headsets quoted.
Q). Do you require onsite services (Boots on the Ground) for hardware setup, ATA, desk phones? If so, do you have potential number of phones and hardware to be deploy with onsite technicians to help ensure accurate pricing?
A). Not required but may be interested. 1000
Q). What is the potential timeframe to start the implementation and when would you potentially like to have it be completed? What is the anticipated “Go Live” date?
A). The implementation timeline is 12 to 18 months with "Go Live" date to be determined and outlined in future Request for Proposal.
Q). What integrations will be required for the new VoIP system?
A). Faxing will be required.
Q). Since TISD is looking to replace Cisco CUCM, Cisco Unity, and Cisco Emergency Responder, I would like to better understand a few requirements before recommending the right our solution:
Which UCaaS platforms are currently being considered?
A). We are open to any.
Q). Of the approximately 1,000 endpoints, what is the breakdown between standard phones, common-area phones, conference phones, DECT, analog devices, etc.?
A). All standard phones
Q). Are all 1,000 endpoints expected to be replaced?
A). Would like to utilize current equipment when possible.
Q). What are the key E911 / emergency calling requirements across the 18 facilities?
A). 911 from phone must report where ethe call is originating from
Q). Are paging, intercom, classroom phones, emergency phones, or other analog devices currently connected to the Cisco system?
A). Maybe 2 elevators
Q). Will TISD keep the existing Grande/Astound SIP service, or will PSTN service be provided by the new UCaaS provider?
A). Will depend on value.
Q). Are there any specific required features?
A). None other than what's listed.
Q). What is the expected timeline for the RFI, RFP, vendor selection, and deployment?
A). We are in the early stages but will need to finalize a solution within the year.
Q). Who is your current telephone service provider?
A). Cisco
Q). Are you under contract for the phone service? If so, when does it expire?
A). yes May 2027
Q). What is your monthly cost for the phone service?
A). This information will be provided once this RFI moves to a formal Request for proposal.
Q). Are you under a maintenance contract for the Cisco phone system? If so, what is your annual cost?
A). This information will be provided once this RFI moves to a formal Request for proposal.
Q). Can you provide a detailed inventory of the type of phones instruments and quantities you are considering (classroom phones, common area phones, administrators phones, conference phones, etc).
A) 7800 series cisco phones approximately 1000 total between 7821, 7841, 7861
Q). Are there any analog lines, fax machines or any other device that requires an analog port connected to the current Cisco phone system? If so, how many and where are they located?
A). Yes, a total of 3.
Q). How many DID do you want to port into the new cloud system?
A). 3700
Q). Do you require call recording? If so, for what percentage of users and for how long must recordings be retained?
A). No
Q). Is the current phone system connected to the paging system at each campus? If so, how is it connected and what brand is the paging system?
A). No
Q). Are there any integrations required for the new VoIP system to 3rd party systems and data?
A). No other than 911
Q). What is your timeframe for implementation?
A).12 – 18 months
Q). Please provide an estimate on the number of administrative/office staff users (heavy phone users) verses classroom/common area phones.
A). 1000 total, 600 classroom, 300-400 admin.
Q). Regarding FERPA compliance, can you specify which categories of student information must be protected within the proposed communications environment? This is related to student data which we do not collect, so we want to understand any specific details related to the question.
A). If you do not collect student data, then we are in compliance.
Q). Are there any specific requirements for data retention, call recording, access controls, or information governance related to district-owned records versus student-associated information?
A). Currently we have a 30-call log. Other than that, there shouldn’t be student information unless with in a voicemail which would need to be secure.
Q). Please provide the total number of physical telephone devices required and break out the quantities by administrative staff and classroom users.
A). 1000 total, maybe 300-400 administrative staff if including everyone outside of teachers.
Q). Please provide the total number of softphone licenses required and break out the quantities by administrative staff and classroom users.
A). We do not currently have softphone licenses. May look into softphone capabilities for all or some. That will be determined later.
Q). Are there any specialized phone requirements for common areas, front offices, cafeterias, nurse stations, security personnel, or emergency response locations?
A). no.
Q). Please clarify the professional services expected as part of the project scope.
Should the proposal include implementation, project management, number porting, system configuration, end-user training, cutover support, and post-deployment support services?
A). Yes, looking for turn key solution
Q). Are there any specific integration requirements with existing systems, such as paging, bell scheduling, emergency notification platforms, door access systems, or other district applications?
A). no
All other terms, conditions, and requirements of the original RFI remain the same.
Please sign and upload this document with your proposal.
Signatures: By signing this document, I agree that I have read and reviewed Addendum #1 RFI 001-27 Temple ISD Cloud Calling & Unified Communications
Name of Company: _____________________________________________
Representative Name: ___________________________________________
Signature: _____________________________________________________
Date________________________
File details come from the government source that posted it. Updated .