Lot Assignments support lot genealogy by allowing input lots (or components) to be assigned, or linked, to an output lot (or finished goods). Enact uses this information to track which components are used in specific output lots—and which output lots contain a particular input lot or component.
Lot assignments are created via the new Lot Genealogy Assignments landing page, found in the Labels menu. Part recipes are used in lot assignments to ensure accurate lot tracking.
Benefit: Lot assignments enable detailed lot tracking within Enact.
Below is the Lot Genealogy Assignments landing page showing the output lots, as well as the input lots assigned to each output lot.
Lot Genealogy Report
The new Lot Genealogy Report supports the following lot tracking scenarios:
- Tracking components, or input lots, used in finished goods or a specific output lot
- Tracking which output lots used a component or specific input lot
- Using lot genealogy to identify the source of poor product quality
- Supporting regulatory compliance through more efficient product recalls
Lot genealogy enables manufacturers to control product quality more effectively. If a substandard component is used in a series of output lots, they can be quickly identified and either removed from inventory or reworked. In the food and beverage industry—where food safety is the highest priority—the Lot Genealogy report helps manufacturers prevent bad products from getting onto store shelves or, in the worst case, helps producers quickly identify output lots to be recalled—greatly aiding in regulatory compliance.
Benefit: Helps manufacturers track lot quality for both internal and external customers.
The following screenshot shows the new Lot Genealogy report.
The first screen shows the landing page where a user selects between an output or input report. In the example below, the Output lot genealogy report is selected.
The next screen shows the output Lot Genealogy report and the input lots used in a completed output lot (finished goods). The first screen shows only the output level, expanded to display statistics. The second screen shows both the output and input lots, expanded to display all statistics.
The second type of Lot Genealogy report is created by selecting the Input
selection on the Configure Options
The screen below shows an input type lot genealogy report for a specific input lot or component, as well as the output lots where this component was used. The first screen only displays input lot statistics. The second screen displays input lots and output lots, expanded to show all statistics.
The statistical data found in both types of lot genealogy reports can be customized via the Configure Columns
button and screen, shown below.
Improved Usability Features
Advanced Filtering for Data Collection
In addition to the existing filtering by part family and operation, you can now add additional filters to include or exclude parts and processes for each individual feature row of a data collection. Data collections on a feature will be skipped if it doesn’t apply to the part and process on which you're collecting data.
These new filters provide additional control during data collection, and allow part families, operations, and data collections to be consolidated – simplifying the system configuration. You can now add a feature to a data collection once, and use part/process to determine if it shows up during a data collection operation.
Benefit: Helps consolidate and simplify process models and data collections. Encourages re-use of data collection configurations—saving system administration and operator time, and reducing system complexity.
Following are the new data collection part/process filtering options.
Enhanced Notification Rules (Enact vs. Email)
Enact notification rules have been enhanced via the addition of a Method option. Users can now choose from the following three options to determine how a notification is delivered:
- None (Inactive)
- Via Enact only
- Via Enact and Email
This enhancement enables users to respond differently to different types of system alerts/events. Some situations warrant an email, while some do not. In addition, users will now receive emails regarding processes they have selected in their My Processes window. This enhancement allows for better control of how alert/event information is shared within a production facility.
Benefit: Facilitates improved control on how event notifications are handled, and ensures that only targeted emails are sent out to users—reducing the number of unwanted emails.
Following is a screen shot of the Notification Rules landing page with the new Methods dropdown list displayed.
New My Processes Window Options
The My Processes window now has the following two options:
- All Visible Processes
The All Visible Processes option is dynamic; if a new process is added to the system, users will immediately see the new process if it is part of his/her responsibilities.
The Custom option displays a selected view of a processes that is static; new processes will not display automatically.
Note: This enhancement may affect what users see when they log in. We recommend that you inform your users about this change—prior to the update—so they don’t get confused.
Benefit: Provides more control over the My Processes window, enabling users to view the data most important to them.
Below is a screen shot of the My Processes window—before and after the change.
At the top of the My Processes
window, you can now select All visible processes
System Alert Notifications
Enact Administrators can now select who receives System Alert Notification emails from InfinityQS. These emails typically include system maintenance and incident notifications, the four-week notifications before significant user interface changes, and regular two-week notification of a new update—including a link to our Enact What’s New page, which contains information about the new features.
This new capability enables Enact system administrators to determine who on their team needs to receive these types of email notifications. For example, most users will not need to know about system maintenance activities.
Benefit: Reduces the number of Enact generated emails sent to users, helping save time and reducing confusion by operator-level users.
Proxy Server Option for Gauge Agent
The update includes a new proxy server option that allows Gauge Agent to send data via a proxy server. This data security feature is often required by corporate IT departments.
This option supports:
- Windows internal proxy settings
- Custom proxy settings via a local configuration file
Helps users meet corporate data security standards when using Gauge Agent and Enact.
Following is a screenshot of the proxy settings used to activate this option.
To see previous Enact updates visit our archive page.