scispace - formally typeset
Search or ask a question

Showing papers on "Enterprise systems engineering published in 1993"


Book
20 May 1993
TL;DR: Reading is a hobby to open the knowledge windows and by this way, concomitant with the technology development, many companies serve the e-book or book in soft file.
Abstract: Reading is a hobby to open the knowledge windows. Besides, it can provide the inspiration and spirit to face this life. By this way, concomitant with the technology development, many companies serve the e-book or book in soft file. The system of this book of course will be much easier. No worry to forget bringing the engineering of knowledge based systems book. You can open the device and get the book by on-line.

126 citations


Journal ArticleDOI
TL;DR: The idea of the extended enterprise offers a unifying idea to explain and justify the application of such technologies as electronic data interchange, engineering data management and knowledge–based systems.
Abstract: The Extended Manufacturing Enterprise represents, as a way of combining manufacturing operations, a distinct alternative both to pure markets and to pure command structures It retains the competitive disciplines and efficient allocation of the market, and adds to this the strategic control of direction characteristic of command structures The Extended Enterprise is characterized by the information channels built between those participating in its activities By sharing knowledge a supplier and a customer can much more readily adapt to changing needs and circumstances: not only do they pool their technical and commercial know–how, but they can act in a co–ordinated manner when, for instance, new products are introduced They can also dispose of many of the costly forms of insurance otherwise needed to cope with uncertainty – intermediate inventories and inspections, for example The idea of the extended enterprise offers a unifying idea to explain and justify the application of such technologies as electronic data interchange, engineering data management and knowledge–based systems

53 citations


Journal ArticleDOI
TL;DR: In this article, the authors present a SWOT analysis of the enterprise's total learning, its contribution to the achievement of enterprise growth, and the role of programmed knowledge in action learning.
Abstract: Posits that every enterprise must institutionalize its workplace learning systems and opportunities in such a way that it radiates what it has already achieved and from this moves on to realize its full potential – in short, the enterprise itself is the key. Examines in successive chapters: the individual manager and questioning insights (Q); the major systems which the enterprise uses to capture and structure its learning; a SWOT analysis of the enterprise′s total learning; action learning, its contribution to the achievement of enterprise growth, and the role of programmed knowledge (P); the Enterprise School of Management (ESM) as a phoenix of enlightenment and effectiveness rising from the ashes of traditional, less effective management training initiatives; and, finally, the practical realization of the action learning dream, as evidenced by emerging examples of successful and profitable implementation worldwide. Concludes with a selection of pertinent abstracts.

33 citations


Book ChapterDOI
17 Oct 1993
TL;DR: The author explores the following issues: Is there such a thing as a generic enterprise model?
Abstract: Computerization of enterprises continues unabated and so does the cost of software. The availability of a generic, common-sense enterprise model is necessary if the costs are to be reigned in. But in order to construct useful generic enterprise models (GEM) there are a number of issues that have to be addressed. In this paper the author explores the following issues: Is there such a thing as a generic enterprise model? Can the terminology be precisely defined? Does all knowledge need to be explicit? Need there be a single, shared enterprise model? How can we determine which is a better enterprise model? Can an enterprise model be consistent? Can an enterprise model be created and kept current? Will the organization accept an enterprise-wide model? The author then briefly describes the TOVE project, which attempts to address many of these issues. >

25 citations



01 Jan 1993
TL;DR: A framework for enterprise engineering that encompasses the formalization of knowledge in an enterprise, its integration into a software tool, and the visualization of the enterprise is presented.
Abstract: We present a framework for enterprise engineering that encompasses the formalization of knowledge in an enterprise, its integration into a software tool, and the visualization of the enterprise.

13 citations


