Use short automatic Tagnames, and Variant Tagnames
You can draw an equipment module or unit and not care about the actual Tagnames. Later you can add the Tagnames as Variant tags. This means that you can start to write the detailed descriptions using Tagnames even before the P&ID or instrument people have defined them and still keep the integrity or your description by adding a lookup table (you can use a Variants Table special object) as a cross reference.
Use Page change tracking.
Do you need to manage small changes under heavy version control?
With page change tracking you can lock a diagram, and then record and add notes to every change you make to the diagram. Once a diagram is locked then unlocking it from the page details form prompts:
"Do you want to track the changes and then relock?"
If you answer Yes, then the diagram is unlocked and opened immediately. Right clicking will show a menu option "Show Changes since Unlock ". This brings up a form where you can enter a description of the changes. You can also get ControlDraw to list the main changes to objects by clicking a List Change button.
An easy way to make a small image with Paintbrush is to use the Edit Copy function - this will create a Bitmap out of the selected area - see Windows Paintbrush Help for further details. Another Paintbrush tip is to set the image attributes to 1 pixel wide and high before pasting, then the bitmap sizes to the image that you pasted. This is very useful when editing ControlDraw pictures.
You can use Tools Sequence numbering to automatically number the steps and transitions in SFC and PFC diagrams. In order for this to work, the Class of the Steps and transitions should have an appropriate setting for the ‘Test Sheet Render Type:’ field in the Data Designer.
Note - this field was first introduced to determine how to represent different classes on test sheets, but has grown to be even more useful than that.
Dont Cut and Paste - Move
Tip - Build an IO List
Why build an IO List?
After all, you may already have P&ID's and an instrument dept to do that.
You can only relate procedural objects to the physical plant in a computer model if the model includes the physical plant.
The IO list in ControlDraw takes much less time to do than the instrument index based list, so the cost is low compared with the instrument based one.
If the counts in the model are close to those someone else has produced then the model is far more likely to be physically accurate. Cross checking the two is an early test that takes time but save the time that would occur later at far greater cost, for example during testing.
It makes sure that the modellers understand the plant in detail.