systems-engineers

"The general public still doesn’t see engineers in the way it does doctors or lawyers. You see doctors and lawyers portrayed on television and in fiction, but engineering only has visibility in documentary formats, so Inwed has an important role to promote the profession.”"

"Engineering is harder to get into as a girl. Schools will generally funnel girls towards law or medicine"

"Teachers and parents don’t see engineers in society. Most people who become engineers already have a family member in the industry"

"It is important to remember that still only 16% of the engineering workforce are women but in society, women make up 51% of the population"

"I needed a third module to complete my degree and chose systems engineering, thinking that it was about computer systems,” she says. It was definitely not what she was expecting but in a good way and it moved her career firmly into the engineering sector. It is clear she now thrives on the opportunities engineering offers."

"Well, Benny, now that we know the thing can fly, all we have to do is improve its range a bit."

"Obama can't announce that man-in-space is out of date because of the political consequences... Senators and congressmen from Florida, Texas and Alabama (centers of space-program jobs) would give him so much trouble he can't cancel it."

"In April 1946, when I came to Hughes Aircraft to institute high-technology research and development, it was far from the place it was to become. Howard Hughes, I was informed, rarely came around. When he did show up, it was to take up one or another trivial issue. He would toss off detailed directions, for instance, on what to do next about a few old airplanes decaying out in the yard or what kind of seat covers to buy for the company-owned Chevrolets, or he would say he wanted some pictures of clouds taken from an airplane. An accountant from Hughes Tool Co. ((started by Howard's father)) had the title of general manager but was there only to sign checks. A few of Howard's flying buddies were on the payroll, using assorted fanciful titles like some in Gilbert and Sullivan's Mikado, but apparently did next to nothing. A lawyer was on hand to process contracts, but there were practically none. In addition to the Spruce Goose flying freighter, a mammoth eight-engine plywood seaplane that barely managed to fly even once, there was an experimental Navy reconnaissance plane under development (which, with Hughes at the controls, later crashed, almost killing him). The contracts for both planes had been canceled. Perhaps, I said to myself, this is one of those unforeseeable lucky opportunities. Why not use Hughes Aircraft as a base to create a new and needed defense electronics supplier?"

"Whether what you manage is a business, hospital, university department, government agency or even a symphony orchestra or dancing school, we suspect you will find it advisable to try to prepare ahead for what might happen in the future."

"We are in rapid transition today to a new world which threatens to be dominated by technological advance. In that new World. (1) man will have learned so much about nature's store of energy and its release that he will have the ability to virtually destroy civilization; (2) production, communication and transportation will all be "automatic" --these operations of man's material world will have become so vast and complex that they will have to proceed with a minimum of participation by man, his muscles, brains and senses; and (3) man will conquer space."

"My final word about editing. I was to appear on the cover of a business magazine, and the writer who came to interview me was intrigued with engineers, scientists, PhDs founding and running companies. It was somewhat more unusual back in those days than now, although it was not without ample precedents in the past. So the question he put to me right away starting the interview was, "Would you say, Dr. Ramo, that engineers make the best managers?" And I said, "Engineers make the best engineers." It may be that some engineers will have managerial talents, and be in the right place at the right time, just as may be true of lawyers or accountants or salesmen, or tax experts or whatever. Now, on the magazine then, here was this picture of me, and here was this quote: "Engineers make the best engineers." Well, someone, before the cover actually got out, knew that that was a mistake. Obviously that had been a misprint. So looking at the text, and seeing the question that was asked of me, he changed it to: "Engineers make the best managers." "I quote Dr. Ramo on engineers." All right."

"[The engineer] must identify the significant and critical problems, but in his education, problems have been predetermined and assigned. He must develop the judgment to know what solutions to problems are possible, but in school the problems encountered are known to have answers. He should be excited by new and unsolved challenges, but for 20 years he has lived in an educational system where he knows he is repeating the work of last year's students."

"Pestel was a very forceful person and quickly saw the power of system dynamics."

"No plea about inadequacy of our understanding of the decision-making processes can excuse us from estimating decision making criteria. To omit a decision point is to deny its presence – a mistake of far greater magnitude than any errors in our best estimate of the process."

