scispace - formally typeset
Search or ask a question

Showing papers on "System integration published in 1994"


Journal ArticleDOI
TL;DR: A case study in which computer-based communication systems were used to support team-based coordination of IT management across dispersed business units and reveals possibilities for future approaches to IT coordination in large, dispersed organizations.
Abstract: The coordination of information technology (IT) management presents a challenge to firms with dispersed IT practices. Decentralization may bring flexibility and fast response to changing business needs, as well as other benefits, but decentralization also makes systems integration difficult, presents a barrier to standardization, and acts as a disincentive toward achieving economies of scale. As a result, there is a need to balance the decentralization of IT management to business units with some centralized planning for technology, data, and human resources. Here we explore three major mechanisms for facilitating interunit coordination of IT management: structural design approaches, functional coordination modes, and computer-based communication systems. We define these various mechanisms and their interrelationships, and we discuss the relative costs and benefits associated with alternative coordination approaches. To illustrate the cost-benefit tradeoffs of coordination approaches, we present a case study in which computer-based communication systems were used to support team-based coordination of IT management across dispersed business units. Our analysis reveals possibilities for future approaches to IT coordination in large, dispersed organizations.

182 citations


Journal ArticleDOI
TL;DR: Based on a national study of nine organized delivery systems, measures of three types of integration that occur in vertically integrated health systems—functional, physician-system, and clinical are developed and used as a “scorecard” to assess progress toward achieving integration objectives.
Abstract: Organized vertically integrated health systems are in a key position to play a major role in present health care reform efforts. To demonstrate a competitive advantage in the new health care environment, however, integration efforts must be successful. Based on a national study of nine organized delivery systems, this article develops measures of three types of integration that occur in vertically integrated health systems--functional, physician-system, and clinical. These measures can be used as a "scorecard" to assess progress toward achieving integration objectives.

103 citations


Journal ArticleDOI
TL;DR: The systems integration problem, defined as coupling GIS and other systems, is analysed by the use of two models based on database and federated database reference models, including a three-schema model of a system.
Abstract: The systems integration problem, defined as coupling GIS and other systems, is analysed by the use of two models based on database and federated database reference models. A three-schema model of a system enables the classification of incompatibilities between systems in terms of differences in external, conceptual and internal schemas. A systems reference model identifies transformation, constructor and accessor operations as the basic mechanisms to overcome these differences. The possible architectures of integrated systems are defined in terms of the presence of these operations and their general strengths and weaknesses are assessed.

79 citations


Journal ArticleDOI
TL;DR: In this article, the authors use object-based models to capture and make visible the system level coordination structure of complex projects, which facilitates the development of a shared view necessary for effective project management.
Abstract: The paper uses object based models to capture and make visible the system level coordination structure of complex projects. These models facilitate the development of a shared view necessary for effective project management. In the paper, development and use of the models are illustrated using examples drawn from the design of custom silicon. We examine three custom silicon design projects to identify the significant coordination problems encountered as well as the difficulties of using activity based project management tools. Then we develop object based models of coordination structure as a tool to overcome these difficulties. We use these models to capture a project manager's view of the four stages of the custom silicon design cycle: design definition, chip design, prototype manufacture, and system integration. We conclude by discussing the relationship between the coordination structure approach and other project management tools, and the managerial advantages of the proposed approach in the management of complex projects. The approach has particular value for the management of projects in which the task structure is complex, uncertain, and unstable, as is typically the case in new product development. >

71 citations


Journal ArticleDOI
TL;DR: The sociotechnical systems approach suggests that the same new information technology is likely to have different implications in various companies in terms of system integration, work design, and organization structure.
Abstract: The integration of change over time is one of the ongoing challenges in a firm's life. Organizations seem to develop unique mechanisms that help them facilitate the integration of changes throughout and across organizational units. Information technologies based on electronic data processing are having a widespread impact on information flow within and between firms, on the structural configurations of the firm, and on management's ability to integrate change. This article proposes sociotechnical systems as a framework for examining the organizational implications of new information technology systems and as a tool for guiding the integration of change. The implications of the implementation of a local area network and its concomitant impact in a software development firm are examined over a 4-year period. The sociotechnical systems approach suggests that the same new information technology is likely to have different implications in various companies in terms of system integration, work design, and organ...

