RFP_34101-250701_ATTACHMENT_6.6_System_Requirements_Matix.xlsx

XLSX spreadsheet 42 KB Posted

Attached to
TEMA Critical Incident Management System - UPDATED
Solicitation number
RFP 34101-250701
Issued by
Davidson County, Tennessee

About this file

This System Requirements Matrix attachment is part of the Request for Proposals issued by the Tennessee Emergency Management Agency (TEMA) for a Critical Incident Management System (CIMS). The RFP requires respondents to complete a detailed evaluation matrix indicating their proposed system's capability to meet 23 specific technical requirements across six primary categories: ESRI ArcGIS Online integration, system capacity and scalability, administrative configuration capabilities, and role-based access control. Respondents must submit their technical and sealed cost proposals by July 7, 2026, at 2:00 p.m. central time, with a mandatory pre-response conference scheduled for May 22, 2026, at 9:00 a.m. CST via Microsoft Teams. The top three ranked proposers will present orally on July 27-29, 2026, and the Notice of Intent to Award is anticipated for August 6, 2026, with a contract effective date of September 15, 2026. The contract term extends for 60 months with potential renewal or extension options to be negotiated with the selected contractor.

The System Requirements Matrix requires respondents to designate each requirement with response codes indicating whether the proposed system can meet requirements without modification (M), with configuration (CF), with customization (CZ), or cannot meet requirements (NO). Key technical mandates include bidirectional data synchronization with ArcGIS Online with a maximum 10-minute delay, support for 300 concurrent users and 5,000 user accounts without fixed maximum limits, FedRAMP Moderate compliance, no-code/low-code administrative configuration capabilities enabling authorized personnel to create and modify data-capture forms and workflows without contractor intervention, and comprehensive role-based access control functionality. The estimated maximum contract value is $800,000 for the full 60-month term, encompassing software licensing, implementation charges, annual SaaS subscription fees, and unit pricing for users and accounts exceeding baseline quantities. No incumbent vendors or set-aside designations are identified, and the selected solution must be the vendor's primary commercial product purpose-built for emergency management and commercially offered for at least three consecutive years prior to RFP release.

View the file

Other files

Show all 12

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

System Requirement

RFP 34101-250701 Attachment 6.6: System Requirements Matrix
RESPONDENT SIGNATURE:
PRINTED NAME & TITLE:
DATE:

RESPONDENT LEGAL ENTITY NAME:

Please complete column D with one of the following responde codes:

M - The System can meet requirements without Configuration or Customization CF - The System can meet requirement with Configuration CZ - The System can meet requirement with Customization NO - The System cannot meet Requirements

Column E is optional

If response code left blank will be considered NO - The System icannot meet requirements.

Req IDCategory NameSystem RequirementResponse CodeAdditional Comments
MD-1ESRI ArcGIS Online IntegrationIntegrates with ESRI ArcGIS Online

MD-2 ESRI ArcGIS Online Integration Allows authorized administrators to configure the integration using the system’s native administrative interface

MD-3 ESRI ArcGIS Online Integration Supports bidirectional data exchange with ArcGIS Online feature services, such that:

a. Data updates in ArcGIS Online are reflected in the CIMS; and

b. Data updates in the CIMS are reflected in ArcGIS Online.

MD-4 ESRI ArcGIS Online Integration 4. Supports automatic synchronization of data between systems without manual intervention.

MD-5ESRI ArcGIS Online IntegrationPerforms synchronization with a maximum delay of no more than ten (10) minutes.
MD-6System Capacity and ScalabilitySupports a minimum of 300 concurrent (simultaneous) active users.

MD-7 System Capacity and Scalability Supports the creation and management of at least 5,000 user accounts.

MD-8 System Capacity and Scalability Does not impose a fixed maximum limit below 5,000 user accounts.

MD-9System Capacity and ScalabilityDoes not require system redesign or custom development to support growth beyond 5,000 user accounts.
MD-10Administrative Configuration (No-Code / Low-Code)Allows authorized administrators to create and modify data-capture forms using the system’s native administrative interface or built-in configuration tools.
MD-11Administrative Configuration (No-Code / Low-Code)Allows authorized administrators to configure and modify workflows using the system’s native administrative interface or built-in configuration tools.
MD-12Administrative Configuration (No-Code / Low-Code)Allows authorized administrators to configure user interface elements or views (e.g., fields, layouts, dashboards, or screens)
MD-13Administrative Configuration (No-Code / Low-Code)Allows configuration changes to be performed without Contractor intervention.
MD-14Administrative Configuration (No-Code / Low-Code)Does not require custom code or software development skills to perform the configurations described above.
MD-15Administrative Configuration (No-Code / Low-Code)Provides these capabilities as native, out-of-the-box functionality (i.e., not dependent on custom development or third-party add-ons).
MD-16Role-Based Access Control (RBAC)The Respondent shall provide a response that the proposed CIMS:

1. Is at least Fedramp Moderate compliant

MD-17Role-Based Access Control (RBAC)2. Supports role-based access control (RBAC) in which user permissions are assigned based on defined roles.
MD-18Role-Based Access Control (RBAC)3. Allows administrators to create, modify, and delete roles using the system’s native administrative interface.
MD-19Role-Based Access Control (RBAC)4. Allows administrators to assign users to one or more roles.
MD-20Role-Based Access Control (RBAC)5. Allows roles to be configured with specific permissions (e.g., access to functions, data, and workflows).
MD-21Role-Based Access Control (RBAC)6. Automatically enforces permissions based on assigned roles at system login and during use.
MD-22Role-Based Access Control (RBAC)7. Does not require custom code or vendor intervention to create or manage roles and permissions.
MD-23Role-Based Access Control (RBAC)8. Allows roles to control user interface elements or data views (e.g., screens, dashboards, or displayed information).

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