Foundational Modules
The Historian keeps your machines' counts, states, cycle times and process values, timestamped. Ask for any shift, run or asset. Every report starts from the same numbers.
How it works
Each machine sends its tags on an agreed path for that machine type. Ask for any shift, run or asset and get one total or the point-by-point series.
Tag capture
Every tag has its own path, unit and update rate, so each reading arrives labelled. It’s written the moment it lands, to a time-series store kept apart from the records the rest of the platform works on. Nobody types it in later from a shift sheet.
Count windows
Ask for a shift, a run or a month, for one asset or a whole site. You get one total or the point-by-point series, whichever the question needs, with in, out and reject counts included.
State history
Every change of state is kept: running, idle, stopped, faulted. Downtime comes straight off that record, per asset, with its reason code, so nobody rebuilds it from a shift report.
Run record
Each run keeps its own record, channel by channel. Open a finished run later and read back what each channel recorded while it ran.
Asset metrics
The OEE Engine works out availability, performance and quality from the readings already here. The number and the evidence behind it come from the same place.
Coverage
The Historian keeps the readings and does no analysis. The SPC and OEE Engines read the series and make the calls. Every asset sends at least its in, out and reject counts and its state, and anything more is agreed per machine type during implementation.
Who reads it
Nobody works inside the Historian all day. Its readings show up where the question gets asked: OEE in the OEE Engine, drift in the SPC Engine, the readings behind a quality hold.
Ask for a shift or a run and the counts come back as a series, not a spreadsheet someone rebuilt. Nothing is calculated twice.
Each run writes its own record on the channels set up for that asset before it starts. Open it afterward and read every channel back, one at a time.
Time-series machine data: counts, states, cycle times and process readings, written as they arrive. It sits in a time-series store, apart from the records the platform transacts on.
No. The SPC and OEE Engines read the series and do the analysis.
Tags arrive from the floor on a defined tag-path convention, each typed with its engineering unit and update frequency. Which tags an asset sends is agreed during implementation.
Yes. Each run keeps its own record on the channels configured for that asset, and a finished run opens for review channel by channel.
30 minutes on your machine data and how the Historian organizes it by run.
We use cookies to understand how the site is used and to connect form submissions to earlier visits. No analytics or marketing cookies are set until you choose. Privacy Policy