UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`DAIMLER AG,
`Petitioner
`
`v.
`
`BLITZSAFE TEXAS,
`Patent Owner
`____________
`
`U.S. Patent No. 7,489,786
`
`“Audio Device Integration System”
`____________
`
`Inter Partes Review No. 2018-____
`
`DECLARATION OF PHILIP KOOPMAN, PH.D IN SUPPORT OF PETITION
`FOR INTER PARTES REVIEW OF U.S. PATENT NO. 7,489,786
`UNDER 35 U.S.C. §§ 311-319 AND 37 C.F.R. §§ 42.100 et seq.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 1 of 154
`
`Daimler Exhibit 1013
`
`

`

`TABLE OF CONTENTS
`
`Page
`
`
`
`
`
`BACKGROUND AND QUALIFICATIONS .................................................... 1
`I.
`ASSIGNMENT AND MATERIALS REVIEWED ........................................... 7
`II.
`III. Controller Area Network (CAN) and The 1991 Bosch CAN 2.0 Specification 9
`IV. Conclusion ........................................................................................................ 14
`
`i
`
`Page 2 of 154
`
`

`

`Ex. A
`
`Ex. B
`
`Ex. C
`
`Ex. D
`
`Ex. E
`
`Ex. F
`
`
`
`
`
`
`
`APPENDICES
`
`Curriculum Vitae of Dr. Philip Koopman
`
`Schill, J., “An Overview of the CAN Protocol,” Embedded
`Systems Programming, Sept. 1997
`Leen, G., et al.,“Digital Networks in the Automotive Vehicle,”
`Automotive Electronics, Jan. 2000
`Upender, B. & Koopman, P., “Embedded Communication
`Protocol Options,” Proceedings of Embedded Systems Conference
`1993, Santa Clara, pp. 469-480, October 1993
`18-549 Distributed Embedded Systems course outline
`
`18-540 Distributed Embedded Systems lecture notes
`
`
`
`iv
`
`Page 3 of 154
`
`

`

`I, Philip Koopman, do hereby declare and state as follows:
`
`I.
`
`BACKGROUND AND QUALIFICATIONS
`
`1.
`
`I am a tenured Associate Professor in the Electrical and Computer
`
`Engineering Department at Carnegie Mellon University. I have a B.S. (1982),
`
`M.Eng. (1982) and Ph.D. (1989) in Computer Engineering. I have been a professor
`
`at Carnegie Mellon since 1996. Prior to that time, I spent several years in the
`
`military and in industry working as a computer engineer and an embedded system
`
`engineer, including significant experience in the area of embedded networks. I am
`
`a named inventor on twenty-six patents, and an author or co-author of over 100 non-
`
`patent publications in a wide variety of fields within electrical engineering and
`
`computer science, including many in the technological area of embedded system
`
`networks. I have been working in computer engineering and embedded systems
`
`since approximately 1980.
`
`2.
`
`I have extensive experience in the field of embedded communication
`
`networks, including automotive networks. For example, I have been the instructor
`
`of the course “Distributed Embedded Systems,” taught to Carnegie Mellon seniors
`
`and graduate students almost every year from Fall 1999 to Fall 2015. This course
`
`includes several lectures dedicated to embedded network operation and
`
`performance, as well as lectures on more generalized embedded networking topics,
`
`including real-time scheduling, reliability, and system safety. The course features a
`
`1
`
`
`
`
`
`
`
`Page 4 of 154
`
`

`

`significant emphasis on automotive networks across a number of lectures. The
`
`course also features a semester-long distributed embedded system project in which
`
`we teach students to build a system that uses embedded network messages to
`
`coordinate operation of a distributed embedded system while guaranteeing that
`
`they can meet real-time deadlines over that network.
`
`3.
`
`I am also the instructor of the course “Dependable Embedded Systems,”
`
`which covers distributed computing and fault tolerance, including the role of
`
`embedded networks in safety-critical system design. I taught this course as part of
`
`a multi-year course rotation between Spring 1999 and Fall 2010.
`
`4.
`
`I have supervised a number of student independent projects and thesis
`
`projects involving embedded networks. As part of this work, my lab has owned and
`
`operated increasingly sophisticated hardware Controller Area Network (CAN)
`
`testbeds from approximately 1997 to approximately 2015, and applied those
`
`testbeds to automotive applications for research projects.
`
`5.
`
`Starting in 1999, I have been an external reviewer for at least 175
`
`embedded system design reviews of products for industry clients, many of which
`
`have included review of the use of embedded network protocols. I have further been
`
`involved in the network protocol selection process and related system architecture
`
`selection process for several embedded system companies in which network
`
`protocols were considered. I taught seminars on embedded network protocol
`
`
`
`2
`
`Page 5 of 154
`
`

`

