Versioning, documenting, coordinate
You plan and construct turnkey facilities for your end customers. All customer projects 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. Procedures have to be executed according to the terms of ISO900x, GMP, GAMP, VDA 6.4 or FDA 21 CFR 11. For this, several departments and suppliers must work together and are coordinated. In addition you possibly allocate partial orders of the facility to external partners, which also provide software
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.
- During implementing of the automation facility it is intensively
optimized on-site at the customer. Especially with stress on-site the
central filing and the automatic data backup are an important subject.
Changes must be traceable. During optimization differences between
different program versions have to be analyzed.
-> With the versiondog implementing server you have as well on-site your data under control and can synchronize your data states alternatively also with the server in your headquarter. On-site you can put under version control and therefore document automatically. By push of a button you compare the most different project data (SIMATICS5, SIMATICS7, SIMATICPCS 7, WinCC, WinCC flexible, InTouch, CoDeSys, TwinCAT, PhoenixPC WORX, RSLogix, SchneiderModsoft, SchneiderConcept, SchneiderUnity, SINUMERIK 840D, BoschIndraWorks, robot programs from ABB and Kuka, MicrosoftWord, MicrosoftExcel, AdobePDF, a.o.) as well as you let indicate the differences to yourself.
- Your customer concludes a service contract for the delivered facility. In that the issue it not only about warranty but as well about availability
and maintenance. The problem: Due to error recovery and optimization,
maintenance of the customer conducts software changes. At a malfunction
of the facility the result are discussions about WHO is responsible for
the breakdown – Is it you as supplier of the plant or the local
maintenance team?
-> If you have remote access (e.g. by VPN tunnel or by DFÜ network) versiondog savesautomatically the software states in the facility and checks for differences on delivery status. Thus you receive information about what your customer changed independently before a malfunction occurs.
