{"text_format":"3","workbook":"xlsx","n_sheets":7,"sheets":["INSTRUCTIONS","1. GENERAL PAYMENTS","2. PAYMENTS & COLLECTIONS","3. REVENUE ACTG & WORKFLOW","4. CUSTOMER MANAGEMENT","Validation","5. TECHNICAL"],"not_rendered":{"defined_names":30},"read":"whole","date_system":"1900"}

{"sheet":"INSTRUCTIONS","index":0,"n_rows":8,"n_cols":1,"rows_kept":8,"merged":[[0,0,0,9],[1,0,1,9],[2,0,2,9],[3,0,3,9],[4,0,4,9],[5,0,5,9],[6,0,6,9],[7,0,7,9]]}
["INSTRUCTIONS"]
[]
["Offeror Response Column:\nThe Offeror shall enter “Yes” if the current release of the software can fully support ALL the functionality described in the row, out-of-the-box, without further development or modification. A “Yes” can only be used if the delivery method is Out-of-the-box or Configuration (see delivery method instructions below).           \n\nOtherwise, enter \"No.\" A \"No\" can only be used with delivery method of Third-Party Product or Custom (see delivery method instructions below)."]
["Delivery Method Column:\nComplete the delivery method using Out-of-the-box, Configuration, Third-Party Product, or Custom (as defined below) that indicates how the functional specification will be delivered.\n\nOut-of-the-box (\"O\") - Current software release of the product can be used as-is out-of-the-box, without further development or modification to meet the functional specification.\nConfiguration (\"C\") - Current software release of the product can be configured to meet the functional specification using tools and utilities inherent to the product without requiring custom programming to extend the product's capabilities.\nThird-Party Product (\"T\") - Offeror recommends a third-party product that is integrated/used with the current software release of the product to meet the functional specification.\nCustom (\"M\") - Current software release of the product can be customized to meet the functional specification via custom programming to extend the capabilities of the product."]
["Third-Party Product Column:\nThe Offeror shall specify the third-party product and the version required to meet the functional specification (for entries of “T” only). In the Comments column, specify why it is required and how it is integrated with the product. Also specify whether licensing and upgrades of the third-party product is included within the licensing and upgrades of the Offeror's System. "]
["Cost Estimate Column:\nThe Offeror shall specify the dollar amount required for third-party product or custom development of the functional specification (for entries of \"T\" or “M” only)."]
["Comments Column:\nThe Offeror shall briefly address how the features and capabilities of the System support the functional specification (limit five sentences).\n"]
["Except as noted, the specifications set forth in the Scope of Work and in this attachment are representative of the  specifications most desired by the County in a new System. However, the County understands no one system will likely meet each and every one of these specifications. The County reserves the right to determine what combination of these specifications, if all cannot be met, best meets its needs and objectives.  "]

