ipolog Web-Views

• Paths of the planning spaces, scenarios and planning states can be copied. This allows to share the concrete name with your colleagues. Just do a right click on the table and the select the element whose name you want so share. 

• Layout goes web

  • We are already supporting the option to see the layout being created in ipolog 4 Workspace in our web view. After saving in ipolog 4 Workspace, the data will be automatically transferred to the web. When opening a planning space via the web browser, you will see the layout elements in the web. Those include areas, facilities, measurements and info-labels. 

• 2D view in web

  • additionally, to the mouse options for navigation, we added also the following short cuts for the navigation in the 2D view:

    • w: to the top

    • a: to the left 

    • s: to the bottom 

    • d: to the right 

• licences:

  • We updated the licences options and the visualisation of them in the web views. The goal was to facilitate the settings of licences and have more transparency about them. 

  • Extended options in the table view and more information for a fast and rough overview 

    • available licences of your system can be activated on your own (depending of the licence setting). This option will be shown in the status column of your licence. 

    • Available licence slots and total number of licences - there is always transparency about the available slots and how many are in use. 

    • Duration of the licence: This information represents how long the licence will be valid.

    • Administration of licences 

      • Now it is possible to add more than one user as a licence manager. Licence managers can also be removed from the list of the licence managers. 

    • Optimisation for user overview: The table of assigned users to the licences was rebuild and optimized. Now all users are visible and also the information to which licence the users are assigned. 

      • Each licence can be assigned flexibel to the user pool. A user can be assigned to several licences, this ist visible directly now. 

      • If one user is no longer using the system, the licence can be easily assigned to another user. Changing the assignment is depending to the licence change interval set for the licence. 

      • The duration of a licence can also be read in this table. 

    • New search options available in the whole licence management view. This supports a faster administration than before. 

Known issues:

• For forzen scenarios it is currently not possible to use the options of the menu when doing a right mouse click on a scenario, such as e.g. copy name. 

• When coping a scenario, the error 409 occurs, but the copying will be finished without any issue. Please ignore this error. 

• When exporting a dwg file, the scaling of areas and facilities it not always the same as in the original file. 

• Common part data:

  • Filtering and sorting: 

    • Filtering for the attribute log-id in combination with the parameter "ends with" is currently not functional. 

    • Filtering and sorting for the attribute "empties log-id" and "rotation of box group" per stage and successor, predecessor and incoming log-ids is currently possible. 
      Also, an error occurs when filtering for log-ids status, log-id type and delivery type inbound. 

• Common racks planning state:

  • Dimensions are filtered by the exact and not rounded values inside the table. 

• Common box planning state:

  • When multiple boxes are edited at once and the attributes initial costs and operating costs changed, the last value is not updated. 

  • (Re-)importing common part data:

    • The attribute "rotation boxgroup" is currently unavailable for reimporting and will not be considered. 

    • A reimport is only possible at the moment, if the import file does not contain log-ids any longer and as import option is set "log-ids of common part data planning state should remain in comparison to the import file". 

    • When publishing many entries of the planning state (more than >2,000), an error 902 is occurring and there still log-ids remaining to be published. To solve this, just publish again the remaining. 

    • If the option "keep data that are not inside the import file" is selected and the import file has some issues, the data not included in the import file is deleted. 

    • Big amount of data:

      • When working with part data more than (>10,000) you have to expect long waiting times, also when publishing the data. 

      • The import of a part data file of 10,000 parts is not possible, if already 10,000 parts are in use. 

      • The import of an import file with around 30,000 parts or more is not possible at the moment. 

Solved issues:

• Import of common part data:

  • The import a file differing from the default is possible now. 

  • When importing a file with errors (e.g. missing data for some cells), the import will be stopped and a concrete reason for the issue will be visualized. 

  • When importing a file that was exported from ipolog 4 Material Flow, the defined products by user will be mapped automatically, now. 

