Introduction to Engineering V. Arrichiello “It seems natural to begin the discussion with an immediate formal definition of systems engineering. However, systems engineering is an amorphous, slippery subject that does not lend itself well to such formal, didactic treatment . ”

Hendrik Wade Bode: The Systems Approach, in Applied Science – Technological Progress, report to the Committee on Science and Astronautics, US House of Representatives (1967)

2 ©2014 Vincenzo Arrichiello - INCOSE Italia Systems Engineering

WHEN? WHY? WHO? WHERE? WHAT? HOW?

3 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context

4 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context

1940 - “Operations Research

1948 - Norbert Wiener “: Or Control and Communication in the Animal and the Machine” 1950 - Ludwig von Bertalanffy “An outline of General Systems Theory”

Google books Ngram Viever 5 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context General Theory While in the past, science tried to explain observable phenomena by reducing them to an interplay of elementary units investigatable independently of each other, conceptions appear itin contemporary sc ithtience that are concerne dithd with what is somewhat vaguely termed "wholeness," i.e., problems of organization, phenomena not resolvable into local events, dynamic interactions manifest in the difference of behavior of parts when isolated or in a higher configuration, etc.; in short, "systems" of various orders not understandable by investigation of their respective parts in isolation.

Hence the appearance, in all fields of science, of notions like wholeness, holistic, organismic, gestalt, etc., which all signify that, in the last resort, we must think in terms of systems of elements in mutual interaction.

Ludwig von Bertalanffy, General System Theory: Foundations, Development, Applications, 1968, Braziller. 6 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context General System Theory

The meaning of the somewhat mystical expression, "the w ho le is more th an th e sum of part s"i" is s imp ly thtthat constitutive characteristics are not explainable from the characteristics of isolated parts. The characteristics of the complex, therefore, compared to those of the elements, appear as "new" or "emergent."

Ludwig von Bertalanffy, General System Theory: Foundations, Development, Applications, 1968, Braziller. 7 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context General System Theory

Open system is defined as a system in exchange of matter with its environment, presenting import and export, building-up and breaking-down of its material components.

The basis of the open-system model is the dynamic interaction of its components.

Ludwig von Bertalanffy, General System Theory: Foundations, Development, Applications, 1968, Braziller. 8 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context General System Theory

Technology has been led to think not in terms of single machines but in those of "systems." A steam engine, automobile, or radio receiver was within the competence of the engineer trained in the respective specialty. But when it comes to ballistic missiles or space vehicles, they have to be assembled from components originating in heterogeneous technologies, mechanical, electronic, chemical, etc.; relations of man and machine come into play; and innumerable financial, economic, social and political problems are thrown into the bargain.

Ludwig von Bertalanffy, General System Theory: Foundations, Development, Applications, 1968, Braziller. 9 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context General System Theory

Technology has been led to think not in terms of single machines but in those of "systems." A steam engine, automobile, or radio receiver was within the competence of the engineer trained in the respective specialty. But when it comes to ballistic missiles or space vehicles, they have to be assembled from components originating in heterogeneous technologies, mechanical, electronic, chemical, etc.; relations of man and machine come into play; and innumerable financial, economic, social and political problems are thrown into the bargain. Thus, a "systems approach" became necessary. A certain objective is given; to find ways and means for its realization requires the systems specialist (or team of specialists) to consider alternative solutions and to choose those promising optim iza tion a t maxiffiidiiltimum efficiency and minimal cost itin a tremen dldously complex network of interactions. Ludwig von Bertalanffy, General System Theory: Foundations, Development, Applications, 1968, Braziller. 10 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context Cybernetics

In the newer study of automata, whether in the metal or in the flesh, … we deal with automata effectively coupled to the external world, not merely by their energy flow, their metabolism, but also by a flow of impressions, of incoming messages, and of the acti ons of out goi ng messages.

To sum up: the many automata of the present age are coupled to the outside world both for the reception of impressions and for the performance of actions. They contain sense organs, effectors, and the equivalent of a nervous system to integrate the transfer of information from the one to the other. They lend themselves very well to description in physiological terms. [Organic Analogy] Norbert Wiener, Cybernetics: Or Control and Communication in the Animal and the Machine, 1948, MIT Press 11 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context Cybernetics

