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.
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.
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
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 |