Showing papers on "System integration published in 2000"

Information system integration

Abstract: Consequently, public security and defense organizations can see the real-time locations of various people, units, and equipment in their GIS system, thanks to Global Positioning System (GPS) technology, while getting updates from SAP ERP with details about the current status and capabilities of those units, also updated in real-time as needed using enterprise services. With this bundle, users can create, maintain, and edit the relationships of organizational units (referred to in enterprise SOA terms as ) in public security and defense organizations (such as, for instance, Functional Units brigades, companies, and platoons), deployed or otherwise. In addition, they can read, change, and update the attributes of positions, personnel, and materials within these units.

Paradigm Shifts - E-Business and Business/Systems Integration

Abstract: The last decade or so spawned a host of business and technology innovations. On the business side, we saw business process reengineering, the management philosophies of customer relationship management and supply chain management, virtual organizations, electronic commerce, and business-tobusiness trading exchanges. On the technology side, we saw client-server computing, enterprise resource planning systems, the widespread adoption of Internet protocols, intranets and enterprise information portals, software package support for customer relationship management, supply chain management and other activities related to electronic business, and applications service providers. This tutorial puts put these business and technology innovations into historical context and relates them to one another through the unifying concepts of business integration and systems integration. One theme of the tutorial is the incomplete linkage between business integration and systems integration. Another is the imperfect relationship between the management philosophies of customer relationship management, supply chain management and electronic

Integration in Electronic Exchange Environments

Abstract: Provided the increasing prevalence of electronic exchange environments-including propriety electronic data interchange (EDI) and some Internet-based EDI (e-commerce) systems-we argue that management's decision-making focus vis-a-vis electronic data interchange (EDI)assumes a tactical disposition rather than a strategic one. We offer that the formulation and execution of tactics may be organized around the general question of how to effectively integrate EDI with internal systems, since this appears to be crucial for obtaining the expected performance advantages. We distinguish between two integration concepts, including the integration between the EDI systems and internal systems (interface integration), and the integration among the internal systems (internal integration). Based on theory and literature, we propose that interface integration is favorably related to performance outcomes, and that interface integration and internal integration are positively related. Using data from the Group Insurance industry, we obtain supportive findings. We conclude that tactical EDI planning should centrally focus on interface integration regardless of how intensively management plans to use EDI. We further conclude that management may want to consider internal integration as a risk factor during EDI implementation, because the ability to establish high interface integration may be inhibited or advanced by low or high internal integration, respectively.

System-On-A-Chip: Design and Test

Abstract: From the Publisher: Starting with a basic overview of system-on-a-chip (SoC), including definitions of related terms, this new book helps you understand SoC design challenges, and the latest design and test methodologies. You see how ASIC technology evolved to an embedded cores-based concept that includes pre-designed, reusable Intellectual Property (IP) cores that act as microprocessors, data storage devices, DSP, bus control, and interfaces — all "stitched" together by a User's Defined Logic (UDL). Part One features a discussion of SoC-related design difficulties including hardware-software co-design, reuse design, and cores design. You get practical, real-world design guidance referencing actual product specifications, delivery requirements, and system integration requirements in use by commercial enterprises and under evaluation by the SoC community. Significant attention is paid to the rules and guidelines for making SoC design reusable, including RTL coding guidelines and design validation. Part One concludes with the information you need to develop test benches at both the cores and SoC level. Part Two contains a review of the challenges you face in testing SoC and test methodologies for overcoming these hurdles. Test methods for embedded logic cores, microprocessor cores, micro-controller cores and large memory blocks are included, as well as methods for testing embedded analog and mixed-signal circuits, and Iddq testing on SoC. You also get an overview of material handling, speed-binning, and production flow to apply your knowledge to actual production processes. System-on-a-Chip: Design and Test is an excellent, one-stop reference for SoC and ASIC designengineers, IP designers and providers, and test engineers seeking comprehensive information on SoC design, testing, and production.

Towards integrating GIS and catchment models

Abstract: Modeling the impact of non-point source pollution in catchments is a complex problem, and one that has troubled natural resource managers for many years. The development of spatially distributed hydrologic models has led to improved model forecasting at the cost of requiring more detailed spatial information. In addition, the analysis is much more sensitive to errors in the data. Incorporation of catchment models into a Geographical Information System (GIS) has improved matters by streamlining data input and providing better interpretation of model outputs. This paper reviews different strategies for linking a catchment model with GIS. It examines data issues related to the performance of models and how well they match physical landscape conditions. Integration with GIS is shown to be necessary for the efficient and proper operation of models in resource management situations. The paper concludes that tighter integration between generic sub-models for physical landscape processes and GIS is still required.

