| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | responsible shop | 0;1 | POINTER | 6922 | B | Engineering shop(s) with PM responsibility. |
| 1 | technician | 0;2 | POINTER | 6929 | The Engineering Service employee who normally does the PM work on this piece of equipment for this shop. | |
| 2 | starting month | 1;1 | SET OF CODES | 1:JAN 2:FEB 3:MAR 4:APR 5:MAY 6:JUN 7:JUL 8:AUG 9:SEP 10:OCT 11:NOV 12:DEC | STARTING MONTH is used by the PM module as a criterion in determining when a PM is due. Let's consider the following example: an item subject to MONTHLY, QUARTERLY, and ANNUAL PM inspections. If STARTING MONTH were set to FEB; an ANNUAL inspection would be scheduled in FEB; QUARTERLY inspections in MAY, AUG, and NOV; and MONTHLY inspections in MAR, APR, JUN, JUL, SEP, OCT, DEC, and JAN. If STARTING MONTH is left blank, JAN will be assumed. | |
| 2.6 | skip months | 0;3 | FREE TEXT | A range of months (inclusive) during which PMI's are to be suspended. For example, an entry of 'NOV-MAR' for an air-conditioner would suppress the scheduling of any PMI's in NOV, DEC, JAN, FEB, and MAR. Some care needs to be taken when using this field. If you want an annual inspection, for instance, be sure that the STARTING MONTH is not within the range specified by the SKIP MONTHS; otherwise the ANNUAL PMI will never be scheduled. Entries must take the form 'MMM-NNN', where MMM is a three character abbreviation of the first month for which PMI's should be suspended and NNN is a three character abbreviation of the last month for which PMI's should be suspended. Valid abbreviations are: JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, and DEC. | ||
| 2.7 | criticality | 0;4 | NUMERIC | An index of the importance of performing PMI's on this device. Enter an integer between 1 and some upper limit not greater than 99 (most sites use 10 or 20). The closer a value is to the upper limit, the more critical the Preventive Maintenance Inspections are. A value of 1 indicates that PMI's are desireable but far from essential (least critical). When PM worklists are generated, the system will ask if all devices should be included or just those whose CRITICALITY is within a certain user specified range (say, 7 to 10). This is intended as a means of adjusting workload to match available resources. When a CRITICALITY range is specified (as part of PM worklist generation), the system will ask the user whether equipment with no value for CRITICALITY should be included or excluded. | ||
| 3 | frequency | 2;0 | MULTIPLE | 6911.13 |
Error: Invalid Global File Type: 6911.01