56 citations


Journal ArticleDOI
TL;DR: One focus is on various control issues that must be confronted before an AHS is deployed, and a more detailed overview of automated highway systems (AHS), the part of IVHS of most interest to control engineers.
Abstract: Intelligent vehicle highway systems (IVHS) involve the systems integration of many emerging technologies to effectively address the needs, both present and future of the nation's roadway complex. An introduction to and brief history of IVHS is presented. Then, a more detailed overview of automated highway systems (AHS), the part of IVHS of most interest to control engineers, is given. One focus is on various control issues that must be confronted before an AHS is deployed. >

51 citations


Journal ArticleDOI
TL;DR: OPIS demonstrates the feasibility and power of using standard object-oriented project models to achieve CAPM system integration and uses a shared object–oriented database as the central unifying core of an integrated project planning system.
Abstract: Future computer-aided project management (CAPM) software will be greatly improved through the technologies of project modeling—the rich, general-purpose representation of the project in the computer—and system integration—the sharing of computer models among applications Our approach is to achieve system integration by establishing standard models that all applications can adopt and share This requires a standard data model that specifies the general data-representation approach, a standard domain model that provides a schema or language for representing construction information, and a project model or database for information about a specific project that can be shared among multiple computer applications This paper reviews these standard models and then describes our prototype integrated system called the object model–based project information system, or OPIS OPIS uses a shared object–oriented database as the central unifying core of an integrated project planning system that includes an interface to an intelligent CADD program, a plan-generation expert system, an estimating application, and a scheduling application OPIS demonstrates the feasibility and power of using standard object-oriented project models to achieve CAPM system integration

48 citations


Proceedings Article
01 Jan 1994
TL;DR: A new client-server based system which is centered around a lifetime data repository (LDR) is under construction, to maintain the patient centered decision support aspects of the existing HELP* system while providing an open architecture that supports faster application development and allows execution of applications to be distributed across many computers.
Abstract: A new client-server based system which is centered around a lifetime data repository (LDR) is under construction. The goal of the new system is to maintain the patient centered decision support aspects of the existing HELP* system while providing an open architecture that supports faster application development and allows execution of applications to be distributed across many computers. These goals are achieved by implementing the system with software components that are commercially available or by adhering to national and international standards for software integration. Keys to successful integration include the use of MS-DOS @, OS/2#, and UNIX Section as operating systems, Microsoft OLE 2.0 as a standard interface to the clinical database, the use of TUXEDO as a transaction/communication manager, and the use of ORACLE [symbol: see text] RDBMS as the underlying database management system.

45 citations