{"sheet":"1. GENERAL PAYMENTS","index":1,"n_rows":33,"n_cols":7,"rows_kept":33,"merged":[[0,0,0,6],[1,0,1,6],[2,0,2,1],[2,2,2,6],[22,0,22,6],[24,0,24,6]]}
["GENERAL PAYMENTS "]
[]
["County Specifications",null,"Offeror"]
["#","Description","Offeror Response","Delivery Method","Third-Party Specifics \n","Cost Estimate \n(For Third-Party or Customization)","Comments \n(Limit 5 sentences)"]
["GENERAL PAYMENT REQUIREMENTS"]
[1.01,"The system shall provide the capability to accept payments for agencies with a back-office application through integration and for agencies that have no back-office applications. Describe the process from start to finish for the payment process from the customer's perspective.  ",null,null,{"$f":"IF(D6=\"Third Party Product ('T')\",\"Enter value\",\"\")","v":""}]
[1.02,"The system shall provide the capability to accept electronic payments in-house, online, by phone (IVR), and in-the-field."]
[1.03,"The proposed solution shall interface with a predefined list of back-office applications, which may change over time. Describe how the proposed solution will interface with the back-office applications to include importing/exporting data."]
[1.04,"The system shall provide customers with an electronic payment solution with 24/7/365 access to account balances and payment channels. Describe how the System will provide around-the-clock payment accessibility to customers."]
[1.05,"The system shall, at a minimum, accept credit cards, debit cards, direct debit (ABD), checks, e-checks and other payment types such as paypal and apple pay. Describe the lifecycle for each tender type that the system accepts."]
[1.06,"The system shall provide the capability to process a single payment transaction with multiple tender types. Describe the life cycle for a single payment transaction with multiple tender types from customer and backend perspective."]
[1.07,"The system shall provide the capability to process a single payment transaction for multiple account debts (I.e. taxes, utility bill, dance class). Describe the life cycle for single payment transactions for multiple account debts."]
[1.08,"The system shall require dual entry of bank account numbers for echeck and scheduled bank debit payments. The system shall mask and prevent copying of bank account numbers. Describe how the system handles dual entry of bank account numbers."]
[1.09,"The system shall identify and handle possible duplicate payments. Describe how the System identifies and handles a possible duplicate payment.   "]
[{"v":1.1,"d":"1.10"},"The system shall generate receipts for all payment transactions (one time, ABD, future, etc.).  Describe the process and output for generating receipts."]
[1.11,"Describe the process for auditing transactions from the back-office perspective."]
[1.12,"The system shall provide a shopping cart functionality; where multiple departments/agency payments can be accepted in one transaction. Describe the process for shopping cart functionality."]
[1.13,"The system shall provide the capability to configure the types of payments/products where credit card convenience fees are passed on to the customer or paid for by the County. Describe how the system handles configuring the fees for a balance with multiple account debt types (i.e. utility bills and taxes in one payment)."]
[1.14,"The system shall calculate and total all selected account balances for display during checkout."]
[1.15,"The system shall allow customers to override the system calculated payment amount and enter a new amount for each bill item and/or total balance. Describe how the system will provide a calculator to aid customers in calculating a different amount to pay, rather than paying the balance in full. "]
[1.16,"The system shall provide the capability for customers to make payments from personal electronic devices (i.e. smart phone, tablet, computer, laptop).  Describe how the System allows customers to make payments from personal electronic devices, smart phones, tablets, pay-by-text, and IVR (interactive voice response)"]
[1.17,"The system shall allow customers to store multiple credit card, bank account information, etc., for payments. Describe how the System allows customers to store credit card, bank account info, etc., for payments. Describe how the stored customer data is PCI compliant."]
["POINT OF SALE, MOBILE POINT OF SALE REQUIREMENTS"]
[1.18,"The system shall process QR codes and barcodes.  Describe how the System processes QR codes and barcodes for in-house and electronic payments. "]
["INTERFACES"]
[1.19,"The system shall track all related transactional activity to the customer, either from transactions directly made via the proposed payment system or interfaced from external payment sources. Describe how the system will track transactional activity from all payment avenues.  "]
[{"v":1.2,"d":"1.20"},"The system shall update back-office applications with payment details. Describe the process of updating back-office applications with payment details, including any integration confirmations and statuses. Describe any time delays, if any, for data being made available online or for customer submissions being ready for back-end processing. "]
[1.21,"The system shall allow County employees to assist customers by troubleshooting their inquiries. Describe the options available for County employees to troubleshoot customer inquiries."]
["Pay by Phone (IVR) Requirements"]
[1.22,"The system shall take payments through an automated IVR system. Describe the process and explain how a customer would look-up their balance due and pay accounts with a back-end receivable, and without one. "]
[1.23,"The system shall allow a County employee to push a caller into the IVR system with accounts already pre-loaded so the customer can pay without making a separate phone call. Describe the process."]
["Kiosks for Payments"]
[1.24,"A self-service payment kiosk should allow payments to post in real time, and the kiosk should accept all payment types, including cash, credit cards, debit cards, and e-checks. Explain how the kiosk will be set up. If kiosk is not included as an option then describe the method of accepting cash, credit cards, debit cards and e-checks at other locations."]