Journal ArticleDOI
TL;DR: To maintain the historical part of this diachronic object base, DECmcc provides comprehensive facilities for collecting, processing, purging, archiving, and exporting historical attribute data.
Abstract: A family of integrated systems has been developed within Digital's enterprise management architecture (EMA). The product called DECmcc is part of a larger EMA implementation, which consists of both an enterprise management director and a framework for developing consistent and integrated management solutions with EMA. An object-based framework provides time-oriented dispatching of operations and serves as a foundation for modules supporting past, present, and future time views of managed objects. Fully integrated modules implement a conceptual diachronic object-base that allows time-oriented, object-based modeling of resources. To maintain the historical part of this diachronic object base, DECmcc provides comprehensive facilities for collecting, processing, purging, archiving, and exporting historical attribute data. The managed object instances, for the existing objects that need to be globally and directly accessible, are stored using DECdns, i.e., essentially DCE/CDS. The historical data are stored on the domain basis locally. Recorded historical data and 'live' enterprise data can be exported to a relational database in a uniform fashion for any combination of past time, current, and future data. >

12 citations



Proceedings ArticleDOI
05 Jan 1993
TL;DR: Extensions to Petri net theory that provide for tracking the genealogy and age of tokens, support for multiple token types, and the prioritizing and sharing of tokens are discussed, with their relationship to enterprise simulations.
Abstract: The authors discuss experiences of and research into applying Petri net graphs and object-oriented techniques in simulating and modeling enterprise processes. Petri nets have been used with great success in the modeling of concurrent and asynchronous tasks in programming and communications systems. Extending this approach to simulating enterprise processes has significant potential for increasing management's ability to understand and improve business processes. Extensions to Petri net theory that provide for tracking the genealogy and age of tokens, support for multiple token types, and the prioritizing and sharing of tokens are discussed, with their relationship to enterprise simulations. An object-oriented framework based, in part, on the work of J. Zachman (1987) is utilized in managing the complexity of the enterprise model. Automated tool support for the business design process is also discussed. >

11 citations


Book ChapterDOI
TL;DR: The Integrated Enterprise Modelling (IEM) concept will integrate different modelling views in one consistent manufacturing enterprise model and will provide a modelling base for construction of an enterprise model from a user's point of view.
Abstract: This paper discusses the planning process of CIM Systems and the support of this planning process by modelling. Today the modelling of an enterprise is enabled by various methods which are used for different purposes and views upon the enterprise. Using an object-oriented approach the Integrated Enterprise Modelling (IEM) concept will integrate different modelling views in one consistent manufacturing enterprise model and will provide a modelling base for construction of an enterprise model from a user's point of view. It will lead the user from a general CIM architecture given by predefined model structures to a particular model and architecture of the system support in his own manufacturing enterprise, which are the essential tasks towards an enterprise wide and integrative usage of information technology. Therefore the basic constructs like object class structure and a related process description method via generic activity model will be presented. The kernel and the main views of a manufacturing enterprise model will be derived. An example using the IEM concept for the specific view of CIM planning and introduction will clarify the main features of the concept.

10 citations


DOI
01 Jan 1993
TL;DR: This thesis presents four parallel algorithms that were developed using Enterprise: chaotic Gauss-Seidel, block matrix multiplication, transitive closure and alpha-beta search, which range from data-intensive to computationally intensive.
Abstract: Enterprise is the latest o ering in integrated programming environments for distributed parallel processing. Enterprise is intended for parallel programming on a network of workstations. The analogy of a business organization or enterprise is used to describe the various parallel constructs (line, department, division, individual, receptionist, representative, individual, and service) o ered. Each asset or stand-alone module intended for one processor is created from the user's familiar sequential code and the graph that describes the parallelism. Enterprise is designed to use standard C code. The appropriate low-level communication and synchronization code is inserted by Enterprise; changes to either resources or the type of parallelism desired are easily accommodated and involve little user involvement. This thesis presents four parallel algorithms that were developed using Enterprise: chaotic Gauss-Seidel, block matrix multiplication, transitive closure and alpha-beta search. The algorithms range from data-intensive (matrix multiplication) to computationally intensive (alpha-beta). Performance and ease of construction were two important metrics used in the evaluation. Performance was marred by the implementation of the communication server. Various experiments were done to isolate and identify the problem areas. Problems local to Enterprise are being addressed. The communication server problems were forwarded to ISIS (creators of the communication code) and may be addressed in the next release of ISIS. Several of the algorithms required user intervention to correct de ciencies in the current implementation of the Enterprise pre-compiler and run-time executive. Modi cations to the Enterprise model and its implementation have resulted from this thesis. The implementation is now more robust and the model has been extended and simpli ed. Acknowledgements I would like to acknowledge the patience and forbearance showed by Steve Sutphen and Carol Smith who put up with my many questions about the workings of the ethernet, UNIX kernels and other arcane topics that crept into this evaluation. Also they were invaluable for suggesting further tests to isolate the quirks of the ISIS and NMP software packages. I am grateful to authors of the executive, pre-compiler, and graphical interface, Pok Sze Wong, Enoch Chan, and Greg Lobe, who were always there when I was initially testing their products. Their quick and timely responses to either suggestions or questions about their work made my work proceed much faster than I anticipated. I would like to thank the patience and continued good nature of Karim Makahani and Caroline Morris who maintain the student computer laboratories where I ran most of my tests. Unfreezing machines that I managed to corrupt, coordinating use where it wouldn't interfere with course work, and providing scarce storage space are above and beyond what their duties are and I am grateful for their assistance. My thanks to Anthony Jones for suggesting the two slow converging problems for the Gauss-Seidel algorithm. Finally, to my wife Edith and my two children Matthew and Ellen: I thank you for allowing me the freedom and opportunity to go back to university.

