What Is a Logging History Event Type?

A logging history event type is the label on one entry in an operation's actuals history, recording what kind of event produced that entry. It turns a list of timestamps into a readable narrative: who did what, when, and whether the entry is an observation, a correction, or a computed total. EDGEBIC by User Solutions uses the type to drive a gutter marker beside each row so the shape of an operation's day is legible at a glance.

How it works

The history keeps every entry made against an operation, and the type says which kind each one is. There are seven values.

Four of them record what an operator did at the machine. Operator start marks the moment work began. Operator pause marks a stop, and a pause normally carries a reason. Operator resume marks the restart after a pause. Operator complete marks the close-out. Together they bracket an operation and expose the gaps inside it.

Supervisor edit is different in kind. It records a later correction to a value that was already logged, made by someone with the authority to change it and always carrying a mandatory reason. Corrections do not overwrite the original: the earlier entry stays and the edit sits beside it, which is what makes the history defensible rather than merely current.

System rollup marks an entry the platform produced rather than a person, generated when underlying records are aggregated into a day's hours. It is labeled separately because a derived figure and an observed one answer different questions, and conflating them is how a reader ends up trusting a number nobody actually recorded.

The last value is a catch-all for anything that does not fit the other six.

Each type maps to a distinct marker in the gutter beside the entry, using a small set of symbols for the state changes, a pencil for edits, and a plus for rollups. The point of the markers is scanning: a reader running an eye down the column sees the run of the day before reading a single value.

A concrete example

Think of the log book a supervisor keeps at a station, where each line records something that happened and the margin carries a small mark saying what kind of thing it was.

An arrow in the margin means the operator started. A pause symbol means they stopped, and the line next to it says why: waiting for material, tooling change, quality hold. Another arrow means they picked it back up. A square means they closed it out.

Now a pencil mark appears three lines further down. That is not the operator; that is the shift lead correcting a figure the next morning, with a note explaining that the operator tapped complete an hour early. The original line is still there, unchanged, and the pencil line sits beneath it.

Finally a plus mark: the end-of-day total, computed rather than written by anyone at the machine.

A reader who understands those five marks can reconstruct the day from the margin alone. That is exactly what the event type gives a person reading an operation's history on screen.

How EDGEBIC uses it

Event types label the entries in an operation's logging history, and the same discipline of never overwriting an earlier record applies throughout: the original stays, the correction is added. Reading that history as a supervisor, including how to make a correction properly, is walked through in reading the kiosk punch history drawer, and the correction record itself has its own glossary entry in punch adjustment.

The underlying shop-floor records these entries describe are classified by their own value set, covered in punch type, with the origin of each record described in punch source. Where a rollup entry's figure ends up is explained in daily hour breakdown.

Entries the system filled from plan rather than from the floor carry their own visible marker, described in the auto-filled actuals badge explained, which matters because a derived figure should never be mistaken for an observed one. For the wider vocabulary, see the manufacturing glossary, and to see actuals feeding a live plan, explore EDGEBIC.