Integration – does it fit every situation?
Some people assume that, because I’m “The Integration Doctor”, that I advocate integration of systems in every circumstance. People who don’t know me assume that… those who DO know me, know that I try to analyze every situation as unique, and based my recommendations based on that analysis. Yes, integration is a good idea in many cases; let’s spend a few minutes talking about the times when integration may not be the ‘right’ answer:
1) When the systems are too disparate to combine. Some systems are not set up to be combined easily – one area may be under regulatory control, for example, while other areas are not. In these cases, it may become too cumbersome to combine these systems (put unnecessary records and requirements on an otherwise well running system, as example); in that case, the organization may choose to keep the systems separate.
2) When the systems are at different levels of complexity/maturity. When a system is at a high level of complexity or maturity, and is being considered for integration into another, less evolved system, the organization may choose to keep them separate.
When have you seen examples of systems that are better off separate than integrated? Let us know!
