Many Ways to Use DBDOC...

Configuration Upgrade

Summary

While you are converting, you can maintain a document where the modules that are converted to Composer are built from Composer, but the others still show their WinCAD ®or CADEWS® source.

DBDOC identifies many system issues, so you can clean them up and avoid copying them into the new system.

With DBDOC...

1. Capture a picture of the old system configuration.

  • Use DBDOC to capture a picture of your system before you start your conversion to make the conversion and checking of the new system easier.
  • If you are converting from WinCAD® /CADEWS® to Composer®, the old version can be used until the Composer® version of the module is completely checked out. A build that archives what your system looked like under WinCAD® is much easier to access for checking purposes than WinCAD or DOS CADEWS® itself, and everyone involved in the project can have this picture. Step by step, you can bring modules converted to Composer® into the DBDOC system, replacing the WinCAD® versions.

2. Easily sort out issues that exist in the old system.

Identify and fix configuration issues before conversion, or directly afterward. Using DBDOC to tidy your system before conversion makes post-conversion clean-up much easier.

DBDOC checks for issues that will affect your conversion:

  • Use DBDOC to identify and correct duplicate output references before conversion. Uncorrected, they can cause "Copy 1" type text after you conversion, forcing you to look at each instance individually to clean them up.
  • Find case-sensitive output references - DBDOC will tell you about output references that differ only in some letters being lowercase. This can prevent a major cleanup job!
  • DBDOC's "No OREF Connection" allows you to find all the places that need an output reference created.
  • DBDOC reports input blocks that import different blocks in Composer® than in WinCAD®.
  • Verify that your root user macro library works - DBDOC does the equivalent of a complete compile that will tell you if any shapes are missing from the library.

3. Reduce the amount of training necessary.

Modern configuration systems are very powerful - but it takes significant training to become a proficient and safe user. For many, the only application of this training is to be able to find problems and fix them. Using existing tools opens up the danger of logic being changed inadvertently. Why send people to costly training that is intended primarily for people who make configuration changes? The cost of installing DBDOC throughout your plant is about the cost of one week of training.

With DBDOC, you can significantly reduce the amount of training needed in order to accomplish faultfinding. Because DBDOC is strictly a read-only system, even inexperienced people can safely use DBDOC for troubleshooting, with no fear of accidentally changing something in the system.

4. Support the system more effectively while training.

If your experts have a copy of DBDOC on a laptop when they are away for training, they can assist people back at the plant much more easily. Because their access is read-only, they cannot make any changes, but can advise the plant.

5. Have a good picture of the old system while training on new techniques.

When people are trying to understand what they are being taught about Composer®, it is very useful to be able to relate the new knowledge being presented to what they know from the existing system.

DBDOC allows them to study Composer® while seeing the WinCAD® picture, helping make the training more effective, especially when training away from the plant.

DBDOC ©1996 - 2024 G. Michaels Consulting Ltd., all rights reserved. All other trademarks and registered trademarks are the property of their respective holders. Website source largely available under the terms of the AGPLv3.