Appendix_A-2_-_Project_and_Implementation_Approach_Module.docx

Appendix A-2 – Project and Implementation Approach for Product/Module Implementation

Responder should submit one attachment per section for each of the five sections listed below, labeled as Appendix A-2 Section 1 Response, Appendix A-2 Section 2 Response, and so on. These documents should NOT list cost detail. If cost detail is included in this document, the State may disqualify the proposal as non-responsive.

1. Solution Overview (Recommended length up to 12 Pages) Responder proposing an OMS solution should give an overview of the product(s) that will be configured and implemented in support of this RFP.

· State assumptions:

· The solution will be implemented using the latest version(s) of the OMS Contractor Hosted environment (Cloud).

· Any features automatically available via updates without significant additional configuration will be available to the OMS project.

· Any new features requiring significant additional configuration are not included in this RFP and would need to be considered on a case-by-case basis, potentially necessitating a contract amendment To the extend the vendor is aware of new features they would propose, these costs should be captured in Tab O1 of the cost proposal.

1.1. Technology Product(s) Overview - Provide an overview of the proposed technology product(s) including descriptions of the key modules and capabilities and any relevant features that enhance the overall usability and functionality. Consider the core applications the State uses today (see Appendix F – OMS Applications) and is seeking to replace with a modern configurable COTS OMS.

1.2. Technical Overview - Provide an overview of the proposed technical solution including descriptions of the key data and application architecture. Include an overview of the proposed environments necessary to support the overall project approach (e.g. Test, Training, Prod etc.). Include an overview of the products data integration (API) architecture. Include an outline of the cloud hosted services and tools available to support management and administration of the product and supporting infrastructure environment. Consider the need for integration with existing agency services and applications as well as any specific tools or services required for data conversion, training, and other implementation specific activities.

1.3. Supporting materials – Provide representative evidence, samples of work, and/or deliverables supporting technical architecture and hosted environment approach.

2. Project Management (Recommended length up to 20 Pages) Appendix G: Project Management provides the State expects related to project management approach and methodology in this area. Responder should provide a high-level overview of their OMS implementation approach and methodology including estimated timeline to complete. Response should also include a sample Project Planning Deliverable. Include a list of clients where implementation approach has been utilized. Describe anticipated key project risks/issues encountered and mitigation approach recommended, indicate examples where approach has been previously adopted to mitigate key risks. Responder should describe how the responder’s approach and methodology differs from the State’s approach identified in Appendix G for a Product Approach. This approach will help the State think holistically about the services that we provide, and how we align our people, processes, technology, and policies to improve the way services are delivered. For more information on the State’s Product approach see Office of Transformation and Strategy Delivery / Minnesota IT Services (mn.gov).

3. Project Gates and Deliverable Acceptance (Recommended length up to 20 Pages) Appendix E: Project Gates and Deliverable Acceptance describes the State’s approach and methodology for a traditional, single implementation approach. Responder should identify in a Product or module implementation methodology all quality stage gates and completion criteria required to successfully complete the project taking into consideration the elements outline in Appendix E. Responder should provide their approach and methodology to manage the project schedule over the implementation project lifecycle. Responder should also provide an initial Project Schedule identifying major tasks and deliverables to be performed, durations for each task, task interdependencies, major schedule milestones, and overall time of completion. Schedule should be submitted in the form of a Gantt Chart. Responder should describe how their approach and methodology differs from the State’s approach identified in Appendix E, identifying any additional proposed project reporting recommendations for consideration.

4. Data and Infrastructure (Recommended length up to 20 Pages) Appendix H: Data and Infrastructure describes the State’s approach and methodology in this area. Responders should provide representative evidence, samples of work, and/or deliverables supporting proposed approach. Responder should also describe their approach to data conversion (example iterative vs one-time conversion). The conversion process should provide documentation identifying records that could not be converted with appropriate reasons for its failure to convert for the purpose of rectifying data issues and performing additional conversion. Responder should describe how their approach and methodology differs from the State’s expectations in Appendix H.

5. On-Going Support and Training (Recommended length up to 18 Pages) Appendix I: On-Going Support and Training describes the State’s approach and methodology in this area. Responder should provide representative evidence, samples of work, and/or deliverables supporting proposed approach and methodology. Responder should also provide their Product Roadmap plans, features, and capabilities. Indicate expected timeline, where applicable. Describe the approach to identifying roadmap needs and communication of future roadmap activities. Provide representative evidence, samples of previous 2 years of roadmap development work, release schedule and availability of proposed features. Responder should describe how their approach and methodology differs from the State’s expectations in Appendix I.

Responder should include additional information on an existing product roadmap and/or additional information pertaining to a new solution/module or capability, if applicable. Response should include information surrounding their future product roadmaps, innovation highlights, and strategic direction of products as it related to the State solution needs, highlighting their company’s roadmap process and what can be expected in a future partnership with the State.

image2.png