3-Addenda 2 RFI 003-27 Temple ISD Cloud Calling Unified Communications.docx

DOCX document 81 KB Posted

Attached to
Temple ISD Cloud Calling & Unified Communications
Solicitation number
RFI-003-27
Issued by
Bell County, Texas

About this file

This is Addendum #2 to a Request for Information (RFI-003-27) issued by Temple Independent School District in Texas regarding the procurement of a cloud-hosted Unified Communications as a Service (UCaaS) solution. The District seeks to replace its existing on-premises Cisco Unified Communications Manager, Cisco Unity, and Cisco Emergency Responder infrastructure with a fully cloud-based platform to serve approximately 1,000 voice endpoints across 18 district facilities supporting 1,500 employees and 8,800 students. The addendum clarifies specifications and pricing methodology through vendor Q&A responses and confirms a district-wide implementation targeted for completion by March 2028, with physical endpoint deployment and configuration to be performed by the vendor and cutover scheduled during after-hours windows to minimize operational disruption.

Pricing shall be submitted on an individual line-item basis with total costs for the full five-year term, including separate quotes for five-year subscription, licensing-only, and licensing-with-new-IP-phones options; all pricing should assume 1,000 users and basic-tier endpoint hardware. The District currently operates 10 gigabit redundant internet connectivity at two sites through Grande/Astound SIP services and UPN WAN infrastructure with Meraki MX 250 switching and Power over Ethernet support. Professional services costs must be quoted as a turnkey fixed price separate from licensing and subscription fees, with the District responsible for providing dispatchable-location mapping data and user identity provisioning through Microsoft Entra ID but the vendor responsible for physical placement, configuration, number porting, and deployment of three analog gateways for elevator phones. The RFI emphasizes that responses are informational only and do not obligate the District to proceed with a subsequent formal solicitation, and vendors should provide recommendations on carrier strategy, contract terms, and AI/analytics capabilities where District preferences have not been finalized.

View the file

Other files

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

August 24, 2026 Addendum #2: RFI-003-27 Temple ISD Cloud Calling & Unified Communications.

Q). We are curious about more details related to this capability. Can you be more specific on your Internet and WAN design? Do you have multiple Internet connections at multiple locations? Is the WAN a hub and spoke or other design with single or multiple connections. Are you looking for a gateway at each school with an alternate Internet connection?

A). Gateway at each school in case a school goes offline.

Q). Can you be more specific on the desire for emergency callback. Are you specifically wanting the 911 operator to be able to callback the 911 caller or something different?

A). Yes, 911 operator to be able to callback the 911 caller.

Q). Are you asking if the UCaaS Service Provider provides annual penetration testing on their environment or are you asking for annual penetration testing on the Temple ISD network?

A). Provider

Q). How much detail do you desire for each comment in the specification’s spreadsheet. Is a yes/no sufficient or are you looking for a detailed response for each question?

A). yes/no will be fine.

Q). What quantity of users should we use for cost purposes? 1000 users?

A). Yes

Q). For License only pricing, what term should we quote?

A). 5 years

Q). Do you desire all pricing line items quoted? Five-Year subscription, License only, and Licensing with new IP phones?

A). yes

Q). For Licensing with new IP phones, how many phones should be quoted? Do you want the same kind of phone, or a basic classroom phone and a more capable admin phone? How many of each?

A). 1000

Q). For analog gateways, would you like a cost for 1 single port ATA or multiple port ATAs. How many of each or how many analog ports do you have at each site.

A). single, 3 different sites

Q). The RFI's confirmation/acknowledgment sheet (page 5) lists the response due date as “September 3, 2020,” while the cover page lists “September 3, 2026.” Please confirm the correct year.

A). 2026

Q). Please provide a per-site breakdown of the ~18 facilities (endpoint count, analog/fax/paging device count, and network closet/IDF details) so vendors can size a bill of materials and dispatchable-location mapping accurately.

A). I believe enough information has been provided to solicit information about the offered solution.

Q). Of the ~1,000 voice endpoints, how many require new physical IP desk phones vs. softphone-only users, and is there a preferred handset model or tier (basic, mid, conference-room)?

A). all basic phones

Q). What is the current WAN/internet circuit bandwidths and QoS configuration at each site (the RFI references UPN WAN and Grande/Astound SIP, but not capacity), and is SD-WAN in place to support cloud voice?

