What TrakState is

TrakState records what happens on the shop floor and makes it answerable — from the machine, through the captured record, to the figure on the screen.

Unlike a bespoke solution, TrakState ships no fixed data model. Which records exist and which fields they carry is yours to decide, in the interface, without a new release. Everything else — capture masks, dashboards, key figures — binds to that model.

The five terms everything rests on

Record type. The kind of event you want to keep: a production report, a fault, an inspection. You define its fields.

Tag. A named value with a path, for example Press1.PartCount. A tag can come from a machine, from a query, from a script, or simply be a remembered value. Tags are the only route by which data reaches the interface — which is why a dashboard needs to know nothing about the database.

Connection. The wire to the plant: MQTT, TCP, or a connector of your own.

Dashboard. A page of widgets, each bound to a tag.

Script. A piece of procedure that runs on a trigger — cyclic, on a schedule, on a condition, or by hand.

Where to start

1. Define the data model — which records, which fields.
2. Set up a connection — so values arrive.
3. Create tags — what you want to see and work with.
4. Build a dashboard — bind widgets to those tags.

Each of these has its own chapter. If you are installing TrakState right now, start with Installation and operation.