Enterprise Resource Planning Software Systems Environment

The Vendor is required to provide for an enterprise resource planning (“ERP”) software systems environment.
- System include:
•    The system has the ability to support modification of underlying content (verbiage, structure) by authorized county and schools users of standard letters/notifications stored in the system for use with mail merge (ex. County and schools user modifies language in an annual notice to be sent to citizens before that language is generated in MS word through mail merge).
•    The system has the ability to import and export data with web services formats.
•    The system has the ability to support API'S (application programming interface) for both incoming and outgoing third-party system integration. 
•    The system has the ability to provide a toolkit to create and manage API'S.
•    The system includes an in-built development platform for custom business logic development across finance, payroll and HR functions. 
•    The system provides an API to allow connectivity with external database or data warehouses (e.g., Microsoft azure connectivity) for access to archived data.
•    The system has the ability to integrate data in a real-time fashion for user-defined functions (i.e., retain the ability to do batch).
•    The system includes a centralized data dictionary that fully describes table structure and appropriate levels of metadata.
•    The system has the ability to support the county and schools preferred current and supported web browsers, including: chrome, Firefox, MS edge, and safari.
•    The system has the ability to be mobile responsive (e.g., tablets, cell phones).
•    The system has the ability to be device agnostic when run on mobile devices (e.g., the system can be run on android, iOS, windows, etc.).
•    The system is WCAG 2.1 AA and section 508 accessibility compliant in all aspects of its user interface and documents, for internal and external platforms.
•    The system has the ability to support internal electronic signatures (e.g., apply a signature to a check).
•    The system has the ability to support electronic signature capture (e.g., DocuSign).
•    The system has the ability to store and apply digital copies of signatures to documents (e.g., notification letters) with appropriate security permissions.
•    The system has the ability to support a production, test and development environment including the ability to track and migrate software changes applied to each environment and roll back as necessary.
•    The system has the ability to support a production, development, and a minimum of four test environments, including the ability to roll back changes.
•    The system has the ability to archive historical records so that overall system performance can be maintained.
•    The system has the ability to be configured to adapt to new regulations.
•    The system has the ability to be fully operational without an instance of an installed client on the desktop.
•    The system has the ability to use locally installed and network printers at each work station.
•    The system has the ability to allow users to save frequently used reports.
•    The system has the ability to create customizable dashboards for users to select desired metrics for viewing upon login.
•    The system provides ends-users the opportunity to select multiple visual metrics (e.g., charts, graphs) from a menu of existing formats to create a customized dashboard.
•    The system has the ability to enter information to be effective at a later date.
•    The system has the ability to provide "document management system" functionality to track electronic files associated with specific system records.
•    The system has the ability to use "drag and drop" or file upload functionality to associate documents to transactions within the system.
•    The system has the ability to attach files to records in the system with the ability to restrict this functionality.
•    The system has the ability to restrict modification of attached documents based on permissions.
•    The system has the ability to support the redaction of county-defined and school-defined information from system created or stored documents (e.g., redact certain employee information prior to release of a document requested through public records request).
•    The system has the ability to support the redaction of county-defined and school-defined information from attachments to system documents (e.g., redact identified employee information from documents prior to release in response to a public records request).
•    The system has the ability to link imported documents to specific records. 
•    The system has the ability to allow a user to scan documents directly into the system.
•    The system has the ability to export a file directly for document storage. 
•    The system has the ability to email a linked image file to another party with appropriate permissions (internally or externally). 
•    The system has the ability to identify records with attachments.
•    The system has the ability to provide drill down capability to see attachments to records based on security permissions.
•    The system has the ability to associate electronic files with a system record (e.g., MS excel, MS word, pdf, .jpg).
•    The system has the ability to support the purging of attached documents and files, according to county and school defined schedules.
•    The system has the ability to identify records and purge based on document and file type, age, and point of origination.
•    The system has the ability to log audit changes (updates, deletions, or changes) to an external centralized log collection system.
•    The system has the ability to allow auditing within modules to be determined by the module, and configured by the administrator.
•    The system has the ability to update all security roles automatically (user discretion) when a change in the "master" role is made.
•    The system has the ability to provide functional security to control what processes can be performed by certain roles (i.e., view vs. Edit benefit information).
•    The system has the ability to allow a county and/or school administrator to configure the duration that time audit logs are retained (e.g., 90 days).
•    The system has the ability to provide access to audit trails for only the user with proper security based upon the role’s security permission.
•    The system has the ability to allow the system/security administrator to add and change permissions for system access.
•    The system has the ability to log users off the system after an administrator-defined period of inactivity, based on user-defined roles. 
•    The system has the ability to allow a system/security administrator to log out users.
•    The system has the ability to provide customizable audit reports.
•    The system has the ability to provide configurable exception reports.
•    The system has the ability to allow authorized roles 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.
•    The system has the ability to be operational on a 24 x 7 x 365 scheduled basis.
•    The system has the ability to apply the same security permissions to system queries and reports as it does to data fields/elements, based on the role (e.g., data fields masked on a record or transaction are similarly masked on reports run by the user).
•    The system has the ability to provide an indicator to allow county and/or school users to manually select fields that are to be considered confidential (e.g., personal cell phone, home address). 
•    The system has the ability for users to identify information that should be considered confidential.
•    The system has the ability to sequence transactions on an individual record to allow multiple updates within a single day, retaining an audit of changes (i.e., life events).
•    The system has the ability to supports multi-factor authentication.

- Contract Period/Term: 10 years
- A Non-Mandatory Pre-Proposal Conference Date: November 20, 2025
- Questions/Inquires Deadline: November 28, 2025