Whitt2003.book Page iii Thursday, July 10, 2003 4:05 PM
Successful
Instrumentation and Control Systems Design Michael...
2176 downloads
4912 Views
17MB Size
Report
This content was uploaded by our users and we assume good faith they have the permission to share this book. If you own the copyright to this book and it is wrongfully on our website, we offer a simple DMCA procedure to remove your content from our site. Start by pressing the button below!
Report copyright / DMCA form
Whitt2003.book Page iii Thursday, July 10, 2003 4:05 PM
Successful
Instrumentation and Control Systems Design Michael D. Whitt
Whitt2003.book Page iv Thursday, July 10, 2003 4:05 PM
Notice The information presented in this publication is for the general education of the reader. Because neither the author nor the publisher have any control over the use of the information by the reader, both the author and the publisher disclaim any and all liability of any kind arising out of such use. The reader is expected to exercise sound professional judgment in using any of the information presented in a particular application. Additionally, neither the author nor the publisher have investigated or considered the affect of any patents on the ability of the reader to use any of the information in a particular application. The reader is responsible for reviewing any possible patents that may affect any particular use of the information presented. Any references to commercial products in the work are cited as examples only. Neither the author nor the publisher endorse any referenced commercial product. Any trademarks or tradenames referenced belong to the respective owner of the mark or name. Neither the author nor the publisher make any representation regarding the availability of any referenced commercial product at any time. The manufacturer’s instructions on use of any commercial product must be followed at all times, even if in conflict with the information in this publication. Copyright © 2004 ISA – The Instrumentation, Systems, and Automation Society All rights reserved. Printed in the United States of America. 10 9 8 7 6 5 4 3 2 ISBN 1-55617-844-1 No part of this work may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written permission of the publisher. ISA 67 Alexander Drive P.O. Box 12277 Research Triangle Park, NC 27709
Library of Congress Cataloging-in-Publication Data is in process. Whitt, Michael D. > Successful instrumentation and control systems design / Michael D. > Whitt. > p. cm. > Includes bibliographical references and index. > ISBN 1-55617-844-1 (Paperback) > 1. Automatic control. 2. Engineering instruments. I. Title. > TJ213.W44 2003 > 629.8--dc21 > 2003011366
Whitt2003.book Page v Thursday, July 10, 2003 4:05 PM
Acknowledgements I’d like to thank Charlie Thompson for helping me get started in the systems integration business. Sometimes you need someone who’s willing to take a chance on you, and, for me, Charlie was that person. I also thank my many friends in the professional community here in Knoxville: the folks at Raytheon—now Lauren Engineers and Constructors, Inc.—with whom I worked for 15 years, and the wonderful team at Mesa. Thanks to Greg, Mike, Rodney, and anyone else who I forgot to mention who helped me by reading and commenting. Any mistakes are mine—not theirs. Also thanks to Edgar and Johnny for their help with the construction section (Part I); to Tony Pyano—a wordsmith; and to Lori Thompson, a wonderful design engineer, P.E., and friend, who wrote the section on instrument specifications (Part III). And, of course, to my friends at ISA who helped shepherd this project to its conclusion – thanks.
Whitt2003.book Page vii Thursday, July 10, 2003 4:05 PM
Dedication I would like to dedicate this book to My wife Mary and son Elliot, who have continually supported me through the travails of writing this book—I’m truly blessed; My parents, who instilled in me a love for reading, and, by extension, writing; and My God, through whom all things are possible.
Whitt2003.book Page xiii Thursday, July 10, 2003 4:05 PM
List of Figures Part I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Figure 1. Success triangle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Figure 2. Effects of constraints on project structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Figure 3. Typical industrial project flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Figure 4. Startup readiness report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Figure 5. Typical I&C project flow diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Figure 6. One form of a customer’s project team (dashed boxes are external) . . . . . . . . . . . . . . . 29 Figure 7. Engineering design team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Figure 8. Construction team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Figure 9. Calculating efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Part II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Figure 1. Typical error pattern caused by deadband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Figure 2. Typical error pattern caused by hysteresis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Figure 3. Conversion problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Figure 4. Data translation process - from field device to HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Figure 5. Signal conversion at PLC input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Figure 6. Engineering unit calculation at the HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Figure 7. Typical document handling process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Figure 8. Typical instrumentation database management cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Figure 9. Form-A contact set (SPST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Figure 10. Form-B contact set (SPST) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Figure 11. Form-C contact set (SPDT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Figure 12. 2-Pole relay (shown in shelf-state) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Figure 13. Common types of switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Figure 14. Make-before-break . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Figure 15. Break-before-make . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Figure 16. Interval timer timing diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Figure 17. T.D.O.D. timer timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Figure 18. T.D.O.E. timer timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Figure 19. Sample ladder elementary format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Figure 20. Defining the cable route (wire W1, Route C1/T1/T2/C2/C2a) . . . . . . . . . . . . . . . . . 72 Figure 21. Sample cable schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Figure 22. Sample conduit schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Figure 23. Typical instrument arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Figure 24. Typical cabling scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Figure 25. Interconnection wiring example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Figure 26. Failsafe interlock chain (devices shown in shelf state) . . . . . . . . . . . . . . . . . . . . . . . . . 77 Figure 27. Hazardous boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Figure 28. Basic discrete (digital) circuit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Figure 29. Discrete circuit wiring technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Figure 30. Simple switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Figure 31. Sourcing switch with sinking load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Figure 32. Sinking switch with sourcing load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Figure 33. Current-sourcing digital input module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Figure 34. Current-sinking digital input module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Figure 35. Isolated digital output module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Figure 36. Current-sourcing digital output module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Figure 37. Current-sinking digital output module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Figure 38. Analog circuit wiring technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Whitt2003.book Page xiv Thursday, July 10, 2003 4:05 PM
xiv
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
Figure 39. Analog wiring methods: 2-wire vs. 4-wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Figure 40. The cognitive cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Figure 41. Typical control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Figure 42. Control system elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Figure 43. Typical control scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Figure 44. Typical control scheme and process controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Figure 45. Graphical User Interface (GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Figure 46. Graphical user interface with pushbutton configuration template . . . . . . . . . . . . . . 105 Figure 47. Trend screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Figure 48. Typical PLC rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Figure 49. PLC program scan patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Figure 50. Sequential function chart washing-machine sequence control application . . . . . . . 117 Figure 51. Continuous function chart washing-machine temperature control application . . . 118 Figure 52. Control detail sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Figure 53. Suggested program flow of control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Figure 54. I/O tally worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Figure 55. Revised I/O tally worksheet reflecting new setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Figure 56. I/O tally worksheet with split by I/O type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Figure 57. Remote I/O network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Figure 58. Project sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Part III . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Figure 1. Instrumentation and controls engineering tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Figure 2. Typical feed tank configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Figure 3. Typical P&ID symbology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Figure 4. Typical P&ID symbology showing combined computer functions. . . . . . . . . . . . . . . 143 Figure 5. TK-10 controls P&ID presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Figure 6. Basic P&ID drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Figure 7. TK-10 feed tank with device labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Figure 8. TK-10 Feed Tank area equipment arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Figure 9. Sample scope of work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Figure 10. Existing control system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Figure 11. New control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Figure 12. List of tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Figure 13. Document control table structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Figure 14. OrderDrawingsQuery (design view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Figure 15. Document control table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Figure 16. Transmittal query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Figure 17. Transmittal query design view (with criteria filter). . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Figure 18. Transmittal query data table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Figure 19. Instrument and I/O list table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Figure 20. Tagname update query, design view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Figure 21. Tagname update query, design view, with criteria filter . . . . . . . . . . . . . . . . . . . . . . 163 Figure 22. Query tagname display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Figure 23. Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Figure 24. Report wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Figure 25. P&ID takeoff query report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Figure 26. P&ID takeoff query report, design view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Figure 27. Finished database products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Figure 27. (continued) Finished database products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Figure 28. Cover sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Figure 29. Devices worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Figure 30. Devices I/O assignment index table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Figure 31. Devices I/O assignment index, revised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Figure 32. Devices I/O calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Whitt2003.book Page xv Thursday, July 10, 2003 4:05 PM
LIST OF FIGURES
xv
Figure 33. Count worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Figure 34. Background data table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Figure 35. I/O configuration worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Figure 36. Labor worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Figure 37. Direct engineering labor, phase one . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Figure 38. Direct engineering labor, phase two. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Figure 39. Indirect engineering labor, phase two . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Figure 40. Engineering and construction labor, phase three . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Figure 41. Engineering summary worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Figure 42. Project cost summary table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Figure 43. Engineering cost summary table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Figure 44. Phase-one deliverables summary table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Figure 45. Phase-two deliverables summary table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Figure 46. Instrument and I/O summary table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Figure 47. Schedule worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Figure 48. Design schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Figure 49. Project man-hour loading chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Figure 50. Systems integration services checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Figure 51. Existing control system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Figure 52. New control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Figure 53. TK-10 feed tank control sequence overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Figure 54. Sequential function chart fragment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Figure 55. Sample sequential function chart logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Figure 56. Sequential function chart (SFC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Figure 57. Continuous function chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Figure 58. Sequence step 2: “fill tank” sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Figure 59. Sequence step 5: “empty tank” sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Figure 60. Pump PP-10 motor controls elementary wiring diagram . . . . . . . . . . . . . . . . . . . . . . 202 Figure 61. Pump PP-10 device control detail sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Figure 62. HV-13 fill valve device control detail sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Figure 63. Sample logic format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Figure 64. Logic diagram showing rat holes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Figure 65. Naming conventions for this project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Figure 66. Timing diagram for a delay timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Figure 67. FILL_TK10 control logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Figure 68. EMPTY_TK10 control logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Figure 69. Device logic for TK-10 fill controls and analog alarms . . . . . . . . . . . . . . . . . . . . . . . . 209 Figure 70. PP-10 device logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Figure 71. PP-10 device on/off logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Figure 72. OSR: one-shot, rising edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Figure 73. Pump restart inhibit signal processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Figure 74. Sample logic diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Figure 75. Selected SAMA symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Figure 76. SAMA control diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Figure 77. Animation plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Figure 78. Preliminary screen graphics, TK-10 overview screen. . . . . . . . . . . . . . . . . . . . . . . . . . 220 Figure 79. Sample control overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Figure 80. Pop-up overlays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Figure 81. Animation detailing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Figure 82. Pump PP-10 control overlay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Figure 83. Animation chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Figure 84. Final screen diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Figure 85. Typical data progression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Figure 86. HMI screen, pumping out in manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Figure 87. HMI screen, filling in auto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Whitt2003.book Page xvi Thursday, July 10, 2003 4:05 PM
xvi
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
Figure 88. HMI screen, sequence status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Figure 89. Sample alarm manager database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Figure 90. Historian sampling points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Figure 91. Simple network single-line diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Figure 11. New control system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Figure 92. Hardware addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Figure 93. Software addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Figure 94. Adding the I/O modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Figure 95. Document control table, design view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Figure 96. Document control table, datasheet view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Figure 97. Document control table, order drawings query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Figure 98. Transmittal query, design view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Figure 99. Transmittal query, datasheet view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Figure 100. Transmittal report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Figure 101. Instrument and I/O list table, design view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Figure 102. Instrument and I/O list database, datasheet view . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Figure 103. Preliminary design query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Figure 104. Plan drawing takeoff query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Figure 105. Plan drawing component schedule (Microsoft® Access to Microsoft® Excel) . . . 243 Figure 106. PlanDwgTakeoffQuery report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Figure 107. Document cross-reference (X-ref) query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Figure 108. Document cross-reference report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Figure 109. Ultrasonic level transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Figure 110. Instrument specification for LT/LSH/LSL-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Figure 111. Instrument specification for PV-48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Figure 112. Three termination room configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Figure 113. Sample instrument location plan drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Figure 114. Instrument location plan design. Step one: initialize drawing. . . . . . . . . . . . . . . . . 261 Figure 115. Instrument location plan design. Step two: locate major equipment items . . . . . . 262 Figure 116. Instrument location plan design. Step three: locate instrument items . . . . . . . . . . 263 Figure 117. Instrument location plan design. Step four: add instrument stations . . . . . . . . . . . 264 Figure 118. PlanDwgTakeoffQuery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Figure 119. PlanDwgTakeoffQuery, filtered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Figure 120. 3D to 2D and back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Figure 121. Instrument location plan design. Step five: add conduit detail . . . . . . . . . . . . . . . . 267 Figure 122. Cable area fill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Figure 123. Cross-sectional views of cable orientation before, during, and after a conduit bend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Figure 124. Conduit facts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Figure 125. Conduit sizing calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Figure 126. Recommended conduit tagging convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Figure 127. Instrument arrangement with support data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Figure 128. Cable code cross-reference chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Figure 129. Component schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Figure 130. Plan001 component schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Figure 131. Cable and conduit takeoff approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Figure 132. Step one: cable takeoff method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Figure 133. Conduit sizing calculator results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Figure 134. Cable takeoff by leg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Figure 135. Conduit takeoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Figure 136. Instrument conduit installation detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Figure 137. Electrical installation detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Figure 138. Instrument mechanical hookup detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Figure 139. Instrument mechanical detail with throttling valve. . . . . . . . . . . . . . . . . . . . . . . . . . 280 Figure 140. Instrument mounting detail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Whitt2003.book Page xvii Thursday, July 10, 2003 4:05 PM
LIST OF FIGURES
xvii
Figure 141. Database log of details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Figure 142. Wiring design basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Figure 143. Fabrication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Figure 144. Wiring interconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Figure 145. Elementary wiring diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Figure 146. Typical instrument elementary content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Figure 147. 4-pole relay coil with contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Figure 148. Four-pole relay coil with cross-references to its contacts . . . . . . . . . . . . . . . . . . . . . 287 Figure 149. Pole-4 relay contacts with cross-reference to its coil . . . . . . . . . . . . . . . . . . . . . . . . . 288 Figure 150. Motor elementary wiring diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Figure 151. Motor elementary wiring diagram showing fused transformer output . . . . . . . . . 289 Figure 152. AC power distribution elementary wiring diagram . . . . . . . . . . . . . . . . . . . . . . . . . 291 Figure 153. AC power panel loading chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Figure 154. DC power distribution elementary wiring diagram . . . . . . . . . . . . . . . . . . . . . . . . . 292 Figure 155. Instrument elementary wiring diagram concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Figure 156. Traditional ladder elementary – washing machine application. . . . . . . . . . . . . . . . 294 Figure 157. “Unhide Columns” window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Figure 158. Instrument and I/O list table, filter by selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Figure 159. PLC digital input module elementary wiring diagram. . . . . . . . . . . . . . . . . . . . . . . 296 Figure 160. Filtered on DOI (digital output, isolated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Figure 161. Digital output (isolated) PLC output module elementary wiring diagram . . . . . . 298 Figure 162. Loop sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Figure 163. Advanced filter/sort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Figure 164. Advanced filter/sort, field selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Figure 165. Results of advanced filter/sort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Figure 166. Creating a connection diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Figure 167. Terminal strip creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Figure 168. Instrument elementary diagram, digital input module. . . . . . . . . . . . . . . . . . . . . . . 303 Figure 169. Instrument elementary diagram, digital output module . . . . . . . . . . . . . . . . . . . . . 304 Figure 170. Termination Drawing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Figure 171. Termination Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Figure 172. Motor elementary fragment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Figure 173. Finished Termination Chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Figure 174. Junction box wiring diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Figure 175. Inner Panel, Cabinet TC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Figure 176. DC wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Figure 177. Wiring diagram section of TC-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Figure 178. AC power distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Figure 179. LT-10 power feed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Figure 180. Wire runs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Figure 181. Fuse/terminal numbering sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Figure 182. NFPA wire color scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Figure 183. TC-2 wiring color scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Figure 184. TC-2 PLC cabinet connection diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Figure 185. Partial junction box diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Figure 186. Partial motor elementary wiring diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Figure 187. Power distribution information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Figure 188. Pressure control loop PIC-48 loop sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Figure 189. Ladder diagram for discrete modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Figure 190. Document control table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Figure 191. Document control table and instrument and I/O list table . . . . . . . . . . . . . . . . . . . 320 Figure 192. Instrument and I/O list table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Figure 193. Terminal block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Figure 194. Setting up a scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Figure 195. Initial layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Whitt2003.book Page xviii Thursday, July 10, 2003 4:05 PM
xviii SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
Figure 196. Single-door enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Figure 197. Function box with bill of materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Figure 198. Finished panel arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Figure 199. Typical purchasing cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Figure 200. Bulk materials takeoff worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Figure 201. Wire and cable calculation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Figure 202. Terminations and cabinetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Figure 203. Conduit and conduit fittings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Figure 204. Installation detail assignment data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Figure 205. New detail sheet tally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Figure 206. Material tabulation by detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Figure 207. Consolidated material with detail quantity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Figure 208. Total item quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Figure 209. Part number and price . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Figure 210. Final bill of materials worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Figure 211. Sort by description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Figure 212. Engineering bill of materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Whitt2003.book Page ix Thursday, July 10, 2003 4:05 PM
Table of Contents List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Part I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Introduction—Part I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Chapter 1: The Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 A. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 B. Predictability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 C. Project Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 D. Project Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 E. Project Deliverables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Chapter 2: The Project Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 A. The Customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 B. The Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 C. The Constructor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Chapter 3: The Managed Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 A. Scope of Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Estimate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35 40 41 42
References—Part I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Part II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Introduction—Part II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Chapter 4: Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 A. Definition of Key Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 B. Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 C. Resolution Effects on Accuracy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 D. Instrument Range versus Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 E. Instrument Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 F. Linearization and Unit Conversions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 G. Practical Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Chapter 5: Design Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 A. Introduction to Information Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Types of Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Basic Wiring Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Failsafe Wiring Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E. Hazardous Area Classification and Effects on Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . F. Wiring to the Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G. Design Practice Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59 61 65 76 78 83 95
Whitt2003.book Page x Thursday, July 10, 2003 4:05 PM
x
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
Chapter 6: The Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 A. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 B. The Cognitive Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 C. Control System Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 D. Process Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 E. Programmable Logic Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 F. Networking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 G. Systems Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 H. Specifying a PLC/HMI System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 References—Part II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Part III . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Introduction—Part III . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Chapter 7: Piping and Instrumentation Diagrams (P&IDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 A. General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Practical Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E. P&ID Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141 141 142 144 146
Chapter 8: Links to Mechanical and Civil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 A. Equipment Arrangement Drawing (Civil and Mechanical). . . . . . . . . . . . . . . . . . . . . . . B. Piping Drawing (Mechanical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Pump and Equipment Specifications (Mechanical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Links Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
147 149 149 150
Chapter 9: Preliminary Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 A. Development of a Detailed Scope of Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 B. Control System Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 C. Project Database Initialization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 D. Estimate and Schedule Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 E. Preliminary Engineering Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Chapter 10: Systems Integration (Control System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 A. Division of Labor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Develop a Control Logic Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Operator Interface Specification Development—HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . E. Network Single-Line Diagram Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F. Other Systems Integration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G. Systems Integration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
183 185 186 216 228 228 235
Chapter 11: Project Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 A. Document Control Table with Related Queries and Reports. . . . . . . . . . . . . . . . . . . . . . 237 B. Instrument and I/O List Table with Related Queries and Reports . . . . . . . . . . . . . . . . . 240
Whitt2003.book Page xi Thursday, July 10, 2003 4:05 PM
TABLE OF CONTENTS
xi
Chapter 12: Instrument Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 A. Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
248 250 250 254
Chapter 13: Physical Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 A. Control Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Termination Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Process Area (Instrument Location Plan) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Instrument Installation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E. Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
255 256 258 277 282
Chapter 14: Instrument and Control Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 A. Instrument Elementary (Ladder) Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Loop Sheet (Ref: ANSI/ISA-5.4-1991) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Connection Diagrams (Ref: NFPA79) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Wiring Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
285 298 301 314
Chapter 15: Panel Arrangements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 A. Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 B. Junction Box JB-TK10-01 Arrangement Drawing ARR-002 . . . . . . . . . . . . . . . . . . . . . . . 324 C. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Chapter 16: Procurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 A. Typical Purchasing Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Material Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Bulk Electrical Bill of Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Bulk Mechanical Bill of Materials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E. Procurement Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
331 333 333 337 343
Chapter 17: Quality Control—The Integrated Design Check . . . . . . . . . . . . . . . . . . . . . . . . . . 345 A. Administrative Content—Individual Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Technical Content—Squad Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C. Squad-Check Roster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Design Check Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
345 345 346 346
Chapter 18: Phase Three—Construction Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 A. Construction Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B. Adjustment of Document Package to Reflect Construction Modifications . . . . . . . . . . C. Issue for Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D. Phase III Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
349 351 351 351
References—Part III . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Whitt2003.book Page xix Thursday, July 10, 2003 4:05 PM
Preface This book began over a decade ago when, as a department supervisor at Raytheon Engineers and Constructors, I started a regular “lunch and learn” training program. Over time, my lesson plans evolved into this book, which now encompasses a broad spectrum of design issues. My purpose in conducting that training was to provide perspective; to help broaden my design group—and myself—by exploring different facets of the I&C design profession. It is my belief that to be efficient, a design team must be able to respond to unusual situations instantaneously, without much conscious thought. To, in fact, be able to anticipate troublesome issues before they arise. In our business, “conscious thought” takes the form of a design meeting or interruption in the flow of the design process. How much better would it be if the situation were handled real-time or even ahead of time at the lowest level possible on the design floor? Don’t misunderstand: I realize that such interruptions will never be totally eliminated. The I&C profession is far too dynamic for that. But, they can certainly be reduced. My goal, for example, is to ensure that every member of the department from the clerk to the lead engineer is fully aware of the issues at hand. Having “situational awareness” is a valuable and difficult to attain trait that gives the individual the confidence and ability to make good decisions. Situational awareness comes only from having perspective beyond one’s current level of responsibility. That is the thought behind this book: to provide perspective. No other book on the market really attempts to describe the business of Instrumentation and Controls design from ground level. From the design supervisor's perspective, this book will do just that. The book is divided into three parts: Part I is about the business end of design engineering. What is a project? Who participates? What is their role? What are some of the key issues relating to project management? Part II focuses on the I&C design basis, laying the foundation for Part III by describing some of the requisite standards and practices and some of the basic design concepts that are needed. Part III then takes a specific design problem and applies good design practice to its resolution, generating a full suite of design products along the way. Who should read this book? Frankly, this book has something for virtually anyone in the Instrumentation & Controls business or thinking of getting into it. The book's topical format—as shown in the Table of Contents—makes it useful as a desk reference. Some of the sections are very detailed, while others merely hit the high points. It does, after all, reflect the author’s personal experience. The book is aimed at the maintenance engineer in a plant who has not been exposed to capital project work; to the process or mechanical engineer who finds it difficult to communicate with the I&C staff; to the junior designer who needs something extra to put him or her on the path to a successful career; and to the design supervisor, who would like to get some additional tools and ideas about how to manage a project and train people. Along those lines, a CD-ROM, which is available separately or with the book (see page 355), is a great resource for training courses and presentations as most of the figures embedded in the book are presented in their “raw” Microsoft® Excel format, ready to be used as-is or “tweaked” to fit a particular need. Called Software Tools for Successful Instrumentation and Control Systems Design, the CD-ROM also includes a Microsoft® Excel-based estimating/scheduling tool. Design is frequently more of an art than a science. There will be some who take issue with some of the solutions presented here, having developed other methods of their own that are, perhaps, better. But, the design solutions presented here are proven and provide the keys to a successful project. And, if you believe, as I do, that the best-learned lessons are those learned “in the trenches”, then this book is for you! Best Regards, Michael D. Whitt
Whitt2003.book Page 5 Thursday, July 10, 2003 4:05 PM
Chapter 1: The Project A. Introduction Project: A project is a temporary activity whose purpose is to create a product or service. Temporary projects have a defined beginning and end. Projects usually involve a sequence of tasks with definite starting and ending points. These points are bounded by time, resources, and end results.1 Project Engineering: 1. Engineering activities associated with designing and constructing a manufacturing or processing facility. 2. Engineering activities related to a specific objective such as solving a problem or developing a product.2 An engineering project is a means to an end. For a project to exist, there must be a perceived need and an expectation that the need can be met with a reasonable investment. The owner must weigh the risks against the rewards and conclude that the project is worthwhile. Making that risk/ reward assessment is sometimes more of an art than a science. Every project involves some level of risk. All pilots take chances from time to time, but knowing—not guessing—about what you can risk is often the critical difference between getting away with it and drilling a fifty-foot hole in mother earth. —Chuck Yeager, 1985.3 More than in most endeavors, the effects of mishandling risk in process engineering projects can be catastrophic. Beyond the economic ramifications of a poor estimate, which are bad enough, the potential risk to the operators and the public at large can be extensive. Therefore, a well-conceived process of preliminary evaluation and project control is necessary. This evaluation begins with a thorough understanding of the issues. Like General Yeager, the key is to know, not to guess. Risk management has three components—assessing, planning and managing risk—that will affect the project timeline, scope, or budget.4 The true keys to project (risk) management are knowledge, experience, and forethought. Each member of the project team needs to have a thorough knowledge of the issues. What is a project? What are some of the outside influences on how a project is executed? How does a project flow from inception to implementation? What are the typical products and services to expect from an I&C service provider? This chapter attempts to answer these questions by discussing the following major topics: • • • •
Predictability. What type of project is it? Deterministic or probabilistic? Project structure. What are some of the most common project types? Project flow. How is a project executed? Project deliverables. What deliverables are typical for an I&C design project?
B. Predictability One of the most important project variables is the level of predictability. How many times have the various members of the project team been exposed to similar projects? Have similar projects even been done before? From the customer’s perspective, proper performance from the engineering team
Whitt2003.book Page 6 Thursday, July 10, 2003 4:05 PM
6
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
is of paramount importance. It is the engineering team’s job to identify and assess the areas of risk during the process of building a project scope, estimate, and schedule. The customer relies on the engineering firm to partner with him in flagging potential problems and devising ways to reduce the financial and physical risks inherent in the project. Still, even after a rigorous investigative process, unknowns will remain and assumptions will have to be made that will leave weaknesses in the plan. To reduce customer anxiety and their financial risk, the engineering provider should employ a scientific investigative approach. This scientific approach should begin with a detailed scope of work that discusses risk-related issues and then continue through the construction of an estimate that is based on hard data. All too often, the project estimate is done on the back of an envelope that is then discarded after the submittal, or is too vague. This reduces the chance for reflection after the project and inhibits the ability of the design team—both the engineering side and the customer side—to take advantage of lessons learned. After the project is in the execution phase, the risk factors identified previously should be closely monitored. The trick for the customer is to find service providers who understand these processes and can adapt them to specific circumstances. Fortunately, most industrial project life-cycles are similar in structure. When a new need is identified in the process controls world, a process is begun that is, for the most part, predictable from one project to the next. The customer has a predictable process to follow to get the project approved. The engineer has a predictable process to follow to prepare a bid. These processes are sometimes adapted to meet unexpected or unusual conditions. But, for the most part, the engineering “process” that takes an idea from conception to implementation is consistent. Such a process lends itself to a deterministic management approach, as opposed to a probabilistic approach, which is used for unique processes. Given the predictability of the process, it would be easy to assume that the interrelationships between customer and service provider would be consistent from one project to the next. This is not necessarily the case. External pressures such as market forces may force changes in strategy. Many of these differences can be traced to the contractual relationships that are established between the customer and the engineering provider. These relationships reflect the risk/reward aspects of the projects and, as a result, must be given full consideration when setting up the project. The following sections of this chapter explain the various structures that affect the execution strategy of a project. Is the project time-driven or cost-driven? Is the project fixed-cost or cost-plus? How do these structures affect the execution of the projects? Later sections of this chapter deal with the execution of the project. How does a project develop? Where do you start, and what is the best process to follow? What set of deliverables should be expected from the I&C design team?
C. Project Structure The structure of a project has a great bearing on the way the project is executed. This is because each member of the project team defines success from its own unique perspective, as viewed through the prism of the project parameters. From the customer’s point of view, success is achieved when the desired end is achieved within the time allotted and/or the funds allocated. This is likely to be a broader interpretation than that of the service provider, who is also interested in making a profit. A truly successful project is one in which both the customer and the service provider are satisfied with the outcome. For this to occur, a zone of success must be created that is as large as possible (see Figure 1).
Whitt2003.book Page 7 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
Service-provider Focus
7
Quality
Profit
Customer Focus
Cost Success triangle
Success is achieved when competing factors balance
Figure 1. Success triangle The success triangle is formed at the point where the goods delivered meet the customer’s cost and quality expectations, while still allowing the service provider to make a fair profit and maintain his reputation for good quality work. Staying within this comfort zone is sometimes a bit tricky, and it really helps to understand the “physics” involved. The physics of a project are defined by the forces that drive it.
1. Time Driven or Cost Driven? Time and resources are two parameters that impose limits on the design process. Time, as it relates to a project, can mean either duration or intensity. Duration is measured by units of the calendar (days, weeks, months); intensity is measured by units of labor (e.g., man-hours, man-weeks). The term time driven in this context implies that the project is constrained by the calendar; the term cost driven implies that the project is constrained by cost. Cost is calculated by finding material cost and then measuring the level of intensity per unit of project time (in man-hours) required to design and construct. Often, these time-driven and cost-driven parameters influence major performance goals that might be set for a project. A time-driven project, for example, is one that locks in an aggressive schedule and provides a bonus or some other incentive to the engineer if he meets the schedule. This type of incentive would be used if there was a marketing window for the end product that would close, making the payback period of the investment longer than desired, or giving a competitor a marketing advantage. In such a project, cost control is frequently lost. But, the cost overrun is somewhat self-limited due to a reduced amount of time available to spend the money. A cost-driven project is oriented toward limiting cost overruns. The performance incentive would thus be related to overall project cost. The schedule becomes flexible and can be adjusted for optimum design efficiency (see Figure 2). It is apparent that the two characteristics are somewhat mutually exclusive. If calendar time is compressed, then there is a likelihood of increased cost. If the calendar is not an issue, then the project cost can be managed and minimized. These two characteristics can be applied to any of the project structures listed next.
2. Cost-Plus Project Years ago, the cost-plus project was far and away the most common project structure. In this format, the engineering firm assumed minimal (if any) financial risk. If rework resulted, for whatever reason, the customer was obligated to pay the engineering firm’s hourly rate. This was primarily due to
Whitt2003.book Page 8 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
8
Cost
Same amount of work...
W O R K
W O R K
Cost driven
Time Time driven
Figure 2. Effects of constraints on project structure the fact that good engineering firms were in short supply, and it was their market. The only recourse the customer had was to avoid using that provider in the future. If the customer was small with limited expectations of future work, then his leverage with the engineering firm was limited. Even so, this was a tried-and-true structure that lent itself to stable, long-term business relationships between customer and service provider. As time passed, competition for the engineering dollar increased, giving the customer the upper hand in the market. Other structures took shape that were less advantageous for the engineering service provider. New terms came into vogue such as fixed-cost, turnkey, and engineering, procurement, and construction (EPC). While the differences between these project types can be subtle, being able to adapt the design to fit the differing requirements is key. A project in which the owner agrees to pay an hourly rate that guarantees a fair profit for the service provider is said to be a cost-plus project. The rate charged could be an amount that represents a composite of the service team’s salary plus expenses and profit, or it might vary according to individual salaries with the service provider submitting time sheets. Either way, this type of project involves a minimum of risk to the service provider, which allows him to make reasonable assumptions as to the unknowns during scope and estimate development. It also eliminates the need for overinflated cost additions in the estimate to allow for large contingencies. Therefore, the owner is apt to receive a more accurate estimate. The cost-plus project is generally not awarded as a result of a bid evaluation, though there are exceptions. Rather, this type of project is best suited for an owner-provider team that has a longstanding relationship. Cost-plus fosters a team atmosphere between the owner and the service provider, as opposed to the fixed-cost project that almost guarantees a contentious relationship. Costplus relieves service providers’ pressure to protect profit since, assuming rates are properly negotiated, their profit is inherently protected. This frees providers to concentrate on meeting not only owners’ needs, but also their own preferences during the design and construction process. The benefit to the owners, therefore, is that they retain a large measure of control during the life of the project. The trick to a cost-plus arrangement is to satisfy the owner’s production and maintenance groups by being flexible in the design (which frequently increases project cost and duration) while simultaneously satisfying the owner’s management team’s budgetary and schedule requirements. This dichotomy presents the designer with conflicting requirements, each tending to place limits on
Whitt2003.book Page 9 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
9
the other. It is unwise for the designer to focus on any one of these elements to the exclusion of the others. Generally, either budget or schedule is the driving force behind the project. Whichever it is (and, yes, it is frequently both, though, as we’ve seen the two are mutually exclusive to a degree), the owner will define measures that the provider must meet. A cost or schedule target will be set, and the provider will have an obligation to bring the project to a conclusion within a specified margin. If events transpire that make that impossible, or if a request from an internal group such as maintenance is made that will put the project at risk, then the provider must submit documentation in the form of an engineering change order that explains the situation and estimates the effect. An arbiter within the owner’s organization will then determine the best path to follow. If there is a cost overrun on a cost-plus project, the owner is still obligated to pay the fee. If the owner is unhappy with the situation, the provider has an incentive to compromise to protect the relationship for future projects. Sometimes an underrun can be almost as bad as an overrun. The owner spends a lot of energy allocating resources and would probably take a dim view of those who make that difficult. If a poor estimate causes the owner to unnecessarily delay an important project, there could be repercussions.
3. Fixed-Cost (Lump-Sum) Project A project in which the owner agrees to pay a fixed dollar amount for a predefined set of products and/or services is called a fixed-cost project. It is similar to a turnkey project, differing only in the degree of latitude retained by the owner. With the fixed-cost configuration, the owner will retain a small measure of control during the design and construction phases. For example, if there are three ways to do something and each is relatively equal in terms of cost, then the owner has the right to intervene and influence the design. A fixed-cost project is generally awarded as a result of a bid evaluation. Typically, the owner seeks three bids. The owner provides each bidder identical information packets, or bid packages. The bid package is developed during the phase-one* stage of the project and could be prepared by one of the three bidders, or even by a fourth firm that is not allowed to bid on the remaining work. A fixed-cost, or lump-sum, project is employed when the owner wants predefined costs, which offers several benefits. The primary benefit is an enhanced ability to allocate resources. It also lowers overall cost. The competitive bidding process reduces cost provided the low bidder can perform the assigned tasks. The owner gains these benefits, but loses much control during the execution of the project. To submit fixed-cost bids, bidders clearly define methods and deliverables they think will best meet the owner’s defined scope of work. This type of project involves maximum risk to the service provider, who must conduct a thorough investigation of the site before submitting a bid. Unknowns must be eliminated to the greatest degree possible. Sage judgment must be employed to “guesstimate” those unknowns that remain. The trick is to build in enough safety margin (contingency) to make a profit while keeping the cost low enough to get the work. Once the owner accepts a bid, the service provider has no obligation to adjust the deliverables or methods if it can be demonstrated that doing so will negatively affect the provider’s ability to turn a profit. If the owner makes a request that is out of bounds with respect to the scope of work, the service provider has the right to refuse the request until the owner approves an engineering change order. The incremental change in scope is sometimes called “scope-creep.”
*
Phase-one engineering develops the scope of work and produces preliminary specifications necessary to allow vendors and bidders to properly estimate their portion of the job.
Whitt2003.book Page 10 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
10
The service provider must be ever vigilant in managing scope-creep. This defensive posture on the provider’s part sometimes leads to a fractious relationship with the customer. It is critical that communication lines be established early and be well maintained throughout the process. A fixedcost project, if properly managed, can be the most efficient and effective format for both organizations.
4. Turnkey Project A turnkey project is very similar to a fixed-cost project except that the owner has no real say in the way the project develops. Phase-one engineering produces a bid package that the service provider uses to prepare a bid and, once the award is made, to execute the work. The service provider’s only obligation once the project is awarded is to meet the phase-one specifications and schedule. Once the project is awarded, the customer’s input drops to virtually nil.
5. EPC Project EPC is an acronym for engineering, procurement, and construction. An EPC project is one in which the owner designates a contractor as a single point of contact. This contractor is referred to as the “Prime” and is the only project participant to be directly paid by the customer. The Prime must obtain bids, award contracts, and provide oversight as necessary to coordinate the activities of all the other sub-contractors. The Prime bears full responsibility for the success of the project, assuming all liability from the standpoint of the customer. To maintain a reasonable risk/reward ratio, the Prime can expect a higher return than would typically be the case. Sometimes a company is large and diverse enough to offer true one-stop shopping, providing all these as organic elements. Bechtel Corporation is one such that specializes in EPC-type projects.
6. Hybrid Project A particular project may exhibit several of the characteristics in the various scenarios described above. For example, the engineering portion of the project might be done on a cost-plus basis, while the construction task as a separate lump-sum contract. It is incumbent upon the service provider to come to a full understanding of possible permutations before producing a bid.
D. Project Flow No matter what style of project, whether fixed cost, turnkey, or EPC, most industrial projects are similar in the way they are developed and executed. There must first be a period of investigation, followed by a period of design execution, followed by a period of construction. Figure 3 depicts this cycle.
1. Preliminary: Identification Before a project can be constructed, it must be engineered. Before it can be engineered, it must be defined. Prior to any external involvement, the end user—generally a production group—must first identify a need and then convince management that the need justifies capital expenditures. Management must then investigate and ensure their investment will pay off in the end. After this assessment is made, funds may be appropriated for an internal study. An engineer or qualified specialist must be selected to do the study and to develop a performance specification*. All this and more must occur before a project ever “hits the street.” Each member of the client’s project team plays a role in this process.
*
A performance specification does not tell one how to do a task, but what the end result should be.
Whitt2003.book Page 11 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
11
Preliminary Issue phase one contract
Submit a request for funding
Identify possible solutions
Phase One
Identify a need
Phase Two Legend
On-site investigation
On- and off-site studies Owner
Planning and staffing
HazOp
Prelim. estimate Scope and sched.
Final estimate Scope and sched.
Engineer
Constructor Prelim. engineering documents
Engineering and design
Procure instruments
Long-lead procurement
Procure bulk commodities
Issue engineering documents
Phase Three Receiving and warehousing
Construction
Checkout and startup
Finalize documents
Figure 3. Typical industrial project flow This section explores some of the “behind the scenes” activities that must occur for a project to become “real.” It describes some of the processes that must occur to initialize a project from the perspective of the customer.
a.
Identify a Need Projects frequently begin on the production floor. A problem needs to be fixed or a process needs to be streamlined. For the issue to be addressed, someone must isolate the problem and prepare a written description detailing its properties and effects. Some of the areas to consider when describing the effects are as follows: • • • • • •
Personnel safety Production rate Product quality Equipment reliability Maintenance Operability
b. Identify Possible Solutions • Analyze the problem. Once a problem has been identified, it should then be researched and analyzed to find possible solutions. Frequently vendors can be of great help in this endeavor as they
Whitt2003.book Page 12 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
12
will make themselves available to evaluate the situation and recommend possible fixes. However, these suggestions should be used with care since their suggestions are not always objective. •
Estimate the cost. A preliminary estimate of the probable cost must be derived. Again, this can be done using input from vendors, or perhaps in consultation with an engineering firm.
c.
Submit a Preliminary Engineering Request for Funding The problem and its possible solution should be presented to management for analysis. Assuming a positive response from management, funding will be appropriated for a phase-one study.
d. Issue a Phase-One Request for Bid and Select the Contractor •
Write a project specification The project specification should clearly describe the project goals. It should provide enough information to let someone prepare a reasonably accurate bid with minimal expense. The following information should be discussed in the specification: 1.
Existing drawings If pertinent existing drawings are available, they should be referenced or included in the specification package.
2.
Equipment performance specifications Performance criteria for individual equipment items should be detailed as performance specifications. For example, if the project aim is to increase product flow rate, then the existing and desired flow rates should be provided, and any equipment related to product flow should be required to be compatible with the new flow rate.
3.
Service provider performance criteria Service provider performance criteria should be detailed in the project specification. The following are examples of issues that should be addressed in the criteria: How should documents be transmitted? a. b. c. d.
What media should be used to prepare the documents? CADD? Manual? What design standards should be adhered to? NFPA? NEC? Internal? What is the desired timetable? What specific deliverables will be expected?
4.
Approved vendors list An approved vendors list should be provided to ensure the contractor orders equipment that is compatible with existing systems for which spares are available.
5.
Safety Any safety information pertinent to the contractor should be included in the specification, particularly if the requirements will cause the service provider to incur additional cost. Plant access issues should also be discussed.
Whitt2003.book Page 13 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
•
13
Select the phase-one engineering contractor 1.
Publish the project specification. The project specification should be made available to any engineering service providers interested in the project. These service providers will analyze the document. Invariably, they will make inquiries for amplification. The customer should make sure that any responses are published officially for each of the potential bidders so that all have the same information from which to work.
2.
Conduct a project orientation After several potential service providers have expressed interest in participating in the project, an orientation meeting should be held. All prospective providers should be invited and should be given identical information packages and a tour of the site. Ground rules and lines of communication should be established. The criteria for bid evaluation should be discussed in detail.
3.
Evaluate the bids Evaluate the bids based on the criteria presented in the orientation meeting. If the bids do not meet expectations, amplification can be given and revised bids accepted provided all participants are given the same opportunity. In some cases, the project specification will need to be revised and the bid process repeated.
4.
Award the phase-one contract Award the contract for the phase-one study based on previously defined criteria. The following are some of the possible criteria for consideration: a. b. c.
•
Previous experience in similar projects Estimated project cost and payment schedule Proposed project schedule
Start phase-one engineering An engineering firm is frequently hired to do the preliminary work that is sometimes referred to as phase-one engineering. This step is the first formal step in the engineering process. The circle of players must expand as necessary to effect a reasonable study that will eliminate as many unknowns as possible. The end product of this effort is a set of conceptual documents that become the foundation of the project.
In short, the end user first identifies a shortcoming in the process and envisions a reasonable “fix.” A document is then prepared that describes the problem and its negative effects on production and/or safety. This document is then evaluated internally by upper management. If the topic is found to have merit, then some funding will be appropriated to conduct a formal internal study. The results of the study will be evaluated to see if further expenditures are merited. If the internal audit shows the possibility of good results—as defined by the cost/benefit ratio—then more funds may be appropriated to hire an outside engineering firm to do a phase-one study and to develop some preliminary engineering documents and specifications. The study is then evaluated and another cost/benefit analysis is undertaken. If this analysis is positive, then the project becomes “real” in terms of general engineering services. This process has evolved as the best way to reduce the customer’s financial risk. Project reviews among all the groups involved acts as a check and balance to ensure that the project needs of one
Whitt2003.book Page 14 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
14
group do not overwhelm the budget needs of another. At any time, the project can be placed on hold while additional analysis is done. If the market is particularly volatile, the cost/benefit ratio could change drastically during the evaluation process. A project that looks good initially might not be cost-effective three months later after the market for the product turns sour. If that occurs, then the products generated during the phase-one study could likely be used later.
2. Phase One: Investigation The first step in the execution of a project is called the phase-one study. This is a step in which a small fund is established to help determine the feasibility of continuing with phase two. The purpose of the study is to eliminate unknowns until the premise of the project is either proved or disproved. Usually a period of evaluation follows this phase to assess the situation before additional funds are committed. The primary purpose of phase one is not the production of documents, though some documentation is produced. Rather, this phase of the project is devoted to an investigation that will reveal actual numbers of items to be managed, the amount of time it will take to produce the design package, the engineering labor cost, and a total installed cost for the project. Tabulations, narratives, and sketches are more often provided as deliverables in this phase. Many documents started here are completed in phase two. As shown previously in Figure 3, phase one is a four-step sequence.
a.
Walkdown—Executing an On-site Evaluation Most projects, whether a formal phase-one study is required or not, begin with an on-site evaluation. These evaluations, called walkdowns, serve three primary purposes: • • •
To familiarize the design team with the site. To allow the design team to interact with the maintenance and operations personnel that will eventually have to take ownership of the system being designed. To allow the design team to obtain visual and tactile information that is frequently not readily available by any other means.
In “greenfield” projects, where everything is new, the need for walkdowns is minimized. But, in most instances, if the on-site walkdown is omitted, it is to the detriment of the design group. Designers who rely on existing drawings and hearsay as the basis for the design are sometimes surprised by a failed project. Frequently, the design team is off-site and must travel to execute the walkdown. Travel has an inherent indirect cost that is easily underestimated. However, the cost should be considered as an insurance premium to protect against unforeseen circumstances. For a retrofit-type project, a walkdown should, at a minimum, include a piping and instrumentation diagram (P&ID) evaluation in which each instrument is eye-balled and located on a P&ID. If a set of P&IDs can be validated, then the instrument and input/output (I/O) lists may be finalized. The budgetary estimate can then be validated and reissued as a detailed estimate. The scope of work can be finalized and the project schedule updated. But, until the P&IDs are field verified, the level of uncertainty will remain high. The evaluation that begins on-site will feed into more in-depth evaluations that will occur in phase two.
Whitt2003.book Page 15 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
15
b. Scope of Work, Estimate, and Schedule The on-site evaluation described above provides a baseline to which the design may be applied. Once the existing situation at the site is known, the provider may begin developing the products that will satisfy the goals of the project. First, a scope of work must be developed. The scope of work begins with the customer’s general specification. Each engineering discipline extracts information from that specification and develops its own scope of work from its unique perspective. This document describes the baseline situation, the desired end result, and the general activities that will be required to bring about the change. All these documents will then be recompiled into a project scope of work. It will be enhanced by adding details of how the project as a whole will need to be executed, including a more accurate list of deliverables and of tasks. After the scope of work is complete, a work breakdown structure (WBS) may then be created. The WBS provides a detailed, task-oriented strategy for project execution, broken down by discipline. This becomes the project schedule.
c.
Preliminary Engineering Documents Several documents are generated during the phase-one study. These products are used as the basis for the phase-two engineering and design task. Such documents include but are not limited to the following: • • • • • • •
Heat and material balance (HMB) Process flow diagram (PFD) Piping and instrumentation diagram (P&ID) Communications network single-line Preliminary bill of materials Studies, such as power distribution, instrument air capacity, and process services Instrument and I/O lists
Each of these is subject to change during phase two. For example, design development changes will almost certainly force P&ID modifications, which will ripple through the entire package. Enough slack must be built into the estimate and schedule to accommodate the normal adjustments that will occur as a result of design development.
d. Hazard and Operability Study (HazOp) After the production process is defined to a fairly high degree, but before the detail design has begun, the envisioned system should be analyzed for operability and safety. Operability concerns relate to the bottom line, by perhaps streamlining the process, but also to safety by defining safe operating procedures. Safety issues that should be analyzed begin with the various raw materials that are brought onto the site. Handling and storage procedures should be discussed and implemented. Personnel safety should be analyzed for each area of the plant. Finally, production and distribution of the final product should be analyzed. This analysis should be all-encompassing and thorough. The time spent will be more than recouped by the improvements that will result. To gain the most benefit from this, the analysis should be a team effort, including representatives from every department that is affected by the project. Finally, management must commit to a reasonable effort to implement the suggestions; otherwise, the whole thing is a waste of time.
Whitt2003.book Page 16 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
16
A systematic approach for conducting this investigation exists. It is called a hazard and operability study, or HazOp. A HazOp provides a structure for analyzing each element of the process facility. This structure is in the form of a checklist that presents a series of process states. Each state listed is a desired state. The series of states listed in Hazop and Hazan5 by Trevor Kletz is as follows: • • • • • •
None More of Less of Part of More than (or as well as) Other than
For example, if analyzing the pressure in a vessel, what happens if zero or negative pressure is detected? What happens if there is more pressure than desired? Or less? What if the pressure deviates from set point (less of or more of)? How could any of these deviations occur, and what should the operator be expected to do to respond? What automatic actions should the control system take? Finally, what if something else entirely were done (other than)? Each of these questions should be asked, and each member of the team should be allowed to provide input. Each question and response should be recorded, along with any remedial action that is defined. The HazOp is a structured brainstorming session. Free-wheeling discussion of the topics should be encouraged, within the boundaries set by the facilitator. For more information on this topic, Kletz’s Hazop and Hazan is an excellent resource.
e.
Long-Lead Procurement Frequently, there are items that must be purchased early to be available when needed. Large or complicated equipment items fall into this category. Items that cannot be purchased “off the shelf” should be considered potential “long-lead” items. Such items should be checked for turnaround times from the vendor. If the turnaround time is of a length sufficient to jeopardize the project schedule, then that item should be ordered as soon as practical. All other acquisitions should be put off until the latter part of phase two in order to reduce warehousing costs. Such long-lead items include analyzers, pressure vessels, and weigh-feeder systems, to name a few. These items must be fabricated to meet a specification and are of a complexity that demands a long dwell time in the factory. Many times, a factory acceptance test must be done prior to shipment with the possibility of additional delays after the test.
The phase-one engineering study is sometimes formal, sometimes not. Many times, depending on the customer, there is no clear dividing line between phase one and phase two. However, much of the investigation that has been described here will need to be done whether the results are delivered as a “study” or whether the results are fed into the churning maw of the phase-two production machine. The success or failure of a project can frequently be traced back to the initial investigation work that was or was not done in the beginning.
Whitt2003.book Page 17 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
17
3. Phase Two: Execution After phase one has been evaluated and the project goals have been confirmed as feasible, funds are released for the final execution of the design. The purpose of phase two is to prepare documentation that will • • •
facilitate construction (phase three), facilitate long-term maintenance of the facility, and provide documentation suitable for disaster-recovery and future training.
Phase two builds on the products of phase one. Every piece of information that was developed in phase one is refined in phase two. The normal order of execution of phase two is as follows:
a.
On-site and Off-site Studies The on-site investigation conducted during phase one becomes the basis for further evaluations in phase two. Vendors are consulted to confirm assumptions, and possible site visits occur to follow leads developed earlier. The information gathered during this period will be evaluated as it relates to scope and schedule impact.
b. Final Estimate, Scope, and Schedule Any phase-two study findings are evaluated for effect on scope and schedule. Changes need to be rolled into the WBS.* If the findings are significant, then the estimate may need to be modified.
c.
Planning and Staffing After the WBS and schedule have been finalized, final staffing arrangements can be made. The structure of the design team needs to accommodate the structure of the project as defined by the WBS.
d. Engineering and Design The “production” phase of the project begins as the design team is assembled. The range of design products are described later in this chapter.
e.
Procurement Several procurement activities occur during the latter part of phase two. Delivery lead times must be considered with respect to timing of orders. In general, the procurement activities are as follows:
*
•
Equipment and Instrument Procurement This category covers items that must be individually specified. Such items are frequently manufactured “to order” and need a little more lead time than “off-the-shelf” items. These items must also be handled differently when they are received on-site, as they are classified as “specific use” items. They should arrive from the vendor already calibrated and tagged, if possible.
•
Bulk Commodity Procurement This category covers items that are considered off-the-shelf, which are purchased in bulk for general use. Such items include cable, conduit, termination components, tubing, tube fittings, and mounting hardware.
The work breakdown structure (WBS) is a list of tasks that need to be executed. Each task is given an ID number and is linked to the schedule.
Whitt2003.book Page 18 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
18
f.
Issue Phase-Two Engineering Documents The final phase-two engineering activity is issuing documents for Construction. Document management is a major evolution throughout the life of the project, but it is critical at this juncture. The design team must always know the version of the drawing that has been issued to the field to be able to provide close support during phase three. Phase-three activities will almost certainly force revisions to the document package. Provisions must be made during phase two to accommodate those changes. A properly designed system of document control is essential.
Phase two is the “production floor” of the engineering process. By the time the phase-two tasks are completed, most of the unknowns in the project should have been eliminated. Phase two, then, is a process of assumption verification and product generation. A set of engineering products and services has been derived over time that satisfies all the above requirements. These deliverables are discussed later in this chapter.
4. Phase Three: Construct and Commission The final step in the execution of a project is called the construction phase, or phase three. This is the phase in which the design is implemented. The constructor assumes the prime role here, with the engineering/design team in support. Frequently, an engineering liaison is assigned to provide close technical support to the constructor and to anticipate problems that are developing before they cause work stoppages. The construction phase is broken into four major tasks as shown previously in Figure 3.
a.
Receiving As equipment arrives on-site, it is handled by either the customer’s receiving department or the constructor. In either case, warehouse management is an important consideration. As each item is received, it must be inspected for damage, logged, tagged, and stored. The constructor is particularly vulnerable to poor management practices in this area. If it is in the constructor’s scope to handle the material, it must be done in the most efficient manner possible, probably under less than ideal conditions. Warehousing is sometimes a makeshift affair with little or no existing infrastructure. To compound the problem, a constructor’s ability to derive an efficient method of storage and disbursement can be limited by poorly organized information provided by a design team that didn’t anticipate his problems. Thus, it is important that the two organizations meet early in phase two to devise a material management process that will be workable in phase three.
b. Construction The construction phase frequently overlaps phase two activities by some margin, beginning construction on design tasks that are complete. During this time, the needs of the constructor ascend in importance over the needs of design. Work stoppages should be avoided at all costs, even to the point of stopping remaining phase-two work to concentrate on a phase-three problem.
c.
Checkout and Startup Checkout and startup require a team effort that includes the customer as well as the design team and the construction team.
Checkout (Bump and Stroke) Each installed item should be verified for proper installation. Sometimes called the “bump and stroke” phase, the checkout should exercise each item to demonstrate proper opera-
Whitt2003.book Page 19 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
19
tion. If the item is controlled through a programmable logic controller (PLC) or distributed control system (DCS), then the action should be initiated there, and any expected feedback animation should be verified at the operator interface. Alarms should be actuated, and safety sequences should be evaluated for proper operation. To do this properly and document it, a checkout procedure should be generated. Using the instrument database and I/O list as a basis, a checklist can be produced that will make this an organized, verifiable process. A sample startup checklist is shown in Figure 4.
Startup Readiness Report Installation
Checkout
Tag Number
Mounted?
Wired?
Tubed?
Rung Out?
Local
Remote
Summary
PT-10
1
1
1
1
1
1
100.0%
PT-11
1
1
1
1
NA
PT-12
1
1
LT-15 PCV-10
80.0% 33.3% 0.0%
1
1
HV-11
33.3% 0.0%
Excel readily lends itself to this type of use. The Summary field can be used to help develop a completion percentage if desired. In this case, the summary assumes each category is weighted equally. The numbers are summed and then simply divided by the number of categories. PT-10 has six categories and PT-11 has five. The equation "=SUM(C5:H5)/6" is loaded into the summary cell for PT-10, for example.
Figure 4. Startup readiness report
Startup Startup should be well organized and sequential. A formal startup procedure is recommended. The procedure should include a sequence of actions to take and should describe the expected system response at each step. A means for confirmation signoff should be provided. The system’s behavior at each step should be fully understood before proceeding to the next step, and the procedure itself should be approved by the owner well prior to its execution.
d. Finalize Documentation At the conclusion of the construction phase (which includes checkout and startup), the set of construction documents needs to be folded back into the original design. Redline markups that occurred due to construction adjustments should be transcribed into the original design package. This sometimes causes a ripple effect that can cause a great deal of rework on the part of the design team. However, these changes could be critical to the maintenance department and could reflect poorly on the design team if not corrected. That is why a complete understanding of each engineering deliverable is necessary. If a document is a construction document, the update is less important than if the document is a deliverable that will be necessary for project archives or for proper facility maintenance.
Whitt2003.book Page 20 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
20
As we have seen, Phase three has an engineering component and a construction component. The engineering team recedes to a supporting role during this portion of the project. Construction support tasks consume much of the engineering focus during this time. Execution of factory acceptance tests, interaction with the vendors, and on-site training are some of the other engineering activities that might go on during this time. At the conclusion of the construction phase, a period of checkout and startup might require engineering support. Phase three, however, is predominantly the domain of the constructor. Receiving and warehousing of equipment, fabrication and construction, and checkout and startup are the primary tasks during this time. At the conclusion of the project, the constructor should turn in all redlined drawings to the engineer so that all the documents may be finalized.
E. Project Deliverables As noted above, several products begun in phase one are completed in phase two. Figure 5 depicts the flow of a typical multidiscipline chemical process design project from the point of view of the instrumentation department. The project flow for other industries might differ slightly, but the overall process will be similar.
Engineering, Phases One and Two Indicates products of others Indicates items started in phase one Indicates items started in phase two 3 Piping and instrumentation diagram (P&ID) Process flow diagram (PFD) and Heat and material balance (HMB)
2
6
4 Equipment arrangement (civil/mech.)
DCS selection and familiarization (Client / SI / I&C) 5
10
11 Piping orthos (mechanical)
12
Control system networking
Pump specs (mech./elec.)
Drawing list
Equip. specs (mechanical)
14
13 I/O config. (client/SI/I&C)
9
8
7
Detailed schedule and estimate
1
Instrument database
Instrument specifications
15 Instr. area plans (spot instruments)
16
Floor and site arrangements
18
Instrument elementaries and/or loop sheets 17
Cabinet and panel arrangements
19 Installation details
21
Wiring diagrams (interconnections)
20
Cost group
Mechanical bill of materials
Quotation
15b Instr. area plans (conduit arrang.)
Electrical bill of materials 22
23
Integrated design check and issue for construction
25 Construction
Procurement
24
Construction, Phase Three Adjust design drawings to reflect redline markups
27
26 Issue for record
Project complete
Figure 5. Typical I&C project flow diagram
This diagram gives graphic evidence of the importance of the P&ID to the I&C design process. The P&ID is ultimately the basis for the entire I&C design package. It is a “living” record of the control system from the sensing elements through the computer system to the final control elements.
Whitt2003.book Page 21 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
21
Following is a brief description of the various products and services depicted in the diagram. Additional information about many of these topics is provided in Part II of this book, and examples are provided in Part III.
1. Process Flow Diagram The owner typically produces the process flow diagram (PFD), though sometimes an engineering firm is retained to generate this as part of the phase-one engineering process. It is a simplified schematic of the system’s mechanical configuration. For example, a tank is piped to a pump that is piped to another tank. Very little detail is provided as to tank or pipe sizes, and virtually none of the instrumentation is depicted. This becomes the basis for the heat and material balance (HMB) sheet.
2. Heat and Material Balance The heat and material balance (HMB) sheet is graphically similar to a PFD except the HMB has additional information concerning the physics of the project. The drawing begins as a PFD showing the major equipment items and the piping that connects them. Heat loads, flow rates, and energy expenditures are calculated and noted on the document. Raw materials that are envisioned are shown as well. Internal engineering sometimes generates this set of documents, as confidential or even secret information will be presented. As a result, the HMB is frequently considered a “classified” document that is sometimes not even given to the engineering design firm. If the project is approved, the HMB becomes the basis for the P&ID.
3. Piping and Instrumentation Diagram (P&ID) The piping and instrumentation diagram (P&ID) is spawned directly from the PFD. The P&ID is a multidiscipline product that is typically the primary responsibility of the process engineering department but is shared by the mechanical, electrical, and instrumentation departments as well. It is a working document that is continually updated as new understanding of the process develops. It provides piping detail in the form of pipe sizes and shows piping fixtures such as expansion joints, flex hoses, blind flanges, and rupture discs. It provides instrument information in the form of instrument “bubbles” to indicate level transmitters, flow switches, and the like. It provides some indication of operability by showing hand-switches, indicator lights, gauges, tank-level sight glasses, and annunciator points among other items. It also indicates major control logic elements by showing interconnected computer functions and interlocks.
4. Equipment Arrangements Equipment arrangement drawings are construction deliverables produced by the mechanical and civil groups. The basis of these drawings is the civil/structural drawings. The mechanical department then begins placing the major pieces of equipment on the floor plan, keeping in mind access routes, building code requirements, weight considerations, etc. These drawings will become the basis for the detailed piping arrangement drawings (piping orthographics) and ultimately the instrument area plans.
5. DCS Selection/Familiarization Selection of a control system is a major consideration for customers. They will sometimes solicit assistance from design engineers or third-party systems integrators. However the system is selected, it is the customer’s decision to make. Once the decision is made, the design engineering firm must gain familiarity with it. From this orientation phase, a drawing is produced that shows basic system interconnections and network particulars. When this system understanding is developed, it is integrated with the P&IDs to develop an I/O configuration that is in turn used to develop elementary wiring diagrams (elementaries) and to generate a detailed estimate.
Whitt2003.book Page 22 Thursday, July 10, 2003 4:05 PM
22
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
6. Detailed Estimate and Schedule P&IDs and I/O lists are generally produced during a phase-one portion of the engineering process. The purpose of phase one is to develop sufficient information to support an estimate that is suitable for bid purposes, one deemed accurate enough for final budgetary appropriations and engineering service provider selection. Customers usually open the project for bidding at this point, obtaining bids from different providers who have used the phase-one material to produce a detailed estimate. Customers then compare the outside bids to their own detailed estimate and then select the engineering provider that best suits their needs. This is, incidentally, not always the lowest bidder. In phase two, the estimate and schedule are finalized, or “detailed.” At this stage, they are considered to be accurate and will be used as management tools throughout the life of the project.
7. Drawing List Document management is very important, and it can be time-consuming. Hundreds of documents might be newly generated. Hundreds might be ordered from the customer to be modified. Managing the documents and tracking their active revision and disposition can be a major undertaking. The drawing list itself is frequently a design deliverable upon completion of the project.
8. Pump Specifications The mechanical group and the electrical group generally team up to produce pump specifications. Most pumps are motor driven, which involves the electrical department.
9. Equipment Specifications Process equipment is generally specified by the mechanical engineering group. They, or the process engineering group, will specify vessels; heating, ventilation, and air-conditioning (HVAC) systems; blowers; heat exchangers, and so on.
10. Piping Orthographic Drawings Piping orthographic drawings (orthos) are construction deliverables produced by the mechanical engineering department. They are scale drawings that detail the piping design. These are sometimes referred to as piping plans, though the drawing package contains both plans (top view) and elevations (side view). Instruments that must be piped in-line are depicted, so the instrument engineer must be prepared to provide flange-to-flange dimensions of in-line instruments.
11. Control System Interconnection Drawing A control system interconnection drawing is an engineering deliverable produced out of the DCS selection/familiarization process. It depicts the major components of the control system and how they are networked together.
12. I/O Configuration The I/O configuration is not a deliverable in its own right. However, it is used to support other functions that are deliverables. The I/O configuration is a list of I/O points organized around the characteristics of the control system. The raw material for this list is generated from the P&IDs. A P&ID ”takeoff” process occurs whereby all the instrument signals depicted on the P&IDs are collected into a list. The signals are then categorized based on type (e.g., digital inputs, digital outputs, analog inputs, analog outputs, RTDs) and then logged in a table or database. These I/O points may be further categorized by their relative locations in the process or by their physical locations on the floor. These counts are then compared to the architecture of the control system to determine numbers of I/O modules that must be bought, and, by extension, the numbers of elementary drawings that might be needed. This database then becomes the basis of the main instrument database.
Whitt2003.book Page 23 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
23
13. Instrument Database An instrument database is key to a properly managed design process. The database, if developed early and then updated religiously during the design process, can be a very useful design tool and a tremendous aid during the design check. Each item touched by the instrument design team should appear as a record in this database. It is initialized by the I/O list as generated during the I/O configuration process, but eventually it should contain records of even unwired instruments that need to be purchased or refurbished.
14. Instrument Specifications Given the availability of support information such as pump specifications, equipment specifications, P&IDs, and an instrument database, the production of instrument specifications can proceed. HMB-generated data such as flow rates and temperatures needs to be available as well. Instrument specifications must be completed before the instrument elementaries or installation details can be finalized. The piping design group also depends on this task.
15. Site and Floor Plans A site plan is typically included in the phase-one study. It is sometimes just a sketch showing the intended future location for equipment, junction boxes, etc. Formal site plans, as engineering deliverables, are considered products of the structural engineering group. Control room and termination room floor plans are usually issued as sketches in phase one, then finalized in phase two. These sketches are part of the I&C deliverables set used for construction purposes. These drawings might also find their way into the customer’s vault as “maintained” drawings. Process area floor plans, sometimes called instrument location plans, are construction deliverables rarely maintained past construction. They provide general information about instrument placement on the process floor, the conduit and/or tubing that must be extended to those instruments, and any support equipment such as field junction boxes and air header connections. The drawings can be scale drawings showing the exact location of the instruments, or they might be done as diagrams, depicting the instrument near its expected location. These drawings can be done in two steps if the schedule demands it, though ideally, the bulk of the work should happen downstream of the elementaries and somewhat parallel to the wiring diagrams. Initial setup of the drawings can occur as soon as the equipment arrangements are essentially complete, which would put this function parallel to production of the piping orthographic drawings. But, due to the conduit sizing and contents information needed, it would not be possible to finish them until after the elementaries (or loop sheets) and subsequent wiring diagrams are completed.
16. Control Room and I/O Termination Room Arrangements Control room and I/O termination room drawings are closely interrelated. The control room design must be settled first, then the I/O room. Sometimes PLC or DCS equipment racks are physically in the control room, with the marshalling panels in an adjacent I/O “spreading” room. Sometimes all the computer hardware is in the I/O room. Frequently, the deciding factor for placement has to do with the availability of environmental control in the I/O room. If that room is not air-conditioned, then the sophisticated hardware might be found in the vicinity of the control room. Another consideration is the availability of “real estate.” Control rooms and I/O rooms are some of the most expensive rooms in the plant in terms of cost per square foot.
17. Instrument Elementary Wiring Diagrams and Loop Sheets Instrument elementary wiring diagrams (elementaries) and instrument loop sheets serve the same basic function in the context of the drawing package. Both types of drawing are nonphysical. Wiring
Whitt2003.book Page 24 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
24
information is presented as a complete electrical circuit, not as a particular physical cabinet or field device, for example. A loop sheet might present some physical information, but its main purpose remains to show the complete electrical circuit. The drawing depicts current flowing from “hot” to “neutral” or from DC+ to DC-. It is rare that a circuit crosses drawings, though it is sometimes unavoidable. This type of drawing differs from the interconnection wiring diagram in that the interconnection drawing shows wiring for a particular device or physical area. That format requires the technician to follow the signal across various paths, possibly crossing several different drawings, to assemble a picture of the entire circuit.
18. Panel Arrangements Marshalling panels are typically large enclosures that provide a place to mate field cables to computer system cables. Generally, field I/O are not organized in a way that is convenient for termination into the control system. Field cables are oriented toward floor location, while I/O cables are oriented toward computer I/O module groupings. The marshalling panel provides a place to crossconnect the cabling systems and to perform any necessary circuit protection and power distribution activities. The marshalling panel arrangement drawing is a fabrication drawing that consists of a bill of materials and a component arrangement. Control panels house electronic equipment and sometimes have controls (e.g., switches, lights) that are presented on the front panel. The arrangement for this type of panel provides interior panel arrangement and possibly a hole-punch guide for the panel front. Field junction boxes are panels that house wiring interconnection components such as terminals and sometimes relays and fuses. Usually, these boxes are simply “breakout” boxes in which multiconductor cables are “broken out” into single-pair cables.
19. Installation Details Instrument installation details are drawings (or sketches) that provide hookup information for the installer. They provide a pictorial representation of the components in their proper relationships to each other and a bill of materials chart that describes such things as part numbers and item numbers. Installation details usually have multiple uses (i.e., they are generic drawings). For example, there might be several control valves in different parts of the plant that are to be installed the same way. One installation detail will suffice for all, provided there is a cross-reference between the instrument and its installation detail. For this, the instrument database is a good tool. It is also a good idea to put that information on the instrument specification as a note. There are usually three categories of such details for each installation: mechanical connections, electrical connections, and mounting.
a.
Mechanical Installation Detail The mechanical installation detail shows a device and its tubing or piping connections and the connection materials. A typical mechanical detail might show the instrument air hookup to a control valve. In this case, any fittings that might be needed, including gaskets and bolts, are called out on the detail.
b. Electrical Installation Detail The electrical installation detail provides information relating to the conduit connections. All conduit fittings are described such as condulets and flex hoses, but only within about a 2-ft. envelope around the instrument. The instrument location plan takes care of material outside that envelope.
Whitt2003.book Page 25 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 1: THE PROJECT
c.
25
Mounting Detail Mounting information such as instrument pipe-stand fabrication, mounting bracket fabrication, and other mounting particulars are described here.
20. Wiring Diagram (Interconnection Drawing) Wiring diagrams depict interconnections within a specific cabinet or panel. The purpose of the wiring diagram is to provide information that will allow the installer to execute the wiring task with a minimum of investigation. The wiring diagram makes no attempt to show a complete electrical circuit, but rather provides point-to-point wiring detail only. Cables are shown entering and leaving the enclosure. Any internal wiring is shown in total. A wiring diagram is generally produced for each and every marshalling panel, field junction box, control panel, relay panel, or any other enclosure in which wiring must be terminated.
21. Mechanical and Mounting Bill of Materials After the mechanical and mounting installation details are created and assigned to each instrument, a mechanical bill of materials can be produced. This bill of materials lists all items needed for the mechanical installation of the instrument. This includes all tubing, tube fittings, brackets, clamps, and mounting hardware necessary to connect the instrument to the process. All materials called for by the mechanical details are compiled into a single bill of materials. The bill of materials is then submitted to purchasing where it is broken into packages by vendor and issued for purchase.
22. Electrical Bill of Materials After the electrical installation details are created and assigned to each instrument, an electrical bill of material can be produced. This bill of material lists all items needed for the electrical installation of the instrument. This includes all conduit, conduit fittings, flex fittings, and drain plugs. All materials called for by the electrical details are compiled into a single bill of material. The bill of material is then submitted to purchasing where it is broken into packages by vendor and issued for purchase.
23. Integrated Design Check Just prior to sending the drawing package out for construction, a full-blown design check should be undertaken. The design check includes checking the drawings of other disciplines where interfaces exist and checking each set of instrumentation design documents for accuracy and proper integration with other drawing sets. Also, P&IDs and the database should be checked in full prior to issue for construction (IFC). Time should be allotted in the schedule for time to make corrections and adjustments as needed.
24. Issue for Construction After a successful design check, the documents can be issued for construction. Note: The issue for review, or IFR, process is not addressed here. However, each drawing package is submitted for customer review and approval at the customer’s discretion. The IFR policy needs to be clearly defined at the beginning of the project.
25. Redlines No design survives construction team review intact. Constructors must be able to make adjustments to the design as needed. As they do this, they should carefully mark (i.e., “redline”) the drawings to reflect as-built conditions. The importance of this process needs to be stressed to the constructor during project meetings as it is often done poorly or not at all. Time needs to be allotted in the schedule and in the design budget for integrating these redlines into the official drawing package.
Whitt2003.book Page 26 Thursday, July 10, 2003 4:05 PM
26
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
26. Issue for Record After all redlines have been integrated and a successful startup has been achieved, the documentation package should be issued to the customer for record. The customer may demand that this be done in a specific manner and that the documents be formatted to specific standards. Customer standards should be reviewed at this time, and any noncompliant documents should be identified and revised.
27. Project Wrap-up As the project is wrapped up, any sensitive information is secured and a final record copy of the project documentation, memos, and other items of import is prepared. Conducting a “lessonslearned” post-mortem can also be useful for future projects. Each and every design project is different. Yet, the way in which the design engineer should approach a new project should not change. The same initial questions should be asked every time. What is the structure of the project? What are the customer’s expectations, and how will he measure success? How much risk is it wise to assume? Once those questions have been answered and the design environment is known, the specific content of the design package can be resolved. The mix of products and services can be changed from project to project, and the design team needs to be able to adapt to changing needs. If the design team has a good feel for all the deliverables that may be offered, then modifying the package by deleting deliverables has little effect on the design process. In contrast, adding products that are new to the team could have a great effect, upsetting the work flow. Therefore, it is in the best interest of all concerned to have all team members fully cognizant of the range of products and services and their interrelationships.
Whitt2003.book Page 27 Thursday, July 10, 2003 4:05 PM
Chapter 2: The Project Team As illuminated in the previous chapter, embarking on a new project is an extraordinarily complex, and sometimes risky, undertaking. A high level of technical expertise on the part of the participants is a must. But, other factors, perhaps less obvious, are also required. The days of sitting back in a swivel chair and working the project for weeks in isolation are over. Projects in today’s world require a lot of interaction. The customer is looking for partners that are proactive and engaged. Several issues must be resolved early in the project. Chief among these is the establishment of good lines of communication among the different organizations that make up the project team. To achieve this, it is important for all team members to understand their roles as they relate to the overall project and to know what to expect from other members and organizations. Communications among these different organizations is critical, as is a mutual understanding of the division of labor among them. Engineering project teams consist of three primary elements: the customer, the designer, and the constructor. Generally, the three are represented by three distinct organizations, though for small projects the distinction can be blurred. For example, on small projects, the designer might be a maintenance technician who will also install (or “construct”) the equipment. Nevertheless, the three elements are present in some fashion. In an ideal world, each major team element would function in perfect concert with the others, performing much like a symphony to produce a work that is equally beneficial to each member of the team. This is, however, difficult to achieve under the best of circumstances. In reality, the normal design process is quite discordant and chaotic. Sometimes the definition of success itself differs widely among the participants. Managing discord becomes a major task, and a well-executed project may differ from a poorly executed one only by the level of disharmony that exists. The three different organizations that make up the project team—the customer, the designer, and the constructor—may never have worked together in the past. This impedes good communications, and frequently results in wasted effort. As a result, when beginning a larger big-budget project, team building is a major consideration. Management teams from the major organizations should meet in an informal atmosphere in an attempt to quickly construct a basis for an effective professional relationship. This pays off in better communications among groups, which results (hopefully) in a more efficient organization. This kind of big-budget approach is not possible on the small project’s limited budget. More often than not, the small project kickoff meeting occurs in a conference room near the project manager’s office and is sandwiched between pressing production matters that may take as much of the project manager’s mental energy as the meeting. Personal discussions are minimized, and team building is a luxury that is not even considered. For the small project specialist, it is imperative that the professional relationships among organizations be fostered on an ongoing basis. Regardless of the size of the project, proper attention to detail in the beginning is critical. Once the project begins, there is a natural “churning” of information that is healthy provided proper levels of communication exist among the groups. This chaotic churning process is particularly evident in the area of instrumentation and controls. The I&C discipline cuts across almost all boundaries, from process to mechanical to civil and structural to operations. And, beyond the engineering aspects, preferential issues relating to operability and maintainability must be considered. Design
Whitt2003.book Page 28 Thursday, July 10, 2003 4:05 PM
28
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
development is a term used to describe design changes that occur due to the normal churning of ideas as a project takes shape. This process is very important and must be accommodated within limits. If allowed to proceed unchecked, the results can be disastrous. Injecting controls into this chaotic environment without entirely stifling creativity must be a primary goal. Thus, it is critical that the I&C professional in particular be able to interact effectively with other disciplines and other organizations. One important step in interacting effectively is to become familiar with the different forces at work behind the scenes. New engineers or junior designers rarely have a “big picture” viewpoint because each project is different and they see only a few facets at a time. Each new project adds a bit more to their store of knowledge until reasonably accurate assumptions can be made about activities outside the field of view. Only then can enough of a picture be constructed to provide perspective. This process of assimilation can, and probably will, take several projects to bear fruit. In an effort to speed up this process, this chapter defines some of the major organizations and discusses some of their goals and methods.
A. The Customer This book often depicts the customer (or client) as some sort of monolithic entity. In reality, however, the client is an amalgam of individuals and subgroups, all of whom are important and must ultimately be satisfied to some degree. Each project, whether it is a capital project or a work-order (maintenance) project, is organized in a similar manner. Someone has the funds, someone has the need, and someone has the ball. Typically, the one with the ball is the project manager. In some smaller work-order projects, the project manager and the production representative may be the same person. Work-order projects are generally very small “tactical” tasks that are funded, and sometimes managed, by the production group (i.e., operations). The task is generally one that makes a minor change to increase production, add convenience, or improve safety. Generally, someone from project management coordinates this sort of project, depending on the skills available in the production group. Capital projects are those funded from the client’s capital budget during yearly budget meetings. These projects can be thought of as “strategic,” or ones that will generate positive long-term effects. Capital project budgets are reported to stock holders, and as such, have high visibility. Projects differ from one facility to the next and even from one project to the next. But, they usually share some similarities. Producers are ultimately driven by the bottom line. If they are spending project money, then projects must have positive results that increase the profit margin. While clients must frequently rely on outside resources, they must not lose control of the process. Thus, a management team becomes a necessity. A client typically has a group of engineers and production specialists who are tasked as members of the management team. Often these individuals have other, more production-related duties as well. Depending on the size of the task and the availability of personnel, the management team could consist of only one individual. In any case, the purpose of this team is to facilitate the work of the contractor by providing oversight, guidance, and information. Figure 6 shows one possible form a customer’s project team might take.
1. Project Manager Project managers are typically senior engineers or production managers who are intimate with the facility and the production team. They are the prime point of contact for the contracted organizations (i.e., the constructors, vendors, and engineers). As such, project managers are generally consid-
Whitt2003.book Page 29 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 2: THE PROJECT TEAM
29
Figure 6. One form of a customer’s project team (dashed boxes are external) ered to be “the clients” by the contractors, who consult them on a myriad of issues. They are facilitators who help to clear obstacles. They pull information from the plant technical groups or set up interviews with the operators. They interpret unclear or ambiguous directives. They also typically have limited budget authority.
2. Production Representative A project manager’s primary customer is the production division. These production groups (who are the ultimate source of funding for the project) identify a need and appoint a representative to interact with other departments. This individual is sometimes called the operations or production representative and is typically a person who is intimate with the production issues and has enough engineering background to be able to communicate with plant engineering to whom the initial request for assistance is made.
3. Technical Representative A project’s technical representative is generally from the maintenance department. This individual is tasked with monitoring the project to ensure the interests of the maintenance department are given proper consideration during the design phase. This function is often overlooked, and input from this quarter is sometimes not sought early enough to have much impact. Occasionally, rework is the result. It is the project manager’s responsibility to make sure both the production department’s and the maintenance department’s concerns are addressed.
4. Construction Liaison A construction liaison may be appointed by the project manager to facilitate construction and provide oversight. This person acts as liaison between engineering and construction and also monitors the construction team’s installation and safety practices. Construction liaisons are the main point of contact for the construction team, and, though they are constrained by project budget and scope of work, they typically work to guard the interests of the maintenance department during the construction phase. The customer is actually several entities, each with its own set of concerns. Contracted personnel need to realize the constraints under which project managers and others in a customer’s organization must operate. The process that results in a project begins long before the contract engineer or constructor gets to the site.
Whitt2003.book Page 30 Thursday, July 10, 2003 4:05 PM
30
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
B. The Designer Like the customer, the designer is an amalgam of several entities. For the purposes of this discussion, the designer will be an engineering firm that has been contracted to take the desired end result as envisioned by the customer and engineer a solution that is both constructable and cost-effective. The design team usually consists of several “disciplines,” or groups with different skills. For example, a design team might require civil engineering to build a structure, electrical engineering to provide lights and power, and mechanical engineering to provide plumbing and other services. These different groups must be managed and their efforts coordinated to achieve a common purpose. Figure 7 and its accompanying discussion present a top-down description of the project team.
Figure 7. Engineering design team
1. Project Manager The project manager has overall responsibility for the project. This person typically has developed a business relationship with the customer and is sometimes quite possessive of that relationship. A project manager guards the customer’s interests within the framework of the project scope, budget, and schedule. The engineering firm generally depends heavily on this person for business development (i.e., sales).
2. Project Engineer The project engineer manages the design team. This person coordinates the efforts of multiple disciplines as they each pursue their particular interests. The project engineer ensures the various discipline engineers are working in concert, using proper procedure and executing their tasks in a manner that is consistent with the goals of the project team. The project engineer also resolves or
Whitt2003.book Page 31 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 2: THE PROJECT TEAM
31
prevents disputes by enforcing good communications practices among the disciplines. This person is (or should be) an enabler, making sure that all forces are properly trained and have all the support personnel and materials they need. The project engineer’s function is sometimes combined with the project manager’s function, with the same individual performing both roles.
3. Discipline Project Engineer A discipline project engineer manages a discipline’s efforts as they relate to a project. A discipline design team typically consists of an engineering staff and a technical support (design) staff. The engineering staff generates conceptual design documents that the technical support staff uses to build a complete documentation package that is suitable for construction and maintenance. Discipline engineers coordinate their activities with other discipline engineers under the direction of the project engineer. Discipline engineers manage their staff to ensure it is functioning efficiently and effectively.
4. Discipline Engineering Staff The discipline engineering staff generates engineering products and services under the direction of the lead discipline engineer. These engineers work closely with the design staff to satisfy the scope of work.
5. Design Supervisor The discipline design supervisor reports to the department head (not shown). The design staff reports to the design supervisor administratively. This person is also responsible for the overall quality of the output of the design and clerical staff.
6. Discipline Technical Support (Design) Staff a.
Lead Designer The discipline lead designer is responsible for the technical design content of the engineering package. This person manages the efforts of the technical support staff, which includes the other designers, CADD drafters, and clerical support under the overall direction of the discipline engineer. This staff uses the information developed by the engineering staff to develop construction drawings and documents for record. The discipline lead designer also coordinates efforts directly with other technical staffs from the client and construction organizations.
b. Designer Designers are technical support personnel with particular skills. Their abilities can range from expertise in a single area of design up to complete competence in all aspects of the design. They are responsible for the technical content of the design drawings, bills of material, databases, etc.
c.
CADD Technician CADD technicians are responsible for the production of the drawing package.
d. Clerk Clerks generate databases and bill of materials listings and perform other administrative tasks. Sometimes the CADD Technician will double as the project clerk. Execution of a design project is a team effort. Design teams are generally ad hoc groups that are assembled for a specific project and then are disbanded. These individuals learn to adapt quickly to new situations and to coalesce into teams on short notice. The success of the project depends on the organization’s ability to execute this maneuver in a timely manner.
Whitt2003.book Page 32 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
32
C. The Constructor Like the designer, the constructor is an amalgam of several entities. These entities are called crafts. Electricians, pipe fitters, and welders are examples of crafts. The construction team’s organizational structure falls more in line with electrical and instrumentation (E&I) with controls falling somewhere among them. Figure 8 and the following discussion present a top-down description of the construction team from the E&I perspective.6
Construction manager
E&I superintendent
Other superintendents
General foreman
Engineering coordinator
Electrical foreman
Instrument electrical foreman
Instrument foreman
Fitter foreman
Motors, switchgear, substations, etc.
Instrument, cable, and conduit checkout
Instrument air tubing and installation
In-line instrument installation
Figure 8. Construction team
1. E&I Construction Superintendent The superintendent’s role on the construction team corresponds to the role of the discipline engineer on the design team. If the project is large enough, each discipline could have a dedicated superintendent. The superintendent is responsible for building a good construction team. Following are some of the most important personnel choices the superintendent makes: • •
A team of frontline supervisors A good material expediter, coupled with knowledgeable receiving and warehouse personnel who will inspect and catalog all instruments for tracking purposes.
This individual is ultimately responsible for schedule and budget, quality of work, safety of the construction team, and accurate time reporting. In short, the buck stops with the superintendent during the construction process.
2. E&I Field Engineer and Coordinator The E&I field engineer interfaces with the design engineer and the E&I superintendent to ensure proper field installation of instrumentation. In coordination with the E&I superintendent, the field engineer performs material takeoffs for all instruments and associated items (if not already provided by the design team). This includes material such as tubing, tube tray/track, tube fittings, and mounting extras such as angle iron, nuts, bolts, and miscellaneous parts. This person also generates bills of materials for electrical items such as conduit, cable, electrical fittings, and associated parts to
Whitt2003.book Page 33 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 2: THE PROJECT TEAM
33
install the wiring for instrumentation systems. The field engineer is also responsible for initiating field change notices (FCNs) or design change notices (DCN’s) as design modification needs are uncovered.
3. E&I General Foreman The E&I general foreman works with the superintendent and other foreman to develop weekly work plans and daily task plans to ensure craftsmen know the priority of projects for the day and week.
4. Instrument Foreman The instrument foreman creates daily and weekly work plans and ensures proper installation procedures are followed by the instrument fitter and/or mechanic.
5. Instrument Fitter or Mechanic The instrument fitter installs each instrument according to installation details. Tubing is run to all valves that are automated by either a solenoid valve or an I/P converter. This person also installs all instruments and associated hardware, including instrument air piping.
6. Pipe Fitter The pipe fitter installs all inline devices such as control valves, magnetic flowmeters, on/off valves, and associated piping required for pressure gauges, pressure switches, and miscellaneous devices.
7. Instrument Electrical Foreman The instrument electrical foreman creates daily and weekly work plans and ensures proper electrical specifications and procedures are followed by the electricians with respect to the instrumentation installation effort. This person supervises installation of conduit, wire pulls, and termination at the instrument and the DCS/PLC at the instrument’s proper address, as well as point-to-point wiring checkout. The project team is supported by three legs: the customer, the engineer, and the constructor. If any of the three legs are dysfunctional, then the project stands a good chance of failing. The three groups must not only work well within their organizations, but also among themselves. The best way to work together is for each to understand the other guy. If an organization attempts to anticipate another organization’s actions by understanding the driving forces behind those actions and to preempt problems, the value of that organization to the project increases inestimably.
Whitt2003.book Page 35 Thursday, July 10, 2003 4:05 PM
Chapter 3: The Managed Project A well-conceived, well-managed project is one that has been given a chance to succeed. Conversely, a poorly managed project may fail regardless of its conceptual viability. If a project fails, yet is well managed, then some positive effects can probably be salvaged—even if the outcome is merely a list of lessons learned. In such a project, the problems will likely be well defined, making it possible to avoid similar entanglements in the future. In a poorly managed project, the root causes may never be uncovered. Well-managed projects do not just happen. They begin with the basics. All members of the project team need to have a clear understanding of the work that needs to be done and a clear view of their role in the process. The days of “mushroom engineering,” in which the project manager keeps the design staff in the basement cranking out drawings, are over. Today, design teams need to be fully engaged from top to bottom—more of a “Velcro” interface. The conversion from “mushroom” to “Velcro” means that the support staff needs to become more sophisticated and more attuned to the specific issues being addressed by the project. Clerical staffs, for example, should be just as familiar with their counterparts in other organizations as the project manager.
A. Scope of Work The first step on the path to a successful project is the generation of an accurate scope of work. A scope of work is simply a description of the tasks that need to be accomplished to achieve the desired end. It is the result of a cycle of investigation intended to eliminate or reduce the number of assumptions that need to be made later. As a general rule, meetings in the initial stages of a project are attended by senior-level managers. The number of participants in these early meetings is kept to a minimum to keep costs low until the project is awarded. As a result of the small number of participants exposed directly to the information, capturing the information on which the bid estimate is based becomes very important. To compound matters, the project specification provided by the customer is usually inadequate for the purposes of a detailed scope of work. Therefore, an internal document that amplifies upon the project specification is needed. The project specification, then, becomes the basis for a more detailed document called the project scope of work. Each discipline is responsible for developing its own individual scope of work based on the project specification, which will become a piece of the overall project scope of work. This is done in consultation with vendor contacts and with appropriate technical resources within the customer’s organization. After the disciplines have generated their discipline scope sections, they are fed back into the project scope of work execution narrative. The finalized scope of work, along with the project estimate and project schedule, is then used as the basis for producing a proposal, or perhaps a phaseone study. If the project is approved, the scope of work is ultimately used as a project management tool by the engineering disciplines. It is recommended that the project scope of work be written in sections that reflect the way in which the project will be executed. For example, if construction will occur in four distinct areas of the plant, then there should be one section in the scope of work for each area of construction. There
Whitt2003.book Page 36 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
36
will likely be a need for a fifth section in the document to cover common services that are not specific to a process area. Each of the sections dealing with a specific area should have subsections devoted to each engineering discipline, even if a particular discipline has no work in that area. The phrase “Not applicable to this discipline” is good information to have. Also, the scope of work will eventually be used as the basis for the proposal. Therefore, the format of the document presented here is very similar to that of the final proposal. The primary difference is that the scope of work has no cost or schedule information. It is merely an internal document that is used to generate a budget estimate and a schedule. Later, once the project has been approved, this document can become a valuable project management tool for the design team. Following is a description of some of the information that should be presented in a scope of work:
1. Executive Summary The executive summary cuts to the chase; it provides the “bottom line” of the project. This section is necessary only if the scope of work document is intended to be a deliverable to others outside the immediate group. This section remains blank until both the estimate and schedule have been completed as the data developed in those sections are summarized here. The executive summary should contain a simple statement of project purpose—a paragraph or so—followed by a cost table or chart and a schedule table or chart. This information can be followed by a short description of some of the key elements of the project.
a.
Statement of Purpose The statement of purpose describes in broad terms the reason for the project. An example of a simple statement of purpose follows: “The existing plant Autocall alarm system in Building 504A is defective. This project will replace the existing autocall plant alarm system with a new Autocall system and replace alarm bells as necessary as identified by field examination. The project will be supervised and funded by the facilities department. The new system will be designed and installed by the maintenance department and will be in place by early March.” This statement should tell who, what, where, when, and how.
b. Summary Data Data presented in the executive summary should be fully supported in the body of the document. For example, dollar amounts shown should be detailed somewhere in the document so that if more detail is needed about how the cost was derived, it may be easily located. The data should provide information as to total project cost and total project duration. Also, depending on the type of project, a schedule of payments and a rate schedule may need to be generated.
2. Clarifications This section should list and discuss “grey” areas of the project that require a sharper focus. This may best be done in sections labeled “Inclusions” and “Exclusions.” These sections do not need to be comprehensive, but should include only those items for which there may be a misunderstanding as to their disposition. A comprehensive “Assumptions” section should be included, however, that lists all assumptions made and their levels of uncertainty.
Whitt2003.book Page 37 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 3: THE MANAGED PROJECT
a.
37
Inclusions If a controversial or unapparent task or function is intended in this proposal, then it should be clearly noted in the inclusions section. This is in the best interest of all concerned, particularly if this document is being submitted as part of a competitive bid. At times, an award may be given to the low bidder simply because he did not include a task that was included in the competition’s proposal.
b. Exclusions The exclusions section should note any related work that will be done by others. Perhaps a customer organization, for example, has elected to do a portion of the project using its own maintenance forces. This section should detail this and any other such aspects of the project that are specifically excluded from the scope of the design team.
c.
Assumptions An assumptions section is very important. Rarely is enough information available to be absolutely sure of the work that will need to be done. Assumptions must often be made to allow work to be estimated. Sometimes worst-case scenarios are used, and sometimes bestcase scenarios. All assumptions should be noted in this section along with the thought process that led to each assumption. It is also a good idea to state the level of certainty (or uncertainty) when describing the assumption.
d. Safety Concerns Any areas of concern regarding personnel or equipment safety should be noted here. If the customer has safety training requirements, they should also be noted.
3. Project Description The description narrative provides general information as to the current state of the system and a statement of intent as to the work that is anticipated. This narrative should be a “birds-eye” view of the system. It might be worthwhile to refer to a site plan or block diagram here if one is available. The following information should be presented in some fashion:
a.
Existing System What process areas are involved? Where is the equipment located? What is its general state of repair? What is the availability of power and services?
b. Disposition of Existing Equipment What existing items will be demolished, refurbished, relocated, or replaced? How will these activities be done? Who will be responsible? How will this be documented?
c.
Disposition of New Equipment What new equipment will be added? Where? How will the area be prepared? Who will purchase the equipment? How will this be documented? How will this affect existing power and service capacity?
d. Company and Applicable Industry Standards If the company has standards that apply to this project, they should be listed here. Any industry standards that are necessary or that are superceded by the company’s standards should be listed. Any applicable guidelines should also be listed. The following questions should be anticipated and answered: Are there any unusual requirements or safety concerns? What pertinent standards were listed in the project specification?
Whitt2003.book Page 38 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
38
Impediments that would prevent members of the design team from consulting the standards should be removed. The best way to ensure standards are easily consulted is to provide copies of the standards, or at least instructions as to how they may be obtained.
e.
Approved Vendors List Does the customer have specific vendors in mind to supply the equipment? This information is probably listed in the project specification and can be copied and placed in this section.
f.
Equipment Any equipment mentioned in the narrative should be listed here with a cross-reference to pertinent drawings. If this list does not exist, then the customer contact who will facilitate generating the list should be indicated.
g.
Instrumentation If the customer has an existing instrument and/or I/O list, it should be included here. Otherwise, the customer contact who will facilitate gathering this information should be indicated.
h. Drawings If the customer has a drawing list, it should be included here. Also, reference should be made to the customer contact for document control. Guidance should be included as to how to interact with this individual. It sometimes proves beneficial to appoint an internal resource as the single point of contact with this individual to reduce confusion. Any internal guidelines for document control should also be included in this section.
4. General Execution Strategy The general execution strategy is a detailed plan of attack at the project level. The activities of all disciplines should be included. The information should be presented in a logical progression of activities that culminate in checkout and startup of the facility. The structure of the general execution strategy is then copied into the discipline execution strategy sections, and each discipline adapts the description of work required to its own needs.
a.
Initial Investigation This section describes the investigation activities required to proceed. Information regarding on-site walk-downs of the facility, gathering of documents, the need for operator interviews, and so on, should be included.
b. Specify and Order Long-Lead Items If any items require long delivery times, they should be identified and ordered as early as practical. This section should list any items of particular concern.
c.
Identify Vendor-Provided Preengineered Subsystems If any subsystems are to be installed intact from the vendor, they should be listed here. Any anticipated interaction on the part of the design team should also be noted. A factory acceptance test may be necessary. Vendor drawings often need to be reformatted into the customer’s drawing system. These issues need to be addressed as soon as practical.
d. Execute Design Tasks This section should list each major task for each process area that falls under the scope of the project. Each task should then be evaluated from the perspective of each discipline.
Whitt2003.book Page 39 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 3: THE MANAGED PROJECT
39
All execution statements should begin with verbs to convey the type of work being done: 1.0 Area X 1.1 1.2 1.3 1.4 2.0 Area Y 2.1
2.2 3.0 Area Z 3.1 3.2 3.3 3.4 3.5
Demolish existing tank X Install pump X Install new tank X Install in-line instruments Refurbish main feed pump PP-7 2.1.1 Remove from service 2.1.2 Replace impeller 2.1.3 Replace seals 2.1.4 Paint 2.1.5 Reinstall and return to service Recalibrate instruments Install computer floor Refurbish lighting Refurbish Fire Suppression System Install computer furniture Install computer hardware
Each task has a unique number called a work breakdown structure (WBS) number. For example, the WBS number for painting pump PP-7 is 2.1.4. An estimate and material cost will be derived for this item and stored as part of the project estimate.
e.
Submit Package to Customer for Design Review If the customer has any specific oversight requirements that result in work, that work should be detailed here. Usually, an intermediate point in the design is chosen for a “spotcheck” to make sure work is progressing according to expectations. Sometimes partial payments for services rendered are tied to these design reviews. Because these take time to prepare, a statement should be included here to indicate the level of detail that might be required.
f.
Deliverables The deliverables section should detail any specifics regarding classes of deliverables the disciplines will need to produce for record. Other documents, such as construction documents or documents for internal use, might need to be done, but this section should list only the documents that will be eventually turned over to the customer. For example, the customer might not see the need for instrument location plans, but the constructor might need them to increase efficiency. In this case, the engineering team might elect to produce location plans but never issue them to the customer.
g.
Attachments Supporting documents should be included as attachments. Some of the types of supporting documents are as follows: • • • • • •
Drawing list Instrument and I/O list Equipment list Project cost estimate Project schedule Sketches
Whitt2003.book Page 40 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
40
A properly executed scope of work—while initially somewhat time-consuming to produce—is essential to the proper management of the project. It is a communication medium that allows the customer’s needs to be placed within the context of the design process. If properly executed, the scope of work eliminates misunderstandings and forms the basis for developing a realistic, task-oriented project schedule and budget. After the project is approved, the scope of work can help the project manager and design team manage their work.
B. Estimate* A proper understanding of the project requirements begins with a well-defined scope of work, as previously discussed. But, the scope of work is only part of the story. After “what” is addressed by the scope of work, “how much” and “when” need to be addressed. Therefore, the next step on the path to a successful project is to generate an accurate estimate of material cost and labor in terms of time. These measures define the “physics” of the situation, setting limits that affect the way in which the project will be executed. These physical measures are the primary tools of the project manager in tracking the project on the strategic level and of the design supervisor in managing the work on the tactical level. The scope of work defines the work to be done. The material cost estimate and labor cost estimate define the parameters within which the work will be done. There are three main types of estimates: budget, bid, and definitive. Following is a brief description of each: •
•
•
*
The budgetary cost and labor estimate is, many times, produced by a group who is familiar with the site and with the process. This group may or may not execute the project. The purpose of this type of estimate is primarily to obtain funding. It is typically “quick and dirty” and is expected to be rather inaccurate. In fact, an error margin of ±30% is acceptable for this type of estimate. Prior to this estimate, a formal scope of work has probably not been done, and, quite possibly, the project specification has not been finalized. This type of estimate is generally unfunded by the customer, or at least underfunded. The service provider pulls the numbers together as quickly as possible with a minimum of research. The expectations for the bid and definitive estimates, on the other hand, are much higher. The bid material cost and labor estimate is produced by the various engineering bidders vying for the work. Again, this estimate is typically unfunded by the customer. The raw information for this estimate is the finalized project specification bid package. All prospective bidders are provided identical bid packages on which to base their bids. This bid package is sometimes flawed or incomplete, but the resulting bids give the customer a good picture of the capabilities of each bidder. Usually, all bidders produce a written proposal that accompanies their estimate. The proposal describes the work as understood by the contractor. This gives the customer an idea of the deliverables each bidder plans to provide. It also gives the customer a means for comparing the capabilities of the various bidders. The definitive material cost and labor estimate is prepared by the engineering firm that was awarded the contract based on their bid. The customer typically includes this as a part of the project, so it probably is fully funded. Once the contract has been awarded and any secrecy agreement issues have been settled, the engineering contractor is given full access
For an in-depth look on how to generate an accurate bid estimate and create a project schedule using Microsoft® Excel, a CD-ROM entitled “Software Tools for Successful Instrumentation and Control Systems Design” is available. Turn to page 355 for more information or visit ISA’s website at http://www.isa.org/whittCD.
Whitt2003.book Page 41 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 3: THE MANAGED PROJECT
41
to the information developed by the customer during the internal evaluation process. The engineering firm then develops a formal scope of work. This information sometimes alters the picture significantly, and the engineering contractor is given an opportunity to adapt the estimate and schedule to the new information. Of course, this reestimating process is bypassed if full disclosure was made during the bid process. In that case, the bid estimate becomes the definitive estimate. The estimate is the baseline document for project management, providing a yardstick to which performance will eventually be measured. It is based on the scope of work and should reflect the work scope on a task-by-task basis wherever possible. Many estimating tools are available. Whichever is chosen, you should be able to produce estimates that are • •
•
• •
accurate, by identifying each task relating to the scope of work and then quantifying the labor and expense of its execution. timely, by being repeatable. Once an estimate structure has been optimized for a particular customer, subsequent estimates should simply build upon the first, thus decreasing the cost and time required to generate them. Each project should be approached in a consistent manner, with consistent estimating practices and tools. verifiable, by adding notes and amplifications and by making the calculations available for dissection. Remember, the time span between the estimate and project execution can be large, and the estimator may not be the executor. meaningful, by relating all the deliverables to hard data. The need for rules of thumb and suppositions should be minimized. adaptable, by being easy to modify.
C. Schedule* After the definitive material cost and labor estimates are produced, a schedule can be generated based on the resources that are expected to be available. The project schedule is built from the project estimate. If the estimate is delineated by task, the project will be easier to manage. If the estimate is built by deliverable item, it will be more difficult. Regardless of the estimate format, schedules are oriented by task. These tasks are broken down by WBS. Each task has a unique WBS identifier. In a perfect world, the WBS would be generated as a part of the original scope of work, with these identifiers already assigned. First, each task listed in the scope of work needs to be evaluated and an estimate made for the labor required. For example, if a two-person team is envisioned for a 120-hour task (3 weeks), it may be inferred that the task will take one and a half calendar weeks to perform, assuming, of course, that the two individuals will be 100% dedicated to that task. If they are expected to be less than 100% effective during that time, it would take more calendar time. Next, each task needs to be evaluated as to its relationship with other tasks. For example, generating loop sheets depends on the P&ID drawings. The P&IDs, therefore, are predecessors to the loop sheets. Linked relationships should be identified and analyzed. For the most part, these relationships may be defined as follows:
*
For an in-depth look on how to generate an accurate bid estimate and create a project schedule using Microsoft® Excel, a CD-ROM entitled “Software Tools for Successful Instrumentation and Control Systems Design” is available. Turn to page 355 for more information or visit ISA’s website at http://www.isa.org/whittCD.
Whitt2003.book Page 42 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
42
•
• • •
Start-to-start: Task B can’t start until Task A starts. This relationship is used when an outside trigger initiates a scheduled chain of events. For example, receipt of a specific material shipment might trigger several tasks at the same time. Finish-to-start: Task B can’t start until Task A finishes. Start-to-finish: Task A can’t finish until Task B starts. Finish-to-finish: Task B can’t finish until Task A finishes.
After the relationships are defined and the resources have been assigned to each task, the overall project duration may be estimated. Many times, the customer has a time frame in mind already, which constrains the schedule to a particular set of milestones.* When the schedule is compared to this time line, resources may need to be modified to lengthen or shorten the schedule.
D. Status Report After the project has begun, the schedule should be used as a management tool to help track progress. Periodically, the design team will be asked to provide some feedback as to their execution status. This feedback will answer questions such as the following: Did you start the project on time? What is your completion percentage? Will you finish the project on time and within budget? Reporting data should be collected for each task (WBS item) and then plowed into the overall project schedule. Status reporting typically includes updating the following parameters: The design team provides data for each task as follows: • • •
Start date: If the task is not started, is the anticipated Start Date still accurate? If the task has been started, what date did it start? Finish date: If the task has not finished, is the anticipated Finish Date still accurate? If finished, what was the date of completion? Percent complete: If the task is active, what is the estimated completion percentage?
The scheduling team plows that information back into the schedule. For example, if a start date is moved by the design team, the schedule is updated to reflect the change. Successor tasks need to change accordingly depending on their relationship to the task in question. After data have been collected, the schedulers begin drawing some conclusions based on the information as follows: •
Earned hours The completion percentages will be used to develop earned hours. This is done by multiplying the reported percent complete by the total number of hours allocated to the task. For example, if a task has 100 hours allocated and the design team reports 50% completion on the task, then the earned hours value is 50.
•
Actual hours Actual hours are the number of hours actually expended to date.
•
Efficiency ratio By comparing actual hours to earned hours, it is possible to develop a ratio that describes the performance of the design team as compared to expectations. In our previous 100-hour task example, we might find that 35 hours were expended on that particular task. Therefore, the efficiency rating of the design team for that task would be 50 divided by 35, or
*
Milestone –A schedule item that is pegged to a particular date. These usually represent targeted points in the engineering process such as “issue drawings.”
Whitt2003.book Page 43 Thursday, July 10, 2003 4:05 PM
PART I – CHAPTER 3: THE MANAGED PROJECT
43
1.43. If 60 hours were expended, the rating would be 50 divided by 60, or 0.83. Any rating under 1.0 should be flagged for further investigation. As a practical matter, relating actual hours down to the task level is difficult because time is generally not kept to that degree of resolution. But, since the estimate is broken down to that level, it is possible to derive task impact factors to help relate the percent complete values being reported to the actual hours. If, the design team were able to report time in only one category—instrumentation, for example—then only the total hours expended by that group would be available for comparison. That is pretty poor resolution! Let’s assume there were 10 design tasks that needed to be done by this group (see Figure 9). Of those, only four have been started. The design team estimates 90% completion on task 01, 75% on task 04, 50% on task 05, and 10% on task 06. The number of estimated project hours for this group is 4270 hours. Based on the percent complete listed, a total of 1175 hours should have been expended. Actual hours logged against these 10 tasks is 1250. This yields an efficiency rating of 94%. So, while regular progress reports may yield a wealth of inferred information, the original data might not be very useful.
Actual hours :
Task 1 2 3 4 5 6 7 8 9 10 Total
1250
Status Report Data Estimated % Comp 250 90% 400 0% 80 0% 400 75% 1000 50% 1500 10% 400 0% 80 0% 80 0% 80 0% 4270
Efficiency rating:
Earned 225 0 0 300 500 150 0 0 0 0 1175
0.94
Note: Efficiency rating is calculated by dividing earned hours by actual hours. Figure 9. Calculating efficiency
Perspective is sometimes difficult to maintain, particularly when a person is involved in the fine details of getting the job done. But, the loss of perspective can cause serious problems. Keeping an “eye on the ball” can be a challenge, particularly if a basic knowledge of project structure, participants, and management is lacking. Part I has been about providing perspective. It answers the questions “what,” “who,” and “how” as they relate to a typical engineering project. What are the major project types? How should designers adapt their thinking based on the type of project? Should interaction with the customer be minimized, or should a designer seek the customer’s
Whitt2003.book Page 44 Thursday, July 10, 2003 4:05 PM
44
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
advice? Should the design be for construction only, or should it provide detail for maintenance as well? What are the real measures of success? Who is the designer’s counterpart in the other organizations? What are some of the key concepts in setting up and managing a project? How do you measure your progress? It is hoped that you, the reader, now have a better grasp of these issues. Part II in this book delves into some of the key technical issues surrounding design engineering.
Whitt2003.book Page 51 Thursday, July 10, 2003 4:05 PM
Chapter 4: Scaling Instrumentation is all about manipulating information. Having the ability to take a sample of a physical process element such as fluid temperature or gas pressure is of little benefit unless someone can make use of the information. In today’s high-speed, low-overhead environment, having an operator manually record the deflection of a needle is no longer an option. Today, the information must be prepackaged, timely, and accurate. So, we in the instrumentation profession must be adept at unit conversions and understand instrument scaling. From the physical measurement to the electrical signal to the numeric representation to the displayed data in engineering units, the conversions must be understood and properly implemented. In this context, the word scaling implies the scale of a ruler. A ruler is marked in inches and parts of inches, or in meters and parts of meters. The ruler, therefore, is said to be scaled for its units of interest (inches or meters). This lesson is an introduction to basic signal scaling. Process controls designers and troubleshooters, and PLC programmers in particular, must be able to maneuver through the various permutations of a signal. But, before we get into the specifics of instrument scaling, a review of some instrumentation basics is in order.
A. Definition of Key Terms • • •
•
•
•
Calibrated zero: A transmitter’s lowest scale setting. A transmitter that is scaled from 15 to 150 pounds per square inch (psi) has a calibrated zero point of 15 psi. Calibrated span: A transmitter’s highest scale setting. A transmitter that is scaled from 15 to 150 psi has a calibrated span point of 150 psi. Range (scale), calibrated: The difference between an instrument’s calibrated span point and its calibrated zero point. An instrument’s calibrated range is usually configured by the user. A transmitter that has been calibrated (scaled) from 15 to 150 psig has a calibrated range of 135 psig. This should not be confused with its design range, which can cover a much wider span than what has been calibrated and is the instrument’s safe operating limits. Range, design: The maximum input span for which a device can provide a linear output. A transmitter that can provide a linear output signal for an input pressure range from 15 to 150 psig has a full range of 135 psig. This is also referred to as the span. This should not be confused with its calibrated range, or scale, which can cover all or just a portion of the unit’s full range. Rangeability (turndown): The ratio of an instrument’s maximum range to its minimum range. If an instrument’s output signal will remain linear for input ranges that are between 0–50 and 0–100 psig, then its rangeability ratio is 100:50, or 2:1. Resolution: The degree to which a change in an instrument’s input is reflected in its output. A computer’s resolution is defined by the size of the data word that can be accommodated. A PLC’s analog input might have 12-bit resolution, which equates to 4096 discrete values that can be used to represent an input voltage or current. For example, if an input signal’s range is 0–10 VDC, a change of 10 V/4096 =.00244 V will be detected.
Whitt2003.book Page 52 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
52
•
• • • • •
Scale: The portion of an instrument’s design range for which it is calibrated to provide a full-scale linear output. It is the calibrated range of the instrument. An instrument’s scalability is the ratio by which the scale can be different from the range. Set point: The point at which a process is supposed to operate (control set point), or the point at which an alarm should occur (alarm set point). Span: See Range. Turndown: See Rangeability. Units, engineering: Units of measure that are useful to the operator. Examples of engineering units are pounds per hour, feet per second, and degrees F. Units raw: Units of measure at the sample point. Examples of sample units are millivolts (mV), milliamps (mA), and inches of water column (inwc). These values are generally of little use to the operator.
There are several good books available that provide a more detailed look at instrumentation concepts and principles. Refer to the ISA Press online library at www.isa.org/books.
B. Accuracy Measurement accuracy is critical to proper system performance, and it is, for the most part, quantifiable. Following are some of the factors that may limit measurement accuracy: •
Mechanical factors • Leaks in the sensor lines (causes span shift) • Mechanical loading (causes zero shift) • Impurities in sensor lines (causes nonlinearity) • Deadband: an attribute of an instrument that describes how well it responds to a change of direction of its input. For a pressure transmitter scaled 0-100 psig with a 1% deadband, it will take 1 psig of downward movement of the pressure to overcome inertia or mechanical slop that was in place due to previous upward movement of pressure.
Typical deadband response to a linear change in input.
Figure 1. Typical error pattern caused by deadband
•
Hysteresis: caused by internal friction, hysteresis is usually evidenced when there is a different output value if the input is at 50% of scale and rising versus when the input is at 50% of scale and falling.
Whitt2003.book Page 53 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 4: SCALING
53
Typical hysteresis curve: As the input changes up or down in a straight line, the output changes with an offset depending on the direction of change.
Figure 2. Typical error pattern caused by hysteresis • •
•
•
Repeatability: the ability of a device to precisely duplicate its output in response to an input signal. Environmental factors • External heating and cooling (causes span shift) • Humidity • Vibration Electrical factors • Output linearity • Component age (causes drift) • Resolution (see Section C below…) Human factors • Calibration • Installation • Manipulation
C. Resolution Effects on Accuracy An instrument’s accuracy is limited by its precision. An instrument’s precision is determined by making minute variations of the measured element (e.g., pressure, temperature) and then monitoring the instrument’s output for a response. The smallest magnitude of change an instrument can detect and then reflect at its output is its precision. This precision rating can be listed in percent of span or in engineering units. For example, a hypothetical ultrasonic transmitter might have a detection range of 0–12 ft with its output scaled 4–20 mA, precise to ±0.1-inch. Precision can be equated to the instrument’s resolution. Rather than a smooth movement of the output as the tank level changes, the output will “step” to a new milliamp value as the level changes in 0.1-inch increments. In essence, the meter’s resolution is 12 ft x 12 in/ft x 10 steps/in = 1440 steps across the range. Therefore, the 4–20 mA signal will change in increments of 16 mA/1440 steps = .01111 mA/step. In the digital world, bits are units of resolution. The term 12-bit resolution tells us the smallest change of signal magnitude that can be reflected by the computer or device. This resolution value relates to the margin of error. Since each device in a system has its own associated resolution (hence, its own margin of error), the overall accuracy of a system is decreased every time a signal is con-
Whitt2003.book Page 54 Thursday, July 10, 2003 4:05 PM
54
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
verted or retransmitted. In some extreme cases where accuracy is super-critical, the best move is to digitize the signal at the sensor and then transmit the value as a digitized data stream rather than as a pure electrical signal, thus eliminating several layers of conversion. Most PLCs currently have 12-bit resolution on their analog inputs. This means that the analog signal is converted to a 12-bit binary integer. Once in integer format, the value can be converted to a decimal integer, or hexadecimal, or whatever, for display. A 4–20 mA signal has a span of 16 mA (20 – 4 =16). This 16 mA span might represent the 0–100% output of an ultrasonic transmitter or other device. For an ultrasonic meter with a calibrated range of 12 ft, how much error will the PLC introduce to the system? 12-bit resolution: 4096 divisions Resolution error: 144 inches/4096 = .0352 inches
D. Instrument Range versus Scale There is a difference between an instrument’s range and its scale. When an instrument is received, it comes with an inherent range. This range value defines the maximum input span for which the device can provide a linear output. For example, an ultrasonic level transmitter might have a range of 12 ft. If we place that transmitter in a 6-ft tank and don’t recalibrate it, we will lose resolution. Its output will only change 50% for a 100% change in tank level. To rectify this, the unit needs to be recalibrated to provide a 0–100% change in output for a 0–50% change in its input, provided the device is scalable to that degree. Sometimes a device is not scalable beyond, say, 10% of its range. This is called rangeability.
E. Instrument Calibration An instrument’s scale and its calibrated range are synonymous. Once a scale is decided on, the instrument must be calibrated. If its range is 0–550 psig and its scale is 10–350 psig, its calibrated span is 350 – 10 = 340 psig. The calibration end points are the zero point and the span point. The point at which the process is expected to operate is called the set point, though this is not generally part of a transmitter calibration other than to confirm that the anticipated set point is near the center of the calibrated span.
F. Linearization and Unit Conversions Instrumentation and control is all about converting (or transducing) physical properties into a more useful format. Pressure in a pipe is converted to mechanical deflection of a diaphragm, which is converted to electrical energy, then to computer data in the form of an integer value, and then to a floating-point engineering unit value for display. This information is also used to help generate output commands, which are converted to electrical signals and then to mechanical action. The trick is to understand the input/output relationships of the various converters. For example, a flow orifice will cause a predictable pressure drop as fluids flow across it. A pressure transmitter can measure this pressure drop. Though this pressure is not linear with flow rate, it has a repeatable relationship to it. This relationship is best approximated as a square-root function. Taking the square root of the pressure signal effectively “linearizes” it with the flow rate. After a linear relationship has been established, the entire conversion sequence from transmitter to computer display can be deduced from one measurement.
Whitt2003.book Page 55 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 4: SCALING
55
To make use of this phenomenon, the technician must be able to move readily from one set of units to another and from one numbering system to another. Computers can communicate using binary, octal, hexadecimal (hex), decimal, BCD, or even more arcane numbering schemes. It is important to know when one is more appropriate than the others. For fun, here are a few conversion problems. Work the problems using the charts provided in Figure 3 (no calculators needed!).
Binary Value Dec 32768 16384 8192 4096 2048 1024 512 256 128 64 32 Bin 2^5 2^4 2^3 2^12 2^11 2^10 2^9 2^8 2^7 2^6 2^5 Bit 16 15 14 13 12 11 10 9 8 7 6 Table 1. Decimal-to-binary conversion Dec
Hex
0
0
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
10
A
11
B
12
C
13
D
14
E
15
F
16 2^4 5
8 2^3 4
4 2^2 3
2 2^1 2
1 2^0 1
Problems 1. Convert 001101100110 (bin) to decimal:
Table 2. Decimal-to-hexidecimal conversion
2. Convert 101101000111 (bin) to decimal:
3. Convert 101101000111 (bin) to decimal:
4. Convert 2020 (dec) to binary:
5. Convert 6060 (dec) to binary:
6. Convert B5A2 (hex) to binary:
7. Convert 1EC2 (hex) to decimal:
ans: 1) 870, 2)2887, 3) 0B47, 4)011111100100, 5) 001010010100, 6) 1011010110100010, 7) 7874 (hint: hex-to-binary-to-decimal)
Figure 3. Conversion problems
Figure 4 depicts two typical temperature measurement circuits as follows: The top configuration uses the internal power supply of the transmitter to power the signal loop. This configuration is referred to as a “four-wire” loop. The bottom configuration uses an external power supply to power the loop. This configuration is referred to as a “two-wire” loop.
Whitt2003.book Page 56 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
56
4-WIRE XMTR
H
110 VAC
N
PLC
ANALOG INPUT MODULE
+
+ 4-20 mA
R
-
HMI
PLC DATABASE 0-4095 40001
V
PLC internal memory location addresses
475 °C
1-5 VDC
-
+
T/C TYPE K
24VDC POWER -
-
-
+
TAG 2 TAG 3 TAG 4
R
Data communications
0-4095 40002
+ 4-20mA
+
TAG 1
40022 40023 40024 1-5vdc
+ -
40021
+
2-WIRE INSTR TT
HMI Database
NETWORK BUFFER
Transmitter converts millivolts into 4-20 mA current.
V
Convert 0-4095 integer value to floating-point engineering unit scaled value (e.g., 0-55 psig)
Convert voltage to a 12-bit binary integer
250-ohm resistor converts 4-20 mA to 1-5 VDC
EXAMPLE TEMPERATURE CURVE TE T/C TYPE K
Thermocouple converts heat into millivolts.
TT TE
mADC mVDC 20
50
UNITS SPAN ZERO
°C 1200 0
NUMERIC RELATIONSHIPS mVDC mADC VDC 50 20 5 0 4 1
INT 4095 0
%EU 100 0
To find equivalent values:
Type K: 0-1200°C equates to about 0-50 mV.
1. Calculate percent of span of known value: 0.3958 (Unitless) 475 °C 1200 °C 4
0 °C 0
2. Use known percent of span to find equivalent values: .3958 x 4095 = 1621 counts. .3958 x 4 VDC = 1.58 VDC. Add 1-VDC offset = 2.58 VDC. .3958 x 16 mA = 6.3 mA. Add 4-mA offset = 10.3 mA.
1200
Figure 4. Data translation process - from field device to HMI The following discussion about unit conversions applies to both circuit types. Focus on the top circuit. A type K thermocouple is the sensing element. Thermocouples are devices that use the principal of bi-metallic contact to generate a small millivolt signal that is virtually linear with a change in temperature. Different combinations of metals are designated by type. Note that the temperature curve presented in the chart is relatively linear throughout the temperature span of interest. Outside of that temperature band, the signal can become less linear, (a characteristic of the thermocouple) but that is of no importance here. Instrument scaling must always begin at the process measurement. The designer consults the heat and material balance (HMB) sheet for our imaginary system and finds that the expected temperature at the measurement point is normally approximately 105°C. The upstream heater is capable of heating the system to approximately 130°C before it shuts down due to its overtemperature interlock. The design engineer knows that a properly calibrated span would place the normal operating point at about the middle of the curve. The upper end would need to be above 130°C. After some thought, the engineer decides on a calibrated span of 15 to 150°C. The thermocouple emits a millivolt signal that is proportional to the process temperature. In this case, the temperature range of interest is between 15 and 150°C. The type K thermocouple provides an output of 0.597 to 6.138 mV over that temperature range1. The temperature transmitter, then, must be bench calibrated to provide a 4–20 mA output signal that is proportional to the 0.597 to 6.138 mV input signal expected from the thermocouple. The transmitter, being a current source (as opposed to a voltage source), varies its power output as necessary to maintain a steady milliamp output that is proportional to the millivolts on its input. (NOTE: A “voltage source”, like a battery, tries to maintain a constant voltage regardless of the load, while a “current source” tries to maintain current regardless of load).
Whitt2003.book Page 57 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 4: SCALING
57
This millivolt signal that is proportional to temperature is detected at the temperature transmitter’s input. The temperature transmitter then converts this signal into a 4–20 mA signal that has been scaled, in this case for a span of 15–150ºC (see Figure 5).
Signal Conversion at the PLC Input E = IR : Volts = Amps x Resistance Zero: E = .004 Amps x 250-ohms = 1 volt at 15 °C Span: E = .020 Amps x 250-ohms = 5 volts at 150 °C
Figure 5. Signal conversion at PLC input The programmable logic controller (PLC) has an analog input module that detects the output of the temperature transmitter. Virtually all analog modules are actually voltmeters, even though they are listed as milliamp inputs. Sometimes the resistor is external on the terminal strip, and sometimes it is internal on the PLC I/O module (see Figure 4 above). In either case, the 4–20 mA signal will be converted to a voltage. Typically, this voltage is 1–5 VDC because the resistor used is typically 250 ohms. The PLC specification lists this particular PLC I/O module as having 12-bit resolution. To find the resolution of the module in terms of the process variable, perform a binary conversion: 212 = 409510. So, for an input span of 1–5 VDC, the PLC I/O module provides an integer value to the PLC program that ranges from 0 to 4095. The PLC program may fetch this data to use as needed. One of the possible actions of the PLC program is to move this data value into a network buffer (a series of contiguous locations in PLC memory) for transmittal upstream to the human-machine interface (HMI). The value (between 0 and 4095) is then encoded for data transmittal across the network. The HMI receives this encoded data stream and uses a communications driver software package to decode the data back into its original 0–4095 value, which is then stored in an input data buffer. The HMI computer has a database called a tag file, which contains instructions about how to manipulate each data item for presentation to the operator. Many of the tags in the tag file are linked to data items in the input data buffer. One such tag is linked to this particular location. The 0–4095 raw value is extracted and converted by use of the formula embedded in either the tag database or the graphic screen that uses the information. The formula in our sample case is shown in Figure 6. The value produced (85.88) would be the value displayed to the operator as Degrees C.
Engineering Unit Calculation at the HMI For a scaled range from 15-150 °C, EU = ((Raw Counts / 4095) x (150-15)) + 15 if Raw Counts = 2150, then EU = 85.88 °C
Figure 6. Engineering unit calculation at the HMI
Whitt2003.book Page 58 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
58
G. Practical Application Billy, an instrument technician at Crazy Al’s RubberWorks, a manufacturing facility, is on his break. He is just sitting down to eat some linguini when he gets a call that solvent flow into a mixing kettle is not reading right, causing the rubber-like material to look like bad oatmeal. He drops his fork and makes his way to the drawing file where he locates the proper drawing and uses it to wipe the noodles off his shirt. Then he goes to the kettle and finds the solvent line and locates the flowmeter. He finds that the differential-pressure flowmeter is calibrated 0–10 inches water column (inwc). After getting approval from operations and confirming that the valve is in manual mode and is closed, Billy disconnects the signal output cable from the transmitter and hooks the cable to a current source (a portable test device) to simulate the transmitter output signal. He then tries to inject a signal into the system. The batteries are dead, so he has to go get more. With new batteries and an ammeter, he measures the signal, which reads 14.2 mA on a 4–20 mA scale. He knows that the resolution of the PLC input module is 12 bits, and the operator wants to read the flow in pounds per hour at a scale of 0–100. • • •
What is the simulated pressure drop across the orifice in inches of water column (inwc)? (Square-root extraction is already accounted for in the transmitter.) What is the decimal integer value in the computer? What should the operator be seeing in pounds per hour?
The solutions follow, but first, try to solve it yourself.
Solution First, Billy adjusts the analog value to account for the live-zero offset: 14.2 – 4.0 = 10.2 mA. He knows that a span of 16 mA equates to 0–10 inwc (i.e., a linear relationship—square-root extraction is being done in the transmitter). Once the relative ranges are known, percent of scale can be used to equate the values: inwc value is (10.2 mA/16 mA) x 10 inwc = 6.375 inwc. Then, Billy decides to check the PLC to make sure it is operating correctly. He knows the PLC has 12-bit analog input resolution, making the valid range of the PLC integer 0 to 4095. He uses a percent-of-scale relationship to determine the proper integer value: (10.2 mA/16 mA) x 4095 counts = 2611 counts. Billy confirms the PLC is reading properly by checking the integer value in PLC memory. He then checks the PLC program to make sure the integer is being moved to the proper memory location so that it can be uploaded to the HMI. He finds that it is being moved to address 40021, which is in a data array that is being placed on the network. The blinking light on the interface module confirms that the network is functioning. So, he reasons, if a problem exists, it must be in the HMI. Billy goes to the control room and views the screen. He calculates the value he expects to see using the percent-of-scale technique: (10.2 mA/16 mA) x 100 lb/h = 63.75 lb/h. The screen is reading 54.2 lb/h. Billy takes the HMI system into development mode and checks the tag file for the configuration of that tag. He finds FT1001 = (13$40021/4095) x 85. He remembers that the flow data array location in the PLC was address 40021, and that the PLC was at network node 13. But, the proper scaling of the displayed value should be 0–100 lb/h, not 0–85. Billy mentions his finding to the operator, who informs him the transmitter, which was broken yesterday, was changed out last shift. Billy changes the 85 to 100, recompiles the HMI program, and relaunches the application. He confirms the displayed value equals the expected 63.75-lb/h value. He reconnects wiring to the transmitter but forgets to turn off the current source, which ensures the batteries will be dead next time, and returns to his linguini.
Whitt2003.book Page 59 Thursday, July 10, 2003 4:05 PM
Chapter 5: Design Practice Industry guidelines are sometimes written, and sometimes not. What does a customer have a right to expect as a given in a design package? Many organizations have written standards in an attempt to define these requirements. These industry standards are rarely implemented in their entirety. Most of the time, the standards are used as a basis, and customers publish exceptions to them in their company standards. There are also practices, which are design approaches commonly understood to be acceptable for a particular industry. One of the more useful standards is National Fire Protection Association (NFPA) 79. This standard defines many of the basic tenets that should be incorporated in a design package. It is well to remember that guidelines issued by the plant always supersede those published by independent bodies such as NFPA, ISA—The Instrumentation, Systems, and Automation Society, or National Electrical Code (NEC). But, if the company standards do not deal specifically with an issue, guidelines published elsewhere should be consulted and followed. This section first describes data management practice—a key part of the design process. It goes on to provide some insight into basic wiring practice, failsafe wiring, hazardous area classifications and their effects on design, and control system wiring.
A. Introduction to Information Management Proper management of large amounts of information has always been a major part of the I&C profession. Handwritten I/O lists, instrument lists, and equipment lists were the order of the day even before the advent of the PC. Many times, these lists were given short shrift, being formalized as an afterthought. The list(s) would be generated from scratch at the end of the project, having been written in pencil in somebody’s notebook throughout. The design manager would obtain a list of information items the client desired for the list, and he would engage a designer to extract that information from an already completed drawing package. The designer would copy the information down and hand it to a data-entry clerk to “pretty up.” In fact, that method is still used all too often. Time spent keying in data is frequently considered “overhead” time. In today’s marketplace, profit margins are small, and the design team must make full use of the tools available to it. Any loyalties that may run from the customer to the service provider are becoming more tenuous as the drive to generate quick profits overrides other considerations. Customers must demonstrate to their investors that any alliances they may have are closely and continuously scrutinized. Even longstanding relationships are no longer sacrosanct if the service provider does not react to new productivity tools as they become available and to market conditions. In other words, basic economic rules apply today more than ever: Designers who can demonstrate that their product has the highest quality at the lowest cost generally wins in the end—no matter what the other considerations may be. Thus, it is important to come to a full understanding of the productivity gains that can be realized by effective management of a “living” database. The importance of a well-designed, well-maintained database to the design process cannot be overstated. The database is the glue that binds the instrument package together. The database should provide a cross-reference into each component of the documentation package and should
Whitt2003.book Page 60 Thursday, July 10, 2003 4:05 PM
60
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
supply information that is difficult to convey in the drawings. It can be used to generate cable schedules and even aid in the production of junction box wiring diagrams. A “living” database, one that is developed along with the design, is indispensable as a tool during the design check because it gives the checking team a means of efficiently managing a comprehensive quality check of all the documents. The database is a deliverable in its own right, but more than that, it can be an effective productivity tool for design, a quality management tool, and an indispensable construction and startup aid. As such, designers should not limit their databases to the information elements being requested by the client or the basic fields that are generated from any of the various “automatic” design tools available today that extract information from the P&IDs to create other documents. Those fields should be merely the starting point. The database can always be pared down later to conform to whatever formats the client desires. The first question we must ask is, “What kind of database program should we use?” There are basically two ways to store data: (1) a spreadsheet, and (2) a database. There are several viable options on the market for each type. What is the difference between a spreadsheet and a database? After all, they both allow data to be stored and retrieved. In very broad terms, a spreadsheet treats each data item independently in its own cell, while a database inextricably links a whole set of data items to a unique record. The difference is subtle, but important, as we will see below. Time spent on the database is generally time well spent, provided the data being entered can be applied to multiple purposes and is easy to retrieve in a useful format. To be effective, a particular data item should only be keyed once, yet be available for many purposes.
1. Spreadsheet Examples of spreadsheet programs are Microsoft® Excel and Lotus® 1-2-3. The greatest benefit of the spreadsheet is its simplicity. It lends itself well to data entry, and what you see is, pretty much, what you get. Data-entry utilities are optimized for entering data cell by cell, giving you plenty of flexibility. Data are immediately available, provided the spreadsheet is well designed for the purpose intended. This aspect is particularly valuable on small projects with only a few elements to manage. However, on larger projects, the spreadsheet quickly becomes cumbersome. Data collected into an I/O list format are difficult to translate into a report organized by equipment. This is especially true if data are split among several “sheets” within the workbook, which would, at first glance, seem a good way to organize the information. The downside is that it guarantees a limited return on the data-entry time investment.
2. Database Examples of database programs are Microsoft®’s Access and Microsoft® Visual Foxpro® and Borland’s® dBase. Compared to the spreadsheet, the database is more restrictive and requires more effort (overhead) to get started. A structure has to be defined, and the data are a bit more difficult to enter. For example, since spreadsheet data are stored by cell, there are handy utilities for entering one cell and then “dragging” the data from that cell to others, thus quickly and easily copying data. A database program has no way to do this other than by an update query or a macro. However, once a data table is created and the data are entered, the data immediately becomes available for a myriad of other uses. Queries can be created to cull particular subsets of the database for editing or viewing. New records can be created from within the queries. Report forms can be created to adapt the data to multiple purposes.
Whitt2003.book Page 61 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
61
In short, the database is a much more powerful tool to use, providing a more secure, better constructed environment for the storage and retrieval of information. But, the database can be a bit unwieldy for those who are unfamiliar with it. Today, database programs are used for most data storage and retrieval operations. Following are a few of the terms: • Database: A medium for data storage and retrieval. Database programs such as Microsoft®’s Access consist of the following elements: • • • •
Tables for storing the data Queries for retrieving specific data or data sets Forms that allow you to optimize data read/write activities Reports that allow you to optimize data presentation.
In short, the database program gives you the ability to quickly enter data or to extract specific information out of the mass of data items in the database. •
•
• •
Table: A two-dimensional array of information consisting of records (rows) and fields (columns). Each record describes a single element in the system, as stored in the fields that are associated with that record. For example, in a drawing database, data relating to a specific drawing are found in that drawing’s record. The drawing’s number is in the DWG NO. field, its title is in the DWG TITLE field, and so on. Record: A collection of data items relating to a single entity such as an instrument or drawing. In the table, data records are organized in rows made up of data fields. Database programs such as Microsoft® Access and Microsoft® Visual Foxpro® inextricably link the data in each record together. This differs from a spreadsheet (e.g., Microsoft® Excel, Lotus®), which does not automatically associate data into records. Field: A column in a data table that defines a specific type of information found in all records. In the drawing list, for example, DWG NO. would be a field in the data table. Query: A preconfigured filter/sort. In the drawing list example, you may generate a query that will list all drawing records that have no date in the ISSUED FOR CONSTRUCTION field.
B. Types of Information So, what types of information must be maintained? First and foremost in importance is—and this may be surprising to many—the drawing list, followed closely by the I/O list and the instrument list. Other lists include the preferred vendors list and the equipment list. This section deals with each of these lists in turn.
1. Document Management—Drawing List Documents are the stock in trade of the engineering firm. They are the only product. As such, engineers should give their documents the same consideration a car manufacturer gives his automobiles. This kind of attention is frequently lacking, however. In the first place, it is easy to dismiss the Drawing List as a mere tabulation of documents. In reality, the Drawing (or “document”) List should reflect the current state of the document package. Thus, it becomes a management tool. A more appropriate name for the Drawing List would be the Document List. Any documents that are to be delivered to the customer should be given a document number and should be listed in this table. This includes specifications, calculations, memos, and sketches.
Whitt2003.book Page 62 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
62
The Drawing List is an extremely important element in the design process. Many times, the drawing ordering process is the engineer’s first contact with his customer. If the engineering provider shows himself to be poorly organized in this area, then it is likely that he will be poorly organized in other areas. The customer may begin to lose confidence in the service provider before the project is fairly started. The Drawing List table should be designed around the drawing control sequence, since formal drawing control procedures probably exist to some degree. The table should have date fields for each step in the design process shown in Figure 7.
Order Prints from the Customer
Identify Drawings for Revision/Creation
Order Drawing Files from the Customer
Review Design
Begin Design
Receive Drawing Files
Issue for Construction
Receive Redlines
Issue Drawing Files for Record to Customer
Figure 7. Typical document handling process The sequence of events as depicted can change slightly depending on the customer, but each step should be logged as it is reached. Date fields with data imply completion of the step, while blank date fields indicate remaining milestones. It is possible, using this process, to develop a quickand-dirty approach for calculating completion percentage by dividing the number of filled dates by the total number of date fields. This approach is crude, but sometimes good enough. Following is a commentary on a typical document-handling cycle for a large capital project:
a.
Order Prints from the Customer A design project typically begins with a tentative drawing list. This list must be developed to derive a project estimate. Drawings identified as “required” during the initial investigation should be listed here. Generally, the investigation is carried out based on prints provided by the customer. Drawings that are ordered as prints should be logged—if for no other reason than to note the fact that the print has been received and is available to the design team for reference.
b. Identify Drawings for Revision/Creation After the prints are in hand, the design team reviews them to see which ones need to be revised as a part of the project. When a drawing is designated as a possible deliverable, it should be so designated in the drawing list.
c.
Order Drawing Files from the Customer After a list of needed drawings has been compiled, a request needs to be sent to the customer for transfer of the files. At this point, the design team is requesting “ownership” of the drawings. Until the drawings or drawing files have been officially received from the customer, they are subject to change by others outside the purview of the project.
Whitt2003.book Page 63 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
63
d. Receive Drawing Files When the drawing files are officially received from the client, the event should be logged. Thus, the design team will always be able to see which drawings have been ordered and are in the pipeline and which are available to be worked.
e.
Design Process When a drawing is completed and checked, that event should be logged in the database. Other intermediate milestones can be logged as well if desired. This is a project management tool for determining project status.
f.
Issue for Construction The issue for construction is a key milestone that signifies the end of the design phase and the beginning of the construction phase. This does not, however, imply that drawing revision activities are over. Sometimes a drawing might be issued several times during the construction process. Each time the drawing is reactivated for design, the issued for construction date should be erased from the database to indicate the drawing is back in the design arena. Each of the field copies should be located and destroyed or redlined with a “Hold” to indicate the area under revision. When the redesign is completed, then the drawing review process should be followed prior to the drawings being reissued.
g.
Receive Construction Redlines Construction is sometimes empowered to make modifications “on-the-fly.” For example, a common on-the-fly change is that of color designations. Many times, the designer will assume that a certain cable with a particular color code will be purchased. However, the purchasing agent may find a “deal” on another cable of a different color that is equal in all other respects. The constructor will then mark up the print to show the correct color combinations. Redline drawings of this type are called as-built drawings, since the changes are required to bring the drawings up to the as-built conditions. Incidentally, in the standard color code for as-built markups, green means “deleted” and red means “added.” Other colors are for information only.
h. Issue for Record The final step in the life of a drawing revision is the issue for record step. At this point, all drawings need to be scanned to make sure they comply with the customer’s standards for both design content and file structure. Most engineering facilities have design guidelines that may not be enforced until it is time to submit the drawing to the customer for inclusion in the drawing control system. The design team should contact the customer well in advance to make sure there are no surprises at this juncture.
2. Device Management Managing the information relating to instruments can become a daunting challenge. Following is some important information that should be captured during the design process: • • • •
Specification: manufacturer, model number, range, etc. Relationship to the controls computer: I/O type (even if “NA”), physical address, software address, software tagnames, etc. Documents: P&ID drawing number, wiring diagram number, etc. Process: physical location, process function, etc.
Whitt2003.book Page 64 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
64
Database activity follows a predictable pattern as shown in Figure 8.
P&ID Takeoff
I/O Configuration
Documentation Cross-Reference
Design Check
Physical Cross-Reference
Specifications
Checkout Checklists
Commissioning
Project Closeout
Figure 8. Typical instrumentation database management cycle
•
•
• • • • • • •
P&ID takeoff. There is a pulse of database activity at the beginning of a project as the initial data are collected from the P&ID set. This is called the P&ID takeoff. The initial “takeoff” occurs as the P&ID drawing set nears completion. I/O configuration. The first thing that usually happens after the initiation step is the computer addressing of the I/O devices. As computerized equipment is identified, each item is given hardware and software addresses that provide a vector into the control system. This process is called “partitioning”. Documentation cross-reference. As the design progresses, each item finds its way into a drawing or set of drawings. Specifications. Instrument specification numbers and purchasing numbers appear in these fields. Physical cross-reference. Physical drawings such as installation details are listed in order to develop materials lists. Design check. A checklist is generated to guide the execution of a design check. Checkout checklist. A checklist may be generated to help guide the construction effort. Commissioning checklist. A checklist may be generated to help guide the commissioning effort. Project closeout. A checklist may be generated to help guide the closeout effort.
As indicated by this broad range of activities, there will be database activity throughout the life of the project. If properly managed, the database should capture information as it is being generated. It is much more difficult to capture data after the fact. Therefore, all members of the design team should have the database active in their workspace at all times, standing by to log their activities. Following are some of the lists that are typical of a design project: •
I/O List: The I/O list ties the field instrument to the control system’s I/O interface. The instrument’s tagname, description, I/O type, and computer address are the minimum data for this list. Other helpful information includes the control schematic or elementary diagram drawing number, a P&ID number, and any other associated drawings. Note: If using
Whitt2003.book Page 65 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
•
•
•
65
a database, the I/O list and the instrument list (discussed in the following section) may be combined. Instrument List: The instrument list, as the name implies, is a list of all the instruments to be purchased, rewired, recalibrated, or otherwise handled as part of the project. Since most instrument signals are fed to a computer system, the instrument list and the I/O list may be combined into a single database to reduce data-entry overlap. Preferred Vendors List: The preferred vendors list is a compendium of instruments, computer equipment, and other items that have been preapproved for use at the site. This list is typically generated by the owner and is usually available upon request. Sometimes the list will also include a section for “black-listed” items, which are items to be absolutely avoided. Equipment List: The equipment list provides detail on all the major equipment items that are associated with the project. Pumps being renovated, motors being rewound, and vessels being purchased are examples of items that would appear in this list.
It is advisable to combine these lists into a single database to reduce the amount of data entry. For example, information required for the instrument list (e.g., instrument tagname) is also needed for the I/O list. Use of a database allows the different lists to be easily generated from a single (or even multiple in the case of a relational-type database) data table. Most databases may be set to allow multi-user activity, and so may sit on the network, available for use by the entire design team. See Part III for an example of a relational database approach.
C. Basic Wiring Practice Generating a document that properly depicts interconnection wiring is something of an art form. There are two basic types of wiring diagram: the inter-cabinet wiring diagram and the intra-cabinet wiring diagram. The former is relatively simple to produce, while the latter is not. One of the best guidelines for this topic is the NFPA 79 standard. While this section deals with more than is contained in the standard, nothing in it conflicts with the standard. To understand some of the concepts, a basic understanding of the terminology is important. Relay circuits, in particular, are becoming anachronistic. They are still used, however, and some of the terminology that evolved during that era is still pertinent in today’s computerized environment. Therefore, this section begins with a review of switching components and related terminology.
1. Definition of Key Terms •
•
•
•
Bit: A binary element that can have the value of either “1” or “0” usually associated with computer programming. A “bit” can be used as a “flag” to denote status, or as a PLC signal to energize a relay or solenoid. There are eight bits in a “byte”, and either 16 or 32 bits in a “word”. Coil: An inductor. Relay coils initiate the switching action. They consist of an electromagnet and a ferrous plate to which contacts are mated. As current passes through the coil, the plate is drawn upward which pull the contact wiper to a new position. Contacts: The part of a switch or relay that alternately close to pass electrical current and open to stop its flow. A “set” of contacts consists of one “common” and either one normally open contact or, more typically, one normally open and one normally closed. The latter configuration is sometimes referred to as “form-C” configuration. DPDT (double-pole, double-throw): Switching terminology that implies a switch or relay with two form-c contact sets.
Whitt2003.book Page 66 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
66
•
•
•
•
Dry Contacts: This term implies an isolated, unpowered contact closure. Some equipment transmits signals using their own internal power. This forces the receiving equipment to provide isolation. Other equipment transmits signals via “dry” (i.e., isolated from any power source) contacts. This allows the receiving equipment to pass its own power through the contacts thus eliminating the need for additional isolation. The term dry contact relates to electro-mechanical relay contacts, not solid-state relays. Edge-Triggered: A circuit is said to be “edge-triggered” if its action depends on the change of state of something (i.e., a “transition”) rather than a steady state. A circuit that responds when its input transitions from low to high is said to be “leading-edge” triggered. A circuit that responds when its input transition from high to low is said to be “trailing-edge” triggered. Flags: A generally accepted programming term to describe a binary bit that is used to communicate status. By monitoring a “flag”, you can learn something about the program or system. Flags are “raised and lowered” as opposed to bits, which are “set and cleared”. Form-A: A generally accepted term to describe a set of contacts with a common (COM) terminal switched to a normally open (N.O.) contact. This is classified as a “single-pole, single-throw” (SPST) configuration.
N.O. COM
COM
N.O.
Figure 9. Form-A contact set (SPST)
Figure 9. Form-A contact set (SPST)
•
Form-B: A generally accepted term to describe a set of contacts with a common (COM) terminal switched to a normally closed (N.C.) contact. This is classified as a “single-pole, single-throw” (SPST) configuration.
COM N.C.
COM
N.C.
Figure 10. Form-B contact set (SPST)
Figure 10. Form-B contact set (SPST)
•
•
Form-C: A generally accepted term to describe a set of contacts with a common (COM) terminal switched to two destination terminals – one Normally Open (N.O.) and one Normally Closed (N.C.). This is classified as a “single-pole, double-throw” (SPDT) configuration. Ice-Cube Relay: This term alludes to the physical appearance of a class of low-cost relays used in most low-current (<10-amp) logic applications. An ice-cube relay is one that is enclosed in a clear plastic cube. The contacts are usually rated for 10-amps, and come in
Whitt2003.book Page 67 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
67
N.O. N.O. COM
COM N.C. N.C.
Figure 11. Form-C contact set (SPDT)
Figure 11. Form-C contact set (SPDT)
•
• • • •
•
•
•
either a DPDT or 3PDT configuration. These relays require a separate plug-in base, which provides termination screws for connecting external wiring. Interposing Relay: A term describing the function of a relay when its only purpose is to convert one signal source type into another. If a digital signal is available as a 110-VAC form, but can only be read if it is 24 VDC, then an interposing relay is used. The coil of this example relay would be operated by the 110-VAC signal, and its contacts would switch 24 VDC. Normally Closed: The set of contacts on a switch or relay that make electrical contact when in the shelf state (i.e., “un-activated”). Normally Open: The set of contacts on a switch or relay that do not make electrical contact when in the shelf state. Poles: See “Switch”. Propagation Delay: In terms of a device, it is the time it takes the device to respond to a change in its commanded state. In terms of a system, it is the total delay that results when a signal must “propagate”, or “ripple” through a series of events. A relay’s propagation delay is the time it takes to switch its contacts from one position to the next. This time is less when energizing than when de-energizing due to the residual magnetism that must be overcome to de-energize. Race Condition: A situation that occurs when two devices “race” to see which one will act first. When a race condition is present, the system is sometimes said to be “metastable”, having more than one stable state for a given condition. The result could be a system that “chatters”, or a system whose actions are not repeatable. Relay: An electro-mechanical device made up of a coil wound around an iron core to form an electro-magnet, and up to several sets of contacts (poles). A flapper plate (not shown) is mechanically linked to from one to several mechanical arms. When the coil is de-energized, the spring-loaded arms pull the plate away from the coil. This is called the relay’s “shelf state”, allowing signal current to pass from the “common” terminal through the springarm to the normally-closed terminal. The magnet, when energized, attracts the flapper plate that causes the conducting arms move up likewise, thus placing them in their “energized state”. Current then flows from the “common” terminal to the “normally-open” terminal. Relay, Timing: Logic circuits frequently require some form of a timing function. This timing is achieved by the use of relays that have some onboard intelligence. An input signal is monitored to start the timing function. Once a trigger is detected, one of several actions can result based on the type of timer. Most timers today can be configured to provide any of the timing functions. A timer can delay its response to the arrival of the trigger signal (see “Timer, On-Delay”), delay its response to loss of the trigger signal (see “Timer, OffDelay”), or respond to the trigger being present for a preset duration (see “Timer, Inter-
Whitt2003.book Page 68 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
68
L1
L2 N.O. COM N.C. N.O. COM N.C.
Figure 12. 2-Pole relay (shown in shelf-state)
Figure 12. 2-Pole relay (shown in shelf-state)
• •
•
•
val”). Most timing relays are manually adjustable (knob or pot) with several specified ranges from which to choose. Contact configurations vary. Ride-Thru Timer: See “Timer, Ride-Thru”. Shelf State: The state of a device as it would be if it were on the shelf (i.e., unwired). A relay’s shelf state would be de-energized, with its normally closed contacts closed and ready to pass current. Solid-State Relay: An electronic device made up of an opto-isolated transistor or, for higher current applications, an SCR. There is generally a single output, which causes this device to operate as a Single-Pole, Single-Throw (SPST) relay. One advantage is its small size and low power consumption. A disadvantage is the fact that a solid-state relay always passes current, even when in the off state. This off-state “leakage” current is sometimes high enough to prevent a load from dropping out when moving from the “on” state to the “off” state. Sometimes a shunt resistor is needed to reduce the amount of current forced through the load. Switch: A mechanical device made up of a lever or pushbutton and its associated sets of contacts. There can be any number of contact sets, which are referred to as “poles”. Each “pole” can be configured to switch from a common terminal to either one or multiple destination terminals. The terminology that describes this action is in the form of “DPDT” (double-pole, double-throw). This implies two sets of “form-C” contacts. “DP4T” implies a four-position rotary switch with two poles. There are two basic types of switch:
Type 1: ROTARY Switches can be multi-pole, multi-throw HAND
OFF
Type 2: PUSHBUTTON switches can be momentary or maintained START
AUTO MOTOR STARTER
PWR
M
RTN
PWR
M
PLC D.O. D.P.3.T. rotary switch shown in "off" position
MOTOR STARTER
STOP
M Momentary stop/start pushbuttons
Figure 13. Common types of switches
RTN
Whitt2003.book Page 69 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
•
69
Switching Action: • Make-Before-Break: A type of switch contact that does not interrupt current flow when being switched from one position to another.
N.O. COM N.C.
Figure 14. Make-before-break
Figure 14. Make-before-break
•
Break-Before-Make: A type of switch contact that does interrupt current flow when being switched from one position to another.
N.O. COM N.C.
Figure 15. Break-before-make
Figure 15. Break-before-make
•
Timer, Interval: An Interval Timer is powered at all times, allowing it to continually monitor a signal input. If the input goes from low-to-high (true), the timer is activated causing its output contacts to change state. The timer’s output remains activated for a calibrated interval. After that interval, the timer’s output is de-activated regardless of the state of the input signal. Only when the input signal is off and the timing interval is past does the timer arm itself again, waiting for another low-to-high transition on its input.
INPUT SIGNAL OUTPUT SIGNAL t Figure 16. Interval timer timing diagram
Figure 16. Interval timer timing diagram
•
Timer, Off-Delay, Or Time Delay on De-Energize (TDOD) Relay: A timing relay that energizes when a signal is applied and remains active after the signal is removed. Since the TDOD timer’s electronics must be powered at all times, this relay coil requires at least three wires. Figure 17 shows the timing diagram of a typical TDOD Relay.
Whitt2003.book Page 70 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
70
INPUT SIGNAL OUTPUT SIGNAL t Figure 17. T.D.O.D. timer timing diagram
Figure 17. T.D.O.D. timer timing diagram •
Timer, On-Delay, Or Time Delay on Energize (TDOE) Relay: A timing relay that begins timing when a signal is applied and energizes only if the signal remains present throughout the timing period and beyond. This relay immediately de-energizes after the signal is removed. Since the TDOE timer’s electronics is only active (timing) when the signal is present, a third wire such as that used on the TDOD relay is not required. If a power terminal is provided separate from the signal terminal, a jumper can be used at the relay to eliminate the third wire as shown in Figure 18.
INPUT SIGNAL OUTPUT SIGNAL t Figure 18. T.D.O.E. timer timing diagram H1
Figure 18. T.D.O.E. timer timing diagram
•
Timer, Ride-Thru: A Timing Relay that is used to “mask”, or cover up a condition for a period of time. This type of relay is most commonly used when starting up a pump that has low discharge pressure as a shutdown interlock, though the term applies in all other similar situations. In the pump example, if the pump is running, its discharge pressure should be above a certain amount, otherwise, a leak can be assumed downstream, and the pump should be shut down. When starting that pump, however, the pressure will always be low, preventing it from running. Therefore, a Ride-Thru Timer is used to mask the low pressure long enough for the pump to get up to speed and the pressure to rise.
2. Wire Numbering Each wire in the installation should have a unique designation. Either a wire numbering or a wire color-coding scheme should be used to identify each wire. Wire numbering is more prevalent than designing by color, primarily because there is no guarantee that the cable type being used in the design will be the cable type actually available during construction. This can cause severe upsets in the field.
3. Numbering Methods So, what is a good wire numbering scheme? Numbering schemes can vary widely and still be effective. The only truly important things are that the wire number be unique and that the scheme be
Whitt2003.book Page 71 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
71
consistent throughout the design package. There is some added value if the wire number conveys some useful bit of information such as an encoded drawing number reference or other vector. One method, if the drawing package is in a loop sheet format, is to use the loop or instrument number as the wire number prefix. Then, simply add a sequential suffix to each wire. If the loop number happens to be embedded in the drawing number, then the field electrician is able to quickly ascertain the proper drawing to pull when troubleshooting. Another method, if the drawing package is in a “ladder” elementary or schematic format, is to use some element of the schematic drawing number and add two digits to it. For example, if the drawing number is 4296-1, then a good wire number range might be 4296-1-XX where XX is a number between 00 and 99. Ladder elementaries typically have such numbers listed in columns outside the wiring area of the drawing (see Figure 19).
Line Number Format: XXXYY where XXX is the sequential part of the drawing no, and YY is a number between 0 and 99 unique to that drawing.
52202
N1
H1
52203
2A
52204
52205FU
52205
2A
52203CR
52205CR
52203FU 52203A
52205CR
ZSC-10 52205B
52205A
DESCRIPTION 05422 (refdwg#)
52203B
DESCRIPTION 03
52205ZSC P&ID Device Tag: Wire Numbers: Any device shown on Same as line numbers P&ID has one. except with an alpha suffix. The number or suffix MUST change when a device other than a feedthru terminal is crossed.
"Elementary" Device Tag: Any device shown on elementary has one, but it's shown only for cross-referencing purposes.
Contact Reference Rules: 1) Use line number alone if the destination line is in the same process area. 2) Add the drawing number to the reference if the destination is in a different building, or if it's needed for clarification. 3) Underline the reference if a normally closed contact is used.
Figure 19. Sample ladder elementary format
In this ladder scheme, wires that are drawn near a particular ladder number assume that numbering sequence. As devices are crossed and numbers change, a letter suffix may be added to make that number unique. If the circuit crosses a boundary between two ladder numbers, the wire number sequence assumes the new number and begins again with the “A” suffix.
4. Handling the Numbers When must a number be changed? A wire number must be changed only when it crosses a device of some sort. Fuses, relays, resistors, and switches are some examples of devices. Feed-through terminals are not considered devices because they do not change the characteristics of the signal. When must a number not be changed? A number must not be changed when exiting a node. An electrical node is typically represented by a black dot. Two electrical lines crossing do not necessarily imply that they are the same wire unless a black dot is present at their junction. In such cases, wires leaving a node will have the same wire numbers as those entering the node. Exceptions to this rule are generally noted on the drawings. A dot on a drawing, however, may or may not imply a feed-through terminal, but in either case, the number should not change.
Whitt2003.book Page 72 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
72
What is a good method to employ when changing the wire numbers? Sometimes designers use the left-to-right method. In this method, letter suffixes change as the circuit moves from left to right across the page. This is a reasonable approach, but is somewhat limited. A better method is to increase the letter suffixes in the order of current flow. In some cases, the designer might find that the information presents better with current flowing from right to left across part of the drawing. It is good practice to increase the letter suffixes in order of current flow rather than the circuit’s left-toright position on the drawing page. This gets the designer thinking more in tune with the circuit and might be of some use in troubleshooting. This method also translates well to the loop sheet format in which the circuit is shown with adjacent source and return wires (out-and-back rather than left-toright). Examples of the various styles of presentation are provided later.
5. Inter-cabinet Wiring Managing information about cabling from cabinet to cabinet or from device to cabinet is very important to the constructor. It is also important to maintain this information as a permanent record in case of fire or other catastrophe for the purpose of disaster recovery. Since this type of information presents well in a tabular format, a series of tables, called schedules, has evolved. The schedules are most meaningful when accompanied by another tool called a location plan drawing. Following is a brief discussion of each of these tools:
a.
Cable Schedule Point-to-point wiring information is provided in a chart called a cable schedule. Each cable is a line item in this list and is given a unique identifier. Source and destination locations are specified (preferably in a cabinet/terminal strip/terminal number format), along with the more salient aspects of the cable specification such as conductor size and quantity, voltage ratings, and jacket type. Routing information is also provided in which each conduit and/ or cable tray used is listed. Figure 20 depicts a cable (Cable W1) that is routed between a control panel (CP1) and a junction box (JB2). The cable passes through conduit to a cable tray system. It then transits back to conduit, and on to JB2.
Conduit C2a
Conduit C2
Cable W1 Tray T1 JB2
CP1
Tray T2
Conduit C1 Destination
Source
Figure 20. Defining the cable route (wire W1, Route C1/T1/T2/C2/C2a)
Whitt2003.book Page 73 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
73
Figure 21 shows a record in the cable schedule for cable W1 shown in Figure 20. Drawing numbers are omitted here, but should be provided on both the source and destination. Note that the routing code (C1/T1/T2/C2/C2a) includes the entire path of the cable through each conduit and tray leg.
CABLE SCHEDULE Cable Type AWG OD Number W1 19/cond 14 .531" W2 3/cond 12 .12"
Source
Destina.
CP-1 CP-1
JB-2 JB-4
Est. Len (ft) C1/T1/T2/C2/C2a 50 Route
Purpose 120VAC Signals
Figure 21. Sample cable schedule
b. Conduit and Tray Schedule The conduit and tray schedule is a chart that lists each conduit section and provides a cross-reference to the cable schedule by listing each cable that it contains. The results of the fill calculation should be listed here, along with any associated drawing numbers. Physical location could also be added to this schedule. Figure 22 shows two of the conduits in Figure 20. Conduit C2 contains three cables at a 25% fill, while conduit C2a contains only a single cable (W1).
CONDUIT SCHEDULE Conduit Size (in) Type Number C2 2 GS C2a 1.5 GS C3
Len (ft) 8 4
Source
Destina.
Tray T2 Cond C2a Cond C2 JB-2
Contents W1/W5/W8 W1
Fill (%) 25 40
Figure 22. Sample conduit schedule
c.
Location Plans Cable and conduit routing information is typically provided in a drawing as well as a schedule. In some cases, if properly designed, the drawing can incorporate enough information to make the separate schedules unnecessary (see the example in Part III). It should be noted that these drawings are rarely intended to be perfectly accurate. Rather, they are usually diagrammatic, providing a reasonable approach to routing the conduit. The construction team will sometimes find better paths to follow, but it should be possible for them to at least group the cables as shown. Whatever the format, these drawings are typically called location plans or conduit arrangements. At a minimum, these drawings provide a physical view of an area from the standpoint of the cable and conduit and raceways. These drawings, first and foremost, show the location of equipment. Next, they depict the conduit connections to these devices and possible routing paths. It is possible to make the conduit numbers meaningful by embedding the plan drawing number into the routing number. In the drawing format dis-
Whitt2003.book Page 74 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
74
cussed here, a cable that transits from a field junction box on one drawing to a marshalling panel on another has its routing numbers assigned “outside-in.” That is, from the field device to the junction box to the marshalling panel. In Figure 23, the process area instrument plan drawing depicts the top view of a vessel with various instrument items depicted as numbered boxes. Conduit fittings are shown as circled letters. A component schedule is used to provide detail about each instrument. Conduit routings are depicted graphically, with additional detail available in the component schedule.
Tank and Pump Instrument Locations AC CKTS
PUMP-1
4
JB1
T
T
T
1
L
TK-10 3
T
2
T
T
T
5
T
6
T
COMPONENT SCHEDULE STA#
TAG#
DESCRIPTION LO LEVEL SW
ELEVA. 6'-0"
CABLE
1
LSL-47
4/C US #14
2
PT-48
PRESS XMTR
4'-0"
TWPR OS #18
3
PCV-48
CTRL VALVE
8'-0"
TWPR OS #18
4
HS-15B
HOA HANDSW
4'-0"
4/C US #14
4
ST-15
SPEED XMTR
4'-0"
TWPR OS #18
4
TT-15
BRG TEMP RTD
3'-0"
TWPR OS #18
5
LT-10
LEVEL XMTR
15'-0"
TWPR OS #18
5
LSH-10
OIL PRESS XMTR
15'-0"
TWPR OS #18
6
HV-10
FILL VALVE
18'-0"
2/C US #14
6
ZSC-10
CLOSED LIMIT SW 18'-0"
2/C US #14
NOTES: 1) Numbered boxes depict instruments or groups of instruments. Conduit bodies are represented by the "circle" symbol with the body type letter designator.
TO DC JBOX (Shown Elsewhere)
Figure 23. Typical instrument arrangement
Each process area plan drawing should have associated cable and conduit schedules that provide detailed information about each conduit routing that originates from that drawing. These schedules may be shown on the drawing itself, or they may be separate documents such as those previously described. In either case, information presented includes routing number, contents of the routing (i.e., number of cables and types), size of the conduit, destination cabinet, and destination plan drawing.
6. Intra-cabinet Wiring Once the cables have been delivered to the cabinet, the designer must terminate them. As discussed earlier, the cable schedule provides some termination information in the form of a chart. But this chart format does not translate well to inside-the-cabinet wiring tasks. This is point-to-point wiring that is frequently done using single-conductor hookup wire. This wiring can be extremely time-consuming for the constructor and difficult to check without applying power and seeing what sparks (i.e., the infamous “smoke test”). A different approach altogether must be employed for this case— the wiring or interconnection diagram. The wiring diagram presents wiring interconnection information in a graphic format that is very useful to the installer. Its usefulness diminishes after construction, so it is sometimes considered to be merely a construction document. As such, this drawing is typically not very well maintained after startup. This makes them a favorite target for elimination for those trying to reduce engineering cost.
Whitt2003.book Page 75 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
75
So, given the cost, are wiring diagrams even necessary if wiring information is sufficiently detailed on the loop sheet or ladder elementary? In most cases, the answer is yes. Installers forced to work solely from the loop sheet, unless it is a very simple installation, must gather many sheets to perform this task. They most likely will cull information from these sheets into a sketch that can be used as a reference during termination. This makes the task much more difficult, fosters mistakes, and probably requires more construction supervision than would otherwise be the case. Negative effects can be noted at startup. The office environment, with the availability of database tools and other aids, is the best environment for packaging this information. In any case, the designer should remember that the ultimate purpose of the drawing is to communicate wiring information to an installer, and possibly to a maintenance technician downstream. Selecting a format that makes the design process simpler might not translate very well to the field. For example, it is possible to generate wiring information using a “coordinate” system. Each wired device terminal has the drawing coordinate of the other end of the wire. The installer must interpret the coordinate to terminate the wire. This method is somewhat easier to draw, but is not very userfriendly.
a.
Generating a Wiring Diagram The most effective approach for laying out the wiring diagram is to start from a physical cabinet mounting arrangement that shows the location of each terminal strip, switch, relay, transmitter, and so on, mounted on it. The devices should be depicted as if viewed from the back of the panel from the point of view of the installer. Each device should be depicted with each terminal shown in a reasonable facsimile of the actual arrangement. Refer to Part III for some practical examples.
b. Depicting Terminations Wiring activities comprise a high percentage of the electrical portion of the construction project. Figure 24 depicts a typical cabling scheme that collects/distributes signals to/from the field devices. A field junction box (FJB) is used to concentrate the signals into multiconductor “homerun” cables. The Homerun cables then terminate in a remote cabinet where the signals are “marshaled”, or reorganized, as necessary to efficiently terminate at the I/O interface of the DCS or PLC system. “Homerun” cables serve multiple end devices. They generally consist of multi-conductor or multi-pair cables that must have their jackets removed (i.e., “stripped”) to get at the individual conductors within. It is desirable to reduce the amount of stripping an installer must do; thus, it is convenient to mass-terminate these cables on terminal strips in the FJB, then distribute the signals to the field devices using individual field cables.
HOMERUN CABLES
DATA COMM CABLES
FIELD JBOX
FIELD DEVICES
FIELD CABLES
MARSHALLING CABINET
I/O EXTENSION CABLES PROCESS AREA TERMINATION ROOM
DCS or PLC
COMPUTER ROOM
Figure 24. Typical cabling scheme
WS
CONTROL ROOM
Whitt2003.book Page 76 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
76
Figure 25 shows a sixteen-conductor homerun cable (Cable A2) landing on such a terminal strip. The wire I.D. label is noted only once because I.D. label designations do not change when passing through a feed-through terminal strip such as TS-1. Wire I.D. labels change only after passing through a device such as a fuse or a relay.
1-16/c#16, 1"c to TC-2, SCH-001 6-1/c#14, 3/4"c to MCC1, DWG MCC-001
A1 A2
15-1/c#14, 3/4"c to TC-2, SCH-001 TO OTHER DEVICES...
JB-TK10-01 TS-1
A4 [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [1] [2] [3] [4] [5] [6]
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
TC2-DC1
HS-TK10-15B-2
ZSC13 M10-N1
TC2-DC1 YS-TK10-15A TC2-DC1 YS-TK10-15B
1 2
SW-10 SWITCH
A2
TC2-5H LSLL47
2 3
A3
4
5
1 IPP6-N1
IPP6-N1
3
CR-4 RELAY
4
6 7
LSLL47
8
HV-TK10-13 IPP6-N1 HS-TK10-15B-2 M10-N1 TS2-1H IPP6-N1
LEGEND: [X] : Conductor Number XX : Wire Number A4
Routing Number
IPP6-N1 A2 A3 A3 B2 B3
Figure 25. Interconnection wiring example
It is usually desirable to fully terminate the homerun cables on consecutive terminals. It is likely that the signals being collected in any specific FJB will ultimately be routed to a common marshalling point, so any spare conductors will likely be put to use later. This is the first step in building a wiring diagram. At each terminal shown on the drawing, whether strip terminal or device terminal, the wire ID (i.e., the wire number) should be noted. It only needs to be noted once, either entering or leaving the terminal, since the number is common to all wires connected to the terminal. The wire should then be drawn to its destination terminal where the wire ID is repeated. Such wires may be “bundled” (see Figure 25) if convenient to simplify the drawing. If multi-conductor cables are used, such as the cable in routing A2, then conductor numbers or colors may be noted. These conductor numbers will need to be differentiated from the wire numbers by the use of brackets or some other visual device.
D. Failsafe Wiring Practice To enter a discussion of the merits of failsafe wiring, we need to come to an understanding of some of the basics terms. The term shelf state refers to the state of a device as it would be if it were on the shelf (i.e., unwired). A relay’s shelf state would be de-energized, with its normally closed contacts in the closed position, ready to pass power if connected to a source. The term normal operating conditions refers to the state of a device when the system is running normally. For example, if a tank has a float switch it uses to detect a low level and if the tank is nor-
Whitt2003.book Page 77 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
77
mally half full, then its low-level switch’s “normally open” contacts will be closed under normal operating conditions. Failsafe wiring refers to a design practice that defines the failure mode of a device or system. The term failsafe implies fault-tolerant, as opposed to fault-free, operation. In other words, a device or system is allowed to fail, but to a known “safe” state. A failsafe device is one that is wired to generate an alarm if power flow is interrupted to an alarm detection device such as a relay to drive a horn or a green “system OK” light. Figure 26 depicts a motor control circuit in which a hand-off-auto (HOA) switch can either enable a PLC output (if in Auto), or directly energize the motor (if in Hand). In either case, however, a level switch and a speed switch must be in safe conditions to allow the motor to run.
LSL
SSL
O H
POWER
J (N t 2)
(N t 2)
INTERLOCKS
A
J
M
RETURN
J PLC
Figure 26. Failsafe interlock chain (devices shown in shelf state)
Critical safety circuits should always be energized, for example, under normal operating conditions. If current flow stops for any reason, an alarm is generated. Normal operating conditions should not be confused with the terms normally open or normally closed. Normal operating conditions are those that are in effect with the equipment running normally. Turning the equipment off or having any component in the system fail should cause a loss of voltage at the annunciator, causing the alarm to be generated. Note that such an alarm does not necessarily imply an alarm condition exists in the process (e.g., tank level too high), but that either the alarm condition exists or the alarm condition is no longer being monitored. Whenever possible, failsafe wiring practice should be employed on feedback signals (digital inputs), non-mission-critical control relays, and annunciator systems. This gives the plant operators knowledge that the sensing or alarming system is in fact monitoring the process and standing ready to inform them of upset conditions. Judgment needs to be exercised, however. On some control circuits that are mission-critical, it might be better to let the circuit fail unnoticed than to bring down the plant. But, the default should be to make all circuits failsafe. This causes an increase in power consumption because the load is always energized. But, the personnel and process safety considerations usually outweigh the relatively minor economic ones. Following are some rules of thumb for failsafe wiring practice: •
•
If the sensing device is a “dumb” (i.e., direct-acting) switch (like a float switch) employed as a “high” process alarm (e.g., high temperature, high level), then its normally closed contacts should be used to support failsafe operation. Why? The switch will not change from its shelf state until it detects an alarm condition. So, it needs to pass power when in its shelf state and when the process is in its normal state. If the sensing device is a “dumb” switch employed as a “low” process alarm (e.g., low temperature, low level), then its normally open contacts should be used to support failsafe operation. Why? The switch will change from its shelf state as soon as the process variable
Whitt2003.book Page 78 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
78
•
(e.g., temperature, level) reaches its normal operating condition. If the process variable falls below the alarm point, the device will return to its shelf state. If the sensing device is electronic, its normally open contacts will generally support failsafe operation because it will probably be configurable. Most sensing devices today are electronic, and most of them provide a user-configurable setting that allows the device to be configured for failsafe operation. Whenever possible, the normally open contact should be made to close during normal operating conditions. Sometimes it is wise to place a note on the loop sheet to that effect to remind the installer of the need to make that field adjustment.
E. Hazardous Area Classification and Effects on Design Those who work in industry, particularly certain sectors of industry, will invariably work in hazardous areas at some point in their career. It is important to realize that processes have been developed, through trial and error in many cases, that bring the risk to personnel and equipment to within acceptable limits. No system or process can guarantee a risk-free environment when working with volatile fluids, dusts, or gases. But, if the guidelines are followed as published by the NFPA and other agencies, the risk is minimized.
1. Hazardous Locations What exactly constitutes a hazard, and what can be done to render an area safe for electronic components? A thorough description of the National Electric Code (NEC)2 can be found in Chapter 5 of the NEC 2002 Handbook, articles 500 through 517. These articles classify the various hazardous environments one might encounter in the industrial process area and stipulate the equipment and practices that must be used to avoid unsafe installation. The designer must have a thorough understanding of these requirements if the area is classified as anything other than “General Purpose.” The plant owner should be able to provide area classification information. Or, in the case of new construction, the contracting project manager or process engineer would have access to that information. Due to the complexities of the subject, this book makes no attempt to be comprehensive in its approach. Rather, it explores some of the key real-world issues surrounding safety considerations for design. Safety issues are certainly a primary concern when designing control systems or subsystems that will be immersed in volatile atmospheres (NEC Class 1, Division 13) or that might be exposed to such atmospheres on a periodic basis (NEC Class 1, Division 24). Such designs must take into account not only normal operating conditions but also abnormal events that could occur. Regulatory agencies such as the Occupational Safety and Health Administration (OSHA) react to catastrophic events by promulgating regulations that are intended to limit the chances of a repeat event. The design team should carefully observe these regulations during the design process. The NEC defines and classifies the hazard boundaries that are in place in the process area5. The NEC also makes suggestions for applying remedies, or at least provides acceptable options. Insurance carriers such as Factory Mutual (FM) factor the myriad of regulations and interpret the NEC to assist in selecting the right remedy on a case-by-case basis. If a brand new design issue arises at a site, it is a good idea to discuss the issue with the insurance carrier before finalizing the design. Insurance carriers are in excellent resources as they have a vested interest in both maintaining a safe
Whitt2003.book Page 79 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
79
plant (to reduce their risk) and in the client’s being able to make a reasonable profit (to maintain their contract). As a result, their opinion is often both workable and affordable. The NEC rating system is broken into three sections: class, division, and group. For example a typical hazardous area may be described as a “Class I, Division 2, Group D” area. In this method of classification, class refers to the type of hazardous area (e.g., gas vapors, fibers), division refers to the likelihood of the area being hazardous at any given moment, and group refers to the volatility of the material that is likely to be in the area. The areas are classified in terms of the likelihood of hazardous conditions being present. For example, most volatile gases are heavier than air. Such a gas, if released, will collect in the lowest area. Therefore, any trench or ditch transiting from the containment area would also be classified as a hazardous zone (see Figure 27).
General Purpose Area High Risk Area Lower Risk Area
High Risk Boundary
Emission Source
Trench
Figure 27. Hazardous boundaries
Figure 27 depicts a fairly typical situation in which a vessel and its support equipment, such as a valve and transfer pipe, are considered emission sources. One or more hazardous area envelopes surround this equipment, the dimensions of which depend on the degree of hazard and the likelihood of a release. The hazardous area classification usually decreases with greater distance. Any electrical equipment mounted within this boundary needs to be specially modified to eliminate the risk of ignition. Vapor seals are required for conduits that cross from one level of hazard into another in order to prevent transmission of the hazardous gas or dust to a remote location. Following is a summary of the hazardous area classifications according to NEC Article 500.56:
a.
Class I Class I locations are those in which flammable gases or vapors are or may be present in the air in quantities sufficient to produce explosive or ignitable mixtures.
Class I, Division 1 A Class I, Division 1 location is one in which it may be assumed that hazardous conditions always exist. Some of the areas listed in the NEC that would fall into this category are areas in which
Whitt2003.book Page 80 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
80
• • •
ignitable concentrations of flammable gases or vapors can exist under normal operating conditions, ignitable concentrations of such gases or vapors may exist frequently because of repair or maintenance operations or because of leakage, or breakdown or faulty operation of equipment or processes might release ignitable concentrations of flammable gases or vapors and might also cause simultaneous failure of electrical equipment in such a way as to directly cause the electrical equipment to become a source of ignition.
Class I, Division 2 A Class I, Division 2 location is a location in which it may be assumed that hazardous conditions could occur on occasion. The NEC details these as areas • in which volatile flammable liquids or gases are handled, processed, or used, but in which the liquids, vapors, or gases will normally be confined within closed containers or systems in case of abnormal operation of equipment; • in which ignitable concentrations of gases or vapors are normally prevented by positive mechanical ventilation and which might become hazardous through failure or abnormal operation of the ventilating equipment; or • that are adjacent to a Class I, Division 1 location and to which ignitable concentrations of gases or vapors might occasionally be communicated unless such communication is prevented by adequate positive-pressure ventilation from a source of clean air and effective safeguards against ventilation failure are provided.
Class I, Division x, Group A, B, C, or D The group designation provides some idea of the volatility of the material in question in descending order of its minimum igniting current (MIC) ratio, or its maximum experimental safe gap (MESG) rating. Materials that are listed in groups A through D are all gases, vapors, or vapor-producing liquids, which will always be used as Class I category modifiers.
b. Class II Class II locations are those that are hazardous because of the presence of combustible dust.
Class II, Division 1 A Class II, Division 1 location is a location in which • combustible dust is in the air under normal operating conditions in quantities sufficient to produce explosive or ignitable mixtures, • mechanical failure or abnormal operation of machinery or equipment might cause such explosive or ignitable mixtures to be produced and might also provide a source of ignition through simultaneous failure of electric equipment, through operation of protection devices, or from other causes, or • combustible dusts of an electrically conductive nature may be present in hazardous quantities.
Class II, Division 2 A Class II, Division 2 location is a location in which • combustible dust is not normally in the air in quantities sufficient to produce explosive or ignitable mixtures and dust accumulations are normally insufficient to interfere with the normal operation of electrical equipment or other apparatus, but combustible
Whitt2003.book Page 81 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
•
81
dust may be in suspension in the air as a result of infrequent malfunctioning of handling or processing equipment, and combustible dust accumulations on, in, or in the vicinity of the electrical equipment may be sufficient to interfere with the safe dissipation of heat from electrical equipment or may be ignitable by abnormal operation or failure of electrical equipment.
Class II, Division x, Group E, F, or G Materials that are listed in groups E, F, and G are all dusts. Group E is metal dusts, Group F is carbonaceous dusts, and Group G is miscellaneous dusts.
c.
Class III Class III locations are those that are hazardous because of the presence of easily ignitable fibers or flyings, but in which such fibers or flyings are not likely to be in suspension in the air in quantities sufficient to produce ignitable mixtures.
Class III, Division 1 A Class III, Division 1 location is a location in which easily ignitable fibers or materials producing combustible flyings are handled, manufactured, or used.
Class III, Division 2 A Class III, Division 2 location is a location in which easily ignitable fibers are stored or handled other than in the process of manufacture.
2. Explosion proofing If a field location is classified hazardous (e.g., Class I, Division 2), it is possible that the field junction boxes will need to be rated “Explosionproof,” or purged with nitrogen, air, or some other nonvolatile gas. Purging is discussed in a later section. The term “explosionproof” is a bit misleading. A more accurate characterization for such an enclosure would be “explosion containment,” for that is exactly what happens. “Explosionproof” would be better applied to a purged enclosure. Semantics aside, the explosionproof enclosure is built to contain any explosions that might originate within it. Small “baffles” in the form of bolt threads prevent the hot combustive gases from exiting the enclosure until they have cooled sufficiently to prevent propagation of the explosion to the surrounding atmosphere. Thus, the enclosure is very bulky. Its metal walls are thick enough to withstand an explosion and provide enough baffle surface area to cool the gases as they expand outward. Such an explosion, however localized, would tend to be harmful to the contents of the enclosure and must be avoided. To accomplish this, the various components inside the enclosure must be properly rated on an individual basis. In some cases a “Nonincendive” rating would be acceptable.7 In others, only an “Explosionproof” rating will do.8 Consult the NEC for clarification.
3. Intrinsic Safety Intrinsically safe circuits are those in which electrical energy is limited to levels insufficient to support combustion. This condition occurs in a “device that will neither generate nor store more than 1.2 volts, 0.1 ampere, 25 milliwatts, or 20 microjoules.”9 This specification can be met by the inherent characteristics of a device such as a thermocouple (i.e., a “simple apparatus”) or by virtue of some energy-limiting device like an intrinsic safety barrier (i.e., an “associated apparatus”). Intrinsically safe equipment may be installed in hazardous areas as if the area were general purpose, provided the proper approvals have been acquired. Gaining approval means independent val-
Whitt2003.book Page 82 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
82
idation of the circuitry, either by a committee set up by the owner or by Factory Mutual or some other body. Consult NEC Article 504 for additional information on intrinsic safety.
4. Purging If a field location is classified hazardous, it is possible that field equipment such as field junction boxes, analyzers, or other equipment will need to be purged with nitrogen, air, or some other inert gas. Purging simply refers to the practice of maintaining a slightly higher pressure inside the box than the surrounding atmosphere. This greatly reduces the likelihood that volatile gases will enter the box where a spark-producing element like a relay can precipitate an explosion. NFPA10 496 defines three purge categories:
a.
Class X Purge A Class X purge reduces the classification within a protected enclosure from Division 1 to unclassified.
b. Class Y Purge A Class Y purge reduces the classification within a protected enclosure from Division I to Division II.
c.
Class Z Purge A Class Z purge is, perhaps, the most commonly used purging scheme. This purge reduces the classification within a protected enclosure from Division II to unclassified.
Probably the greatest benefit of Class X or Class Z purging is that neither the enclosure nor its contents need to be rated for hazardous atmospheres. An enclosure located in a Class I area that is purged to those specifications can have components inside it that are only rated for general-purpose use. This is a great benefit as compared to the explosionproof enclosure method in which all the components inside the enclosure must be individually rated as explosionproof. Caution: In either the purging case or the explosionproof case, components mounted on the door of the enclosure, and thus outside the protective envelope of inert gas or explosionproof container, must be properly rated for the outside conditions. Refer to the NFPA specification for particulars regarding purging. The following list paraphrases some of the key elements of the Class Z purge specification: •
• • •
• •
The protected enclosure shall be constantly maintained at a positive pressure of at least 0.25 Pa (0.1 inwc) above the surrounding atmosphere during operation of the protected equipment. Measures shall be taken to protect the enclosure from excessive pressure of the protective gas supply. (Note: This implies a relief valve of some sort.) If positive pressure is not maintained, a suitable device for alarm or indication will warn you of the failure or automatically de-energize power to the ignition-capable equipment. An alarm or indication shall be provided to indicate failure of the protective gas supply. (The NFPA specification goes on to explain the types of alarms that are appropriate.) One key stipulation is that the alarm must be observable at a location that is “constantly attended.” Adequate instructions shall be provided on the enclosure to ensure that the system can be used properly. Several labels are specified that must be mounted on or near the enclosure. Opening a purged enclosure allows the protective gas blanket to dissipate, as will any protection that it provided. So, before opening a purged enclosure, one of two things must be
Whitt2003.book Page 83 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
•
83
done: (1) Remove power from the enclosure or (2) use a combustible gas analyzer to test the area. If the enclosure is opened under power, the analyzer must remain in the area during the time the enclosure is open. If the enclosure is unpowered when opened, power cannot be restored to it until either a gas analyzer is used to confirm safe conditions or the door is closed and several volumes of purge gas are forced through the enclosure. This last requirement forced the advent of the “fast purge” valve, which may be opened during the pre-powerup purge period and then closed after the proper number of air volumes have flowed through the enclosure.
If all this seems too complicated or risky, there are purge packages available commercially that will do the trick. Just mount the package on the enclosure, hook up the purge gas, and away it goes. Enclosures can also be purchased prefitted with the appropriate purge fittings. The comments made here give a brief overview of the issues only. So, be sure to refer to the NFPA guidelines before attempting to design a purge system. Operating within a hazardous area is sometimes unavoidable in process industries. It is possible to function in a hazardous area, however, provided the risks are fully analyzed. If a HazOp or other form of recognized hazard analysis process is used to analyze the hazardous risks and proper steps are taken to accommodate those risks, then it is possible to work in those areas with confidence.
F. Wiring to the Control System I/O modules come in a variety of formats called form factors. They consist of an electronics section and an I/O interface section. In a typical rack-mount configuration, the electronics section is powered from the backplane of the I/O rack. This power may or may not be distributed to the field devices. In most cases, field power (also called wetted voltage) is from a separate source. In the case of most PLC installations, this source is a power supply that is entirely separate from the PLC itself. In the case of many DCS installations, the wetted voltage is internally distributed but still separate from the electronics power distribution system. From the manufacturer’s standpoint, a major objective is to pack as many I/O points in a given amount of space as possible. Another objective might be to be able to switch large loads. Since the two objectives are mutually exclusive, the PLC manufacturer must provide his customer several alternatives. In the drive to increase point density, probably the single largest limit is the physical space needed for terminating field wiring. By “internalizing” as much wiring as possible, the space needed for field wiring terminations could be reduced. So, internally bussed power structures evolved. Today, most manufacturers provide modules with a density of up to 32 points. This is accomplished by providing an internal signal “common” that gives each point either a path to power (sourcing) or a path to ground (sinking). By such means, it is possible to terminate only one field wire to the module itself, rather than both wires that return from the field device. However, this increases the risk of having power distribution conflicts between wetted and unwetted power. Other wiring concerns should be considered given the many configurations that are possible. This section describes some of the more important wiring basics.
1. Discrete (Digital) Wiring The terms discrete and digital are interchangeable when used to describe on/off-type circuits. Turning on a light by flipping a switch is an example of a digital circuit, whereas using a dimmer to mod-
Whitt2003.book Page 84 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
84
ulate the light intensity is an example of an analog circuit. Digital circuits are composed of at least three elements: a power source, a signal source, and a load. Figure 28 shows a typical lighting circuit as you might find in your home. Current flows only when the switch is flipped. Since the circuit is either on or off, it is considered a digital circuit.
AC Power Source H
Signal Source
N
Load
Figure 28. Basic discrete (digital) circuit
Today’s on/off control is done through the PLC. Figure 29 is an overview of one discrete (on/ off) circuit, showing the entire process from the power supply through the sensor and on to the PLC.
Marshalling Panel TWISTED-PAIR CABLE
03A
PT 0
+ -
PT
+ -
PT 2
+ -
PT 3
+ -
06B 02N
02H 04A 05A 06A
1 2 3 4
06B 02N
CB2
02H 02N
Level Switch
Breaker Panel
N
XXX
H
XXN
N
110VAC
LSH-47 FJB
H 1 2 3 4
MULTICONDUCTOR HOMERUN CABLE (some not shown…)
06A 06B 02N
+ -
LOGIC
PLC
03FU 04FU 05FU 06FU 07FU
TWISTED-PAIR CABLE
N
TWISTED-PAIR CABLES
Figure 29. Discrete circuit wiring technique
In the Figure 29 example, a level switch is mounted to a vessel. The switch is monitored by a PLC digital input module. The circuit is powered through a circuit breaker (CB2) in an instrument power panel. The main power feed is brought to a marshalling panel where the power is split, feeding multiple fused circuits. Fuse 03FU is the main disconnect fuse while the remaining fuses are distribution fuses. Fuse 06FU feeds our circuit. “Hot” wire 06A is passed to the field junction box (FJB) as one wire in a multi-conductor cable. This cable, sometimes called a “homerun cable” is broken out at the field junction box (FJB), where, in this example, two unshielded twisted pair cables are fed to the end device, LSH-47. This leaves one spare conductor. The “hot” wire 06A hits the “+” termi-
Whitt2003.book Page 85 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
85
nal of the form A contact and jumpers to the “H” terminal to power up the electronics of the switch. The wire number changes across the relay contact to 06B. This wire feeds the signal back to the FJB, where the signal is passed back to the termination cabinet via the multi-conductor homerun cable. There the signal and neutral are paired and passed to the PLC module. Note that the return neutral wire, labeled 02N (since it is the return wire for CB2), is split to both the PLC and the level switch. Note: It is always advisable to use twisted-pair wire when connecting to a PLC system. Twistedpair cables exhibit excellent noise immunity, which is particularly useful when connecting to highimpedance loads, such as are found on PLC I/O modules. That’s it, in a nutshell. Following is a commentary on connectivity issues relating to PLC signal wiring.
Sinking and Sourcing The terms sinking and sourcing relate to discrete (on/off) circuits and are used to describe the way a particular component in the circuit relates to power flow. These terms actually stem from the days of transistor logic. A transistor can be thought of as a simple switch for this discussion (see Figure 30).
DC(+)
CR
DIGITAL OUTPUT
DC(+)
DIGITAL OUTPUT
a.
DCC CASE 1 SOURCING
CR
DCC CASE 2 SINKING
Figure 30. Simple switching
This type of transistor requires a small resistance on its collector (the upper side) or it will burn up. In the Case 1 example, the resistor is in place, with the load shown in parallel with the transistor. When the transistor conducts, the load is shorted out and de-energizes. When the transistor stops conducting, current flows again to the load through the resistor, which is very small in relation to the load. This is called a sourcing circuit because the load is energized when the current is sourced by the module. In the Case 2 example, the load is the collector resistor. When the transistor conducts, the load energizes. From the standpoint of the board electronics, this is a better configura-
Whitt2003.book Page 86 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
86
tion because all the heat is dissipated by the load. For several years, switching the “neutral” was common due to this characteristic. This concept can be extended to any circuit. For example, the switch in Figure 31 is considered to be sourcing because it is passing power to the load. The load is considered to be sinking because it is completing the path to ground (i.e., allowing the current to sink to ground).
DC Power Source -
Signal Source
+
Load Toggle Switch
Figure 31. Sourcing switch with sinking load
If the situation were reversed, as in Figure 32 the terminology would reverse as well. The switch is now considered to be sinking” and the load is considered to be sourcing.
DC Power Source +
Signal Source
-
Load Toggle Switch
Figure 32. Sinking switch with sourcing load
This “neutral-switching” configuration should be avoided because power is always present at the load. If a short to ground occurs between the load and the switch, the load will activate with, perhaps, unfortunate consequences.
b. Circuit Protection (Fusing) Most I/O modules are internally fused. However, that does not mean all that much to the user. While the internal fuse does limit the damage to the module itself, in most cases the module still must be sent to the factory to be repaired. So, the end result is the same to the user regardless of the internal protection.
Whitt2003.book Page 87 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
87
As a result, it is good practice to add external fuses to each I/O point at a rating just below the fuse rating on the circuit board. While this limits the size of the load that can be driven directly by the module, the internal fuse is protected. Caution: If internally fused discrete outputs are embedded in interlock chains, or if they are in circuits that depend on normally closed contacts to initiate safety actions, then another type of module that is unfused should be used. Or, interposing relays could be deployed. It is possible to have the I/O point function normally but still not pass power due to an internal fuse that is blown.
c.
Digital Input Circuits (Figures 33 and 34) Digital input (DI) modules continually scan their input points for the presence or absence of voltage. If voltage is present, a 1 is written to a memory location. If voltage is absent, a 0 is written there. The voltage type and magnitude are two of the factors that distinguish one DI module from another. Most DI points have high impedances, thus minimizing the amount of current absorbed, and so have a relatively minor effect on the power distribution system. Each digital input point can be thought of as a lamp. In many cases, only one terminal is available per point on the I/O module, so the other side of the “lamp” must be internally connected within the module to complete the circuit. DI modules can be electrically isolated point to point, or they can be grouped by internally bussing the I/O common. Most modules today are grouped as grouping allows for higher density. Point densities of up to 32 points per module are common in the grouped configuration. Figures 33 and 34 show two different DI modules. The first module internally “busses” the DC(+) side of the circuit. The I/O point then passes power to the field device. This type of module is called a sourcing module. This configuration is unusual. Switching the “common” side in the field is typically not done.
16-POINT DI MODULE
+
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
-
FU1
2 FU3
4 FU5
6 FU7
8 FU9
10 FU11
12 FU13
14 FU15
16
NOTE: Internally-Bussed Power
Figure 33. Current-sourcing digital input module
Whitt2003.book Page 88 Thursday, July 10, 2003 4:05 PM
88
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
16-POINT DI MODULE
-
+
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
FU1
2 FU3
4 FU5
6 FU7
8 FU9
10 FU11
12 FU13
14 FU15
16
NOTE: Internally-Bussed Power
Figure 34. Current-sinking digital input module If the module internally busses the DC-common side of the circuit, then the module is considered a sinking module. The I/O point completes the path to DC-common. This configuration is used in the vast majority of cases. In either case, the current flows in the same direction through the switch.
d. Digital Output Circuits Relay contacts are considered output devices because they force other devices to react when they change state. PLC digital outputs can be thought of as relay contacts. In many cases, that is just what they are. In others, the switching element may be a solid-state device of some sort. Even in that case, the relay analogy works as long as the designer remembers to consider leakage current. Review the definition of “Relay” in the Definition of Terms section if necessary. DO modules switch voltage on and off to cause an external device to change state. These modules are either isolated or non-isolated. If a module is non-isolated, then it is either sinking or sourcing.
Isolated Digital Output Circuits (Figure 35) An isolated circuit is one in which the power source can be isolated between I/O points. The source is not internally bussed. The cost is two terminals per point and so is expensive in terms of real estate. In Figure 35, there are two sources of wetted power, with the top four points isolated from the bottom four.
Nonisolated Digital Output Circuits (Figures 36 and 37) Like the DI PLC module, point density is an important feature of DO modules. As can be seen in the isolated module example in Figure 35, isolation comes with a price. A 16-terminal module has a point density of only eight, since two terminals are needed per point. By internally bussing a common, the point density can be improved dramatically. However, the result is a nonisolated module that places limits on the designer. Power
Whitt2003.book Page 89 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
Form-A Contacts
16-POINT DO MODULE
89
+
-
1
FU1 CR
2 2
FU3 CR
4 3
FU5 CR
6 4
FU7 CR
8 5
FU9 CR
10 6
FU11 CR
12 7
FU13 CR
14 8
FU15 CR
16 +
-
NOTE: Isolated Points, No Internal Bussing
Figure 35. Isolated digital output module sources must be managed. In most cases, this is not a problem since extending PLC I/O power to the field device is feasible. However, if a field device must source its own signal, then an interposing relay must be added to the circuit to provide isolation. Figures 36 and 37 show two different digital output modules. The first internally busses the DC(+) side of the circuit. The I/O point then provides a path to power, making it a sourcing module. If the module busses the DC-common side of the circuit as shown in Figure 37, then the module is considered a sinking module. The I/O point completes the path to common. This type of module is rarely used today, though several years ago it was common.
2. Analog Wiring Unlike the discrete (on/off) circuit, analog signals vary across a range. Taking the same tank described previously in Figure 29, how would the wiring change if we replaced the switch with a level transmitter? Notice in Figure 38 that we have the same circuit breaker panel as in Figure 29, but now it is feeding a DC power supply. The power supply could be in its own cabinet, or it could be in the marshalling panel. In any case, DC power is distributed in the marshalling panel. A single fuse could power several circuits, or each circuit could be fused. The transmitter is fed +24 VDC at its positive terminal. The 4–20 mA current signal is sourced from the (-) terminal to the PLC. Cabling is twisted pair and shielded. The shield is terminated in the marshalling panel where all shields are gathered and terminated to a ground lug that is isolated from the cabinet. Care should be used to ensure that the shield is only grounded at one spot. Shields that are grounded in more than one spot inject large noise spikes onto the signal. This condition is called a ground loop and can be a very difficult problem to isolate, as the problem is intermittent. A “quiet” ground should be used to ground all the shields at one point. The signal cable is numbered with the transmitter number, and the wires inside are numbered to provide power source information.
Whitt2003.book Page 90 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
90
Form-A Contacts
16-POINT DO MODULE
+
FU1 CR
1
2
2
FU3 CR
3
4
4
FU5 CR
5
6
6
FU7 CR
7
8
8
FU9 CR
9
10
10
FU11 CR
11
12
12
FU13 CR
13
14
14
FU15 CR
15
16
16
NOTE: Internally-Bussed Power
Figure 36. Current-sourcing digital output module
Form-A Contacts
16-POINT DO MODULE
-
+ FU1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CR
2 FU3 CR
4 FU5 CR
6 FU7 CR
8 FU9 CR
10 FU11 CR
12 FU13 CR
14 FU15 CR
16
16
NOTE: Internally-Bussed Common
Figure 37. Current-sinking digital output module That is the basic two-wire analog input circuit. Following is some specific information regarding the various analog possibilities:
a.
Circuit Protection (Fusing) Analog circuits are always low voltage, usually 24 VDC, and thus below the danger threshold. As a result, fusing individual analog circuits is generally not required for personnel
Whitt2003.book Page 91 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
Twisted-Pair Unshielded Cable
Marshalling Panel 03A
Twisted-Pair Shielded Cable
PT 0
+ -
PT
+ -
PT 2
+ -
PT 3
PLC
+ -
03FU 04FU 05FU 06FU 07FU 1 2 3 4
06B 02N
DC(+) 04A 05A 06A
91
Power Supply Cabinet 24-VDC Power Supply H DC(+) N DCC G
Breaker Panel CB2 H XXX 110 VAC N XXN Level Transmitter
02H 02N G
N
LT-10
FJB 1 2 3 4
06B DCC
06A 06B SHLD
+ -
Shield Ground Busbar Twisted-Pair Shielded Cables S
Figure 38. Analog circuit wiring technique safety. Also, most analog I/O modules have current-limiting circuits onboard. So, fusing is generally not required to protect the modules. If these two conditions are true—and the designer should confirm this with the manufacturer—then per-point fusing can be avoided if desired. If a designer wishes to save money by not fusing every point, then grouping the circuits into damage-control zones should be considered. For example, if there is a pump pair, a primary and a backup, instruments for the two should be in separate fuse groups to prevent a single blown fuse from taking them both out.
b.
Noise Immunity Analog circuits are susceptible to electronic noise. If, for example, an analog cable lies adjacent to a motor’s high-voltage cable, then the analog signal cable will act as an antenna, picking up the magnetically coupled noise generated by the motor. Other sources of noise exist such as radio-frequency (RF) radiation from a walkie-talkie.
Twisted-Pair Cables Electronic noise may be greatly reduced by the use of twisted-pair cabling. Most instruments use two wires to transmit their signals. Current flows out to the device in one wire and back from the device in the other. If these wires are twisted, then the noise induced will be very nearly the same in each wire. Since the current flow is identical in each except that it travels in opposite directions, the noise is mostly cancelled out.
Shielding A further refinement in noise rejection is shielding. Most of the noise is rejected through the use of twisted-pair cabling. Additional noise may be filtered out by use of a grounded braid or foil shield. The shield should never be grounded in more than one place to avoid ground loops. Most instrument manufacturers recommend grounding the shield at the field instrument. However, a better place to do it is in the marshalling panel. It is easier to verify and manage the grounds if they are in one place. Also, it is possible to ensure a good ground at that point.
Whitt2003.book Page 92 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
92
Conduit A final refinement in noise rejection is grounded metallic conduit. This is rarely required except for data communications cables, but is an option for particularly critical circuits.
c.
Resistance Temperature Detector A resistance temperature detector (RTD) is made of a special piece of wire whose electrical properties of resistance change in a predictable way when exposed to varying temperatures. The material of choice today is 100-ohm platinum, though other types such as 10ohm copper are sometimes used. For the platinum RTD, the rating is for 100-ohms at 0ºC. Changing the temperature causes the resistance to change in the wire. These changes are very minute, causing voltage variations in the millivolt range. RTDs are connected to a Wheatstone bridge circuit that is tuned to the RTD. But, tuning occurs on the bench. What about the field environment? We have already discussed the line attenuation difficulties inherent in millivolt signals (Part II, Chapter 4). This problem is overcome in the RTD circuit by the use of one or two “sense” inputs. These inputs help negate the effects of copper losses due to long lines and temperature variations and are additional wires that must be included in the RTD cable, hence the terms three-wire and four-wire RTDs.
d.
Thermocouple A thermocouple device employs the property of physics that when two dissimilar metals are joined, an electromotive force (EMF) is developed that changes with temperature. This EMF manifests itself as a millivolt signal. When certain combinations of these dissimilar metals are used, a predictable curve results as temperature at the junction is changed. The signal is measured at the open end of the two wires, and a millivolt-per-degree scale is used to convert the voltage to engineering units. The thermocouple is thus a two-wire device. It is susceptible to radiated and induced noise and so is usually housed in a shielded cable if extended for a very long distance. The thermocouple signal is also susceptible to degradation due to line loss, so minimizing the cable length is desirable. Also, it is important to use the proper extension wire. A thermocouple usually comes with a short “pigtail” connection to which extension wire must be attached. If a different wire material, such as copper, is used to extend the signal to the PLC, a cold junction is created that causes a reverse EMF that partially cancels out the signal. Therefore, the proper extension wire should be used, else a device called a cold-junction compensator, or ice-point reference, needs to be installed between the copper wiring and the thermocouple wiring. Thermocouple I/O modules already have the cold-junction compensation onboard, so using the proper thermocouple extension wire is required. Specific types of thermocouples exhibit different temperature characteristics. A type J thermocouple is formed by joining an iron wire with a constantan wire. This configuration provides a curve that is relatively linear between 0 and 750ºC.11 A type K thermocouple has a nickel-chromium wire mated to a nickel-aluminum wire, sometimes called chromel/ alumel. The type K thermocouple spans a temperature range of -200 to 1250ºC. Other combinations yield different response curves.
e.
0–10 Millivolt (mV) Analog Analog signals were first generated by voltage modulation. In the old days, a transmitter would generate a weak signal that had to be captured and then filtered and amplified so it
Whitt2003.book Page 93 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
93
could be used to move a pen on a recorder, or a needle on a gauge. The Achilles heel of the millivolt signal is its susceptibility to electrical noise. This signal-to-noise ratio problem increases as a function of cable length. So, the transmitter needs to be in close proximity to its load. Millivolt signals today are, by and large, fed to transducers that convert the small signal to a current or to other media less susceptible to noise and decibel (dB) loss before leaving the vicinity of the sensing element. However, some recorders and data acquisition systems still operate on the millivolt signal.
f.
4–20 Milliamp (mA) Analog The drive to overcome the line attenuation shortcomings of the millivolt signal resulted in the development of the 4–20 mA current loop. As a result, this method of transmitting analog signals quickly became the industry standard. Most field instruments on the market today have a sensing element and a transmitting element. The transmitter is “tuned” to the sensor, which may provide any type of signal from a frequency-modulated analog to a millivolt DC level. In any case, the transmitter will interpret this input signal and convert it to an output current that is between 4 and 20 mA and, within that span, is proportional in magnitude to the input. The process of tuning the output to the input is called scaling. Thus, the transmitter becomes what is referred to as a variable current source. Just as a battery, as a voltage source, tries to maintain a constant voltage regardless of the amount of load applied to it, the current source tries to maintain a constant current (for a given input signal) regardless of load. Since current is common at all points of a series circuit, the problem of cable length—as noted as a problem with the millivolt signal—is nullified. Of course, the ability of the device to force a constant current through a circuit can be overcome if enough load is applied. Therefore, the designer must know how much energy the current source is capable of producing. Generally, today’s instruments are able to maintain 20 mA at a circuit load of 1 k ohm. Since a typical instrument has no more than 250 ohms of input resistance, it is possible to “hang” several instruments from a single current source without needing an isolator. For example, a single transmitter should be able to feed its signal to a PLC, a chart recorder, and a totalizer at a cost of 750 ohms plus the line resistance. This should still be within the comfort zone of a typical transmitter. Note: There are still instruments with 600-ohm ratings on the market, so the designer should always check if a complex circuit is contemplated. To determine the energy available to the circuit, the designer must be able to identify the provider of that energy. That task is sometimes not as straightforward as it might appear, and the answer to the question will greatly impact the wiring of the circuit. There are two primary types of analog circuit, as described from the point of view of the transmitter. Transmitters with two wires are considered to be passive devices that sink current, while transmitters with four-wires are active devices that source current. Figure 39 depicts three temperature transmitters, all connected to different I/O points on the same PLC module. One transmitter is directly powered (i.e., four-wire), while the others are indirectly powered (i.e., two-wire). Each transmitter is connected to a control device—in this case, a PLC input. From the PLC perspective, all 4–20 mA current inputs are really voltage inputs. Resistors, either user-provided external ones as shown here or internal ones, are used to convert the current to a voltage. The computer points themselves are actually high-resistance volt-
Whitt2003.book Page 94 Thursday, July 10, 2003 4:05 PM
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
94
4-WIRE TRANSMITTER
ANALOG INPUT MODULE
250-ohm resistor converts 4-20 mA to 1-5 VDC V
°C +
+
+ 4-20 mA
TT
TE
R
-
-
N
24-VDC POWER +
2-WIRE TRANSMITTER
Point #2
-
V
+
+
R
-
-
+
Transmitter converts millivolts into 4-20 mA current
1-5VDC
Point #3 V
Module +24 VDC
4-20 mA
TT -
+
R
T/C TYPE K 110 VAC
Volts
Module C 20 DC Common
+
-
TI -
T/C TYPE K 2-WIRE TRANSMITTER
Module +24 VDC
+ 4-20 mA
TT
TE
Volts
1-5VDC Module C 20 DC Common
H
TE
TI -
T/C TYPE K 110 VAC
Point #1 Module +24 VDC
H
+
R
TI
Volts
-
-
1-5VDC
N
Module C 20 DC Common Volts
1-5 VDC RECORDER
Jumper
Fi 39 A l ii t h i 2 i 4 i Figure 39. Analog wiring methods: 2-wire vs. 4-wire
meters, which gives them excellent isolation from the field devices and minimizes additional loading on the input circuit. The I/O points on the PLC are shown with internal power available for each point, so the module is capable of being the voltage source for the loop. Following is a detailed commentary on the differences between two-wire and four-wire devices:
Four-Wire Circuit A four-wire transmitter is one that provides the energy to both power the loop and generate the current-modulated signal. Most level transmitters, for example, are four-wire devices. Four-wire devices always have power connections in addition to the signal connections. Yet, not all such powered transmitters are four-wire. If a powered transmitter’s output is noted as “passive”, then the device may be treated as a two-wire unit from the standpoint of the signal circuit. Most recording devices are externally powered, but are passive on the circuit. In these cases, the external power is for the internal electronics of the unit only. The signal circuit is
Whitt2003.book Page 95 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 5: DESIGN PRACTICE
95
isolated from this power source. Note that the recorder shown on the bottom circuit is a powered, passive device.
Two-Wire Circuit A two-wire device is said to be loop powered. This means that the device functions by absorbing energy from the current loop. This is also referred to as current sinking. This can be a bit confusing because a transmitter that is current sinking is still the signal source for the circuit. However, the energy that it needs to generate the signal is absorbed from the loop. Power for the current loop is supplied elsewhere. A transmitter classified as two-wire must typically be the first device in the circuit with respect to current flow. In other words, the positive terminal of the transmitter must be directly connected to the positive terminal of the voltage source. The voltage source is usually a 24-VDC power supply.
(a) Two-Wire Circuits with Stand-Alone Power Supply Referring back to the Figure 39, PLC I/O point 2 depicts a two-wire circuit with an external DC power supply. Notice that the wires must be rolled at the PLC for the proper polarity to be present across the I/O point. That is because current flow is now reversed with respect to the previous example because the transmitter must become the first load in the loop as opposed to being the energy source for the loop.
(b) Two-Wire Circuits with PLC Internal Power Supply Most PLC systems today are able to source the loop current themselves by simply connecting the positive terminal of the transmitter to a different terminal at the PLC. The negative terminal of the transmitter is then tied to the positive side of the I/O point and the negative side of the I/O point is jumpered to the PLC system DC common. That is depicted in the I/O point 3 example. In that example, a recorder has been added to the loop.
G. Design Practice Summary To be comfortable in a design role, one needs to be knowledgeable about the expectations of those in the business. This chapter has attempted to address some of the more important concepts: • • • • •
What is an instrument database, and what good is it? What is involved in document management? What are an I/O list and an instrument list, and what is a good way to maintain them? What is good wiring practice? How should wires be tagged? What should be presented on a wiring diagram? What is a hazardous area, and what are some of the design considerations? What is intrinsic safety, and how is it different from explosionproof?
These topics provide a basic understanding of some of the issues dealt with in Part III.
Whitt2003.book Page 97 Thursday, July 10, 2003 4:05 PM
Chapter 6: The Control System The control systems world is wide and deep. It is a world of acronyms and keywords that represent arcane systems and concepts, interfaces and networks, and hardware and software. Like an iceberg, much of its mass is below the surface. To most engineering professionals, the plant’s control system consists of a set of enclosures bolted to a raised floor behind the control room, or a set of monitors. To the control systems professional—the systems integrator—it is a lush world unto its own. This chapter is written for the outsider. It is written for the project manager who needs some perspective or for the new engineer or technician who needs some basic understanding. It is written around no particular control system, though more time is spent on the PLC than on the DCS. I/O interface concepts, for example, are valid regardless of the flavor of the control system. This chapter explores some of the different types of control systems in wide use today and delves into some of the major issues: •
• • •
Process controller. How did the process controller evolve? What are the origins of the two most common controller styles, the DCS and the PLC? How are they different, and how are they used today? Human-machine interface (HMI). How did the HMI evolve, and what are some of the issues relating to specification and design of the basic HMI? Data communications interface. What are some of the major communications protocols in use today, and what are some of their features? I/O interface. How is the control system mated to the production facility? What are some of the basic concepts? How is an I/O map derived? How is an I/O count derived? What I/O module types are available, and what are some of the considerations for proper wiring practice?
A. Introduction An industrial plant exists for one purpose: to convert raw material into something useful. This can hopefully be done in such a way as to make the end product more valuable than the sum of the uncombined source materials, the energy expended to effect the conversion, and the cost expended in bringing the end product to market. Otherwise, why bother? In much of the discussion that follows, as in industry, the term process is used frequently and in various applications. For example, the act of energizing a washing machine is one step of the clothes-cleaning process. This is the more common use of the word. However, in the controls industry, the term process is used as a generic term to describe both the production method and the related equipment. To expand on the washing machine analogy, by selecting “permanent press,” the operator has selected a specific method, or process, that changes the way the agitator functions, among other things. The agitator itself is then referred to as process equipment.
B. The Cognitive Cycle The physical plant is an entity capable of processing raw materials into a desired product. It is inanimate. Yet, by mating this inanimate object with an operator, it is transformed into something else
Whitt2003.book Page 98 Thursday, July 10, 2003 4:05 PM
98
SUCCESSFUL INSTRUMENTATION AND CONTROL SYSTEMS DESIGN
entirely. By adding a properly designed control system, the plant acquires the approximation of a central nervous system. Like the nervous system of any creature, this one detects the condition of its environment, encodes the information, and transmits it to a “brain,” where the information is decoded and processed. During this processing stage, the information is used as the basis for decision making. The end result is a set of commands that is encoded and transmitted to the “muscles” where action is initiated. Action occurs, causing changes that are sensed and analyzed and which result in additional actions. In the background, some of the raw and resulting processed information is stored in historical memory for later retrieval. This cognitive cycle (see Figure 40) is a natural phenomenon as basic as the sine wave. Sentient creatures everywhere follow the same pattern as they traverse their environment. They sense their surroundings to gather information, they analyze the information, and then they react to it. Rather elementary, as are most things that work well. And, this is a process that works, as evidenced by the fact that we are here! Few creatures are able to affect the physical world and change to fit their needs, however. That is left, mostly, to humans. The machines we have built to manage our world follow this same control cycle.
ANALYZE
DETECT
The Cognitive Cycle
REACT
The Physical World Figure 40. The cognitive cycle
In industry, process sensors detect the condition of material being processed. These sensors, made up of detectors and transmitters, convert the mechanical and physical properties of the material into electrical facsimiles. These signals are coupled to a central processing site where they are converted to numeric values and analyzed. The analysis compares the actual process conditions to the desired conditions and develops a set of corrections that are expected to result in elimination of errors. These numeric correction commands are then converted to electrical signals that are fed to final control elements, where conversion from electrical energy to mechanical energy takes place.
Whitt2003.book Page 99 Thursday, July 10, 2003 4:05 PM
PART II – CHAPTER 6: THE CONTROL SYSTEM
99
C. Control System Basics Processing facilities today are, for the most part, computer controlled. Computer systems that are used in control applications can be broken into several basic components as shown in Figure 41.
TYPICAL CONTROL SYSTEM OPERATOR
OPERATOR INTERFACE
OTHER COMPUTERS
COMM INTERFACE
I/O INTERFACE
FIELD DEVICES
COMM INTERFACE
"SMART" EQUIPMENT
CPU
Figure 41. Typical control system
•
•
• •
The central processor is the heart of the control system. The central processing unit (CPU) contains the operating instructions for the control system. These instructions define how the control system will react to various stimuli such as a change in process temperature or flow or a change in operational mode. New information is gathered by the CPU using various translators called interfaces. These interfaces convert information from various sources into a common language that can be understood by the CPU. The operator interface is typically a desktop computer running a software package that converts commands from the operator into digital values, and transmits them to the CPU in the right format. The communications interface translates communication protocols and allows a path for communication to other supervisory computers or process control computers. The I/O interface converts electrical input signals to data and then converts data to electrical signals to be fed to output devices.
The various interfaces exist to pass information among the central processor and various users, whether those users are human or other machines. Figure 42 provides the basic structure of the process control system as it relates to the production facility. There are variations to this theme, of course, but this will do as a generalization. The control system senses the condition of the physical plant and converts this information into useful data that may be presented to the operator. The operator analyzes this information and compares the actual condition of the process to the desired condition. The operator then issues commands back to the control system, which responds by converting these commands into electrical signals that are fed to the final control elements. These final control elements are devices that consume energy and do work such as move control valves, start and stop motors, and so on. Like muscles, these control elements impose the operator’s will on the process. Everything begins with the plant operator (see Figure 43), who places the control system into either automatic or manual mode. Automatic or manual mode is usually selected by the use of a physical switch instead of a computerized mode selection to preserve the ability to run the plant manually if the computer fa