LogiX 3.17

Release Notes:

1. Hint rules list

Every single factory has all of the available hints enabled by default. You can disable any of it if needed.

Open

Hint rules switcher

2. Add the Dummy machine flag to the work spectrum view.

If the machine is a dummy (a machine without any signals connected to PackOS, one of the options in the “Settings and properties” tab), a ‘Dummy’ label appears.

Open

Dummy machine example - Unscrapper

3. Add an option to set production targets for the Area and Factory level.

4. Edge devices' new screen

The table is placed in Settings → Advanced. It is a list of Vision and LogiXGate edge devices. You can add a new one or delete it. There’s information including the attached line, type, time source name, and time correction. Available with Plant Admin permissions. More to read here.

The second tab: “Tags“ allows you to display all of your tags. You can narrow the result by using searching and selecting a direct Edge device. Example below:

The 3rd tab: “Tag history“ is the way to verify the past considering edge devices and limit the result to a specific date and scope of time.

5. Cameras new screen

The table is placed in Settings → Plant configuration. It is a list of cameras attached to certain machines. You can add a camera, assign it to a line, or a machine, and configure the time window (before and after the downtime starts and ends) for the video clips that are collected by the system.
Available with Plant admin permissions.

6. Modified “Manual Way Of Working” form

To enable In-process production reconciliation for a specific line, use setting property MANUAL_WAY_OF_WORKING_ENABLED to true.
The view is refreshed and separated into ‘Production' and 'Waste’ tabs. You can input the total amount (from the beginning of the order till the chosen end date) or the increased amount.

7. Updating and revalidating the order after changing the product definition

For SKU and SKU groups, when you change the Line configuration or Packing structure, the order in Draft or Released status becomes validated again and jumps to Draft status again when it needs some changes. Activated or Started orders aren’t sensitive to those changes.

8. New problems` tags

Add a way to set the problem to one of four tags:
- BeforeRootCause: A downtime marked with this tag will instruct PackOS to set the root cause of the downtime to a previous downtime on the same machine. This tag is set by default for all downtimes grouped in the "Operator Stopped" state.
- NoRootCause: Downtimes marked with this tag will never have associated other root causes from a different machine. This is especially useful for holdups/idles which are strictly performance-related stoppages. Where no downtime of an external machine is the reason for a stop
- DownstreamRootCause: Downtime marked with this tag will instruct PackOS to look for the root cause of the downtime on downstream machines (machines that are after the stopped machine in the current product flow). This tag is set by default for all downtimes grouped into the "Holdup" state.
- UpstreamRootCause: Downtime marked with this tag will instruct PackOS to look for the root cause of the downtime on upstream machines (machines that are before the stopped machine in the current product flow). This tag is set by default for all downtimes grouped into the "Idle" state.

9. Checking the Packing structure before order activation

You are informed whether units are defined, packing structures are filled and flow is given. The order is being validated before going from Draft to Released state.
If you correct the order (eg. change the line, correct expected effort, or packing structure), the order will revalidate automatically and go to the Released state https://app.shortcut.com/ilabo/story/24035/sprawdzenie-struktury-pakowania-przed-aktywacj%C4%85-zlecenia.

10. OEE report warning-box.

Add the warning box informing you about the different scope of time and resolution. In the example, the user selects only 3 hours (10:00 - 13:00) and sets the Day resolution. So if the workday starts from 6:00, the user should consider showing resolution - None to display only the required time, not the whole day.

11. Organizing the Licenses section in ConfigHub

We distinguish the following elements that are essential when calculating licenses for PackOS (the license calculation method may vary slightly among different clients):

1. Base Automated Machines (standard maximum of 20 signals per Automated Machine)

2. 20 Signals Extensions (a package of additional 20 signals for an Automated Machine)

3. Manual Machines

4. Dummy Machines

5. Vision Extensions

6. Advanced Signals Extensions
   
   

    

12. Changing the way of selecting Problem type during adding/editing line/machine downtime

The previous process included a few steps to go through:
- select line/machine
- select state and
- select problem
here’s an example:

The new process streamlines adding/editing downtime by limiting steps and showing problems` classification in only one screen:

13. Add a way to edit or delete the comment

You, as an owner of the comment, can edit or delete it. Action will cause the update in the Comments report.

14. Display the result of the pre-processing function

Execution history allows you to verify if the created function performed correctly or if some errors occurred. You can select the date and the scope of time.

15. Changing the way to download clips.

Video player (Line view) allows you to display clips from all configured cameras. You can read more here.