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

17 - P&ID (Web Page)

A P&ID is a detailed graphical representation of a process including the hardware and software (e.g., piping, equipment, instrumentation) necessary to design, construct and operate the facility. Common synonyms for P&IDs include EFDs (Engineering Flow Diagrams), UFDs (Utility Flow Diagrams) and MFDs (Mechanical Flow Diagrams). See more in Wikipedia

Producing the P&ID's is generally the responsibility of Process Engineers Process Engineers decide on what each P&ID should contai
n but they are usually drafted by CAD technicians.

P&ID's are also used for operation and maintenance of the unit after construction and are retained and used for many years.

P&ID's however have problems when being used for the Control systems information on them.
P&ID standards are very variable from company to company, what is shown and the numbering systems vary enormously
They are often very inaccurate, frequently missing details of control loops, contents of process packages etc.
P&ID's are not object oriented in any way. For example where are several identical units (ie one Unit Object) they still mostly draw one P&ID for each. If you are lucky. Sometimes you will find more than one unit (say 2 and a half) on one P&ID or one unit defined on 2 or more P&ID's!
The instrument database behind typical P&ID software is often inadequate for Control purposes. The text in them is often useless (we know FT means Flow Transmitter, we want to know what the flow is doing!)
P&ID's have a slow development cycle and are almost always out of date apart from the marked up paper one the process engineer has.
P&ID's are not designed for operational purposes, for example they are full of clutter such as nozzle sizes that are not relevant to the control, or even the plant operators.
They are usually a poor basis for control system graphics.
P&ID's totally fail to represent procedural functions

In fact for all but the simplest control loops, additional documentation such as Loop Diagrams are always needed


ControlDraw can be used to produce simple P&ID's - but typically they ultimately need to be drafted in CAD software such as AutoCAD, program that can handle large diagrams with many elements.
Where ControlDraw can have a role with P&ID's is to sketch the main elements before committing them to a CAD program. There are advantages if this is done, for example:
Counts, Equipment lists, instrument indexes etc can all be generated from the contents of the diagrams
Instrument Tag numbers can be assigned automatically


ControlDraw with CAD Process Eng Diagram Flow


Page Review Status: None Version 411