A2__FRR_6__Citizen_Portal_Requirements.xlsx
XLSX spreadsheet 28 KB Posted
- Attached to
- Enterprise Resource Planning (ERP) System State and local contract opportunity
- Solicitation number
- P-26-08-COC
- Issued by
- Brevard County, Clewiston City, Florida
About this file
This is a requirements document for a Citizen Portal component of an Enterprise Resource Planning (ERP) system solicitation for the City of Cocoa, Florida. The document outlines comprehensive functional requirements organized across six primary categories: General Requirements, User Management, Public Access Information, Usability, Security, and Web-Based Payment capabilities. The General Requirements section specifies that the portal must function as a centralized, 24/7 operational platform with configurable appearance matching the City's website, capable of capturing usage statistics, encrypting sensitive information, supporting online form submissions with document attachments, and maintaining ADA compliance. User Management requirements include self-registration capabilities, mobile authentication with one-time passwords, mass registration through file upload, push notifications based on user interests, password reset functionality, administrative controls for user and group management, and feature-level access blocking. The portal must also provide comprehensive user access logs and administrative modules for managing portal features.
The Public Access Information section mandates integration with external data sources to display events, interactive community dashboards, GIS mapping capabilities with latitude/longitude precision, third-party reports, traffic and utility disruption notifications, advanced search functionality with auto-completion and Boolean search support, analytics integration with major platforms such as Google Analytics and WebTrends, personalized content delivery based on user location, and feedback management components. Usability requirements emphasize interactive user interface design with drag-and-drop widget functionality, email and SMS gateway integration, display of user login history and IP addresses, clear and organized layouts, consistent cross-platform experience, screen reader optimization, and built-in tutorials and help features. Security requirements include user authentication, permission management, credential-based information access restrictions, single sign-on capability, work-in-progress saving functionality, request status tracking, electronic signature generation, and identity field pre-population. Web-Based Payment capabilities must support credit card processing integration, ACH and credit card management, permit and application payment processing, real-time receipts, special assessment and fine payments, partial payments, inspection and license fees, multi-account consolidated payments, and payment type restrictions. The Data Analytics section specifies requirements for data repository consolidation from multiple system databases, SQL database connectivity, FTP data transfer capabilities, integration with Microsoft Office products and ESRI GIS systems, data relationship management, user portal presentation layers, key performance indicator establishment and display, dynamic database selection, pattern and trend detection, and scalability for future integration with additional data sources.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| P2608COC_NOTICE_OF_INTENT_TO_SHORTLIST.pdf | ||
| 08272026_P2608COC_ERP_System_Meetingv2.pdf | ||
| Master_Bid_Tabulation_Sheet_P2608COC.pdf | ||
| Addendum_3_P2608COC_QA.xlsx | XLSX spreadsheet | |
| Addendum_2_P2608COC.pdf | ||
| Addendum_1_RFP_P2608COC.pdf | ||
| A1__Proposal_Response_Forms.docx | DOCX document | |
| A2_FRR_2__Finance_Accounting_and_Reporting_Requirements.xlsx | XLSX spreadsheet | |
| A2__FRR_1__General_System_Requirements.xlsx | XLSX spreadsheet | |
| A2__FRR_4__Human_Resources_Management_Requirements.xlsx | XLSX spreadsheet | |
| A3__Terms_and_Conditions_P2608COC.docx | DOCX document | |
| A4__Combined_Proposer_Certifications_and_Affidavits.docx | DOCX document | |
| A2__FRR_3__Purchasing_Requirements.xlsx | XLSX spreadsheet | |
| A2__FRR_5__Utility_Billing_Requirements.xlsx | XLSX spreadsheet | |
| RFP_NO._P2608COC_Enterprise_Resource_Planning_System.pdf |
Show all 15
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
Portal
| Citizen Portal | |||
| # | Requirement | Response | Comments |
| General Requirements | |||
| 1 | Provide a Citizen Portal to be one stop shop for citizens. All online payment transactions are in one place with one log in. | ||
| 2 | Provide a configurable Citizen Portal that can have a similar look and feel as the City's website. | ||
| 3 | Provide a Citizen Portal that is operational on a 24x7 basis. | ||
| 4 | Ability to capture and track usage volume statistics. | ||
| 5 | Ability to send an email notice of successful submission to a user that contains hyperlinks to the relevant areas of the Citizen Portal. | ||
| 6 | Ability to allow "online form submission" whereby users can complete fillable forms for electronic submission. | ||
| 7 | Ability to encrypt sensitive information. | ||
| 8 | Ability to allow documents to be attached to online form submissions. | ||
| 9 | Portal must meet the latest available ADA compliance requirements & be updated to meet such requirements as they evolve | ||
| User Management | |||
| 10 | Ability to enable user to register themselves. | ||
| 11 | Ability to highlight the mandatory fields to be filled for registration. | ||
| 12 | Ability to support mobile authentication with one time password for registration. | ||
| 13 | Module should also support mass registration through file upload for admin users. | ||
| 14 | Ability to have user interests to be captured at the time of registration and relevant events push notifications to be sent to users via email, text and Mobile Push Notifications. | ||
| 15 | After registered user logs in to the Portal, Portal should redirect user to the home page. | ||
| 16 | Provide a forgot password mechanismin the Login page. In case user forgets the password/wish to reset a link should be sent to user’s registered Email address or by sending OTP on registered mobile to reset password. | ||
| 17 | Provide an admin module using which Portal administrator(s) can create/edit/delete users and groups. | ||
| 18 | Provide the capability of feature wise blocking. City needs to have the abilit to choose which features are accessible. | ||
| 19 | Ability for Portal to provide user access logs. | ||
| Public Access Information | |||
| 20 | Events: Ability to pull data from an existing outside source in which users can view events happening in the City on a particular date. | ||
| 21 | Dashboards: Ability to create and show interactive community dashboards to maintain citizen engagement. The data of these dashboards will be fetched from third party systems via intergration with the Module. | ||
| 22 | GIS: Ability of displaying any GIS map example open street maps, Google Map, etc. Portal should have capability to map boundary and locations with exact latitude and longitude. | ||
| 23 | Reports: Ability to show reports created by City in other 3rd party applications. | ||
| 24 | Disruptions: Ability to inform about upcoming traffic disruptions due to road, bridge constructions and water supply, drainage disruptions, notify customers of targeted areas of water outages for repairs. | ||
| 25 | Search: Provide built-in search or should be able to integrate with any third party search tool providing smart search. Portal visitors should be able to quickly and easily find the appropriate information on the portal in the context of portal. The search functionality should support content search with features like auto-completion, partial words and phrases, and Boolean search. | ||
| 26 | Analytics: Portal should be able to integrate with all major analytics packages like WebTrends and Google Analytics etc. | ||
| 27 | Personalization: Ability to display personalized content for registered users (e.g. location based content). The portal should have the capability to remember and store registered user preferences. | ||
| 28 | Feedback: Provide a feedback management component which would allow users to provide feedback related to different categories of the website. | ||
| Usability | |||
| 29 | Interactive Display: User interface should be interactive. Portal should support use of Modules/Widgets that can be placed onto pages that provide static, dynamic or interactive content. Users should be able to re arrange widgets on a portal page with easy to use drag and drop feature. | ||
| 30 | The solution should have out of box support to integrate with external email gateway and SMS (text message) gateway. | ||
| 31 | The solution should be able to store and display registered user’s last login, location, IP address, time, and date. | ||
| 32 | The solution will provide clear layout and organized displays. | ||
| 33 | The solution will provide consistent experience across all Digital Platforms. | ||
| 34 | The solution should be optimized for integration with standard screen readers on the market. | ||
| 35 | The solution must be easy and intuitive to learn (The degree to which the solution can be used without specific training). | ||
| 36 | The solution should include built in tutorials and help features to allow easy asistance for users. | ||
| 37 | The solution will allow an agreed set of tasks to be completed by an agreed duration e.g. make a payment, view a bill, book a service etc. | ||
| Security | |||
| 38 | Provide a security-enabled functionality set (i.e., user ID and password required). | ||
| 39 | Ability to maintain permissions by user (need to inactivate a user) | ||
| 40 | Ability to allow certain information to be restricted for viewing only by users logged-in with appropriate credentials. | ||
| 41 | Ability for users to employ a single username/password combination for all security-enabled functionality. | ||
| 42 | Ability to allow a user to save work in progress with the ability to edit prior to submission (i.e., log out and then log back in without losing information). | ||
| 43 | Ability to allow a user to view the status of a request/submission after logging in. | ||
| 44 | Ability to pre-populate basic identity fields based on the account information stored with the user's ID/password. | ||
| 45 | Ability to generate an electronic signature based upon approved login credentials. | ||
| Web-Based Payment | |||
| 46 | Ability to integrate with the City's credit card processing merchant to accept payments through the self-service portal. | ||
| 47 | Ability to allow customers to set up and edit ACH and credit card information on line. | ||
| 48 | Ability to allow payments for certain permit and application types in the self-service portal. | ||
| 49 | Provide a receipt of payments made in real time. | ||
| 50 | Ability to allow payments for certain special assessments, liens and fines in the self-service portal. | ||
| 51 | Ability to allow partial payments in the self-service portal. | ||
| 52 | Ability to allow payments for certain inspections and licenses in the self-service portal. | ||
| 53 | Ability to pay multiple accounts with one payment. | ||
| 54 | Ability to restrict payment types to City-defined parameters (i.e., credit cards accepted). |
| Compliant |
| Alternative Method |
| Modification Required |
| Non Compliant |
Data Analytics
| Data Analytics | |||
| # | Requirement | Response | Comments |
| Data Analytics | - | ||
| 1 | Ability for data from multiple system databases to be stored in a single repository/collection. | ||
| 2 | Ability to establish a direct connection to all SQL databases throughout the City. | ||
| 3 | Ability to establish a FTP connection to the exported data and facilitate data transfers to the system. | ||
| 4 | Ability to integrate / interact with standard Microsoft Office products, including Word, Excel, Access, Outlook (email and calendar), Visio and SharePoint. | ||
| 5 | Ability to integrate with the ESRI GIS system. | ||
| 6 | Ability to actively relate common data points (e.g. utility bills and permits to pull up all information on a single address). | ||
| 7 | Ability to create User Portals as a presentation layer to access data, queries, reports, dashboards, and other applications. | ||
| 8 | Ability to establish acceptable norms for key performance indicators on the User Portals, and display them as part of the presentation layer. | ||
| 9 | Ability to dynamically select data bases used for source data in a query or report. | ||
| 10 | Ability to automatically and dynamically detect and identify patterns and trends in data around undefined data elements and /or parameters. | ||
| 11 | Provide scalability for future integration with additional data sources and tools. |
| Compliant |
| Alternative Method |
| Modification Required |
| Non Compliant |
File details come from the government source that posted it. Updated .