scispace - formally typeset
Search or ask a question

Showing papers on "System integration published in 2002"


Journal ArticleDOI
TL;DR: This research examines these two important concepts in terms of their evolution, functions and current development and further explores the rationales for their integration by analyzing the problems of ERP and presenting the solutions of SCM.
Abstract: Enterprise resource planning (ERP) and supply‐chain management (SCM) have been growing in popularity across various industries. New initiatives in resources planning, electronic commerce and extended supply chain drive the trend among corporations towards integrating strategic business applications. ERP systems assist enterprises in automating and integrating corporate cross‐functions such as inventory control, procurement, distribution, finance and project management. Through information sharing, SCM enables supply‐chain partners to work in close coordination to facilitate supplier‐customer interactions and minimize transaction cost. This research examines these two important concepts in terms of their evolution, functions and current development and further explores the rationales for their integration by analyzing the problems of ERP and presenting the solutions of SCM. This study is concluded with the imminent development of SCM and EPR systems and the industrial trend toward their integration.

237 citations


Book ChapterDOI
François B. Vernadat1
24 Apr 2002
TL;DR: Modelling and integration issues to progress towards Enterprise Interoperability are discussed and how the CIMOSA architecture can be revised to host these emerging techniques and standards are shown.
Abstract: Enterprise Modelling and Integration has evolved over the last decades from entity-relationship and activity modelling to object and flow modelling as well as from pier-to-pier system integration to inter-organisational exchanges enabling various forms of electronic commerce. The next challenge is Enterprise Interoperability, i.e. seamless integration in terms of service and knowledge sharing. The paper discusses modelling and integration issues to progress towards Enterprise Interoperability and shows how the CIMOSA architecture can be revised to host these emerging techniques and standards.

220 citations


Journal ArticleDOI
TL;DR: The design of a component-oriented system, GeoVISTA Studio, is illustrated as a means to overcome difficult system design and software engineering problems by using state-of-the-art component-based software engineering techniques.

192 citations


Patent
17 Oct 2002
TL;DR: Application views as mentioned in this paper can abstract away much of the complexity in dealing with the application, such that non-programmers can maintain the services and events exposed by an adapter for that application.
Abstract: An application view (102), or application view component, can represent a self-describing interface to functionality in a resource such as an application or enterprise system. An application view can abstract away much of the complexity in dealing with the application, such that non-programmers can maintain the services and events exposed by an adapter (106) for that application. Application views can also simplify the way in which adapters (106, 108 and 110) are accessed, and can allow the functionality exposed by the adapter to be invoked as a business service. An application view can be specific to a single adapter, and can define a set of functions on the corresponding application.

154 citations


Journal ArticleDOI
TL;DR: Could system integration and cooperation be improved with agentified enterprise components?
Abstract: Could system integration and cooperation be improved with agentified enterprise components?

146 citations


Patent
01 Apr 2002
TL;DR: In this article, a method and system for facilitating the integration of a plurality of dissimilar systems by allowing networks of integration framework installations and/or other compatible B2B servers to inter-operate across corporate enterprise boundaries to integrate the disparate systems operating within each corporate enterprise.
Abstract: The present invention is related to a method and system for facilitating the integration of a plurality of dissimilar systems by allowing networks of integration framework installations and/or other compatible B2B servers to inter-operate across corporate enterprise boundaries to integrate the disparate systems operating within each corporate enterprise.

131 citations


Patent
13 Dec 2002
TL;DR: In this paper, a declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems.
Abstract: Techniques are provided to integrate two or more application systems by using an declarative approach that describes functions or rules to be performed to integrate application systems. Particular integration functions are defined that may be useful for common integration activities hitegration functions may be defined for particular objects and may be assembled to form a declarative business process flow. The declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems. An application integration workstation is described that provides a framework and tools to design, develop and modify (or maintain) application integration software. Such an application integration workstation may reduce the time required to construct or maintain application integration software, which may be referred to as “rapid application integration.”

115 citations


