Table of contents:

ipolog Web-Views 

Topics related to ipolog 4 Material Flow and ipolog 4 Workspace

ipolog 4 Material Flow

ipolog 4 Workspace 

ipolog Factory Viewer

Technical adaptations:

ipolog Web-Views

important information when working with ipolog

• Migration

  • The migration of locked scenarios from the old to the current structure is currently not possible. We have added an information hint. 

• Common part data

  • For customer specific columns and products, we have added some restrictions concerning special characters. The following characters are not allowed when adding those columns: The following characters are allowed:

    • ,\_-/\()[]{}:?

    • empty spaces

    • A-Z, a-z

    • numbers

    • invalid characters: ³²@µ€|><;.#~*+ß´`=&%$§!

• When creating a new planning space, it is required to add a start date. 

Known issues:

•  Common part data

  • Changes to the names of customized column names for custom columns and products are not updated to the part data of the scenario.

  • When editing log-ids, the groups can get lost if the grouping feature for part data is activated.

  • When editing the planning state, the last editor and last updating date and time is not updated. 

  • For bulk changes and deleting the value of the attribute "loading unit" or "loading carriers per loading unit", it is not possible to save, and an error message will be shown.

  • If a filter, being in relation to the empties is stopped, it is possible that the empties are no longer shown in the table. Please do a refresh in this case. 

• Scenario part data

  • When exporting the part data, the empties of each stage are not considered. 

  • After publishing changes from ipolog 4 Material Flow or ipolog 4 Workspace, the changes are visible immediately in the scenario part data. But for exporting them, a refresh of the view is necessary in the portal to receive the correct data setting. 

• Ruleset

  • The creation of a ruleset for products with the assembly rate 0 is not possible.
    Additionally, please keep in mind, for filtering for an assembly rate of 50%, you need to add the value 0,5 in the ruleset. 

  • When deleting one rule of the ruleset, the button to save the updates is not getting active. In this case, please change another parameter back and forth to activate the save button. 

• Diff view

  • In the diff view of a scenario, it is possible that the attributes on the right-hand side do not show the correct naming. In this case, just close and reopen this view. 

Solved issues:

• Common part data

  • Changes to the attributes "loading carrier", "loading unit", "parts per loading carrier", "loading carriers per loading unit" is possible when doing a bulk edit. 

  • Changing the safety-, reorder-, and initial level is possible again. 

  • Adding and deleting a product is possible again for all cases. 

  • The material areas are added correctly for normal part log-ids and sequence log-ids if the import of a grouping chain contains only material area 1 or material area 1 and material area 2. 

  • Manual added parts (log-ids), that are in use in the planning space, are now deleted, if the settings is chosen to delete them. 

  • Reimport

    • The sequences/grouping chains, are now deleted when reimporting a logistic quantity framework, if the setting is chosen like this. 

    • Incoming log-ids are removed from sequences/grouping chains that are no longer in use. 

  • Migration

    • When importing a logistic quantity framework, the attribute "rotation of boxgroup" is set to none instead of null. This enables us to keep the initial placement of the boxes when e.g. migrating from the old to the new structure. 

• Scenario part data

  • All sequences/grouping chains of a planning space will be kept in the scenario part data, even if they are no longer in use inside the planning space. 

• Common data

  • If only a common box planning state is assigned to the scenario, the synchronisation of it is now possible again. 

  • If there were changes to common data of one scenario, the racks and part data can be used and accepted without any issues. Beforehand, there was an error 409 shown. 

• Ruleset

  • The supplier rate is no longer multiplied with 100 when the ruleset was updated.

  • Other

  • • Publishing changes from the planning space is sequences/grouping chains are involved is possible again.

    • Copying a scenario is possible again. 

Important facts

• Ruleset

  • If a material is excluded from a planning space, due to the ruleset and another material is getting to be included, and both of them are part of the same sequence, the excluded material stays in the planning space and will not be considered in the ruleset.
    So the base rule for sequences is, all material of a sequence will be shown till every single material of a sequence will be excluded due to the ruleset. 
  • When migrated scenarios of the old structure (v2) should use a ruleset containing custom columns, it is important to open the planning spaces once in ipolog 4 Material Flow and ipolog 4 Workspace. After each was opened, the ruleset can be added later on to the planning space, otherwise the data cannot be migrated correctly. 
  • Planning space whose rulesets contain a product, should also include this product inside the part data planning state. If not, there can be issues when opening the planning space or data is missing. 

• Diff view when opening a planning space

  • The diff view shows the changes of the allowed part data respecting the ruleset and the common part data of the scenario.
    If log-ids get excluded from the planning space due to the ruleset, they are shown as deleted in the diff view because they are no longer part of the planning space. 
    Unpublished changes of the planning space are no longer shown in the diff view as a difference. 

