Upcoming Webinars
Access the latest trends and insights shaping the profession—free for members.
.png)
 (1).jpg)
_1.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.png)
.jpg)
.jpg)
.jpg)
Document
ART - Award - Public Bid Opening via Webcasting 2011
Year Created: 2011
DOCUMENT
RFP - New Divisional Software System 2006
- YEAR CREATED: 2006
- ENTITY TYPE: County
- TYPE OF DOCUMENT: RFP - Request for Proposals
- Management
- Technology
The document provides context information for a system that needs to interface with the Clerk of Courts finance system, SAP. The system is required to handle daily processes for three cash locations, with the ability to add additional cash locations. It should be able to confirm the successful daily interface with the SAP FTP site. The system should also be able to monitor refunds and partial refunds, with a comment area for description and detail. It should have the ability to run reports for the status of receipts and provide various reporting capabilities, including daily transaction reports, payment summaries by fee codes, and general ledger account reports. The system should have access-restricted maintenance tables for managing fee codes, GL accounts, fee types, and status. It should also have the capability to calculate and collect fees for non-residential and residential land development. The system should integrate with peripherals such as credit card processing, cash drawers, and check verification.
In addition to the above, the document also discusses the requirements for a contractor licensing system. The system should support contractor and sub-contractor licensing information and monitoring, with the ability to scan paper documents into the contractor's record. It should track licensed and unlicensed contractor citations, capture and maintain contractor complaints, and generate messages to be sent to contractors when their license is put on hold or inactive. The system should be able to create annual contractor license renewal forms and print reminder notices for those who did not renew.
The document also mentions the need for multi-leveled security in the system, with the ability for the system administrator to create user accounts, assign access rights, and manage user privileges. The system should confine access based on user privileges and enforce server to field level security. It should also allow authorized staff to modify various tables and fields to adapt to changes in business rules/operations. Additionally, the document highlights the requirement for a method to regulate logon/work group authorization to add or modify the physical address fields of all project/permit records.
Overall, the document provides a detailed overview of the requirements for the system to interface with the Clerk of Courts finance system and handle various functionalities related to cash management, refunds, reporting, contractor licensing, system administration, and the regulation of logon/work group authorization for address field modifications.