"In spite of the tentative nature of the world model described here, various conclusions are drawn from it. Man acts at all times on the models he has available. Mental images are models. We are now using those mental models as a basis for action. Anyone who proposes a policy, law, or course of action is doing so on the basis of the model in which he, at that time, has the greatest confidence. Having defined with care the model contained herein, and having examined its dynamic behavior and implications, I have greater confidence in this world system model than in others that I now have available. Therefore, this is the model I should use for recommending actions. Those others who find this model more persuasive than the one they are now using presumably will wish to employ it until a better model becomes available."

"The strongest criticism has come from some economists. The objections range from simple misunderstanding, through belief that essential structures have been omitted from the world model, to concern over the costs and feasibility of halting economic growth. Although there is a basis for the criticisms, they have not had sufficient substance to dismiss the central issues. The debate seems to be gradually moving away from the question of whether or not industrial growth must slow to the question of what strategy should be used to limit growth. The latter question, however, remains unanswered."

"Professor Forrester told the National Academy of Engineering this fall, the "enterprise engineer," cast in the mold of the "professional engineer of folklore," is needed now more than ever before "to resynthesize the fragments caused by the specialization of other man"."

"The enterprise engineer must be a leader, a designer, and a synthesizer. He is a doer. He understands theory as a guide to practice. He must concern himself with human organization because the pace and success of technology are becoming more dependent on interaction with the social system and less on scientific discovery. In private as well as public research and development, such men must find ways to reverse the deterioration of ethics and efficiency. They will strengthen the information links between physical design and the public so that technology can better serve society. In the public sector they must show the level of wisdom and leadership that can co-ordinate great engineering projects with politics. They will recognise that informing the public and becoming a nucleus for crystallising public opinion is even more important in many programmes than is the underlying science."

"Another tradition in systems theory, known as system dynamics, originated at Massachusetts Institute of Technology. The founder of this tradition was Jay Forrester, a creative engineer who invented the magnetic core memory for computers and who built the , which is now in the Smithsonian Institution."

"There may be no realistic hope of the present underdeveloped countries reaching the standard of living demonstrated by the present industrialized nations. The pollution and natural-resource load placed on the world environmental system by each person in an advanced country is probably 20 to 50 times greater than the load now generated by a person in an underdeveloped country. With 4 times as many people in the underdeveloped countries as in the present developed countries, their rising to the economic level that has been set as a standard by the industrialized nations could mean an increase of 10 times in the natural-resource and pollution load on the world environment. Noting the destruction that has already occurred on land, in the air, and especially in the oceans, capability appears not to exist for handling such a rise in standard of living. In fact, the present disparity between the developed and underdeveloped nations may be equalized as much by a decline in the developed countries as by an improvement in the underdeveloped countries."

"Mesarovic and Pestel are critical of the Forrester-Meadows world view, which is that of a homogeneous system with a fully predetermined evolution in time once the initial conditions are specified."

"It is to be hoped that those who believe they already have some different model that is more valid will present it in the same explicit detail, so that its assumptions and consequences can be examined and compared. To reject this model because of its shortcomings without offering concrete and tangible alternatives would be equivalent to asking that time be stopped. But the world will continue to turn. We always use the most acceptable model at any point in time. But how should we proceed so that the most acceptable model is also the best one that is available? We should try for three things. First, the best existing model should be identified at each point in time. Second, the best currently existing model should be used in preference to traditional models that may be less clear and less correct. Third, aggressive effort should be devoted to a continual improvement in the available models of the world system."

"Formulating a model of a system should start from the question “Where is the boundary, that encompasses the smallest number of components, within which the dynamic behavior under study is generated?”"

"In concept a feedback system is a closed system. Its dynamic behavior arises within its internal structure. Any action which is essential to the behavior of the mode being investigated must be included inside the system boundary."

"In complex systems cause and effect are often not closely related in either time or space. The structure of a complex system is not a simple feedback loop where one system state dominates the behavior. The complex system has a multiplicity of interacting feedback loops. Its internal rates of flow are controlled by nonlinear relationships. The complex system is of high order, meaning that there are many system states (or levels). It usually contains positive-feedback loops describing growth processes as well as negative, goal-seeking loops. In the complex system the cause of a difficulty may lie far back in time from the symptoms, or in a completely different and remote part of the system. In fact, causes are usually found, not in prior events, but in the structure and policies of the system."

"It seems traditional for explicit models of social systems to be greeted by vague criticisms about their lack of perfection. Instead, we need equally explicit alternatives with a demonstration that the alternative leads to a different and more plausible set of conclusions. By proposal and counter proposition our understanding of social systems can advance."

