Upload

Uploading the RCM-based scheduled maintenance program from the analytical engine to the CMMS/EAMS completes the analytical work. Uploading depends on the type of CMMS/EAMS where the final scheduled maintenance plan will reside and on the format used to develop the new PM program. Text documents like those produced with Microsoft Word have been in use for a least a decade to develop and maintain new scheduled maintenance plans. They are easy to develop, but uploading the results is limited to providing reference documents to be re-entered into the CMMS/EAMS scheduled maintenance table text fields. At best, Word documents with relevant PM plans can be opened and information cut and pasted into the scheduled maintenance tables.

CMMS/EAMS systems in commercial use today use relational database engines like MS SQL Server and Oracle 9i. They transfer PM table data files into their scheduled maintenance tables with straightforward queries that can import data from spreadsheets like Excel or databases like Access using an object database compliant (ODBC) process like that provided by Access. The key to successful uploading is developing the output products so that uploaded files are compatible with the table formats of the CMMS/EAMS. Every CMMS/EAMS has its own location and use design for the location and use of scheduled maintenance tables. Some use PM models to initiate new maintenance work orders as they are scheduled in the PM subroutine. The model is essentially the content of the work order. Scheduling functionality is separate and triggers the reissue of...