Topics related to ipolog 4 Material Flow and ipolog 4 Workspace

Feature-updates:

• There was an information added if planning spaces cannot be opened due to missing custom columns or if they were added after the creation of a planning space. 

Known issues:

• Smaller issues regarding the visualisation in the diff view were solved when comparing the different states of common data. 

• Changes of rack in a rack planning state cannot be synchronized to a scenario at thie moment.  

ipolog 4 Material Flow

Known issues:

• When deleting one knote in the decision tree, the assignment of other default process chains to log-ids can be changed. Please be careful when updating/ changing the decision tree. 
• In some cases, errors can occur when calculating cycled routes.  
• In our submodule shift schedule management, there are smaller visualisation glitches. 
•  The detailed calculation of production orders can only be done if the shift schedule was assigned in the calculation of the base product. 
• The option to delete grouping chains is not working at this moment when reimport a logistic quantity framework. 
• In KPI-monitor there can be smaller issues in some cases when working with this view. 

Solved issues:

• Crashes

  • Crash when using a shift schedule with the duration of more than 24h.

  • There was also one crash when using "import all" in the cockpit and no common data was included inside the scenario of the planning space. 

• Update of common part data to a single planning space

  • In the supply chain editor view, we integrated a new update-feature. This allows to select the different update behaviour for log-ids and its attributes due to common part data changes. There it can be selected how to handle the material areas and other attributes of the stages. 

  • Due to the latest ipolog version, the ruleset is respected for the part data of one planning space. Before this update, some of the part data were not shown. 

• Other

  • In rar cases, the module bar can be frozen. This issue was solved now. 

ipolog 4 Workspace

Features: 

The Omniverse Connector is now available for everyone! This feature can be found on the right corner, we have added here a new button. 

Known issues:

• It could happen, that the fine placement of parts gets lost. This is happening, if the material area was changed inside a planning space and those changes were synced back to the scenario part data. If you export the scenario part data in the next step and reimport them to the part data planning state you are currently using. Afterwards you sync the data back to the scenario and to the planning space. We suggest to change the material area directly in common part data and sync it then back to the planning space. 
• In production flow view, there were in some cases crashes when synchronizing the views. 

• Changes of the box planning state were not transferred to the planning space.  

• In some cases, the 2D view was empty. For those case the issue can be solved by reloading this view. 
• After changing the product offset in the conveyor editor, the position of the product was not shown correctly. 
• The changes of the production positions in the product definition cannot be saved at this moment. 

Solved issues:

• Crashes

  • When clicking two time on a material area in the 3D view to zoom to the selected material area. 

  • After creation of several stations and renaming them. 

  • When trying to open a planning space if changes to the common box planning state were done and the boxes won't fit anymore inside the rack. 

  • In several cases, when a jt export was done. 

• Ruleset

  • Defined rulesets are considered for migrated planning spaces of the old project structure - please read also through the "important facts" of this release

  • Defined rulesets are respected correctly in the planning space. Beforehand, parts that were excluded by the ruleset were shown inside the planning space, what is now no longer the case. 

• Boxes

  • For all parts, that do not have a loading carrier or loading unit assigned, a dummy box is generated in ipolog. This can be replaced by the user via the box catalog. Till now, those material was not shown in ipolog. 

  • Updated dimensions of the boxes can be transferred now to the scenario if the box planning state is updated. 

• Other

  • Due to loss of the internet connection it was no longer possible the establish the connection again and to sign in. This issue was solved now. 

  • Migrated planning spaces of the old project structure that did not have any planning state assigned, can be opened now after changes inside the planning space. 

  • Working Points of the catalog can be edited again. 

  • The creation of info labels in the 2D is only possible with valid characters, e.g. characters as “<“ oder “>“ are not allowed. Old info labels containing those invalid characters are deleted automatically with this version by opening the planning space. 

  • After changing the part data planning state of a scenario, the saving of the planning space is possible again. 
  • The loss of the fine placement in a planning space due to the reimport of common part data in relation with the sequences (without changes) is solved. The fine placement gets no longer lost. 

  • Created sequences that were not published are ungrouped correctly and the former stages are created if changes of the log-ids of the common part data area in use. 

ipolog Factory Viewer

Known issues:

• The .gltf files of a facility created from a 2D .dgn file are not placed correctly.

• There is a offset between the factory viewer and the animation in ipolog 4 Material Flow.  

• Boxes with special geometries are not placed correctly on the agv in any case.  

Solved issues:

• A crash was solved in the timebar of workers.  

Technical adaptations:

• The .msi installer for ipolog 4 Workspace and ipolog 4 Material Flow can be used again, when they are downloaded via the portal.