`selection to attendees of the Embedded Systems Conference in 1993 and 1994.
`
`6.
`
`I served as the Guest Editor of a special edition of the magazine IEEE
`
`Micro titled “Critical Embedded Automotive Networks” in July-August 2002, which
`
`included automotive embedded network content.
`
`7.
`
`I am a named author on numerous papers that discuss or are relevant to
`
`embedded networks, including:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Koopman, Driscoll, Hall, "Selection of Cyclic Redundancy
`Code and Checksum Algorithms to Ensure Critical Data
`Integrity,” DOT/FAA/TC-14/49, March 2015.
`
`Koopman, P. & Szilagyi, C., “Integrity in Embedded Control
`Networks,” IEEE Security & Privacy, 2013.
`
`Szilagyi, C. & Koopman, P., “Low cost multicast authentication
`via validity voting in time-triggered embedded control
`networks,” Workshop on Embedded System Security, October
`2010.
`
`Koopman, P. & Ray, J., “Mitigating the Effects of Internet
`Timing Faults Across Embedded Network Gateways,”
`MMB/DFT 2010, p. 1, March 2010.
`
`Szilagyi, C. & Koopman, P., “A flexible approach to embedded
`network authentication,” DSN 2009, pp. 165-174.
`
`Ray, J. & Koopman, P., “Queue management mechanisms for
`embedded gateways,” DSN 2009, pp. 175-184.
`
`Maxino, T., & Koopman, P. “The Effectiveness of Checksums
`for Embedded Control Networks,” IEEE Trans. on Dependable
`and Secure Computing, Jan-Mar 2009, pp. 59-72.
`
`Driscoll, K., Hall, B., Koopman, P., Ray, J., DeWalt, M., Data
`Network Evaluation Criteria Handbook, AR-09/24, FAA, 2009.
`
`3
`
`
`
`
`
`Page 6 of 154
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Szilagyi, C. & Koopman, P., “A flexible approach to embedded
`network multicast authentication,” WESS 2008.
`
`Ray, J., & Koopman, P. “Efficient High Hamming Distance
`CRCs for Embedded Applications,” DSN06, June 2006.
`
`Paulitsch, Morris, Hall, Driscoll, Koopman & Latronico,
`“Coverage and Use of Cyclic Redundancy Codes in Ultra-
`Dependable Systems,” DSN05, June 2005.
`
`Koopman, P. & Chakravarty, T., “Cyclic Redundancy Code
`(CRC) Polynomial Selection For Embedded Networks,”
`DSN04, June 2004.
`
`Morris, J. & Koopman, P., “Critical Message Integrity Over A
`Shared Network,” FeT03, July 2003.
`
`Koopman, P., “Critical Embedded Automotive Networks,”
`IEEE Micro, July-August 2002.
`
`Koopman, P., Tran, E. & Hendrey, G. “Toward Middleware
`Fault Injection for Automotive Networks,” Fault Tolerant
`Computing Symposium, pp. 78-79, June 23-25, 1998.
`
`Koopman, P., “Tracking down Lost Messages and System
`Failures” Embedded Systems Programming, 9(11), October
`1996, pp. 38-52.
`
`Upender, B. & Koopman, P., “Communication protocols for
`embedded systems,” Embedded Systems Programming, 7(11)
`46-58, November 1994.
`
`Upender, B. & Koopman, P., “Embedded Communication
`Protocol Options,” Proceedings of Embedded Systems
`Conference 1993, Santa Clara, pp. 469-480, October 1993;
`repeated in Proceedings of Embedded Systems Conference East
`1994, Boston, April 1994.
`
`8.
`
`I have industry experience in embedded network protocol use and
`
`selection, specifically including embedded networks in elevators (Otis Elevator,
`
`
`
`4
`
`Page 7 of 154
`
`

`

`circa 1991-1995), jet aircraft engines (Pratt & Whitney, circa 1992-1995), and
`
`heating/ventilation/cooling systems (Carrier, circa 1995).
`
`9.
`
`I have been Principal Investigator or co-Principal Investigator on a
`
`number of sponsored research projects over the past two decades that directly
`
`involved the use or analysis of embedded network technology, including:
`
`
`
`
`
`
`
`
`
`
`
`
`
`General Motors Corporation, “Dependable Systems.” Full
`support for 1 to 3 students (varies by year) as one of four thrust
`area leaders in the CMU/GM research laboratory, including
`work with both CAN and FlexRay. (2000-2015)
`
`Bosch, “Intelligent Sensors.” Research on a CAN testbed.
`(2000-2001)
`
`Federal Aviation Administration (FAA), Evaluation Criteria for
`Databuses. (2005-2006)
`
`US Army TARDEC, “Safety Subsystem” task within contract
`for “Autonomous Platform Demonstrator (APD).” (2010)
`
`US Army, “Unmanned and Autonomous Systems Test (UAST)
`Science and Technology (S&T): A methodology for stress-
`testing autonomy architectures,” BAA W9000KK-09-R-0038
`topic #3. (2011-2016)
`
`FAA, “Software and digital systems program – data integrity
`techniques,” DTFACT-11-R-00002. (2011-2013).
`
`10.
`
`I have extensive experience in evaluating, selecting and using
`
`embedded network protocols in safety-critical systems. For example, I am a co-
`
`author of the Federal Aviation Administration’s Data Network Evaluation Criteria
`
`Handbook, already cited above, which sets forth evaluation criteria for embedded
`
`networks to be used in safety-critical flight control applications. The “Distributed
`5
`
`
`
`Page 8 of 154
`
`

`

