The 7 Deadly Sins of Data Integration
You cant just write a quick program to share data and be done with it for 5-8 years anymore... Nothing in the world of business technology stands still these days. As the need to incorporate new applications intensifies, and as existing applications undergo constant updates, the old approach of custom-coding connectors to enable new versions to share data with other parts of the system is quickly becoming infeasible. At the same time, rapid shifts in regulatory environments are making it ever more burdensome for individual companies within larger networks to securely adapt information stored in one location to a format that can be readily consumed by their partners. So it’s no surprise that data integration technology has been such a popular topic lately in industries like healthcare and retail. Watch this archived webinar as Aptera’s Integration and Business Intelligence Expert Richard Spice walks us through some of the mistakes and misconceptions that commonly trip businesses up as they move toward a more comprehensive integration strategy. The pitfalls you’ll be learning to avoid include: - Tackling integration only as an afterthought, when individual projects are completed, with no thought of reusability or overall enterprise architecture - Failure to account for inevitable changes to business processes and updates to supporting technologies - Treating integration as a one-time project instead of as its own system requiring an ongoing focus on server health, error handling, and other operational issues
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Mehr von Aptera Inc
Mehr von Aptera Inc (15)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
The 7 Deadly Sins of Data Integration
- 1. The 7 8 BIGGEST Mistakes Companies Make with Integration
- 2. Common Mistake #1 Lack of Knowledge
- 3. Educate Yourself About Integration What is an integration system? What advantages are there with integration models?
- 4. Common Mistake #2 Integration is considered a tool instead of a system
- 5. Integration Is A System, Not A Tool A centralized integration platform should be viewed as its own system. There should be a clear strategy for budget, planning, maintenance, and project teams.
- 6. Common Mistake #3 Shifting Process Details
- 7. Shifting Process Details Integrations are often developed while the integrating systems are still under construction. Changes to the system interfaces can be costly if they are not made responsibly.
- 8. Common Mistake #4 Tests? Who needs test material?!
- 9. Comprehensive Test Material Is Important Auto generated tests are not enough. It is vital to have testing material for all possible variations of inputs and outputs to the integrating systems. Comprehensive test planning helps ensure reliability.
- 10. Common Mistake #5 No commitment to upkeep
- 11. Commitment To Upkeep After the integration system is implemented, there are still operational tasks that need to be done. Server health, error handling, and other operational problems cannot be ignored.
- 12. Common Mistake #6 Unprepared for Changes
- 13. Prepare For Changes The nature of systems and processes is that there will be improvements or replacements over time. Have a plan for software upgrades and changing standards.
- 14. Common Mistake #7 Lack of ownership
- 15. Designate an integration champion Integration across an enterprise needs to be a priority with a flagbearer. Fill out other important roles
- 16. BONUS! Common Mistake #8 Lack of a plan
- 17. Have An Integration Roadmap Integration work is often tacked on at the end of individual projects without any thought of reusability or overall enterprise architecture. Develop a 1yr, 3yr, and 5yr plan and revisit those plans often.
Hinweis der Redaktion
- This should be an explanation of what integration systems are and the advantages of those models: Three key areas Business to Business Enterprise Application Integration Enterprise Data Integration Reusability of logic Message durability
- Having and centralized integration platform needs to be viewed as its own system and not simply a tool for other projects to use. When an integration if funded by an individual project, it is likely to be tailored to fit a smaller vision, instead of meet a broader purpose. Individual projects wont necessarily know what has already been done and could likely duplicate effort. There needs to be a clear strategy in order to be successful. Planning Budget Maintenance Project Teams
- This may be one of the most difficult situations involved in integration projects. Establishing a reliable contract to communicate between systems in important. Projects should involve a business analyst that is familiar with the ‘real world’ needs to establish concrete requirements. An integration solution should be created in a way that is flexible to shifting needs. Changes need to be understood and made with deliberation with all stakeholders.
- This is one of the MOST important keys to having a successful integration project. Low quality or no test material leads to manual or auto-generated test cases that do not properly reflect the real world interface for the integration. It is vital to have testing material for all possible variations of inputs and outputs to the integrating systems. Failure to test properly WILL lead to COSTLY rework and troubleshooting.
- An integration system is not a fire and forget solution. Error handling Server capacity / volume growth Service packs Version upgrades Performance metrics Change management (leads to next topic)
- One thing is certain with integrations, something is going to change. The nature of systems and processes is that there will be improvements or replacements over time. Direct integrations are very rigid, and costly to update when changes are necessary. A good integration system can allow applications, external businesses, etc to be changed out easily. New trading partners added / removed Changing to a new ERP system, but maintain all of the integration to consuming systems.
- There are several roles that need to be filled within the organization to help facilitate a healthy integration team. It is possible for multiple roles to be filled by the same person. You need a person who holds “political responsibility” of the integration system. He or she is there eliminate any obstacles that the integration team might bump into. This person would manage the budget of the integration center and communicate with stakeholders like business unit directors and program managers. Other important roles Business analyst Understand the business process what we are tying together as a whole sequence of actions across parties involved. Enrich user stories in Business Backlog Walk through the processes with business people and real life samples Use checklists to ensure that requirement are met Project manager a good scrum master Daily, weekly and monthly meetings and communications Business backlog Communications with integration vendors or internal integration developers All integration work done by external or internal parties Manage communications for other system owners like ERPs and CRM teams Integration architect Design and define the integration patterns to be used in the solution
- THIS IS THE CALL TO ACTION All of these pitfalls can be boiled down to this: “you need an integration plan to be successful” Trying to develop individual integrations, end up with a spaghetti mess. Create a roadmap that takes into account current needs and future growth and changes.