"We consider an organization to be a set of constraints on the activities performed by agents. This view follows that of Weber, who views the process of bureaucratization as a shift from management based on self-interest and personalities to one based on rules and procedures. Mintzberg [1983] provides an early (and informal) analysis of organization structure distinguishing among five basic parts of an organization and five distinct organization configurations that are encountered in practice. This “ontology” includes several mechanisms that together achieve coordination, like goals, work processes, authority, positions and communication. The various parts of an organization are distinguished by the specific roles they play in achieving coordination with the above means. The “” (Winograd 1987) on cooperative work in organizations provides an ontology that emphasizes the social activity by which “agents” generate the space of cooperative actions in which they work, rather than the mental state of individuals. The basic idea is that social activity is carried out by language and communication."

"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."

"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."

"In , we want to define the actions performed within an enterprise, and define constraints for plans and schedules which are constructed to satisfy the goals of the enterprise. This leads to the following set of informal competency questions:"

"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."

"Reference disciplines are existing bodies of knowledge that help establish the new discipline, that are a foundation of support for future work, and that are logical linkages to previous works. Throughout history, new disciplines have emerged from the need to solve new problems that are not fully addressed by existing disciplines. Emerging disciplines build upon the knowledge, subject matter, methods, tools, and theories of existing reference disciplines."

"An enterprise must be viewed from several perspectives if it is to be fully described and understood (Barnett 1994; ESPIRIT Consortium AMICE 1991). Previous work in the development of architectures by the Automation & Robotics Research Institute (Presley et al. 1993) describes a five view approach. The Business Rule (or Information) View defines the entities managed by the enterprise and the rules governing their relationships and interactions. The Activity View defines the functions performed by the enterprise (what is done) while the Business Process View defines a time sequenced set of processes (how it is done). The resources and capabilities managed by the enterprise are defined in a Resource View. Finally, the Organization View is used to define how the enterprise organizes itself and the set of constraints and rules governing how it manages itself and its processes."

"Enterprise Engineering is defined as that body of knowledge, principles, and practices having to do with the analysis, design, implementation and operation of an enterprise. In a continually changing and unpredictable competitive environment, the Enterprise Engineer addresses a fundamental question: “how to design and improve all elements associated with the total enterprise through the use of engineering and analysis methods and tools to more effectively achieve its goals and objectives”..."

"An enterprise architecture can be thought of as a "blueprint" or "picture" which assists in the design of an enterprise. The enterprise architecture must define three things. First, what are the activities that an enterprise performs? Second, how should these activities be performed? And finally, how should the enterprise be constructed? Consequently, the architecture being developed will identify the essential processes performed by a virtual company, how the virtual company and the agile enterprises involved in the virtual company will perform these processes, and include a methodology for the rapid reconfiguration of the virtual enterprise."

"There is a paradigm shift towards a distributed and integrated enterprise. Currently, computer systems that support enterprise functions were created independently. This hampers Therefore, there is a need for a computer based data model which provides a shared and well defined terminology of an enterprise, and has the capability to deductively answer common sense questions. This paper discusses how TOVE tackles these needs by defining a framework for modeling generic level representations such as activities, time, and resources. Since there has never been a well-defined set of criteria to evaluate such models, this paper also introduces a set of evaluation criteria which may be used to evaluate modelling efforts."

"A discipline has six basic characteristics:"

"The presence of an enterprise reference architecture aids an enterprise in its ability to understand its structure and processes. Similar to a computer architecture, the enterprise architecture is comprised of several views. The enterprise architecture should provide activity, organizational, business rule (information), resource, and process views of an organization."

"Wayne’s book, A Mathematical Theory of Systems Engineering: The Elements, John Wiley, New York [1967] appeared in an era that spawned the concept of a mathematical system as a generalization of the control systems of engineers and the automata theories of computer scientists. Wymore employed the unusual term “Tricotyledon Theory of System Design” to portray the tri-partite nature of his theory. Tricotyledon, or three leaved seed, pictures a leaf for the class of models of the behavior of the system being designed, a second leaf for the technologies that are available to implement the system, and a leaf for the intersection of the two previous classes, namely, the technologies that can implement the models according to specified evaluation criteria. In subsequent work over three decades, he deepened the theory and applied it to numerous system engineering problems. The theory became the basis for his book, Model-based System Engineering, CRC Press, Inc. Boca Raton, FL, USA © 1993 and helped to spawn the trend toward use of systems modeling tools for systems design. However, Wayne himself did not emphasize the use of modeling and simulation as essential tools in systems engineering practice."

