Workplaces
A workplace is a place where work happens: a machine, a cell, a line. You link the tags of that place to it, so UpBlue knows that the speed, the counter and the stops of the filler belong together. Operator screens pick workplaces and show the stops of their operation tags.
A workplace is linked to values of your labels, such as its hall and its line, and its tags take those over. Read more about workplaces and articles.
Create a workplace
Open the Workplaces page
Go to the Workplaces page, in the OEE group of the menu. It lists every workplace with the values it is linked to as badges. Filter on its labels to see, for example, every workplace of Line 2.
Create it
Give it a name, for example Filler line 2. The workplace opens.
Settings
Click a workplace to open it.
- Name — unique among the workplaces.
- Also known as — other names of this workplace, for example
line2orL2: a filter or route onworkplacematches them too. - Labels — a picker per label: the values this workplace belongs to, such as its hall and line. A workplace can have several values of one label, for example a palletizer that serves two lines. With no labels yet, the card links to the Labels page.
Under its labels the card says how many tags take them over: “Applies to 50 tags of this workplace; 2 have their own choice”, with those tags listed. A tag with its own choice keeps its own value of that label. When the change reaches a started route or a destination, UpBlue asks you to confirm it first: it takes effect at once, without a deploy. Read more.
Tags of the insert API
A tag that the insert API or a data import makes with a label workplace gets the workplace that label names, by its name or what it is also known as, without regard to case; one that does not exist yet is made. A tag you link to another workplace keeps it.
Linking tags
A tag belongs to at most one workplace. Link it in one of three ways:
- On the workplace page — in the Tags card, pick a tag in Add tag. The trash icon removes it again. The Linked column shows how each tag got there: by hand, from a label value, from the screen (see below) or made from labels.
- On the tag — the Workplace picker in the form in which you create or edit a tag, with a picker per label under Labels.
- On the rule — a connection rule with a tag has a Workplace picker and Characteristics. Picking a workplace links the rule’s tag, and when the rule creates events, its operation tag too. Clearing the field unlinks them.
A change on the tag or the rule saves at once and takes effect at once: routes that select on a workplace follow it within seconds, without a deploy.
Linking a tag that is on another workplace moves it, with its history: data and stops are read through the tag.
Editors and admins create workplaces and change everything on the workplace page.
Available time
The Available time card says which roster the workplace follows and since when. Without one it follows the default roster of your organisation. Change picks another roster from a date: the days before keep the roster they had, so the figures of past months stay as they were.
To give several workplaces a roster at once, select them in the list and click Roster for N selected.
Where it comes from
The Where it comes from card says from which data UpBlue calculates what the workplace does. Each field offers only what it can be.
- State — whether the workplace runs: an operation tag, which runs while no stop runs. A measurement becomes a state with an event rule or a state model.
- Reasons — with an operation tag as State: which reason tree operators pick the reasons of its stops from. Default, a tree, or None.
- Good and Scrap — a counter (a data tag that counts the pieces), or a number field of a form on this workplace; for scrap also a lines field, which counts with its total. An entry is divided over the roster time its period covers: a report at 14:00 that covers the time since 22:00 the day before counts in the shifts of that period, not in the night between them. An entry whose period holds no roster time counts in no total.
- Norm — the pieces per minute the workplace makes. Below it, the norm per article on this workplace, which wins over the norm of the workplace.
- Article — an Article field of a form on this workplace: from each entry on, the workplace makes that article.
A tag that a field points at cannot be deleted while it does: pick another source first.
State model
When one signal does not say whether the machine runs, a State model derives it from several: a speed, an alarm and a mode, for example. Click State model on the workplace page. Editors and admins make, change and deploy a state model.
- Writes on — an operation tag of its own. The model writes every stop on it, and the workplace’s State follows it: on the Where it comes from card the state is then read only.
- Inputs — the data tags it reads, each with a short name, such as
speed. An input must come from a rule of a connection: a tag filled by a device, by the insert API or by an import is refused. - States — tried from the top; the first whose condition holds is the state. A condition compares an input with a number or a text in double quotes, such as
alarm == 1ormode == "setup", with==,!=,>,>=,<and<=, combined withand,or,notand parentheses. Each state has a label, a kind and, unless it runs, an optional Reason: its stops get that reason, and the operator can still correct it. Otherwise is the state when no condition holds. - Kind — Running, Stopped or Not scheduled. A stop that is not scheduled is not counted in the available time.
- Minimum duration — how long a state must hold before it counts, so a short flicker makes no stop.
- Unknown after — an input that sends nothing for this long makes the state Unknown, which counts as not scheduled.
Save keeps the model as a draft; Deploy makes it run. It runs on the Collector that reads every input, also while the connection to UpBlue is down: the changes wait there with their time. A state starts when the Collector read the value that made it, whatever time the machine gives that value. It needs Collector version 1.10.0 or later. When that Collector is online but still runs what it had before your last deploy, the card says the Collector is behind; it catches up when it reconnects. Inputs from several Collectors or from a cloud source cannot be deployed yet. The operator screen shows the label of the state on each stop.
Screens
The Screens card lists the operator screens that show this workplace. A screen shows the stops of the workplace’s State tag when that is an operation tag. Without it, the screen shows the stops of every operation tag of the workplace, except the tags of alert rules and the tags another field of the card points at.
Existing screens
Screens made before workplaces existed picked operation tags directly. Each of them was converted into a workplace with the name of the screen, holding the screen’s operation tags, and the screen now picks that workplace. A tag that was on several screens went to the workplace of the screen with the fewest tags; the other screens no longer show it until you add that workplace to them.
Deleting a workplace
Delete workplace at the bottom of the side column. A workplace that still has tags, screens or forms cannot be deleted: the message says what is left. Remove those first. Its state model is deleted with it.