ipolog Web-Views

• Tables and Filtering:
  • We have adjusted the visualisation and the functionality of our tables. This allows a consistent look and feel when working with them, e.g. filtering, grouping or sorting. For you as a user, the identification of the entries you are looking forward is much faster than before. The adjustment was made for the following tables:
    • Common Data
      • list of all box, rack and part data planning state
      • list of all boxes, racks and part data entries in their planning states
    • List of scenarios of a project
    • list of planning Spaces of a scenario
  • All options, that were beforehand on the right-hand side of a table row, are now available via a right click on one table rack with the mouse.
  • Additionally, we adjusted our filter visualisations in the tables to get more transparency about the currently selected filter options. This allows to adjust them faster than before and to understand the filtered entries better, especially if more filter are active at the same time.
  • The columns inside the tables can be positioned individually at different places and can be made visible/ invisible by the users themselves. This allows to personalize the tables more than before. After a restart or reopening the same view, the tables rest also at their positions as it was defined by the users.
  • All columns can be grouped except the name and the date columns. If you want to group a single column, you have to move the column header into the bare above the table.
  • The functionality to do bulk changes is kept as before. 

Known issues:

• When creating a rule set and using the assembly rate as a filter criterion, please keep in mind to add the decimal number instead of the percentage number. 

• Creating a log-id with german browser language selection needs for the assembly rate no comma, but a dot. The same is for creating and editing racks. 

• After editing some entries of a part data planning state, not all numbers are visible in the part data table in each cell. To solve this, refresh of the browser window solves this situation. 

• After deleting a part that was edited beforehand in the part data planning state, a error message appears. 

• If names of custom specific columns or custom specific products are changes, those changes are not reflected inside the scenario. 

• The filter for sequences shows currently also log-ids that have the type normal part. 

• Common data

  • Reimport

    • A reimport is not possible if an import file without sequences is imported by using the option delete log-ids if they are no longer in this import file. In this case we suggest importing the file with keep data and delete the sequences manually. 

Solved issues:

• Several adaptations of the user interface and hints for missing entries were made when attributes are missing, especially for sequences.
• Common Data
  • Boxes:
    • Last modifier and last modification data are now updated correctly if changes to boxes were done.
    • Boxes, whose names contains only letters, can be imported via the .csv file again.
    • For some attributes the marker as required attribute " * " was missing. It is added now.
    • Je nach eingestellter Sprache ist eine Trennung von Dezimalzahlen entsprechend nur mit Punkt oder Komma möglich. Eine entsprechende Warnmeldung wurde eingebaut, um Transparenz zu schaffen.
  • Racks:
    • Editing a gap between rack bays is possible again.
    • After deleting a rack, it is shown now as deleted with all attributes.
    • Saving of racks is only possible when all data of a rack, including the geometry, are stored. This allows us to save all data on all sides.
  • Part Data:
    • bulk edit
      • After a bulk edit that deletes data of the attributes of "loading unit" and "loading carriers per loading unit" the saving is possible again.
      • When doing a bulk edit of parts, there are no longer any side effects. Also, validities can be set now via a bulk edit.

      • Dependencies between loading carrier, loading unit, parts per loading carrier and loading carriers per loading unit are considered. In the past, it resulted into error messages. A short overview about this: 

        • Loading carriers and parts per loading carriers can be set together

        • loading unit and loading carriers per loading unit can be set together now, but only if the attributes loading carrier and parts per loading carrier were set before 

    • When importing part data, there is a validation for the supply rate and the assembly rate that those values are not bigger than 100%. Please keep in mind, that the separation of the decimal places is not the same separation as in the import file.
    • The material areas of empty log-ids are now updated correctly again when the material areas of full good log-ids are updated.
    • The attributes of "valid from" and "valid to" of parts and log-ids behave in the same way again.
    • For some attributes the marker for required attribute " * " were missing. This is adapted.
    • The mapping of part data during the import is possible again if the header row in the excel file is not the first row of the excel sheet.
    • Reimport
      • The reimport of part data, that has sequences, is possible without any issues.
        Mit der Ausnahme das ein Reimport abgebrochen wird, wenn bei diesem mit einer Import Datei ohne Sequenzen die Option verwendet wird, dass LOG-IDs/Daten gelöscht werden sollen, welche nicht in der Import Datei enthalten sind (also die bereits vorhandenen Sequenz-LOG-IDs). In diesem Fall empfehlen wir die Import Option zu verwende Daten zu behalten und die Sequenzen manuell zu löschen.
      • In order to keep the fine placement as much untouched as possible, the reimport and all changes that are impacted by it do not consider sequences anymore. This means: existing sequences inside a planning space are kept unchanged. The exception is changes to the number of stages of a sequence - those are considered. 
        We suggest doing the adjustments of the sequences in the common part data and to publish them there.
      • For the reimport, it is possible again to choose the option to import only attributes if they were set to empty beforehand.
      • To keep or to overwrite single attributes individually when reimport a file is possible again.
• Scenario part data
  • Directly after publishing the changes of ipolog 4 Material Flow and ipolog 4 Workspace to the scenario part data, those changes are visible inside the part data. This allows also to have all current data inside the export of scenario part data.
  • If changes to log-ids were done for the attribute material area inside ipolog 4 Workspace planning space, also the empties are adjusted now correctly due to the update of the full good log-id.

• Area filter

  • Changes of the available areas after the reimport of the common part data are now available in the area filter after synchronising the scenario.

