Course Introduction

1. EMIS 7307 Course Introduction

2. EMIS 7307 Background • Highlights (which hopefully will give useful insights to course topics): • Much of career has been backwards! • Started with reverse engineering included basic science and now am technical support to acquisition programs.

3. EMIS 7307 Background • Analyzed Soviet missile telemetry to determine guidance law of ICBMs. • Goal - assess accuracy. • Telemetry from their test program. • RF signal containing sampled engineering parameters. • They made many launches. • Would there be so many today? Why/ why not?

4. EMIS 7307 Background • Test director for AAR-34 improvement program • F-111 tail mounted IR detector of aircraft and AAMs. • Numerous false alarms rendered it useless in Vietnam. • Contractor/PO needed to test improvements. • Safety issues (reason not done right originally). • Once safety resolved, 20+ sensors piggy-backed. • Fired 120 missiles (Would that happen today?).

5. EMIS 7307 Missile protection on F-111 Infrared sensor

6. EMIS 7307 In Viet Nam Jungle with ponds Sun- glint Sun Glint To the F111 warning sensor, it looked like an enemy missile or aircraft!

7. EMIS 7307 Dispense chaff and flares!

8. EMIS 7307 What to do? • Improvement program…a sensor redesign • Improvements need to be tested • Took improved sensor to White Sands Missile Range (WSMR) New Mexico for testing

9. EMIS 7307 WSMR What else was tested here?

10. EMIS 7307 Fired 120 missiles at the sensor Falcons, Sidewinders including…

11. EMIS 7307 10 Soviet Atolls In 1958 a Sidewinder was fired from a Taiwanese F-86 Sabre aircraft. It lodged without exploding in a Chinese MiG-17. It was transferred to the Soviets who made the Atoll based on it.

12. EMIS 7307 WSMR Over 20 sensors “piggy-backed” on these missile firings test! Over 100 people at the test site.

13. EMIS 7307 A day in my life • Fly to WSMR test control station • Helicopter to test site • Fly back to control station • Supervise test • Return to home base • Look at data, and get reports of results Extreme excitement and satisfaction!

14. EMIS 7307 Background • SGEMP experimenter. • Basic research. • Info for spacecraft design using vacuum tank and idealized models of spacecraft shapes. • Note sometimes only the gov’t can afford to get the needed engineering info, market dependent. • Unless security issues, info is freely available. • AFOTEC operations analyst. • Operational test planning. • From the very beginning!

15. EMIS 7307 Background • Director of GPS user equipment test program. • Gathered data for the Air Force to use in it’s Milestone 2 (B) decision. • Instrument approaches, bombing, surveying etc. • Doubter’s chair. • Circular error probable (CEP).

16. In the 1970s… • GPS did not exist • Military navigation done with • Compass • Map • Star sighting with a sextant • Time of signal to go to a known place and back • Both accuracy and not being detected were big issues

17. Could GPS be the answer? • Satellites send signals containing the satellite’s position. • A receiver receiving three or more satellite’s signals can calculate its own position without being detected. • The questions were… • Would it work? • How to find out? • The answer was… • A test program!

18. The test setup • A few satellites were launched, and a few pretend satellites were installed, on the ground, at Yuma Proving Ground, Arizona. • Whenever the satellites passed overhead, a test could be conducted. • The idea was to see if a variety of possible users would find GPS useful.

19. Some of the GPS users

20. 2000-pound dumb bomb

21. Used GPS to position the airplanefor bomb drop

22. Repeatedly impacted in a small area Doubter’s chair

23. You know the rest of the story This is GPS now. Based on this test program, the Pentagon decided to build the GPS.

24. EMIS 7307 Background • System engineer for equipment for a spacecraft’s handling and testing. • So big only the shuttle could launch it. • Extreme reliability. • Needed testing in space environment. • Think about the difference in the test requirements compared to GPS user’s equipment.

25. EMIS 7307 Background • I&T manager for “special” program. • Involved from the beginning. • Major contributor to specification. • “If you can’t readily imagine a verification technique it’s not a good specification!” • System Integration lab is a crummy place to find interface issues caused by poor communication during the design process. Sources of poor com? • However, the fully assembled, ultimate system, is a much worse place!!

