- Many different applications and sources of data are causing projects to take longer and cost more as they try to manage around unintegrated data or face the need to develop multiple data and application integrations.
- Before a data integration project can even be considered, the mess of current integrations must be defined, understood and mapped. This can be time consuming and expensive.
- This solution set will provide a straight-forward mechanism to rate the magnitude of the data integration challenges you face and help you put strategies and tactics in place for immediate improvement and going forward.
Our Advice
Critical Insight
- Organizations measure against complex and sophisticated architectures, believing they can move to them overnight, when really they must first gain control of their architecture.
- Hand-coding seems like the best integration method, but tool-created integrations are easier for future developers to adapt and manipulate, and help the organization get on the path to standardization.
- 82% of organizations report that data integration projects are never funded as stand-alone projects; organizations need to be smart about leveraging the right application renewal projects to transform their architecture over time.
Impact and Result
After completing some or all of the suggestions in this solution set, the following items will be finalized:
- Data architecture model chosen.
- Data inventory complete.
- Business projects with potential for DI inclusion identified.
- Gaps in current architecture identified.
- Architecture documented and mapped.
- Data dictionary created.
- Standards set and enforced.