1. Review of the Existing ORIS Application • Conduct a detailed review of the current ORIS application, including architecture, functionality, integrations, workflows, user experience, data structures, and underlying technology components. • Identify strengths, weaknesses, constraints, and technical debt. • Document findings in a structured format suitable for functional and technical stakeholders. 2. Assessment and Documentation of High-Level- Application Requirements • Gather and document high-level business and technical requirements necessary to support ODC’s record-keeping processes. • Identify unique ODC requirements that may not be met by outsourced service models or commercial off-the-shelf (COTS) application packages. • Develop a catalog of opportunities and pain points, including efficiency gaps, manual processes, risk areas, compliance concerns, and modernization opportunities. 3. Review and Documentation of the Current Application Roadmap • Review ODC’s existing ORIS roadmap and validate current assumptions regarding technical upgrades, enhancements, and long-term- viability. • Estimate future development costs, including enhancements required to maintain compliance, performance, scalability, and supportability. • Estimate ongoing support costs, including staffing, infrastructure, licensing, and vendor/consulting expenditures. 4. Review and Documentation of Non-Customized- Solution Options The vendor shall evaluate and document potential alternative solutions to ORIS, including but not limited to: 4.1 Service Model Options • Managed service or outsourced record-keeping models. • Vendor capabilities, operating models, SLAs, and pricing structures. 4.2 Application Packages • COTS record-keeping platforms. • Pension/retirement system solutions and financial administration systems aligned with ODC’s needs. 4.3 Solution Demonstrations • Coordinate demonstrations of leading candidate solutions. • Prepare demo scripts aligned to ODC requirements. • Document functional fit, gaps, and usability observations.
