Workplaces and articles
Workplaces and articles are two labels that UpBlue has from the start, each with a page of its own: a workplace is a machine or a station, an article is what a workplace makes. Your own labels, such as a hall or a line, are on the Labels page.
Workplaces
A workplace is a value of the label Workplace, made on the Workplaces page. It is linked to the values of your other labels: the filler belongs to Hall 1 and to Line 2. A workplace can have several values of one label, for example a palletizer that serves two lines. There is no tree: a hall is not a workplace above workplaces, it is a value that workplaces are linked to.
The tags of a workplace take over its values: link the filler to Line 2 once, and its fifty tags are on Line 2, also the tags you link to the filler later. A tag with a value of its own keeps it. Read more about a workplace.
The key of the label Workplace is workplace: {workplace} in a topic prints the name of the tag’s workplace.
Articles
An article is a value of the label Article, made on the Articles page, with its norm per workplace, its limits of measurements and its documents.
Fields and KPIs
The Fields and KPIs button on the Workplaces and Articles pages opens what a workplace or an article can have, and the KPIs calculated over it. A label of your own has them too, on its page under Labels; that page shows the label’s key next to its name, and Edit label changes both. The workplace comes with the fields State, Good, Scrap, Norm and Article (see Where it comes from) and the KPIs availability, performance, quality and OEE; these are marked Fixed and cannot change.
You add fields and KPIs of your own:
- A field — a key (lower-case letters, digits and
_), a name and a type: a number, a text, a tag, a field of a form, a value of another label, or a source (a counter tag or a number field of a form, counted like Good). You fill it in on the workplace’s page (Own fields), in the norms drawer of an article, and on the page of a value of your own label. - A KPI — a key, a name, a formula and a unit (
percentfor a ratio). A formula uses numbers,+ - * /, parentheses and names: the totalsavailable,run,run_outside,unknown,good,scrapandexpected, the number and source fields, and the other KPIs. For exampleenergy / (good + scrap)with a source fieldenergy. The KPIs datasource calculates it for workplaces like OEE.
A field that a value has, or that a KPI uses, cannot be deleted; nor a KPI that another KPI uses.
Editors and admins see the Labels, Workplaces and Articles pages and make labels and values.
Two values of one label
A tag of a workplace that serves two lines takes over both. Routes and dashboards handle that: a route on either line takes the tag, and a dashboard column prints both names joined with +.
A destination cannot: a topic factory/{line}/… needs one line. The destination does not send such a message; it counts as not accepted and is listed under Messages with the reason. The tag page says so before it happens. Pick a line on the tag itself to give it one.
Changes take effect at once
Picking a tag’s labels, changing the values of a workplace, renaming a value, changing what it is also known as and changing the key of a label need no deploy. Within seconds, routes on a label take or drop the tags, and destinations print the new names. A system that reads the destination sees the change right away.
So when a change reaches a started route or a destination, UpBlue asks first. The Confirm change dialog says how many tags change, and lists:
- Routes — the routes that gain or lose tags.
- Destinations — the destinations whose output changes, with the topic before and after, for example “topic becomes factory/Line 2 packing/… instead of factory/Line 2/…”.
- Tags with two values of one label — and the destinations that will refuse their messages.
Click Save to make the change, or Cancel to leave everything as it was. A change that reaches no route and no destination saves without the dialog.