{"sheet":"2. PAYMENTS & COLLECTIONS","index":2,"n_rows":21,"n_cols":7,"rows_kept":21,"merged":[[0,0,0,6],[1,0,1,6],[2,0,2,1],[2,2,2,6]]}
[]
["PAYMENTS AND COLLECTIONS PROCESSES"]
["County Specifications",null,"Offeror"]
["#","Description","Offeror Response","Delivery Method","Third-Party Specifics \n","Cost Estimate \n(For Third-Party or Customization)","Comments \n(Limit 5 sentences)"]
["PAYMENT SCHEDULES"]
[2.01,"The system shall provide customers the capability to schedule a single or multiple future payments, installments, Automatic Bank Debits (ABD), and one time payments. Describe how the System allows scheduling of multiple billing items, installments, ABD, and future payments based on payment date and amount. "]
["PAYMENT DISTRIBUTION"]
[2.02,"The system shall allocate and post payments to the appropriate balance, accounts, receivables, penalties, fees, and update accounts based on pre-defined rules. Describe the process from start to finish for how the System allocates and posts payments to the appropriate balance, accounts receivables, penalties, or fees, and what updates are made when this occurs."]
[2.03,"The system shall provide the capability for customers to make payments without an attached receivable. Describe how the System will identify and handle payments with no receivable.  "]
[2.04,"The system shall provide the capability for customers to make payments where there is no attached receivable and the customer's input determines the amount owed. Describe how the system will handle File and Pay business taxes, where the customer's input determines the amount owed.  "]
[2.05,"The system shall track and record payments and payment statuses for a customer account. Describe what history is maintained of payments posted and pending payments."]
["DECLINED PAYMENTS, RETURNS, REFUNDS"]
[2.06,"The system shall identify, track, and record declined payments, including returned checks, declined credit cards, chargebacks and other declined payments.  Describe the System process to handle declined payments, to include one-time, recurring, and ABD payments. Describe how chargebacks/disputed charges are handled."]
[2.07,"The system shall provide the capability to configure alerts and notifications triggered by declined payments. Describe all system notifications provided for declined payments for customers and County staff.  "]
[2.08,"The system shall prevent customers and County staff from attempting to enter a check or e-check payment that has previously had a returned check. Describe the tools, notifications, and alerts available."]
[2.09,"The system shall provide the capability to restrict customers with previously declined payments. Describe the process, tools, and configurations used to restrict such customers from making payments through the customer portal."]
[{"v":2.1,"d":"2.10"},"The system shall provide the capability for customers to cancel transactions within a configurable timeframe. Describe how the System allows the cancellation of transactions and how these cancellations are processed."]
[2.11,"The system shall process refunds. This should include issuing refunds to a credit card or by ACH used for the transaction. Describe the System processes for returns and refunds, including the process for County staff to initiate a refund to the customer, and specify what updates are made once the refund is processed.   "]
[2.12,"The system shall process chargebacks. Describe the System processes for chargebacks, including the process for County staff to initiate a chargeback to the customer, and specify what updates are made once the chargeback is processed.   "]
[2.13,"The system shall provide customers the capability to request a refund.  Describe the process for customers requesting refunds through the customer payment portal."]
[2.14,"The system shall provide the capability to process prenotes. Describe the prenote process, including any customer notifications and letters generated. "]

