“Considering enterprises as "open socio-technical systems" helps to provide a more realistic picture of how they are both influenced by and able to act back on their environment. It points in particular to the various ways in which enterprises are enabled by their structural and functional characteristics (“system constants”) to cope with the “lacks” and “gluts” in their available environment.”

—  Eric Trist

Source: Organizational choice, (1963), p. 6

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Considering enterprises as "open socio-technical systems" helps to provide a more realistic picture of how they are bot…" by Eric Trist?
Eric Trist photo
Eric Trist 29
British scientist 1909–1993

Related quotes

“From the physical point of view the characteristic state of the living organism is that of an open system. A system is closed if no material enters or leaves it; it is open if there is import and export and, therefore, change of the components. Living systems are open systems, maintaining themselves in exchange of materials with environment, and in continuous building up and breaking down of their components.”

Ludwig von Bertalanffy (1901–1972) austrian biologist and philosopher

Von Bertalanffy (1950) " The Theory of Open Systems in Physics and Biology http://vhpark.hyperbody.nl/images/a/aa/Bertalanffy-The_Theory_of_Open_Systems_in_Physics_and_Biology.pdf" In: Science, January 13, 1950, Vol. 111. p. 23
1950s

“A framework as it applies to enterprises is simply a logical structure for classifying and organising the descriptive representations of an enterprise that are significant to the management of the enterprise as well as to the development of the enterprise's system [with the aim of] rationalising the carious concepts and specifications in order to provide for clarity of professional communication, to allow for improving and integrating development methodologies and tools, and to establish credibility and confidence in the investment of systems resources.”

John Zachman (1934) American computer scientist

Zachman cited in: Egon Berghout and Dan Remenyi, Egon Berghout (2003) Proceedings of the 10th European Conference on Information Technology Evaluation - 2003. p. 503
In this quote the "framework" refers to the Zachman Framework

“From a pessimistic viewpoint, it can be stated that there is no good general way of structuring a system. However, from an optimistic point of view one can say that a number of good ways of structuring systems exist and that some are better than others for any particular system. In this and the following sections, there will be a presentation of a number of structuring approaches that have merit and have been employed successfully, including functional structuring, equipment structuring, and use of various coordinate systems.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), Systems Engineering Methods (1967), p. 107

“Various perspectives exist in an enterprise, such as efficiency, quality, and cost. Any system for enterprise engineering must be capable of representing and managing these different perspectives in a well-defined way.”

Mark S. Fox (1952) Canadian computer scientist and Professor of Industrial Engineering

Michael Grüninger and Mark S. Fox (1995) " The role of competency questions in enterprise engineering http://www.eil.utoronto.ca/enterprise-modelling/papers/benchIFIP94.pdf." Benchmarking—Theory and Practice. Springer US, 1995. 22-31.

Russell L. Ackoff photo

“Analysis of a system reveals its structure and how it works. It provides the knowledge required to make it work efficiently and to repair it when it stops working. Its product is know-how, knowledge, not understanding. To enable a system to perform effectively we must understand it—we must be able to explain its behavior—and this requires being aware of its functions in the larger systems of which it is a part.”

Russell L. Ackoff (1919–2009) Scientist

Source: 1990s, Re-Creating the Corporation (1999), p. 12.

“The scientist has to have a way of thinking about the environment of a system that is richer and more subtle than a mere looking at for boundaries. He does this by noting that, when we say that something lies ‘outside’ the system, we mean that system can do relatively little about its characteristics or its behavior. Environment, in effect, makes up the things and people that are ‘fixed’ or ‘given’, from the system’s point of view.”

C. West Churchman (1913–2004) American philosopher and systems scientist

Source: 1960s - 1970s, The Systems Approach (1968), p. 35

“There are several world view assumptions present in enterprise engineering. The first assumption is that the enterprise can be viewed as a complex system. This is necessary because systems in organizations are systems of organized complexity. Complexity is the result of the multiplicity and intricacy of man’s interaction with other components of the system. Secondly, the enterprise is to be viewed as a system of processes. These processes are engineered both individually and holistically. The final assumption is the use of engineering rigor in transforming the enterprise. The enterprise engineering paradigm views the enterprise as a complex system of processes that can be engineered to accomplish specific organizational objectives. In the Enterprise Engineering paradigm, the enterprise is viewed as a complex system of processes that can be engineered to accomplish specific organizational objectives.”

Donald H. Liles (1947) American engineer

Source: Enterprise modeling within an enterprise engineering framework (1996), p. 993

“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 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.”

Mark S. Fox (1952) Canadian computer scientist and Professor of Industrial Engineering

Source: Methodology for the Design and Evaluation of Ontologies (1995), p. 1: Introduction

“# Macrosocial systems. These include systems in communities and industrial sectors, and institutions operating at the overall level of a society. They constitute what I have called "domains". (Trist, 1976a; 1979a). One may regard media as socio-technical systems. McLuhan (1964) has shown that the technical character of different media has far-reaching effects on users. The same applies to architectural forms and the infrastructure of the built environment. Although these are not organizations, they are socio-technical phenomena. They are media in Heider's (1942) as well as McLuhan's sense.”

Eric Trist (1909–1993) British scientist

Source: The evolution of socio-technical systems, (1981), p. 11

“Simulation is the use of models and/or the actual conditions of either the thing being modeled or the environment in which it operates, with the models or conditions in physical, mathematical, or some other form. The purpose of simulation is to explore the various results which might be obtained from the real system by subjecting the model to representative environments which are equivalent to, or in some way representative of, the situations it is desired to understand or investigate. Simulation may involve system hardware and the actual physical environment, or it may involve mathematical models subjected to mathematical forcing or disturbance functions representative of the systems conditions to be studied.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), p. 111 as cited in

Related topics