Grouping
This routine is intended to reduce the volume of orders to be reported, and avoid duplication of tasks in maintenance planning. So when you release the Plan through the routine Grouping, the system searches all SO's for the same good and service, with different sequences, when the system seeks information from the field SO Repl., which was informed of the routine Maintenance.
Based on the most frequent maintenance, it assigns a safety margin of 50%, in days, more or less than the maintenance released.
Example:
Maintenance for Asset AC001.
Service = Preventive
Sequence 1 = maintenance time increment (15 days)
Sequence 2 = maintenance time increment (30 days)
In the maintenance register, inform in the maintenance of sequence 2, in the field SO Repl., that it can cancel the maintenance of sequence 1.
The System considers the maintenance of higher frequency in the above example, the maintenance of sequence 1, which occurs every 15 days. Based on this information, it assigns for the date expected to start maintenance of sequence 2, a safety margin of 50% more or less, which in this case is 7 days before or 7 days after the start date, all maintenance for the same GOOD, SERVICE, and SEQUENCE 1 in this range is canceled.
The SO Repl is only found in routine Maintenance; there is no link with the routine Standard Maintenance, because the rule of SO Grouping must be treated individually and for good and service. Maintenance by a counter is only Cancelled if there is another for the same start date; there is no tolerance. When exceeding 7 SO for the same Asset + Service + Sequence in the same month, you cannot view using Gantt chart and you must use the routine Confirmation of Standard Plan. |
Procedures
To Group SO:
1. | In Grouping, select the plan and click Confirm. |
A window is displayed to confirm the SO in the plan.
2. | Click Confirm to release the SO. |
1. |
See Also
Warning Workflow of Service Order Release