Efficient object-oriented integration and regression testing

Abstract: This paper presents a model, a strategy and a methodology for planning integration and regression testing from an object-oriented model. It shows how to produce a model of structural system test dependencies which evolves with the refinement process of the object-oriented design. The model (test dependency graph) serves as a basis for ordering classes and methods to be tested for regression and integration purposes (minimization of test stubs). The mapping from unified modeling language to the defined model is detailed as well as the test methodology. While the complexity of optimal stub minimization is exponential with the size of the model, an algorithm is given that: computes a strategy for integration testing with a quadratic complexity in the worst case; and provides an efficient testing order for minimizing the number of stubs. Various integration strategies are compared with the optimized algorithm (a real-world case study illustrates this comparison). The results of the experiment seem to give nearly optimal stubs with a low cost despite the exponential complexity of getting optimal stubs. As being a part of a design-for-testability approach, the presented methodology also leads to the early repartition of testing resources during system integration for reducing integration duration.

Network-based configuration method for systems integration in test, measurement, and automation environments

Abstract: Network-based methods and systems are disclosed for configuring and building systems and providing systems integration for the test, automation and measurement environment The methods include internet or intranet-based applications that configure and quote a system or system integration project in response to selection of system features, system components and/or system configurations by a network user The methods may be implemented as part of a build-to-order internet application

B2B Application Integration: e-Business-Enable Your Enterprise