26. EMIS 7307 Background • Contracting Officers Representative (COR) for “special” program. • Good system engineers are very hard to find. • Engineers revert to their roots. • Therefore perhaps best if roots are SE? • Even with the best of intentions there is never enough time for testing. • Design issues eat into test time and the delivery date doesn’t change. • Decision? Bad (or untried) system vs. late system! • Integrated test and product teams work well.

27. EMIS 7307 Overview and Chapter 1 • Goal is to appreciate and understand the different perspectives!

28. EMIS 7307 Overview and Chapter 1 • I&T are integral and essential aspects of systems engineering. As such a foundational understanding of SE is essential to the understanding of the subject. • We are going to survey the process of systems engineering, however: • Always thinking about the effect on I&T and T&E • Bottom line: These so-called “tail-end” functions aren’t really - thinking, planning and occasionally executing are from the beginning.

29. EMIS 7307 Overview Integration vs. Interoperability • Notion of integration and interoperability getting blurred. • Integration implies within a system. • Interoperability implies between systems. • With systems of systems becoming more common the difference in the words shrinks. • Interoperability is a user driven requirement. • Especially in the defense and banking industries.

30. EMIS 7307 Overview What does it mean to integrate. • Data and data storage have a shared understanding. • Control: single string of control. • Presentation to the user - seamless and “feels” like it’s designed by one person.

31. EMIS 7307 Overview • Integration • Property of a relationship i.e. 2 or more entities. • Done well - a users perspective. • Done easily - an engineers perspective.

32. EMIS 7307 Overview • Interoperability • Much more than data and data exchange. • More will be required shortly after completion. • When a component evolves the interoperability of the whole must be maintained. • Can’t the same be said within a system? • If so what’s the difference in the two words? • Interoperability = cooperation = integration

33. EMIS 7307 Chapter 1 • Design Integration • The process that results in a design that appropriately includes the suitability (“ilities”) factors and assures that the various components of a system will work together synergistically and cooperatively. • I&T • A process of assembly of hardware and/or software components to create a system. The checking of the results (during the build-up) and fixing of problems is included.

34. EMIS 7307 Chapter 1 • Test • A form of verification that that gets data which can be used to demonstrate whether a certain parameter meets or could potentially meet it’s requirement. • Evaluation • The process of using data to determine whether a requirement has been met. May suggest areas to “fix” to bring the system into compliance.

35. EMIS 7307 Chapter 1 • What are systems? • Why are they so complex? • How do we handle complexity? • What is a “systems” approach? • What is a bottoms-up vs. top-down design approach?

36. EMIS 7307 Chapter 1 • What is ‘driving’ the need for more and better SE? See Fig 1.4 • Market (Changing requirements, competition etc) • Deliver now- fix it later • Complexity (Systems full of what were formerly systems, world-wide suppliers and customers) • How do we deal with complexity? • Subsystems • What process becomes harder with more complexity? I&T

37. EMIS 7307 Fig. 1.4

38. EMIS 7307 Chapter 1 • What historically bad practices does SE attempt to change? Why? M.E.s? E.E.s? • What is the most expensive time in a systems life cycle for making changes? • Later is almost always significantly worse. Fig 1.5 and1.8. • Look at Fig 1.7. What are the most often forgotten aspects of a system?

39. EMIS 7307 Fig 1.5

40. EMIS 7307 Fig. 1.8

41. EMIS 7307 Fig. 1.7

42. EMIS 7307 Chapter 1 • Look at Fig 1.2. Do you include these items when thinking of a system? • System life cycle. • From idea, to creation, to use, to disposal! • All phases contain consideration for SE! • Surprisingly all phases require I&T consideration too!

43. EMIS 7307 Fig. 1.2

44. EMIS 7307 Chapter 1 • System engineering identifying qualities. • Top down - viewing system as a whole. • Life cycle view. • “Complete” effort to identify system requirements “up-front”. • Interdisciplinary team approach.

45. EMIS 7307 Chapter 1 • Note the three perspectives in Fig 1.18. • Parallels from both sides of the V. Note Figure 1.19. • Although says for software I believe it’s really a system diagram i.e. substitute design engineering in place of software engineering. • Note how I&T considerations apply to every block.

46. EMIS 7307 Fig.1.18

47. EMIS 7307 Fig. 1.19

48. EMIS 7307 Chapter 1 • DOD 5000 version of Fig 1.26.

49. EMIS 7307 Fig. 1.26

50. EMIS 7307 Chapter 1 • Evolutionary development DOD.