Factry Historian v8.3: one home for reference values, and stalled feeds you can’t miss

Factry Historian v8.3 is live! Plants can change shared reference values once instead of in every calculation, catch stalled data feeds sooner, and run heavy calculations with less memory.
Factry Historian v8.3 over a lookup table

Historian v8.2 made the platform easier to plug into. v8.3, released today, makes your data easier to trust. It puts reference values in one place, shows you when a feed stalls, and makes calculations cheaper to run. Read the changelog here or continue reading.

Most data problems in a plant are silent. A limit gets updated in some calculations but not others. A feed stops overnight. One calculation slowly takes over the server. Each one makes the numbers a little less trustworthy. Historian v8.3 deals with all three.

Who this is for, and why it matters

This release is for the people who run plants and keep their data working: operations managers, automation engineers and the IT or data owners who look after the historian. It fits food and beverage, building materials, and fine and specialty chemicals, where a wrong setpoint or a silent data gap can mean scrap, downtime or a failed audit.

Recipe and grade data

Products, recipes and grades often map to a set of properties, such as target temperatures or bend times. Many teams keep that mapping in a separate database or in workarounds inside measurements. Lookup tables let you keep the mapping in Historian and read it directly from your calculations.

Machine limits and setpoints

When a temperature or pressure limit changes, every calculation that uses it has to be updated. If a copy also sits in a spreadsheet, the copies drift, and the mistake can go unnoticed for months. Lookup tables keep the value in one place, so one change reaches every calculation that uses it.

Teams moving from another historian

Teams moving from another historian often rely on lookup tables for recipe data and grade-to-property maps, and they need that data to keep working after the move. Lookup tables let you bring it into Historian and use it in your calculations.

Stalled feeds

A feed that stops updating can leave a dashboard showing the last good value for hours. The Last value column shows the newest value of every measurement, so a stalled feed stands out without opening each one.

Heavy calculations on a shared server

As more calculations run on the same server, slow ones can quietly take capacity from the rest. The calculation load view shows which calculations cost the most, and lower memory use with many calculations leaves more room on the same server.

Lookup tables: reference data in one place

Lookup tables keep shared values in one typed table on the new Lookup tables page. Calculations and calculated event properties can read the table and filter its rows, so one change reaches every calculation that uses it. For example, keep a spec limit per product code in one table: change the limit once, and every calculation for that product follows.

  • Import from xlsx or csv, and export the table to Excel
  • Columns are typed as String, Number or Boolean

Creating or changing tables requires the lookup tables license feature. Access is controlled with the READ_LOOKUP_TABLES and MANAGE_LOOKUP_TABLES privileges.

Lookup table spec_table in Historian v8.3, with import and export
A lookup table on the new Lookup tables page.
Calculation script reading a value from a lookup table
A calculation script that reads from the table above.

See stalled feeds early

A feed that stops updating is easy to miss. The new Last value column shows the newest value of every measurement, with its timestamp, so a stalled feed stands out without opening each one.

See what each calculation costs

The new calculation load view shows what each calculation costs. Use it to find the calculations that slow the server before they become a problem. Memory use is also lower when many calculations run.

Calculation load view listing calculations by relative load and memory

Built to stay fast as you grow

v8.3 targets the parts of the system that slow down on large databases:

ChangeWhat it does
Event filteringFiltering events on a property value is faster on large databases.
Event SQL viewsThe per-event-type SQL views load faster on large databases.
Query cacheQueries can be answered from memory when the cache covers the requested range.
Periodic event propertiesCalculated event properties can now be periodic.
Child eventsChild event configurations get parent window and wait for parent settings.

Still the same Historian, still moving forward

v8.3 is about making the data you already collect easier to manage and trust. The full list of changes, including the upgrade details, is in the release notes.

Read the full v8.3 release notes

Not on Factry yet? Book a demo

Subscribe to our newsletter

Stay updated on the latest Factry news and gain insights to improve the way your factory works.

Still hungry? There's more to read

Discover some of our most popular stories.
View all