| Computer-aided Maintenance |
Article Index for Computer-aided |
Website Links For Maintenance |
Information AboutComputer-aided Maintenance |
| CATEGORIES ABOUT COMPUTER-AIDED MAINTENANCE | |
| help desk | |
| product lifecycle management | |
| computer systems | |
|
The first computer-aided maintenance software came from DEC in the 1980s to configure VAX computers. The software was built using the techniques of Artificial Intelligence Expert System s, because the problem of configuring a VAX required expert knowledge. During the research, the software was called ''R1''. As one of the first expert systems to be pressed into commercial service, renamed '' XCON '', it created high expectations, which did not materialize, as DEC lost commercial pre-eminence. But, fundamentally, ''XCON'' was a rule-based Configuration Database . The expert system used Forward Chaining rules. Reference: Virginia E. Barker and Dennis E. O'Connor. Expert systems for configuration at Digital: XCON and beyond. Communications of the ACM, 32(3):298--318, March 1989. HELP DESK SOFTWARE Help Desk Software frequently captures Symptom s of a Bug and relates them to fixes, in a Fix Database . One of the problems with this approach, is that the understanding of the problem is embodied in a non-human way, so that solutions are not unified. STRATEGIES FOR FINDING FIXES #The ''bubble-up'' strategy simply records pairs of symptoms and fixes. The most frequent set of pairs is then presented as a tentative solution, which is then attempted. If the fix works, that fact is further recorded, along with the configuration of the Presenting System , into a Solutions Database . #Oddly enough, shutting down and Booting up again manages to 'fix' (or at least 'mask' a bug) in many computer-based systems; thus ''reboot'' is the remedy for distressingly many symptoms in a 'fix database'. #Currently, most expertise in finding fixes lies in human domain experts, who simply sit at a replica of the computer-based system, and who then 'talk through' the problem with the client to duplicate the problem, and then relate the fix. |
|
|