So far it was hard to see if an order is already deckled but not yet definitely scheduled on the corrugator. For such orders, there are already are runs in Program Memory, but no starting time and program number have been assigned yet. That made it impossible to tell in order lists whether an order was already deckled or not scheduled at all on the corrugator.

Now a new status color has been introduced to distinguish such orders. If the corrugator appears in gray letters on a light yellow background in an order's machine sequence this indicates that this order is in Program Memory but hasn't been assigned a starting time yet.

So now e.g. in the order view by customer you can see if an order is scheduled on the corrugator, complete with starting time and program number, or if the order so far only has been deckled but not definitely scheduled yet.

The PC-Topp.NET Program Memory page now indicates which programs contain orders that require special scores. You can identify those programs by the small red icon ( ) next to their program number.

If you click on such a program number the combinations view opens with red icons in front of those orders in the program which have to be run with special scores.

This feature is particularly useful if there are restrictions for special scores which the Automatic Optimization cannot take into account, e.g. if there is only a limited number of certain score types available. With the new marker the planner can easily distinguish the programs concerned and check if the restriction is observed.

It is now possible to specify not just a maximum overrun tolerance, but also a minimum overrun tolerance for an order. This new parameter handles better the case where a customer accepts the ordered quantity plus or minus 10% (see example below).

There is a new field called "Min. %" in the classical Order Entry / Update screen (next to the maximum overrun tolerance field "Tol. %"). The value entered in this field determines the minimum number of finished goods required for an order. If set, the new value overrides the Minimum Overrun Tolerance in the Optimisation parameters.

Positive and Negative Minimum Overrun Tolerance

The minimum overrun tolerance can be a positive or a negative value.

• Positive Min. % value: More items are required than actually ordered.
• Negative Min. % value: Fewer items are accepted than actually ordered.

See the table below for a practical example.

Ordered		3000	Too Few	OK	Too Many
Case 1	Tol. % Min. %	10   3	< 3090	3090-3300	> 3300
Case 2	Tol. % Min. %	10 -10	< 2700	2700-3300	> 3300

(Make sure to set the minimum overrun tolerance to a smaller value than the maximum overrun tolerance; otherwise the latter will be ignored.)

So far, orders could only be marked yellow and blue (meaning e.g. Urgent and Very Urgent) in the classical programs Conversion Machine Scheduling or Order Entry / Update. This facility has been extended to five different flags so that now you can assign more different priority levels to your orders.

Besides, these flags can now be set not just in the classical programs mentioned above but also in any PC-Topp.NET page where the Order Summary is available. You just have to click Change in the new Priority field to successively set the following flags:

Classical Programs	Priority	PC-Topp.NET
	Low
	Normal
	Increased
	High
	Very High

If an order is given a priority level its special status is emphasized by an eye-catching icon next to the order number so you can immediately see that it has a special status.