`Embedded Systems” course I previously mentioned teaches students how to select
`
`an embedded network for a particular embedded system application, covering
`
`network options such as CAN and FlexRay in depth, and includes a discussion of
`
`other protocols specifically including LIN and J1850.
`
`11.
`
`I am a named inventor on the following patents that specifically address
`
`embedded control networks:
`
`
`
`
`
`
`
`U.S. Patent No. 5,535,212; “Implicit Token Media Access
`Protocol Without Collision Detection”; Koopman &
`Brajczewski,” filed on Jan. 31, 1994, issued on Jul. 9, 1996.
`
`U.S. Patent No. 5,450,404; “Explicit and Implicit Token Media
`Access Protocol with Multi-Level Bus Arbitration”; Koopman
`& Brajczewski, filed on Dec. 21, 1992, issued on Sep. 12, 1995.
`
`U.S. Patent No. 5,436,901; “Synchronous Time Division
`Multiplexing Using Jam-Based Frame Synchronization”;
`Koopman, filed on Feb. 25, 1994, issued on Jul. 25, 1995.
`
`12.
`
`I was the General Chair for the Dependable Systems and Networks
`
`Conference in 2008 (which is a first-ranked international academic conference on
`
`dependability, fault tolerance, and related topics including networked embedded
`
`system dependability). I was also Program Chair for the Dependable Computing
`
`and Communications Symposium (DCCS) of this same conference in 2012. I am a
`
`member of International Federation of Information Processing (IFIP) Working
`
`Group 10.4, an invitation-only organization of international researchers on the topic
`
`of Dependable Computing and Fault Tolerance that holds periodic
`
`workshops. These proceedings routinely address the topic of achieving safe and
`6
`
`
`
`Page 9 of 154
`
`

`

`reliable operation of distributed embedded networks and systems using such
`
`networks.
`
`13.
`
`I am a senior member of both the Institute of Electrical and
`
`Electronic Engineers and the Association for Computing Machinery. I am a
`
`member of the Society of Automotive Engineers (SAE International).
`
`14. Based on the above education and experience, I believe that I have
`
`a detailed understanding of the networking technology during the relevant
`
`period and, specifically, embedded networking.
`
`15. A copy of my curriculum vitae is attached hereto as Ex. A.
`
`II. ASSIGNMENT AND MATERIALS REVIEWED
`
`16.
`
`I submit this declaration in support of the petition for Inter Partes
`
`Review of U.S. Patent No. 7,489,786 (“the ‘786 patent”) submitted by Petitioner.
`
`17.
`
`I am not an employee of Daimler or of any affiliate or subsidiary
`
`thereof.
`
`18.
`
`I am being compensated for my time at my customary rate of $595
`
`per hour.
`
`19. My compensation is in no way dependent upon the substance of
`
`the opinions I offer below, or upon the outcome of Daimler’s petition for Inter
`
`Partes review (or the outcome of the Inter Partes review, if trial is instituted).
`7
`
`
`
`
`
`
`
`
`
`
`
`Page 10 of 154
`
`

`