A). 10GB

Q). How many active DIDs/telephone numbers require porting, who is the current SIP trunk/PSTN provider of record, and what is that contract's term or exit date?

A). Astound\ ports previously answered.

Q). How many analog devices (fax machines, elevator/emergency phones, clock/paging/intercom systems referenced under NIGP code 838-35) require gateway support, and is paging/intercom/clock integration in scope for this UCaaS replacement or handled separately?

A). 3 elevators

Q). Approximately how many users/roles require call recording (Item 48), and is recording driven by a specific compliance need (e.g., front office, special education, or business office lines)?

A). none

Q). What identity provider is currently in use district-wide (Microsoft Entra ID, Google Workspace, or other), since this affects the recommended SSO integration path?

A). Microsoft Entra

Q). Is a phased, per-campus cutover preferred over a single district-wide cutover, and is there a target project completion date or budget appropriation window?

A). District, March 2028

Q). Please clarify how the district would like proposal priced, price sheet has quality one of each item.

A). There may be a bid process to follow so do what's best for the RFI.

Q). Should the respondent provide a lump sum or individual pricing?

A). individual

Q). Question Set 5 mentions a complete bill of materials should this include detailed pricing as well?

A). not for the RFI Q). What versions of Cisco Unified Communications Manager, Cisco Unity Connection, and Cisco Emergency Responder are currently deployed?

A). 12.5

Q). Please provide the model, approximate quantity, and firmware version of the Cisco phones currently in use.

A). Previously answered.

Q). Does the District expect existing Cisco phones to be reused, or should respondents assume that all physical phones will be replaced?

A). Previously answered.

Q). Does the District have current documentation of its dialing plan, call flows, auto attendants, hunt groups, call queues, shared lines, and emergency-routing configuration?

A). no

Q). For future planning, should respondents assume that the District will provide existing call-flow documentation, or that discovery and documentation services will be required?

A). yes

Q). Does the District intend to replicate its current calling configuration, or is it open to redesigned cloud-based workflows and capabilities unavailable in the existing system? Best practice

Users, Endpoints, and Licensing Q). Please provide the approximate number and type of endpoints at each of the District’s 18 facilities. Previously answered.

Q). Of the approximately 1,000 endpoints, how many are assigned to individual users versus classrooms, common areas, conference rooms, departments, and other shared locations?

A). Previously answered.

Q). Are there different user profiles or feature requirements based on job function? If so, please provide approximate quantities for each user category.

A). No

Q). How many users are expected to require a physical phone, desktop softphone, mobile application, or a combination of these options? A). 1000

Q). May respondents recommend a mix of physical phones and desktop/mobile applications to improve flexibility and reduce total cost?

A). yes

Q). How many endpoints require voicemail, voicemail-to-email, advanced call handling, multiple line appearances, shared lines, busy-lamp fields, or participation in call queues?

A). 1000

Q). Please identify the number and type of analog devices that may require continued support, including fax machines, alarms, elevators, paging equipment, door phones, and modems.

A). Previously answered.

Dialing Plan and Calling Services Q). Must existing extension numbers be preserved during migration?

A). Yes

Q). Should each location maintain a separate extension range or site-specific prefix, or may the new platform use a district-wide consecutive extension plan?

A). yes

Q). What extension length and inter-location dialing method does the District prefer?

A). 4

Q). Should respondents assume that Grande/Astound will continue providing SIP and PSTN services, or should the proposed UCaaS provider include local, long-distance, toll-free, DID, and carrier services?

A). Taking recommendations

Q).Approximately how many DIDs, main numbers, toll-free numbers, and fax numbers will need to be ported?

A). Previously answered.

Q). Approximately how many dispatchable locations must be configured to meet Kari’s Law and RAY BAUM’S Act requirements, and is room-level location identification required?

A). 18 locations, yes

Q). Which personnel or departments must receive emergency-call notifications, and through which methods—email, SMS, voice call, desktop notification, or another channel?

A).Handled by groups.

Q). What calling behavior does the District expect during a WAN, Internet, power, carrier, or cloud-service outage?

A). Continuous failover operation when available

Q). Does the District require integration with campus police, security, mass notification, paging, intercom, bells, or other emergency-management systems?

