ControlDraw verison 3.6.1208 improves Recipe Parameter Handling

This version has greatly improved the Descended Object Linking.

You can use this to establish links between objects, typically Recipe parameters.

For example you can create a link between a Master Recipe parameter on a Cell Level Recipe procedure and the corresponding parameter on the phase that actually deploys the parameter. Then you can using the new Parameter Map show the link and the Unit Procedures and Operations that the parameter has to pass through to get to the phase.

The Parameter Map below show 4 Master Recipe Parameters that are linked via Recipe Procedures and Operations down to phases. (In this example the Uit Procedure level is not used)

You can also use this to create Master Recipe Parameters by looking down the hierarchy and to find all the parameters that the Entire Recipe Procedure uses and then selecting some of them to be Masters.

Improved Hyperlinks to documents and web pages

When you are specifying or designing a system it is generally necessary to keep a collection of documents, such as the P&ID's, Process descriptions and so on. Often these documents can become superseded by a model, but it is always useful to be able to refer back to them, to ensure traceability and to be able to check back. Keeping track of these can be tedious.ControlDraw has long supported simple hyperlinks, provided you had a web or file address on the first line of an object's text. This has been greatly improved recently.
You can now set a Linked Documents Path that is a top level folder that contains all the documents that you want to be able to open from a model.
You can also copy File Names in Explorer and then paste them as hyperlinks.

The Transfer Route Queries

You may not know about this although it has been possible for a long time
If you draw a diagram that shows connections between units via common resources there are standard queries that can show a table of the routes, including those that go from unit to unit (single level) , those that go from onne unit to via another unit to the last unit (2 levels) and those that go from a unit to another via two units (3 levels).
The diagram below show a simple example.
For convenience the single level and two level queries are also shown on this diagram using FAV: UserQuery special objects.

New - Tag Balloons

The latest version of ControlDraw provides a new way of attaching text to symbols, these are call Tag Balloons and are based on the ISA tag symbols for P&ID's. The picture below shows how to set them and the styles. Click to enlarge. You can now set the tagname to appear separately from the object in a variety of shapes as shown above. You can then drag the tagname to position it relative to the object.

Tag balloons are auto sized and split the first letters before the number part and the remainder.

The position of the tag balloon is stored relative to the object so you can use Copy and Paste Object properties to set other tag balloons the same - just click the Appearance button in Paste Object properties.

Rotating Symbols

The latest version of ControlDraw has added the ability to rotate symbols and their connection points easily. The illustration below shows how to change a horizontal valve to a vertical one.
This is very useful when re-organising diagrams to improve the process flow, for example when designing an HMI after starting with a P&ID type layout.

Requirements Analysis Progress Biotech plant

A video showing some more modelling is here
http://www.controldraw.co.uk/Movies/BiotechPlant2.html
This shows the development of the model to include BioReactor diagrams, (but not the details, that will follow)
It shows how to create a polymorphic diagram and it instances

Requirements Analysis Progress report

There are so far about 20 people who have expressed interest in following and contributing to this, and many more listening, judging from the number of visitors here.

One person has offered a process, in fact a complete plant!

" The process starts in the cell culture lab where biologicaly engineered cells are taken from a cell bank and grown in lab scale fermentation process until enough cells are produced to seed the first industrial fermentor. Process flow is : cell Culture - Fermentation- Harvest- Recovery- Purification - Freezing. Upstream Area, Midstream Area, and Downstream Area are the main first level of physical models in the two trains. "

Unfortunately there are no P&ID's or process descriptions available, so it is not good basis to proceed with. But some modelling is possible - see

http://www.controldraw.co.uk/Movies/BiotechPlant1.html

A free peer reviewed automation design model for your process!

ControlDraw Ltd proposes to carry out and show online the development of functional requirement of a readers process.

Readers will define the process that will be used.

Readers will contribute by helping to choose which reader’s process we start with, and by reviewing the documents as they develop. This will be done using LinkedIn Groups

The Process
This could be a portion of a process plant, say a couple of process units.It may be batch or continuous
Ideally this will be one that is real and is soon to be automated. Even if you have already started – you might like to use the exercise to compare your own design.


Source information
Please send ,in the first place, a brief (but not too brief) description of your process. You must also be able to supply P&ID’s no more than 3. As this process will be carried out publicly you must accept that anything you send will be published online.

This will of course use ControlDraw, but others (especially those that promote their own methodologies) are invited to do the same using their normal documentation system.

Here is an overview of the plan

Tag Naming - P&ID and in ControlDraw