Proceedings ArticleDOI
30 Aug 1993
TL;DR: Object-oriented notations supply an ideal foundation for describing the components because they support reuse by means of inheritance, and traditional techniques begin with 'a blank sheet of paper'.
Abstract: Architectural methods, such as information engineering, are the most comprehensive and intellectually rigorous means of information systems planning. Despite their many virtues though, there remain difficulties with both their theory and their practice. In particular, there are numerous problems associated with enterprise modeling which is at the heart of these methods. Current techniques are inflexible, cumbersome, and lack theoretical underpinning. But, most of all, they are laborious and time-consuming. One reason why enterprise modeling takes so long is that traditional techniques begin with 'a blank sheet of paper'. Instead it might be possible to use standardized components in order to compile a draft model. Since these components may be used again and again, they need a rigorous basis. Object-oriented notations supply an ideal foundation for describing the components because they support reuse by means of inheritance. >


Proceedings Article
02 Sep 1993

DOI
01 Jul 1993
TL;DR: In this paper, the authors present practical considerations in applying systems engineering in the development of complex systems that have natural conflicts with management processes, and conclude with some thoughts on a management philosophy that supports systems engineering.
Abstract: This paper presents practical considerations in applying systems engineering in the development of complex systems that have natural conflicts with management processes. Many efforts focus on the elements, program phases and tools of systems engineering, but generally do not address practical steps for applying systems engineering, while integrating the “human element” into the process. This paper addresses: a) the current environment, b) the distinction between systems engineering processes and elements of management, c) profiles of a good systems engineering manager vs. a good systems engineer, and d) the relationship of processes to organizational structure. The paper concludes with some thoughts on a management philosophy that supports systems engineering.

Proceedings ArticleDOI
04 May 1993
TL;DR: Methods of collecting plant-floor data, transmitting it by means of networks and developing an enterprise database are discussed, which are based on business planning and structured engineering techniques focused on developing a competitive advantage.
Abstract: A yarn manufacturing enterprise includes diverse components such as process machinery, materials handling equipment, computers, software, databases, communications networks, and people. Integrating all of these components is necessary for continuous improvement of operations and to develop a competitive advantage. The elements of a spinning enterprise and a methodology for integrating it are described. The methodology is based on business planning and structured engineering techniques focused on developing a competitive advantage. Methods of collecting plant-floor data, transmitting it by means of networks and developing an enterprise database are discussed. >

Proceedings ArticleDOI
05 Jan 1993
TL;DR: A modern paradigm of strategy development and an application of systematic analysis to the evolution of the enterprise model are introduced.
Abstract: The union of the tools and methods of scientific management and engineering disciplines is likely to be manifest in the emergence of the structured enterprise model. A definition of the systems method is suggested for both the engineer and the management scientist. A perspective on the realm of systems thinking is presented. A modern paradigm of strategy development and an application of systematic analysis to the evolution of the enterprise model are introduced. >

