Scope_Compliance_Matrix.xlsx
XLSX spreadsheet 14 KB Posted
- Attached to
- Telecommunications System
- Solicitation number
- 2026-RFP-047
- Issued by
- Riverside County, California
About this file
This is a Scope Compliance Matrix for a telecommunications system replacement project for the City of Palm Desert, California, detailing whether the proposed vendor solution meets specified requirements. The project involves replacing the City's existing on-premise Mitel/ShoreTel phone system with a modern, cloud-based VoIP/UCaaS telecommunications solution. Key requirements include hosted telephony and UCaaS capabilities, Microsoft Office 365 and Teams integration, unified messaging and voicemail, SMS/MMS texting functionality, paging through phone speakers, external analog paging access, Revolution Activate ENS integration, AI tools, administrative portal with role-based permissions, telephone devices and licensing, automated attendant capabilities, E911 compliance, call detail reporting, training services, maintenance and support, and implementation with cutover and acceptance period provisions.
The scope compliance matrix serves as an evaluation tool for assessing vendor proposals against mandatory and optional requirements. The matrix requires vendors to indicate compliance status for each requirement as "Comply," "Partial," or "Does Not Comply," and to specify whether each component is included in the base price or represents a third-party or optional component. Vendors must provide explanations, exceptions, and references to proposal pages for each requirement. The proposed solution must align with the City's existing technology standards, including Microsoft Office 365 and Teams for collaboration and directory integration, while maintaining compatibility with the City's use of Zoom for public meetings and the Revolution Activate ENS mass-notification system for emergency alerts, including bi-directional communication capabilities and documented integration.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Telecommunications_System_(Addendum_#2_Revision).pdf | ||
| Pricing_Proposal_REVISED.xlsx | XLSX spreadsheet | |
| Intake_Form_-_Solicitations.pdf | ||
| Telecommunications_System.pdf | ||
| Pricing_Proposal.xlsx | XLSX spreadsheet | |
| Professional-Services-Agreement_FOR_OPENGOV.docx | DOCX document |
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
Sheet1
| Scope Compliance Matrix | ||||
| Scope Requirement | Comply / Partial / Does Not Comply | Included in Base Price? | Third-Party or Optional Component? | Explanation / Exception / Reference to Proposal Page |
| Hosted telephony / UCaaS solution | ||||
| Microsoft O365 and Teams integration | ||||
| Unified messaging and voicemail integration | ||||
| SMS/MMS texting | ||||
| Paging through phone speakers | ||||
| External analog paging access | ||||
| Revolution Activate ENS integration | ||||
| AI tools | ||||
| Administrative portal and role-based permissions | ||||
| Telephone devices and licensing | ||||
| Required telephony features | ||||
| Automated attendant requirements | ||||
| E911 compliance | ||||
| Call detail reporting | ||||
| Training | ||||
| Maintenance and support | ||||
| Implementation and cutover | ||||
| Acceptance period |
File details come from the government source that posted it. Updated .