Developing Data-Input Standards for Computerized Maintenance Management Systems Summary of a Symposium/Workshop (1994) / Chapter Skim
Currently Skimming:
PROPOSED ELECTRONIC MAINTENANCE DATA INPUT STANDARDS - LEVEL ONE
PROPOSED ELECTRONIC MAINTENANCE DATA INPUT STANDARDS - LEVEL ONE
Pages 26-34
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 26... ...
Computerized Maintenance Management Systems (CMMS) have been developed to overcome some of these problems by gathering operation and maintenance information together into a unified data library which can be made available throughout an organization via networked computer terminals.
|
From page 27... ...
PROPOSED STANDARD - LEVEL ONE: Operation and maintenance information will be provided in an electronic master file, with associated graphic and database files, and an optional menu file. MASTER FILE: Basically, the master file is the current instruction manual in straight ASCII format, with header information and links to graphics and/or database tables, if any, designated according to the procedural rules below.
|
From page 28... ...
Optionally, warning text between the embedded codes may be right and left indented and/or enclosed within an ASCII line drawing box to further draw attention to it. Developer Requirements: CMMS software shall read embedded warning codes and display the enclosed text in a warning color.
|
From page 29... ...
Developer Requirements: CMMS software shall read parameters in navigational embedded codes and display the corresponding navigational information on the screen, even as the mam body of the text scrolls. CMMS software shall create a document map or Table of Contents from the navigational codes, to a user specified level of detail (e.g., 2 or 3~.
|
From page 30... ...
Developer Requirements: CMMS software shall read parameters in embedded Redefined files codes as user scrolls through the master file. Software shall define a hotkey or mouse pick to activate the display of the currently active file through an appropriate viewer.
|
From page 31... ...
Insert proper embedded code at the appropriate place within the master file. Developer Requirements: CMMS software shall read parameters in embedded executable external file codes as user scrolls through the master file.
|
From page 32... ...
activities to be performed link to external file with text description - include activity level number parameter e.g., @@txt:maintfil 3@@ Parts List part description manufacturer's number manufacturer activity level number (link to maintenance schedule) view file name (@@DXF:explodia 12456@@)
|
From page 33... ...
The first 9 menu items may be standardized, such as: eXit - leave program Help - displays help information by developer GoTo - brings up submenus, including table of contents created from @@NAVx lines and list of figures/executables from other @@ display/execute lines also,: dump to line number and option to change NAVx level displayed. Key - hotkey toggles to currently active shell activity Find - requests text string to find, not case sensitive Edit - brings up editing submenu grayout toggle redline editing BM - toggles book mark, if on line with bookmark, erases it; otherwise sets a mark +BM - zooms to the next book mark (NOTE)
|
From page 34... ...
table of contents (generated from @@NAVx: in main file) different levels would be possible troubleshooting parts list schematics - exploded diagrams preventive maintenance schedule operations search for text bookmarks/placemarks redline/grayout editing select and print (to printer or file)
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.