Proceedings ArticleDOI
11 Sep 1994
TL;DR: In this paper, the authors propose a methodology for automatically generating redesign suggestions for reducing setup costs for machined parts based on interpreting the design as a collection of machinable features.
Abstract: All mechanical designs pass through a series of formal and informal redesign steps involving the analysis of func tionality manufacturability cost and other life cycle factors The speed and e cacy of these steps has a major in uence on the lead time of the product from conceptualization to launching In this paper we propose a methodology for automatically generating redesign suggestions for reducing setup costs for machined parts Our approach is based on interpreting the design as a collection of machinable features Our method ology generates alternate machining features by making geo metric changes to the part and adds them to the feature set of the original part The designer may provide restrictions indicating that certain surfaces and volumes should not be changed in which case all redesign suggestions generated by our approach honor those restrictions Using features from the extended feature set generated above one or more new designs may be found that need fewer setups than the original part INTRODUCTION In all component design procedures the design goes through a design cycle consisting of analysis and review of the design for cost e ectiveness and quality Ideally the design review would take into account the capabilities and costs of the production processes to be used However it is not always possible to do this for all facets of the production process particularly for complicated methods such as ma chining After the component enters the production cycle experienced process planners and machinists may discover that alterations in the design would be bene cial but few companies have organizational structures that enable the design team to take advantage of this information If tools were available at the design stage to suggest design revisions for cost containment this would help in reducing the prod uct realization cost This paper describes a rst step toward the development of such a tool The production cost of a machined component comes from many factors but one of the biggest factors is the number of setups it takes to machine the component Re ducing the number of setups will reduce the machine s idle time and will require fewer work holding devices Further more reducing the number of setups will result in better machining tolerances In this paper we describe a struc tured methodology for generating the possible modi cations to a component for reducing the number of setups it takes to machine the component The basic steps of the redesign scheme are as follows Initial Step Preprocessing Get the design of the part P from the designer The designer may also provide re strictions indicating that certain surfaces and volumes should not be changed in which case all redesign sug gestions generated by our approach will honor those restrictions This step in described in Section Step Analyze the current design Step a Find all the possible machining features in the original part P which can be removed from the stock S to produce P for details see Put all these features into the set F Step b Find the precedence constraints on the order in which the features in F can be machined as described in Section Step c As described in Section nd the lowest number of setups in which P can be machined from S using the features in the set F This in volves examining Feature Based Models FBMs in F these are subsets of F that contain no re dundant features and are su cient to create P Step Generate possible feature modi cations For each feature f F use feature modi cation oper ators see Section to generate alternate features for f These alternate features will have di erent geome try from f but will satisfy the designer s restrictions Let F be the set of all of the old and new features Step Generate and present design alternatives Step a Determine precedence constraints among the features of F see Section Step b If FBMs can be found in F that require fewer setups than the original part then present them to the designer as redesign suggestions see Section The paper is organized as follows Section contains def initions Section reviews related work Sections through describe the details of our approach with an example to explain how the procedure works Finally Section includes concluding remarks and ideas for future work DEFINITIONS AND NOTATION A part P is the nal component created by executing a set of machining operations on a piece of stock S A work piece is the intermediate object produced by performing zero or more of the operations needed to create P To represent P and S we use geometric solids cf For example Figure shows an example part which we will call P this part would typically be machined from a rectangular piece of stock A machining feature is a portion of the workpiece a ected by a particular machining operation A machining feature consists of three components the volume removed the ap proach direction the direction from which the operation is performed and the type of operation In this paper the only types of operations we will consider are end milling slot milling and drilling performed in a vertical machining cen ter Each machining operation is capable of creating certain types of surfaces drilling produces cylindrical and conical surfaces and end milling and slot milling produce planar and cylindrical surfaces The basic three types of machin ing features used in this paper are shown in Figure As an example Figure shows some of the end milling slot milling and drilling features for the part P F is the set of all machining features f that could po tentially be used in generating P from S for details see For the part P Figure shows some of the features in F An FBM feature based model F F is a set of machining features such that subtracting F from the stock S produces the part P and F does not contain any redundant feature s For example Figures and show two di erent FBMs for the part P In general a single part may have several dif ferent FBMs and thus there may be several di erent ways to machine the part

38 citations


Journal ArticleDOI
TL;DR: In this paper, a survey of logistics professionals revealed that centralized structures accommodated logistics system integration better than decentralized structures and that centralized firms spent a lower percentage of net sales on logistics costs and information system support costs than decentralized firms.
Abstract: Organizational structure significantly influences firm performance. A recent survey of logistics professionals revealed that centralized structures accommodated logistics system integration better than decentralized structures. Also, centralized firms spent a lower percentage of net sales on logistics costs and information system support costs than decentralized firms. On the other hand, no signficiant differences were identified between centralized and decentralized firms in terms of information system performance. Information system support needs were addressed comparably regardless of organizational structuring. However, while centralized and decentralized firms exhibited similar capabilities in terms of effectiveness (reaching goals), centralized firms appeared to be more efficient (resource utilization).

33 citations


BookDOI
01 Jan 1994
TL;DR: This paper presents methods for Planning and Evaluating the Integration and Collaboration of Information Models, Software, and Theories for Integration, and discusses the nature and Metrics of Integration.
Abstract: Preface. I: Integration in Concurrent Design. II: Integration in CIM/E. III: Methods for Planning and Evaluating the Integration and Collaboration. IV: Interaction and Collaborative Work. V: Information Models, Software, and Theories for Integration. Panel Reports: 1: Integration Opportunities and Requirements. 2: The Design of Integration. 3: Integration Implementation. 4: Nature and Metrics of Integration. Index.