Proceedings ArticleDOI
17 Sep 2002
TL;DR: This work presents a new paradigm for business process integration based on a conversation model that enables autonomous, distributed BPM modules to integrate and collaborate and discusses the current implementation of this conversation model and early experience in applying the model to solve customer problems.
Abstract: Business process integration and automation (BPIA) has emerged as an important aspect of the enterprise computing landscape. Intra-enterprise application integration (EAI) as well as the inter enterprise integration (B2B) are increasingly being performed in the context of business processes. The integration scenarios typically involve distributed systems that are autonomous to some degree. From the BPIA perspective, the autonomy refers to the fact that the systems being integrated have their own process choreography engines and execute internal business processes that are private to them. In the case of B2B integration, the systems being integrated are fully autonomous, while various levels of autonomy exist in systems partaking in EAI. We present a new paradigm for business process integration. Our approach is based on a conversation model that enables autonomous, distributed BPM (Business Process Management) modules to integrate and collaborate. Our conversation model supports the exchange of multiple correlated messages with arbitrary sequencing constraints and covers the formatting of messages that are to be sent as well as the parsing of the messages that have been received. The crux of our conversation model is the notion of a conversation policy, which is a machine-readable specification of a pattern of message exchange in a conversation. Our model supports nesting and composition of conversation policies to provide a dynamic, adaptable, incremental, open-ended, and extensible mechanism for business process integration. We discuss the current implementation of this conversation model and early experience in applying the model to solve customer problems. The implementation utilizes distributed object technology.

85 citations


Journal ArticleDOI
TL;DR: The multivariate analysis reveals that integration mechanisms in system operation are positively correlated and positively affect IDSs' efficiency, and the beneficial effects have been realized in IDS performance.
Abstract: This study analyzes integration mechanisms that affect system performances measured by indicators of efficiency in integrated delivery systems (IDSs) in the United States. The research question is, do integration mechanisms improve IDSs' efficiency in hospital care? American Hospital Association's Annual Survey (1998) and Dorenfest's Survey on Information Systems in Integrated Healthcare Delivery Systems (1998) were used to conduct the study, using IDS as the unit of analysis. A covariance structure equation model of the effects of system integration mechanisms on IDS performance was formulated and validated by an empirical examination of IDSs. The study sample includes 973 hospital-based integrated health care delivery systems operating in the United States, carried in the list of Dorenfest's Survey on Information Systems in Integrated Health care Delivery Systems. The measurement indicators of system integration mechanisms are categorized into six related domains: informatic integration, case management, hybrid physician–hospital integration, forward integration, backward integration, and high tech medical services. The multivariate analysis reveals that integration mechanisms in system operation are positively correlated and positively affect IDSs' efficiency. The six domains of integration mechanisms account for 58.9% of the total variance in hospital performance. The service differentiation strategy such as having more high tech medical services have much stronger influences on efficiency than other integration mechanisms do. The beneficial effects of integration mechanisms have been realized in IDS performance. High efficiency in hospital care can be achieved by employing proper integration strategies in operations.

84 citations


Proceedings ArticleDOI
07 Aug 2002
TL;DR: The personal computer-based environment seems to be a very suitable platform for system integration and the personal computers can be linked by the network and are capable of powerful computation and easy display and can be taken advantage of to develop an integration system.
Abstract: In recent years, electronic appliances can be monitored and controlled by embedded microprocessors and be displayed on terminals, but they are still in lack of integration. Since the present home automation (HA) system is not equipped with efficient integration mechanism, it cannot fully manifest the worth of these developments. In order to achieve this goal of integration, many appliance manufacturers focus on the development of intelligent (or information) appliances to be integrated into a complete HA system for monitoring and controlling. Due to the advent of advanced computer and wideband network, the personal computer-based environment seems to be a very suitable platform for system integration. The personal computers can be linked by the network and are capable of powerful computation and easy display. We can take advantage of such abilities to develop an integration system.

79 citations


Journal ArticleDOI
TL;DR: A gap between the goal and reality of physician-system alignment appears to be the result of systems' responding to a changing mix of policies, not all of which foster integration.
Abstract: Incentives for vertical integration in the health care industry have led many hospitals to consolidate into health systems and profess a desire for closer alignment with affiliated physicians. In t...

Patent
13 Dec 2002
TL;DR: In this article, a declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems.
Abstract: Techniques are provided to integrate two or more application systems by using an declarative approach that describes functions or rules to be performed to integrate application systems. Particular integration functions are defined that may be useful for common integration activities. Integration functions may be defined for particular objects and may be assembled to form a declarative business process flow. The declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems. An application integration workstation is described that provides a framework and tools to design, develop and modify (or maintain) application integration software. Such an application integration workstation may reduce the time required to construct or maintain application integration software, which may be referred to as “rapid application integration.”

