My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CENTAMAN, INC.
Clerk
>
Contracts / Agreements
>
C
>
CENTAMAN, INC.
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/3/2024 9:46:19 AM
Creation date
11/7/2022 3:37:37 PM
Metadata
Fields
Template:
Contracts
Company Name
CENTAMAN, INC.
Contract #
A-2022-216
Agency
Parks, Recreation, & Community Services
Council Approval Date
11/1/2022
Expiration Date
10/31/2030
Notes
For Insurance Exp. Date see Notice of Compliance
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
78
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
3. For on -premises hosting of internal servers, the Zoo prefers Windows servers and SQL Server databases. If <br />another OS or database is used, please identify whether you offer any sort of managed service option. <br />4. Ability to use LDAP integration for authentication/SSO. <br />5. The system should provide the ability to integrate with Windows Active Directory and support a single user <br />sign on if on a Windows system. <br />6. Ability to support Google Chrome browser for all transactions. <br />7. The system should contain a date/time entry stamp and user information reflecting an audit trail on every <br />data element. <br />8. The system should provide access from outside of the firewall by non -domain external users in accordance <br />with generally accepted security standards. <br />9. The system should enable the client to enter organization -specific values in coding fields (i.e., lookup <br />tables). These and other user configurations should be preserved around software updates. (i.e., product <br />upgrades/software releases should not overwrite client -specific coded data or configurations.) <br />10. The system should allow on-line search capabilities based on any field or any combination of fields. <br />11. The system's on-line help should be available at the system, function, screen, and field level. <br />12. The system's on-line help/documentation should be updated with each new version release. <br />13. The system's on-line help should provide an index and search capability. <br />14. The system's on-line help should be context sensitive. <br />15. The system help information should be able to be edited and/or augmented by the Client for specific <br />additional help information. This information should be retained during upgrades. <br />16. The vendor's support site should contain a knowledge -base where users can access system related reference <br />material and documentation. <br />17. The vendor's support site should contain complete and up-to-date manuals for all system modules and <br />functionalities. The manuals should be available for all available versions of the software and should be able <br />to be reproduced if required to distribute to multiple staff members. <br />18. The vendor's support site should contain a complete data dictionary for all system tables and data fields. <br />19. The system's error messages should be integrated with online help functions, allowing the data entry person <br />to be able to click on an error message and open the online help document to the appropriate section. <br />20. The system should have the ability to interface or integrate with Microsoft Exchange to utilize the email and <br />calendar functions with the applications. <br />21. The system should track the use of the system by authorized users. <br />22. The system should have the ability to report attempts by unauthorized users to use the system. <br />23. The system should have the ability to suspend after 'Y' attempts to access the system with an incorrect <br />password if authentication is internal to the system. <br />24. The system should have the ability to copy a security profile. <br />25. The system should provide e-commerce security including customer authentication and encryption to <br />protect customer data. <br />26. The system's e-commerce capabilities should be PCI-compliant. <br />27. The system should support standard Internet security including, but not limited to Secure Socket Layers <br />(SSL). If SSL is not supported, please describe the supported Digital Certificates. <br />City of Santa Ana RFP 22-008 <br />Page 21 <br />
The URL can be used to link to this page
Your browser does not support the video tag.