Orders

In Eclipse, an order represents the definition of what should be produced at a machine. For XL200 orders, it is the unit of work that can be independently scheduled.

Order Code

This is the primary reference.

note

Use an order number that makes sense for production. This is typically either a Sales Order number or Work/Production Order number. We include both workOrder and salesOrder fields but often only one is used.

Material Code

Material defines a type of material. Currently, this is assumed to be a type of coil. The Material Code is a key that is referenced by orders and coils. Some material code is synonymous with the part number of a coil. Any number of coils will have the same Material Code.

Tooling Code

Toolings help define what a finished product is and what machines can produce it.

Tooling Code is called "Product Code" or "PCode" in Eclipse Classic.

info

The reason we changed it in Eclipse Pro is because there was a common misconception that "Product" would fully define the finished product, including material details (color, etc.). This creates problems when scheduling because there is no way to see the difference between changing a color (simple coil change) from changing a profile (typically much more involved).

Typically, a change in Tooling Code should happen when a physical change to the machine configuration is required.

**give some examples

Schedule Unit (aka Job).... [this needs a better title]

The unique combination of the above three values are what define an Eclipse Order. This is what can be scheduled to machines.

Order Items

Length

Quantity

Editing items in Eclipse Pro

Two roles govern order editing. job-editor covers changes that leave the total scheduled quantity alone: editing patterns, messages and user fields, moving items between bundles, and resequencing. job-editor-quantity includes everything job-editor can do and adds anything that changes total quantity: editing pieces or length, adding or deleting items, and creating or duplicating orders. A user needs only one of the two.

The order detail page lets a user with either role change items in place, move items between bundles, and resequence them. Three further actions are available from the items toolbar:

• Add Item (the plus button beside the column picker) opens a form for a new line item. The form starts from the checked item when exactly one is checked, otherwise from the order's last item, and the new item inherits that item's option, labels and user fields. Pick an existing bundle or New bundle; the item is appended to the end of the sequence.
• Duplicate Selected Items (in the items action menu) appends a full copy of each checked item to the end of the order, in sequence order.
• Delete Selected Items... (in the items action menu) removes the checked items after a confirmation.

These actions write straight through to Eclipse Classic and follow its rules:

• The order must be editable: not at a machine, and not in a DONE, MACHINE, RECALL or SENDING status.
• Items with completed pieces cannot be deleted, because production history refers to them.
• An order must keep at least one item. To remove them all, delete the order.
• Adding or deleting items changes the order's quantity, so it needs the job-editor-quantity role. Users without it do not see the add, duplicate and delete item controls.
• An order cannot exceed 800 items.

The orders list

Each row's text colour shows the order's state, with the same meanings as in Eclipse Classic:

Colour	State
Orange	On hold, whatever its status
Blue	At the machine: on the machine, sending or being recalled
Red	Done
Dark green	Scheduled
Green	Sequenced on a machine
Magenta	Returned from the machine
Dark grey	Unscheduled

The order a machine is running right now is shown in bold.

The status buttons above the list (All, Unscheduled, Sequenced, On Machine and Done) show only the orders in that state, with a count on each. Their labels are written in the row colours, so they double as the key. Scheduled orders count under Sequenced, and returned orders under On Machine. On Hold narrows the list to orders on hold, and combines with a status: On Hold and Sequenced together show the sequenced orders that are on hold. The counts follow the filter box and the Completed setting (how far back finished orders are included), but not the status buttons themselves.

Normal and Compact set the row height. A touch screen also offers Touch, with taller rows, which is the default on tablets. Lengths and weights show their unit in the column header, in the user's units. The browser remembers the status filter, row height and column layout.

On a portrait tablet the list starts with fewer columns (Order, Status, Customer, Required By, Remaining and Alerts), and Columns, Print and Row size are in the ⋮ menu.

Creating an order in Eclipse Pro

The orders list has a New Order button at the right of the Orders heading for users with the job-editor-quantity role. The New Order dialog asks for the order code, material code and tooling code, plus the length and pieces of the first line item, because an order cannot exist without at least one item. Material and tooling are picked from the existing lists; typing a code that exactly matches is accepted without choosing from the dropdown. Press Enter or Create to save. The new order opens as soon as it has synced back from Eclipse Classic, which normally takes a second or two.

The same rules apply to Duplicate Order on the order detail page, since a copy is also new quantity.

Information passing fields

The following are available to be used in bundle tags, part print, and other uses. They do not affect any processes.

Order Header Fields

Field	Description	Notes
workOrder		* see order number note above
salesOrder		* see order number note above