The behavioristic approach consists in the examination of the output of the object and of the relations of this output to the input. By output is meant any change produced in the surroundings by the object. By input, conversely, is meant any event external to the object that modifies this object in any manner. … a uniform behavioristic analysis is applicable to both machines and living organisms, regardless o fthf the comp lex ity o fthf the be hav ior.

Rosenblueth A., Wiener N. and Bigelow J., Behavior, Purpose and Teleology, 1943, Philosophy of Science, 10 12 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context Cybernetics

The terms "black box" and "white box" are convenient and figurative expressions of not very well determined usage. I shall understand by a black box a piece of apparatus, such as four-terminal networks with two input and two output t ermi na ls, w hic h per forms a de fin ite opera tion on the presen t an d pas t of the input potential, but for which we do not necessarily have any information of the structure by which this operation is performed. On the other hand, a white box will be similar network in which we have built in the relation between input and output potentials in accordance with a definite structural plan for securing a previously determined input-output relation

Norbert Wiener, Cybernetics: Or Control and Communication in the Animal and the Machine, 1948, MIT Press 13 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context Operations Research

An objective of Operations Research is to provide managers of the organization with a scientific basis for solving problems involving the interaction of components of the organization in the best interest of the organization as a whole.

The comprehensiveness of O.R.'s aim is an example of a "systems" approach, since "system" implies an interconnected complex of functionally related components.

... to see a system as a whole means not only to see all its components and their interrelationships but also all aspects of its operations .

Churchman C.W., Ackoff R.L., Arnoff E.L., "Introduction to Operations Research", John Wiley & Sons, 1957 14 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Cultural Context Operations Research

Mixed Team Approach Although mathematicians, physicists and engineers were essential, the best of the groups also contained physiologists, biochemists, psychologists, and a variety of representatives of other fldfhbfields of the bioc hemica l an d socia l sciences. … it was found that members of such diverse groups could work together and could form a unit which was much greater than the mere sum of its parts.

Warren Weaver “Science and complexity,” American Scientist, 36 (1948) 15 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Technological Context

16 ©2014 Vincenzo Arrichiello - INCOSE Italia Historical Context

"On Guard! The Story of SAGE", IBM Corporation, Military Products Division, (ca. 1956), The Internet Archive, Prelinger Archives 17 ©2014 Vincenzo Arrichiello - INCOSE Italia Historical Context

"On Guard! The Story of SAGE", IBM Corporation, Military Products Division, (ca. 1956), The Internet Archive, Prelinger Archives 18 ©2014 Vincenzo Arrichiello - INCOSE Italia Historical Context

"On Guard! The Story of SAGE", IBM Corporation, Military Products Division, (ca. 1956), The Internet Archive, Prelinger Archives 19 ©2014 Vincenzo Arrichiello - INCOSE Italia Historical Context

"On Guard! The Story of SAGE", IBM Corporation, Military Products Division, (ca. 1956), The Internet Archive, Prelinger Archives 20 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Historical Context

21 ©2014 Vincenzo Arrichiello - INCOSE Italia When? Systems Engineering was mainly developed "out of necessity" by these programs

ICBM SAGE APOLLO

22 ©2014 Vincenzo Arrichiello - INCOSE Italia Intercontinental Ballistic Missile Program (ICBM)

The Air Force ballistic missile program is the largest single military program ever undertaken by the United States. It is managed by the Air Force, with the support of more than 30 major contractors, 200 majj,,ppor subcontractors, and 200,000 suppliers in industries across the Nation, whose joint resources include skills of thousands of scientists, engineers, and technicians. Findings Resulting From Initial Review of The Ballistic Missile Programs of the Department of the Air Force - The Comptroller General of the United States, 1960

23 ©2014 Vincenzo Arrichiello - INCOSE Italia A Dangerous Mix

24 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? A Dangerous Mix

Novel, heterogeneous technologies

25 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? A Dangerous Mix

Novel, heterogeneous technologies

Complexity

26 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? A Dangerous Mix

Novel, heterogeneous technological technologies race

Complexity

27 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? A Dangerous Mix

Novel, Cold War heterogeneous technological technologies race

Compressed Complexity Time -scale

28 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? A Dangerous Mix

Novel, Cold War heterogeneous technological technologies race

Compressed Complexity Failure rate Time -scale

29 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? A Dangerous Mix

Novel, Cold War heterogeneous technological technologies race

Compressed Complexity Failure rate Time -scale

30 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies

Rocket RF Propulsion Communic.

