The coming revolution in the $4B Test & Measurement industry that will change the world.

1. of an industry
Revolution
the
that will change
the
World
Test & Measurement

2. change the world?!?
we are
obviously
CRAZY
.. .right?
YZ

3. how could an industry you likely
never heard of possibly
change the world??

4. stick with us,
we will explain
✔
what “Test & Measurement” is
✔
why you should give a damn
✔
how a revolution in a historically boring
industry will bring fascinating change

5. a long time ago
someone built
somethingO O
complex
and it didn’t work as expected

6. they needed to figure out
what was wrong

7. swapping parts and guessing
just wasn’t cutting it

8. along came someone with an
instrument that could “test” and
“measure” the pieces and parts of
that complex something

9. the right tool made
troubleshooting tons easier and
saved a lot of
time

10. the concept of Test &
Measurement was born
(more on the history of Test & Measurement as an industry in a bit)

11. why should anyone
care about Test &
Measurement?

12. $113 billion
identifying & correcting product defects
in the US,
is spent every year

13. let’s put $113 billion into context
~~

14. with $113 billion, you could
~~
end world hunger ($30B)
and buy
$30B $10B $4B $4B $4B
$4B $3.3B $2.5B $2B $2B
and still have $17B left

15. we sense your skepticism.
$113B is an unbelievably big number!
what exactly is that being spent on?

16. the average engineer spends
1,500 hours / year fixing product bugs!!
~~

17. that’s 75% of our work time!
that means 75% of your engineering
team salary goes to fixing product bugs!

18. oh wait, you thought we spent most of
our time designing cool stuff?

19. wrong!!
there are 100 bugs per 1,000 lines of
development code.
engineers spend most of their time
finding and fixing these bugs!

20. $time is expensive during
product development

21. $113Badd up 75% of all of the product
engineering salaries across the US plus
the cost of all of the debug tools they use

22. this does not even include the $$$ you
lose when your product launches late b/c
of those pesky bugs
$113B+

23. and this is why Test & Measurement matters –
a $4B industry (today) directly affecting $113B+
$

24. a history lesson

25. the invention of the
integrated circuit in the
1950s set the stage for the
electronics revolution

26. thousands of small parts
joined together by
invisible voltages,
currents, and connections

27. how do you troubleshoot a
complex circuit if you can’t “see”
the things that make it work??

28. back in 1946, C. Howard
Vollum and Melvin
“Jack” Murdock invented
the world’s first time
based triggered
oscilloscope

29. an oscilloscope uses probes to capture
voltages in a circuit and turn them into
waveforms that you can “see”

30. big problem
meet
big solution

31. by the mid-1960s, Tektronix was booming
as it dominated the o-scope market and
Test & Measurement became a high-
growth industry*
* in the 1940s and 1950s, Test & Measurement was a much smaller industry
primarily focused on tools for testing communications, audio, and video equipment

32. the 1970s welcomed the explosion of
digital systems, microprocessors, and
inexpensive memory

33. o-scopes are great at capturing a lot of
detail for a short period of time
(i.e. they are good for debugging “analog” systems)

34. but they suck at debugging digital data
~~(digital debug requires capturing a LOT of 1s and 0s over time)

35. in 1973, Hewlett-Packard introduced the logic
analyzer, designed for digital system debugging
probe and capture large amounts of
digital data, program trigger events
that initiate capture, view digital
data as waveforms

36. for 30 years, the Test & Measurement
industry was dominated by
oscilloscopes and logic analyzers

37. for 30 years, the probe was the
product engineer’s debug tool of choice

38. in the early 2000s, Test
& Measurement began
to completely
change . . . and no one
was talking about it
(especially those companies who had
dominated the market for 30 years)

39. Marc Andreessen once predicted that
“software will eat the world”

40. started to eat
software
hardware

41. the
riseof powerful system-on-chips (SoCs)
fallof memory and silicon prices
the 2000s brought
the

42. it was practical for us to put powerful processors
and lots of memory inside our hardware products

43. we made our simple products substantially more
complex, like giving them a brain

44. these “smart”
products could
execute lots of
complex code fast

45. software/firmware
bugs
became the biggest obstacle in
the # of
product development

46. o-scopes and analyzers grew dusty b/c
they were not built for software/
firmware debug

47. what tools were we using for debug?

48. embedded processor debuggers were the tool of
choice for firmware developers b/c they could stop
the processor and step through code

49. but what did non-firmware
engineers use for debug?

50. how did we debug if we did not have
physical access to the main circuit board to
plug in one of these debuggers?

51. how did we debug in-the-field?

52. the rise of the log file

53. a log file is like a journal
of what happened inside
a product

54. if software can detect it,
software can “log” it

55. log files give us the
ability to “see” what
software is doing

