I review a lot of Request for Proposals for system implementations – some well-written, some not. But one of the things I see lacking in most RFP’s is sufficient attention paid to the topic of data.
When data is under-addressed in the RFP, in the subsequent negotiations and/or the project itself -- bad things can happen. Even if you are planning a brand new installation without any data to migrate, there should be a well-articulated strategy for data. Likely, the primary reason software you’re getting implementing is so that you can get data into and out of the system reliably. Think of software as the plumbing in your house and your data as the water that will flow through that plumbing system. Unless you want to risk the success of the project, you need to make sure you plan in advance for the planning, coordination, and monitoring of those water pressure tests.
As you are poised, fingers hovering above keyboard, writing your RFP, don’t neglect to include a well-crafted Data Readiness section. Be sure to address the details and the related RACI chart for the sub-topics of Data Cleansing, Mocks, Extraction, Load Programs, Transformation, Data Validation and Data Readiness Metrics.
Making your Data Readiness Strategy as a well-constructed pillar of the project from the very beginning will help you build that comfort you need for when you turn on that data faucet at Go Live!
To learn more about how to plan an effective Data Readiness Strategy that you can build into your RFP or project, attend ValidDatum’s free webinar:
Avoiding A Data Disaster: Planning A Successful Data Readiness Strategy for Your Project