Pension Management System

The Vendor is required to provide an organization with a proven history of success within the pension management information systems industry.
• Provides a user-friendly interface to add, search, enter and view data.
• Provide standard, custom, and ad hoc reporting, analysis, and query capabilities.
• Provide a centralized system that manages all financial information in a single location for current and future retirees.
• Has the ability to create new retiree records by pulling necessary data from existing HR systems.
• Has the ability to integrate well with other systems i.e. oracle, SharePoint, and kronos as needed?
• Ability to apply retention periods based on established rule sets and provide notification of records that exceed established rules.
• Maintain record metadata for changes, including deletion or destruction of records.
• Ability to identify duplicates within the system.
• Track records across their entire life cycle.
• Provide a user-friendly self-service portal that allows retirees to access and update records, as allowed by software protocols, i.e. address changes, dependent updates, etc.
- A pension management system would manage the pension process and streamline record creation, maintenance, and management throughout their lifecycle from record creation to disposal.
- Currently, pension management is accomplished using a heavily customized application that has been sunsetted and no longer supported by the original developer.
- Supporting records necessary for the calculations used in retirement pay determinations are housed outside of the system requiring manual retrieval and input of multiple variables necessary for the process.
- This system would provide a more efficient method of records management and retention, increase reporting and audit capabilities and increase operational efficiency within the department.
- Implementing a new system will enhance both the department and retiree experience by providing access to data in real or close to real time for changes and updates within the system.
- Server/desktop preferences are as follows:
• In general, there is a preference for commodity-based, non- proprietary hardware.
• Any departure from this will require extensive justification.
• Architectural preference is for a redundant, scalable, multi-tiered, multi server environment.
• Preference is for a common shared backup management, logging, and recovery environment.
• The city utilizes an enterprise grade server management platform for administration, maintenance and logging.
• Operating system preference is currently windows server 2019.
• Relational database management system preference is Microsoft SQL server 2019 or higher.
• The expectation is for a high-capacity, high-speed, redundant online disk storage subsystem.
• We would prefer to leverage this storage system if it is economically feasible for this implementation.
• The city uses exchange online as its messaging and collaboration system.
• The primary desktop and laptop client is an intel-based system, with windows operating systems.
• Currently most of the clients are running 64-bit windows 11 operating system.
• The city’s client pcs that have been purchased over time include many different processor speeds and other hardware combinations, so proposers must specify the minimum required client configuration.
• New desktops being purchased are 4.5 GHZ processors, 16 GB ram, 256 GB SSD, 64-bit windows 11 operating system, and Microsoft office 365.
• Mobile broadband in 4g or 5g may exist for some client systems.
• Ability for application packaging and distribution is highly preferred.
• Server virtualization compatibility is highly preferred and accomplished using Microsoft Hyper-V.
• SharePoint online is our primary “intranet” and document storage solution.
• Power bi and SQL server reporting services are our primary dashboard and reporting tools.
- Data integration preferences
• Software proposers should provide industry-standard APIS for data integration that support multiple data formats and protocols, such as rest, soap, OData, JSON, and xml.
• Software proposers should provide comprehensive API documentation including, but not limited to, all endpoints, query parameters, request/response format, rate limiting, authentication and authorization mechanism, error codes, and examples of how to use the API.
• Software proposers should adhere to industry-standard data modeling standards, such as common data model (CDM), to ensure that the data is well-structured and can be easily integrated with other systems.
• Software proposers should follow industry-standard security protocols, such as SSL/TLS encryption, to ensure that data is transmitted securely and protected from unauthorized access.
- Contract Period/Term: 5 years
- Questions/Inquires Deadline: May 29, 2025