A). Must dial and report location to 911.

Q). What level of Microsoft 365, Teams, Exchange Online, Entra ID, SAML SSO, directory synchronization, and automated user-provisioning integration is expected?

A). All the above in some form

Q). What is the District’s anticipated implementation timeframe, and does it prefer a phased site-by-site migration or a district-wide cutover?

A). Previously answered.

Q). For five-year budget planning, should respondents include separate pricing assumptions for licensing, replacement phones, implementation, training, number porting, analog gateways, optional AI capabilities, call recording, and future expansion? A). yes

Q). The Acknowledgment Sheet asks vendors to confirm they understand the "evaluation criteria as described," but no evaluation criteria appear in the RFI. Will responses to this RFI be scored, and if so against what criteria and weightings?

A). This is purely information we are not making a decision at this time based on weights and criteria.

Q). The purpose of this RFI is understood to gather information from qualified vendors for an upcoming solicitation for a new Unified Communications as a Service (UCaaS) solution. What is the anticipated timeline of the future solicitation and award?

Section B — Cost Specifications Sheet (BT-50KD), Mechanics and Basis of Pricing A) previously answered

Q). For each of the ten-line items, should Unit Price be entered as (a) a per-user, per-month rate, (b) an annual total, or (c) a total for the full five-year term? Please state a single basis so all vendor responses are directly comparable.

A) total

Q). Line #0-1 "Five-Year subscription pricing," line #0-2 "Licensing only pricing," and line #0-3 "Licensing with new IP phones pricing" appear to overlap. Are these intended as mutually exclusive alternates or as additive line items? Because the sheet's Grand Total sums all lines, completing all three as written will double- or triple-count subscription cost. Please clarify or issue a revised pricing sheet.

A) Provide both this is only information and we can make necessary adjustments

Q). Because Quantity is locked at "1" and no per-item detail can be entered, will the District accept a detailed pricing workbook as a supplemental upload, showing SKU, description, quantity, unit price, term, and extended cost, with BT-50KD used only for roll-up totals? If yes, which document governs in the event of a discrepancy?

A). yes, this is purely informational

Q). For line #0-3, "Licensing with new IP phones," should endpoint hardware be priced as (a) an outright purchase, (b) a lease or rental, or (c) bundled into the recurring subscription as a device-as-a-service rate? Does the District have a preference between capital and operating expense treatment? Please confirm whether a specific phone model, model tier, or minimum feature set is required.

A). C

Q). For line #0-4, "Professional Services," should the price be a fixed-fee, turnkey figure covering the full multi-site deployment, or a labor rate card by role? If fixed fee, please confirm the scope assumptions raised in Section K so all vendors price the same work. If a vendor's professional services are already included within its licensing/subscription pricing, is a separate dollar entry still required for this line, or may it be noted as included/$0?

A).Turnkey fixed price, separate dollar amount Q). For line #0-5, "Number porting costs," should this be quoted per DID, per port order/BTN, or as a single project total? Please provide the total DID count to be ported. If a vendor's porting costs are already included within its licensing/subscription pricing, may this line be entered as $0/included?

A). Project total yes it may be included.

Q). For line #0-6, "Analog gateway costs," is the District expecting the vendor to supply analog gateways/ATAs for existing analog devices? Please provide the count and location of analog ports required or confirm vendors should price from an assumed quantity and state that assumption.

A). Yes 3 elevators.

Q). For line #0-7, "Training costs," should this be a fixed fee for a defined number of sessions? How many administrator sessions and end-user sessions does the District expect, at how many physical locations, and delivered on site or virtually?

A). Fixed locations and training to be determined.

Q). For lines #0-8 (Optional AI licensing) and #0-9 (Optional call recording licensing), should these be quoted for the full user population or for a defined subset? If a subset, how many users of each?

A). Full user

Q).For line #0-10, "Future expansion pricing," please define the unit to be quoted: a per-user add-on rate held firm for the contract term, a per-site rate, a new-facility turnkey rate, or a MACD rate card.

A). All of the above

Q). Is the District's intended contract term five years firm, or would it like alternate terms (for example three-year and seven-year) priced for comparison?

A). alternate is fine.

