Exhibit_A.2_-_Technical_Requirements_Matrix_(1_TAB_TO_COMPLETE).xlsx
XLSX spreadsheet 16 KB Posted
- Attached to
- Banking Services
- Solicitation number
- 25-P-131TF
- Issued by
- Volusia County, Florida
About this file
The document is a Technical Requirements Matrix (Exhibit A.2) for a Banking Services Request for Proposal (RFP) issued by Volusia County, Florida. The exhibit details comprehensive technical requirements for a banking services solution, focusing on system capabilities across areas such as overall system requirements, integration, application architecture, security, and disaster recovery. The matrix provides a structured approach for potential vendors to respond to specific technical criteria using response codes including Yes (Y), No (N), Configuration (CO), Customization (CU), Future (F), and Third-Party Supplied (3).
The technical requirements emphasize robust security features, including password protection, user access controls, unauthorized access tracking, and administrative management capabilities. Key technical specifications include browser compatibility, data export functionality, audit trail tracking, field-level edit checks, and system availability guarantees of 95% per month. The document also outlines specific disaster recovery requirements, such as maintaining a secondary hosting facility with real-time failover, ensuring all servers are located in the United States, and maintaining data currency within 60 minutes of the primary site. The matrix serves as a comprehensive evaluation tool for assessing potential banking services technology solutions that can meet Volusia County's complex operational and technological needs.
View the file
Other files
Show 40 more
50 files listed here. See the rest on GovTribe.
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
Technical Requirements Exhibit A.2 - Technical Requirements Matrix
Complete the following table with the appropriate response(s) as defined below:
| Response Code | Definition |
| Y - Yes | The functionality exists in the proposed product, and/or the Respondent agrees that the requirement will be adhered to upon any potential award. The functionality shall be implemented ‘out of the box’ without configuration, customizations or modifications to the existing applications or reports. |
| N - No | Requirement shall not be provided. |
| CO - Configuration | Requirement shall be met through changes to settings of tables, switches, and rules without modification to source code. Include any changes to the existing or “out of the box” workflow functionality. |
| CU - Customization | Requirement shall be met by changing existing software or through the use of software tools such as application report writer, query, etc. Note: In the Comments column next to this response, you shall indicate the following: Description of customization Estimated level of complexity (High, Medium, Low) |
If there is an additional cost it shall be included in the cost proposal exhibit.
| F- Future | Requirement shall be met by packaged software that is currently under development, in Beta test, or not yet released. Note: In the Comments column next to this response, indicate the date when requirement shall be available for implementation. If possible, also indicate any additional costs. |
| 3 - Supplied by 3rd Party | The requirement shall be met by a third-party software package, and the third party software is included in this Proposal for implementation. Note: In the Comments column, indicate the name of the proposed 3rd party software package and indicate the interface/integration services being proposed. |
| Comment Field | Provide information, description, clarification, or explanation to assist the County in making an informed decision. |
25-P-131TF One Response Per Requirement Exhibit A.2 - Technical Requirements Matrix
| Y/N | CO | CU | F | 3 | |||
| No. | TECHNICAL REQUIREMENTS | The items listed below are the minimum features that shall be included in the Solution. Exceptions or alternatives shall be clearly marked and detailed in the comment row provided. |
| 1.0 | Overall System Requirements |
| 1.1 | System provides easily retrievable audit trail information. |
| 1.2 | The system supports auto populating of fields wherever possible. |
| 1.3 | The system supports the ability to fully function in the latest version of the Mozilla Firefox, Google Chrome, and Microsoft Edge web browsers. |
| 2.0 | Integration |
| 2.1 | The software shall be able to export data in ASCII, Microsoft Excel, PDF and other standard formats. |
| 3.0 | Application Architecture |
| 3.1 | The system should provide field level edit checks for transactions during data entry and provide immediate user feedback, including error messages and possible corrective actions (i.e., warnings when entering existing address, etc.) |
| 3.2 | The County is to be licensed to make unlimited copies of any training materials. Such material Is to be used for an ongoing training plan within the County. |
| 3.3 | Cut and paste capability from data fields and screens to other applications |
| 3.4 | The system shall provide uninterrupted access and service during working hours, with unscheduled downtime not exceeding a maximum of one (1) hour per month; |
| 4.0 | Security (Technical) |
| 4.1 | The system should not display passwords during user entry. |
| 4.2 | The system should allow a County administrator to suspend a County user ID from further use from one or more modules. |
| 4.3 | The system should require users to periodically change their password based on a Bank-determined parameter. |
| 4.4 | The system should time-out or suspend users after a period of time of being idle. This time out requires the user to re-enter their password before continuing. |
| 4.5 | The system should restrict access to user administration data and functionality. |
| 4.6 | The system should set a minimum password length (i.e., eight characters) and should be composed of letters and numbers. |
| 4.7 | Passwords should be stored encrypted without a means to decrypt. |
| 4.8 | The system should allow a County administrator to reset passwords and force the user to change on next logon. |
| 4.9 | The system should allow an administrator to add and modify user security information using online screens with immediate profile update. |
| 4.10 | The system should record or capture information about each unauthorized access attempt such as: user ID, workstation, IP Address, date, time. |
| 4.11 | The system should allow an administrator to review and report on attempted security violations. |
| 4.12 | The system should allow an administrator to generate online inquiry and batch reports to review user access profiles. |
| 4.13 | The system should record in the system who changes security profiles and when changes are made (user name, changes made, date and time stamp). |
| 4.14 | The system should have a threshold for the number of invalid logon attempts. |
| 4.15 | User accounts should have e-mail addresses for notifications. |
| 4.16 | The system should provide the ability to group users into classes and to assign these classes’ rights that will be applied to each user in the group. When the user’s explicit rights are in conflict with the rights granted by group membership, the user's settings prevail. |
| 5.0 | Disaster Recovery & System Administration Requirements for Contractor Hosted Solutions |
| 5.1 | Guaranteed Availability: The County requires a guarantee of 95% system availability as a minimum per month for all County services hosted by the Contractor; three (3) days prior notice for any planned maintenance; and, one (1) hour notice for downtime required for high-priority and/or security issues. |
| 5.2 | The County requires the Contractor to have at least one (1) secondary hosting facility, with real-time failover in the event that the primary hosting facility fails or is not operational via the internet. |
| 5.3 | All primary servers and / or failover sites shall be located in the United States unless specifically agreed to by the County. |
| 5.4 | The primary and secondary hosting locations shall be in different regions of the United States. |
| 5.5 | The Contractor owns and operates the primary and secondary hosting site(s). If not, then the Contractor shall provide all required documentation and references for this subcontracted service in this comment section. |
| 5.6 | The failover site shall provide the same services as the primary site. Application, content, and data currency shall lag no more than 60 (sixty) minutes behind the primary site. |
&"Arial,Bold"&12 25-P-131TF &"Arial,Bold"&12 Exhibit A.2 - Technical Requirements Matrix
Page &P of &N
File details come from the government source that posted it. Updated .