Documentation and versioning

You construct and build serial machines for your end customer. All projects with its alternatives are stored manually and clearly on a server or network drive. The documentation and versioning occurs as well manually by name allocation and possibly in a Word document or a self created Access data base. For this purpose several departments have to be coordinated and work together – from construction and development to the point of production and service.

Procedures have to be executed according to the terms of ISO900x, GMP, GAMP, VDA 6.4 or FDA 21 CFR 11.

Your today’s world:

• You store software versions manually on a central server or network drive. The versioning runs by name assignment but nevertheless not every employee stand to the rules. It leads to “confusions” or there is „something missed“ or possibly „overwritten“. However you never know exactly WHO changed WHAT, WHEN and WHY. The last implementing of the customer was forgotten to be archieved. Where is the current version?
  -> versiondog automates this procedures. The system documents automatically who changed when what and stores the data considering the user rights on the server centrally.

• Changes must be traceable. During optimization differences between different program versions have to be analyzed.
  With the versiondog you can during implementing put under version control directly on-site and therefore document automatically. By push of a button you compare the most different project data (SIMATIC S5, SIMATIC S7, SIMATIC PCS 7, WinCC, WinCC flexible, InTouch, CoDeSys, TwinCAT, Phoenix PC WORX, RSLogix, Schneider Modsoft, Schneider Concept, Schneider Unity, SINUMERIK 840D, Bosch IndraWorks, robot programs from ABB and Kuka, Microsoft Word, Microsoft Excel, Adobe PDF, a.o.) as well as you let indicate the differences to yourself.

• You work with standard modules to optimize your development. You construct libraries for the most different functions or for particular machine modules. These are enhanced and optimized in the curse of time. You use the content of the libraries by simple copy & paste. The problem: with manual handling of software states you do not know, which version of a library function was used in which version of a machine. In case of an error an overview is missing which shows you where an incorrect version was used.
  -> versiondog supports with the standard module administration (SIMATIC S7). versiondog safes for you automatically the cross-reference: WHICH module was used in WHICH version and in WHICH customer project – and this without further administrative expenditure. With the scope of works you track which customer application have to be updated when and with which priority.