Book ChapterDOI
01 Jan 1993
TL;DR: The ability of the profession of systems design to meet the demands placed upon it is increasingly being questioned and executives and professionals find that computing and information technology (IT) either offers them nothing of personal relevance or creates new problems that outweigh the anticipated benefits.
Abstract: The ability of the profession of systems design to meet the demands placed upon it is increasingly being questioned. Cost over-runs and systems abandoned before completion are reported in the press almost everyday to the extent of being an academically verified phenomenon (e.g. Belotti, 1988; Stowell, 1991). in addition, the satisfaction of users with systems that do achieve completion is by no means universal, frequently executives and professionals find that computing and information technology (IT) either offers them nothing of personal relevance or creates new problems that outweigh the anticipated benefits (e.g. Zuboff, 1988; Mumford, 1983).

Journal ArticleDOI
TL;DR: In this paper, a model of a major "extraterrestrial enterprise" in cis-lunar space is presented, consisting of 10 individual companies and institutions, two of which are owned by a group of governments.

Dissertation
02 Jan 1993
TL;DR: Enterprise Modeling Framework (EMF) represents a significant advancement over existing enterprise modeling methodologies and has been demonstrated by modeling an apparel manufacturing enterprise.
Abstract: An enterprise model encompassing the function, information and dynamics facets of an enterprise is required for an enterprise to achieve quick response capability and flexibility. To handle the complexity and dynamic nature of the enterprise, the model should evolve continuously and be scalable. The modeling methodology should facilitate the creation of such models and the framework should also be easy to use. Enterprise Modeling Framework (EMF) consists of a methodology for modeling the three major facets of an enterprise, viz., function, information and dynamics, and software tools implementing the methodology. These facets of an enterprise have been broadly structured using the object-oriented paradigm into three EMF models, viz., the Activity Model, the Entity Model and the Knowledge Model. From the experience gained during modeling enterprises, a method for combining structured and object-oriented analysis methods has been adopted. A methodology has been developed for integrating constraints with the EMF Entity Model. Dynamics modeling has been integrated with function and information modeling by automatic generation of SIMAN code from the Activity and Entity Models. The hierarchical nature of the EMF Activity Model is used to generate simulation models at the desired level of detail. Based on the principal performance metrics for evaluating a modeling methodology, viz., learning time, model development time, workload on the user and completeness in terms of enterprise facets modeled, EMF represents a significant advancement over existing enterprise modeling methodologies. The merits of EMF have been demonstrated by modeling an apparel manufacturing enterprise.




DOI
01 Jul 1993
TL;DR: A strategy based on a hierarchy of systems engineering processes, with the systems approach at the top of the hierarchy is proposed, that will work for any industry and product unique considerations.
Abstract: In the commercial market sector, (non-DoD) systems engineering is usually not required by customers The decision to use it has to be based on what's good for business However, very little information is available on how to develop a strategy for employing systems engineering in the commercial market sector This paper proposes a strategy based on a hierarchy of systems engineering processes, with the systems approach at the top of the hierarchy The systems approach identifies; (1) the basic systems engineering activities and their purpose, (2) a standard system life cycle model that integrates the basic systems engineering activities over time, and (3) guidelines on tailoring the systems approach into a systems engineering process that will work for any industry and product unique considerations

01 Jan 1993
TL;DR: The structural problems to be solved in the large enterprise are examined and the viability of RPC as such an integration mechanism is commented on.
Abstract: There is a great deal of interest currently in how the large computing enterprise is to be integrated into a “seamless whole”. Organizations find themselves with a wide variety of hardware, operating systems, and networks in place to run their mission-critical applications. Remote Procedure Call (RPC) has received a great deal of attention as the candidate integration mechanism. Here we examine the structural problems to be solved in the large enterprise and comment on the viability of RPC as such an integration mechanism.

Book ChapterDOI
01 Jan 1993
TL;DR: The assumptions that each product is produced in the same technological way and at the same production centre can sometimes limit the applicability of input/output modelling as discussed by the authors, which is a limitation of our approach.
Abstract: Enterprise models discussed by Pichler (1961), Mueller-Mehrbach (1964), Teusch-Schluetter (1985), and Mesko (1986) depend on the characteristics of the production process and on the operative purposes but they represent only a specific form of the input/output modelling (Kloock, 1969). The assumptions that each product is produced in the same technological way and at the same production centre can sometimes limit the applicability of input/output modelling.