The file's text, extracted by GovTribe without its formatting.
EXHIBIT D
TECHNICAL REQUIREMENTS & CHECK LIST
| F |
| Fully functional, provided "Commercial Off-The-Shelf (COTS)" |
| CU |
| Customization (Change to source code required) |
| CO |
| Configuration (Setup required with built-in tools and procedures but no change to source code is required.) |
| TP |
| Third-Party (Additional software required to provide Requirement.) |
| R |
| Provided with Reporting Tool |
The Vendor must complete this checklist by indicating at what level each requirement can be met. Please respond by entering the appropriate Key code next to each requirement. Vendors should also use the comments section to further explain how their proposed solution meets the requirement.
| Req. No. |
| Requirement | |
| Key* | |
| Comments | |
| D.1.1 |
| General Application Requirements |
| D.1.1.1 |
| Vendor applications are compatible or can co-exist, with the County's technical environment (see Section 3.0) |
| D.1.1.2 |
| Vendor proposed system is able to run concurrently with County standard workstation Windows applications (see Technology Standards section), subject to processor and memory limitations. |
| D.1.1.3 |
| Vendor proposed system is able to run Citrix Zen App 6.5 environment. |
| D.1.1.4 |
| All data for the proposed system should be directly accessible from major industry standard data access tools for potential use in reporting and integration with other County systems. |
| D.1.1.5 |
| The proposed system must maintain data integrity and prevents data loss or corruption. |
| D.1.1.6 |
| The proposed system must utilize graphical user interface (GUI), which is intuitive to operate for both novice and experienced users. |
| D.1.1.7 |
| The proposed system application must demonstrate that technology infrastructure is in place to insure full compliance with the Health Insurance Portability and Accountability Act (HIPAA), consistent with County HIPAA policies. Vendor must enter into a HIPAA Business Associate Agreement with the County, should they be the successful Vendor, as defined in Federal regulations and Walworth County Administrative Procedures. |
| D.1.1.8 |
| The proposed solution must be able to utilize the SAN environment for the storage of data. |
| D.1.1.9 |
| The County shall be entitled to any and all upgraded versions of the proposed system covered in the contract which becomes available from the Vendor. The Vendor must provide free and timely upgrades to the software when published. |
| Req. No. |
| Requirement | |
| Key* | |
| Comments | |
| D.1.1.10 |
| Any software product(s) provided under the contract shall be the latest version available to the general public as of the due date of this solicitation. |
| D.1.1.11 |
| Any software product(s) provided under the contract shall perform unattended system and data backup operations on an administrator-scheduled basis. |
| D.1.1.12 |
| The proposed system should provide a browser interface. |
| D.1.1.13 |
| The proposed system should provide interfaces and/or integration with other applications, and make use of Service-oriented Architecture (SOA). |
| D.1.1.14 |
| Vendor application should provide ability to assign default values for enterable fields, whenever possible. This includes defaulting User ID fields to the currently signed-on user, department fields to the current user’s department, and date fields to the current date, when appropriate. |
| D.1.1.15 |
| The proposed system should identify or differentiate information by a means other than color. |
| D.1.1.16 |
| The proposed system should have the capability to present users with tools which are relevant in the current context, eliminating or disabling irrelevant tools. It should use progressive disclosure to reveal information as it is needed and give users the option to hide information they don’t consider useful. |
| D.1.1.17 |
| The proposed system should have the capability to identify individual table entries as expired and no longer usable in the entry of new records, but still valid for display of existing records. |
| D.1.1.18 |
| The proposed system functionality should provide intelligent support related to drop-down table entries. For example, it should be possible to select items in a list by clicking on the desired choice or typing as much of the item description as is needed to uniquely identify it (similar to the Microsoft Outlook address book). It should be possible to type an exact value into a table-validated field. |
| D.1.1.19 |
| The proposed system should ensure key data persists as the user moves from one window (screen) to the next, to minimize re-entry and mistakes. |
| D.1.1.20 |
| The proposed system should provide means to validate column data by checking entered values against a list of valid values maintained in tables by County or service provider personnel. |
| D.1.1.21 |
| The proposed system should utilize meaningful abbreviations in Table structures, i.e. use of abbreviations that also displays clear descriptions of the information they represent which are intelligible to a novice user. The proposed system should not display codes that are meaningless or abbreviations so short as to be meaningless. |
| D.1.1.22 |
| The proposed system should provide the capability for defined user groups to configure custom data validation rules to meet specific needs. |
| D.1.1.23 |
| The proposed system should be interoperable with other Windows applications, support Dynamic Data Exchange (DDE), support saving data in industry-standard file formats, use standard protocols for data interchange, i.e. extensible markup language (XML), and provide data import and export capabilities. |
| Req. No. |
| Requirement | |
| Key* | |
| Comments | |
| D.1.1.24 |
| The proposed system should be capable of importing files for mass-loading of data. Data formats should include standard delimited types that can be generated by MS-Excel or other data tools (i.e. CSV files). |
| D.1.1.25 |
| Ability for licensed users to access and view records from locations outside County facilities. Remote access is supported and conforms to HIPAA and other security requirements. |
| D.1.2.1 |
| The DBMS for the proposed system should be MS-SQL Server 2008 R2. |
| D.1.2.2 |
| The proposed system should utilize standard database back-end, i.e. SQL Server. The data tables should allow insertion of data from a third party tool, i.e. Digital Transformation Services (DTS) or SQL Server Integration Services (SSIS), for at least basic setup of tables or synchronization points, i.e. vendor lists, contacts, etc. |
| D.1.3.1 |
| The County uses TCP/IP and Ethernet over a Local Area Network (LAN) sub netted into multiple VLANs. The network operating system is Windows 2008/2012, using Active Directory, Domain Name System (DNS) for address resolution and Dynamic Host Configuration Protocol (DHCP) for address assignment. The backbone is Gigabit Ethernet with desktops connected at 100 megabits. |
| D.1.3.2 |
| If the proposed system interfaces to an existing user electronic mail system, the interface must be Messaging Application Programming Interface (MAPI) or Simple Mail Transfer Protocol (SMTP) compliant. |
| D.1.3.3 |
| Vendor must acknowledge their proposed system runs satisfactorily on an Ethernet network. |
| D.1.3.4 |
| The proposed system must be able to operate with an Internet connection that is currently rate-limited to 50Mb/s. 800 users share this 50 Mb/s connection. |
| D.1.3.5 |
| If the proposed system requires remote access from a mobile workstation, Vendor must describe the requirements of their proposed system’s remote access from a mobile workstation. |
| D.1.4 |
| Security / Administration |
| D.1.4.1 |
| Security capability must exist, such that access to all components of the proposed system shall be only granted to authenticated users. |
| D.1.4.2 |
| Authorized users of the proposed system must be identified by a User ID and Password or another means that provides equivalent or better security. |
| D.1.4.3 |
| The system administrator must be able to establish new users on the system, to remove users from the system, and to set security access rights for users that both restrict and allow access to system capabilities. |
| D.1.4.4 |
| The system administrator must be able to lock user accounts based on inactivity. |
| D.1.4.5 |
| The system must provide multilevel security that protects records and restricts access to selected records. |
| Req. No. |
| Requirement | |
| Key* | |
| Comments | |
D.1.4.6
The system administrator must be able to restrict access to selected system functions based on user identification.
| D.1.4.7 |
| The security system must maintain an audit trail of staff access to records as determined by the administrator. |
| D.1.4.8 |
| Must include a “break-the-glass” option for emergency access with the ability to access restricted data or to access unassigned passengers. This function must have an audit trail. |
| D.1.4.9 |
| Vendor must provide to the County Operation and Instruction Manuals in an electronic format. |
| D.1.4.10 |
| If the proposed system connects to the Internet, an industry accepted level of encryption must be used for data transmissions. |
| D.1.4.11 |
| The proposed system must not transmit User ID’s or passwords in clear text. |
| D.1.4.12 |
| If the system resides in Walworth County’s secure computer facility and remote access to the system is required, access will be provided through a Virtual Private Network (VPN) with two (2) factor authentication. Remote Vendor access for support must be accomplished through secured methods. |
| D.1.4.13 |
| Vendor application security must effectively block unauthorized users from accessing the application by any means. |
| D.1.4.16 |
| The proposed system should disable a user account if a defined number of unsuccessful logon attempts are made within a defined time period. |
| D.1.4.17 |
| If the proposed system is to reside in Walworth County’s secure computer facility, the proposed system should use Microsoft’s Active Directory for user authentication and authorization. |
| D.1.4.18 |
| The proposed system should support the current County standard of an eight or nine-character alphanumeric User ID.8.2 |
| D.1.4.19 |
| Vendor system should allow users to change their passwords. |
| D.1.4.20 |
| Vendor system should provide the capability to establish a user account that requires the password be changed the next time the user logs on. |
| D.1.4.21 |
| Vendor system should provide the capability to set rules for password strength. It should restrict users from reusing recent passwords. |
| D.1.4.22 |
| Vendor system should have the capability to expire user passwords after a set time period. |
| D.1.4.23 |
| The password field should require alphanumeric/special character values at a minimum of eight (8) characters long. Vendor system’s password format should allow County to specify the minimum password length. |
| D.1.4.24 |
| The proposed system should limit access to individual system functions and reports to authorized users. |
| D.1.4.25 |
| The proposed system should provide the capability to track (audit) user activity. |
| D.1.4.27 |
| The proposed system should automatically log users off of the application running on a workstation after a defined period of inactivity on that workstation. |
| Req. No. |
| Requirement |
| Key* |
| Comments |
| D.1.5.1 |
| The proposed system must permit operating system patching and updates, and allow for a system restart when a patch or update requires it. |
| D.1.5.2 |
| The proposed system must be able to operate on Microsoft Windows 2008 R2 Server with latest Service Pack. |
| D.1.5.4 |
| The proposed system must operate on Microsoft Internet Information Server. |
| D.1.5.5 |
| The proposed system must operate and fully support running in the VMware Virtual Server environment. |
| D.1.5.6 |
| The proposed system must cooperate satisfactorily with the County’s current antivirus software and permit automatic antivirus definition updates. The current antivirus software is Symantec End Point. |
| D.1.5.7 |
| Any web application components of the proposed system should use .NET 4.0 Framework. |
| D.1.6.1 |
| Vendor systems that are located in the County computer facility and managed by the County for backup and recovery are required to utilize the Walworth County back up facility. Walworth County will use the following backup system: Unitrends. |
| D.1.7.1 |
| Capability to interface and exchange data with industry standard query tools. |
| D.1.8 |
| Implementation Requirements |
| D.1.8.1 |
| The system specified in the contract shall be considered ready for testing upon receipt of documentation from the Vendor that a successful system audit or diagnostic test was performed at the site demonstrating that the system meets the minimum design/performance capabilities stipulated in the purchase agreement. |
| D.1.8.3 |
| The Vendor must guarantee that the recommended hardware configuration shall meet the functional needs of the Department for the first two years of operation. |
| D.1.8.4 |
| Vendor shall include in the Implementation Plan the ways and means of how the implementation shall be managed, including, but not limited to schedule, risk, and quality. |
| D.1.8.5 |
| Vendor shall include in the Implementation Plan the descriptions of the vendor roles and responsibilities during the solution implementation. |
| D.1.8.6 |
| Vendor shall include in the Implementation Plan the descriptions of the County roles and responsibilities during the solution implementation. |
| D.1.8.7 |
| Vendor shall state in the Implementation Plan assumptions and expectations for both the vendor and County stakeholders, in order to reduce any and all ambiguity during the implementation. |
| Req. No. |
| Requirement | |
| Key* | |
| Comments | |
| D.1.8.8 |
| Vendor shall include in the Implementation Plan the process for loading data into reference tables, such as users, roles, etc. |
| D.1.9.1 |
| Vendor shall provide application availability and technical support on a 24/7 basis. |
| D.1.9.2 |
| Vendor must provide application support by phone (toll-free), fax, and e-mail during normal business hours (8:00 A.M. - 5:00 P.M.CST, M-F). |
| D.1.9.3 |
| Upon completion of any maintenance or support call, the Vendor shall provide the agency with a signed service report that includes, at a minimum: a general statement as to the problem, action taken, and the number of hours required to complete the task, if it is a billable activity. |
| D.1.9.4 |
| The proposed system should have capability to provide a test environment so County personnel can test new versions of the system without affecting the production environment. |
| D.1.9.5 |
| Vendor training should utilize a methodology for any type of training on the proposed system without affecting production data. Any actions in the test environment should not affect the availability of the training environment. However, the training environment may share hardware used by the test or production environment. |
| D.1.9.6 |
| Vendor shall provide a comprehensive description of the technical training available to the County for the proposed system. |
| D.1.9.7 |
| Vendor shall provide a comprehensive description of the functional training available to the County for the proposed system. |
REQUESTED TECHNICAL INFORMATION
The Vendor should address these information requests with concise answers and to the best of their ability.
Comments
| D.2.1.1 |
| Vendor should describe any known dependencies on specific versions of any workstation operating system objects and any known incompatibilities between the proposed system and other commonly used workstation software. |
| D.2.1.3 |
| Vendor should describe how workflow can be configured by authorized users. Workflow elements may include, but are not limited to, report initiation, report validation, report approval and report distribution. |
| D.2.1.4 |
| Vendor should provide cost information for all server and workstation application licenses for users for both the production and test environments. |