Showing papers on "Enterprise systems engineering published in 1995"

Methodology for the Design and Evaluation of Ontologies

Abstract: As information systems play a more active role in the management and operations of an enterprise, the demands on these systems have also increased. Departing from their traditional role as simple repositories of data, information systems must now provide more sophisticated support to manual and automated decision making; they must not only answer queries with what is explicitly represented in their Enterprise Model, but must be able to answer queries with what is implied by the model. The goal of the TOVE (TOronto Virtual Enterprise) Enterprise Modelling project is to create the next generation Enterprise Model, a Common Sense Enterprise Model. By common sense we mean that an Enterprise Model has the ability to deduce answers to queries that require relatively shallow knowledge of the domain. We are taking what can be viewed as a `second generation knowledge engineering' approach to constructing our Common Sense Enterprise Model. Rather than extracting rules from experts, we are `engineering ontologies.' An ontology is a formal description of entities and their properties, relationships, constraints, behaviours. Through interaction with our industrial partners, we encounter problems that arise in their particular enterprises. Our approach to engineering ontologies begins with using these problems to de ne an ontology's requirements in the form of questions that an ontology must be able to answer. We call this the competency of the ontology. The second step is to de ne the terminology of the ontology its objects, attributes, and relations. In this way the ontology provides the language that will be used to express the de nitions in the terminology and the constraints required by the application. The third step is to specify the de nitions and constraints on the terminology, where possible. The speci cations are represented in First Order Logic and implemented in Prolog. Lastly, we test the competency of the ontology by proving completeness theorems with respect to the competency questions. Our initial e orts have focused on ontologies to support reasoning in industrial environments. The tasks that we have targeted to support are in `supply chain management' which extends MRP (Manufacturing Requirements Planning) to include logistics/distribution [Fox

The Role of Competency Questions in Enterprise Engineering

Abstract: We present a logical framework for representing activities, states, time, and cost in an enterprise integration architecture. We define ontologies for these concepts in first-order logic and consider the problems of temporal projection and reasoning about the occurrence of actions. We characterize the ontology with the use of competency questions. The ontology must contain a necessary and sufficient set of axioms to represent and solve these questions. These questions not only characterize existing ontologies for enterprise engineering, but also drive the development of new ontologies that are required to solve the competency questions.

The Great Transition: Using the Seven Disciplines of Enterprise Engineering to Align People, Technology, and Strategy

Abstract: This guide explains how to combine the forces of information technology, culture and strategies, to create an enterprise which constantly evolves, adapts to fast-changing demands, and continually learns at all levels. The book also: explains how to integrated the three critical aspects of an organization - culture, strategy and technology - into an "intimate partnership; and presents the author's approach - "enterprise engineering" - a sophisticated provess for creating a unique "family" of change-methods tailored to meet each company's needs. Using the enterprise engineering approach, readers learn how to: comprehend the enormous power of information technology, which is both creating this new dimension and enabling companies to make the trasition; and to understand and distinguish all the major change methods, such as TQM, radical reinvention of business process, enterprise redesign and strategic visioning. James Martin is the author of "The Wired Society" for which he won a the Pulitzer Prize nomination.

Information Integration for Concurrent Engineering (IICE) Compendium of Methods Report

Abstract: : For all the rapid advances in computer hardware and specific software technology, enterprise engineering, reengineering, and enterprise integration efforts continue to lack effective, widely understood methods for engineering large-scale information systems. Diverse methods are needed to engineer systems that exhibit desirable life-cycle characteristics (e.g., flexibility, responsiveness, scalability, maintainability, ease of use, integration, performance) and for engaging teams of people in critical life-cycle system development activities. Integration Definition (IDEF) methods, a key product of the IICE program, provide easy-to-use techniques and standard languages of communication that promote good engineering discipline. This report summarizes new IDEF developments toward establishing reliable methods for business constraint discovery (IDEF9), design rationale capture (IDEF6), human system interaction design (IDEF8), and network design (IDEF14). For each method, the conceptual foundations, relevance, issues, and recommended follow-on development activities are discussed.

Net change management for object-oriented modeling

Abstract: The invention facilitates modeling of an enterprise. A model developer uses a high-level modeling language to describe the enterprise with constructs that are more readily accessible to the model developer than those used in other previous modeling languages. The high-level description is translated into a low-level description that can more readily be used by a processing device to dynamically exercise the model. The constructs of the modeling language shield the model developer from many of the mundane tasks associated with maintaining data integrity in complex data structures. Of particular importance, the modeling language includes data constructs that make it easy to track and maintain data that changes during execution of a program, without considerable effort on the part of the model developer. These data constructs can be used to restore various states of the modeled enterprise during execution of the program, either automatically or at the direction of a user. The invention is particularly useful for modeling a complex enterprise, the operation of which is characterized by a large body of information. The invention can be used, for example, to develop a scheduling system for scheduling a complex activity and revising the schedule as necessary to accommodate changed circumstances. However, the invention is broadly applicable to modeling of any enterprise.

Industry Requirements and Associated Research Issues in the Extended Enterprise

Abstract: In this paper, we consider the difficulties faced by manufacturing companies and their response in terms of the emergence of the Extended Enterprise. We argue that the Extended Enterprise represents the context within which manufacturing systems research must be conducted and we identify what we consider to be the key topics for future manufacturing systems research and development.

Re-engineering the Enterprise

Abstract: The definition of tasks and functions as well as their relationships is one of the main tasks of organising an enterprise. Usually, this is done step by step. This means the complexity of an enterprise's overall task is broken down. The resulting subtasks must be assigned to individual task performers. Only if the task is adequately broken down, task performers will be able to execute it properly. Starting from present-day requirements, this paper explains fundamental organisational patterns to reduce the complexity in enterprises. As point of departure these patterns are used to derive the conception of planning centres. Afterwards, the way down to planning centres-i.e. the enterprise's re-engineering-is lined out and experiences gained in an industrial project are explained.

Systems engineering for better engineering

Abstract: The complexities of today's products and the techniques needed to make them have made systems engineering methods essential to effective competition. The author discusses the rise of Japanese industry and how it overtook the West by using a systems engineering approach. In systems engineering. an uncoordinated, piecemeal enterprise is replaced by a coordinated approach taking a total view of the common system purpose, so that the separate elements are subsumed in the identity of the whole system with its overall measures of performance. The ability of the Japanese to make products of high quality, low cost and strong consumer appeal is based on the application of many methodologies and technologies within a systems engineering approach. The whole activity is supported by the relentless use of kaizen-continuous improvement against benchmark measures of performance. The author discusses some of these processes and looks at the concepts of the business as a system and the product as a system.

The Scsi Bus and Ide Interface: Protocols, Applications and Programming

Abstract: From the Publisher: As the pace of change in business and technology continues to quicken, the business systems that are key to the enterprise's ability to adapt and prosper must also change rapidly. The expansion of enterprise computing into the world of the Internet makes the task of developing, deploying, and maintaining today's information systems even more challenging. With its modular approach to programming and capacity to manage complexity, object technology holds the key to success for enterprise computing to meet these challenges. Enterprise Computing with Objects helps the reader place rapidly evolving technologies-the Internet, the World Wide Web, distributed computing, object technology and client/server systems-in their appropriate context in relation to modern information systems. The authors distinguish what is essential from what is incidental, while imparting a clear understanding of how the underlying technologies fit together. The book examines essential topics, including data persistence, security, performance, scalability, and development tools. Even readers with existing experience in object technology or client/server programming can benefit from the perspectives offered here. With this book as an aid, designers and developers can better transition their information systems into the twenty-first century.

A Theory of Complex Actions for Enterprise Modelling

Abstract: Enterprise modelling is an essential component in defining an enterprise, such as a manufacturing facility, an end-item distribution company, a financial institution, or a university department. The goal of our enterprise modelling research is to create generic representations of enterprise knowledge that can be reused across a variety of enterprises. Towards this end, we have been developing the TOVE (TOronto Virtual Enterprise) ontology [Fox and Griininger 94]. TOVE provides a rich and precise representation of generic knowledge, such as activities, resources, time, and of more enterprise oriented knowledge such as cost, quality, products, and organization structure. In this paper, we present enterprise modelling as a new area of application for theoretical work in reasoning about action. We give an overview of the problems encountered in enterprise modelling and the requirements that they impose on any theory of action. We outline our approach to these problems using an extension to the situation calculus.

Accounting and the Enterprise: A Social Analysis

Abstract: Written from a sociological perspective, Accounting and the Enterprise explains how the study of accounting is an important element in understanding the way in which modern enterprises and societies operate.

A systems theory based approach to systems engineering of computer based systems and its consequences

Abstract: This paper argues that, like for any engineering discipline, experience and heuristics of Engineering of Computer Based Systems need to be grounded in a practical theory. On top of such a theory, a systems engineering approach has to be defined that allows the professional practice of the discipline and the safeguarding of the entire life cycle of all its artifacts. Such a systematization of a discipline inevitably leads to guidelines and reference standards. Those reference standards reflect the systems engineering approach and regulate the engineering process. The different classes those reference standards fall into are discussed, the nature of the underlying theories is elaborated on, and the consequences for the contents of the reference standards are sketched.

An enterprise modeling approach to organizational decision support

Abstract: A novel and comprehensive framework is outlined at a mostly conceptual level for future enterprise modeling systems. We discuss some major design issues and indicate the direction future research could take to support enterprise wide problem formulation and problem solving. The focus of the paper is chiefly on investigating the question of how to better do model building, and how to extract the relevant parts of the model to support specific analyses of corporate issues in an enterprise wide environment. Conceptually, we are looking for an enterprise modeling system (EMS) which automatically builds and executes task specific models as needed in response to queries posed by the user. EMS is especially aimed at supporting strategic decision making such as predicting the effects of changes in business policies, analyzing possible reactions to internal and external threats, and exploring new business opportunities. >

A Software Engineering Paradigm as a basis for Enterprise Integration in (Multi-) Client/Server Environments

Abstract: The ability to build and execute enterprise models including data, service and process models is a topic of growing importance for industry. It addresses the problem to develop reasonable models of the enterprise but has to cope also broadly with implementation and execution issues in heterogeneous environments. With respect to implementation and execution, client/server architectures, request broker mechanisms and distributed data and applications are emerging as the future state-of-the-art. In this context, the existing heterogeneity of technological frameworks as well as coping with legacy systems is a crucial fact. Existing methodologies and tools are not overwhelming these problems. They often do not integrate aspects of enterprise- or process-modelling, CASE (Computer Aided Software Engineering), workflow management and client/server execution. As a consequence, new kinds of architectures are needed. This paper outlines an approach, developed at FAW for the described scenario. The main objective of this solution is to cope with heterogeneity by a neutralizing approach instead of standardization The described software engineering paradigm supports a model-oriented development of distributed data, services and processes in a uniform way towards a neutralizing execution environment. The FAW software engineering paradigm complies with the specifications of CIMOSA and accomplishes the requirements of the CORBA architecture.

Systems engineering of computer based systems: status and future perspectives

Abstract: There are many ways in which we can describe systems engineering. It can be described according to structure, function, and purpose. It may be described in terms of efforts needed at the level of systems management, systems methodology, and systems engineering methods and tools. We can speak of systems engineering organizations in terms of their organizational management facets, in terms of their business processes or product lines, or in terms of their products or service. We can speak of systems engineering in terms of the knowledge principles, knowledge practices, and knowledge perspectives necessary for present and future success in systems engineering. This paper takes a multifaceted view of systems engineering. It attempts to describe systems engineering in terms of this relatively large number of trilogies. The process view of systems engineering is expanded on in some detail. Within this, a large number of necessary roles for systems engineering are described. We present a brief discussion of systems engineering from the perspective of each of these necessary roles as it applies to the systems engineering of computer based systems, including some 21st century projections.

A Systems Engineering Approach for Computer Based Systems Outline and First Results of a Program

Abstract: This paper argues for the necessity of an engineering discipline for computer based systems and outlines its beginnings. It is based on results obtained and directions mapped out for such a discipline by the IEEE Technical Committee on Engineering of Computer Based Systems (ECBS). Computer Based Systems are seen as the technical artifacts of a dedicated engineering discipline. Experience and heuristics of such a discipline need to be grounded in a practical theory. On top of such a theory, a systems engineering approach has to be defined that allows the professional practice of the discipline and the safeguarding of the entire life cycle of all its artifacts. Such a systematization of a discipline inevitably leads to guidelines and to reference standards. Those reference standards reflect the systems engineering approach and regulate the engineering process. The different classes those reference standards fall into are discussed and some consequences are proposed.

Systems engineering: A problem of perception

Abstract: The characterization of systems engineering as a discipline, process, procedure or a set of heuristics will have an impact on the implementation strategy, the training methodology, and operational environment. The systems engineering upgrade activities in the New Mexico Weapons Development Center and a search of systems engineering related information provides evidence of a degree of ambiguity in this characterization of systems engineering. A case is made in this article for systems engineering being the engineering discipline applied to the science of complexity. Implications of this characterization and some generic issues are delineated with the goal of providing an enterprise with a starting point for developing its business environment.

An agent-based distributed multimedia service environment

Abstract: This paper describes our experiences in using agent-based technology for the design of distributed multimedia service environments. These new systems must be able to operate in a constantly evolving enterprise and to adapt to unexpected contingencies or failures in hardware, software and even human resources. Our Multi-Agent-Architecture for Networked Applications (MANA) is based on the notion of an organizational network of agents that cooperate to provide services to internal and external customers of the enterprise. Key to the approach is the decoupling of service definition and provisioning through a declarative model of the enterprise.

System Engineering Deployment

Abstract: INTRODUCTION Where Are We Going? System Defined Systems Beget Systems Creative vs. Canned Responses The Current Plateau New vs. Modified The Book THE HUMAN FOUNDATION FOR SYSTEM ENGINEERING The Expanding Knowledge Base and its Effects Knowledge Dimensions Knowledge Bond Knowledge and its Exchange Individual vs. Group Work Communication Facilitation and Facilitization The Enterprise Knowledge Base ENTERPRISE KNOWLEDGE REQUIREMENTS AND THE FUNCTIONAL ORGANIZATION The Knowledge Transform Generic Knowledge Needs Product Line Base The Customer Base Organizing Possibilities Program Implementation through Teams Building Modes ENTERPRISE GENERIC PROCESS DEFINITION AND FUNCTIONAL ALLOCATION The Ultimate Enterprise Functionality First-Tier Functionality Expansion The Marriage of Enterprise and System Functionality Functionality Allocation Lower-Tier Development Functionality Formal Allocation of Functionality to the Functional Department Structure FUNCTIONAL ORGANIZATION CHARTERS AND RELATIONS Functional Department Formation First-Tier Functional Departments Expansion of the Functional Organizational Hierarchy and Charter Development The Popular Knowledge Map Program Knowledge Interfaces Process Integration GENERIC PRACTICES DOCUMENTATION Enterprise Generic Documentation Tree Practices Documentation Content and Responsibility System Engineering Manual External Standards Mapping The Discipline for Process Compliance Practices Deployment to Programs Process Quality Assurance on Programs Functional Metrics Process Improvement ORGANIZATIONAL STRUCTURE FOR WORK Overview The Two Axes Team Structures Team Formation and Staffing on Programs IPT Work PIT Activity The PIT-IPT Team Matrix PROGRAM COMMUNICATIONS Communication Dichotomy The Critical Nature of Communications A Common Database War Room Or Wall Virtual Teams in Your Future PRODUCT SYSTEM DEFINITION System Development Process Overview System Requirements Analysis Architecture Syntheses A General Theory of Structured Analysis INTERFACE DEVELOPMENT IN A NEW WORLD Interface Fundamentals Interface Depiction Terminal Responsibility Interface Documentation Traditional Management of Interface Development Management of Interfaces Within the Context of Ownership Dynamics International Effects Summary GENERIC PROGRAM PROCESS DEVELOPMENT Aggregate Planning Goals General Planning Data Structure Program Planning Structure Making the Transform Between Generic and Program Models PROGRAM WORK DEFINITION AND INTEGRATION USING THE USAF INTEGRATED MANAGEMENT SYSTEM The Ultimate Requirement and Program Beginnings Program Plan Tree Know Thyself Though Generic Program Planning Data Integrated Management System Overview Generating the Six Primary Documents Work Responsibility Who Plans the Program? A Generic SEM/SEMP for You Rapid Identity Documentation PROGRAM WORK DEFINITION AND INTEGRATION USING THE JOG SYSTEM ENGINEERING METHOD Goals Again Functional Structures Program Structures Mapping Generic Identity to Program Structures Functional Department Mapping The Apparent Disappearance of the SOW Integration of Inputs into the IMP Integrated Master Schedule (IMS) TASK COST AND SCHEDULE ESTIMATING The Three Principal Program Planning Parameters Task Data Sheets Estimate Improvement How-To Knowledge Access Knowledge Depth Differences Sources How-To Knowledge Dictionary SYSTEM ENGINEERING TRAINING PROGRAM DEVELOPMENT Training Program Overview Process Evaluation and Training Prioritization The Low-Cost Lunch-Time Seminar Local University Cooperation Purchase of A Tailored Commercial Certificate Program A System Engineering Help Window SYSTEM ENGINEERING ASSESSMENT AND IMPROVEMENT Is A Static Identity Adequate? Procedures Media Lessons Learned and Continuous Improvement Performance Measurement Systems Formal Post Mortem Two-Dimensional Process Audit External Maturity Models MOTIVATION OF THE SYSTEMS APPROACH The Logic is Not Accepted Everywhere The Causes of Poor System Engineering Performance on Programs Changing Manager Attitudes Customer Demand for Improvement Moving the Top Person's Attitude The Workers Need for Motivation Closing Appendix A, Enterprise Process Definition Appendix B, Enterprise Organizational Structure Appendix C, Enterprise System Engineering Practices Manual Index

Managing the dynamic environment

Abstract: We all live in a complex and dynamic world. The last 20 years have seen, particularly in Europe and North America, the relentless shift from manufacturing-based to knowledge-based industries. I propose that enterprise modelling provides some support for managing knowledge and information, but not enterprise modelling as people might already know it. I propose a holistic approach: understanding the whole and the interdependencies of all the component parts. The emphasis is less on information engineering and more on information management, ensuring that information is shared, reused and easily accessible. There are already many simple software tools available which help people understand and communicate the complexity of their environments. I maintain that systems thinking and a more scientific approach to management can and should contribute to an enterprise model. (3 pages)

A practical application of object-oriented enterprise modeling

Abstract: As the Air Force and Navy look forward to replacing outdated resources, it became apparent that a better understanding of and an accurate analytic model for, the existing process of training pilots and navigators was essential Object oriented analysis (OOA) was selected to make use of the perceived advantages it offers such as data modeling, encapsulation of objects and their behavior, the potential for reuse, and its ability to scale-up to huge systems The goal of the analysis was to create a set of OOA models that describes: (1) the implementation of the current (physical) enterprise; (2) the essential (logical) enterprise requirements of a combined Air Force and Navy integrated training management system; and (3) the essential (logical) enterprise requirements of an enhanced combined Air Force and Navy integrated training management system The enterprise models will be used as a springboard for the development of requirement specifications for a training integration management system (TMS) TMS will be an automated system that manages all undergraduate flying/aviation training It will support the Ground Based Training System We present the steps taken in the analysis and modeling process for the creation of these enterprise models including: (1) object-oriented methodology, CASE tool and database selection; (2) user-driven paradigm mix and migration, (3) data collection process; (4) classification and development of class/object views: 5) development of information (functional) flow views; (6) development of dynamic (time dependent views; (7) user validation of current enterprise views; (8) future system enhancements and improvements; and (9) lessons learned

Managing the New Enterprise: The Proof, Not the Hype

Abstract: From the Publisher: Transitioning to a distributed client/server environment involves more than mastering a new paradigm. This practical companion to the best-selling Rightsizing the New Enterprise: The Proof, Not the Hype describes in detail the key technology support infrastructures, including networking, data centers, and system administration that are critical to building and managing the New Enterprise. What is the New Enterprise? It's what businesses or corporations must do to survive in the 1990s. Businesses are changing and IT (Information Technology) must change to meet the new business requirements. Global competition is becoming more intense; profit margins are falling. To remain competitive, the New Enterprise must diversify and focus on products and services that provide a competitive advantage, all the while reducing costs. The goal is to "rightsize" the enterprise; to get the right information to the right people to support business requirements in the '90s. This book not only provides the proof that it can be done, it tells you exactly how to do it.

Narrowing the gap of SME for IT innovation with enterprise architectures

Abstract: Contemporary changes in market structures demands adequate response from Small and Medium sized Enterprises (SME). The rapid evolution of information-technology offers new challenges and exiting new opportunities for innovation. The approach presented in this paper will take the information system architectures of the enterprise as a starting point. It will be extended middle-out to a meta-level dealing with methodology issues and to a project level dealing with involved people, activities and results.