| David Iverson |
|
|
| Sep 30 2007 | |
|
Page 1 of 3 Computer Scientist, NASA’s Ames Research Center, Moffett Field, CA
NASA Tech Briefs: How long have been with NASA and what were some of the projects you worked on prior to getting involved with the Inductive Monitoring System? David Iverson: I started with NASA as a co-op student back in 1985, so I’ve been here a while. I spent a lot of that time working in health monitoring, automated diagnosis, artificial intelligence, things like that. And I’ve been involved, on and off, in space applications. I did some space shuttle payload monitoring applications a while back. Aeronautical applications, looking at helicopters and some of the jet aircraft that NASA has, and mission control types of applications. A little bit of everything that NASA is involved with that might benefit from system health monitoring. NTB: How does the Inductive Monitoring System work? After that you can feed IMS real-time data coming from the system or look at other archived data and compare it to the model or characterization that you’ve built. IMS will give you an indication – hey, this looks like it has before, the system behavior hasn’t changed, or it might deviate somewhat from what you’ve seen before. You can think of the output from the IMS as a sort of a distance from what we expect to see from a normally operating system. A small distance means your system is looking like what we expect from the training data. If that distance number increases you’re moving farther and farther away from what you expect, from what you’ve seen before, and that could be an indication that something is not working quite right in your system and you should probably check things out. |



















