Application Framework
Assets
The system ships with a set of default asset statuses including an "Available" status. The "Available" status is typically configured to be the default idle status for assets which is automatically used when all work is booked off an asset.
In this release, the "Available" status is renamed to "Idle" to be more intuitive.
New installations have the following default asset statuses (with status class in brackets):
Idle (class: downtime)
Breakdown (class: downtime)
Running (class: running)
Unscheduled time (class: excluded)
e-CHR / Electronic Signatures
eCHR Mode enhancements
Prior to this release the eCHR functionality was focused on as manufactured records. With the development below it is starting to expand out functionality to manage post manufacturing work also. The following configuration allows the user control over how the eCHR is generated / managed in a number of different scenarios:
Manufacturing is started in the standard production flow – during production, work is carried out under an auxiliary flow (e.g. rework / non conformance / additional inspection) - all work needs to be recorded appropriately in the as manufactured record.
A minor issue is found on an item after it has completed the production workflow – this can be rectified in a new repair workflow but should be included in the as manufactured eCHR record.
An item is repaired or serviced, potentially after being returned from a customer – this work is done on a repair workflow and is added to a separate as maintained eCHR record
The eCHR Mode that is configured as part of a Workflow Type (e.g. production, rework, non conformance, repair) specifies how to deal with the eCHR when you create a task using a workflow of this type.
In this release, to guard against inconsistent eCHR generation or invalid task spawning, this functionality has been enhanced to ensure the adherence to validation rules, to ensure the alignment between workflow versions, eCHR profiles (across multiple versions and statuses), recipes, and BOMs.
Workflow Type eCHR modes
The eCHR modes control how an item’s eCHR is managed.
Use Add to existing eCHR when the workflow is launched for an immediate, as-manufactured repair or rework.
Use a Create New eCHR when the workflow relates to a new item created, or a later activity, such as a repair long after production, a service, an upgrade, or a return from vendor.
Use None where no eCHR is required.
Summary of rules for create new eCHR vs adding to an existing eCHR vs None
ECHR Mode | Suitable for: | Start node | Requires |
Create new |
|
|
|
Add to existing |
|
|
|
None |
| Any | n/a |
ECHR Listing - Serial Numbers
Standard production processes involve the legitimate update of serial numbers for items during the course of production. This change is stored in the eCHR.
As of 10.2 the eCHR listing now has extended eCHR search - to allow users to search for items based on historical serial numbers rather than only current values.
Label Printing
Label Design Version fields
Enhancements have been made to label design.
Label field configuration
Enhanced the Label Design Version functionality to support configurable default values for SQL and prompt fields. This improves both test printing and reference image generation.
New fields
Label design versions now have the following additional field settings:
Literal Text or Value
Test Print Default Value – value to be used when the print type is test print (e.g. might want to use the maximum number of characters allowed by the Bartender template)
Live Print Default Value (e.g. might want an obvious error message to help operators spot missing SQL generated values e.g. ‘ERROR - DO NOT USE!!!’)
These fields are shown based on the selected field source.
Test print behaviour
Refined test print behaviour so that all configured fields are displayed with the correct default values and editability settings.
Controls for assignment of a product label version to an approval
Assignment controls
The feature enforces strict controls on how product label versions are assigned to approvals, ensuring only one active approval per label version at any time. It also prevents conflicting assignments by restricting reassignment to completed, abandoned, or deleted approvals and validating all attempts.
Status management
Label version status is fully driven by the approval lifecycle, ensuring status changes occur only through defined workflow steps. It also enforces consistent behaviour by preventing manual overrides and automatically synchronising states when approvals are updated or removed.
Validation rules
The system ensures that only valid and approved label design versions can be assigned to approvals. It also prevents invalid lifecycle changes, such as assigning unapproved designs or obsoleting designs linked to active approvals.
Product Label Approvals screen
Improves the Product Label Approvals screen to provide a clearer and more consistent view of approval records and statuses.
Enhances usability by adding filtering, column updates, and status indicators, ensuring users can easily identify the correct approval and understand its current state.
Label reference images
Improved the label design process by enabling easier creation of label reference images directly from the Label Design screen. Also, extended the test print capability so that configured label fields and their resolved values can be reviewed during reference image generation, supporting both SQL-driven and default value scenarios.
A label design version can be selected and the ‘Reference Image’ button pressed
The user can then select a corresponding product label version and click ‘Reference Image’ to either upload or generate a new reference image for the product label version selected.
Product label translations
Previously, it was possible to link a product label field to a translation but then hard code it to something different, i.e., the field value is different to the translation even though the field looks like it is linked to a translation key.
In this release, when a field is linked to a translation, it is not possible to overwrite the value.
Product label UI
Simplified the UI and made it more intuitive for creating new product labels. The product search and label design search have been removed and replaced with search combo boxes. The “Label Design Version” field has been added.
Material Reasons
The following Material Reasons improvements have been made:
Changes made to buttons:
Renamed 'Types' to 'Material Reason Types'.
Made the following changes to the Manage Reasons by Product Type screen:
Left hand grid has a search enabled combo box for product type.
Assigned Material reason grid has a search combo box for Material Reason Type at the top and a search combo box for Material Reason.
'Assign / Unassign - button visible when a material reason is selected.
Units of Measure conversions
It is sometimes necessary to convert from one Unit of Measure to another.
In this release, the unit conversion which is accessed from the Unit of Measure screen, has been improved by allowing you to select a Type:
Fixed: Conversion factors that are always constant and universally valid, regardless of the product.
Example: conversions between units such as millimetres, centimetres, and metres, where the relationship never changes.
Product Specific: Conversion factors where the product itself affects the conversion value. Used when the same units do not have a consistent relationship across all products.
Examples: Converting between weight and volume, where the conversion depends on the material, such as:
Water: 1 g = 1 ml
Milk: 1.04 g = 1 ml
Public API
List transactions with no record returned
Standardised on returning an empty array when no record is returned.
Product Upsert
Product case data can be assigned / unassigned as part of a product upsert call.
Quality
The Check Result History grid used to label attribute results and sample size as “Primary” and “Secondary” values with the result showing 0 or 1 to indicate pass or fail.
In this release, traceability/readability is improved. The Check Result History now displays user-friendly columns and values based on input control configuration.
Reporting
The following report enhancements have been made:
Description to Issue Analysis Report: Added the issue Description field to the Issue Analysis report by including ISSUE.DESCRIPTION in the underlying dataset.
This allows you to access and use issue descriptions in Power BI reporting, allowing you to list and analyse issues more effectively.
Scrap by Work Centre Analysis: Since release 10.0.9.5, it’s been possible to record work centre that was the root cause of the scrap. In this release, the Scrap by Work Centre Analysis report was enhanced to include data related to where scrap originated.
Scrap by WO report: The following enhancements have been made to improve clarity:
Reports on all scrap transactions for products being made on work orders (item in WIP).
Reports on all scrap transactions relating to 'remove and scrap' for children of items in WIP.
The report downloaded in .CSV shows the record for scrap performed for the child and parent.
Labour Performance reports: The following updates and improvements have been made:
Labour Performance by Team Utilisation has been renamed Labour Utilisation by Team and moved to the Labour Utilisation menu item.
Added User Group and Department filters. To support use in custom dashboards, these values can be set automatically from page parameters.
Labour Performance by Team Performance has been renamed Labour Performance by Team and moved to the Labour Performance menu item.
Added User Group and Department filters. To support use in custom dashboards, these values can be set automatically from page parameters.
Overall Labour Effectiveness navigation has been enhanced. Over time the repository of labour performance reports has become large, covering an extensive range of aspects around OLE – Overall Labour Effectiveness.
This has now been structured into a more user-friendly format, allowing the user to search for reports according to what aspect of OLE they are interested in:
Summary Analytics: Provides an overview of OLE, breaking it down into its elements.
Labour Utilisation: How much of an operator’s time is spent doing direct work.
Labour Performance: What is the output rate of an operator vs expectation.
Note that a wider set of quality reports in the Quality Section also dives into quality losses, including labour losses.
Workstation
The ‘Other Options’ search filters are now grouped logically to improve search usability.
Asset Management: Contains ‘Move Tool’.
Time Management: Contains ‘Take Break’, ‘Indirect Activity’, ‘Log Off’, ‘Clock Out’.
Inventory Management: Contains ‘Item Status, ‘Shop-Floor Moves’, ‘Shop-Floor Moves in Transit’, ‘Shop-Floor Moves Pending Collection’.
Plans and Queues: Contains ‘Planned Work List’, ‘Label Print Queue’, ‘View Silent Queue’.