Ever since P&ID’s were first drawn, tag names have been used to identify the instruments. And as they are intended to identify every single instrument, the tags have to be unique.
More than that, the tags always have some meaning, providing a clue as to the purpose and location of the instrument.
Tag naming is one of the first things you need to understand when you start a new project, because most projects have different ways of tagging.

How are Tags constructed?
Generally they have a letter prefix, a number or code, and often a suffix.
Conventionally these tagnames were allocated by instrument engineers whilst at the same time keeping a record of the used tag names in an Instrument Index. More modern CAD systems may keep the index and tags at the same time.
The ISA S5.1 ISA S5.1 standard, codes for Process Instrumentation provides a basis for the letter parts, but not for the number part, and methods of assigning these vary from company to company and even from plant to plant. You can always work out that PIC (or maybe PC) means a pressure indicating controller. But the next part, 1299 say or r123- or whatever is not obvious. Whenever I start working with P&ID I ask for the Equipment/Tagging standard, no two are the same! The standards cover much more than just instruments, for example equipment tags (R for reactor etc), the Area numbers and much more has a company standard. I get bored by the pipe naming.
One classic scheme is to number the instruments within the P&ID, and with part of the P&ID number in the tag. Often In turn the P&ID drawing number contains a higher level, say an area.
So we might have TIC3012-5 where 30 is the area, 12 indicates the twelfth PID in that area and 5 is the fifth Temperature measurement on the P&ID.
A more advanced scheme used by many practitioners is to base Tags on the Equipment number, so the Tags relate to the equipment, and even better so that if there are several similar equipment items the tags within each are the same.
For example, V3249-01 (or perhaps R3249-V01) might be the first valve in reactor R3249, V3250-01 the first valve in reactor R3250, and so on.
Some also have a standard so that similar items have similar sub-number, even in different type of equipment, for example Discharge valves are always V####-01

But when it comes to describing – or even programming – a controlled entity such as a
Unit or Equipment module, it is very useful to have some things that the classic method does not cover. One is Tagnames that are consistent within objects so when you look inside two similar objects (say 2 reactors) the Tags are the same – at least when you exclude the part that identifies which reactor. Then you only have to use nice short names. like V01 or FC02. It can save a lot of time.
Another issue is that, on an HMI, long tag names are unfriendly and clutter the screen. Yes, the best graphics have an option to not display the tagnames, but when you do show them short ones are easier on the eye. And combining Equipment based tagging with Unit relative graphics makes it possible.

The ISA letter parts have a problem - they are based on a very old concept – panel instruments.
In particular the use of the A for alarm letter has become almost a distraction. The A letter meant something in the old days, it might imply a need to use a trip amp and an annunciator lamp, things that had to be purchased. Now, everything can have an alarm, do you really want to change the P&ID because you added an alarm?
Similarly using I to show that something should be displayed? I would hope that everything should be displayable.


The reality is often that there are inconsistencies in the P&ID tag names, even when the tagging scheme is equipment based. (For example when the P&ID tagging has a shared common resource ‘inside’ the first equipment that uses it)

What’s all this got to do with ControlDraw?

ControlDraw provides several ways to handle this:
The External Tag can be set to match whatever the P&ID tag is.
Variants can often be used to reconcile inconsistent tags
Clones can be used to position an object within the P&ID Equipment but still in the right module
Scripts can extract the information from the tag and use it consistently.

Extract the meaning of the Tags with Scripts
Now, whatever the tag naming scheme, there is always some useful information contained within the tag name. And ControlDraw provides several useful ways to deploy that information. The most powerful is by using Scripts.
The Scripts can use parts of the hierarchy of tagnames, for example to set the Engineering Units according to the instrument letters.
TagPrefix0 is the first letters of the lowest level in the hierarchy of tagnames
Select Case TagPrefix0
Case "FT","FI","FIA"
CalcTag = "m3/hr"
Case "PT","PI","PIA"
CalcTag = "Bar"
Case "TT","TI","TIA"
CalcTag = "DegC"
Case "LT","LI","LIA", "CV", "FCV", "LCV","PCV", "TCV"
CalcTag = "%"
Case Else
End Select

Process Flow Sheets with ControlDraw

Did you know that ControlDraw can produce Process Flow Sheets that show process flows and the material properties for equipment and lines. This is achieved by using Symbol Data - name value pairs that you can set for each symbol, or by a matrix.
An example and explanation is provided in the latest Sample Models.
And of coure, like pretty well everything in ControlDraw (and unlike say Visio) the data becomes available for use in Queries and even calculations.