`20.
`
`I have been asked to provide certain opinions relating to the
`
`patentability of the ’786 patent. Specifically, I have been asked to provide
`
`opinions related to various aspects of the Bosch CAN 2.0 specification,
`
`including my opinions regarding (i) whether a publication entitled “BOSCH
`
`CAN Specification Version 2.0,” Ex. 1011, was publicly available before
`
`December 2002 to those of skill in the art and (ii) Ex. 1011 is an authentic copy
`
`of that specification.
`
`21. For the reasons set forth below, it is my opinion that the Bosch 2.0
`
`specification was published in approximately 1991, and was publicly available
`
`by at least 1993, but in any event was publicly available no later than October
`
`of 2001. It is my further opinion that the copy of the Bosch CAN specification
`
`Ex. 1011 is a true and correct copy of the version that would have been
`
`available before December, 2002.
`
`
`
`8
`
`Page 11 of 154
`
`

`

`
`
`
`
`
`III. Controller Area Network (CAN) and The 1991 Bosch CAN 2.0
`Specification
`
`22. By the late 1990s, the Controller Area Network (CAN) protocol was
`
`well established. A commonly used version of the CAN specification, was the
`
`Bosch CAN Specification Version 2.0 from 1991 (Ex.1011), which was initially
`
`targeted for use by the automotive industry.
`
`23. As I describe in more detail below, Ex. 1011 came from my personal
`
`archives, which based on personal knowledge, I downloaded at least in October of
`
`2001, cited in publicly available conference papers I authored before 2001, and
`
`used as suggested readings in courses I taught in the Fall of 2001.
`
`24.
`
`I know from personal experience that, by the late 1990s, CAN chips
`
`were being made by many companies, and the use of CAN had spread beyond
`
`automotive and had become widespread use in industrial applications. This is
`
`supported, for example, by Schill, J., “An Overview of the CAN Protocol,”
`
`Embedded Systems Programming, Sept. 1997. Ex. B. As another example, Leen
`
`notes that “[i]t is estimated that there are already over 140 million CAN nodes
`
`installed worldwide” by 1999, with “the majority of CAN applications exist[ing]
`
`outside of the automotive industry, employed in numerous other applications
`
`ranging from farm machinery to photocopiers.” Ex. C at 6. I have personal
`
`knowledge that Schill was publicly available before the priority date of the ’786
`9
`
`Page 12 of 154
`
`

`

`patent because, among other reasons, it was required reading for a course lecture I
`
`taught in October 2001.
`
`25. Compelling reasons for CAN’s popularity were its suitability for real-
`
`time applications and its relatively low cost, with CAN chips costing perhaps two
`
`dollars ($2) to four dollars ($4). See, e.g., Ex. B at p. 2. But the cost was also lower
`
`because its adoption by the automotive industry led to broad market appeal, which
`
`in turn led to cost reduction via high-volume production. See, e.g., id.
`
`26. Version 2.0 of Bosch’s CAN specification (Bosch, CAN Specification
`
`Version 2.0, Robert Bosch GmbH, Stuttgart, 1991 at A-6 (the “Bosch CAN
`
`Specification, version 2.0”)) is attached at Ex. 1011.
`
`27. Ex. 1011 is the specification for the Controller Area Network
`
`protocol. Version 2.0 of this specification was first published in 1991, and further,
`
`the copy attached at Exibit 1011 is a true and correct copy of version 2.0 that was
`
`first published in 1991. I have personal knowledge that the Bosch CAN
`
`Specification, version 2.0 was publicly available before the filing date of the ’786
`
`patent (which I am informed is December, 2002) because, among other reasons, I
`
`used it as a reference in papers I wrote prior do that date. Indeed, the 2.0 version
`
`of the specification was well-known to those of ordinary skill in the art related to
`
`the ’786 patent, and was publicly available to anyone interested in the specification
`
`at Bosch’s web site.
`
`
`
`10
`
`Page 13 of 154
`
`

