System integration: Difference between revisions

Revision as of 05:43, 8 September 2022

Latest revision as of 19:49, 29 April 2024

(6 intermediate revisions by 6 users not shown)

Line 1:

{{short description|Bringing together component sub-systems into one system}}

{{Software development process}}

'''System Integrationintegration''' is defined in [[engineering]] as the process of bringing together the component sub-[[system]]s 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,<ref name="Heat">{{Citation| last = Gilkey| first = Herbert T | year = 1960| contribution = New Air Heating Methods| title= 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.| publisher=National Research Council (U.S.). Building Research Institute| place=Washington | pages = 60 | oclc =184031}}</ref> and in [[information technology]]<ref>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.</ref> as the process of linking together different [[computing]] systems and [[software application]]s physically or functionally,<ref name="SICourse">{{Citation| title=CIS 8020 – Systems Integration| publisher=Georgia State University OECD}}</ref> to act as a coordinated whole.

The [[system integrator]] [[data integration|integrates]] discrete systems utilizing a variety of techniques such as [[computer network]]ing, [[enterprise application integration]], [[business process management]] or manual [[Computer programming|programming]].<ref name="Info">{{Citation| last=Moore | first=June | date =13 December 1982| contribution= Software Reviews, BusinessMaster II+, ledger for CP/M systems| title=InfoWorld | publisher=InfoWorld Media Group, Inc| page = 31 | issn=0199-6649}}</ref>

Line 17:

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.<ref name="Integ"/>

'''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.<ref>{{Cite web|title=The Value of Data-Centric Execution Architecture in System Integration Frameworks for Industrial Energy Assets|url=https://www.vistaprojects.com/system-integration/|url-status=live|website=Vista Projects Limited}}</ref> 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 [[data conversion|convert data]] to/from every other applications' formats, [[Enterprise application integration]] (EAI) systems usually stipulate an application-independent (or common) data format.<ref>{{Citation|title=Aircraft/Store Common Interface Control Document Format Standard|publisher=SAE International|doi=10.4271/as5609a}}</ref> 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 willingwillingness 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 [[Application programming interface|API]] standards.<ref>{{Cite journal|last=Gulledge|first=Thomas|date=September 2002|title=B2B eMarketplaces and small- and medium-sized enterprises|journal=Computers in Industry|volume=49|issue=1|pages=47–58|doi=10.1016/s0166-3615(02)00058-1|issn=0166-3615}}</ref> These challenges result in creating hurdles that “prevent"prevent or slow down business systems integration within and among companies”companies".<ref>{{Cite journal|last1=Hvolby|first1=Hans-Henrik|last2=Trienekens|first2=Jacques H.|date=December 2010|title=Challenges in business systems integration|journal=Computers in Industry|volume=61|issue=9|pages=808–812|doi=10.1016/j.compind.2010.07.006|issn=0166-3615}}</ref> Clear communication and simplified information exchange are key elements in building long term system integrations that can support business requirements.

== Benefits of integration ==

Line 30:

{{div col|colwidth=25em}}

* [[Artificial intelligence systems integration]]

* [[Cloud-based integration]]

* [[Configuration design]]

* [[Continuous integration]]

*[[System in package]] and [[system on a chip]]

* [[Enterprise application integration]]

* [[Integration platform]]

* [[Integration Competency Center]]

* [[Integration platform]]

* [[Interoperability]]

* [[Modular design]]

* [[Multidisciplinary approach]]

* [[System of record]]

* [[Systems integrator]]

* [[Multidisciplinary approach]]

* [[Cloud-based integration]]

* [[System design]]

* [[System in package]] and [[system on a chip]]

* [[Modular design]]

* [[Connectivity Integrator]]

* [[Configuration design]]

{{div col end}}