Journal ArticleDOI
TL;DR: This paper presents an approach to the development of concurrent engineering software applications based on a knowledge sharing technology called federation, where individual programmers write their programs in the form of separate modules called software agents, which interoperate with their peers using an expressive communication standard called Agent Communication Language.
Abstract: This paper presents an approach to the development of concurrent engineering software applications based on a knowledge sharing technology In this approach, individual programmers write their programs in the form of separate modules called software agents, which interoperate with their peers using an expressive communication standard called Agent Communication Language The runtime activities of the individual software agents are coordinated by task-independent programs called facilitators Facilitators perform a wide variety of tasks, including the automated selection of agents to accomplish subtasks, the mediation of terminology, the buffering of partial knowledge in communication between agents, and the management of communication with other facilitators on other machines Once set in operation, software agents interoperate to accomplish the overall task in a heterogeneous distributed architecture called federation The paper discusses the major aspects of this approach and briefly describes three con

Proceedings Article
01 Jan 1994
TL;DR: A new discipline, known as Environmental Informatics, is emerging which combines research fields such as data base systems, geographic information systems, modeling and simulation, computer graphics, user interfaces, neural networks, knowledge processing, and systems integration.
Abstract: In recent years, systems for processing environmental information have been evolving from research and development systems to practical applications. Today, many of these systems already support environmental activities at the industrial, governmental, and worldwide levels. A broad range of applications in environmental protection is covered by these systems, including monitoring and control, conventional information management, computation and analysis, as well as planning and decision support. A new discipline, known as Environmental Informatics, is emerging which combines research fields such as data base systems, geographic information systems, modeling and simulation, computer graphics, user interfaces, neural networks, knowledge processing, and systems integration. Keyword Codes: H.0; I.0, J.2

Journal ArticleDOI
TL;DR: The concept of multimedia within the context of integration of these database systems will be presented and an example is given on how to access these information systems by a radiologist's desktop personal computer.

Journal ArticleDOI
TL;DR: This software integration greatly enhances the use of geographically oriented resource data and knowledge accumulated from Forest Service experts to assist in project planning, alternative development and environmental assessment.

Journal ArticleDOI
TL;DR: It is shown that the use of an object-oriented data model for building a “uniform” view of several databases can greatly simplify this task, and actually extends the scope of integration towards two directions.
Abstract: The object-oriented paradigm has several features that facilitate the integration of heterogeneous data management systems. One of the main problems in the integration is to provide users with the same data model and language to access very different systems. This problem exists in all kinds of distributed heterogeneous data management systems, independently from their integration architecture (like classical distributed databases, federated databases, multidatabases). This paper shows that the use of an object-oriented data model for building a “uniform” view of several databases can greatly simplify this task, and actually extends the scope of integration towards two directions. The first concerns the integration of data management systems to which traditional integration techniques, based on mappings among data models, cannot be applied. The second direction moves the goal of integration to re-using not only data but to re-using data and application software using these data. In the paper we also briefly discuss some requirements for an object-oriented integrated platform.

Journal ArticleDOI
TL;DR: It is argued that in addition to networking and the selection of a distributed client/ server architecture that conforms to open systems protocols, the adoption of standards and the establishment of a management technology infrastructure would provide the necessary steps and mechanisms to allow for a smoother transition to greater sophistication in the development of total systems integration.
Abstract: This article discusses the importance of integrating health care with information technology to improve the efficiency, effectiveness, and innovation of health care institutions. It is argued that in addition to networking and the selection of a distributed client/server architecture that conforms to open systems protocols, the adoption of standards and the establishment of a management technology infrastructure would provide the necessary steps and mechanisms to allow for a smoother transition to greater sophistication in the development of total systems integration.


