INSTITUT

TEKNOLOGI
DEL

TOPIK KHUSUS BIDANG MINAT

SISTEM ENTERPRISE
ENTERPRISE TECHNOLOGY

“Any sufficiently advanced technology is indistinguishable from magic.”– Arthur C. Clarke (1917-2008), British science-
fiction author.
 INSTITUT
TEKNOLOGI
DEL

Garis Besar
Introduction

Integration Challenges

Enterprise Integration Levels

Integration and Standardization

Data Integration Technologies

Application Integration Technologies

2
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE TECHNOLOGY
INTRODUCTION

3
 INSTITUT
TEKNOLOGI
DEL

Introduction
• Enterprise Integration makes the operation of the enterprise seem as if it is
a single entity working towards achieving a known goal.

• The integration goal includes:

• Improving the quality and timeliness of information, and providing
information on demand and where it is needed, regardless of the source
system.
• Coordinating decisions made by separate
organizational units so that all the units work together
towards fulfilling the overall enterprise goals, and thus
avoid local optimization.
• Management of the actions among people in the
enterprise and synchronization of business processes
to efficiently and effectively provide quality products
and services.
Source:
http://ids-technologies.in
4
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE TECHNOLOGY
INTEGRATION CHALLENGES

5
 INSTITUT
TEKNOLOGI
DEL

Integration Challenges
• Encountered in the three enterprise views: process,
information, and organization.
• Process integration challenges occur when processes are not
viewed as end-to-end business processes serving a customer.

FIGURE 16.1
Process integration.

6
 INSTITUT
TEKNOLOGI
DEL

Integration Challenges
• Information integration challenges occur when the data are
located in many different locations creating problems in using
the data.
• Organizational challenges occur when the decisions and
actions of organizational units are not coordinated, or the
goals are not aligned and units may actually make decisions
that are detrimental from an enterprise perspective.
• The integration challenges are overcome by enterprise design.
• By recognizing the integration challenges the enterprise
engineering project teams can identify existing problems and
avoid potential problems before they occur.

7
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE TECHNOLOGY
ENTERPRISE INTEGRATION LEVELS

8
 INSTITUT
TEKNOLOGI
DEL

Enterprise Integration Levels

• Giachetti (2004) presents a framework to describe the different
types of integration in an enterprise.
• The enterprise is decomposed into five levels to reveal the different
integration types.
ENTERPRISE INTEGRATION
LEVELS TYPES

Organization Alignment
Process Coordination
ENTERPRISE
Application Interoperability
INTEGRATION
Information Data Sharing
Infrastructure Connectivity

• Enterprise integration is defined as the achievement of all the

integration types together.
R.E. Giachetti, “A Framework to Review The Information Integration of The Enterprise,” International Journal of Production Research,
42(6):1147–1166, 2004.
9
 INSTITUT
TEKNOLOGI
DEL

Infrastructure Level
• Issue: the physical heterogeneity of the hardware, machines,
devices, and their operating systems.
• Integration goal: connectivity, defined as the linkages between
devices.
• Simply ensures that data and/or messages can be sent from one device
to another device, not whether the data sent can be interpreted by the
receiving system.
• In practice, the integration of information and communication
hardware via networks both wired and wireless has been very
successful, i.e Internet.
• The Internet provides a global and open network for integrating
various computer hardware platforms through conformance to
network protocols.

10
 INSTITUT
TEKNOLOGI
DEL

Information Level
• Integration goal: provide the ability for the enterprise
applications and users to freely and easily utilize and share
data.
• The greatest problem facing information integration is the
heterogeneity of the information sources.
• Information sharing must address the schema diversity
problems described by Batini et al. (1986):
• Different perspectives or names for the same information object.
• data-name conflicts, data-value conflicts, data precision conflicts, data-
type conflicts
• Equivalence among information definitions.
• Relationships between the domains.
• Weak semantics.

11
 INSTITUT
TEKNOLOGI
DEL

Application Level
• The applications are software systems that provide a service.
• Each application, programming language, or system tends to
use locally defined data and message formats that lead to
heterogeneity.
• Integration goal: interoperability, defined as the ability of one
software application to access/use data generated by another
software application or the ability to invoke services of
another software application.

12
 INSTITUT
TEKNOLOGI
DEL

Process Level
• Integration goal: coordination of the business process by
managing the interdependencies between process activities.

• Interdependence is the degree to which the actions and

outcomes of one organizational unit are controlled by or
contingent upon the actions of another organizational unit.
• If interdependence is high, then the time, cost, and effort necessary to
coordinate the process will be high.
• Here, coordination is defined as managing the dependencies between
entities