Abstract: Preface. Acknowledgments. I. INTRODUCTION. 1. Defining B2b Application Integration. Moving to e-Business. Using B2B Application Integration. What's B2B Application Integration?. Leveraging Your Assets. Applying Technology. Making the Business Case for B2B Application Integration. Middleware and B2B Application Integration. Middleware Makes B2B Application Integration. Approaching e-Business. New e-Tricks for Old Dogs?. Types of B2B Application Integration. Data-Oriented. Application Interface-Oriented. Method-Oriented. Portal-Oriented. Process Integration-Oriented. II. TYPES OF B2B APPLICATION INTEGRATION. 2. Understanding Data-Oriented B2b Application Integration. Going for the Data. Data-Oriented B2B Application Integration by Example. Consider the Data Source. Relational. Object-Oriented. Multidimensional. Other Data Storage Models. Working with Data-Oriented B2B Application Integration. 3. Application Interface-Oriented B2b Application Integration. Application Interfaces. What's an API?. Approaching Application Interfaces. The Interface Tradeoff. Packaged Applications. Packaged Application Technology Architecture. Packaged Application APIs. Other Interfaces. Vertical Market Application Interfaces. Custom Applications. Using Application Interfaces. 4. Method-Oriented B2b Application Integration. Method-Oriented Example. Scenarios. Leveraging Frameworks for B2B Application Integration. The Value of Frameworks. Framework Functionality. Framework Types. Framework Categories. Enabling Technology. Application or Transaction Servers. Distributed Objects. Sharing Methods within Your Trading Community. 5. Portal-Oriented B2b Application Integration. Portals by Example. Portal Power. Web-Enabled World. Single-System Portals. Multiple Enterprise System Portals. Trading Community Portals. Portal Architecture. Web Clients. Web Servers. Database Servers. Back-End Applications. Application Servers. Portals and B2B Application Integration. 6. Process Integration-Oriented B2b Application Integration. What Is Process Integration-Oriented B2B Application Integration?. Implementing Process Integration-Oriented B2B Application Integration. Documenting Processes. Defining Processes. Executing Processes. Tools and Approaches. Process Modeling. Middleware Interfaces. Process Integration and B2B Application Integration. III. e-Business Integration Technology. 7. An Introduction To Middleware. What's Middleware?. Middleware Models. Point-to-Point Middleware. Many-to-Many Middleware. Synchronous versus Asynchronous. Connection-Oriented and Connectionless. Direct Communications. Queued Communications. Publish/Subscribe. Request/Response. Fire-and-Forget. Types of Middleware. RPCs. Message-Oriented. Distributed Objects. Database-Oriented. Transaction-Oriented. Message Brokers. Tough Choices. 8. Transactional Middleware and B2B Application Integration. Notion of a Transaction. The ACIDTest. Scalable Development. Database Multiplexing. Load Balancing. Fault Tolerance. Communications. Application Servers. Evolving Transactions. Enterprise JavaBeans. Transactional COM+ (Using AppCenter). Future of Transactional Middleware. 9. RPCS, Messagig, and B2B Application Integration. RPCs. Message-Oriented Middleware. Future of MOM. 10. Distributed Objects and B2B Application Integration. What Works?. What's So Difficult? What's So Easy? What's a Distributed Object?. The General Idea of ORBs. CORBA. COM+. The Realities. 11. Database-Oriented Middleware and B2B Application Integration. What Is Database-Oriented Middleware?. Types of Database-Oriented Middleware. ODBC. JDBC. OLEDB. Going Native. Database Gateways. Ready for Prime Time. 12. Java Middleware Standards and B2B Application Integration. Categories of Java Middleware Standards. Database-Oriented. Inter-Process. Message-Oriented. Application-Hosting. Distributed Objects. J2EE. Built-in Middleware. Transactional J2EE. Messaging J2EE. Distributed App J2EE. Middleware Platforms Emerging. The Future of Java and Middleware. 13. Message Brokers and B2B Application Integration. Message Broker Services. Why a New Layer?. Considering the Source (and Target). Message Transformation Layer. Schema Conversion. Data Conversion. Intelligent Routing. Rules Processing. Message Warehousing. Repository Services. Graphical User Interface. Directory Services. Management. Adapters. Thin Adapters. Thick Adapters. Static and Dynamic Adapters. Using an API. Other Features. Topologies. The Future of B2B Application Integration and Brokers. IV. B2B APPLICATION INTEGRATION STANDARDS. 14 Xml And B2b Application Integration. The Value of XML. What XML Is. What XML Adds. What XML Does Not Add. XML Meets Middleware. Integration Solutions. XML-Enabled Standards. XML and B2B Application Integration. 15 Using Rosettanet For B2b Application Integration. RosettaNet History. What's RosettaNet?. Business Process Modeling. Business Process Analysis. PIPDevelopment. Dictionaries. It's the PIP. The Technology. PIP Communications. PIPMessage Structure. RosettaNet Networked Application Protocols. RosettaNet and B2B Application Integration. 16. Biztalk And B2b Application Integration BizTalk Framework. BizTalk Documents. BizTalk Message Structure. Document Routing. BizTalk Architecture. Schema Management. Framework Portal. BizTalk Server. Routing Documents. Delivering Documents. Security. Application Integration Components. BizTalk Management Desk. BizTalking. 17. Using Xslt For B2b Application Integration. What's XSLT? The Mechanisms. XSLT Processors and Processing. Transformation Process. XSLT B2B Applications. Schema Conversions. Converting XML to Something Else, and Vice Versa. XSLT and B2B. 18. Understanding Supply Chain Integration. Value of the Chain. Defining Your Supply Chain. Extending Applications. Binding the Home System to a Stranger's. The Process. Supply Chain Technology. Supply Chains Organize. 19. B2B Application Integration Moving Forward. Problem Domains Change. B2B Applications Emerging. Moving from EDI to XML. Moving from Data-Oriented to Application-Oriented Integration. Loose Ends. Security. Performance and Scalability. Administration. Middleware Vendor Approaches. Data-Oriented. Application Integration-Oriented. Process Integration-Oriented. Transaction-Oriented. Distributed Object-Oriented. United We Win, Divided We Fail-Technologies Join Forces. Selecting B2B Technology. Approaches. Which One? B2B Application Integration-Clearly the Future. V. APPENDIXES. Appendix A: Integrating SAP R/3. Appendix B: Integrating PeopleSoft. Appendix C: RosettaNet PIP Specification. Bibliography. Index.

Putting it all together: improving display integration in ecological displays.

Abstract: Computer displays are being designed for increasingly larger industrial systems. As the application domain scales up, maintaining integration across different kinds of views becomes more challenging. This paper presents the results of a study of three different approaches to integration based on the spatial and temporal proximity of related information objects. The domain used for evaluation was a simulation of an industry-scale conventional power plant. All three displays were ecological displays developed using an abstraction hierarchy analysis. Views were integrated in a high-space/low-time, low-space/high-time, and high-space/high-time integration of means-end related objects. During a fault detection and diagnosis task, it was found that a low level of integration, high-space/ low-time, provided the fastest fault detection time. However, the most integrated condition, high-space/high-time, resulted in the fastest and most accurate fault diagnosis performance. Actual or potential applications of this research include computer displays for large-scale systems such as network management or process control, for which problem solving is critical and integration must be maintained.

Interpreting integration with respect to information systems in organizations – image, theory and reality

