Changelog
A full rundown of our latest releases, improvements and bug fixes.
APPBug Fix
Last updated
A full rundown of our latest releases, improvements and bug fixes.
For S7 Classic data sources (S7-300 and S7-400), the ENLYZE EDGE interface now includes a tool that shows information about the connected PLC. Just enter the PLC's IP address to get everything you need.
Do not know the IP address? No problem — run Data Source Discovery first. The S7 is listed together with its IP address; copy it and paste it in.

You can now connect OMRON PLCs independently. We integrate OMRON PLCs natively via the FINS protocol. Find more information in our detailed OMRON connector documentation.
When configuring performance or downtime parameters, you now receive clear error messages if a variable is selected without a unit or scaling factor. Previously, saving only showed a confusing error message. Now you'll see exactly what the problem is and how to fix it.
The production overview now displays the product-specific performance reference line for each production run (purple dashed line). This lets you see at a glance whether a production suffered from both availability issues and performance deficits — without opening the production run detail modal each time. To show the performance reference line, check the Performance reference checkbox.

With ENLYZE MCP, you can connect your AI tools directly to your data in ENLYZE. This lets you run AI analyses, chat with your data, or have your AI agent build reports for you. Setting up the connection takes just a few clicks.
Learn how to set up the connection here.
The "Go to batch record" button is now properly disabled when no setup sheet is defined for a product and therefore no batch record exists. This makes it immediately clear when no batch record is available. Previously, you had to hover over the button to see the tooltip.
Downtime reasons can now be searched when you want to record a downtime reason. This is especially helpful when you work with a large downtime catalog with many reasons and want to quickly find a specific one.
Find more details about this new feature in the documentation.

You can now create and manage personal and organizational API keys. Find out how personal and organizational API keys differ and when to use each option in Manage API keys.
ENLYZE EDGE now supports Zumbach's laser-based ODAC measuring heads. They measure the diameter, ovality, and position of round products and profiles without contact and are typically used in wire, cable, and hose extrusion as well as in plastics and rubber processing.
The new ODAC connector reads the measured values (such as diameter, deviation, and production length) directly via the measuring head's Ethernet interface. Thanks to Variable Discovery, the available variables are detected automatically, so connecting is quick.
Find out more in ODAC.
Identifying data quality issues and their causes is a major topic, especially early in an ENLYZE rollout. Often, such issues only become visible and traceable with ENLYZE. One of the most common causes is overlapping production runs on the same machine: incorrect manual run bookings cause runs to overlap in time. Such overlaps prevent a clean assignment of time series data to runs and products. Any metric that depends on the run context (such as OEE or performance tracking) can then no longer be determined reliably. With the new feature, these overlaps become visible for the first time, so you can analyze and fix their causes.

Find out more in Analyze overlapping production runs.
Previously, the OEE was undefined for any period where scrap data was expected but not yet recorded. The quality metric was set to "undefined", which made the OEE undefined as well (since it's calculated multiplicatively). Because scrap is often recorded after the fact, OEE values on the home screen were frequently unusable.
We now assume 100% quality by default until scrap is actually recorded. In the user interface, the quality metric remains visible as "undefined" so it's clear that scrap data is still missing.
Automatic TLS detection If an S7+ data source supports TLS, this is now detected and configured automatically. Certificate paths no longer need to be located and set manually.
Connection established as HMI by default Previously, the S7+ connector identified itself as an Engineering Station to the S7 controller. If connected HMIs had automatic Transfer Mode enabled, they switched from normal operation into Transfer Mode when the connection was established — disrupting the running process. A more detailed explanation is available here. The connector now connects as an HMI by default. This means fewer permissions, but no disruption to operations. If the connection as HMI fails, the connector can still be configured as an Engineering Station with elevated privileges.
Bugfix in the password field When opening an existing S7+ connection, the password toggle was incorrectly reset to "required", even when no password had originally been configured. This is now fixed.
When you hover over a production run in the performance distribution chart on the Product Details page, the tooltip now shows quality-data warnings if that run has issues like negative scrap or missing quantity data. This alerts you to potential reliability concerns when interpreting OEE and quality numbers.
When creating or editing a data source, the IP/Host field now validates that input is a valid IPv4 address and strips leading or trailing whitespace. Invalid entries are caught immediately with clear feedback, preventing connection errors caused by typos or accidental spaces.
In the product list and product detail view, we now show the total number of orders and clearly indicate which orders are not included in the "Performance distribution" chart. Previously, orders were filtered out without notice, which caused confusion — orders seemed to disappear unexpectedly. From now on, you can see at a glance how many orders cannot be shown in the performance distribution. One click opens a list of all excluded orders, including the reason for each. This creates a clearer overview, strengthens trust in the underlying data, and makes data quality issues traceable.

The back button in sheet navigation now correctly maintains the full history of sheets you've visited. Previously it stopped working after the first navigation step. Now you can move back through multiple sheet transitions without losing your navigation path.
You can now delete the throughput configuration of a machine — previously only adjusting the performance parameter was possible.
Current limitation: Editing or deleting is only possible for machines without configured setup data sheets. The reason: setup data sheets reference the performance parameter directly, so changes could otherwise cause errors in the app.
If you'd like to adjust or remove performance tracking for a machine that already has setup data sheets, reach out to your support contact — we'll handle it manually.
Over the coming weeks, we're working on enabling editing and deletion of performance tracking even when setup data sheets already exist.
The tolerance input fields in the setup data sheet now correctly accept and store negative values, which are essential for parameters like vacuum pressures or cooling zone levels. Previously, entering a negative value would strip the minus sign and revert to a positive number.

The date range picker's "Last X Days" label now correctly indicates the rolling 24-hour window behavior. When selecting 1 day, the button now displays "Last 24 Hours" instead of the ambiguous "Last Day", eliminating confusion with calendar day selections.
Fixed a rendering issue where machines with downtime configuration but no throughput configuration would show downtimes as tiny dots at the edge of the chart. Downtimes now display correctly across the full 24-hour timeline regardless of throughput setup.
Fixed a crash that occurred when a setup data sheet referenced variables that were no longer available or had been updated. The view now displays the data sheet correctly instead of showing a misleading error message, and Co-Pilot accurately reflects whether a setup data sheet exists.
Last updated