Journal ArticleDOI
TL;DR: The ACCESS demonstration was successful in terms of project-centered integration but not overall system integration, and more extensive implementation of strategies for system change was associated with higher levels of overall systems integration.
Abstract: OBJECTIVE: The aim of this study was to evaluate the first of the two core questions around which the ACCESS (Access to Community Care and Effective Services and Supports) evaluation was designed: Does implementation of system-change strategies lead to better integration of service systems? METHODS: The study was part of the five-year federal ACCESS service demonstration program, which sought to enhance integration of service delivery systems for homeless persons with serious mental illness. Data were gathered from nine randomly selected experimental sites and nine comparison sites in 15 of the nation's largest cities on the degree to which each site implemented a set of systems integration strategies and the degree of systems integration that ensued among community agencies across five service sectors: mental health, substance abuse, primary care, housing, and social welfare and entitlement services. Integration was measured across all interorganizational relationships in the local service networks (over...

Patent
13 Dec 2002
TL;DR: In this paper, a declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems.
Abstract: Techniques are provided to integrate two or more application systems by using a declarative approach that describes functions or rules to be performed to integrate application systems. Particular integration functions are defined that may be useful for common integration activities. Integration functions may be defined for particular objects and may be assembled to form a declarative business process flow. The declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems. An application integration workstation is described that provides a framework and tools to design, develop and modify (or maintain) application integration software. Such an application integration workstation may reduce the time required to construct or maintain application integration software, which may be referred to as “rapid application integration.”

Journal ArticleDOI
TL;DR: In this article, a cost function is proposed and adopted for optimal partner selection in a virtual enterprise, which not only considers a partner's manufacturing capability and process requirements, but also the processing time, partner's location and product due date.
Abstract: With the fast development of the world economy, distributed virtual manufacturing is becoming increasingly important since it can respond rapidly to market changes and make resource sharing more efficient among manufacturing partners. In this environment, partners may be located at different geographical locations, and co-operation among partners is a vital task and thus concurrent planning and scheduling has become a challenging research topic. This paper presents a computerized model that can integrate these manufacturing functions and resolve some of the critical problems in distributed virtual manufacturing, such as virtual co-operation, optimal partner selection, etc. This integration model is realized through a multi-agent approach that provides a practical approach for software integration in a distributed environment. A cost function is proposed and adopted for optimal partner selection in a virtual enterprise, which not only considers a partner's manufacturing capability and process requirements, but also the processing time, partner's location and product due date. Through establishing a virtual manufacturing model in a simulated environment, the proposal was validated with a case study. It shows that the proposed methodology can satisfy the distribution and agility requirements. This approach is able to contribute to the reduction of product cost, improving product quality and shortening lead time, compared to the sequential approach in the normal engineering and production practice.

Proceedings Article
01 Nov 2002
TL;DR: SkyQuery is presented, a successful prototype of an evolving federation of astronomy archives that interoperates using the emerging Web services standard and it efficiently evaluates a probabilistic federated spatial join query.
Abstract: Traditional science searched for new objects and phenomena that led to discoveries. Tomorrow's science will combine together the large pool of information in scientific archives and make discoveries. Scientists are currently keen to federate together the existing scientific databases. The major challenge in building a federation of these autonomous and heterogeneous databases is system integration. Ineffective integration will result in defunct federations and under utilized scientific data. Astronomy, in particular, has many autonomous archives spread over the Internet. It is now seeking to federate these, with minimal effort, into a Virtual Observatory that will solve complex distributed computing tasks such as answering federated spatial join queries. In this paper, we present SkyQuery, a successful prototype of an evolving federation of astronomy archives. It interoperates using the emerging Web services standard. We describe the SkyQuery architecture and show how it efficiently evaluates a probabilistic federated spatial join query.

Journal ArticleDOI
01 Mar 2002
TL;DR: This paper describes the experience with implementing and modeling SCIs, and presents the integration architecture and the software components of the prototype implementation of a multi-echelon supply chain process model spanning multiple organizations.
Abstract: The need for supply chain integration (SCI) methodologies has been increasing as a consequence of the globalization of production and sales, and the advancement of enabling information technologies. In this paper, we describe our experience with implementing and modeling SCIs. We present the integration architecture and the software components of our prototype implementation. We then discuss a variety of information sharing methodologies. Then, within the framework of a multi-echelon supply chain process model spanning multiple organizations, we summarize research on the benefits of intra-organizational knowledge sharing, and we discuss performance scalability.

