How to Configure a Rush Order in MxAPS

Use this procedure when a production order needs to be scheduled ahead of normal work.

Before You Begin

Confirm which production order status is being scheduled:

1. Planned
2. Firm Planned
3. Released

Use the same status when you generate the MxAPS schedule, otherwise the order may not be included.

Configure the Rush Order

1. Search for the applicable production order list:
   • Planned Production Orders
   • Firm Planned Production Orders
   • Released Production Orders
2. Open the production order.

3. In the MxAPS Scheduling FastTab, set Priority.

   Set Priority to the value that your MxAPS scheduling rules treat as higher priority.

   In the default setup, normal priority is typically 5. Do not assume whether a lower or higher number is more urgent unless you have reviewed the scheduling rules.

4. Confirm the prompt to update related routing lines.

   When Priority is changed on the production order, MxAPS prompts to update the related Prod. Order Routing Lines.

5. Open the production order routing lines.

   From the production order, choose the line/routing action that opens Prod. Order Routing.

6. Review the Priority on each relevant operation.

   If only some operations are urgent, set Priority directly on those Prod. Order Routing Lines.

   If an operation has its own Priority, that value is used before the production order header Priority.

7. Avoid setting Rank unless a forced sequence is required.

   Rank forces an operation into a scheduling position. It is stronger than a normal rush priority and should only be used when the planner intentionally wants to force the sequence.

8. Optional: Set Start After DateTime.

   Use this only if the rush order must not start before a specific date and time.

   Leave it blank if the operation can start as soon as capacity and material are available.

9. Review Just-in-Time fields.

   For a rush order, make sure Just-in-Time settings are not delaying the order unintentionally.

   Check these fields:

   Field	Rush order guidance
   Just-in-Time Increment Duration	Leave blank or zero unless the order should still be delayed toward its due date.
   Max. Early Days	Only relevant when Just-in-Time scheduling is enabled.
   Max. Late Days	Only relevant when Just-in-Time scheduling is enabled.

10. Optional: Set Allow Holes.

If appropriate, allow the operation to use available idle time before other work.

11. Close the routing lines.

Regenerate the Schedule

1. Search for MxAPS Generate a Schedule.
2. Enter the normal schedule options:
   • From Cell No.
   • To Cell No.
   • Start Date
   • Schedule Duration
3. Use Filter or Scheduling Filter Set to make sure the rush order’s production order status is included.
4. Optional: Select Consider Manual Changes From if the new schedule should preserve machine moves or ranking changes from a previous schedule result.
5. Choose Generate Schedule.

Review the Result

After the schedule is generated, confirm:

1. The rush order is included.
2. The urgent operation moved earlier.
3. The order is not blocked by material availability.
4. The order is not blocked by machine/work center availability.
5. Other orders were not moved in an unacceptable way.
6. The order is not still late.

Troubleshooting

If the rush order did not move earlier, check:

1. The schedule run included the order status.
2. The schedule filter did not exclude the order.
3. Priority is used by the active scheduling rules.
4. The direction of the priority scheduling rule is understood.
5. An operation-level Priority is not overriding the production order Priority.
6. Start After DateTime is not preventing an earlier start.
7. Just-in-Time settings are not delaying the order.
8. Required material is available.
9. Required capacity is available.
10. Related parent or subassembly orders were included in the same schedule run.

Notes

MxAPS resolves Priority in this order:

1. Priority on the Prod. Order Routing Line.
2. Priority on the Production Order.
3. Default Order Priority from MxAPS setup.
4. A fallback value of 5.

Use Priority for most rush order scenarios.

Use Rank only when a forced sequence is required and the planner understands the effect on the rest of the schedule.