Glossary

The terms TrakState uses on screen — in the same meaning they carry there.

Data and model

Record type. The kind of event you want to record: a production report, a fault, an inspection. You define its fields yourself, in the surface, without a new program version.

Field. A column of a record type. It has a name, a type, and can be required. The types are text, integer, numeric, timestamptz, boolean and file.

Record. One single row of a record type.

Master data. A record type that does not record what happened on the floor but is a list of values — shifts, fault kinds, articles. Operational (operational) and master (master) are the two data classes a record type can have.

Value list. A master-data type a field is tied to. It is why the same characteristic does not have three spellings after a year.

Tags

Tag. A named value with a path, for example Press1.PartCount. Tags are the only way data reaches the surface — and the reason a dashboard needs to know nothing about the database.

Tag path. A tag’s name, structured with dots. That structure is also the tree you see on the left. A tag is bound by a stable id, not by its path — so renaming breaks no binding.

The six tag kinds.

Kind	Where the value comes from
Memory tag	Set by hand. Held here and nowhere else.
Query tag	From the database, through a query.
Connector tag	From a connection, that is, from a machine.
Record tag	From the database: the last field value, or the last record of a type.
Script tag	Computed here.
Timer tag	From the clock.

A value’s state (reliability). Every value read comes with a rating: Good, Uncertain, Unusable or No access. A value that cannot be determined is a result with a state — not a crash. A derived value takes the worst state of its inputs and the oldest timestamp: it is only as fresh as its stalest input.

Direction. Whether a tag reads from the machine, writes to the machine, or both. A write to an outbound tag really goes to the machine and fails if it does not arrive. An inbound tag only records.

Binding. Tying a query or script parameter to another tag.

Reach. How far a value applies: shared (the whole tenant), personal (one person across their sessions) or single view (one browser window).

Historised. A tag whose history is stored. The opposite is live only.

Connections

Connection. The wire to the plant: an MQTT broker, a TCP peer, a connector of your own. You can have several — one per hall, plus a public one.

Connector. The type of a connection, that is, the protocol. A connector brings its own settings form; TrakState renders it without knowing the protocol.

Connector plugin. A package that adds a new connector type.

Sidecar. A process of its own next to the application, brought by a plugin, started and supervised by TrakState. This is the shape for a connector that holds a connection open.

Surface

Dashboard (board). A page made of widgets. A board holds no data — every widget points at a tag.

Widget. A building block on a board or in a capture mask: a key-figure tile, a trend, a table, a filter.

Capture. Entering records by hand, through a mask generated from your own data model.

Page type. A kind of page a plugin offers — “Board” or “Capture mask”, for example. You create as many named pages of it as you need and hang them in your navigation.

Navigation. Your own menu tree. You create the folders and entries; a plugin does not decide what your menu looks like.

Presentation mode (kiosk). The chrome-less view for a wall screen: no toolbar, no menu, and no visible way out - press Esc three times, or hold a finger in the top right corner for three seconds.

Surface. Where a page is drawn: main (the normal shell), kiosk (presentation mode) or capture (touch-first capture).

Command palette. The search box for commands, opened with Ctrl + K.

Queries and scripts

Query. A question to the database, either assembled in the builder or written as SQL. Switching back from SQL to the builder drops the description.

Builder. The guided form of a query: source, result, period, filter, breakdown. It writes the SQL for you.

Dry run. Running a query or script with the current values and writing nothing. What would be written is shown.

Script. A piece of procedure that runs on a trigger and writes what it decides. A script tag computes a value; a script does something.

Trigger. When a script runs:

Trigger	Meaning
Tag change	Every write to one of the named tags is a chance to run.
Cyclic	Every so often, counted from when it was armed — not from the hour.
Schedule	On the clock the plant runs by: every quarter hour, daily at 06:00, weekdays at 06:00.
System event	Something the instance itself did.
Manual	It runs when somebody presses Run.
Library	It never runs by itself; other code calls it.

Watchdog. The supervision of a cyclic script. A cyclic script that stops is the quietest failure there is: nothing errors, no value turns bad — the plant simply stops being told things.

Key figures

Availability. Share of the actual runtime in which the line was running — measured against the time that was worked, not the time that was planned.

Performance. Ideal time for the parts produced, against the time the line actually ran.

Quality. Parts that ended up good, rework included, against everything produced.

OEE. Availability × performance × quality.

First pass yield. Parts good without any rework, against everything produced.

Rework rate. Parts that needed rework, against everything produced.

Jobs per hour. Good parts per hour of runtime.

Achievement. Where the planned quantity enters the assessment.

Users and permissions

Tenant. One customer, or one plant. Each tenant runs in its own instance with its own data and its own plugins.

Security role. A person’s coarse classification: tenant-admin, user or display. It comes from the sign-in.

Role. A fine bundle of rights you grant inside the tenant itself. One person can hold several.

Permission. The right to one single action, written as namespace:verb, for example tenant-user:create.

Directory. The source of user identities. Sign-in, passwords and multi-factor methods live there, not in TrakState.

Audit trail. The record of who changed what and when. Separate from the application log, which is for fault-finding.

Plugins and operation

Plugin. An extension. A plugin can bring pages, server-side procedures, commands, settings, page types or connectors. The product’s own building blocks are plugins too.

System plugin. A plugin that is part of the application. It cannot be switched off or removed.

Package. A plugin’s shipped file, .tspkg (with an embedded signature) or .zip (with a detached .sig).

Manifest. The description inside the package: id, version, the permissions it asks for, what it contributes.

Signature. The cryptographic proof of who built a package — never of what is in it.

Signing key (trust anchor). The public key a signature is checked against. The operator has one; a tenant can register its own.

Catalogue. The operator’s curated shelf of packages that install with one click.

Origin. Where an installed plugin came from: System plugin, Catalogue, Your key, Unsigned, Key revoked or Origin unknown.

Installed / active. Two different states. A package sits installed and inert until somebody switches it on.

Template. A whole configuration — record types, fields, tags, roles, pages — to export and load back in.

Operator. Whoever runs the installation and sets up tenants. A separate level outside the tenant boundary.

Licence. The entitlement to use the application and individual plugins. When it expires nothing is locked out: the application goes read-only, data stays visible and exportable.