Posted Content
TL;DR: In this article, the authors present SkyQuery, a successful prototype of an evolving federation of astronomy archives, and show how it efficiently evaluates a probabilistic federated spatial join query.
Abstract: Traditional science searched for new objects and phenomena that led to discoveries. Tomorrow's science will combine together the large pool of information in scientific archives and make discoveries. Scienthists are currently keen to federate together the existing scientific databases. The major challenge in building a federation of these autonomous and heterogeneous databases is system integration. Ineffective integration will result in defunct federations and under utilized scientific data. Astronomy, in particular, has many autonomous archives spread over the Internet. It is now seeking to federate these, with minimal effort, into a Virtual Observatory that will solve complex distributed computing tasks such as answering federated spatial join queries. In this paper, we present SkyQuery, a successful prototype of an evolving federation of astronomy archives. It interoperates using the emerging Web services standard. We describe the SkyQuery architecture and show how it efficiently evaluates a probabilistic federated spatial join query.

Journal ArticleDOI
TL;DR: In this article, the authors describe the implementation of information systems to support the production planning and scheduling functions in two steel processing business units of a steel plant, and discuss typical issues that have to be solved when ERP and APS systems are integrated.
Abstract: This article describes the implementation of information systems to support the production planning and scheduling functions in two steel processing business units of a steel plant. In particular, the integration of the implementation of two systems is described: Enterprise Resource Planning (ERP) and Advanced Planning and Scheduling (APS). The article presents a functional architecture that integrates the two systems, and discusses typical issues that have to be solved when ERP and APS systems have to be integrated. Lessons learnt included the importance of an architecture to facilitate discussions, issue management, the importance of the primary process, differences between an ERP and APS implementation and differences in process descriptions.

ReportDOI
01 Sep 2002
TL;DR: In this article, the US DOE Distribution and Interconnection R&D (formerly Distributed Power Program) activities, furthering the development and safe and reliable integration of DER interconnected with our nation's electric power systems.
Abstract: Interconnecting distributed energy resources (DER) to the electric utility grid (or Area Electric Power System, Area EPS) involves system engineering, safety, and reliability considerations. This report documents US DOE Distribution and Interconnection R&D (formerly Distributed Power Program) activities, furthering the development and safe and reliable integration of DER interconnected with our nation's electric power systems. The key to that is system integration and technology development of the interconnection devices that perform the functions necessary to maintain the safety, power quality, and reliability of the EPS when DER are connected to it.

Proceedings ArticleDOI
07 Aug 2002
TL;DR: A system developed to demonstrate integration of a number of key research areas such as localization, recognition, visual tracking, visual servoing and grasping is presented together with the underlying methodology adopted to facilitate the integration.
Abstract: A system developed to demonstrate integration of a number of key research areas such as localization, recognition, visual tracking, visual servoing and grasping is presented together with the underlying methodology adopted to facilitate the integration. Through sequencing of basic skills, provided by the above mentioned competencies, the system has the potential to carry out flexible grasping for fetch and carry in realistic environments. Through careful fusion of reactive and deliberative control and use of multiple sensory modalities a significant flexibility is achieved. Experimental verification of the integrated system is presented.

01 Jan 2002
TL;DR: A comparative analysis of the architectural modeling capabilities of established notations widely used by object-oriented, information engineering and structured methods, applied to typical problems found in utilities' ESSI are presented.
Abstract: The escalating development of Information Technology enables utilities to reorganize or migrate from their existing disparate software systems towards an integrated Enterprise Software System Infrastructure (ESSI) that embraces the total organization. Integration of software systems is expected to increase competitiveness and to cut costs. However, since utilities' present ESSI is heterogeneous as to type and technical platform, overlapping with regard to both data and functionality, and relying on ad-hoc low-level middleware, integration and management of ESSIs often turn out to be hazardous.This paper presents a comparative analysis of the architectural modeling capabilities of established notations widely used by object-oriented, information engineering and structured methods, applied to typical problems found in utilities' ESSI. Architectural descriptions may be used to visualize technical risks and opportunities in a utility's current and future ESSI, as well as to improve communication between different groups within the utility, e.g. management and technical staff, and between the utility and its vendors of software systems.


Patent
Thanh V. Lam1
29 Aug 2002
TL;DR: In this article, a technique for integrating software components is presented, which includes providing an application integration model capable of adapting to different environments by dynamically using different software components at application runtime.
Abstract: A technique is presented for integrating software components. The technique includes providing an application integration model capable of adapting to different environments by dynamically using different software components at application runtime. The software components are categorized into different stages, with the stages being indicative of when the software components are to be loaded and executed within an application by the application integration model. The technique further includes employing the application integration model to assemble software components into the application within a runtime environment. The application integration model includes an application runtime driver (ARD), which drives work flows of the application integration model through multiple predefined application stages, and a component runtime integration box (CRIB), which includes multiple common data structures employed by the software components during integration into the application.