`

`28. Moreover, I used and cited version 2.0 of the Bosch CAN
`
`specification attached at Ex. 1011 in Upender, B. & Koopman, P., “Embedded
`
`Communication Protocol Options,” Proceedings of Embedded Systems Conference
`
`1993, Santa Clara, pp. 469-480, October 1993 (“Upender & Koopman”) (e.g., it is
`
`reference 14 in Ex. D, which I co-authored) as well as in my teaching. Ex. D was
`
`publicly available via being given to attendees and additionally via publicly
`
`available purchase from the conference organizers in 1993, and was a well-known
`
`resource to anyone interested in automotive computer technology. Additionally, as
`
`author I know that I made the contents of this paper (Ex. D) publicly available via
`
`the Carnegie Mellon University Web site as of January 18, 1997.
`
`29. Moreover, I know from personal experience that Ex. 1011 was
`
`publicly available because I cited it in another of my publications, see, e.g.,
`
`Koopman, P., “Control Area Network,” 18-540 Distributed Embedded Systems on-
`
`line lecture notes (“Koopman”) (Ex. F at 1,16), which I know as the author, I made
`
`publicly available via Carnegie Mellon University ECE’s Department web site on
`
`or before October 4, 2000. The Carnegie Mellon University’s ECE department’s
`
`web site was a well-known, publicly available website, and was well-known to
`
`those in the field related to the ’786 patent, and would have been a well-known,
`
`and readily available resource.
`
`30.
`
` I also am personally aware that the Bosch 2.0 CAN specification was
`
`
`
`11
`
`Page 14 of 154
`
`

`

`publicly available because I taught a course in Fall 2001 at CMU that used this
`
`specification. The course was 18-549 Distributed Embedded Systems (a re-
`
`numbered but substantially similar course to 18-540 referenced above), and I
`
`posted the updated course materials that including a link to the Bosch CAN 2.0
`
`specification no later than October 8, 2001. It is my normal practice to create an
`
`archive (zip file) of course materials each semester, and I was able to find and refer
`
`to the archive for that semester for the below information.
`
`31. One of the course web pages was a list of references for students to
`
`use. That web page with the list was publicly visible to the public Internet (not just
`
`Carnegie Mellon University) via the university’s web site and, indeed, anyone of
`
`ordinary skill in the art related to the ’786 patent could be expected to have been
`
`aware of that web site. I am personally aware that others of ordinary skill in the art
`
`were in fact aware of the course materials for that site, as I was personally aware of
`
`other professors’ course materials from other Universities. In any event, the Bosch
`
`CAN specification was publicly available not only by virtue of my posting it in my
`
`course materials, but by virtue of the fact that I posted a link that was publicly
`
`available and accessible to anyone of ordinary skill in the art (indeed, I had no
`
`problem locating the specification and referencing it for my students). A copy of
`
`that web page is attached at Exibit E.
`
`32.
`
`I assigned suggested reading for lecture #11 as the Bosch CAN
`
`
`
`12
`
`Page 15 of 154
`
`

`

`specification. At that time the specification was publicly available at:
`
` http://www.bosch.de/de_e/productworld/k/products/prod/can/docu/can2spec.pdf
`
`I know this because I have a web page from my Fall 2001 course that has this URL
`
`as the external URL to obtain the CAN specification, and it is my normal practice
`
`to ensure that those links work properly. Since it is suggested reading, my normal
`
`practice would have been to put that link in place on or before the date of the
`
`lecture, which was October 8, 2001.
`
`33. Additionally, that same course web page points to a local copy with
`
`the file name: bosch91_canspec.pdf. I have an archived copy of that file with a date
`
`stamp of: October 5, 2001. That date is correct because it was (and is) my normal
`
`practice to keep an accurate date on my computer and use an operating system that
`
`I have observed to consistently record correct dates when saving files. It also
`
`checks with the lecture timeline as having been set up three days before the
`
`October 8, 2001 lecture.
`
`34.
`
`It was (and is) also my practice to download a file from the public URL
`
`indicated and save it as a local copy for use by students in case of an internet access
`
`problem at the last minute before homework assignments are due. Therefore, I am
`
`sure that this file, which is Ex. 1011 is a true and accurate copy of the file that was
`
`available from Bosch at the above URL on or before October 5, 2001.
`
`35. Moreover, in preparing this declaration I also located a copy of a
`
`
`
`13
`
`Page 16 of 154
`
`

