“An internal combustion engine is 'clearly' a system; we subscribe to this opinion because we know that the engine was designed precisely to be a system. It is, however, possible to envisage that someone (a Martian perhaps) totally devoid of engineering knowledge might at first regard the engine as a random collection of objects. If this someone is to draw the conclusion that the collection is coherent, forming a system, it will be necessary to begin by inspecting the relationships of the entities comprising the collection to each other. In declaring that a collection ought to be called a system, that is to say, we acknowledge relatedness. But everything is related to everything else. The philosopher Hegel enunciated a proposition called the Axiom of Internal Relations. This states that the relations by which terms are related are an integral part of the terms they relate. So the notion we have of any thing is enriched by the general connotation of the term which names it; and this connotation describes the relationship of the thing to other things… [There are three stages in the recognition of a system]… we acknowledge particular relationships which are obtrusive: this turns a mere collection into something that may be called an assemblage. Secondly, we detect a pattern in the set of relationships concerned: this turns an assemblage into a systematically arranged assemblage. Thirdly, we perceive a purpose served by this arrangement: and there is a system.”

—  Anthony Stafford Beer

Source: Decision and control: the meaning of operational research and management cybernetics, 1966, p. 242.

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 "An internal combustion engine is 'clearly' a system; we subscribe to this opinion because we know that the engine was d…" by Anthony Stafford Beer?
Anthony Stafford Beer photo
Anthony Stafford Beer 23
British theorist, consultant, and professor 1926–2002

Related quotes

“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

“Models are used essentially for evaluation and prediction purposes as well as for the analysis and study of the different parts of the system so that the systems engineer or designer may arrive at sound engineering decisions regarding the system design.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), p. 113; As cited in: Alberto Ortiz (1992, p. 12-13)

A. Wayne Wymore photo

“In the minds of many writers systems engineering is synonomous with component selection and interface design; that is, the systems engineer does not design hardware but decides what types of existing hardware shall be coupled and how they shall be coupled. Complete agreement that this function is the essence of systems engineering will not be found here, for, besides the very important function of systems engineering in systems analysis, there is the role played by systems engineering in providing boundary conditions for hardware design.”

A. Wayne Wymore (1927–2011) American mathematician

Source: A Mathematical Theory of Systems Engineering (1967), p. 193.

“A. D. Hall's (1962) classic account of the methodology was based on his experience with the Bell Telephone Laboratories. Hall sees systems as existing in hierarchies. In systems engineering, plans to achieve a general objective must similarly be arranged in a hierarchy, with the systems engineer ensuring the internal consistency and integration of the plans, The methodology itself ensures the optimization of the system of concern with respect to its objectives. This requires a number of steps, the most important being problem definition, choosing objectives, systems synthesis, systems analysis, systems selection, system development, and current engineering. With Hall, the system of concern is usually a physical entity.”

Mike Jackson (1951) systems scientist

Michael C. Jackson (1992) Systems Methodology for the Management Sciences. p. 74; About A.D. Hall (1962)

“Within the past ten years there have appeared with increasing frequency books, articles, conferences, and monograms dealing with system engineering, system analysis, system design, the systems approach, the design of systems, system theory, and problems of systems engineering. The number of publications and the stature of their authors does not allow the dismissal of the subject as a passing fad. The breadth of engineering activity involved in even a cursory examination of recent publications is of interest… It is therefore obvious that whatever Systems Engineering may or may not be, it is non-sectarian and encompasses activities that are of concern in all phases of engineering. On the other hand undergraduate college offerings akin to Systems Engineering are rather limited and even graduate programs are not extensive.”

Allen B. Rosenstein (1920–2018) American systems engineers

Source: Systems engineering and Modern Engineering Design (1965), p. 1.

A. Wayne Wymore photo

“[In the year 1957] I have just returned from an exciting meeting of the American Society for Engineering Education where I heard a paper on the new discipline of systems engineering. It is no longer sufficient for engineers merely to design boxes such as computers with the expectation that they would become components of larger, more complex systems. That is wasteful because frequently the box component is a bad fit in the system and has to be redesigned or worse, can lead to system failure. We must learn how to design large-scale, complex systems from the top down so that the specification for each component is derivable from the requirements for the overall system. We must also take a much larger view of systems. We must design the man-machine interfaces and even the system-society interfaces. Systems engineers must be trained for the design of large-scale, complex, man-machine-social systems.”

A. Wayne Wymore (1927–2011) American mathematician

Systems Movement: Autobiographical Retrospectives (2004)

“Enterprise engineering is an emerging discipline that studies enterprises from an engineering perspective. The first paradigm of this discipline is that enterprises are purposefully designed and implemented systems. Consequently, they can be re-designed and re-implemented if there is a need for change. The second paradigm of enterprise engineering is that enterprises are social systems. This means that the system elements are social individuals, and that the essence of an enterprise's operation lies in the entering into and complying with commitments between these social individuals.”

Erik Proper (1967) Dutch computer scientist

Preface.
Advances in Enterprise Engineering II (2009)

“A new concept and a new method were needed. The concept from the engineering standpoint is the evolution of the engineering scientist, i. e., the scientific generalist who maintains a broad outlook. The method is that of the team approach. On large-scale-system problems, teams of scientists and engineers, generalists as well as specialists, exert their joint efforts to find a solution and physically realize it.
We are led to the concept of the system-design team, a small group of engineers or scientists, to lead a large project and organize the system effort. Such men have been variously called engineering scientists, system engineers, system analysts, or large-scale-system designers. The technique has been variously called the systems approach or the team development method. It is toward this man and his teammates that these discussions are directed. With the realization that not enough can be learned in all the required fields to make him a specialist, enough is introduced to make him aware of the language and problems of the specialist. This generalist is a new quantity in the engineering world, and his education must be begun.”

Robert E. Machol (1917–1998) American systems engineer

Source: System Engineering (1957), p. 8

Maurice Wilkes photo

“In the judgment of design engineers, the ordinary means of communicating with a computer are entirely inadequate. […] Graphical communication in some form or other is of vital importance in engineering as that subject is now conducted; we must either provide the capability in our computer systems, or take on the impossible task of training up a future race of engineers conditioned to think in a different way.”

Maurice Wilkes (1913–2010) British computer scientist

Sect. 4: Design and Assembly
"Computers Then and Now" (1968)

Qian Xuesen photo

“The purpose of "Engineering Cybernetics" is then to study those parts of the broad science of cybernetics which have direct engineering applications in designing controlled or guided systems. It certainly includes such topics usually treated in books on servomechanisms. But a wider range of topics is only one difference between engineering cybernetics and servomechanisms engineering. A deeper - and thus more important - difference lies in the fact that engineering cybernetics is an engineering science, while servomechanisms engineering is an engineering practice.”

Qian Xuesen (1911–2009) Chinese rocket scientist

Source: Engineering cybernetics, (1954), p. vii

Related topics