Q). Will the agreement be subject to a non-appropriation or termination-for-convenience clause requiring annual budget appropriation? If so, how should vendors reflect that risk in five-year pricing?

A). yes, whatever your normal practice

Q). The RFI cites approximately 1,000 voice endpoints, approximately 1,500 employees, and support for "approximately 1,000 users." Please confirm the exact number of licensed users to be priced and clarify whether every employee requires a licensed account or only those assigned a physical endpoint.

A). 1000

Q). Please provide a breakdown of endpoints by intended license type: (a) full UC users with desk phone, desktop client, and mobile app; (b) softphone/mobile-only users with no desk phone; (c) common-area or shared endpoints (classroom, hallway, workroom, gym, cafeteria); and (d) analog devices. Common-area licensing is typically a fraction of full-user cost, so this breakdown determines the total recurring price.

A). previously answered.

Q). How many endpoints are located in classrooms, and does the District require a phone in every instructional space?

A). mix of environments. Devices listed in other questions.

Q). Please provide a site list for the approximately 18 facilities, including physical address, endpoint and user count per site, and facility type (elementary, secondary, administration, athletics, transportation, maintenance, warehouse, police/security, early childhood).

A). This information is not needed to know the offering.

Q). What is the total count of DID numbers in service? How many published main numbers and toll-free numbers are in use? Previously answered. Not toll-free numbers A).

Q). Please provide an inventory, by site and quantity, of the analog devices that must be supported: fax machines, elevator phones, fire alarm panel (POTS) lines, intrusion alarm dialers, blue-light or emergency call boxes, gate and door callbox intercoms, athletic field and pool phones, and any modem or credit-card lines.

A). 3 elevators

Q). For life-safety analog circuits (elevator, fire alarm communicator, area-of-rescue assistance), does the District intend to retain carrier-provided POTS lines, migrate to a managed POTS-replacement service, or expect the UCaaS vendor to provide an alternative? Please state a single approach so all vendors price the same scope.

A) UCaaS vendor to provide an alternative

Q). Please identify the overhead paging system at each site by manufacturer and model (for example Bogen, Valcom, Atlas, Rauland Telecenter, Dukane), and confirm whether integration is expected natively via SIP or via an analog loop-start/trunk port from a vendor-supplied gateway.

A). Bogen integration not needed.

Q). Is the new platform expected to support bell/tone scheduling and classroom-to-office intercom or call-back functions, or do those functions remain entirely within the existing paging/intercom system? If the platform must provide them, please describe the required behavior.

A). no

Q). Please provide switch models, PoE standard (802.3af/at/bt), and available PoE budget by site. Are there locations where PoE capacity, switch model, or software version would require upgrade to support new endpoints, and would that upgrade be in the District's scope or the vendor's?

A). Meraki MX 250, district scope

Q). What is the Internet bandwidth at each facility? Is Internet access broken out locally at each site or centralized through a district hub? Is there a redundant or diverse path, and who provides each circuit?

A). 10Gb redundant 2 sites

Q). Requirement #17 calls for "automatic failover during outages." Does the District require on-site survivability if a campus loses WAN or Internet connectivity, for example a local survivable gateway with a backup PSTN or cellular path, or is cloud-side geographic redundancy sufficient? Please state the expected behavior for on-campus station-to-station calling and for 911 calling during a site outage. This requirement materially changes both architecture and price.

A). yes

Q). The RFI notes existing Grande/Astound SIP services. Does the District intend to (a) port all numbers to the UCaaS provider's carrier and retire the existing SIP service, (b) retain the existing SIP trunks and integrate them with the cloud platform (bring-your-own-carrier), or (c) have vendors price both? This is among the largest cost variables in the response.

A). Will evaluate at later date provide your recommendation based on your solution.

Q). What is the contract expiration date and any early-termination liability on the existing Grande/Astound service? Should vendors assume a period of parallel service during migration, and if so, how long?

A). previously answered.

Q). Are the District's DIDs distributed across multiple carriers or billing telephone numbers? Can the District provide a current Customer Service Record (CSR) and DID list during the RFI period, or will that be provided with the RFP?

A). Will be provided.

Q) Requirement #14 specifies "dynamic E911 with dispatchable location." What granularity does the District require: building, floor, wing, or individual room/switch port? Room-level mapping across 18 facilities and approximately 1,000 endpoints represent significant professional-services labor and must be scoped identically by all vendors.