• Common part data

  • If German is selected as a language, the editing and the creation of log-ids with decimal digests for the assembly rate is possible again. 

  • When publishing changes, it can occur that some log-ids are not selected even if "select all" is chosen. This could result that into a planning space that cannot be opened. In this case, it is sufficient to reopen the pending changes view and publish those changes in order to solve the issue. 

Good to know

• If scenarios where copied, it is necessary to open a planning space once before changes can be done to the scenario. This supports to keep the detailed placement on areas. 

ipolog 4 Material Flow

Known issues:

• It could possible, that changes cannot be publsihed to the scenario part data if the planning space was migrated from the old to the new structure and contains several products. 

Solved issues:

• When exporting the LMG, the decimal separators for decimal numbers are set depending to the selected language. This allows an import without any issues to the common part data. 

• Process chain editor:

  • Saving of different resupply amounts or amounts of empties for identical part groups was not possible and reset to 1. This is changed and different values can be added. 

• Publish to scenario part data:

  • It is possible again to publish after reimporting a file exported from the scenario with identical areas but different stages of a default process chain. 

  • When a scenario is opened, part data can be published containing an empty chain at stage 1 and changing of the common part data of a scenario at the stage before. 

• Use changes from common part data planning state for your planning:

  • Changes regarding empty log-ids can be selected and synchronized to the planning space. 

ipolog 4 Workspace

Solved issues:

• publishing inside a planning space to scenario part data:

  • It is possible to publish in a migrated scenario without stage information changes. 

  • Sometimes it happend, that there was the need of 2-3 tries to publish inside a planning space that used a rule set. This is possible at the first try now. 

• Copied scenarios can opened without any issue. 

• The issues inside the reporting and in the single reports were fixed. Due to this, the reporting shows again the concrete results for the model mix. 

• After the migration of a planning space, several errors occurred which were fixed. Now, the following options are possible again:

  • when opening the first time.

  • saving after multiple openings. 

  • open then after several times of opening.

Known issues: 

• In the view "screenshot" there is currently a crash, if buttons of this view are in use. 

• Currently there is a crash when synchronizing a big plant and the activate/ deactivate options are clicked to fast in the production flow view. 

• The fine placement of the box count gets lost, after publishing the scenario part data inside the planning space and updating the common part data afterwards. 

ipolog Factory Viewer

• From now on, there is a message shown if the version of the factory viewer if the versions of ipolog 4 Material Flow and/ or ipolog 4 Workspace do not fit to the one of the ipolog Factory Viewer.

• The version allows you to view ipolog view vr glasses. To experience this mode, please open the corresponding version in our installer. With this option, you will have a real realistic 3D impression. 

• There is a synchronisation of the product geometry, the cycle time and the whole visualisation day. This allows to represent the whole production program inside the ipolog Factory Viewer scene. 

Known issues:

• For some clients it is not possible to establish a connection to the MQTT server when starting the publish process from ipolog 4 Material Flow or ipolog 4 Workspace to the ipolog Factory Viewer. To allow the transfer of data to the ipolog Factory Viewer, it is necessary to open the ipolog Factory Viewer manual. 

• It could be possible that the defined height for the walk mode is wrong. This occurs if was changed beforehand with the mouse left/  right and the setting field was edited afterwards. In this case the value set by the user is not considered. 

Solved issues:

• Boxes, that are transported on agvs are not placed correctly on the mean of transport. 

• Boxes being on trailer of a tugger train are now visualized correctly again. 

Technical adaptations:

• We changed the open-source data store management to PostgreSQL. As a result, we have the following benefits: 

  • Fast data queries: Frist parts of the software profit by this change resulting into shorter loading times and better performance. 

  • Efficient data processing: Complex data queries, that request beforehand several smaller steps, cannot be solved via intelligent data base queries. 

  • Future stable basis: This change offers new options for the optimization of the business logic and for a powerful development of new software components in the future. 

  • Easier backups and higher stability: Backups are available since longtime, but with using PostgreSQL it is easier for us to handle them. Additionally, there is the technical base available now for modern data base features as replication and cloud native scaling.