Agriculture Financial Services Corporation - Negotiated Request for Proposal - RFP 0716 - Livestock Price Insurance (LPI) Modernization - Professional Services & Application Platform

2.1 Introduction Agriculture Financial Services Corporation (AFSC) is an Alberta Provincial Crown Corporation under the Ministry of Agriculture and Irrigation. For over 80 years Agriculture Financial Services Corporation (AFSC) has provided Alberta’s agricultural producers, agribusinesses and other small businesses with loans, crop insurance and farm income disaster assistance. Our unique role allows us to deliver services to assist our valued clients in managing their risk. AFSC partners with agricultural producers, agribusiness and commercial entities to support and advance development, create new opportunities and improve the quality of life for rural Albertans. AFSC is a provincial Crown corporation guided by a private sector Board of Directors. Proposing suppliers should visit our website at www.afsc.ca for our company’s mission, any recent news, and other pertinent information. 2.2 Background AFSC is seeking to modernize our on-premises application that delivers the Livestock Price Insurance Program (LPI). Mywlpip.wlpip.ca was developed over a decade ago and since then, there have been major technological advances affecting both web application and user centered design. These issues include lack of responsive design to maximize the cross browser and mobile experience, as well as ease of use, and integration with other platforms. AFSC’s goal is to enhance the experience and value it delivers to its clients and stakeholders through its online delivery of LPI. Currently, this transactional web application is available to 6,675 LPI clients in total across Western Canada, 3,493 clients from Alberta and 3,182 non-Albertan clients. LPI was initially offered to Western provinces administered by AFSC and recently has been extended to Maritime provinces with 24 clients with only option to purchase by paper. AFSC expects user growth by around 2% annually. In terms of web application traffic, it will vary based on the markets. AFSC expects 20-60 daily users on average and peak traffic up to 500 daily users most likely to occur between May and the second week of June with additional increases in volume from October through January. 2.3 Objectives AFSC is seeking to modernize the LPI application, both the web application and the platform itself, from an on-premises to an off-premises solution that resides in a Canadian Data Centre. The modernization must align with or improve upon AFSC's branding, user experience and architecture patterns and standards. This RFP has been issued with the expectation that the Service Provider will bring the recommended cloud Platform Vendor. This request has three parts, the Service Provider will provide the following: a) the recommended platform(s) where the application will be developed and deployed b) the modernization of the LPI application with AFSC architecture guidelines and approval c) a ten (10) year support model and cost for the LPI application. This LPI re-development work includes multi-experience design, development and testing of user journeys on both web and mobile interfaces; system integration e.g. third party e-Payment system, authentication services, Client Master data; and historical data migration from the current system onto the new target data store. The notion of having an LPI mobile application is nice to have. This may result in two separate but highly related contracts from this RFP – 1. One, for a Service Provider to work as a partner with AFSC to re-develop the LPI web application, who will primarily be a systems integrator but with additional skills, including but not limited to; experience in the chosen platform; more modern methodologies; executing user experience methodologies; integration with legacy applications; providing insight on potential IT and business role changes that come from using the chosen platform. 2. Second, for the Service Provider’s recommended Platform Vendor. Respondents should realize that AFSC is looking for their recommended off-premises platform, on which the LPI application will be hosted. The proposal must contain both aspects (Service Provider and Platform Vendor) of this RFP. Failure to do so will result in the respondents’ proposal being rejected. Platform vendors that have their own Professional Services (Service Provider) are welcome to participate. AFSC’s expectation is that the work will be largely remote, with key activities being on-site in Lacombe at our Central Office, as mutually agreed to. PROJECT DELIVERY AND COST FRAMEWORK: The project will be delivered using an Agile methodology, with an emphasis on iterative development and the delivery of a Minimum Viable Product (MVP) as an initial outcome. While the final scope will evolve through collaboration and discovery during the project lifecycle, the Total Cost of Ownership (TCO) submitted in response to this RFP will serve as a foundational budgetary benchmark. The selected Vendor will be expected to align their delivery approach and resourcing to the TCO provided, based on the scope as currently defined in this RFP. This cost will set a precedent for financial expectations throughout the engagement. Vendors are encouraged to ensure that their proposed costs are realistic and aligned with the scope and complexity outlined in this RFP. Submissions that appear significantly misaligned may be subject to additional review during the evaluation process. Licensing costs are subject to the same expectations: they must be clearly outlined in the proposal and will be treated as part of the overall TCO. Any significant deviations from the proposed licensing model during the project must be justified and approved in advance. PROJECT DELIVERABLES: The following provides sample deliverables expected for this project. This is by no means a complete list. 1. Project management plans 2. Technical Documentation • Architectural documents • Security documentation • Architecture Decision documents • Developer user guides e.g. coding standards, secure development • Standards Documentation 3. Transition Plans, Knowledge Transfer, and Operational Guidelines 4. Test Strategy, test plans and test cases At the time of this writing, AFSC deliverables standard formats are MS Word, Excel, PowerPoint, Visio, MS Project or Lucid. PROJECT OVERVIEW The LPI program is facing several challenges with the current technology stack which is preventing LPI from meeting customers’ expectations and achieving program growth targets. Some of the issues encountered include the reliability and stability (Uptime) during peak selling periods, and the lack of mobile access and support for modern browsers has been cited as a detriment to user adoption. KEY ISSUES AND SYMPTOMS: 1. Most clients of LPI utilize the portal to purchase their insurance policies. During the peak times of the purchase cycle, the system’s reliability during this time is less than adequate. The inability to support a moderate level of online traffic is a big concern among the stakeholders. 2. The application lacks support for modern browsers and portable devices. This is frustrating for clients and impacts user adoption and growth, as they cannot access information or purchase policies when and where they want. 3. Approximately 20% of LPI client calls are portal related (navigation, providing information that could be self-served). These include user experience issues and related issues that can be resolved by utilizing common modern application principles in modern application design. 4. The application lacks the ability to provide key metrics/KPIs/data that could give customer insights for better strategic planning, communication, and marketing engagement. 5. Premium rates are released daily, settlements weekly, and are time sensitive, so missing a purchase or claim day can have financial consequences for clients. Reliability, stability and redundancy of the application are key to ensuring the LPI Program is delivered successfully to our clients. 6. Dated technology and unsupported software versions and frameworks. 7. The Government of Alberta system audit compliance. PRIMARY OBJECTIVES: 1. An off-premises platform preferably on Azure or AWS to deploy and develop LPI system as described in the Application and Technology Architecture section. 2. To design and develop the LPI system using modern architecture techniques while improving user experience and applying LPI branding as described in Business Architecture section. 3. To partner with a vendor that has verifiable success in delivering a solution on proposed platform. 4. To design and map out data from source to target data migration activities. 5. Ten (10) year cost analysis to support the LPI system for AFSC engagement considerations. 6. Provide project management and delivery. 7. Provide the necessary training to Staff both AFSC and non-AFSC. 8. Provide operational training and transition. SUCCESS CRITERIA: 1. A functioning LPI solution is developed and fully tested 2. The platform solution must have a 99.9% uptime reliability 3. The platform solution must scale and be elastic 4. Passes the LPI system penetration testing 5. LPI data is migrated successfully with appropriate reconciliation reports 6. Increased user adoption 7. Increased client user satisfaction 8. Increased capability within the system for staff and clients 2.4 Duration Project commencement is contingent upon internal approvals from AFSC, and projected timelines are subject to change pending further review. The expected start date is February 2026, with an estimated duration of nine months.