Book ChapterDOI
28 Feb 1994
TL;DR: In this work, it is shown how process traceability models and process guidance models can be developed and related in a standard repository framework and demonstrated with a prototype requirements engineering environment developed in ESPRIT project NATURE.
Abstract: Evolution is a fact of life in information systems. Not only systems evolve but also their development processes. IS environments must therefore be designed for accommodating and managing change. The management of process meta models in repositories is one important step; we show how process traceability models and process guidance models can be developed and related in a standard repository framework. In addition, the currently available tool integration along the presentation, data, and control perspectives have to be augmented for process integration. In our process-adaptable and interoperable tool concept, tool behavior is directly influenced by the process guidance model and automatically traced according to the traceability model. The approach is demonstrated with a prototype requirements engineering environment developed in ESPRIT project NATURE.

Book
27 Oct 1994
TL;DR: Information Needs Plant Personnel Managers Facility Management Systems GIS and FM Overview Applications Intelligent Drawings Accuracy Drawing Structure and Organization Drawings and Photos from Aerial Surveys Coordination Among Project Participants Converting Available Drawings Integration of Drawings Importing Map Files from Public Sources Integration Factors Affecting Integration.
Abstract: Information Needs Plant Personnel Managers Facility Management Systems GIS and FM Overview Applications Intelligent Drawings Accuracy Drawing Structure and Organization Drawings and Photos from Aerial Surveys Coordination Among Project Participants Converting Available Drawings Integration of Drawings Importing Map Files from Public Sources Database Management Compliance Waste Site Characterization Site Visualization Site Remediation Approach for an ES&H Facility Management System Information Products Prototype System Executive Information Systems Example Information Products Systems Integration Factors Affecting Integration The Players The Information The Data Model Regulatory Information System Management Computer Hardware Software System Use System Implementation References Index

Journal ArticleDOI
TL;DR: An integrated system, essential to the city of Los Angeles during the 1992 riots and the 1994 earthquake, is examined to demonstrate the usefulness and benefits of expert systems and multimedia integration.
Abstract: Expert systems and multimedia are being incorporated into organizations at increasing rates because, while being independently developed, they possess capabilities appropriate for integration with each other. This paper examines the potential for such integration, providing support to users beyond the capabilities of each independently used technology. An integrated system, essential to the city of Los Angeles during the 1992 riots and the 1994 earthquake, is examined to demonstrate the usefulness and benefits of expert systems and multimedia integration. The potential for this integration is further explored by examining issues related to an integration framework where the two technologies support each other. Three integrated prototype systems are reviewed to promote the legitimacy of expert systems and multimedia integration. Preliminary findings conclude that this integration will offer benefits to various applications.

Journal ArticleDOI
TL;DR: In this paper, the authors take a fundamental look at the concept of integration to determine its essential properties, and it is expected that this will lead to a better understanding of the concept, and also to applications in manufacturing environments which might ultimately lead to the full realization of computer integrated manufacturing.
Abstract: As manufacturing gets ever more competitive, integration will come to be seen as a means whereby performance can be improved while flexibility is, at the same time, also being enhanced. Takes a fundamental look at the concept of integration to determine its essential properties. It is expected that this will lead to a better understanding of the concept, and also to applications in manufacturing environments which might ultimately lead to a full realization of computer integrated manufacturing (CIM).


Proceedings ArticleDOI
Medsker1, Turban
01 Jan 1994
TL;DR: This paper provides a comprehensive framework and examples of such an integration of neural computing and expert systems to achieve some improvements in the implementation of each as well as increase the scope of application.
Abstract: Expert (or knowledge-based) systems are used today either as stand-alone or in conjunction with other computer based information systems (CBIS) in thousands of organizations world wide to provide decision support for solving problems that traditional information systems were unable to solve. Neural computing is an emerging promising technology with few successful applications. By integrating the two technologies one can achieve some improvements in the implementation of each as well as increase the scope of application. This paper provides a comprehensive framework and examples of such an integration. >

DOI
01 Jul 1994
TL;DR: In this article, the authors propose a method to solve the problem of "uniformity" and "uncertainty" in the context of health care, and propose a solution.
Abstract: 1