13
 INSTITUT
TEKNOLOGI
DEL

Process Level

FIGURE 16.7
Interdependence types.

14
 INSTITUT
TEKNOLOGI
DEL

Organization Level
• Organizational alignment seeks to have all the units working
together toward the enterprise mission and goals.
• Organizational alignment starts by creating an organization-
wide understanding of the enterprise’s mission, vision, core
values, and strategy.
• The next step is to make sure that it is communicated widely
throughout the organization.
• The organizational systems that support alignment are within
the domain of human resources.
• These systems include: the performance monitoring system, the
reward system, training, leadership development, recruitment and
retention, recognition and career development.

15
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE TECHNOLOGY
INTEGRATION AND STANDARDIZATION

16
 INSTITUT
TEKNOLOGI
DEL

Integration and Standardization

• One means to achieve integration is through standards.
• A standard is a formal specification to establish the technical
requirements for the operation of a system.
• Idea: if all systems used the same standards, removes many of the
obstacles to integration.
• In the domain of enterprise integration, there are various
standardization organizations that generate standards: the Institute
of Electrical and Electronics Engineers (IEEE) and the International
Organization for Standardization (ISO) are two such examples.
• Note that there are no universal standards.
• While standards are an important part of specifying the technical
integration of the enterprise’s subsystems they cannot solve the
integration problem by themselves.

17
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE TECHNOLOGY
DATA INTEGRATION TECHNOLOGIES

18
 INSTITUT
TEKNOLOGI
DEL

Data Integration Technologies

• Successful integration between business entities requires
sharing of appropriate data.
• Shared information is important for operating business
processes, decision making, and coordination between
different organizational units whether inter- or intra-
enterprise.
• To share data across the enterprise, the options include:
1. Point-to-point integration.
2. A single, centralized database for the entire organization.
3. A federated data, which is a collection of cooperating but
autonomous databases.
4. Data warehouse.

19
 INSTITUT
TEKNOLOGI
DEL

ENTERPRISE TECHNOLOGY
APPLICATION INTEGRATION TECHNOLOGIES

20
 INSTITUT
TEKNOLOGI
DEL

Application Integration Technologies

• Enterprise Application Integration (EAI) is the unrestricted
sharing of data and business processes among any connected
applications and data sources in the enterprise.
• An application programming interface (API) is a set of
procedures that allow external applications to connect to an
application and obtain data or services.

21
 INSTITUT
TEKNOLOGI
DEL

Application Integration Technologies

• Middleware is the main means to achieve application integration.
• Middleware is software that lets systems talk to each other; it is
connectivity software that consists of a set of enabling services that
let multiple applications run on one or more machines to interact
across a network.
• There are many types of middleware;
• Remote Procedure Call (RPC), piece of code in the client application that
invokes a procedure on the server application.
• Object Request Broker (ORB), manages the sending and receiving of
method invocations across a network so that applications can be
distributed.
• Message-oriented middleware (MOM), software or hardware
infrastructure supporting sending and receiving messages between
distributed systems.

22
 INSTITUT
TEKNOLOGI
DEL

Referensi
• R. E. Giachetti, “Design of Enterprise Systems: Theory, Architecture, and Methods,” CRC Press, 2011.
• C. Batini, M. Lenzerini, and S.B. Navathe, “A Comparative Analysis of Methodologies for Database
Schema Integration,” ACM Computing Surveys, 18(4):324–365, 1986.
• K.A. Crowston and T.W. Malone, “The Interdisciplinary Study of Coordination,” ACM Computing
Surveys,” 26(1):87–119, 1994.
• M. Fowler and D. Rice. “Patterns of Enterprise Application Architecture,” Addison-Wesley
Professional, New York, NY, 2003.
• R.E. Giachetti, “A Framework to Review The Information Integration of The Enterprise,” International
Journal of Production Research, 42(6):1147–1166, 2004.
• T. Gulledge, “What is Integration,” Industrial Management & Data Systems, 106(1):5–20, 2006.
• IEEE, “IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries,”
1990. Technical Report, 1990.
• K. Kosanke, F. Vernadat, and M. Zelm, “Cimosa: Enterprise Engineering and Integration,” Computers
in Industry, 40:83–97, 1999.
• A.P. Sheth and J.A Larson, “Federated Database Systems for Managing Distributed, Hetereogeneous,
and Autonomous Databases,” ACM Computing Surveys, 22(3):183–236, 1990.
• D. Smith, L. O’Brien, K. Kontogiannis, and M. Barbucci, “The Architect: Enterprise Integration,”
http://www.interactive.sei.cmu.edu, 2002.

23