A). switchport room

Q).Is the vendor expected to perform the initial dispatchable-location data build, switch port-to-room mapping, address validation, and PSAP record loading, or will the District supply a validated location table? If vendor-performed, will the District provide accurate as-built port and room documentation?

A). district provide.

Q). For requirement #16, "emergency notification": where should notifications of 911 calls be delivered (campus front office, District police/security, a designated distribution list, mobile app, Microsoft Teams), and in what form (email, SMS, on-screen alert, audible)? Should notification be campus-scoped, district-wide, or both?

A). email and call selected users.

D).Does the District require integration with a school-safety or silent panic alert platform in support of Texas requirements, for example Centegix CrisisAlert, Raptor, CrisisGo, Navigate360, or Rave? If so, please identify the platform and describe the expected integration behavior.

A). No

Q). Will the District require execution of a Texas Student Data Privacy Agreement (TX-SDPA / SDPC) or its own data privacy agreement for this service? If so, please provide the template with the RFI or confirm it will be issued with the RFP.

A). RFP

Q). What is the authoritative source of user identity for provisioning: Microsoft Entra ID, on-premises Active Directory, or the District's SIS/HR system (for example Skyward, Frontline, or TEAMS)? Is automated provisioning and deprovisioning (SCIM) required, and from which system of record?

A). Entra, automated

Q). Requirement #5 (hunt groups and call queues) and requirements #58–59 could be satisfied either by basic queueing or by a full contact-center product. Does any department, for example enrollment, child nutrition, transportation, or the technology help desk, require formal contact-center capability with skills-based routing, supervisor monitoring, real-time dashboards, and historical agent reporting? If so, how many agents and supervisors?

A). no

Q). For requirement #48 (optional call recording): how many users require recording, what retention period is required, and is recording needed always-on, on-demand, or by policy? Are there any departments with a legal or board-policy recording requirement?

A). 0

Q). Requirement #47 of the RFI and line #0-8 (Optional AI licensing) of the BT-50KD reference AI capability without defining scope. Requirement #58 of the RFI and specification #6.0.1 of the Specifications (Q-14DS) reference an "AI receptionist" without further definition. Please elaborate on the desired outcome and functional scope for this requirement (for example, automated attendant/call routing, natural-language IVR, after-hours virtual receptionist, or another use case).

A). Whatever you see may be value add.

Q). Requirement #59 of the RFI references advanced analytics and reporting. What level of analytics and reporting is required (for example, standard usage/QoS reporting vs. advanced workforce or contact-center analytics), and should this apply to the entire user base or a defined subset of users or groups?

A). standard

Q). Does the District want a phased cutover by campus or a district-wide flash cut? If phased, how many sites per cutover event, and over what total project duration?

A). district

Q). What cutover window does the District require or prefer: summer break, weekends during the school year, or after-hours weeknights? Please identify blackout dates such as the first and last weeks of school, STAAR testing windows, registration periods, and major UIL or district events.

A). after hours

Q). Is the vendor expected to perform physical endpoint deployment, unboxing, placement at each desk and classroom, connection, and removal of the legacy device, or will District staff perform physical placement with the vendor providing configuration and cutover support? This is the largest single driver of professional-services labor for a 1,000-endpoint deployment and must be defined identically for all vendors.

A). Physical placement

Q). Is the vendor expected to remove, decommission, and dispose of or recycle the legacy Cisco endpoints and the CUCM, Unity, and Emergency Responder server infrastructure? If so, does the District require certified data destruction and asset disposition reporting?

A). no q). After go-live, does the District expect to perform moves, adds, and changes itself through the administrative portal, or does it want a vendor-managed MACD service included in recurring pricing? If vendor-managed, what monthly MACD volume should be assumed?

A). District

End >

All other terms, conditions, and requirements of the original RFI remain the same.

Please sign and upload this document with your submission.

Signatures: By signing this document, I agree that I have read and reviewed Addendum #2- RFI 001-27 Temple ISD Cloud Calling & Unified Communications

Name of Company: _____________________________________________

Representative Name: ___________________________________________

Signature: _____________________________________________________

Date________________________ Page 1 | 1 image1.png

File details come from the government source that posted it. Updated .