Inertial Aerodynamics ICBM Navigation

Structural Automatic Eng. Control

31 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies ADVERSE INTERACTIONS

Rocket RF Propulsion Communic.

Inertial Aerodynamics ICBM Navigation

Structural Automatic Eng. Control

32 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies ADVERSE INTERACTIONS

Rocket RF Propulsion Communic.

Vibrations

Inertial Aerodynamics ICBM Navigation

Structural Automatic Eng. Control

33 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies ADVERSE INTERACTIONS

Rocket RF Propulsion Communic.

Electrom. Vibrations interference Inertial Aerodynamics ICBM Navigation

Structural Automatic Eng. Control

34 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies ADVERSE INTERACTIONS

Rocket RF Propulsion Communic.

Electrom. Vibrations interference Inertial Aerodynamics ICBM Navigation Environm. stress

Structural Automatic Eng. Control

35 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies ADVERSE INTERACTIONS

Rocket RF Propulsion Communic.

Electrom. Vibrations interference Inertial Aerodynamics ICBM Navigation Environm. Reliability stress

Structural Automatic Eng. Control

36 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies

Rocket RF Propulsion Communic.

Inertial Aerodynamics ICBM Navigation

Structural Automatic Eng. Control

37 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies POOR COMMUNICATIONS

Rocket RF Propulsion Communic.

Inertial Aerodynamics ICBM Navigation

Structural Automatic Eng. Control

38 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies POOR COMMUNICATIONS

Rocket RF Propulsion Communic.

Inertial Aerodynamics ICBM Navigation

Pieter Bruegel de Oude, De toren van Babel Structural Automatic Eng. Control

39 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Diverse worlds

40 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Diverse engineering worlds

Joseph Griffith Reed Radio Pioneer Robert H. Goddard 41 ©2014 Vincenzo Arrichiello - INCOSE Italia Rocketry Pioneer Who, Where? Systems Engineering to the rescue

"novelty, depth of knowledge, and heterogeneity [of the new disciplines], made it impossible for any one person to master in depth all of the skills needed... “jack-of-all-trades” technical generalist assumed critical importance." The United States Air Force and the Culture of Innovation,1945–1965 - Stephen B. Johnson

42 ©2014 Vincenzo Arrichiello - INCOSE Italia Who, Where? Systems Engineering to the rescue

"novelty, depth of knowledge, and heterogeneity [of the new disciplines], made it impossible for any one person to master in depth all of the skills needed... “jack-of-all-trades” technical generalist assumed critical importance." The United States Air Force and the Culture of Innovation,1945–1965 - Stephen B. Johnson

Interdisciplinar Knowledge

43 ©2014 Vincenzo Arrichiello - INCOSE Italia Who, Where? Systems Engineering to the rescue

"novelty, depth of knowledge, and heterogeneity [of the new disciplines], made it impossible for any one person to master in depth all of the skills needed... “jack-of-all-trades” technical generalist assumed critical importance." The United States Air Force and the Culture of Innovation,1945–1965 - Stephen B. Johnson

Holistic/System Thinking Interdisciplinar Knowledge

44 ©2014 Vincenzo Arrichiello - INCOSE Italia Who, Where? Systems Engineering to the rescue

"novelty, depth of knowledge, and heterogeneity [of the new disciplines], made it impossible for any one person to master in depth all of the skills needed... “jack-of-all-trades” technical generalist assumed critical importance." The United States Air Force and the Culture of Innovation,1945–1965 - Stephen B. Johnson Teamworking Ability Holistic/System Thinking Interdisciplinar Knowledge

45 ©2014 Vincenzo Arrichiello - INCOSE Italia Who, Where? Systems Engineering to the rescue

"novelty, depth of knowledge, and heterogeneity [of the new disciplines], made it impossible for any one person to master in depth all of the skills needed...

“jack-of-all-trades” Life Cycle technical generalist Visi on assumed critical importance." The United States Air Force and the Culture of Innovation,1945–1965 - Stephen B. Johnson Teamworking Ability Holistic/System Thinking Interdisciplinar Knowledge

46 ©2014 Vincenzo Arrichiello - INCOSE Italia Who, Where? Systems Engineering to the rescue

General Bernard A. Schriever Simon Ramo Western Development Division (WDD) Dean Wooldridge 47 ©2014 Vincenzo Arrichiello - INCOSE Italia Ramo-Wooldridge Corporation What, How? Systems Engineering to the rescue Communications - Documentation

