System integration

System integration is defined in engineering as the process of bringing together the component sub-
systems into one system (an aggregation of subsystems cooperating so that the system is able to deliver the
overarching functionality) and ensuring that the subsystems function together as a system,[1] and in
information technology[2] as the process of linking together different computing systems and software
applications physically or functionally,[3] to act as a coordinated whole.

The system integrator integrates discrete systems utilizing a variety of techniques such as computer
networking, enterprise application integration, business process management or manual programming.[4]

System integration involves integrating existing, often disparate systems in such a way "that focuses on
increasing value to the customer"[5] (e.g., improved product quality and performance) while at the same
time providing value to the company (e.g., reducing operational costs and improving response time).[5] In
the modern world connected by Internet, the role of system integration engineers is important: more and
more systems are designed to connect, both within the system under construction and to systems that are
already deployed.[6]

Methods of 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.[7] 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.[8]

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.[8]

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.[8]
The horizontal scheme can be misleading, however, if it is thought that the cost of intermediate data
transformation or the cost of shifting responsibility over business logic can be avoided.[8]

Industrial lifecycle integration is a system integration process that considers four categories or stages of
integration: initial system implementation, engineering and design, project services, and operations.[9] This
approach incorporates the requirements of each lifecycle stage of the industrial asset when integrating
systems and subsystems. The key output is a standardized data architecture that can function throughout the
life of the asset.

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.[10] 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' 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).

Challenges of integration
System integration can be challenging for organizations and these challenges can diminish their overall
return on investment after implementing new software solutions. Some of these challenges include lack of
trust and willing to share data with other companies, unwillingness to outsource various operations to a third
party, lack of clear communication and responsibilities, disagreement from partners on where functionality
should reside, high cost of integration, difficulty finding good talents, data silos, and common API
standards.[11] These challenges result in creating hurdles that “prevent or slow down business systems
integration within and among companies”.[12] Clear communication and simplified information exchange
are key elements in building long term system integrations that can support business requirements.

Benefits of integration
On the other hand, system integration projects can be incredibly rewarding. For out-of-date, legacy systems,
different forms of integration offer the ability to enable real-time data sharing. This can enable, for example,
publisher-subscriber data distribution models, consolidated databases, event-driven architectures, reduce
manual user data entry (which can also help reduce errors), refresh or modernize the application's front-end,
and offload querying and reporting from expensive operational systems to cheaper commodity systems
(which can save costs, enable scalability, and free up processing power on the main operational system).
Usually, an extensive cost-benefit analysis is undertaken to help determine whether an integration project is
worth the effort.

See also
Artificial intelligence systems integration
Continuous integration
System in package and system on a chip
Enterprise application integration
Integration platform
Integration Competency Center
Interoperability
System of record
 Systems integrator
Multidisciplinary approach
Cloud-based integration
System design
Modular design
Connectivity Integrator
Configuration design

References
1. Gilkey, Herbert T (1960), "New Air Heating Methods", New methods of heating buildings: a
research correlation conference conducted by the Building Research Institute, Division of
Engineering and Industrial Research, as one of the programs of the BRI fall conferences,
November 1959., Washington: National Research Council (U.S.). Building Research
Institute, p. 60, OCLC 184031 (https://www.worldcat.org/oclc/184031)
2. For computer systems, the term "systems integration" has included the plural word "systems"
although the singular form has also been used in referring to computer systems.
3. CIS 8020 – Systems Integration, Georgia State University OECD
4. Moore, June (13 December 1982), "Software Reviews, BusinessMaster II+, ledger for CP/M
systems", InfoWorld, InfoWorld Media Group, Inc, p. 31, ISSN 0199-6649 (https://www.worldc
at.org/issn/0199-6649)
5. Vonderembse, M.A.; Raghunathan, T.S.; Rao, S.S. (1997). "A post-industrial paradigm: To
integrate and automate manufacturing". International Journal of Production Research. 35 (9):
2579–2600. doi:10.1080/002075497194679 (https://doi.org/10.1080%2F00207549719467
9).
6. Merriman, Dan (19 Feb 1996), "Tying it all together", Network World, IDG Network World Inc,
p. 51, ISSN 0887-7661 (https://www.worldcat.org/issn/0887-7661)
7. Lau, Edwin (2005), "Multi-channel Service Delivery", OECD e-Government Studies e-
Government for Better Government, Paris: OECD, p. 52, ISBN 9789264018334,
OCLC 224889830 (https://www.worldcat.org/oclc/224889830)
8. Gold-Bernstein, Beth; Ruh, William A (2005), Enterprise integration: the essential guide to
integration solutions, Addison Wesley, ISBN 0-321-22390-X
9. "The Value of Data-Centric Execution Architecture in System Integration Frameworks for
Industrial Energy Assets" (https://www.vistaprojects.com/system-integration/). Vista Projects
Limited.
10. Aircraft/Store Common Interface Control Document Format Standard, SAE International,
doi:10.4271/as5609a (https://doi.org/10.4271%2Fas5609a)
11. Gulledge, Thomas (September 2002). "B2B eMarketplaces and small- and medium-sized
enterprises". Computers in Industry. 49 (1): 47–58. doi:10.1016/s0166-3615(02)00058-1 (http
s://doi.org/10.1016%2Fs0166-3615%2802%2900058-1). ISSN 0166-3615 (https://www.worl
dcat.org/issn/0166-3615).
12. Hvolby, Hans-Henrik; Trienekens, Jacques H. (December 2010). "Challenges in business
systems integration". Computers in Industry. 61 (9): 808–812.
doi:10.1016/j.compind.2010.07.006 (https://doi.org/10.1016%2Fj.compind.2010.07.006).
ISSN 0166-3615 (https://www.worldcat.org/issn/0166-3615).

External links
CSIA (Control System Integrators Association) (http://www.controlsys.org)
Retrieved from "https://en.wikipedia.org/w/index.php?title=System_integration&oldid=1121151072"