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

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
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

83 - History of ControlDraw (Web Page)

Many years ago, in the mid 70's, I began working with Process Control System. It was about the time that the first PLC and DCS systems were coming into use in the Process Industries.
I was an instrument engineer for a major contractor I was responsible for specifying these systems for many plants.
Typically I worked for weeks or months with a pen and a sketch-pad to produce the diagrams and the lists that were needed to specify the systems. Eventually I was spending up to a year on-site following up my designs.

Then the first computers became available to engineers, and I began to use a computer (a Univac) to produce the lists. 

Some time later the first PC's began to arrive in the office (at this time the term PLC was about to be replaced by PC - Programmable Controller, dropping the Logic bit since they had by now become much more than Logic machines.)
Soon after, I was using the PC to produce the specs:
MSDos Graphics like Freelance for diagrams
Manuscript for the Words
Smart (!) for the database and spreadsheets.
I had been using the Univac system for the Instrument and IO Lists for some time, and it was a great improvement to find that I could do all I needed on a 286 in my office rather than having to go to the DP centre to submit and collect batch jobs.
I developed a database that was much more than the simple flat table that most people were using at the time. It even included Functional aspects, such as list of the operations related to the Units, Recipes and so on. However I could not get everything into the database, I still needed diagrams to express things efficiently.

Also, controlling the various files and keeping them in step began to be a big problem, especially with large fast changing project.

When I originally started work on what became ControlDraw with Visual Basic 2 it was going to be a database, with table and text based interface. At the time integrating Databases with VB was not half as easy as it is now, let alone producing diagrams.. The idea of producing any graphics was not in my mind at the time - apart from including a few references in the database to some externally produced diagrams.

It started when I wanted to produce some simple Sequence definitions, and I had the idea of using a few Icons to represent sequence steps, and then it just grew from there. I spent a lot of time thinking about diagrams and came up with a generic model for diagrams, and with a long and hard struggle, including a lot of calls the to Windows API, I managed to get my VB2 program to produce them something like they way that I wanted. That is now ControlDraw1 (Cdraw) - it was finished in VB4.

Since then VB6 has arrived, and component technology has greatly improved. One wonderful OCX control, Addflow3 from Lassalle has made a great difference. It handles all the diagramming graphics, and more, mostly eliminating the need for the API calls and greatly improving on the diagram user interface.


Page Review Status: None Version 417