Bell Telephone Laboratories performed research and development for AT&T.

The Secret of Apollo: Systems Management in American and European Space Programs, Stephen B. Johnson, Johns Hopkins University Press, 2006 48 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Communications - Documentation

Bell Telephone Laboratories performed research and development for AT&T.

BllLbBell Labs researc hers typ ica lly ass igne dhdd hardware prototype manufacturing to Western Electric, AT&T's manufacturing arm.

The Secret of Apollo: Systems Management in American and European Space Programs, Stephen B. Johnson, Johns Hopkins University Press, 2006 49 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Communications - Documentation

Bell Telephone Laboratories performed research and development for AT&T.

BllLbBell Labs researc hers typ ica lly ass igne dhdd hardware prototype manufacturing to Western Electric, AT&T's manufacturing arm.

Because of the large size of the corporation and the multiplicity of projects, Bell Lab and Western Electric developed formal specifications and pppaperwork to handle the relationshi p between researchers and Western Electric engineers and manufacturing workers.

The Secret of Apollo: Systems Management in American and European Space Programs, Stephen B. Johnson, Johns Hopkins University Press, 2006 50 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Systems Analysis - Trade-Offs

Nose-cone systems study R-W personnel examined trade-offs between warhead weight and yield, guidance accuracy, re-entry speed and thermodynamics, nose-cone materials, and other variables.

51 "Necessity as the Mother of Convention: Developing the ICBM, 1954-1958", Davis Dyer, BUSINESS AND ECONOMIC HISTORY, Fall 1993 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Systems Analysis - Trade-Offs

Nose-cone systems study R-W personnel examined trade-offs between warhead weight and yield, guidance accuracy, re-entry speed and thermodynamics, nose-cone materials, and other variables.

This analysis permitted scaling down of the gross weight of the Atlas from 460,000 pounds to 240,000 pounds and reduction of the propulsion system from five rocket motors to three.

52 "Necessity as the Mother of Convention: Developing the ICBM, 1954-1958", Davis Dyer, BUSINESS AND ECONOMIC HISTORY, Fall 1993 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Systems Analysis - Trade-Offs

Nose-cone systems study R-W personnel examined trade-offs between warhead weight and yield, guidance accuracy, re-entry speed and thermodynamics, nose-cone materials, and other variables.

This analysis permitted scaling down of the gross weight of the Atlas from 460,000 pounds to 240,000 pounds and reduction of the propulsion system from five rocket motors to three.

It is estimated that this analysis ... saved more than one year of development time and reduced the total cost of the missile by a quarter.

53 "Necessity as the Mother of Convention: Developing the ICBM, 1954-1958", Davis Dyer, BUSINESS AND ECONOMIC HISTORY, Fall 1993 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Extensive Testing

All components underwent tests that checked environmental tolerances (temperature, humidity, and so forth), vibration tolerance, component functions, and interactions among assembled components. The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson

"On Guard! The Story of SAGE", IBM Corporation, Military Products Division, (ca. 1956), The Internet Archive, Prelinger Archives 54 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Extensive Testing

All components underwent tests that checked environmental tolerances (temperature, humidity, and so forth), vibration tolerance, component functions, and interactions among assembled components. The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson

"On Guard! The Story of SAGE", IBM Corporation, Military Products Division, (ca. 1956), The Internet Archive, Prelinger Archives 55 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Extensive Testing

All components underwent tests that checked environmental tolerances (temperature, humidity, and so forth), vibration tolerance, component functions, and interactions among assembled components. The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson

"On Guard! The Story of SAGE", IBM Corporation, Military Products Division, (ca. 1956), The Internet Archive, Prelinger Archives 56 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Extensive Testing

All components underwent tests that checked environmental tolerances (temperature, humidity, and so forth), vibration tolerance, component functions, and interactions among assembled components. The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson

"On Guard! The Story of SAGE", IBM Corporation, Military Products Division, (ca. 1956), The Internet Archive, Prelinger Archives 57 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Extensive Testing

All components underwent tests that checked environmental tolerances (temperature, humidity, and so forth), vibration tolerance, component functions, and interactions among assembled components. The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson

"On Guard! The Story of SAGE", IBM Corporation, Military Products Division, (ca. 1956), The Internet Archive, Prelinger Archives 58 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Change Control - Configuration Management

