Six common variables are involved in determining the necessity of integration. Each variable defines an inherent problem, which allows for rectification through integration.
- Usability - From the user's perspective, a common problem in enterprises is the variety of different systems that they need to interact with to perform a job. Through integration, the tasks that a particular user needs to perform can be provided in a single, seamless, user interface. Training costs and time to perform a task can be decreased, which can also lead to greater consistency and customer satisfaction.
- Volume - Where data volumes are large, or are changing regularly, it can be problematic to duplicate. Through integration, rather than by copying or migration, the data can be accessed from a common place.
- Real-time - It is important to have access to up-to-date information about customers. Because customer data can be managed by different teams or as part of a regulated process, it might not be possible to use the same system to support both business needs. Integration can make it possible to access up-to-date data in real-time, ensuring accuracy every time.
- Cost - Some functionality is cheaper to access externally rather than reproduce. One example is address lookup. Integration to an external provider can be cheaper than replicating the capability from the raw postal service source data within the system.
- Duplication - Consistency of data is critical. One example is the allocation of service resources to tasks. Duplication might result in double-booking, which will result in an inability to deliver the required service. Though this capability might be required across multiple business areas, it is not uncommon for a single system to manage the allocation and offer that consistent service to other systems, an ability that integration can provide.
- Reuse - Reimplementing common functionality is expensive, particularly when ongoing maintenance and regression testing of enhancements are considered. An approach where common functionality is reused, rather than being reimplemented, can often be cheaper and can lead to greater consistency. Integration can provide this vital undertaking.