"System design can be requirements based, function based, or model based. Model based system engineering and design has an advantage of executable models that improve efficiency and rigor. One of the earliest developments of this technique was Wymore’s (1993) book entitled Model-based System Engineering, although the phrase “model-based system design” was in the title and topics of Rosenblit’s (1985) PhD dissertation. Model-based systems engineering depends on having and using well-structured models that are appropriate for the given problem domain."

"In the folklore of systems engineering, there are sayings, “If it isn't testable, it isn't a requirement,” and, “If it is not quantifiable, it is not testable.” I had always tended to subscribe to the particle of wisdom in these sayings. One of the many lessons that I learned from the CATIE experience, however, was that systems engineering had to be able to deal directly and purposively with what are usually considered to be strictly qualitative (unquantifiable) aspect of systems, such as quality of life, for example. The agricultural practices of these small farmers in Central America is such a large part of their lives that to change any part of their agricultural practices might be seen as diminishing their quality of life - even with respect to the color of the beans that the new practices might require. But even if we cannot deal directly with quality of life or user friendliness or enmity/sympathy, we can identify quantifiable figures of merit relating to these qualitative aspects and if we find enough figures of merit and combine them suitably, we might eventually obtain agreement that we have captured the essence of the qualitative aspect, at least as far as this particular set of stakeholders is concerned."

"Over 80 million people have participated in Cub Scout Pinewood Derbies. Pinewood is a case study of the design of a Cub Scout Pinewood Derby for one particular scout pack. The system helps manage the entire race from initial entry through final results. Many alternatives for race format, scoring, and judging are presented."

"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."

"After earning the PhD degree and acquiring some relatively extensive experience in digital computers… It was time to leave the University. The result of an extensive search for the right job was a family move to Arlington Heights, Illinois, where it was a short commute to the Research Laboratories of the Pure Oil Company at Crystal Lake. I was given the title of Mathematical and Computer Consultant. The Labs were set in a beautiful campus, the professional personnel were eager to learn what I had to teach and to include me in many interesting projects where my knowledge and skills could be put to good use. I was encouraged to initiate my own program of research. I went to work with enthusiasm. The corporate headquarters of Pure Oil were located in down town Chicago. Pure Oil had been trying to install an IBM 705 computer system for all their accounting needs including calculation of all data necessary for the management of exploration, drilling, refining and distribution of oil products and even royalties to shareholders in oil wells. Typical for those early days, the programming team was in deep difficulties and needed help; they lacked adequate resources and suitable training. The Executive Vice President of Pure Oil, when he heard that there was a computer expert already on the payroll at the Crystal Lake lab, ended our family blissful dream and I was reassigned to the down town office."

"During this period I was able to carry out only one project of real interest to me. Pure Oil was a fully integrated oil company in the sense that they engaged in exploration for oil, construction of oil wells, production of crude oil, transportation to refineries, distribution of refinery products to company owned storage facilities and to gas stations. We developed a linear programming model of the whole network hoping to discover the optimum allocation to and from connected nodes in order to meet required deliveries at minimum cost. Then we collected all the data needed by our model and ran the model. The computations took several days and the results were disappointing: The optimum allocations were not significantly different from their current practices. Is it possible that we had discovered a system of human beings in which everyone knew the payoff functions and constraints, and, over time, had evolved behavior patterns that enabled them to achieve near optimum performance? Or was it possible that our model was not detailed enough as it was based so closely on current practice that no new behavior could emerge? Or was our data incorrect? This was disappointing but great experience."

"[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."

"General systems theory is considered as a formal theory (Mesarovic, Wymore), a methodology (Ashby, Klir), a way of thinking (Bertalanffy, Churchman), a way of looking at the world (Weinberg), a search for an optimal simplification (Ashby, Weinberg), didactic method (Boulding, Klir, Weinberg), metalanguage (Logren), and profession (Klir)."

"If all the theories pertinent to systems engineering could be discussed within a common framework by means of a standard set of nomenclature and definitions, many separate courses might not be required."

"Every author has several motivations for writing, and authors of technical books always have, as one motivation, the personal need to understand; that is, they write because they want to learn, or to understand a phenomenon, or to think through a set of ideas."

"Only if mathematical rigor is adhered to, can systems problems be dealt with effectively, and so it is that the systems engineer must, at least, develop an appreciation for mathematical rigor if not also considerable mathematical competence."