19-Exhibit C - FWWD RFP Technical Requirements.v2.xlsx
XLSX spreadsheet 42 KB Posted
- Attached to
- RFP Customer Information System (CIS) Software
- Solicitation number
- 25-0128
- Issued by
- Tarrant County, Texas
About this file
This document is a Technical Requirements Exhibit (Attachment C) for the City of Fort Worth Water Department's (FWWD) Request for Proposal (RFP) for a Customer Information System (CIS) Software replacement. The RFP seeks a comprehensive, turn-key solution that includes Customer Information and Utility Billing system, Customer Relationship Management (CRM), and Mobile Workforce Management System (MWFM). The extensive technical requirements document comprehensively evaluates potential software solutions across multiple critical areas including architecture, scalability, reliability, performance, maintenance, security, user interface, content management, records management, customer engagement, support, documentation, reporting, dashboarding, and contact center functionality.
The technical requirements document reveals that the current proposed solutions have significant gaps, with many requirements scoring as "fail" across various categories. The evaluation framework includes technical scoring criteria (Available Out of the Box, Requires Configuration, Requires Customization, Not Answered or Not Available), prioritization of requirements (High, Medium, Low), and assessment of whether features are current, future, or both capabilities. The document indicates that vendors must respond to each requirement with details on technical score, core or non-core classification, whether the feature is included in the proposed price, and provide narrative explanations of how each technical requirement is met. The comprehensive nature of the requirements suggests FWWD is seeking a highly sophisticated, secure, and flexible software solution to replace its existing systems.
View the file
Other files
Show all 18
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
Attachment C - Technical Req
| Instructions: For each Requirement, fill-in the requested information for: Technical Score; Core or Non-Core; Included in the Proposed Price; and Comments. In the Comments column, give a narrative response to the technical requirement and how it is met. | ||||||||
| Ref # | Functional Area | Functionality or Characteristic | Technical Score | Priority | Current or Future | Pass / Fail | Core or Non-core | |
| (Respond if score = Requires Customization) | Included in the Proposed price (Y/N) | Comments | ||||||
| Feature Scoring Criteria: Available Out of the Box, Requires Configuration, Requires Customization, Not Answered or Not Available | ||||||||
| Architecture | ||||||||
| Architecture | Database, Data and Storage | |||||||
| 1 | Architecture | The ability to support database environments: Is the proposed database environment suitable and effective for your solution? Please provide a list of supported environments in the comment column. | 5 - High | Current | fail | |||
| 2 | Architecture | Database table and column naming philosophy. Is human-readable naming used, in order to support ad-hoc queries and reporting? | 3 - Medium | Current | pass | |||
| 3 | Architecture | The ability and effectiveness of standard query tools for data interaction. Please list supported query tools in the comment column. | 5 - High | Current | fail | |||
| 4 | Architecture | The availability, support, and effectiveness of Extract-Transform-Load (ETL) tools currently in use or used in previous migrations with existing clients? Please list supported ETL tools in the comment column. | 5 - High | Current | fail | |||
| 5 | Architecture | The ability to ensure data residency: Do the storage devices used to store FWWD data reside within the United States? Please provide the locations in the comment column. | 5 - High | Future | fail | |||
| 6 | Architecture | The ability to ensure data separation and integrity: Is FWWD data kept separate and secure from other users' data in any SaaS environment? Describe how data is kept separate and secure in the comment section. | 5 - High | Future | fail | |||
| 7 | Architecture | The proposer will certify that FWWD maintains ownership rights of the data upon termination of business relationship. | 5 - High | Both | fail | |||
| Architecture | Flexibility and capacity to add user-defined fields at the following data set levels? Please provide the number of user-defined fields in the comment column. | |||||||
| 8 | Architecture | - Customer. | 5 - High | Future | fail | |||
| 9 | Architecture | - Account. | 5 - High | Future | fail | |||
| 10 | Architecture | - Premises. | 5 - High | Future | fail | |||
| 11 | Architecture | - Service. | 5 - High | Future | fail | |||
| 12 | Architecture | - Asset (including meters, registers, radios, backflow, grease trap, etc.) | 5 - High | Future | fail | |||
| Architecture | External Systems Integration and Interfacing: | |||||||
| 13 | Architecture | System support API integrations? Please provide a list of the specific API types supported in the comment column. | 5 - High | Current | fail | |||
| 14 | Architecture | The ability to directly connect to third-party vendors / systems securely using methods and protocols such as SFTP to retrieve and transmit data files. Please provide type/level of encryption in the comment column. | 5 - High | Current | fail | |||
| 15 | Architecture | The ability to interface with existing enterprise service bus. MuleSoft is the current integration and automation solution at FWWD. MuleSoft's AnyPoint Platform supports API-led connectivity. | 5 - High | Current | pass | |||
| 16 | Architecture | The ability to support multiple end point devices: Does the proposed solution support platforms such as Microsoft Windows, Linux, Android, iOS, etc.? Please provide a list of the supported platforms in the comment column. | 5 - High | Current | pass | |||
| Architecture | Network | |||||||
| Architecture | The ability for utility technical staff to add and configure: Please use the comment column to add specific information as needed. | |||||||
| 17 | Architecture | - Custom edits for data fields. | 5 - High | Current | pass | |||
| 18 | Architecture | - Pop-up alerts based on events or data criteria. | 5 - High | Current | pass | |||
| 19 | Architecture | - Launching a URL from within the CIS (by a user). | 5 - High | Current | pass | |||
| 20 | Architecture | - Field level validation rules (including the use of tables, input masking and expressions). | 5 - High | Current | pass | |||
| 21 | Architecture | - Field level validation rules includes masking and regular logical expressions. | 5 - High | Current | pass | |||
| Scalability | ||||||||
| 22 | Scalability | The ability to support multiple users: Does the system accommodate a maximum number of users per module and/or overall? Please provide the maximum number of users for each module and/or overall in the comment column. | 5 - High | Current | pass | |||
| 23 | Scalability | The ability to scale: Is the solution scalable in terms of customer accounts? Please provide any potential limits FWWD might experience and under what conditions in the comment column. | 5 - High | Current | pass | |||
| 24 | Scalability | The ability to scale up: Are there specific points at which additional software licenses are required to scale up the system? Please provide a list of these points in the comment column. | 5 - High | Current | pass | |||
| 25 | Scalability | The ability to manage system scale: Are there any consequences if a customer exceeds their allocated system size/scale? Please provide a list of these consequences in the comment column. | 5 - High | Current | pass | |||
| Reliability | ||||||||
| 26 | Reliability | The ability to manage antivirus and malware: Are there any known issues with antivirus and anti-malware software? Please provide a list of any known issues in the comment column. | 3 - Medium | Current | pass | |||
| Reliability | The ability to audit fields: Does the system have the capability for FWWD to view and/or provide audit logs at the following field levels? | |||||||
| 27 | Reliability | - Prior value | 5 - High | Current | fail | |||
| 28 | Reliability | - New value | 5 - High | Current | fail | |||
| 29 | Reliability | - Date/time of change | 5 - High | Current | fail | |||
| 30 | Reliability | - User ID making the change | 5 - High | Current | fail | |||
| 31 | Reliability | - User IP address of user making change | 5 - High | Current | fail | |||
| 32 | Reliability | The ability to manage system history: Are there processes and functions where increasing amounts of history on the system might affect user response time? Please provide a list of these processes and functions and your resolution in the comment column. | 5 - High | Current | pass | |||
| 33 | Reliability | The ability to insert an ad hoc batch job into the day's job run. | 5 - High | Current | fail | |||
| 34 | Reliability | The ability to avoid impact of batch job production on other daily activities if batch processing is scheduled during normal business hours. | 5 - High | Current | fail | |||
| 35 | Reliability | The ability to add accounts in mass: Does the CIS system support the ability to add accounts in bulk? FWWD may use this ability when a new service area is annexed or acquired, during system upgrades or migrations, or when integrating data from external sources. | 3 - Medium | Current | pass | |||
| 36 | Reliability | The ability to process bulk changes (i.e. premises or street name). | 3 - Medium | Current | pass | |||
| Performance | ||||||||
| 37 | Performance | System provides a sub-second response time for all online transaction processing for common customer account services. | 5 - High | Current | pass | |||
| 38 | Performance | The ability to access data files at the same time without collision or file / record / field locking problems. | 5 - High | Current | pass | |||
| 39 | Performance | The ability to generate standard reports efficiently: Please provide a list of any reports that require significant time to run and additional details in the comment column. | 5 - High | Current | pass | |||
| 40 | Performance | The ability to perform triage and provide early warning detection: Does the system have performance triage and early warning detection processes in place, along with collaboration steps with the FWWD support team to resolve issues? | 5 - High | Current | pass | |||
| 41 | Performance | The ability to respond efficiently to queries: Please provide more details on query performance in the comment column. | 5 - High | Current | pass | |||
| 42 | Performance | The ability to support required desktop applications: Are there any required desktop applications and associated licensing needs for the overall solution? Please provide a list of the required applications, their licensing requirements, and the supported versions in the comment column. | 5 - High | Current | pass | |||
| 43 | Performance | The ability to meet hardware requirements: Are there minimum hardware requirements necessary for the software to run optimally for FWWD office, remote, and field staff? Please provide a list of the minimum hardware requirements in the comment column. | 5 - High | Current | pass | |||
| Maintenance | ||||||||
| 44 | Maintenance | The ability to install new point releases: Is there a typical time required to install a new point release of the software in various environments (development, test, training, production and on-premise reporting)? Please provide the estimated times for each environment in the comment column. | 5 - High | Current | pass | |||
| 45 | Maintenance | The ability to preserve and migrate application modifications: Does the system support preservation and migration of FWWD-specific application modifications via version control, while prioritizing configuration over customization? Please provide details in the comment column. | 5 - High | Current | pass | |||
| 46 | Maintenance | The ability to version control custom reports and interfaces and manage the migration of those application components during software version changes. | 5 - High | Current | pass | |||
| 47 | Maintenance | The ability to version control FWWD's customization and manage the migration of those application components during software version changes. | 5 - High | Current | pass | |||
| 48 | Maintenance | The ability to support report writers: Does the system support report writers? Please provide a list of the supported report writers in the comment column. | 5 - High | Current | pass | |||
| Security | ||||||||
| 49 | Security | The ability to support sign-on authorization: Does the system support user single sign-on (e.g., Active Directory and/or Federated sign-on)? Please provide details of the supported sign-on methods in the comment column. | 5 - High | Future | fail | |||
| 50 | Security | The ability to utilize Lightweight Directory Access Protocol (LDAP) to query Active Directory for user validation and authentication. | 5 - High | Current | fail | |||
| 51 | Security | The ability for each component to support SAML 2.0 for internal and external applications. | 3 - Medium | Current | fail | |||
| 52 | Security | The system must support the ability to mask sensitive information such as date of birth (DOB), social security numbers, and driver's license numbers, while also identifying any limitations related to masking. Please use the comment column to explain these capabilities and limitations | 5 - High | Current | fail | |||
| 53 | Security | The ability to manage regulatory field associations: Does the system allow FWWD to configure regulation-to-field associations and disable specific system functionality to reduce regulatory exposure? | 5 - High | Current | fail | |||
| 54 | Security | The ability to support data encryption: Are there recommended data encryption methods applicable across all solutions (CIS, Mobile, AMI data, telephony, etc.)? Please explain in the comment column. | 5 - High | Current | fail | |||
| 55 | Security | The system must support configurable cryptographic algorithms and mechanisms to ensure data protection and compliance with industry standards. This includes compatibility with encryption protocols, hashing algorithms, and authentication mechanisms. Vendors must specify the supported algorithms. | 5 - High | Current | fail | |||
| 56 | Security | The ability to implement future cryptographic algorithms: Does the system have a roadmap for implementing future cryptographic algorithms or mechanisms? Please provide details in the comment column. | 5 - High | Current | fail | |||
| 57 | Security | The ability to support vulnerability disclosure policy. Vendor reporting on system vulnerabilities is required for Federal reporting needs by the FWWD. | 5 - High | Current | fail | |||
| 58 | Security | The ability to configure security levels: Does the system support multiple levels of security, including group, role, user, and field-level security? Please provide details in the comment column. | 5 - High | Current | fail | |||
| 59 | Security | The ability to store and transmit passwords in encrypted form. | 5 - High | Future | fail | |||
| 60 | Security | The ability to support password and access controls: Does the system support password complexity rules, role-based or group-based access to data, and self-service password capabilities? Additionally, does it support OKTA for MFA as required by FWWD and CoFW? Please use the comment column to explain. | 5 - High | Current | fail | |||
| Security | The system must provide granular access controls to restrict and manage access based on the following criteria: | |||||||
| 61 | Security | - Department. | 5 - High | Current | fail | |||
| 62 | Security | - Division. | 5 - High | Current | fail | |||
| 63 | Security | - User ID. | 5 - High | Current | fail | |||
| 64 | Security | - Screen. | 5 - High | Current | fail | |||
| 65 | Security | - Menu. | 5 - High | Current | fail | |||
| 66 | Security | - Report. | 5 - High | Current | fail | |||
| 67 | Security | - Database table. | 5 - High | Current | fail | |||
| 68 | Security | - Object. | 5 - High | Current | fail | |||
| 69 | Security | - Record. | 5 - High | Current | fail | |||
| 70 | Security | - Field. | 5 - High | Current | fail | |||
| 71 | Security | - Job function / Role | 5 - High | Current | fail | |||
| 72 | Security | - Element in chart of accounts. | 5 - High | Current | fail | |||
| 73 | Security | - Customer group. | 5 - High | Current | fail | |||
| 74 | Security | - Transaction type. | 5 - High | Current | fail | |||
| 75 | Security | - User defined fields (e.g. Business Unit, Company Code, Billing Partner/Political Entity). | 5 - High | Current | fail | |||
| 76 | Security | The ability to allow FWWD to determine which fields are visible to which users. | 3 - Medium | Future | pass | |||
| 77 | Security | The ability to update all security roles automatically when a change in the "master" role is made. | 5 - High | Current | fail | |||
| 78 | Security | The ability to allow system hardware to integrate security and file system permissions within an LDAP (Active Directory) environment and capabilities for Active Directory integration and roles/access inheritance. | 3 - Medium | Future | pass | |||
| 79 | Security | The ability to allow the System Administrator to add and change permissions for system access. Is there a limit to number of System Administrator? | 5 - High | Current | fail | |||
| 80 | Security | The ability to allow a System Module Administrator to add and change permissions for module access. | 5 - High | Current | fail | |||
| 81 | Security | The ability to log users off the system after an administrator-defined period of inactivity, based on user-defined roles. What are the temporary access or special access abilities with time limit and access limits. Please explain in the comment column. | 5 - High | Current | fail | |||
| 82 | Security | The ability to allow a System Administrator to log out users. | 5 - High | Current | fail | |||
| 83 | Security | The ability to provide customizable audit reports. | 5 - High | Current | fail | |||
| 84 | Security | The ability to provide configurable exception reports. | 5 - High | Current | fail | |||
| 85 | Security | The ability to allow authorized users to have access to a log of security activity to determine users that have signed on and off the system, as well as unsuccessful attempts to sign on to the system. | 5 - High | Current | fail | |||
| 86 | Security | The ability to synchronize with a centralized time server. | 1 - Low | Current | pass | |||
| 87 | Security | The ability to meet PADSS (Payment Application Data Security Standards) compliance standards. | 5 - High | Current | fail | |||
| 88 | Security | The ability for security to replicate over support multiple business continuity environments, with replicated system data. | 5 - High | Current | fail | |||
| 89 | Security | The ability to allow a user to configure which business process are prompted with a warning to proceed, with appropriate security permissions. | 3 - Medium | Current | pass | |||
| User Interface | ||||||||
| 90 | User Interface | The ability to provide drop down boxes and "pick lists" for data selection, based on user permissions. | 5 - High | Current | fail | |||
| 91 | User Interface | The ability to comply with accessibility standards defined in the Americans with Disabilities Act (ADA) in order to provide a more seamless experience for the user including customer self-service portals and field mobile apps. | 5 - High | Current | fail | |||
| 92 | User Interface | The ability to provide functional online help documentation for system end users. | 5 - High | Current | fail | |||
| 93 | User Interface | The ability to provide technical online help documentation for system administrators. | 5 - High | Current | fail | |||
| 94 | User Interface | The ability to integrate with a tool to copy / paste data, with appropriate security permissions. Provide the supported tools in the comments. | 5 - High | Current | pass | |||
| 95 | User Interface | The ability to provide error messages that appear in a consistent format across all system modules. | 5 - High | Current | fail | |||
| 96 | User Interface | The ability to provide error messages that are integrated with online help functionality. | 5 - High | Current | pass | |||
| 97 | User Interface | The ability to create error logs with details associated with the error. | 5 - High | Current | fail | |||
| 98 | User Interface | The ability to allow users to send error reports to FWWD Water IT. Describe how error reports are delivered in comments section. | 3 - Medium | Current | pass | |||
| 99 | User Interface | The ability to customize tool tips and/or user error messages. | 5 - High | Current | pass | |||
| 100 | User Interface | The ability to provide user-defined fields, including field masking and formatting options, with appropriate security permissions. | 5 - High | Current | fail | |||
| 101 | User Interface | The ability to allow FWWD to determine which fields are required. | 5 - High | Current | fail | |||
| 102 | User Interface | The ability to provide an administrative messaging system (e.g. a message to alert users of system maintenance activity). | 5 - High | Current | fail | |||
| 103 | User Interface | The ability to provide customizable screens based on roles and permissions. | 5 - High | Current | fail | |||
| 104 | User Interface | The ability to provide customizable screens including moving rows and columns, locking fields, and freeze columns based on roles and security permissions. | 5 - High | Current | pass | |||
| 105 | User Interface | The ability to provide contextual help with the ability to turn this feature off (i.e. field descriptions that are displayed based on the location of the mouse or cursor). | 5 - High | Current | pass | |||
| 106 | User Interface | The ability to provide customizable knowledge database functionality. | 5 - High | Current | fail | |||
| 107 | User Interface | The ability to provide data validation on entry | 5 - High | Current | fail | |||
| 108 | User Interface | The ability to attach files to Customer, Account, Location records. Describe in the comments the data hierarchy that files can be attached. | 5 - High | Current | fail | |||
| 109 | User Interface | The ability to provide drill down capability on all screens with appropriate security. | 5 - High | Current | fail | |||
| 110 | User Interface | The ability to provide drill down capability to see attachments to records based on security permissions. | 5 - High | Current | fail | |||
| 111 | User Interface | The system allows a user screen to have an option for the number of records that will be displayed (i.e. 25, 50, 100 search results with the option to choose how many). | 5 - High | Current | pass | |||
| 112 | User Interface | System-wide limitations for number of search results that can be displayed. | 5 - High | Current | pass | |||
| 113 | User Interface | The ability to provide the user with standard field editing capabilities including but not limited to, navigation forward and backward to complete data entry. Provide your approach in the Comments section. | 5 - High | Current | fail | |||
| 114 | User Interface | The ability to easily use tab key through fields to quickly navigate. | 5 - High | Current | fail | |||
| 115 | User Interface | The ability to easily configure graphical user interface through web browser favorites. | 5 - High | Current | pass | |||
| 116 | User Interface | The ability to easily view all relevant accounts accessed by the user. | 5 - High | Current | fail | |||
| 117 | User Interface | The ability to configure and add workspaces/work queues and assign to users or user groups / roles. | 5 - High | Current | fail | |||
| 118 | User Interface | The ability to easily develop customized and modify existing "help" functionality and associate it with the appropriate context within the system. | 3 - Medium | Current | pass | |||
| 119 | User Interface | The ability to spell check on any field, including user defined field, with the ability to turn this feature on and off. | 5 - High | Current | fail | |||
| 120 | User Interface | The ability to maintain a stop-word functionality to prevent certain words or phrases from entering the system. | 5 - High | Current | fail | |||
| 121 | User Interface | The ability to allow an administrator to configure the dictionary within the system that drives the spell check functionality. | 5 - High | Current | fail | |||
| 122 | User Interface | The ability to accommodate word-wrap in a data field without having to hit "return". | 5 - High | Current | fail | |||
| 123 | User Interface | The ability to search by wild cards, based on security permissions. | 5 - High | Current | fail | |||
| 124 | User Interface | The ability to support pre-filled fields in appropriately pre-formatted screens eliminating redundant data entry. | 5 - High | Current | fail | |||
| 125 | User Interface | The ability to provide links to associated modules from any display screen to minimize backing out of one screen to access another, with appropriate security. | 5 - High | Current | fail | |||
| 126 | User Interface | The ability to support access from employee mobile devices outside the FWWD network using web interface with appropriate security permissions. FWWD employees have smartphones, tablets, and laptops for authorized remote access. | 5 - High | Current | fail | |||
| 127 | User Interface | The ability for multiple windows to be open at the same time without having to log in to the system multiple times. | 5 - High | Current | pass | |||
| 128 | User Interface | The ability to warn a user that they are about to execute a process and ask if they want to proceed. | 1 - Low | Future | pass | |||
| 129 | User Interface | The ability to configure a warning to a user that they are about to delete information and ask if they want to proceed. | 1 - Low | Future | pass | |||
| 130 | User Interface | The system has the ability to allow split screen views on dual monitors. | 5 - High | Current | pass | |||
| 131 | User Interface | The ability to allow the configuration of processes using either the keyboard only, the mouse only, or a combination of the two, depending on a user's preference. | 1 - Low | Future | pass | |||
| 132 | User Interface | The ability to provide the user with integrated application modules that offer a consistent user interface to minimize user training and administration of the system. | 5 - High | Future | fail | |||
| Content Management | ||||||||
| 133 | Content Management | The ability to provide integrated content management functionality across all system modules. | 5 - High | Future | fail | |||
| 134 | Content Management | The ability for established system security to apply to documents stored in the content manager (i.e. some documents will not be viewable to all users). | 5 - High | Current | fail | |||
| 135 | Content Management | Does the content management system support storing and managing files in multiple formats? Please specify the range of formats supported and any limitations in the comment column. | 5 - High | Current | pass | |||
| 136 | Content Management | The ability for the content manager to store audit trail information of events associated with documents stored (i.e. user, date, time, etc.). | 5 - High | Current | fail | |||
| 137 | Content Management | The ability to provide content management functionality that allows search of all documents stored. | 5 - High | Current | pass | |||
| 138 | Content Management | The ability to allow access to all documents stored in the content manager when a user is remotely using the system through a web interface with proper security, assuming the remote device has the appropriate software available to support document viewing (PDF viewer, for example). | 5 - High | Current | fail | |||
| Records Management | ||||||||
| Records Management | For each module to be provided under this system: | |||||||
| 139 | Records Management | - The ability to define and store a set of customized standard records retention policies, otherwise known as the records retention and disposition schedule. FWWD's retention is based on the Texas State Library Archives Commission retention requirements. | 5 - High | Future | fail | |||
| 140 | Records Management | - The ability the support a manual run or automated, systematic and auditable records disposal. | 5 - High | Future | fail | |||
| 141 | Records Management | - The ability to apply a records retention and disposition schedule to every record set or type, including retention period and trigger. | 5 - High | Future | fail | |||
| 142 | Records Management | - The ability to execute records retention and disposition schedule instructions, for example deletion/purge, retain indefinitely, transfer, etc. | 5 - High | Future | fail | |||
| 143 | Records Management | - The ability to record/document any deletion or disposal action comprehensively in the process metadata. | 5 - High | Future | fail | |||
| 144 | Records Management | - The ability to lock or freeze aggregations of records to prevent relocation, deletion or modification when circumstances require, for example, pending legal action or audit. | 5 - High | Future | fail | |||
| Customer Engagement | ||||||||
| 145 | Customer Engagement | The ability to support Chatbot functionality. | 3 - Medium | Future | pass | |||
| 146 | Customer Engagement | The ability of the system to support co-browsing and/or viewing of a customer's current portal screen. Define limitations, if any, such as secured fields and/or custom-designed portal extensions. | 3 - Medium | Future | pass | |||
| 147 | Customer Engagement | The ability to integrate with the telephone system for scheduling a call-back and/or put on a virtual hold. | 5 - High | Current | pass | |||
| Support and Documentation | ||||||||
| 148 | Support and Documentation | The ability to provide online software documentation for all software application modules. | 5 - High | Current | pass | |||
| 149 | Support and Documentation | The vendor offers access to an online user group community and user conference. | 5 - High | Current | pass | |||
| 150 | Support and Documentation | The vendor offers a suite of online training modules. | 5 - High | Current | pass | |||
| 151 | Support and Documentation | The vendor offers periodic live webinar training. Please describe including if they is an associated cost. | 5 - High | Current | pass | |||
| 152 | Support and Documentation | The vendor offers recorded training sessions to be viewed at no cost. | 5 - High | Current | pass | |||
| 153 | Support and Documentation | The vendor offers an implementation project management methodology/tools/website, that includes SFTP process for file sharing between the vendor and client. | 1 - Low | Current | pass | |||
| 154 | Support and Documentation | The ability for FWWD-requested enhancements collection, evaluation, prioritization, development, and implementation. | 1 - Low | Future | pass | |||
| Reporting and Dashboarding | ||||||||
| 155 | Reporting and Dashboarding | The ability to query on all data fields in the system to provide a user defined query screen. | 1 - Low | Future | pass | |||
| 156 | Reporting and Dashboarding | The ability to provide operational dashboard(s) and executive-level performance dashboard. | 3 - Medium | Future | pass | |||
| 157 | Reporting and Dashboarding | The ability to customize the information presented on the Executive Information System by user. | 3 - Medium | Future | pass | |||
| 158 | Reporting and Dashboarding | The ability to display information based on real-time operational data in combination with the Executive Information System. | 3 - Medium | Future | pass | |||
| 159 | Reporting and Dashboarding | The ability to provide an integrated report writer that has a consistent look and feel across all system modules. | 5 - High | Future | pass | |||
| 160 | Reporting and Dashboarding | The ability to send emails and reports to be saved in an integrated content manager. Include report file types / formats in the comments section. | 5 - High | Current | fail | |||
| 161 | Reporting and Dashboarding | The ability to allow generated reports to be viewed on screen prior to printing. | 5 - High | Current | fail | |||
| 162 | Reporting and Dashboarding | The ability to allow reports generated to be searchable. | 3 - Medium | Future | fail | |||
| 163 | Reporting and Dashboarding | The ability to schedule reports to run in the future. | 5 - High | Current | fail | |||
| 164 | Reporting and Dashboarding | The ability to run scheduled queries for data extract on a pre-determined basis. | 5 - High | Current | fail | |||
| 165 | Reporting and Dashboarding | The ability to configure automatic distribution paths for generated reports (i.e. automatically send a report to a user). | 5 - High | Current | fail | |||
| 166 | Reporting and Dashboarding | The ability to display when a report is being run, or in process, so that a user does not run the report again. | 5 - High | Current | pass | |||
| 167 | Reporting and Dashboarding | The ability to configure the page breaks for any printed report. | 3 - Medium | Current | pass | |||
| 168 | Reporting and Dashboarding | The ability to notify users when a specific number of pages in a report will be printed. | 3 - Medium | Current | fail | |||
| 169 | Reporting and Dashboarding | The ability to allow users to cancel the printing of the report. | 5 - High | Future | fail | |||
| 170 | Reporting and Dashboarding | The ability to allow reports generated to have "drill-down" capabilities. | 5 - High | Current | pass | |||
| 171 | Reporting and Dashboarding | The ability to create ad hoc queries using a query builder or a SQL statement for authorized users | 5 - High | Current | fail | |||
| 172 | Reporting and Dashboarding | The ability to allow a user to modify existing reports, with appropriate security permissions. | 5 - High | Current | fail | |||
| 173 | Reporting and Dashboarding | The ability to modify copies of standard reports and prevent modification of standard reports with appropriate security permissions. | 5 - High | Current | fail | |||
| 174 | Reporting and Dashboarding | The ability to include user-defined fields in queries, reports and dashboards. | 5 - High | Current | fail | |||
| 175 | Reporting and Dashboarding | The ability to preserve system reports (not ad hoc reports) to support report audits. | 5 - High | Current | pass | |||
| 176 | Reporting and Dashboarding | The ability to export files in multiple formats (e.g. .csv, .txt). Please list formats in the comments section. | 5 - High | Current | fail | |||
| 177 | Reporting and Dashboarding | The ability to export data from system at user defined frequencies, i.e. hourly, daily, etc. | 5 - High | Current | fail | |||
| Contact Center | ||||||||
| 178 | Contact Center | The ability to integrate with the phone system (i.e. AVAYA platform), so that the call recording / screen recording administration (indicating which extensions should be recorded) occurs centrally rather than recording at the agent's desktop. | 5 - High | Current | pass | |||
| 179 | Contact Center | The ability to store video from the recordings on a server rather than on the agent's desktop. | 5 - High | Current | pass | |||
| 180 | Contact Center | The ability to store audio from the recordings on a server rather than on the agent's desktop including live screen monitoring and audio monitoring options | 5 - High | Current | pass | |||
| Other | ||||||||
| 181 | Other | The ability to support virtual (electronic) signatures by customers or staff when required on electronic documents and storing, securing/protecting that information. | 5 - High | Future | pass | |||
| 182 | Other | The ability to support international mailing addresses, including APO. | 5 - High | Current | pass | |||
| 183 | Other | The ability to support international phone numbers. | 3 - Medium | Current | pass |
&"Arial,Bold"&12Ft. Worth Water CIS Replacement Technical Requirements
&P
Data Validation List
| Technical Score | |
| Available Out of the Box | 10 |
| Requires Configuration | 7 |
| Requires Customization | 3 |
| Not Answered or Not Available | 0 |
| Core or Non-core |
(Respond if score = 3 = Requires Customization)
| Core |
| Non-Core |
| Included in the Proposed price (Y/N) |
| Yes |
| No |
File details come from the government source that posted it. Updated .