C-952_Attachment_G_-_Transition_Plan.docx
DOCX document 15 KB Posted
- Attached to
- Construction Solicitation Virtual Plan Room
- Solicitation number
- 2000015626
- Issued by
- Ramsey County, St. Paul City, Minnesota
About this file
This document is the Transition Plan (Attachment G) for a Construction Solicitation Virtual Plan Room contract opportunity issued by the State of Minnesota, involving the jurisdictions of Ramsey County and the City of St. Paul. The Transition Plan details how the successful vendor will facilitate a smooth transition from the current system to the new vendor's system, including setting up accounts, providing training, and creating a customized link for the State's website. The plan also outlines the process for transferring previously bid project data and Plan Holder's lists to the new vendor's system at the end of the contract term, including data mapping, extraction, and production deployment.
The Construction Solicitation Virtual Plan Room contract will provide a system that supports free viewing of plans, drawings, and specifications, with a per-project pricing model for downloads. The system will also allow for responses to construction solicitations. This is a formal Request for Proposal (RFP) event, with a submission deadline of no later than the specified Finish Time. Interested parties may submit questions, which will be responded to via an addendum to the official Solicitation holders.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| C-952_Attachment_F_-_Functionality_Grids.docx | DOCX document | |
| C-952_RFP_Attachments_A-E.docx | DOCX document | |
| Construction_Solicitation_Virtual_Plan_Room.pdf | ||
| Exhibit_A4_CORRECTIONS_FACILITY_REPORT.pdf | ||
| C-952_RFP.docx | DOCX document | |
| C-952_SampleContractandExhibits.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment G – Transition Plan
1. Contract Vendor must provide transition plan detailing how a successful transition from the current vendor System to a new vendor System will be achieved. The plan must include an estimated timeline for implementation and utilize the Department of Administration – Office of State Procurement - to test the System.: the Contract Vendor’s customer support team will set up an account for each State department. Contract Vendor will schedule training with each department and this training typically takes about an hour. Contract Vendor’s customer support team will email instructions on creating additional IDs/Passwords and Project Posting User Guides. It will create a customized link for the State’s website, which takes about a week. Once State’s administrators have been trained and the State has placed the link on its website, Partner and Users will be ready to start posting projects.
2. Contract Vendor must provide transition plan detailing how stored data of previously bid projects and Plan Holder’s lists will be transferred to a new Vendor’s system at the end of their contract term.: Contract Vendor’s has a robust data integration capability allowing for easy importing and exporting of data in a variety of formats. This makes the planning and delivery of data conversion very straight forward.
· State and Contract Vendor’s will identify each of the data sources including data elements that need to be converted and brought into the new system.
· Contract Vendor will build a data mapping document that defines the source data structures to the destination data structures. This would include the documentation of any business rules that need to be applied to the data.
· Contract Vendor will document the easiest method of extraction of source data. This may be exporting to flat files in a variety of formats, pulling data from source system via web services or API, or pushing data into the Contract Vendor’s system via web services.
· Upon completion of the data mapping document and agreed upon data delivery methods, an accurate timeline for delivery is determined.
· Data will first be delivered to the Contract Vendor’s test system where it is reviewed by the appropriate business experts. Formal approval will be given and a production deployment schedule is determined.
· Data will then be placed into production where final approval will be given.
· Depending on the approach, a final “incremental” file may be required in order to complete the migration.
File details come from the government source that posted it. Updated .