Abstract: The integration of information systems (IS) is a phrase which is commonly used in both research and practice within the IS field and across many organizational contexts. This paper uses a historical review to explore how the image of integrated IS has been constructed, evolved over three decades and how this has resulted in the widespread acceptance of idealized goals and benefits. A literature search for an underlying theoretical basis for the concept of systems integration is made, highlighting a diversity of opinion. Two case studies are used to examine the meaning of integration relative to the images and ideals, theory and reality. The study concludes that there is an urgent need for better conceptual and theoretical models of integration to enable more effective discourse of the concept. These models must also encompass and include more diverse non-technical factors for the adoption of more complex forms of IS.

Power electronics building block and system integration

Abstract: The power electronics building block (PEBB) concept is an integrated systems approach to standardize power electronics components and packaging techniques in the form of interchangeable subassemblies and modules. This paper presents the overview of this concept and some of the issues such as the soft-switching techniques for the PEBBs, the packaging approaches, the communication among the PEBBs, and the system-level compatibility. One of the research prototype systems is also demonstrated in this paper.

How useful are strategic plans for information systems

Abstract: Although much research has been done in the area of strategic planning for information systems (IS), relatively less research has focused on the output of the IS planning process, namely, the IS plan. This paper examines the usefulness of IS plans through a field survey of 136 IS executives. Results indicate that IS plans are generally perceived to be useful for supporting business objectives, improving systems integration, exploiting information technology (IT) for competitive advantage, and prioritising IS development projects. Conversely, IS plans are perceived to be less useful for clarifying the role of IS, evaluating IS performance, anticipating surprises and crisis, and adapting to unanticipated situations. Implications of these results are discussed.

A synthetic environment for dynamic systems control and distributed simulation

Abstract: Rapid prototyping and controlled motion evaluation of complex human-machine interfaces, from nuclear plant operation panels to deep submerged underwater vehicles to advanced airplane cockpits, require hardware-in-the-loop, man-in-the-loop, and software integration. What appears to be needed is specific software to give designers tools for analyzing and simulating complex and integrated projects. The research software described in this article promises to fill that need, providing a new synthetic environment for simulation and control synthesis of dynamic systems. The article addresses problems of high performance, realistic environments, and vehicle simulation, with particular attention to synthetic world creation and visualization. The new software is capable of handling most of the simulation and visualization requirements highlighted.

DataFoundry: information management for scientific data

Abstract: Data warehouses and data marts have been successfully applied to a multitude of commercial business applications. They have proven to be invaluable tools by integrating information from distributed, heterogeneous sources and summarizing this data for use throughout the enterprise. Although the need for information dissemination is as vital in science as in business, working warehouses in this community are scarce because traditional warehousing techniques do not transfer to scientific environments. There are two primary reasons for this difficulty. First, schema integration is more difficult for scientific databases than for business sources because of the complexity of the concepts and the associated relationships. Second, scientific data sources have highly dynamic data representations (schemata). When a data source participating in a warehouse changes its schema, both the mediator transferring data to the warehouse and the warehouse itself need to be updated to reflect these modifications. The cost of repeatedly performing these updates in a traditional warehouse, as is required in a dynamic environment, is prohibitive. The paper discusses these issues within the context of the DataFoundry project, an ongoing research effort at Lawrence Livermore National Laboratory. DataFoundry utilizes a unique integration strategy to identify corresponding instances while maintaining differences between data from different sources, and a novel architecture and an extensive meta-data infrastructure, which reduce the cost of maintaining a warehouse.

A strategic supply chain simulation model

Abstract: In this paper, we describe a simulation game designed to quantify the benefits of an enterprise resource planning system coupled with the balanced scorecard framework in an extended enterprise. We present three scenarios of the same enterprise: a base case scenario with a non-integrated legacy system, a scenario with an integrated, enterprise resource planning system, and a scenario with an enterprise resource planning system using the balanced scorecard framework. Results from this game support our research and teaching activities on the benefits of systems integration, data and process standardization, visibility across the business enterprise, improved decision support functionality, and operationalizing strategy.

Consistent Integration of Formal Methods

Abstract: The usability of formal concepts for system design depends essentially on their integration in the design process. We discuss several possible levels of integration: technical integration of tools considering APIs and tool interfaces, conceptual integration of metamodels of description formalisms combined with hard and soft constraints, semantical integration of semantics of description techniques using a common semantic model, and finally methodical integration by an embedding in the development process. We show the feasibility of such an integrated approach and its advantages presenting AutoFocus/Quest, a formal method CASE-Tool with its levels of integration. Parts of a banking system model are used as example.

Calculating costs for quality of security service