{"sheet":"3. REVENUE ACTG & WORKFLOW","index":3,"n_rows":18,"n_cols":7,"rows_kept":18,"merged":[[0,0,0,6],[1,0,1,6],[2,0,2,1],[2,2,2,6]]}
[]
["REVENUE ACCOUNTING AND WORKFLOW PROCESSES"]
["County Specifications",null,"Offeror"]
["#","Description","Offeror Response","Delivery Method","Third-Party Specifics \n","Cost Estimate \n(For Third-Party or Customization)","Comments \n(Limit 5 sentences)"]
["GENERAL LEDGER REPORTING       "]
[3.01,"Describe the configuration available to support journal entry posting to the systems of record, including posting one transaction to multiple systems and how individual debt types are identified. ",null,null,{"$f":"IF(D6=\"Third Party Product ('T')\",\"Enter value\",\"\")","v":""}]
[3.02,"The system shall track, identify, and alert County staff to transactions that have failed to post. Describe how the System identifies transactions that have failed to post.  "]
[3.03,"The system shall generate a file in the required format to interface with the County's General Ledger system on a daily basis to record summarized transactional data. Describe the process for generating the file."]
["RECONCILIATION"]
[3.04,"The system shall generate daily cash reports for reconciliation of payments, refunds and cancelled transactions recorded to receivables by department, account type, source of payment, etc. Describe the tools, queries, and reports available to reconcile System data including the number of payment transactions and sum of the transactions."]
[3.05,"The system shall provide the capability to alert County staff when there is a mismatch in the reconciliation of daily payments recorded to the receivables and to the general ledger. Describe how the system identifies mismatch payments and alerts/notifications available . "]
["REVENUE ACCOUNTING AND WORKFLOW REPORTS"]
[3.06,"The system shall provide daily activities to multiple receivable systems and County’s system of record."]
[3.07,"The system shall provide batch settlements that do not combine debits and credits in the same batch."]
[3.08,"The system shall provide batch settlements that are separated by types of payment (card and e-check) - Each report should include the post date, account code and amount."]
[3.09,"The system shall provide daily deposit and settlement processing with multiple banking partners."]
[{"v":3.1,"d":"3.10"},"The sysem shall allow provide the ability to identify the obligation paid by a unique index or settle code"]
[3.11,"The system shall provide daily reporting of all activity by department - Including debit card, credit card, and checks."]

