ControlDraw Introduction
Upcoming SlideShare
Loading in...5

ControlDraw Introduction



Do you manage automation projects?

Do you manage automation projects?



Total Views
Views on SlideShare
Embed Views



2 Embeds 15 11 4



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

ControlDraw Introduction ControlDraw Introduction Presentation Transcript

  • ControlDraw Ltd
    • 10 years successful operation
    • Providers of Software plus expert consulting
    • Clients and users around the world
    • Lends money to banks
  • Francis Lovering ControlDraw Ltd 24 years with EPC Technical manager Automation group 10 years ControlDraw Ltd Active and Award winner in World Batch Forum [email_address]
  • (How) Do you?
    • Ensure Automation Systems meet End User needs
      • Must haves, wishes etc
      • Manage User approvals
    • Manage automation projects
      • Design before programming!
      • Track progress
      • Manage changes
    • Ensure Specifications are accurate
    • Define the Modularisation of a system
      • S88 etc
  • ControlDraw Introduction
    • Software for Specifying and Designing Automation systems
    • Hierarchical and Graphical Object models
    • Discrete, S88 batch and Continuous control
    • High definition Specifications for the entire Life Cycle
    • Improves User understanding
    • Improves Project Management
    • Reduces errors
    • Accelerates development
  • ControlDraw Description
    • Uses a Hierarchical and Graphical object modelling approach
    • Appropriate Diagrams for all modules
    • Includes State oriented objects and methods
    • Includes simulation, verification and more
    • A ControlDraw model is database
      • Tables automatically generated from the contents of diagrams
      • Advanced data population
  • Advantage of graphical specifications
    • (Good) Diagrams are much less ambiguous than text
    • User understanding is improved
      • New Users may need a few hours of training
      • Then User approval is more meaningful
      • And traceable
  • Graphical Objects
    • Diagrams show the Objects in a process
    • Diagram Symbols can be much more than pictorial, they can be S88 Objects corresponding to the S88 entities
      • Recipe Procedures, Units Equipment modules, Control Modules etc
  • Hierarchical
    • Objects can contain objects, by linking an object to a Child Diagram
    • This is recursive so allowing hierarchies that match the S88 Physical and Procedural Models
  • Object properties
    • Class
      • Extended S88 types
        • Eg Unit, EM, CM
      • Data structure for instance data
    • Data
      • Symbols can contain data
      • This can cascade down the hierarchy (inheritance)
  • Object Instances
    • ControlDraw scans a model to create records for all object instances
    • Each Class has configurable database tables
    • These can match PLC and DCS structures
  • Diagrams
    • Process Cells
  • Diagrams
    • Units,
  • Diagrams
    • Equipment Modules
  • Diagrams
    • SFC – Sequential Function Charts
      • for Phases and Operation (Equipment Procedural Entities)
  • Diagrams
    • PFC –Procedure Function Charts
      • For Recipe Procedures, Recipe Unit Procedures, Recipe Operations
  • Diagrams
    • SAMA, Logic
      • For Control Modules
  • States and state matrices
    • All objects in a model can have States
    • These can be related to each other.
    • An SFC action can set the state of an object
    • A State Matrix can be built relating for example Equipment Module to Control Module states
  • Simulation
    • Many Diagrams types can be put into simulation mode
    • Test Control Strategies
  • S88 Procedure to Equipment Linking
    • The Recipes can be linked to the equipment by referencing Recipe Procedural elements to Equipment Procedural elements
  • Build libraries of modules.
    • Diagrams can be re-used in multiple models
    • Reference model contains the shared diagrams
    • Reference model also defines the classes
    • Diagrams can be made polymorphic so the one diagram can cover a number of similar modules
  • Version Controls
    • Everything in a model has a version number:
      • Diagrams
      • Classes
      • Matrices
      • Data
    • Compare facilities provide details on all changes
  • Comparison with P&ID CAD systems
    • Products like SmartPlant and Comos have some capability
    • But only a small portion of the scope of ControlDraw models
  • What can a Project manager get out of ControlDraw?
    • High quality System Independent Specifications
      • Provide traceable estimates
      • Can be for implementation in-house or externally by a third party
      • With design control retained even when using third party
    • Proposal Models
      • Estimates
      • Initial client approval
    • Project Control
      • Continual Scope Measurement
      • Change Tracking
      • Built in features such as Diagram Review Status help
  • What expertise must my engineers have?
    • Not all need the same level
    • Some might just do the simpler things
      • P&ID based tasks for example to take a P&ID and make a ControlDraw diagram
    • Experts can then develop the model
      • It is possible to quickly make major changes and even restructure models without losing the value of the work already done
    • CD includes Model Review and Advisor functions
      • To check for consistent models and much more
  • The ControlDraw Reviewer
    • View, navigate, and print the contents of a ControlDraw model
    • Make comments on the diagrams and matrices
    • Make compare reports that show all changes between model versions
    • Extract all data from models
    • Can be used for online documentation
  • Opportunities
    • Get in at the beginning of projects
      • Develop System independent models
      • Focussed on end user requirements
    • in the recession
      • Clients may scale back or postpone projects
      • But often they keep a small front end going
  • System Development One Page
  • Concluding
    • The more you do with ControlDraw, the more you can get out of it
    • Examine all the documents you produce outside CD
      • Can they be done With CD?
      • If not then maybe improvements to ControlDraw can be made