• Rule set
  • If a rule is removed from a rule set, the button to save the changes is getting active again.
  • The state attributes can habe now commas as a decimal separated when creating a ruleset.
• Scenarios and planning spaces
  • Scenarios, that have the status "template", "deleted" and "archived" are not getting active, if they were opened once again. 

• More:

  • In KPI comparison, it is possible again to switch the planning space as a reference for the evaluation. Alos, the reference planning space can be deleted and there is no longer any error message shown. 

  • Scenarios and the favorite scenarios are listed again without any issues. 

Overall topics ipolog 4 Material Flow and ipolog 4 Workspace

Solved issues:

• The synchronisation when opening a planning space from a scenario is working, when beforehand the part data was changed with another part data planning state.

• The published fine placement of your planning space is kept, if you e.g. add new cmmon part data to the planning state and use them inside the planning space. 
  There is a validation done between the current published common part data planning state and the planning state being used in your planning space. If you have empty attributes for e.g. rack template name or rotation of boxgroup, they are not considered but the values that were added by the user beforehand inside the planning space are kept. 

• If, since the last release (4.5.2), a scenario containing sequences with boxes/material from several products was edited in the old structure, material was lost in these sequences so that the sequences only contained material from one product. If the scenario of the old structure was transferred to the new structure, these were missing accordingly and the fine placement was partially lost, but publishing to the scenario part data was also not possible. We have now fixed this problem.

ipolog 4 Material Flow

Known issues:

• If you delete a node in the decision tree, the assignment of default process chains to the other nodes is changed. 

• Currently, there are some smaller issues with the calculation of cycled routes. 

• The calculation of single product groups in the view production data is only possible, if the shift schedule is also selected for the calculation of the basic product (rough calculation). 

• The option to delete grouping chains is currently not functional after reimporting the logistic quantity framework. 

Solved issues:

• In the simulation of transports is it possible again to activate single route transports and means for direct transports. Also, only the number of tuggers for those is shown. Also, the evaluation of the mean usage of them is working again.
• When discarding inside the view production data, the values for "parts per product" are shown correctly and also the calculation of values for the attributes inside the logistic quantity framework (LQF) is working fine. 

ipolog 4 Workspace

Known issues:

• In the view production flow, there could be a crash when synchronising the different views. This crash occurs only under special circumstances. 

• Changes of the box planning state are not reflected in all cases inside the planning space. 

• In rar cases, the 2D view does not show any content. In this case, please reopen this view. Afterwards, all elements are shown again. 

• After changing the product offset in the conveyor editor, the position of the product is no longer shown correctly. 

• The changes of the product position in the product definition is currently not stored.  

Solved issues:

• Imported 3D facilities via the MS-Plugin are now available also for all users that do not have imported those files in the 3D view.
• The import of facilities via the MS-Plugin is working again also for users whose names contain a vowel.
• The defined anchor-points in the production flow view are considered for the alignment for single planning space again.
• Migrated provision requirements of the old structure (without log-id names) can be deleted totally. 

• The migration of scenarios of the old structure does currently a check with the placement requirements of the base product. This is done independently if the material is placed on the outside corner are or on the material area. Those are kept as being inside the container. 

• Saving inside the planning space is possible again, also for the migrated scenarios of the old structure, if the part data was changed beforehand. 

New features for ipolog Factory Viewer

• We have expanded the mouse-over information for direct and route transports in order to be able to assign them better and faster. The route name is now also displayed for route transports. For direct transports, the group name (from the group formation module) is now also displayed.
• Our new ‘Viewpoints’ function is now available in the menu bar at the top left. This allows you to create viewpoints for each project in the ipolog Factory Viewer. The views and animation times saved in these viewpoints are available to you at any time in the ipolog Factory Viewer. This enables precise navigation in meetings.
• For direct transports, the number of transported containers is now visualised on the respective means of transport, which helps you to better understand the planning data.
• We have optimised the time scale for you. This makes it easier to navigate through it, for example to jump to a specific point in time in the animation. The display of the entire time period with subdivisions at every full hour or the output of the current animation time with day and time now provides you with help.
• The visualisation of the transfer of data to the Factory Viewer has been optimised.
• A search function is now available to you. This is located at the top of the module bar. If the search function is active, you have the option of filtering your existing elements by type, e.g. rack or transport, or using the input field with your input. You can now use the filtered list to find your desired element quickly and clearly. You also have the option of double-clicking on an entry in the list to ‘fly’ with the camera to the corresponding position in the simulation.
• We have also integrated a “ Walk mode”. This can also be started via the menu bar. This allows the user to walk through the factory at a self-defined eye level and recognise what is visible from this position.
• Furthermore, there have been design adjustments for buttons and dropdowns according to ipolog design guidelines.
• The name of the button for transforming data from ipolog 4 Workspace and ipolog 4 Material Flow changes depending on whether the Factory Viewer is already open or has yet to be opened.

Known issues:

• When discarding the edited project in a planning space of the user, the local factory viewer settings are in use instead of the others. 

• Boxes, that have a special geometry are not placed correctly on the agvs.

Solved issues:

• Rack geometries are now displayed correctly. There were problems converting .gltf files.
• Visual optimisations when zooming in parallel to this in ipolog 4 Material Flow in the transport simulation in the Gantt.
• Certain data records crashed when they were transferred with product and worker data. This crash has been fixed.

• The transfer of data from ipolog 4 Material Flow is working without any issues, if the options are selected to transfer different data. 

Technical adaptations:

• Significant performance improvements through technical adjustments in the background.