{"sheet":"4. CUSTOMER MANAGEMENT","index":4,"n_rows":46,"n_cols":7,"rows_kept":46,"merged":[[0,0,0,6],[1,0,1,6],[2,0,2,1],[2,2,2,6],[37,0,37,6]]}
[]
["CUSTOMER MANAGEMENT"]
["County Specifications",null,"Offeror"]
["#","Description","Offeror Response","Delivery Method","Third-Party Specifics \n","Cost Estimate \n(For Third-Party or Customization)","Comments \n(Limit 5 sentences)"]
["ELECTRONIC CUSTOMER ACCESS"]
[4.01,"The system shall give customers online access to account history. Describe what account, balance, and installment history information is available to the customer online and how it is displayed. "]
[4.02,"The system shall provide a one-time payment option with no registration and the option to register for a account. Describe the process from start to finish of a customer making a one-time payment with no account registration.  "]
[4.03,"Describe what online customer actions require confirmation or additional support from County staff, and the process for working these requests."]
[4.04,"The system shall display payment confirmations and statuses for all transactions. Describe what confirmations and statuses are provided to the customer either displayed onscreen or as electronic notification."]
[4.05,"The system shall allow customers to personalize their accounts and layout. Describe all options available for customers to personalize their account access and layout through the payment portal."]
[4.06,"The system shall provide the capability for customers to add, link, and remove accounts from their online payment account. Describe how a customer would manage their accounts."]
[4.07,"The system shall allow customers to access only their own account(s). Describe what options are offered to authenticate the customer in accessing their own account(s).  "]
[4.08,"The system shall provide the capability for customers to close their online payment account. Describe how the system handles customers closing their online accounts."]
["CUSTOMER PROFILE"]
[4.09,"The system shall allow customers to create a profile to access their online accounts using personal electronic devices. Describe the process from start to finish of a customer signing up to access their accounts online."]
[{"v":4.1,"d":"4.10"},"The system shall link multiple agency accounts to a single customer account.  Describe the preferred approach for linking customer and account data in the System.  "]
[4.11,"The system shall provide the capability to capture customer data to include customer names(s), email(s), phone number(s), etc. Describe what customer data may be stored."]
[4.12,"The system shall support jointly-owned accounts. Describe how the System handles jointly-owned accounts, such as multiple owners for the same vehicle, residence, business, or dog account and fees."]
[4.13,"The system shall support third party access to accounts e.g. accountants can access business accounts. Describe how third party access is granted and maintained."]
[4.14,"The system shall support additional County-defined fields. Describe how the System supports additional County-defined fields without custom code."]
[4.15,"The system shall validate data within customer records and between related accounts to avoid creating duplicate accounts. Describe how the System validates data (credentials) within and between accounts. "]
[4.16,"The system shall identify and alert County staff and customers to duplicate accounts, merging, and separating of accounts. Describe how the System facilitates data correction, checks and validates duplicates, merging or separating of related customers and accounts."]
[4.17,"The system shall provide updated customer account information to the back-office applications. Describe how the system would share updated customer account information, such as demographics, to the back-office application. Describe any system limitations. "]
[4.18,"The system shall track and record customer account modifications. Describe how the system maintains a history of modifications to customer information, and how this audit trail is accessible to the customer, to the County, and on audit reports."]
[4.19,"The system shall record customer information and track outbound County correspondence for customers without established accounts and receivables. Describe how this can be achieved by the system."]
[{"v":4.2,"d":"4.20"},"The system shall allow a user to update a profile while it is simultaneoulsy being updated by another user without loss of data. Describe how the system prevents loss of data when a user updates a profile that is simultaneously updated by another user. "]
["CUSTOMER ACTIVITY"]
[4.21,"The system shall display customer data, transactional activity, and attachments in a summary and detailed view. Describe how system will provide the capability and options to display customer data, related transactional activity, and system attachments.  "]
[4.22,"The system shall provide the capability to search for and access customer data. Describe the options for searching for and accessing customer information from the customers perspective and County staff perspective"]
[4.23,"Describe what system functions or actions are accessible from within the customers' profiles to the customers and County staff e.g. saving payment information, viewing bills."]
[4.24,"The system shall provide the capability to track and record data for one-time customers and established customers. Discuss the options for recording customer data and tracking transactional activity for one-time customers."]
["CUSTOMER CORRESPONDENCE"]
[4.25,"The system shall generate outbound electronic billing, notifications, and other correspondences by email, text message, etc., on preconfigured cycles, triggered events, or on an ad-hoc basis. Describe the process and output for generating  electronic correspondences."]
[4.26,"The system shall track all generated outbound correspondences to the customer, including bills, invoices, and reminders sent by emails, text messages, and other methods of correspondence. Describe how the system tracks the outbound correspondence and the types of correspondence it supports."]
[4.27,"The system shall provide customers with online access to their accounts and allow reprinting bills, receipts or payment confirmations. Describe this functionality.  "]
[4.28,"The system shall support online form submission. Describe the systems capability to support online form submissions attached to payments. Describe how forms would be exported to agencies without back office applications.  Forms may include, but not limited to; license applications, health and business inspections, and inventory orders."]
[4.29,"The system shall provide the ability to upload PDFs (online forms or PDF uploads). Describe the system's ability to upload PDFs or any other forms of documents."]
["CUSTOMER SUPPORT"]
[{"v":4.3,"d":"4.30"},"The system shall allow back-office staff access to re-send email receipts and bill notifications, reset passwords, update account information/settings, set-up auto-pay and paperless upon customer request, and void payments, issue credits, etc. Describe all the administrator functionalities available for County staff. "]
[4.31,"The system shall provide dashboards and query functionality. Describe what dashboards and query functionality is available to search for customer, account, and transaction records."]
[4.32,"The system shall allow different roles and responsibilities for customers and staff. Describe how the system handles varying roles and responsibilities for customers and County staff."]
[4.33,"Describe the available customer support offered to customers who may have trouble paying, linking, registering, or have questions concerning payment processing, denials, or  bank/credit card statement items."]
[4.34,"The system shall validate data entered in some specific system fields using validation logic, as well as provide capability to execute County-specific logic. Provide an overview of the validation."]
[4.35,"The system shall provide the capability to configure the types of alerts and notification to County staff based on user-defined triggered events. Describe how the System supports configurable alerts and notifications to County staff based on user-defined trigger events. "]
[4.36,"The system shall allow customers to register for notifications and select the method of notification (Text, Phone, Email – with ability to select one, some, all, none). Describe the notification alerts and the types of notifications."]
[4.37,"The system shall allow customers to send a message or chat with county staff asking questions through the system?"]

{"sheet":"Validation","index":5,"n_rows":6,"n_cols":2,"rows_kept":6,"hidden":true}
["Vendor Response","Delivery Method"]
[]
["Yes","Out-of-the-box ('O')"]
["No","Configuration ('C')"]
[null,"Third Party Product ('T')"]
[null,"Custom ('M')"]

