Transcript ControlDraw, Modularisation,Standards And Re-Use

ControlDraw, Modularisation,
Standards And Re-Use
Standardised Specification and Modular
Design
How ControlDraw Help
Standardised Specifications and
Modular Design
• An organisation that does large numbers of projects
should have standards that help, and that make each more
efficient than the last one.
• Modular designs are one essential for this, as they can
ensure re-usability within a project and from project to
project.
• Traditionally it is done by having Standard Office
Documents, and a code library.
• How can ControlDraw improve the situation?
• Here in S88 terms are some answers.
Modular Specifications
• ControlDraw designs are inherently modular, the entire
hierarchical structure promotes modular thinking
• Control Modules (such as motor drivers) are generally
represented on one diagram plus one class definition.
• Equipment Modules can be represented in diagrams,
these containing the required control modules as child
diagrams
• The same applies to Units, Phases, Operations etc.
• The physical model diagrams can also define process part
of the HMI Graphics.
Polymorphic Modules
• ControlDraw diagrams can be polymorphic, that is they
can support many variations of a module very efficiently
• This can hugely improve the standardisation within a
project.
• For example you may have three different types of
reactor, all similar but with differences. One has only has
heating, another has heating and cooling, another has an
extra feed.
• All can be defined in the same diagram.
Importing
• You can import into one ControlDraw model any of the
contents of another.
• So, if you have a ControlDraw model containing a
standard collection of modules you can build a new
model from the standard collection in minutes
• However, this is a one way process, if the standard
subsequently changes then the constructed model does
not automatically change too.
• ControlDraw has a far better way.
• It’s called Reference Models
• Linked
models
• Each
provider
owns their
part
• You have
control
view the
Reference
model
Process
supplier A
Process supplier B
Process Zone A
ControlDraw
Area Model
Process design by Process
supplier A
ControlDraw
Area Model
Diagrams
Units and
Operation,
Equipment
Modules
and phases
Tabular data
Standard
ControlDraw
Reference
Model
Procedure control
product standard, eg PLI
Data Classes
Control
System
supplier
Building blocks
Reference Models
Reference Models
• provide
common objects
Reference models
• Reference models are modular standards.
• They do most of the hard work of ensuring standard
designs are followed
• When linking an area model to a reference model :
– The referenced diagrams and matrices are imported into the Area
model
– the Area model classes classes, queries etc are synchronised to
the reference model
• Subsequently, changes in the reference model are
automatically reflected in the area model.
• The use of reference models enables large projects to be
spit into several area models, and one reference model.
How is ControlDraw better than
standard office tools?
• Everything is linked
• Compare and Version controls vastly exceed the desktop
norms
• The classes, diagrams, libraries etc are designed for
control systems.
• Much is built in to improve the document review process,
and Clients can use the free reviewer to see and comment
on models.
• Operators can use it for training and even as a help guide
in the control room.
• Compared with any Word/Excel/Visio specification it is
incredibly quick for finding what you want to know.
Is the database strong enough. What
about SQL server
• ControlDraw uses Access,which is standard on desktops.
• By using reference models large projects are defined
using several area models, and one reference model.
• Each is an Access database.
• Each is relatively small, there is no need for very large
numbers of users working on one database.
• The ability to copy the entire model, and archive a read
only copy, helps with keeping records of changes
How is ControlDraw better than IT
Software tools like UML?
• The diagrams, libraries etc are designed for
control systems.
• The diagrams are familiar and have been used
successfully for decades.
• End users such as process engineers can
understand them
• The data comes out in standard Access tables
Who should build the models?
• It’s up to you. But they need to
– Understand the process they are working with,
– Understand the control systems of course.
– Have a good feel for the software
• The real experts should develop the Reference
model, especially if it is to be used on a large
scale, for example for a corporate standard.
What can advanced users get out of
ControlDraw
• Tag databases, IO Lists, Parameter lists etc come easily.
• There is a lot you more that you can do, here are some
possibilities
– The reference model can the place where all the standard code
modules interfaces are documented.
– Electronic Testing achieved by comparing the model with data
exported from the system
• The model can become the life cycle database for storing
the settings of all the process variables, recipes etc in the
installed system. And for tracking changes made to the
system. Readily adaptable Tools already exist for this
purpose.
You can extend ControlDraw
• As the models are Access Databases, you have the entire
world of VBA etc to add your own functionality.
• For example if you know how to structure files for
importing modules ,you should be able to write programs
to generate the files.
– Perhaps even the graphics, SFC’s etc
• You can make a tool to generate minutes of review
meetings from the Reviewer database.
• The more you use it the more you will be able to do with
it.
ControlDraw
• There’s much more –
• From it’s role in project management
• To the way it improves designers
• www.controldraw.co.uk