Proceedings ArticleDOI
02 Oct 2002
TL;DR: An automatic method of SoCs design validation based on a generic simulation wrapper architecture that provides automatic generation of executable models throughout different stages of SoC design flow is presented.
Abstract: Currently, since many SoCs include heterogeneous components such as CPUs, DSPs, ASICs, memories, buses, etc., system integration becomes a major step in the design flow. To enable this integration, we use a design approach called component based-design approach. In this approach, the validation of system integration takes most of design efforts. This paper presents an automatic method of SoCs design validation. Based on a generic simulation wrapper architecture, the presented method provides automatic generation of executable models throughout different stages of SoC design flow. A case study of validating a VDSL application shows the effectiveness of the method.

Proceedings ArticleDOI
15 Jul 2002
TL;DR: The NASA Integrated Vehicle Health Management (IVHM) Technology Experiment for X-37 was intended to run IVHM software on board the X- 37 spacecraft, and the development effort resulted in major improvements in Livingstone's efficiency and safety.
Abstract: The NASA Integrated Vehicle Health Management (IVHM) Technology Experiment for X-37 was intended to run IVHM software on board the X-37 spacecraft. The X-37 is an unpiloted vehicle designed to orbit the Earth for up to 21 days before landing on a runway. The objectives of the experiment were to demonstrate the benefits of in-flight IVHM to the operation of a Reusable Launch Vehicle, to advance the Technology Readiness Level of this IVHM technology within a flight environment, and to demonstrate that the IVHM software could operate on the Vehicle Management Computer. The scope of the experiment was to perform real-time fault detection and isolation for X-37's electrical power system and electro-mechanical actuators. The experiment used Livingstone, a software system that performs diagnosis using a qualitative, model-based reasoning approach that searches system-wide interactions to detect and isolate failures. Two of the challenges we faced were to make this research software more efficient so that it would fit within the limited computational resources that were available to us on the X-37 spacecraft, and to modify it so that it satisfied the X-37's software safety requirements. Although the experiment is currently unfunded, the development effort resulted in major improvements in Livingstone's efficiency and safety. This paper reviews some of the details of the modeling and integration efforts, and some of the lessons that were learned.

Journal ArticleDOI
Frank Leymann1, Dieter Roller1
TL;DR: Flows provide access to a huge variety of data sources, such as standard applications, home-grown backend systems, and Web services, and can help in managing units of work across these data stores.
Abstract: Information integration has two fundamental aspects, data integration and function integration. Function integration is based on flow technology and adapter technology, and both of these add powerful capabilities to information integration. They provide access to a huge variety of data sources, such as standard applications, home-grown backend systems, and Web services. For accesses that are not restricted to read operations, flows can help in managing units of work across these data stores. When a database system is coupled with a flow engine, all of these capabilities are made available to database applications.

Book
21 Oct 2002
TL;DR: This volume contains a collection of research papers that describe ideas and insights associated with the task of integration.
Abstract: The advances of the World Wide Web have dramatically increased the need for efficient mechanisms to provide integration methods for multiple information sources. This volume contains a collection of research papers that describe ideas and insights associated with the task of integration.

Journal ArticleDOI
TL;DR: A dynamic coordination policy is proposed that places coordination activities at optimal (and often nonuniform) intervals during the construction of a system and shows that, if a system stabilizes slowly, more intense coordination should occur early in the project.
Abstract: In constructing a software system, extended periods of coding without adequate coordination (such as system integration and testing) can result in considerable fault correction effort. On the other hand, too much coordination can also prove counterproductive by disrupting the smooth flow of development work. The goal, therefore, is to find an optimal level of coordination so as to minimize system construction effort while adhering to functionality and schedule constraints. Previous research, however, has not considered dynamic project factors such as system growth, system stability and team learning when addressing the above coordination problem. Dynamic factors are important because they could lead to differences in the intensity (frequency) of coordination needed at different stages of system construction. Unlike existing studies, we propose a dynamic coordination policy that places coordination activities at optimal (and often nonuniform) intervals during the construction of a system. Our analysis shows that, if a system stabilizes slowly, more intense coordination should occur early in the project. Also, if the team's knowledge of the system improves with time (i.e. learning effects are present), more intense coordination should occur both near the beginning and near the end of the project. Our analysis also shows that, by encouraging more frequent coordination, superior development tools could facilitate team learning. Finally, the application of the coordination model to data from a NASA software project demonstrates that optimally coordinating a project could significantly reduce the system construction cost.