|
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).
The opposite of '''''spaghetii architecture''''', which assumes "chaotic" connection of IT systems on the basis of all systems with all, which causes redundant and often unnecessary data flows between IT systems is the '''Integrated Information System architecture - ''IIS architecture.'''''
The concept of the Integrated Information System (ERP class system) should be distinguished from the concept of the Integrated Information System (IIS) of the Enterprise, which includes all IT systems in the enterprise along with the interfaces that are logically connected to each other, creating a single whole aimed at meeting all IT needs of the enterprise. The core of the IIS is the ERP class system and the other IT systems are its satellite systems.
'''The Integrated Information System framework (IIS architecture) usually consists of 4 basic application layers:'''
'''I layer''' - Integrated IT System (ERP class system) as the core of IIS,
'''II layer''' - the Electronic Document Circulation System constituting software for group work,
'''III layer''' - Data Warehouse + Business Intelligence as a central analytical tool,
'''IV layer''' - other business IT systems used in the enterprise, e.g. CRM, billing, intranet applications, extranet applications (e.g. e-commerce applications, e-government) as well as Internet portals and applications, etc.
Logically integrating these 4 application layers with each other using programming interfaces makes it possible to meet all the information needs of the enterprise. This concept was created and successfully used, among others, during the comprehensive computerization of the Poznan University of Technology.
Designing IIS in the enterprise is also aimed at logical integration of backend systems (used within the enterprise) with frontend systems (issued for clients/applicants on the Internet), which translates into the possibility of dynamic management of e-services offered to clients/applicants.
==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 ==
{{div col|colwidth=25em}}
* [[Artificial intelligence systems integration]]
* [[Cloud-based integration]] ▼* [[Configuration design]] ▼* [[Continuous integration]]
* [[Integration Competency Center]] ▼*[[System in package]] and [[system on a chip]] ▼* [[Enterprise application integration]]
* [[Integration platform]]
▲* [[Integration Competency Center]]
* [[Interoperability]]
* [[Multidisciplinary approach]] ▼* [[System of record]]
* [[Systems integrator]]
▲* [[Multidisciplinary approach]]
▲* [[Cloud-based integration]]
* [[System design]]
▲* [[System in package]] and [[system on a chip]]
* [[Connectivity Integrator]]
▲* [[Configuration design]]
{{div col end}}
| 