so that the enterprise behaves as an integrated whole,
therefore enhancing its overall productivity,
flexibility, and capacity for management of change
(or reactivity)” (Vernadat, 1996).
EI does not represent a new issue. Evolving from
physical integration to application and later business
integration, EI has been a challenge for both
information technology (IT) and manufacturing
industries for several decades. Despite the existence
of a significant number of computer-based tools
claiming to support EI and scientific results in the
business networking area and on the so-called
“collaborative work”, it is generally accepted that
more work needs to be done since available
solutions are usually cumbersome and lack in
flexibility to respond to the most recent
technological outcomes, focusing on very specific
aspects, and do not provide or tackle all aspects
related to EI. The scientific community agrees that
questions related to the formalization, conceptual
development and semantic integration (namely
concerning the formal description of the domain,
ontology, behavior, etc.) are fundamental research
topics waiting for a consistent development
(Camarinha-Matos, 2003).
2.2 Enterprise Integration Reference
Models, Frameworks, Standards
and Technologies
Several reference models and architectures were
developed aiming at organizing EI knowledge and
serve as guide in EI programs. This section
succinctly presents some integration reference
models, frameworks, standards referring to business-
to-business (B2B) domain, and relevant
infrastructures and technologies supporting EI.
A. Reference Models and Frameworks
SCOR (Supply Chain Operations Reference
Model) (www.supply-chain.org) is a process
reference model developed as cross-industry
standard for supply-chain management, used to
describe, measure and evaluate supply-chain
configurations. SCOR model is organized around
five primary management processes (plan, source,
make, deliver and return) that allow it to be used to
describe, measure and evaluate very simple or very
complex supply chains by using a common set of
definitions.
GERAM (Generalized Enterprise Reference
Architecture and Methodology) (GERAM
IFAC/IFIP, 2000) refers to the methods, models and
tools which are needed to build and maintain the
integrated enterprise, a single enterprise or a
network of enterprises. GERAM is not a reference
architecture; it aims at organizing enterprises’
existing integration knowledge.
Zackman’s Framework for enterprise
architecture (Zachman, 1987) describes a holistic
model of an enterprise information infrastructure
from different perspectives, ensuring that all aspects
of an enterprise are well organized and exhibit clear
relationships.
Workflow Reference Model (Workflow
Management Coalition, 1999) provides the general
architecture framework that defines interfaces and
covers broadly various area of functionality between
a Workflow Management System and its
environment.
B. Business-to-Business Integration Standards
As defined by (Bussler, 2003), B2B integration
is the enabling technology and the necessary
infrastructure (referred as B2B integration
technology) to make automated supply chain
integration possible, to send XML-formatted
messages over the Internet, to send messages in a
P2P pattern to trading partners or to exchange
messages with marketplaces.
According to (SWWS, 2003), B2B standards’
scope can be roughly separated into: catalogue
systems (i.e. BMEcat, eCX-Electronic Catalog
XML, OCP-Open Catalog Protocol) and
classification standards (i.e. Ecl@ss, UNSPSC-
United Nations Standard Products and Services);
document exchange (i.e. EDI-Electronic Data
Interchange, EDIFACT -Electronic Data Interchange
For Administration, Commerce and Transport,
XML- eXtensible Markup Language, xCBL-XML
Common Business Library, cXML-commerce
eXtensible Markup Language, RNIF-RosettaNet
Implementation Framework); collaboration (i.e.
ebXML – Electronic Business XML Initiative,
RosettaNet); and business processes.
C. Infrastructures and Technologies
Message-Oriented Middleware (MOM) is a
client/server infrastructure that increases the
interoperability and flexibility of an application by
allowing it to be distributed over multiple
heterogeneous platforms.
Agent technologies brought a promising
contribution to the development of infrastructures
and services supporting collaborative networked
organizations (Camarinha-Matos, 2004). The
conceptual approach behind solutions designed and
developed for agent-based architectures strongly
relies on the interaction of autonomous processes
that dynamically coordinate their actions by
communicating with each other.
Web services are self-contained, self-describing
modular applications that can be published, located
and invoked across the Web.
ICEIS 2005 - INFORMATION SYSTEMS ANALYSIS AND SPECIFICATION
456