{"sheet":"5. TECHNICAL","index":6,"n_rows":115,"n_cols":3,"rows_kept":115,"merged":[[0,0,0,2],[1,0,1,2],[2,0,2,1],[75,0,75,1]]}
[]
["TECHNICAL"]
["County Specifications",null,"Offeror"]
["#","Description","Comments "]
["GENERAL TECHNICAL"]
[6.01,"Illustrate with a diagram your overall recommended architecture and model (e.g. hosted, on premise, Software as a Service (SaaS) or other), including all System and user access components on the network, recommended security components, and bandwidth requirements between components of the System. Clearly state the single recommended approach to the technical environment. Describe the system availability for the architecture model proposed."]
[6.02,"Provide copies of any standard agreements needed to fulfill the above question."]
[6.03,"What hardware platforms, operating systems, and web browsers do you support? Does your system require any installed apps or browser plug-ins?"]
[6.04,"Describe your policy to stay current with new versions of operating systems and web browsers."]
[6.05,"Specify the standard system performance and all the requirements to meet these expectations across all platforms. Response must also identify recommended environments (development, staging, test, production, etc.) required to support a fully operational System."]
[6.06,"List the RDBMS products and versions with which the System is certified to operate."]
[6.07,"List any additional System components required to make the proposed solution work."]
[6.08,"Describe in detail the System’s ability to allow staff with Administrative privileges to allow editing of business rules, listing of box data values, aesthetic modification of screens and addition of fields and database columns. Describe the functions available to staff with Administrative privileges.."]
[6.09,"Describe in detail the configuration changes that can be done by vendor staff only."]
[{"v":6.1,"d":"6.10"},"Describe how the System integrates with Microsoft O365."]
[6.11,"Describe how the user interface utilizes current UI standards for the operating Systems in which it is deployed."]
[6.12,"Describe how the System provides support for inter-process communication including, but not limited to, the following: attachment of standard object types and cut and paste capability from data fields and screens to other applications."]
[6.13,"Does the System include all support software, tools and utilities (e.g. compilers, text editors, library products, code generators, scripts) needed to perform configuration, installation, operation, administration and management tasks? If they are not included, provide a list of third party applications and vendors."]
[6.14,"Describe the recommended (optimal) and minimum desktop hardware/software requirements needed to support the System on all platforms to maintain the Offeror’s defined performance objectives."]
[6.15,"Describe the capabilities provided to administer and monitor all aspects of the System and platforms."]
[6.16,"Provide your Data Dictionary that supports the System."]
[6.17,"Describe how the System generates editable documents."]
[6.18,"Describe System capabilities for configuring fields as required. Include how the required fields are displayed to the end user."]
[6.19,"Describe in detail the online help available for the System. Include information about the System’s ability to configure the online help to be County specific."]
[{"v":6.2,"d":"6.20"},"Describe in detail System functionality to copy all or part of a record (e.g. tax type) and allow the user to modify the copied record."]
[6.21,"Describe how your system allows for an integrated, seamless customer experience with your client’s main websites. Is there a configuration panel? Can you use client’s Cascading Style Sheets? How customizable are your public facing web pages?"]
[6.22,"Describe how you design the customer facing web interface to ensure a streamlined, easy-to-use public facing system. Elaborate on any user testing, focus groups, feedback systems you use to drive innovation and best practices for your customer experience."]
[6.23,"The customer portal shall be ADA aacessible. Describe how the customer portal meets the ADA accessibility guidelines and standards for web content and design."]
["MOBILE"]
[6.24,"Describe in detail any native mobile applications that are part of the offered solution. Describe any System functions that are performed via native mobile applications. Can the application provide services through a mobile web-browser only?"]
[6.25,"Describe in detail the System processes that cannot be handled by mobile devices."]
[6.26,"Describe how information entered on mobile devices may be transferred to the System database and/or records management System, including any offline store and forward capabilities."]
[6.27,"Describe how conflicts with mobile data uploads and System information are reconciled."]
[6.28,"Describe how you ensure a mobile first, moible enabled customer facing experience."]
["REPORTING AND QUERYING"]
[6.29,"Describe in detail the reporting engine and tools provided in the solution that support custom and ad-hoc reporting and query functions."]
[{"v":6.3,"d":"6.30"},"Provide a list of all available reports provided in the solution."]
[6.31,"Describe in detail the System’s drill down capabilities for reports."]
[6.32,"Describe in detail how the System will support analytical reporting (OLAP)."]
[6.33,"Describe in detail any business intelligence tools and systems that will provide interactive decision support, performance metric dashboards and scores associated with enterprise resources to County staff and customers."]
["BACKUP AND RECOVERY"]
[6.34,"Describe in detail the Offeror’s approach to application and database backup and recovery."]
[6.35,"Describe what disaster recovery services (including physical security of building and access to server, as well as protection from fire, flooding, etc) are available."]
["SUPPORT AND MAINTENANCE"]
[6.36,"Describe in detail what is included in support/maintenance services."]
[6.37,"Provide a sample copy of the standard maintenance/service agreement."]
[6.38,"Describe the migration path that is required for System upgrades."]
[6.39,"Describe the frequency of upgrades/patches and how often new upgrades/patches are made available."]
["SECURITY"]
[{"v":6.4,"d":"6.40"},"Describe in detail what type of user access controls the System supports."]
[6.41,"Describe in detail how Personal Identifiable Information (PII) is stored in the System and the safeguards in place to protect this information."]
[6.42,"Describe in detail how health payment information  is stored in the System and the safeguards in place to protect this information as regulated by HIPAA. For example, if a Health test is being paid for, how is this information masked?"]
[6.43,"The system shall maintain a full audit trail of all security maintenance performed. Describe in detail how the System maintains a full audit trail of all security maintenance performed by date, time, user id, device, and location; the value before and after the change; and how this information is accessed."]
[6.44,"Describe in detail how the System maintains a full audit trail of all actions taken on every record by date, time, user id, devise and location; the value before and after the change; and how this information is accessed."]
[6.45,"The system shall provide the capability to audit the system.  Describe how the audit logs can be applied to the System."]
[6.46,"Describe how the System defines and supports varying levels of user access."]
[6.47,"How does the System update to protect against vulnerabilities?"]
[6.48,"Describe in detail how the System encrypts data at rest and in transit."]
[6.49,"Describe any antivirus and end point security functionality or software used with the System."]
[{"v":6.5,"d":"6.50"},"What are the security mechanisms for exposing the API(s) and/or web service(s) to destinations inside and outside the firewall? What are the security mechanisms for ensuring that values passed to an external payment system are received intact by that system? Provide specific security information for transmitting sensitive data such as payment information."]
[6.51,"Describe in detail how PCI Compliance requirements are satisfied within the System and how the software is updated to keep PCI Compliance."]
[6.52,"Describe how the System tracks user login attempts and locks a user out after a specified number of attempts. Can the number of login attempts before system lockout be changed in configuration? Can the system lock the user out after a specified amount of time being idle?"]
[6.53,"Describe how the solution can integrate to single sign-on using Microsoft Azure identification management system for Backoffice users"]
[6.54,"Describe the multifactor authentication process for portal user"]
[6.55,"Provide a description of the process portal user can use to reset password / multifactor authentication configuration."]
[6.56,"Describe your security incident management and customer notification procedures."]
["RECORD RETENTION"]
[6.57,"Describe how the System allows for records to be tagged (classified) and assigned a retention policy/schedule to ensure that the record is retained pursuant to the policy."]
[6.58,"Describe the capabilities to generate automated reports prior to the deletion of records that have been tagged to be deleted."]
[6.59,"Describe how the System allows for automated destruction/deletion of records that have met or exceeded the required retention schedule."]
[{"v":6.6,"d":"6.60"},"Describe how the System allows for retrieval and production of information for eDiscovery and FOIA compliance."]
["INTERFACES"]
[6.61,"Describe the tools, technologies, standards, etc. provided to import and/or export data and/or interface with other systems or data sources.   \n\n"]
[6.62,"Describe how the system utilizes API's or web services to communicate with any system.  Does the web service need to be coded in a specific language?  If so, what language?"]
[6.63,"Describe if the system supports Standard Interchange Protocol (SIP) to integrate with library systems."]
["Interface information for the following existing applications:"]
[6.64,"Cayenta – County’s Utility Billing system"]
[6.65,"CRIF - Excel sheet"]
[6.66,"Elavon - Payment processor for transactions made through the rppp.arlingtonva.us web site."]
[6.67,"Merkle - Lockbox service for check payments"]
[6.68,"iNovah - Cashiering / POS system"]
[6.69,"CAPP - Online payment portal"]
[{"v":6.7,"d":"6.70"},"IVR System"]
[6.71,"Virginia Vital Events and Screening Tracking System (VVESTS) - The VVESTS is a suite of applications and houses modules for the registration of Virginia births, deaths, infant hearing and birth defect screenings"]
[6.72,"WebVision - The Virginia Department of Health's computer system to record client information, appointments, medicines, charges, statements and balances"]
[6.73,"Environmental Health Database (EHD) - The Virginia Department of Health's computer system to record inspections information on restaurants, swimming pools, violations and enforcement actions"]
[6.74,"Access Database (NCM) - Nursing Care Management System"]
[6.75,"Access Database (Walter Reed)"]
[6.76,"Access Database (Fraud Collection) - Fraud Recoupmemnt"]
[6.77,"Cerner - Electronic Health Record for CSB Behavioral Health Services"]
[6.78,"Visual Homes/Excel - Property Management/Excel for Housing Choice Voucher"]
[6.79,"Envisionware (Self Service and Library Efficiency)- payment system for cash and credit card"]
[null,"Nayax - payment system for cash and credit card"]
[null,"EnvisionWare eCommerce - online payment system for credit cards"]
[{"v":6.8,"d":"6.80"},"CodePAL (Sybatech Inc.) - County's Fire Department's Building Safety inspection system (Sybase’s CodePAL) to record the Fire Dept.'s payments"]
[6.81,"DigiTech - Third Party Billing"]
[6.82,"Retiree Direct Pay - Payment of retiree insurance premiums"]
[6.83,"COBRA - COBRA payments from former employees and dependents"]
[6.84,"Payment of Quarterly Movement Class Programs - Healthsmart Movement Classes"]
[6.85,"Quarterly Movement Class Programs - Healthsmart Movement Classes"]
[6.86,"RD Subsidy - Consultation Benefit"]
[6.87,"RecTrac - Registration/Reservation system - Staff use only"]
[6.88,"RecTrac/WebTrac Convenience Fees - Separte MID for convenience fees for all CC charges through RecTrac and WebTrac"]
[6.89,"Sports League Registration System (various) - Sports league registrations"]
[{"v":6.9,"d":"6.90"},"My School Bucks -Heartland/ Schoolcare Works"]
[6.91,"ACEware"]
[6.92,"EZ facility - Merchantware Payment Gateway"]
[6.93,"Accela Permits Plus/ePlan - Permitting System"]
[6.94,"OpenCities: Content Management System - Describe how the solution would integrate with the CMS(Content Management Solution) used by the public website to provide for a single integrated user experience(UX) for residents and businesses to use. Does the solution have either through API or other means provide for SSO(Single Sign-On)?"]
["DATA CONVERSION"]
[6.95,"Describe in detail the tools, technologies, and methodology provided to import and/or export and transform data. If third-party tools are used, provide the names of the tools and describe how and when they are used during data conversion."]
[6.96,"Define a high level data conversion plan for extracting, transforming, and loading all current and historical data required from the County’s legacy systems to the Offeror’s System."]
[6.97,"Describe how the data integrity and validation rules will be handled in the conversion process."]
[6.98,"Describe the Offeror’s recommended approach to data conversion verification.  Include the methodology for correcting individual or batched records, if necessary."]
[6.99,"Are the field sets customizable so that we can ensure we are collecting data in a way that is consistently formatting to match data collection in other systems? (for example, the ability to have name as a minimum of two fields with unique field ids)."]