12-J. Application Requirements Matrix Form.xlsx
XLSX spreadsheet 20 KB Posted
- Attached to
- NPDES MS4 SCM Compliance Software Solution
- Solicitation number
- FY26-RFP-07
- Issued by
- Mecklenburg County, Charlotte City, North Carolina
About this file
The document is an Application Requirements Matrix Form for the City of North Carolina, specifically for an NPDES MS4 Stormwater Control Measures (SCMs) Compliance Software Solution. The matrix outlines 20 detailed software requirements ranging from technical capabilities such as GIS-based data storage, internet and mobile accessibility, inspection tracking, compliance status monitoring, and reporting functionalities. The requirements are categorized as either required or optional, with each requirement designated a unique identifier (e.g., R-GN-10, R-GN-20) and requiring bidders to respond with a numeric rating indicating their solution's alignment (0-4).
The software solution must support comprehensive tracking and enforcement of annual stormwater control measure inspections, with critical features including automatic inspection scheduling, ability to work offline, support for NPDES MS4 Annual Report generation, mass data import capabilities, multiple file type uploads, and Okta user authentication. Key technical specifications include geographically assignable inspectors, third-party inspection submission processes, compliance status tracking, trend analysis, and the ability to categorize SCMs based on qualifying regulations. The solution is intended to help the city maintain regulatory compliance with its MS4 permit requirements, with strict operational expectations such as no more than two business days of system downtime.
View the file
Other files
Show all 11
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 Instructions: In the Bidder Response field, select the appropriate response (0-4) for each requirement. Add any comments that help explain the response selection 0 = Meets out of box 1 = Meets via Configuration 2 = Meets via Customization 3 = Does not meet, but on roadmap (provide date) 4 = Does not meet; Cannot modify
| REQ # | Functionality or Characteristic | Required or Optional | Company Response (Enter 0, 1, 2, 3, or 4) | Company Explanation/Comments |
| R-GN-10 | GIS Based data structure storing SCM records. Each SCM record should include standard information provided by project team, SCM inspection compliance status, and results of individual inspections. | Required | ||
| R-GN-20 | Software should be accessible via internet or mobile device (such as iPhone or iPad) | Required | ||
| R-GN-40 | Software should be able to geographically assign inspectors for SCM responsibility | Optional | ||
| R-GN-50 | Software should be able to send out notices of inspection to multiple parties associated with the SCM for required inspections. | Required | ||
| R-GN-60 | Software should be able to allow 3rd party inspectors to submit inspection for review by city inspector for an SCM | Required | ||
| R-GN-70 | Software should be able to track the compliance status of each SCM based on inspection time and results (Compliant, Needs Inspection, Corrective Action Required (CAR), Notice of Violation (NOV), and Penalty) | Required | ||
| R-GN-80 | Software should be able to track trends related to compliance and inspected features. | Optional | ||
| R-GN-90 | Software should allow each inspector to complete an inspection at the SCM regardless of network connectivity. | Optional | ||
| R-GN-100 | Software should allow for the City to download a copy of their hosted data to local assets (such as a Spatial Data Warehouse) in a tabular, database format | Required | ||
| R-GN-120 | Software should allow for automatic scheduling of inspections for SCMs based on service dates and last inspection | Required | ||
| R-GN-130 | Software should be able to report on all required items as a part of of NPDES MS4 Annual Report and Stormwater Management Plan | Required | ||
| R-GN-140 | Software should be able to allow form based inputing for SCMs | Required | ||
| R-GN-150 | Software should be able to mass-import exisitng SCMs and associated data | Required | ||
| R-GN-160 | Software should allow for different inspection templates for each SCM | Required | ||
| R-GN-170 | Software cannot be inaccessible, or inoperable for longer than 2 business days | Required | ||
| R-GN-180 | Software should be able to allow upload and storage of multiple file types. | Required | ||
| R-GN-190 | Software should be able to categorize SCMs based on qualifying regulations. | Required | ||
| R-GN-200 | Softwarer should be able to use Okta for user authentication | Required |
File details come from the government source that posted it. Updated .