Orders
An order is work to be done: an order number, optionally an article, a quantity and a planned start. Its routing steps say where it is made: each step has a sequence, a name and one workplace, and optionally a norm in pieces per minute. An order without steps is one step, shown on the operator screen as the order number alone.
Make an order
Go to Orders, in the OEE group of the menu.
Fill in the order number and, when you know them, the article, the quantity and the planned start. Add a step per workplace the order passes, in the order of their sequence. An order made by hand can be edited later; a saved step is not removed but cancelled.
On the operator screen
A workplace runs orders once it has an order tag: on the workplace’s page, under Orders, click Orders on this workplace. That makes an operation tag named after the workplace that holds its order events. The operator screens of the workplace then show the Work queue: the planned, running and paused steps on it, an order without routing as its order number.
The operator taps Start when work on a step begins and Pause or Done when it stops. One step runs on a workplace at a time: a second one waits until the first is stopped. Each run is an event on the order tag with the norm it ran with: the step’s own norm, else the article’s norm on the workplace, else the workplace’s. A step can run several times; paused, it is started again.
The work queue shows per step how many good pieces it made so far against the order’s quantity. What an order made, per step and as a whole, is in the Orders datasource for dashboards and OData feeds; OEE per order is the KPIs datasource with the breakdown per order.
Documents
A drawing or an instruction is shown on the operator screen for the step that runs. An order, each of its steps and an article (see Articles) have Documents, on the order page and in the article’s drawer:
- A link: a title and an http or https address on the internet. The operator screen never opens the address itself: UpBlue fetches it and shows it. It must answer without a redirect and without a login, with a PDF, PNG or JPEG of at most 25 MB.
- A file: a PDF, PNG or JPEG of at most 25 MB, uploaded to UpBlue. Use it for a document that is not reachable from the internet, such as one on a SharePoint that needs a login. The type is read from the file itself, not from its name.
On the operator screen the running step has a button Documents (n) with the documents of the step, its order and its article; a workplace in the work queue without orders shows those of the article it runs now. A document opens over the screen. UpBlue shows documents; it does not keep versions of them or approve them. A system that sends orders through the API sends the links of the order and its steps with them (documents); uploaded files stay when it sends the order again.
A step is planned, running, paused, done or cancelled. The order follows its steps: it runs while one of its steps runs, is paused while a step is paused, waits between steps (one is done and another still planned) and is done when every step is done or cancelled. On the order page you can set a step that is not running to planned, paused, done or cancelled, and Cancel order cancels every step that is not running. A running step can be set to paused or done there too, for instance when the tablet is out of use: its run ends at that moment. While a step runs, its workplace stays: it cannot be deleted, taken off its last operator screen or given another order tag, and an order sent again does not move the step to another workplace.
Orders from another system
A system such as an ERP can send orders through the API (POST …/work_order, see the API reference). It gives each order its own key, external_id: sending an order again with the same key updates it instead of making a second one. A step is found again by its own external_id, else by its sequence, and a running step keeps running. Such an order is changed by sending it again; on the order page only its status can be changed.