`

`substantially identical CAN specification (with some addendum material) at
`
`archive.org,
`
`publicly
`
`available
`
`as
`
`of
`
`June
`
`2001.
`
`
`
`See
`
`https://web.archive.org/web/20010612044724/http://www.bosch.de:80/de_e/produ
`
`ctworld/k/products/prod/can/docu/can2spec.pdf. I have used archive.org on
`
`numerous occasions and have found that it is a reliable source of archived materials.
`
`This further corroborates that Ex. 1011 is the same specification I saved on my hard
`
`drive.
`
`36. Based on my industry experience and on my personal knowledge, those
`
`of ordinary skill in the art at least as early as 1993 were very well-aware of the Bosch
`
`2.0 specification through its prolific use in the industry, and would have found the
`
`specification readily available and accessible at least before December, 2001.
`
`37. Based on all of the above, it is my opinion that Ex. 1011 was publicly
`
`available in approximately 1991, and at least before December, 2002 and that Ex.
`
`1011 is a true and correct copy of the version of what was available at that time.
`
`IV. Conclusion
`
`38.
`
`I declare that all statements made herein of my own knowledge are true
`
`and that all statements made on information and belief are believed to be true, and
`
`further that these statements were made with the knowledge that willful false
`
`statements and the like so made are punishable by fine or imprisonment, or both,
`
`under Section 1001 of Title 18 of the United States Code.
`
`
`
`14
`
`Page 17 of 154
`
`

`

`
`
`________________________
`Signature: Philip Koopman
`
`Dated: 6 June 2018
`
`
`
`
`15
`
`Page 18 of 154
`
`

`

`EXHIBIT A
`
`EXHIBIT A
`
`Page 19 of 154
`
`

