Application Framework
Expand all/collapse all buttons
The expand all/collapse all buttons have been added to tree view screens.
Configurable drop down options – Property Definition
Some property definitions require a selection to be made from a list. In the past, when you created new properties, you had to write custom SQL to create an option list.
Option Lists can now be configured in the Option Lists screen.
Option lists can be user defined (user defines exactly what options are available) or SQL (e.g. if you want a dynamic list of options).
In 9.5, you can user pre-configured options lists in property definition. If you select ‘Combo box’ when configuring a new property definition, you then have the ability to select a pre-configured option list (or use a SQL statement as before).
Login page
The Eyelit MES login screen has been updated and simplified. If it is a registered device, the ‘User Mode’ and ‘Device Mode’ radio buttons will be displayed where you have to choose which mode you want to login as.
Pre 9.5
From 9.5
Install logs version numbering
Eyelit Technologies is moving towards a unified numbering system i.e. all software within the group will have the same sequence of major version across the board. As part of this the Eyelit MES now has a Eyelit Technologies Release number in front of the usual release numbering.
The first Eyelit Technologies unified release is 10.0. 10.1 is planned for the middle of the year.
This can be seen in install Logs version numbering system, where the current application version listed in the Install Logs is shown in the following format: 10.0.9.X.X
The image shows the numbering for release 10.0.9.5.0.
Assets
Work Centre Group
The following improvements were made to the Work Centre Group UI:
Paging has been added to both 'Work Centre Groups’ and ‘Assigned Work Centres’ grids.
The Work Centre Group grid is sorted by name alphabetically.
The 'Count' column is renamed to 'No Assigned Work Centres'.
Added a hidden field, 'SUID' to work centre group grid.
Added a search box for Work Centre Group names.
Documents
Control of documents has been tightened up to ensure that there is no chance of controlled documents being changed inadvertently, and to ensure that uncontrolled documents where changed are fully traceable in terms of revision history.
If a document is controlled you can’t edit it without up versioning it.
If, however, a document is uncontrolled, you can have several revisions associated with a version because you’re allowed to edit it without incrementing the version. In 9.5, it’s possible to view the revision history for these documents.
eCHR
Enhanced Line Type - Use/Remove transaction reporting
In the past, when you did ‘Remove’ and removed a child component from a parent, the eCHR of the parent didn’t record what happened to the child item. A child item that was removed could be placed on hold, scrapped, or returned to vendor.
In 9.5, we now report on what the linked transaction was, i.e., hold, scrap or return to vendor, in the parent eCHR.
New Line Type - Check Results Set document
The Line Type - Check Results Set Document has been added to allow you to upload a document against a check result set and it will automatically be added into the eCHR. For example, an output of a piece of test equipment or a photograph of the item being inspected.
Issues
Added label design and product label scopes for issues
Some labels, particularly in regulated industries, are critical to quality. If an issue is found with a label design or configuration during production it may be important to instantly block any chance of that label being printed before the issue is resolved.
In 9.5, it is possible to associate tickets with two new scopes: Label Design and Product Label. These scopes allow you to link a hold issue to a product label version or a label design version.
Label Design Scope
If a hold issue is linked to a label design version then no labels of this label design version can be printed (note that this could be label design version or a product label version that references the specified label design version) unless they are test prints or admin prints.
Product Label Scope
If a hold issue is associated with a specific product label version then no labels of this product label version can be printed unless they are test prints or admin prints.
Note that the Product Label Scope option is only visible in the UI for customers that hold the Advanced Label Printing license.
Label Printing
Advanced label printing module
In 9.5 Eyelit has created a new Advanced Label Printing module, building advanced regulatory label printing controls over and above the out-of-the-box label printing functionality.
Basic Label Printing
Works with Bartender templates to generate an image based on a label design and configured parameters.
Correct batch data is automatically included in the label without having to type or select correct values.
Prompts / enables the printing of labels at the appropriate times on the shop floor.
Advanced label printing allows for further control and additional functionality over in addition to the above:
Controlled product specific data for product labels (including translations) - this approval controls the combination of label design and layout with data.
Full approval process to ensure that only full checked and approved labels can be used on the shop floor – compliant with FDA and ISO electronic signature and record keeping requirements.
Printing is triggered on the shop floor when needed via an enhanced label print action.
Advanced label printing UI for operators to be able to view the pending print image and compare it side by side to a reference image as part of enhanced quality checks on the line.
Tools to enforce and control comprehensive reconciliation of every label printed in line with regulatory requirements.
Granular permissions in line with label printing functionality
In some industries, especially medical devices, control of specific labels printed is paramount. Every label printed / scrapped / reprinted must be accounted for, and for this reason these are typically printed by specifically authorised people. Other labels, e.g., tote labels are not important for quality and can be printed by anyone, so do not need the same level of control.
In 9.5 enhancements have been made to Label Printing - specific permissions can now be set at label type, controlling print / reprint / scrap of labels of that type:
Previously, Product Label data fields weren’t nullable. It was required to add a blank space into those fields. In 9.5, you can now leave these fields empty. A product label field with a null value is printed as an empty string.
Improvements have been made to the Product Label Management screen (Advanced label printing only):
Product Label screen is where label designs can be combined with product specific requirements in a controlled configuration and approvals process.
Added server-side paging for faster load times.
Additional filters (Label Type, Label Design and Label Design version) and toggles to facilitate searches.
Additional extensive information available within the grid
Added a shortcut button to the Label Design version.
Replace 'Edit Button' with 2 buttons:
Edit Product Label: Allows you to edit product label parameters (comments/description and qty).
Edit Version: Allows you to view / edit version specific parameters.
The following new permissions and roles were created/updated in line with the Advanced Label Printing Module vs basic label printing module:
New permission: Advanced Product Label Administration - Users with this permission can add / edit product labels / versions. It’s added to the Advanced Product Label Administrator role which in turn is part of the following permissions:
Advanced Product Label Administration
Print Unapproved
Review Labels
Set Product Label Draft From Pending
Set Product Label Draft from Obsolete
Set Product Label Obsolete from Approved
Set Product Label Obsolete from Draft
Set Product Label Pending From Draft
New permission: Label Design Administration - Users with this permission can add / edit label designs. It’s added to the Label Design Administrator which in turn is part of the following permissions:
Label Design Administration
Label Printer Administration
Review Labels
Material Item Status
Item Status – check results view
In Item Status, Check Results view, items with a large amount of check results display in a very long list of results. This requires excessive scrolling to find a result. The following enhancements have been made in 9.5:
Check Results Set and Check Result grids have paging.
When a results set is selected in the results grid, 'View results in full screen' appears. The view check result details pop-up in full screen/maximised screen
Check Results Set grid hides the following fields: major version / minor version / ID.
Public API
Upsert on unique fields
You can call the following Workflow Type Upsert endpoint without an ID (where the entity exists then the ID is retrieved from the unique field, i.e., name).
Tool Type list based on SUID and/or name
When the Tool Type SUID and/or name is provided, the appropriate Tool Type is returned.
User/Upsert endpoint
Updated the User Upsert public API to standardise the manager field as a simple string value, allowing the manager to be set, cleared with null, or left unchanged when omitted, and removing the unintended object-based payload format.
Align all existing API that shouldn't use optional field
Standardised multiple Public API endpoints to remove optional data wrapper objects and use consistent field semantics, ensuring omitted fields are ignored, null values clear data where allowed, and provided values update correctly across workflow, user, tool, and job-related APIs.
api/JobOperationPlan/Update.
api/ToolGroup/List.
api/User/Upsert.
api/Workflow/UpsertStartNode.
api/Workflow/UpsertEndScrapNode.
api/Workflow/UpsertEndConvertNode.
api/Workflow/UpsertJumpToTaskNode.
api/Workflow/UpsertEndCompleteNode.
api/Workflow/UpsertStartNewTaskNode.
api/Workflow/UpsertWorkflowOperationNode.
api/Workflow/DeleteNode.
api/WorkflowVersion/Upsert.
api/WorkflowVersion/Delete.
Quality
Rollback mistakenly entered check result
Previously, if you unintentionally entered a check result value but hadn’t actually done the check, there was no way to remove it. In 9.5, there is added support to clear previously entered checklist results so operators can roll back non‑checkbox check step values to null, with mandatory checks still enforced during checklist completion or approval.
Scrap WIP with an open check result set
As of 9.5, it is possible to scrap a partial quantity of an item which has an open check results set, as often checks do trigger scrap if non-conformance is found.
Checklist statuses aligned to those used in workflow, BOM, recipe versions
Prior to 9.5, the statuses for checklists were different to the statuses used throughout the rest of the UI (workflow, BOM, recipe version). In 9.5, checklist statuses have been aligned with the rest of the system to provide more granular control over where they are applied within workflows and ensure that they are used appropriately.
A Checklist Type can be controlled or uncontrolled.
Only checklists of a controlled type can be referenced in workflows of a controlled type.
Additional controls in place for controlled checklists are in line with workflow, i.e., for a controlled Checklist Type:
Checklists can only be promoted to ‘Approved’ status from 'Pending Approval' (and only by users with the appropriate permissions).
Checklists can only be changed to 'Obsolete' from 'Approved' status.
Checklist versions can have the following approval statuses:
Draft: Cannot be referenced in any workflows that are not in draft status.
Pending Virtual Test: Cannot be referenced in any workflows that are in ‘Pending Approval’, ‘Pre-production’ or ‘Production’ status.
Pre-production: Cannot be referenced in any workflows that are in ‘Approved’ or ‘Pending Approval’ status.
Pending Approval: Cannot be referenced from an approved workflow.
Approved: Can be referenced in workflows of any status.
Obsolete: No longer valid. Checklists being set to obsolete must have the following validation:
They are not directly referenced in any approved workflow.
They are not the designated approved latest version (or major / minor version) if reference is ‘Use latest major / minor version’.
Reporting
Scrap by period report
When reporting scrap in the Scrap by Period report, it used to calculate the percentage scrapped based on the qty completed. This doesn’t take into account what’s in WIP, which could be significant in, for example, long-running operations. The reported percentage scrapped could therefore be far lower than what was reported.
In 9.5, the Scrap by Period report uses the following calculation:
Scrap % = (Scrapped Qty / Total Quantity) × 100
Where, Total Quantity = WIP Qty + Completed Qty + Scrapped Qty
This gives a scrap % that:
Starts at 0%.
Gradually increases as scrap occurs.
Better reflects real manufacturing behaviour (especially partial completions)
TAKT Time report
A new TAKT Time report has been added to the Performance section of the OEE reporting suite.
Note that this report is reliant on full production scheduling reflected in MES, with planned start / end times and planned work centres populated for all operations.
This report provides a real-time, plan‑based view of production performance, allowing you to assess whether output is tracking against plan during the current shift or selected time window.
This report works from the formula
TAKT Time = Available production time / Customer demand
How this is applied within Eyelit MES:
Available time = time window (hourly buckets of time within selected parameters)
Customer Demand = planned output for that hour, based on job operation plan start and end times and planned work centres.
Example
A work centre is running an operation for 10 hours. The planned output for the 10 hours is 6000 units.
Takt time = 600/6000 = 0.1 minutes per unit
The expected output per hour = 60/0.1 = 600 units.
The dashboard shows a status summary example for the current hour vs the expected output for the hour, as well as a view of output per hour across the shift (discrete and accumulative).
Quality dashboard
We have introduced a new Quality Dashboard as a standard system report which provides a consistent, configurable view of quality performance across the system.
In previous versions, it was always possible to link a scrap event to the point in the workflow at which it happened. However, the root cause of that scrap could have been much earlier in the workflow. In the past, information about root cause was typically recorded as case data, with potentially custom case data reports.
Link scrap to manufacturing root cause
In 9.5 we have added the ability to link scrap losses to a manufacturing root cause, allowing scrap to be attributed back to the originating operation and work centre. This will enable more system reporting to come around scrap root cause analysis out of the box.
When recording a scrap transaction, users can optionally capture the manufacturing root cause, making it easier to analyse where defects were introduced and improving the accuracy of OEE and quality reporting.
The scrap UI allows you to specify the manufacturing root cause of the scrap and to choose: ‘Unknown’, ‘Current Operation’ or ‘Prior Operation’. Selecting ‘Prior Operation’ displays a further drop down list where you can select an operation and a work centre.
Tooling
Tool Manager UI
We have streamlined the Tool Manager to make it the central hub for tooling and maintenance.
Navigation to Maintenance Management has been simplified with direct shortcuts and smarter filtering, terminology has been standardised across tooling screens, and menus have been reorganised under a new Asset Management structure.
These changes reduce navigation effort and improve visibility of tool maintenance and status.
Tool Use Log and Maintenance Management UI
We have improved the integration between Tool Manager and Maintenance Management to provide better visibility of tool usage and history.
Key improvements include:
Added a new Tool Use Log pop‑up, accessible from both Tool Manager and Maintenance Management for a selected tool.
Improved tool usage visibility with a consolidated grid showing individual use records and cumulative usage for each tool.
Enhanced filtering of tool use history with a date range filter, defaulting to recent activity.
Improved data capture by allowing time as well as date to be recorded for tool use entries.
Clarified navigation and labelling by renaming the maintenance history action and adding a dedicated Use History entry point.
These changes make it easier to analyse how tools are used over time and strengthen the link between tooling and maintenance activities.
Workflow
We have added support for concurrent workflow task start, allowing you to start a child task while remaining booked on the original workflow operation.
This enables activities such as checklists to run in parallel without interrupting the main workflow, while continuing to record time on both tasks.
Validation ensures concurrent tasks can only be started where the work centre supports concurrent activity, improving flexibility while maintaining control.
This is configured by selecting ‘Concurrent’ in the Start Mode field on the Edit Start Node pop-up in the Design Workflow screen.
Workstation
We have improved the Workstation search experience by adding support for filtering work orders by operation name or operation number. This allows you to quickly find all relevant work orders for a selected device or work centre based on the operation you need to perform, even when jobs are not yet planned or started.
We have made the Workstation action screen less cluttered by allowing the Stat Profile to be shown or hidden, giving more space to action content on busy screens such as checklists and detailed work instructions.
Static stat profiles are intended for data that does not change while the operator is booked onto the action screen, e.g., serial number, product, op number, etc.
We have made the static section of the Workstation stat profile configurable by adding the ‘Workstation Static Stat Info SQL’ property in Application Properties.
It is a site-level static SQL that you can select or clear, while continuing to support multiple action-specific dynamic stat profiles. This restores the intended flexibility to control which static statistics are shown and how they are populated.
