4.1: PandID General Information
- Page ID
- 22560
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)Piping and Instrumentation Diagrams (P&IDs) use specific symbols to show the connectivity of equipment, sensors, and valves in a control system. The following sections will outline general information about P&IDs that is necessary to to know before trying to draw one.
P&ID vs. PFD
P&IDs may often be confused with PFDs, or process flow diagram. P&IDs and PFDs generally utilize the same notation for equipment. However, they serve different purposes and provide different information. The purpose of a PFD is to show exactly what a process does during operation, and a P&ID shows all controllers, valve types and the materials that are used in construction. A PFD shows the connectivity and relationships between the major equipment and materials in a process. However, it also includes tabulated design values such as normal, minimum, and maximum operating conditions that a P&ID does not contain. A PFD does not include minor piping systems or other minor components that a P&ID typically includes. The difference between P&IDs and PFDs is that P&IDs typically include more information regarding piping and safety relief valves than process flow diagrams. P&IDs do not contain operating specifications that PFDs contain, such as stream flows and compositions. It is important to note that differences between PFDs and P&IDs will vary between institutions. Most corporations maintain designated standards to create and modify the documents. Both PFDs and P&IDs are controlled documents and need to be maintained with a document control procedure. To see an industrial example of PFD vs P&ID refer to, PFD/PID industry example Wiki Page.
Information Incorporated in P&IDs
The following information is given on a P&ID that is not explicit on a PFD:
- ALL valves and valve types
- Controllers present
- Controller architectures
- Pipe diameters, materials of construction, and insulation properties (including minor piping systems)
- Equipment materials of construction
Uses of P&IDs
- Develop operational methodology
- Develop safety philosophy and safeguards
- Develop control philosophy
- Serve as a basis for control programming
- Serve as a communication document for how the process works
- Serve as a basis for equipment design, pipe design, estimating cost, purchasing
- Use for evaluation of construction process
- Train employees
- Serve as a conceptual layout of a chemical plant
- Provide a common language for discussing plant operations
Characteristics of P&IDs
- Grouped by specific section of plant
- Show the connections between all the sensors and actuators
- A general schematic - NOT a layout and NOT to scale. It should be noted that P&IDs do not specifically imply the following: same elevation of equipment, relative sizes, where valves are located on the equipment, how close equipment is to each other, and impeller types/location. They are also not the same as control or incidence diagrams. This type of information can be seen in either a plant layout drawing (can be either satellite view, showing distance between units, or a slice of building, showing height of units) or construction drawings, such as plant blueprints.
- Must be clear and uncluttered
- Must be systematic and uniform. P&IDs are used extensively in industry to document plant information. These documents need to be easily read by anyone working within the company, and easily explained to anyone else. OSHA audits can occur anytime and it is imperative that operational information can be provided to the auditor when requested. Without standard notation, it would be very difficult to go from plant to plant within your company and understand the P&IDs.
- Are generally highly confidential and have restricted access, as they can be used to replicate a process
What A P&ID Is Not
- Not an architectural diagram of a process (should show the flow of material across the plant floor between sensors and actuators, not necessarily corresponding to a 3D location)
- Does not need to be drawn perfectly to scale
- Does not imply any relative elevations
- Do not need manual switches
- No actual temperature, pressure, or flow data
- Leave out any extensive explanations
What A P&ID should include
- Instrumentation and designations
- Mechanical equipment with names and numbers, and their specifications such as material, insulation, maximum flow rate, working pressure and temperature, maximum power etc.
- All valves and their identifications
- Process piping, sizes and identification
- Miscellaneous - vents, drains, special fittings, sampling lines, reducers, increasers and swagers
- Permanent start-up and flush lines
- Flow directions
- Interconnections references
- Control inputs and outputs
- Interfaces for class changes
- Vendor and contractor interfaces
- Identification of components and subsystems delivered by others
- Intended physical sequence of the equipment
P&ID Revisions
- Revisions should be clearly identified
- Regularly issued to all related employees at each significant change to the process, as well as at benchmark points
- If small changes are made that don't warrant a completely new revision, "red pencil" additions are generally accepted between issues
- 15-20 revisions are typical during process design
- All revisions need to be communicated to EVERYONE so that only the latest revision is used. This is critical in order to avoid serious (not to mention expensive) construction mistakes. (Typically outdated P&ID is discarded to avoid confusion)
How do you generate a P&ID?
P&IDs can be created by hand or computer. Common programs, for both PC and Mac, that create P&IDs include Microsoft Visio (PC) and OmniGraffle (Mac). For creating a P&ID by hand or on a computer, please refer to the P&ID Standard Notation Wiki Page for standard equipment notation as well as computer templates.