ControlDraw
This web was generated automatically from a sample ControlDraw model.
Move the mouse over the diagram area - you can click on the objects that have numbers by them to go to the detailed diagram for the object. It is a bit like using ControlDraw (but that is much more powerful!)
More Sample models    Go to ControlDraw.co.uk


List of Diagrams
[First] [Previous]][Next][Last]
001 - index
002 - About Process Control
003 - Your Business
004 - For Manufacturers
005 - For EPC Companies
006 - For Systems Integrators
007 - For DCS/PLC suppliers
008 - Education
009 - Process Operation
010 - Process Control Systems
011 - Automation Software Design
012 - Functional Design
013 - S88 Links
014 - Process Design
015 - Design Documents
016 - FRS
017 - P&ID
018 - Process Descriptions
019 - SDS
020 - URS
021 - PCS Graphic
022 - Engineers
023 - For DCS/PLC Programmers
024 - For Automation Engineers
025 - For Process Engineers
026 - Process Eng Diagram Flow
027 - For Project Managers
028 - Project Management ControlDraw
029 - For Instrument Engineers
030 - Automation Design
031 - Requirements Analysis Process
032 - Instrument Engineering
033 - Diagrams
034 - Logic Diagrams
035 - Control Loops
036 - PFC
037 - Process Flow Diagram
038 - Sequential Function Charts
039 - State Transition Diagrams
040 - Polymorphic
041 - Controldraw Software
042 - Automation Models
043 - Hierarchical Objects
044 - Database
045 - IO List
046 - Data lists
047 - S88 Models
048 - S88 Recipes
049 - S88 Physical Model
050 - Process Cells
051 - Units
052 - Equipment Modules
053 - Control Modules
054 - S88 Procedures
055 - Recipe Procedure
056 - Unit Procedure
057 - Operation
058 - Phase
059 - State Matrices
060 - State Based Control
061 - Control Design Reviews
062 - ControlDraw Reviewer
063 - Overview
064 - Why Controldraw
065 - FAQ
066 - CONTROLDRAW COMPARED
067 - Main Screen
068 - Matrix Screen
069 - Life Cycle
070 - Life Cycle and Models
071 - Specifications
072 - Functional Requirements Spec
073 - Functional Design Specification
074 - User Requirements
075 - Support
076 - Download
077 - Standards
078 - Services
079 - About Web Site
080 - ControlDraw Prices
081 - History
082 - History of Control
083 - History of ControlDraw
084 - History of S88
085 - History of Diagrams
086 - Documentation for the Life Cycle
087 - Large distributed projects
088 - System Development Structure
089 - The RTF Editor
090 - ControlDraw with CAD
091 - Web Layout
092 - Prototyping Partnership
093 - All pages
094 - IEC1131
095 - OnePageOverview

66 - Controldraw Compared (Web Page)

Evaluation Key points
This is a short collection of points that you may wish to consider when evaluating ControlDraw against it's competitor.
Top Levels of the Models
Process Cell, Area etc. In ControlDraw these are very good for navigating models and forming the basis of the higher level overview type graphics in a system.
Recursion
ControlDraw supports Phases in Phases, Control modules in Control modules and similar recursive structures that the S88 guidelines identify. This was a key reason why one user who evaluated both chose ControlDraw.
Free Viewer
With ControlDraw, users and operators etc can navigate and comment on CD models using the reviewer without having a license.
State matrices
A very powerful feature of ControlDraw is the State matrix capabilities
Variants
This is another very important part of ControlDraw whereby one object (eg Unit, Equipment Module, Control Module) can be designed to cover a number of similar objects. For example two similar units where one has a jacket and the other does not can be defined in a single polymorphic object. You can see some of these in the Milkshake demonstration model.
P&ID's
One competitor depends on 'good' P&ID's - ie ones designed with S88 in mind. Often this is not the case.
And where are several similar P&ID's do you have to do more work to add the EM's and CM's to each of these P&ID's?
With ControlDraw you just draw it once and then define the differences in a Variants table. And if a change is made you make it once and it applies to all.
Another problem with using the P&ID's is that these tend to be subject to a slow development process.
Database
ControlDraw uses Access - remember ControlDraw is a life cycle product and can/should be used to maintain the documentation even after the system is delivered, meaning that the software works in the standard desktop environment, on standalone PC's and Laptops etc.
Code Generation
ControlDraw does not generate PLC code, however it can generate complete tag databases for import into PLC/SCADA or DCS products. There are also issues with auto-generated code. For example, does the code generated use the full capabilities of the actual system? If code has to be changed, does what take seconds in the system software development environment take much longer if the source model has to be changed and the code re-compiled? All that said, there is scope to use the model to auto-generate some of code - contact ControlDraw for details
System
ControlDraw is not tied to any of the major suppliers of systems -although the working relationship is good.

Web Export
ControlDraw model as a web site - see examples this can help in the operational phase of plants by enabling users to explore the application without having ControlDraw installed.



Page Review Status: None Version 116