Advanced Planning and Scheduling (APS)
You can update our APS based on events that happen on the shop floor. For example, you may have a very good estimate of how long some sorts of down time could last. This information can be used to update the schedule to keep it up to date and more in line with what’s happening on the shop floor.
In this release, you have the ability to specify the estimated end date on the downtime of an asset, and if it’s greater than a threshold, to send that information to the scheduling engine. Below the threshold, for example, when the operator turns off the machine when taking a break, it will not trigger an update to the schedule.
eCHR/ Electronic Signatures
eCHR Profile revision tracking
Under certain circumstances, eCHR Profiles are editable. Typically, once they’ve been approved, not many edits happen, although you can still change the name. Any change, however, will track who made the change and when.
If one or more versions are in any status other than ‘Draft’, editing the profile is not permitted.
A ‘History’ button has been added to the eCHR Profiles screen which provides the Version Revision History of the selected eCHR Profile version.
New Line Type - Item Summary Data
The Line Type, Item Summary Data, provides the framework for capturing any data relating to an item that hasn’t previously been captured when the eCHR is finalised, for example, the expiry date or version.
Control over multiple items being added to an eCHR
When an order is to produce multiple items or lots, we need to be able to configure whether all the data belongs in one eCHR or whether each item in a lot has its own eCHR.
Previously, we had control over that when items were split mid-manufacture through the ‘Force eCHR Transfer on Serial Number Change’ toggle on the ‘eCHR Profile Version’ screen. In this release, this control is extended to items or lots from the start of the process.
The ‘Force eCHR Transfer on Serial Number Change’ toggle has been replaced by the ‘Separate eCHR per Serial Number’ toggle which caters for both scenarios.
Issues
Issue Priorities page configurable
Users can define a hierarchy for issue priorities to make it clear what level of priority an issue is. Drag-and-drop functionality is supported in sequencing the issue priority list, and this is the same sequence they will appear in drop-down lists.
Label Printing
Product Label improvements
Previously, when you created a new label design version, if you wanted to apply it to many products, and it wasn’t currently assigned to any product, you first had to create the first product label and then copy that to all of the others.
Now, you can apply a product label design to several products when you create a label design.
Product Label Version revision history
The Product Label Version Revision History page has been added to keep track of changes made within a product label version.
BarTender integration
When you create a label design to be printed, it has several placeholders for fields like product name, serial number, expiry date, etc. When you design the label in BarTender, you define those parameters with their names.
In the past, you had to upload the BarTender file into Eyelit and then manually add all the label fields being careful to ensure the names match.
In this release, the Label Printing function has been enhanced to generate those fields automatically from the BarTender design file that was uploaded.
SQL fields
Previously, when choosing ‘SQL’ as the source, you needed to find and open the SQL statement, find the field name, and then type it into the SQL Field Name field.
Now, when you choose ‘SQL’ as the source (which would have been identified in the label design version), a new field appears that lists all available fields from the statement, letting you easily pick the one you want. You don’t need to open the SQL statement or have SQL skills to select the required field.
Label Print Queue additional information
The Label Print Queue now lets you search label print jobs by product and also displays the order number in the results.
‘Where Used’ on Label Design and Product Labels screens
‘Where Used’ has been added to the Label Design and Product Label screens to list what workflows reference the label design. This improves visibility of label usage and supports safer change management.
Label Design Version notes
In this release, you can add and maintain notes against label design versions. For example, a note can be used to explain that there was a minor typo correction between versions.
Public API
MES API multi-site
Historically, the API path was mysite.eyelit.com/api/endpoint. This required a site reference (mysite) in the path to an endpoint. The problem with this is that if you had 10 sites, you’d have 10 different paths to the same endpoint. That is inefficient and could be costly.
In this release, we added support for a single public API endpoint that routes requests to the appropriate site based on a Site ID provided in the payload. This enables multi-site integrations while keeping a single base URL for all environments.
API development
MaterialItem/Update API
The following fields are no longer mandatory but optional when calling the MaterialItem/Update API:
productID
statusID
startDT
locationID
currencyID
V2 BOM/Upsert
When doing a BOM upsert, you can also upsert the BOM slot properties in a single API call rather than making multiple API calls.
V2 & V3 BOM/Upsert API
When updating a BOM using v2 of the BOM Upsert API, the response includes only the BOM version that was updated.
User/Upsert API
The API allows the assignment of a user to multiple teams with one team being the default. It also allows you to unassign the user from a team if it’s not the default team.
Quality
Check Result Set status
The Item Status -> Check Results view now indicates the status of each check result set, which can be open, completed, cancelled, or partially completed. This enhancement also ensures that cancellations of check results are clearly reflected.
‘Approved’ validation status name change
For absolute clarity of what a status means, the ‘Approved’ status was changed to ‘Prod Approved’. This clearly identifies something as being approved for production. This removes the possibility of this status being misinterpreted as being approved for testing, for example.
So, the list of statuses are: Draft, Pending Approval, Prod Approved, Pending Approval (Pre-production), Pending Virtual Test and Obsolete.
Reporting
The following improvements have been made to reports:
Adjusted Labour Minutes column has been added to the Activity Log screen.
Updated the Simple Operation Planning and Detailed Operation Planning screens to display a stopped status in text when an operation is stopped, and an estimated end date is defined. For more context, see Line Block section above.
This improves visibility of paused operations in planning views. This relates to the new capability that allows you to specify the estimated end date on the downtime of an asset.
Improvements have been made to the Asset Status History report relating to filter functionality, and the inclusion of ‘Raw Data’ and ‘Detailed Status Data’ options. Also, only users with the required permissions are allowed to edit.
Enhanced the Scrap by Work Centre Analysis Power BI report to link scrap records to the root cause work centre. This improves accuracy for scrap analysis and reporting.
The Actual vs Standard Analysis report now includes labour performance by shift data. This could, for example, highlight issues that may be related to a specific shift.
A new Check Result Set report has been introduced to provide a generic, configurable view of completed checklist results. The report allows you to filter and analyse check result sets by product, work order, checklist, work centre, dates, approvers, and inspection outcomes, with one record per recorded result. This allows you to slice and dice checklist data for reporting and analysis without being constrained by Item Status.
Tooling
Maintenance override history
Tool use information can be adjusted, such as recording usage for a tool that was used before being registered in the MES.
In the current release, overrides are tracked in a history log. This is valuable because maintenance schedules may rely on how often tools are used. You can make these overrides from the Maintenance Management screen.
Overrides are tracked and can be viewed on the Override History screen. It shows what was overridden, who did it, and when.
Total use logs
The total use count of a tool has been added to the Tool Manager screen as a hidden column. This allows you to track the full age of a tool in terms of how much it has been used in total.