"a number of test failures resulted from mismatches between the design of the missile and the actual hardware configuration of the missile on the launch pad" The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson

59 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Change Control - Configuration Management

"a number of test failures resulted from mismatches between the design of the missile and the actual hardware configuration of the missile on the launch pad" The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson "Configuration Control Board, which had responsibility for assuring that any necessary changes in component design would be immediately reflected throughout the total missile configuration." "Necessity as the Mother of Convention: Developing the ICBM, 1954-1958", Davis Dyer, BUSINESS AND ECONOMIC HISTORY, Fall 1993

60 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Change Control - Configuration Management

"a number of test failures resulted from mismatches between the design of the missile and the actual hardware configuration of the missile on the launch pad" The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson "Configuration Control Board, which had responsibility for assuring that any necessary changes in component design would be immediately reflected throughout the total missile configuration." "Necessity as the Mother of Convention: Developing the ICBM, 1954-1958", Davis Dyer, BUSINESS AND ECONOMIC HISTORY, Fall 1993

"fii"configuration contro ldl drew from the Boeing Company’s aircraft programs" Samuel Phillips and the Taming of Apollo - Stephen B. Johnson, Technology and Culture, October 2001

61 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How?

Systems Engineering to the rescue System Management

62 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How?

Systems Engineering to the rescue System Management

A meeting in the program control and status room in the Air Force Ballistic Missile Division offices. The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson, Air Force History and Museums Program, Washington, D. C., 2002

63 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How?

Systems Engineering to the rescue System Management

A meeting in the program control and status room in the Air Force Ballistic Missile Division offices. The United States Air Force and the Culture of Innovation, 1945–1965 - Stephen B. Johnson, Air Force History and Museums Program, Washington, D. C., 2002 Project Control Room: "to serve as a nerve center for all project ifinforma tion, inc ldiluding har dware dlidelivery sc hdlhedules, tes t sc hdlhedules, and operational planning schedules" "Necessity as the Mother of Convention: Developing the ICBM, 1954-1958", Davis Dyer, Business and Economic History, Fall 1993 64 ©2014 Vincenzo Arrichiello - INCOSE Italia Systems Engineering to the rescue some signs of improvement

Apollo launch-vehicle man-rating: Some considerations and an alternative contingency plan - RAND Corporation, 1965 65 ©2014 Vincenzo Arrichiello - INCOSE Italia Semi-Automatic Ground Environment (SAGE) "first major real-time, -based command-and-. DiDesigne dtd to pro ttthUitdSttftect the United States from long range bom bers " http://www.ll.mit.edu/news/ieee-milestone-SAGE.html

66 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies

Radar

Software SAGE Communications

Human Air D ef ence Factor

67 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies UNPRECEDENTED CHALLENGES

Radar Computers

Software SAGE Communications

Human Air D ef ence Factor

68 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies UNPRECEDENTED CHALLENGES

Radar Computers

Reliability

Software SAGE Communications

Human Air D ef ence Factor

69 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies UNPRECEDENTED CHALLENGES

Radar Computers

Reliability

Software SAGE Communications Human-machine Interaction

Human Air D ef ence Factor

70 ©2014 Vincenzo Arrichiello - INCOSE Italia Why? Multiple Technologies UNPRECEDENTED CHALLENGES

Radar Computers

Reliability

Software SAGE Communications Software Human-machine Development Interaction

Human Air D ef ence Factor

71 ©2014 Vincenzo Arrichiello - INCOSE Italia Who, Where?

MIT - Lincoln Laboratory Whirlwind control room

Jay Forrester and Bob Everett (standing) 72 ©2014 Vincenzo Arrichiello - INCOSE Italia Who, Where?

The pioneers of SAGE, Dr. Jay Forrester (left) and Robert Everett (right) at the IEEE Milestone Award ceremony (27 June 2012)

MIT - Lincoln Laboratory Whirlwind control room

Jay Forrester and Bob Everett (standing) 73 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Reliability (systemic approach)

74 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Reliability (systemic approach)

• Vacuum Tube Life • Marginal Checking

75 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Reliability (systemic approach)

• Vacuum Tube Life • Marginal Checking • Easy Maintenance • Duplexing

76 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Reliability (systemic approach)

• Vacuum Tube Life • Marginal Checking • Easy Maintenance • Duplexing