Proceedings ArticleDOI
05 Sep 1994
TL;DR: The paper outlines one architecture which has been developed for the control of a robotic excavator and compares it with the architecture adopted for an intelligent paper roll manipulator and certain of the problems of achieving the required level of autonomy within the specified environments are identified.
Abstract: The development of intelligent autonomous and semi-autonomous systems capable of operating safely in unstructured environments such as those outlined above will to a significant degree be dependent on the achievement on the levels of system integration and the transfer of functionality between the mechanical, electronic and software domains suggested by mechauonics. In particular, the system must be structured around an architecture which is capable of accommodating a range and variety of machine geometries and operational modes and which is also capable of supporting the associated sensing and safety requirements. The paper outlines one such architecture which has been developed for the control of a robotic excavator and compares it with the architecture adopted for an intelligent paper roll manipulator. Both these architectures are based around a goal oriented approach with the selection and organisation of the individual tasks necessary to achieve the desired goal left to the system. The extension of these architectures to incorporate the safety requirements for operation in an unstructured environment in association with other items of plant and machinery and with humans is also considered along with associated sensing requirements. From these considerations, certain of the problems of achieving the required level of autonomy within the specified environments are identified.

Journal ArticleDOI
TL;DR: A formal, unified methodology for design and management in order to facilitate AEC collaboration is described and constraint management is described as the core of the unified methodology.
Abstract: This paper describes a formal, unified methodology for design and management in order to facilitate AEC collaboration. Issues related to the AEC industry pave the way for a description of the collaborative AEC environment and its requirements for supporting information systems. Next, constraint management is described as the core of the unified methodology. A system architecture is briefly presented with an illustrative example. A discussion of integration philosophies and a comparison with parallel research in the area of system integration in the civil engineering domain conclude the paper.

Journal ArticleDOI
TL;DR: Fuzzy logic, case-based reasoning, and commonsense modeling are among the new research areas that hold the most promise for a second wave of smart systems for business use, and this time the promise might become a reality.
Abstract: Such issues as standards, operational performance, and system integration capabilities have hindered the development and implementation of expert system applications. Fuzzy logic, case-based reasoning, and commonsense modeling are among the new research areas that hold the most promise for a second wave of smart systems for business use, and this time the promise might become a reality.

01 Jan 1994
TL;DR: It is concluded that efficient integration is facilitated by the preexistence of a plan that defines a common methodological framework and computing environment for all component systems, and the most essential integration elements are a common referencing convention, data base, and computerized user interface.
Abstract: The integration of pavement and bridge management systems is addressed for the New York State Thruway Authority. A phased plan provides a unifying framework for development and accommodates agency requirements. Early efforts focus on the development of the data base and analytical methodologies for pavement management. Subsequent work produces similar methodologies for bridge management, expands the data base to serve bridge management needs, and integrates the data base with pavement and bridge analysis programs. The requirement for integration is maintained throughout the entire planning, design, and implementation process. The integrated computer system is prototyped as Windows-based program managers using graphical user interfaces to unify C/C++ applications. Early prototypes highlight remaining issues of integration and facilitate the selection of appropriate procedures for interfacing the data base with the application programs. Important issues related to system integration are discussed. On the basis of developments to date, it is concluded that (a) efficient integration is facilitated by the preexistence of a plan that defines a common methodological framework and computing environment for all component systems, and (b) the most essential integration elements are a common referencing convention, data base, and computerized user interface.

Journal ArticleDOI
TL;DR: The paper outlines principles and methods of Integration Engineering with respect to developing client-server based business information systems and shows how the methodology was successfully applied in a large project.
Abstract: Integrating information systems has become a major issue in IS development and information management. As organizational change is a permanent process, new information systems have to be developed continually to meet new requirements, but old ones also continue to be in use. This means that new components have to be integrated into existing environments. To make the process of permanent extension and modification manageable, a methodology is needed that supports easy integration of modules into existing environments. We call this methodology Integration Engineering. The paper outlines principles and methods of Integration Engineering with respect to developing client-server based business information systems. The methodology was successfully applied in a large project. The goal of the project was to develop an enterprise-wide information system for a plantbuilding company. The case study is described in the second part of paper.