`

`Philip Koopman
`Associate Professor, Electrical and Computer Engineering
`Carnegie Mellon University
`
`
`1. Biographical Data
`
`1.A. Name
`Philip Koopman
`
`1.B. Citizenship
`US Citizen by birth
`
`1.C. Education
`
`Degree
`
`
`
`
`
`
`
`
`
`
`
`
`
`M.Eng.
`
`
`
`Ph.D.
`
`
`
`
`
`
`
`B.S.
`(Magna cum Laude)
`
`
`
`
`Date
`University
`
`
`Discipline
`_________________________________________________________
`
`Computer Engineering
`
`
`
`
`
`Rensselaer Polytechnic
`Troy, NY
`
`Computer Engineering
`
`
`
`
`
`Rensselaer Polytechnic
`Troy, NY
`
`Computer Engineering
`
`
`
`
`
`Carnegie Mellon
`Pittsburgh, PA
`
`1982
`
`1982
`
`
`1989
`
`
`
`
`
`
`
`1.D. Positions
`
`Submarine Officer. United States Navy, USS Haddock (SSN-621), U.S. Pacific Fleet.
`1983-1985
`Sonar Officer and Weapons Department Head aboard nuclear-powered fast attack submarine.
`Responsible for operation and maintenance of on-board sonar and target tracking computer systems;
`watch standing; supervising 25 men. Awarded Naval Achievement Medal, Naval Expeditionary
`Medal, and Sea Service Ribbon. Official combat veteran status for participation in the Cold War.
`Engineering Duty Officer. United States Navy, Trident Command and Control Systems
`1985-1987
`Maintenance Activity (TRICCSMA), Newport, RI.
`Deputy Department Head in charge of Systems. Project management and technical consultation for
`submarine computer systems. Led research and development in embedded system prototyping,
`system certification, and configuration management.
`Startup Founder. WISC Technologies Inc., La Honda, CA.
`1984-1990
`Co-Founder/Chief Engineer. Conducted computer technology research and development as the
`technical half of a two-person startup company. Developed, prototyped, and patented an embedded
`CPU design; negotiated a technology license to Harris Semiconductor. (This was concurrent with my
`time in the Navy, my time as a Ph.D. student, and my time at Harris Semiconductor.)
`Senior Scientist. Harris Semiconductor, Melbourne, FL.
`1989-1990
`Chief architect for Real Time Express (RTX) family of embedded control microprocessors, reporting
`directly to VP of Processors. Technical contributions to CPU design, architectural tradeoffs,
`simulation, compiler optimization, and product roadmaps.
`
`
`
`Philip Koopman
`
`June 2018
`
`
`
`
`
`1
`
`Page 20 of 154
`
`

`

`Principal Research Engineer. United Technologies Research Center, East Hartford, CT.
`1991-1995
`Team leadership, technical contribution, and research planning at corporate R&D center.
`Contributions in embedded communications, embedded processor applications, system design
`methodologies, discrete event simulation, and cryptographic security. Application areas included
`elevators (Otis), large-scale air conditioning (Carrier), automobiles (UT Automotive), jet engines
`(Pratt & Whitney, Hamilton Standard), Radars/Sonars (Norden), and helicopters (Sikorsky).
`Visiting Senior Research Engineer. Engineering Design Research Center, Carnegie
`1996-1997
`Mellon University, Pittsburgh, PA.
`Team leadership and technical contributions in wearable computers, automated highway systems, and
`embedded system reliability. Visiting Associate Professor at CMU ECE department.
`Assistant Professor. Electrical and Computer Engineering Department, Carnegie
`1997-2001
`Mellon University, Pittsburgh, PA.
`Research and teaching in affordable dependability, embedded computer systems, and computer
`architecture. Major projects: Ballista, Amaranth, RoSES, Automated Highway Systems. Also
`Embedded and Reliable Information System thrust leader for the Institute for Complex Engineered
`Systems.
`Associate Professor. Electrical and Computer Engineering Department, Carnegie
`2001-…
`Mellon University, Pittsburgh, PA. (See Assistant Professor description above for details.)
`Granted tenure effective July 1, 2002 at the rank of associate professor. Dependable Embedded
`System thrust leader for GM/CMU Vehicular Technology Collaborative Research Lab through 2015.
`Principal Investigator for Stress Test for Autonomy Architectures project and follow-ons at the
`National Robotics Engineering Center. Courtesy faculty member of Robotics Institute, and Institute
`for Software Research.
`Co-Founder. Edge Case Research, LLC, Pittsburgh PA
`2014-…
`Start-up company for robotic and embedded system software robustness testing tools and techniques.
`
`1.E. Technical Consulting Engagements
`1996-1999
`United Technologies Automotive, Intellectual Property Department. Dearborne, MI
`48126. Client: Phil LeMay. (Company now part of Lear Corp.)
`Support of patent application and evaluation of intellectual property positions (e.g., technical
`evaluation of possible patent infringement) for automotive applications. Additionally, technical
`support and training for their low-cost cryptographic security technology.
`July 1999
`AT&T Laboratories, Florham Park, NJ. Client: Yennun Huang.
`Dependable distributed system architecture, testing, and hardening techniques.
`1999-2003
`Adtranz/Bombardier, West Mifflin PA. Client: Tom Lemak/Bob DiSilvestro
`Technology assessments and design reviews for various aspects of train and peoplemover systems.
`Taught advanced embedded systems course to 30 ADtranz employees in Spring 2001 & Spring 2002.
`1999-…
`Emerson Electric, St. Louis MO & Pittsburgh, PA. Client: Bill Trosky
`Technology assessments and design reviews at various Emerson business units, including ASCO
`(power control), ASTEC (central switch emergency power; power supplies), Avocent (data center
`infrastructure), Branson (ultrasonic welding), Brooks (flow meters), Climate Control, Copeland
`(compressors; manufacturing
`tests), CPC (HVAC equipment), CSI (adaptive maintenance
`monitoring), Daniel/DeltaV (critical process flow meters, process monitoring and control), Dent
`Instruments (power meters; Emerson supplier), EC&P (power supplies; embedded computer boards),
`EMC (motion controllers), Emerson Network Power China (data center infrastructure), Fisher (flow
`control), HIROSS (compressors), Intermetro (medical carts), Kato (machinery monitoring),
`
`
`
`Philip Koopman
`
`June 2018
`
`
`
`
`
`2
`
`Page 21 of 154
`
`

`

`Krautkramer (ultrasound inspection), Liebert (large UPS systems), Marconi (large power supplies),
`MicroMotion (Coriolis flow meters), Moobella (ice cream machines; Emerson partner), NetSure (DC
`power systems); Network Power (telecomm power regulation; safety-critical computers), Power &
`Water Solutions (power generation), Remote Automation Solutions (SCADA and controls), Ridge
`Tools (small tool control), Rosemount (chemical process instrumentation devices, networks &
`security), Tekmar (sample processing automation), Therm-O-Disc (temperature controllers;
`automotive components), White Rodgers (thermostats), and others. Principal author of Emerson
`corporate software review risk screening process.
`2000
`
`Gravitate, San Francisco, CA. Client: Geoff Hendrey
`R&D for wireless telephony location-aware applications.
`
`Verizon, Bedminster, NJ.
`
`2001
`Evaluation of wireless base station computers in context of evolution from analog to digital cell
`phone system network.
`
`ABB Corporate Research, Baden, Switzerland. Client: Hubert Kirrmann
`2001-2002
`Embedded network protocol reviews for next-generation critical embedded systems.
`
`Lutron, Allentown PA. Clients: J.P. Steiner, W. Zaharchuk
`2001-…
`Evaluation of several embedded network protocols for integrated lighting systems
`
`DirecTV, El Segundo, CA.
`
`2002
`Evaluation of piracy technology with respect to smart-card based security systems.
`
`Ingersoll Rand.
`
`2003
`Embedded design tutorial.
`
`ThyssenKrupp Elevator, San Diego, CA.
`2003-2007
`Architectural definition of elevator system product families.
`
`FlexRay Consortium.
`
`2004
`Embedded network protocol analysis.
`
`Violin Technologies, New Jersey
`
`2006
`Tailored CRC polynomial selection for startup company.
`
`John Deere Co.
`2008-2009
`Embedded system security
`
`Residential Control Systems
`
`2011
`Thermostat software and hardware design review
`
`Google Inc.
`2011-2013
`
`Topic area: Embedded system design.
`
`Barr Group, LLC
`2014-2015
` Design review team member and other embedded system consulting assignments. Assignments to
`date include: MTD (lawnmowers).
`
`
`2014-2015
`
`The National Transportation Systems Center (Volpe).
`
`
`
`Philip Koopman
`
`June 2018
`
`
`
`
`
`3
`
`Page 22 of 154
`
`

`

`Future automotive software safety standards analysis and recommendations to NHTSA.
`
`
`
`
`
`
`2014-…
`Chief Technologist & Startup Co-Founder, Edge Case Research LLC, Pittsburgh PA.
`
`Commercialization of robust embedded software services. Consulting for multiple clients including
`government, startup companies, and Fortune-500 companies.
`
`
`
`
`
`
`
`
`
`
`
`
`
`Philip Koopman
`
`June 2018
`
`
`
`
`
`4
`
`Page 23 of 154
`
`

`

`2. Teaching and Education
`
`2.A. Courses Taught at CMU
`
`Semester Number Course Title
`
`Fall 97
`
`18-742
`
`Fall 98
`
`Fall 99
`
`18-540
`
`Fall 00
`
`Fall 01
`
`Spring 02 18-749
`
`Fall 02
`
`Number
`of
`Students
`
`Joint
`Faculty
`
`Hours/
`Week
`
`4 hours;
`12 units
`4 hours;
`12 units
`4 hours;
`12 units
`4 hours;
`12 units
`5 hours;
`12 units
`4 hours;
`12 units
`5 hours;
`12 units
`
`N/A
`
`N/A
`
`N/A
`
`N/A
`
`N/A
`
`N/A
`
`N/A
`
`N/A
`
`N/A
`
`Priya
`Narasimhan
`
`27
`
`26
`
`31
`
`13
`
`33
`
`13
`
`33
`
`12
`
`35
`
`22
`
`36
`
`FCE
`Score
`Instructor
`(out of 5)
` 3.85
`
`FCE
`Score
`Course
`(out of 5)
` 3.77
`
` 4.65
`
` 4.70
`
` 4.68
`
` 4.64
`
` 4.75
`
` 4.92
`
` 4.59
`
` 4.92
`
` 4.41
`
` 4.92
`
` 4.72
`
` 4.72
`
` 4.91
`
` 4.91
`
` 4.