between June and November 1955, the computer operated on a 24- hour, 7-day schedule with 97.8% reliability MIT Lincoln Laboratory: History:Early Digital http://www.ll.mit.edu/about/History/digitalcomputing_2.html 77 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Human System Integration

78 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Human System Integration

• interactive ggpraphic displays,

79 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Human System Integration

• interactive ggpraphic displays, • light-pen input

80 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Human System Integration

• interactive ggpraphic displays, • light-pen input • training (virtual simulations)

81 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Software Development (method and documentation)

82 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Software Development (method and documentation)

• process and dttidocumentation

Production of Large Computer Programs - H. D. Bennington [1956], IEEE Annals of The History of Computing, 1983 83 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Software Development (method and documentation)

• process and dttidocumentation • thorough testing

Production of Large Computer Programs - H. D. Bennington [1956], IEEE Annals of The History of Computing, 1983 84 ©2014 Vincenzo Arrichiello - INCOSE Italia What, How? Systems Engineering to the rescue Software Development (method and documentation)

• process and dttidocumentation • thorough testing • problem-reporting procedure

Production of Large Computer Programs - H. D. Bennington [1956], IEEE Annals of The History of Computing, 1983 85 ©2014 Vincenzo Arrichiello - INCOSE Italia Systems Engineering reaching maturity

May 25, 1961 July 20th, 1969

First, I believe that this nation should commit itse lf to ac hiev ing the goa l, before this decade is out, of landing a man on the moon and returninggy him safely to the earth. "Houston,,qy Tranquility base here. The

Special Message to the Congress on Urgent National Needs, President John F. eagle has landed.” Kennedy 86 ©2014 Vincenzo Arrichiello - INCOSE Italia The wi nni ng trai ts of S ystems E ngi neeri ng

Systems Engineering has proved effective in bringing to success large, complex, and innovative projects by combining: • Strong motivation • Technical prowess • Creativity • Systematic approach • Systemic vision

87 ©2014 Vincenzo Arrichiello - INCOSE Italia Systems Engineering SYSTEMATIC and SYSTEMIC

88 ©2014 Vincenzo Arrichiello - INCOSE Italia Systematic and Systemic

Systematic –refers to taking a structured, orderly approach to solve the problem and to implement the system.

89 ©2014 Vincenzo Arrichiello - INCOSE Italia Systematic and Systemic

Systematic –refers to taking a structured, orderly approach to solve the problem and to implement the system.

Systemic – refers to the holistic appreciation of the problem/system of interest, considering its context, stakeholders, and the interrelationships and interconnections.

90 ©2014 Vincenzo Arrichiello - INCOSE Italia Systematic and Systemic

StSystems eng ineer ing is an itdiiliinterdisciplinary approach and means to enable the realization of successful systems.

INCOSE Systems Engineering Handbook v. 3.2.2, December 2011 91 ©2014 Vincenzo Arrichiello - INCOSE Italia SYSTEMATIC and Systemic

StSystems eng ineer ing is an itdiiliinterdisciplinary approach and means to enable the realization of successful systems. It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, and then proceeding with design synthesis and system validation while considering the complete problem: operations, cost and schedule, performance, training and support, test, manufacturing, and disposal. SE considers both the business and the technical needs of all customers with the goal of providing a quality product that meets the user needs.

INCOSE Systems Engineering Handbook v. 3.2.2, December 2011 92 ©2014 Vincenzo Arrichiello - INCOSE Italia Systematic and SYSTEMIC

StSystems eng ineer ing is an itdiiliinterdisciplinary approach and means to enable the realization of successful systems. It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, and then proceeding with design synthesis and system validation while considering the complete problem: operations, cost and schedule, performance, training and support, test, manufacturing, and disposal. SE considers both the business and the technical needs of all customers with the goal of providing a quality product that meets the user needs.

INCOSE Systems Engineering Handbook v. 3.2.2, December 2011 93 ©2014 Vincenzo Arrichiello - INCOSE Italia StSystemati creference: Processes and Standards

INCOSE Systems Engineering Handbook v. 3.2.2, December 2011 94 ©2014 Vincenzo Arrichiello - INCOSE Italia Systemic reference: Principles - Guidelines

“Left Shift” “Seven Pillars”

95 ©2014 Vincenzo Arrichiello - INCOSE Italia Left Shift

