1 year ago

Factsheet - versiondog ExportModule

  • Text
  • Component
  • Versiondog
  • Export
  • Module
  • Auvesy
  • Automated
  • Backups

versiondog ExportModule versiondog – for more efficient production versiondog is the leading version control and data management software solution for automated production. It makes tracking changes and safeguarding data significantly more efficient. versiondog brings order and clarity where project data needs to be continually changed and made available from a central source. The increased safety, security and certainty provided by this software system quickly results in measurably increased productivity. versiondog makes it easy for you to optimise the interplay between all your different types of robots, controllers, field devices, drives, programming languages, file formats and software applications. This data management system gives you ultimate data traceability, minimising your risks and costs, and saving you time and effort. The ExportModule The ExportModule is an add-on that is used to export data and reports from the versiondog system. With it you can export to the universal data formats CSV and XML whenever you need to. Data is structured for straightforward import and further processing in other systems. This open interface is one of the ways that versiondog supports the processes of analysis and optimisation across multiple systems. Fig. 1: The Command Line controlled interface for the export of the project tree, component information and job results. © AUVESY GmbH · Fichtenstraße 38 B · 76829 Landau in der Pfalz Date: 25.07.2018 Page 2 of 8

versiondog ExportModule Application example 1 "Currentness indicator" for automated backups The "currentness indicator" is determined from the cyclical export of job results for which a difference exists between the backup and the most recent version on the server. From versiondog 4.0 onwards exported reports can be used to determine: - When exactly the last backup was the same as the most recent version on the server - How often (since the last time they were the same) a difference between the backup and the latest version was reported because a new job was executed - How often the comparison result could not be determined (e.g. due to changes to the firewall) Users can now use filters to find out which PLCs have been running a different version to the server for a long period of time. Three different time allowances can be defined as follows: 1) Non-critical time allowance: Ongoing maintenance work or modifications always result in differences, but these can be classified as non-critical as they only last for a few days. 2) Time period for notifications: Differences between backups and the version on the server are displayed as notifications if they are present for longer than a certain amount of time (e.g. 1 week). In this case, it is necessary to review the situation and to Check-In the latest version onto the server as soon as possible. 3) Time period for critical warning: If the notification (see point 2) is not addressed for a long time, then after a certain period of time (e.g. 4 weeks) it will be treated as a critical warning. In this case, the situation must be reviewed and it must be ensured that the most recent version is both checked in on the server and loaded onto the PLC. The "currentness indicator" for automated backups is therefore calculated as follows: Q = (n – x) / n where: Q = x = n = "Currentness indicator" for automated backups Number of critical warnings Number of jobs executed cyclically with the compare policy "Compare backup with version". © AUVESY GmbH · Fichtenstraße 38 B · 76829 Landau in der Pfalz Date: 25.07.2018 Page 3 of 8

versiondog Factsheets collection

© Copyright 2020 AUVESY GmbH - All rights reserved.