System Integration

System Integration

In information technology, a system is an aggregation of subsystems cooperating so that the system is able to deliver the overarching functionality. System integration (SI) is the process of creating a complex information system that may include designing or building a customized architecture or application, integrating it with new or existing hardware, packaged and custom software, and communications. It linking together different computing systems and software applications physically or functionally, to act as a coordinated whole. E-SPIN adopt multidisciplinary approach to brings together discrete systems utilizing a variety of techniques such as computer networking, enterprise application integration, business process management, manual programming, to fulfil interoperability requirement.

One enterprise with multiple IT systems can result in confusion, inefficiency and decreased productivity. Let E-SPIN global experience and expertise transform your enterprise into one streamlined and optimally-functional entity.

Typical Deliverables Of  System Integration

Typical system integration service engagement are likely to include appliance, hardware, software, systems and enterprise architecture, software and hardware engineering, interface protocols, customization or new middle tier application development – System, Modular and Configuration design, custom programming scripting, project turnkey management, application/cloud/data center/network and security integration and general problem solving as a whole.

They are likely to include new and challenging problems with an input from a broad range of Client division, department and unit where E-SPIN “pulls it all together” as single unified integrated system for Client.

Methods of System Integration

• Vertical integration. Vertical integration (as opposed to “horizontal integration”) is the process of integrating subsystems according to their functionality by creating functional entities also referred to as silos. The benefit of this method is that the integration is performed quickly and involves only the necessary vendors, therefore, this method is cheaper in the short term. On the other hand, cost-of-ownership can be substantially higher than seen in other methods, since in case of new or enhanced functionality, the only possible way to implement (scale the system) would be by implementing another silo. Reusing subsystems to create another functionality is not possible.
• Star integration. Star integration, also known as spaghetti integration, is a process of systems integration where each system is interconnected to each of the remaining subsystems. When observed from the perspective of the subsystem which is being integrated, the connections are reminiscent of a star, but when the overall diagram of the system is presented, the connections look like spaghetti, hence the name of this method. The cost varies because of the interfaces that subsystems are exporting. In a case where the subsystems are exporting heterogeneous or proprietary interfaces, the integration cost can substantially rise. Time and costs needed to integrate the systems increase exponentially when adding additional subsystems. From the feature perspective, this method often seems preferable, due to the extreme flexibility of the reuse of functionality.
• Horizontal integration. Horizontal integration or Enterprise Service Bus (ESB) is an integration method in which a specialized subsystem is dedicated to communication between other subsystems. This allows cutting the number of connections (interfaces) to only one per subsystem which will connect directly to the ESB. The ESB is capable of translating the interface into another interface. This allows cutting the costs of integration and provides extreme flexibility. With systems integrated using this method, it is possible to completely replace one subsystem with another subsystem which provides similar functionality but exports different interfaces, all this completely transparent for the rest of the subsystems. The only action required is to implement the new interface between the ESB and the new subsystem.

A common data format is an integration method to avoid every adapter having to convert data to/from every other applications’ formats, Enterprise application integration (EAI) systems usually stipulate an application-independent (or common) data format. The EAI system usually provides a data transformation service as well to help convert between application-specific and common formats. This is done in two steps: the adapter converts information from the application’s format to the bus’s common format. Then, semantic transformations are applied on this (converting zip codes to city names, splitting/merging objects from one application into objects in the other applications, and so on).

Key differentiators

• Vendor/Technology Neutral. For system integration service subscriber, our focus is on building solutions and providing services across those solutions. We are open to work with any OEMs or in any technical environment.
• Strategic alliances. E-SPIN has strategic partnerships with all the leading technology manufactures – HP, Dell, IBM, CISCO, Microsoft, VMware, RedHat etc. These alliances help us serving our clients with multiple choices and reduced cost. Apart from these strategic alliances, we have global tie ups with all leading OEMs.
• Global Deployment Capabilities. E-SPIN has a direct and indirect presence in multiple region, countries and a robust partner eco system cover the globe which help our clients with on time and efficient deployment of products.
• Flexible pricing models. We offer our clients flexible and transparent pricing options which help them reducing their upfront cost and convert that into an operational expenditure.

Inquiry

Please feel free to contact E-SPIN for your inquiry and requirement, so we can assist you on the exact requirement in the packaged solutions that you may required for your operation or project needs.