Earl y commit ment of resources i n th e proj ect lif ecycl e (the resource profile shows a”peak” on the left side) • anticipated discovery of errors and omissions • proactive building of a problem-specific knowledge basis

Emes, MR; Smith, A; James, AM; Whyndham, MW; Leal, R; Jackson, SC; (2012) “Principles of systems engineering management: Reflections from 45 years of spacecraft technology research and development at the mullard space science laboratory”. In: 22nd Annual International Symposium of the International Council on Systems Engineering, INCOSE 2012 96 ©2014 Vincenzo Arrichiello - INCOSE Italia Left Shift Anticipated discovery of errors and omissions

Problems discovered and solved

Project lifelife-cycle-cycle

97 ©2014 Vincenzo Arrichiello - INCOSE Italia Left Shift Anticipated discovery of errors and omissions

Problems Costs of discovered solving and solved problems

Project lifelife-cycle-cycle Project lifelife-cycle-cycle

98 ©2014 Vincenzo Arrichiello - INCOSE Italia Left Shift Proactive building of problem-specific knowledge basis

INCOSE Systems Engineering Handbook v. 3.2.2, December 2011

99 ©2014 Vincenzo Arrichiello - INCOSE Italia Left Shift Proactive building of problem-specific knowledge basis

Blanchard, B., and Fabrycky, W., Systems Engineering and Analysis, Prentice Hall, 1998 100 ©2014 Vincenzo Arrichiello - INCOSE Italia Left Shift Proactive building of problem-specific knowledge basis

101 ©2014 Vincenzo Arrichiello - INCOSE Italia Left Shift Proactive building of problem-specific knowledge basis

Left-Shfhift

102 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Life -Cycle

Requirements

The Seven Pillars of

Perspectives Gates Systems Engineering

Trade-Offs Operational Effectiveness Modeling & Simulation

Adapted from: Systems thinking : coping with 21st century problems, 103 ©2014 Vincenzo Arrichiello - INCOSE Italia John Boardman, Brian Sauser, Taylor & Francis, 2008 The Seven Pillars of Systems Engineering

Life -Cycle

104 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Life -Cycle

CONCEPT DEVELOPMENT PRODUCTION UTILIZATION SUPPORT RETIREMENT

105 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Gates

"to ensure controlled progress toward a final goal"

106 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Gates

"to ensure controlled progress toward a final goal"

107 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Requirements

"thoroughly explore and understand both the Problem and Solution Spaces" 108 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Requirements

"connecting, but keeping separate "

109 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Requirements

WHAT HOW

110 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Requirements

111 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Perspectives

112 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Perspectives

113 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Perspectives

114 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Perspectives

115 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Perspectives

116 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Perspectives

117 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Perspectives

118 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Perspectives

119 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Perspectives

120 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Trade-Offs

Objectives Hierarchy

121 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Trade-Offs

Objectives Hierarchy

Quantitative VlValue M Mdlodel

122 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Trade-Offs

Objectives Hierarchy

Pareto Quantitative frontier VlValue M Mdlodel

123 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Modeling & Simulation

124 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

"My brother Orville and I built a rectangle-shaped open-ended wind tunnel out of a wooden box. Modeling & It was, in fact, the first wind tunnel in which small Simulation models of wings were tested " Wilbur Wright

125 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

"My brother Orville and I built a rectangle-shaped open-ended wind tunnel out of a wooden box. Modeling & It was, in fact, the first wind tunnel in which small Simulation models of wings were tested " Wilbur Wright

Modeling saved their time, money and, probably, lives.

Kitty Hawk, December 17, 1903 126 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Operational Effectiveness

127 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Operational Effectiveness

128 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Operational Effectiveness

129 ©2014 Vincenzo Arrichiello - INCOSE Italia The Seven Pillars of Systems Engineering

Operational Effectiveness

130 ©2014 Vincenzo Arrichiello - INCOSE Italia RECAP

Systems Engineering is: not just a set of processes (Systematic) but mainly a mindset , a point of view, a method of attack of complexity, with a focus on the fundamental objectives (needs) to be achieved (Systemic)

131 ©2014 Vincenzo Arrichiello - INCOSE Italia 132 ©2014 Vincenzo Arrichiello - INCOSE Italia Thank you for yor attention. Questions? 133 ©2014 Vincenzo Arrichiello - INCOSE Italia [email protected]