7-Attachment F - Functional and Technical Requirements Index.xlsx
XLSX spreadsheet 16 KB Posted
- Attached to
- Cellular and Data Service State and local contract opportunity
- Solicitation number
- 543470
- Issued by
- Wayne County, Detroit City, Michigan
About this file
This is a Functional and Technical Requirements Index matrix for a cellular and data service Request for Proposal issued by the City of Detroit, Michigan, Office of Contracting and Procurement on behalf of the Department of Innovation and Technology. The RFP seeks qualified vendors to provide comprehensive cellular and data services, including mobile telecommunications devices, voice and data plans, and related support to serve the City's mobile workforce. The requirements matrix outlines 42 distinct functional and technical requirements organized across ten categories: Account and Portal Access, Asset Management, Billing and Reporting, Compliance and Innovation, Coverage and Network Performance, Device and Plan Flexibility, Device and Equipment Support, Device Provisioning, Management and Monitoring, Mobile Device Management, Network and Coverage Controls, Reporting and Transparency, Roaming Controls, Security and Access Control, Security and Administration, Self-Service Administration, SIM Management, Support and Escalation, Support and Lifecycle, System Updates, Transition and Portability, and Vendor Management. Requirements are designated as either Critical or Desired, with 28 marked as Critical and 14 as Desired.
The matrix establishes that vendors must demonstrate compliance with stringent security, operational, and service standards. Critical requirements include encrypted login credentials and role-based access control for administrative portals, itemized billing reports in machine-readable formats, real-world drive test coverage data for the City of Detroit, device refresh and upgrade programs, Mobile Device Management capabilities with remote wipe and lock functionality, multi-factor authentication and Section 508/WCAG 2.1 AA accessibility compliance, 24/7 support for public safety departments with next-business-day support for administrative users, and U.S.-based hosting for all administrative systems and billing portals. The vendor must also provide tools and documentation to support transition of devices and user data to another carrier at contract end without penalty, participate in quarterly service reviews, and adhere to the City's data access, account management, and security policies. Additionally, vendors must submit AI usage disclosure and a City AI Factsheet if applicable, and controls must be in place to prevent unintended international roaming near the Detroit-Windsor border.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| 1-Equalization Credit Statement.pdf | ||
| 5-Attachment A - Respondent Questionnaire RFP.docx | DOCX document | |
| 6-Attachment C-Pricing Matrix 2025.xlsx | XLSX spreadsheet | |
| 8-Attachment E- City of Detroit Technology Contract.docx | DOCX document | |
| 3-Attachment D-2 - Conditions of Award.pdf | ||
| 2-Attachment D-1 Required Forms Affidavits.pdf | ||
| 4-Attachment B - Respondent Proposal Introduction and Solution Approach.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
General Technical
| ATTACHMENT F - REQUIREMENTS MATRIX | ||||
| RFP Name & RFP # _________ | Vendor | |||
| Available Responses | ||||
| C | Requirement Met and Proposed (Standard features available in the product) | 0 | ||
| A | Intent of Requirement Met and Proposed with Alternative | 0 | ||
| N | Requirement Not Met with Proposal | 0 |
. TOTAL 0
| Req # | Function | General Technical Requirement | Criticality | Vendor Response | |
| (C, A, N) | Modules/Extras Required to Fulfill Requirements | Comments | |||
| 1 | Account & Portal Access | Administrative portals support encrypted login credentials and role-based access control. | Critical | ||
| 2 | Account & Portal Access | Proposal describes process for managing user accounts, contact escalation, and account roles. | Critical | ||
| 3 | Account & Portal Access | Proposal describes how system access is monitored and audit logs are maintained. | Critical | ||
| 4 | Account & Portal Access | The solution includes a secure administrative portal with self-service line management, activation/suspension, and multi-user access controls. | Critical | ||
| 5 | Asset Management | The solution supports inventory tracking by user, department, and device status. | Desired | ||
| 6 | Billing and Reporting | The solution includes itemized billing reports in machine-readable formats (e.g., CSV, JSON), sortable by user, department, or line type. | Critical | ||
| 7 | Billing and Reporting | The solution includes support for departmental billing code tagging or crosswalk mapping for automated reconciliation. | Desired | ||
| 39 | Compliance & Innovation | AI usage disclosure and submission of City AI Factsheet if applicable. | Critical | ||
| 8 | Coverage and Network Performance | The proposal includes verified real-world drive test data demonstrating voice and data coverage within the City of Detroit. | Critical | ||
| 40 | Data & Reporting | Integration with ESRI GIS systems for coverage and service analytics. | Desired | ||
| 10 | Device & Plan Flexibility | The solution supports pooled usage plans and seasonal accounts, if financially advantageous to the City. | Desired | ||
| 11 | Device & Plan Flexibility | The solution includes support for SIM and eSIM provisioning for both new activations and device migrations. | Critical | ||
| 12 | Device & Plan Flexibility | The solution includes device refresh or upgrade program to support scheduled replacement, contract-end swaps, or damage scenarios. | Critical | ||
| 13 | Device and Equipment Support | Vendor offers a range of modern smartphones, tablets, modems, and vehicle routers, including ruggedized and public safety options. | Critical | ||
| 14 | Device and Equipment Support | The solution includes support for eSIM provisioning, SIM card swaps, and number portability. | Critical | ||
| 15 | Device and Equipment Support | The solution includes a device trade-in, recycling, or environmentally responsible end-of-life program. | Desired | ||
| 16 | Device Provisioning | Vendor supports zero-touch enrollment, Apple DEP, or Android Enterprise provisioning. | Desired | ||
| 17 | Management & Monitoring | The solution includes a self-service administrative portal with real-time usage data, customizable reporting, and the ability to flag dormant or inactive lines. | Critical | ||
| 18 | Management & Monitoring | The solution includes alerting mechanisms for overages, international usage, or cost anomalies. | Critical | ||
| 19 | Management & Monitoring | Administrative portal allows City administrators to view, flag, and deactivate underutilized or dormant lines. | Critical | ||
| 20 | Management & Monitoring | Vendor portal allows for configuration of alerts (e.g., high usage, international roaming, inactive devices). | Desired | ||
| 21 | Mobile Device Management (MDM) | The solution includes MDM which provides functionality for remote wipe, lock, and policy enforcement. | Critical | ||
| 37 | Network & Coverage | Controls to prevent unintended international roaming near Detroit-Windsor border (e.g., geofencing, network-locking). | Critical | ||
| 38 | Network & Coverage | Submission of recent (within 12 months) real-world coverage evidence (drive tests or equivalent). | Critical | ||
| 22 | Reporting & Transparency | The solution supports real-time and historical reporting for all active lines, including data, voice, and messaging usage per device. | Desired | ||
| 23 | Reporting & Transparency | Reports are exportable in machine-readable formats (e.g., CSV, XLSX) and filterable by department or account group. | Critical | ||
| 24 | Reporting & Transparency | The solution includes APIs for automated usage and billing data integration into City systems. | Desired | ||
| 25 | Roaming Controls | The solution supports administrative control over international roaming and report related activity. | Critical | ||
| 26 | Security & Access Control | The solution's administrative systems support multi-factor authentication (MFA) and role-based access control for City users. | Critical | ||
| 27 | Security & Access Control | Portal systems comply with accessibility standards (Section 508, WCAG 2.1 AA). | Critical | ||
| 28 | Security & Administration | The solution and the vendor will adhere to the City’s general data access, account management, and security policies. | Critical | ||
| 41 | Security & Compliance | Confirmation of U.S.-based hosting for all administrative systems and billing portals. | Critical | ||
| 29 | Self-Service Admin | The solution provides functionality for City staff to reassign devices and manage user changes without requiring vendor support. | Critical | ||
| 30 | SIM Management | The solution includes support for SIM management tasks including bulk provisioning and porting existing numbers. | Critical | ||
| 31 | Support & Escalation | Proposal defines roles and responsibilities between vendor and City staff. | Critical | ||
| 32 | Support & Escalation | The solution provides 24/7 support for public safety departments, next-business-day support for administrative users; defined SLA escalation paths. | Critical | ||
| 33 | Support & Lifecycle | Vendor will participate in quarterly service reviews and provide reporting ahead of those meetings. | Critical | ||
| 34 | Support & Lifecycle | Proposal describes service-level expectations for provisioning, replacement, and repair of mobile devices. | Critical | ||
| 35 | System updates | The system supports remote deployment of system updates and system maintenance. | Critical | ||
| 42 | Transition & Portability | Vendor must provide tools and documentation to support transition of active devices and user data to another carrier at contract end, without penalty. | Critical | ||
| 36 | Vendor Management | Vendor will participate in quarterly usage and contract review meetings with City representatives. | Critical |
File details come from the government source that posted it. Updated .