Purpose of this Solicitation: The purpose of this RFP is to enter into a contract to provide operations, software maintenance, and technical support services, as well as software enhancements for the Mountain Plains States Consortium (MPSC) System operated by the Mountain Plains User Group (MPUG). Services shall include application maintenance, development, deployment, enhancements, defect tracking and repair, and documentation as requested by the MPUG. It is the intention of Utah (UT), the Lead State, to procure these services under a maintenance and enhancement (M&E) master contract, on behalf of the MPUG. Please refer to the Scope of Work document located in the Buyer Attachments section for full details and scope.
It is anticipated this RFP will result in a single contract award to the responsive and responsible offeror with the highest score justified by the procurement code.
Question and Answer (Q&A) Period: The Q&A Period opens on February 22, 2021 and ends on April 26, 2021 at 4:00pm Mountain Time.
Closing date and time: The closing date and time for this sourcing event is 5/25/2021 at 3PM Mountain Time. If your time is different from that shown, your profile may be set to a different time zone. Please see the attachment titled "Changing Your Time Zone" in the Buyer Attachments section for directions on how to update your profile. It is your responsibility to make sure you submit your response by the date and time indicated above.
Length of the Contract: The contract resulting from this RFP will be for TEN (10) years and THREE (3) months.
Background: The scope of this contract is to provide software maintenance and enhancement (M&E) services to the MPUG for the MPSC System.
The Contractor shall provide Information Technology (IT) software M&E services in Section 8: MPSC Software Maintenance and Enhancement Services. In addition, the Contractor shall be responsible for the support, maintenance, and modifications of the System in conformance with the regulations, policies, and standards in the most recent versions of the following: 1) USDA’s Functional Requirements Document for a Model WIC System (FReD-E); 2) Vendor Regulations including the federally mandated report, “The Integrity Profile” (TIP); 3) Women, Infants, and Children EBT Universal MIS EBT Interface (WUMEI) 4) Financial and participation count by category computations supporting federally mandated reports; and 5) WIC System interfaces and standard reports, included but not limited to those identified in Attachment L: State Interfaces.
Technology Refresh: The MPSC Web-based application utilizes smart client architecture to couple the features of intelligent network usage with a high-quality user interface constructed via Windows Forms. The smart client architecture, constructed on Microsoft’s .NET Framework, is intended to improve the user experience and data presentation while still maintaining all the benefits of a Web-based application.
Since initial development in 2005, there have been many advances in the technology available to support a WIC program. It is a priority to modernize the existing MPSC System to meet the following objectives.
1) A solution that retains the flexibility to adopt future technology and functionality over the System lifespan. The application should be interoperable with all operating systems and work on commonly used devices, including, but not limited to, notebooks, desktop PCs, and tablet PCs.
2) A solution that provides high configurability to allow for state options, such as:
a) The ability to make data changes in the application as defined by roles-based security. Data changes should include the appropriate cascading changes to the database.
b) Externalization or separation that allows users, based on role-based permissions, to modify business rules without the need for code changes.
3) A solution that achieves savings in maintenance and support costs over the System lifespan. A cost driver for MPSC System support is the handling of defects. Methods proposed shall identify efficiencies in defect resolution that expedite fixes and lower maintenance costs.
4) A solution that provides a System upgrade path to ensure security compliance with software that is being used to support the System. The solution should ensure the application can be run securely on any operating system and any device including any PC or mobile device such as a tablet.
5) A solution that facilitates efficient code changes that can be completed without impacting code in other functional units. Current System design is all part of a single code base; coding for functional units are compiled as a single code base. Functional units currently in the MPSC System include Clinic Services, Scheduler, Operations, Vendor Management, Finance, Food Management, System Administration, and Reports.
6) As a cost-containment measure, MPUG state agencies would like the ability to choose which functional units to implement within their State. As an example, several MPUG state agencies are considering use of a reporting solution outside of the MPSC System; under a new contract, the MPUG would like a solution that would allow state agencies not to implement the Reporting functional unit and have a corresponding reduction in MPSC System maintenance services cost. Other functional units may be considered as well.
7) An assessment of business workflows to identify System workflow improvements or external tools that would lead directly to an enhanced user experience and less time to complete tasks.
8) Additional existing technology options that could extend the life cycle of the MPSC System or provide more functionality for the state agencies using that System should be offered for consideration.
These objectives have been designed to provide bidders with the overall goals of the MPUG without prescribing what the solution must be to solicit innovative solutions that could be unknown to the MPUG at this time. Bidders should include a recommended solution that aligns with these objectives within their proposal. Solutions should include a description of the approach and an anticipated timeline with an explanation of how the solution meets these objectives. Bidders are invited to propose multiple solutions for consideration.
The MPUG intends to engage in this technology refresh effort immediately after contract execution and to complete the effort under this contract as a separate task order but reserves the right to decline these services. Scope confirmation will be initiated following contract transition activities (see Section 10: Transition-In Considerations). An IAPD will be required prior to the execution of any task order for this effort and is expected to take approximately one (1) year to develop and gain FNS approval. Once the IAPD has been approved, and funding becomes available, the MPUG intends to execute a task order for this effort. This timeline is subject to fiscal and schedule constraints, and approval from FNS.
State Contract Analyst
Division of Purchasing