Abstract: Presents a quality-of-security-service (QoSS) costing framework and a demonstration of it. A method for quantifying costs related to the security service and for storing and retrieving security information is illustrated. We describe a security model for tasks, which incorporates the ideas of variant security services invoked by the task, dynamic network modes, abstract security level choices and resource utilization costs. The estimated costs can be fed into a resource management system to facilitate the process of estimating efficient task schedules. Integration and scalability issues have been taken into account during the design of the QoSS costing demonstration, which we believe is suitable for incorporation into a resource management system research prototype.

Mechatronic systems: concepts and applications

Abstract: The synergetic integration of mechanical processes, microelectronics and information processing opens new possibilities to the design of processes as well as for its automatic control. The solution of tasks within mechatronic systems is performed on the process side and the digital-electronic side. As the interrelations during the design play an important role, simultaneous engineering has to take place from the very beginning. Mechatronic systems are developed for mechanical elements, machines, vehicles and precision mechanic devices. The integration of mechatronic systems can be performed by the components (hardware integration) and by information processing (software integration). The information processing consists of low-level and high-level feedback control, supervision and diagnosis and general process management. Special signal processing, model-based and adaptive methods are applied. With the aid of a knowledge base and inference mechanisms, mechatronic systems with increasing intelligence will b...

On the way to component-based 3D/4D geoinformation systems

Abstract: Fundamental Principles- Examples of Today's Geoinformation Systems- Data Modelling and Management for 3D/4D Geoinformation Systems- Systems Development: from Geodatabase Kernel Systems to Component-Based 3D/4D Geoinformation Systems- Data and Methods Integration- Systems Integration- Outlook

On integrating mobile devices into a workflow management scenario

Abstract: While the desire to gain full access to stationary information sources (e.g. the company's backoffice database) from abroad is only natural, inherent design limitations (such as a lack of computational power, extremely limited resources and closedness to modifications), mean that mobile system integration can still be a difficult issue. In contrast to other approaches to the field, the "Java Border Service Architecture" introduced in the article does not require modifications to the mobile device's system software or the application environment to be accessed from the mobile system.

A mediator-based approach for decentralised production planning, scheduling and monitoring

Abstract: The improvement of business processes along the supply chain has become a focus in industry and research during the past decade. Based on advanced technologies for communication and data structuring this paper describes a software system called the Mediator that provides support for integrating decision-making of several separate actors in decentralized business organizations. The Mediator is designed to offer an adequate level of decision-making integration, taking into account the effort needed for the integration of heterogeneous computer systems by use of the Extended Mark-up Language (XML). The approach is demonstrated for industrial pilot cases in multi-site and supply-chain production.

Taxonomy of Factors for Information System Application Integration

Abstract: Application integration technology is a new class of system integration that involves the development of new strategic business solutions. These securely integrate functionality from disparate applications. In considering this, the presented paper seeks to describe the application integration arena and proposes a novel taxonomy for this new scope of technology. Furthermore, it analyses factors that are related with the impact of application integration on companies and presents a number of research questions that are associated with this area.

Optoelectronics-VLSI system integration Technological challenges

Abstract: Hybrid VLSI-optoelectronics, also called smart-pixel technology, exploits the respective strengths of optics and electronic processing for the production of optical information processing systems of high performance. The recent integration of micron-size optoelectronic components such as emitters, photodetectors and spatial light modulators within VLSI electronic chips allows the fabrication of on/off chip data communication rate systems of the order of 10 12 pin-Hz. This aggregate rate is at least one order of magnitude higher than is presently achievable in electronics alone. Several issues, however, remain to be resolved in order to fully benefit from this technology. These include the relevance of optics in information processing in general and computer science in particular, the design and choice of the logic complexity of the electronic circuitry, its interfacing with optoelectronic components, the assembly and testing of the resulting systems. These technological challenges are discussed in this article in the light of the rapid progress achieved in this field.

Asset Management Model and Systems Integration Approach

Abstract: Transportation asset management is an integrated set of best practices and systems that achieve optimal and cost-effective investment and use of transportation assets throughout their service life cycle. Most infrastructure management programs and systems contain certain elements of asset management functions. However, they lack a strong capacity to accomplish the overall asset management goal. Presented is an asset management model together with an approach for systems integration. The asset management model illustrates basic asset management goals, strategies, principles, and analysis methods. An example of an integrated maintenance program incorporates the features of the model. Supporting the asset management model is a systems integration approach that demonstrates how component asset management systems can be integrated at different stages of their development life cycles. The integration process is needed to ensure that system interoperability truly supports an effective asset management program. The approach can be defined in five phases: (a) business integration, (b) system requirements integration, (c) logical design integration, (d) physical design and development integration, and (e) implementation integration. Each phase carries a particular integration objective and develops unique integration products. An operational scenario tool is introduced as an implementation strategy for asset management.