Procedure Charts
Previous Topic  Next Topic 

>View >Procedure Charts

There are many ways of using Procedure Charts.

The original intent was to provide a means of producing a step table of the procedural elements mapped to their equipment. And this is exactly what you can do. In the URSWriter (where the charts first started) that is all you can do with them at present.

Procedure charts are tables that have Pages as columns and object tagnames in the cells.

For example if a Unit has three operations that it can perform, and the Unit diagram has these operations as objects on the unit diagram then the procedure editor can provide a list of operations to run on each step. In edit mode it provides a drop down list to select the operation to run on each step.

However, with ControlDraw, there are other things you can do with them. They provide a quick way of defining for example Unit States mapped into child Equipment states.

Procedures charts are very much easier to produce than PFCs, or even state matrices.

You can select what goes in the cells for a given column as either RCP/UP/OP or by class. If you select the procedural objects then those that appear in the drop downs when you click a cell are the objects on the diagram whose class type is Step-Trans.

By default ControlDraw models set this for those objects that behave as if they have both a step and a transition, for example phases, operations and unit procedures. This same property by the way is what makes the PFC right menu functions recognise them.

Procedure charts have no way of showing synchronisation between equipment, however there is a workaround means of adding notes. Create a diagram for step notes and then give them a class such as MemoryString.


At present procedure charts do not have any dynamic functionality and cannot be used for simulations.