56. log files were a big hit
every product has a free,
built-in “debugger”Z
log files are super-easy &
super-fast to useZ
just retrieve it and read it

57. if given the choice between using an
o-scope/analyzer or a log file, what
wins 99% of the time?

58. the easier and faster tool

59. this is the part where we let you in
on a little secret about engineers

60. we don’t enjoy using o-scopes and
analyzers - they take too long to setup
and the usability sucks

61. we don’t like sticking metal probes
inside of products that are running

62. blowing up a $150,000 prototype
because you stuck a probe in the
wrong place changes you

63. product development has become
more software-centric
&the # of bugs to fix before
product launch is exploding
today,

64. o-scopes & analyzers are no longer the
center of the Test & Measurement universe

65. Test & Measurement Today (2014)
log files
used by all types of engineers a lot
o-scopes / analyzers
used by electrical engineers only when necessary
embedded processor debuggers
used by coders when practical

66. there are big problems with
the current approach to debug
!

67. software (log files) can’t
“see” everything we need
for product debug

68. there are times we need to capture
raw hardware signals at a high rate
of speed, something log files can’t do

69. for example,
what if software tells a pin to turn “on” but that
pin is grounded “off” due to a hardware defect?
a software log can’t see this problem!!

70. there are times we want to use log files
but need to use o-scopes/analyzers

71. what tool do we use to debug the issues
where software and hardware intersect?
hardware software
signals events

72. it’s a hardware
problem
it’s a software
problem

73. these problems cost an unreal amount of
time
and
$$$

74. these problems cost an unreal amount of
the revolutions
are coming

75. we need
tools that give us instant access to
anything going on inside our products~~
~~

76. we need
tools that are super-easy and
super-fast to use
~~
~~

77. we need
tools that help us quickly understand
the data we capture~~

78. we need
the power of scopes & analyzers and
the efficiency of log files~~
~~

79. the power of scopes & analyzers and
the efficiency of log files
we need
~~
built inside every product made
~~
~~

80. the embedded instrument
revolution

81. Moore’s Law has driven the size
of transistors in ICs smaller and
smaller and smaller . . .

82. silicon real estate has become so
cheap, it is common to find
unused silicon inside today’s ICs*
* a pad-limited IC cannot be shrunk any further because there would not be
enough room for the bonding pads used for I/O pins on the outer perimeter of the
die, leaving unused silicon areas within the die itself

83. embedded instrumentation is the
concept of inserting the
capabilities of external test
equipment inside ICs

84. embedded instruments are
controlled by a laptop, mobile
device, etc.

85. the power and functionality of your o-scope /
analyzer shrunk down and placed inside the
IC that was already going into your product

86. ~~
for a growing # of
today’s ICs, the
additional cost for
adding an embedded
instrument is
$0

87. it gets even better!!

88. embedded instruments can do things
scopes and analyzers could never do
(no, not this)

89. b/c they are inside the same IC that
contains the microprocessor, embedded
instruments can capture hardware signals
and software events, at the same time
hardware software
signals events

90. your scope, analyzer, and software
logger rolled into one

91. ~~
except, there are no probes
you won’t need them

92. the connected
revolution

93. from 10 billion web connected devices today,
to 212 billion connected devices by 2020

94. the ip address will replace the probehttps://192.168.0.1

95. instantly access and troubleshoot
web-connected products~~

96. from anywhere

97. the software
revolution

98. the future of debug is in the cloud

99. web software will collect data from
web-connected products

100. smart platforms will know what
type of data was collected
and deliver powerful,
customized visualizations
log visualization-
as-a-service

101. BIG DATAbillions of web-connected devices
producing trillions of data points

102. instantly available at the click of a button
information
answers
insights

103. why this matters

104. new product development
will happen significantly faster
~~

105. better tools will remove a
barrier to technology
advancements

106. service industries will
completely change
imagine your next generation repairman
remotely logging into your appliance and telling
you what is about to break before it breaks
~~

107. the financial and global
impact will be profound
~~

108. the solutions to today’s Test &
Measurement problems are going to open
doors of possibilities that will disrupt
industries, spawn new markets, and
accelerate technology advancements

109. https://www.initialstate.com
tools built for engineers, by engineers

110. Sources:
http://www.ibm.com/developerworks/rational/library/4995.html
Watts S. Humphrey, A Discipline for Software Engineering, Addison Wesley, 1996
Philip B. Crosby, Quality Is Free. Penguin, 1980
http://sqgne.org/presentations/2011-12/Jones-Sep-2011.pdf
http://www.crosstalkonline.org/storage/issue-archives/2005/200504/200504-
Jones.pdf
http://inventionmachine.com/the-Invention-Machine-Blog/bid/87840/What-Are-
Late-New-Product-Launches-Costing-You
http://www.bls.gov
http://oakstonepartners.com