Specifications include, but are not limited to: The ERP software should include a variety of general system characteristics that are not specific to any particular subsystem, component, or module but that are global in their nature and are required by City personnel to use the system efficiently, effectively, and economically. These global requirements are defined in the Vendor Response Sheets. In general, the system should include table driven features for logic rules, edit and validation for data entry, and error reporting. Reference tables must be easy to update from the base online functionality. The system should support online data entry and editing at remote sites. Menu-driven programs, online help facilities, and easy-to-use and establish error correction routines should further improve data entry and editing processes. Online inquiries can either be predefined or may be ad hoc and should be able to print summary or detail data. Data can be uploaded from and downloaded to PCs for additional user-controlled manipulation. A state-of-the-art report writer is an integral capability of the system. The City currently uses Crystal Reports with Tyler/EDEN and Springbrook for customized reports. The report writer provided should include the ability to easily export data to office automation software (e.g., Word and Excel). The report writer should include number formats and calculation features such that non-technical users can easily develop reasonably sophisticated reports. Security should be a key requirement of the system and should be provided at a variety of levels across all subsystems. Security functionality must support central and local security administration, and support screen, field and field content access authorization. Report generation must reflect online access authorization rights. Documentation and Vendor support are also a key general system requirement and should be designed to facilitate the user’s access to, and understanding of, the system. Effective dating is a requirement for all time-sensitive transactions. Modifications to software must be made in a manner which will not adversely affect the applicable warranty from the Vendor regarding the unmodified portions of the current version of the Vendor’s software. In addition, such modifications will not impair the functionality of the unmodified portion of the current version of the Vendor’s software. Modifications must also be implemented in a fashion that will not impact future upgrades of the base software and all third-party support software.
