IESNA DG-28-2015 Design Guide for Selection Installation Operations and Maintenance of Roadway Lighting Control Systems.pdf

1、PREPARED BYANSI/IES DG-28-15Design Guide for Selection, Installation,Operations and Maintenance ofRoadway Lighting Control SystemsANSI/IES DG-28-15Guide for Selection, Installation, Operations and Maintenance of Roadway Lighting Control Systems Publication of this Design Guidehas been approved by IE

2、S.Suggestions for revisionsshould be directed to IES.Prepared by:The Energy Management Subcommittee of the Roadway Lighting Committee of theIlluminating Engineering Society of North America ANSI/IES DG-28-15Copyright 2015 by the Illuminating Engineering Society of North America.Approved by the IES B

3、oard of Directors, June 12, 2015, as a Transaction of the Illuminating Engineering Society of North America.Approved as an American National Standard July 23, 2015.All rights reserved. No part of this publication may be reproduced in any form, in any electronic retrieval system or otherwise, without

4、 prior written permission of the IES.Published by the Illuminating Engineering Society of North America, 120 Wall Street, New York, New York 10005.IES Standards and Guides are developed through committee consensus and produced by the IES Office in New York. Careful attention is given to style and ac

5、curacy. If any errors are noted in this document, please forward them to the Director of Technology, at the above address for verification and correction. The IES welcomes and urges feedback and comments. ISBN # 978-0-87995-314-0Printed in the United States of AmericaDISCLAIMERIES publications are d

6、eveloped through the consensus standards development process approved by the American National Standards Institute. This process brings together volunteers represent-ing varied viewpoints and interests to achieve consensus on lighting recommendations. While the IES administers the process and establ

7、ishes policies and procedures to promote fairness in the development of consensus, it makes no guaranty or warranty as to the accuracy or completeness of any information published herein.The IES disclaims liability for any injury to persons or property or other damages of any nature whatsoever, whet

8、her special, indirect, consequential or compensatory, directly or indirectly result-ing from the publication, use of, or reliance on this document.In issuing and making this document available, the IES is not undertaking to render professional or other services for or on behalf of any person or enti

9、ty. Nor is the IES undertaking to perform any duty owed by any person or entity to someone else. Anyone using this document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professional in determining the exercise of reasonable care in any given c

10、ircumstances.The IES has no power, nor does it undertake, to police or enforce compliance with the contents of this document. Nor does the IES list, certify, test or inspect products, designs, or installations for compliance with this document. Any certification or statement of compliance with the r

11、equirements of this document shall not be attributable to the IES and is solely the responsibility of the certifier or maker of the statement.ANSI/IES DG-28-15Prepared by the IES Roadway Lighting Energy Management Sub-CommitteeJim Frazer, Sub ChairOmar Rivera, Vice ChairJ. Adams*L. AsselinS. Banksto

12、n*G. Brunet*K. Burkett*J. Camp*D. Cavalcanti*J. Cheung*M. Cunningham*J. DaCosta*M. Dudas*A. Duma*K. Fitzmaurice*J. Garcia*R. HarveyA. Hoefer*J. Howarth*R. JonesJ. Kaufman*D. McLean*K. Min*P. MitchellJ. Mugivan*R. Patel*D. PaulinC-A. PoirierM. Poplawski*R. Rainer*L. SmithM. Stevens*F. StohlC. Suvagau

13、*G. Westergren*M. Wilbur*H. Wolfman*Roadway Lighting CommitteeWilliam Smelser, ChairJ. Bloomfield, Vice ChairJ. Frazer, SecretaryE. Morel, TreasurerM. AitkenheadC. AndersenJ. ArmstrongM. Baginski*J. BastianpillaiD. BaumJ. Brown*M. BucciK. BurkettD. Cavalcanti*G. ChelvanayagamJ. CheungN. Clanton*R. C

14、learS. CoyleC. Craig*D. Crawford*M. CunninghamJ. DaCosta*C. DibleyN. DittmannM. DudasA. Duma*R. Ebbert*G. Engstrom*K. Fitzmaurice*R. GibbonsR. GuptaJ. HartR. HarveyJ. Havard*W. Hughes*D. Husby*M. Janoff*J. Jewell*J. JiaoR. JonesH. KashaniR. KauffmanD. KeithM. Kelly*C. Kerschner*E. KramerC. KwongS. L

15、ansfordR. LariveeG. Lauziere*L. LeetzowO. LetamendiR. LeVere*I. Lewin*G. ListerT. Lohman*X. Lou*P. Lutkevich*L. Lutley*E. MacGill*M. MaltezosJ. Marsh*M. MayerJ. McCormick*S. McKnight*J. Meyers*J. Mickel*P. MitchellK. MolloyD. Monahan*J. OConnor*H. Odle*D. Okon*D. PaulinM. Pearse*C. Pekar*J. Petty*C-

16、A. Poirier*L. RadetskyR. RainerM. Riebling*O. Rivera*J. RobinsonP. SabauM. SeppeltB. Shelby*A. SilbigerJ. SimmersL. SmithM. SmolyanskyJ. Snowden*R. StemprokM. Stevens*F. StohlL.Tebow*M. TedescoG. Thiesse*U. Thurairajah*J. WeaverS. WegnerS. WentworthE. Yao*R. YeagerAdvisory Members*Honorary Members*A

17、NSI/IES DG-28-15AMERICAN NATIONAL STANDARDApproval of an American National Standard requires verification by ANSI that the requirements for due process, consensus, and other criteria have been met by the standards developer.Consensus is established when, in the judgment of the ANSI Board of Standard

18、s Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made toward thei

19、r resolution.The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether that person has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the st

20、andards.The American National Standards Institute does not develop standards and will in no circumstances give an interpretation to any American National Standard. Moreover, no person shall have the right or authority to issue and interpretation of an American National Standard in the name of the Am

21、erican National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard.CAUTION NOTICE: This American National Standard may be revised at any time. The procedures of the American National Standards Inst

22、itute require that action be taken to reaffirm, revise, or withdraw this standard no later than five years from the date of approval. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute.ANSI/IES DG

23、-28-15Please refer to the IES Bookstore after you purchase this IES Standard, for possible Errata, Addenda, and Clarifications, www.ies.org/bookstoreContents1.0 Introduction .12.0 Goals and Best Practices .12.1 Safety .12.2 Project Planning Introduction .12.2.1 The Systems Engineering Process 22.2.1

24、.1 What is a System?22.2.1.2 What is Systems Engineering? 22.2.1.3 Systems Engineering Principles .22.2.1.3.1 Start with Your Eye on the Finish.22.2.1.3.2 Stakeholder Involvement is Key22.2.1.3.3 Define the Problem Before Implementing the Solution22.2.1.3.4 Delay Technology Choices32.2.1.3.5 Divide

25、and Conquer .32.2.1.3.6 Connecting the Dots - Traceability32.2.1.3.7 The “V“ Systems Engineering Model32.2.1.3.8 Overview of the “V“ Model 32.2.1.3.9 Connecting the Left and Right Sides of the “V“42.2.1.3.10 Decision Points.52.2.2 User Needs .52.2.2.1 Who and What Can Generate User Needs? .52.2.3 Op

26、erational and Functional Requirements 62.2.4 Testing .82.4 Cost Benefit Analysis92.5 Procurement .93.0 Control Technologies.93.1 Stand-alone Technologies 93.1.1 Background.93.1.2 Dusk to Dawn Photo Controls (Photocells) .103.1.3 Time Switches103.1.4 Part Night Photo Controls (Photocell) .103.1.5 Ast

27、ronomical TIme Clocks 113.1.6 Motion Detectors113.2 Networking and Communications Technologies 113.2.1 Background113.2.2 Management Station.123.2.3 Data Logger .133.2.4 Streetlight Controllers 143.2.5 Data Logging.143.2.6 Data Security.14ANSI/IES DG-28-154.0 Adaptive Lighting Design 144.1 General Co

28、nsiderations .144.2 Specific Design Considerations 164.2.1 Residential Streets 164.2.2 Collector and Arterial (Major) Streets174.2.3 Freeways and Highways .184.2.4 Sidewalks, Walkways and Alleyways184.2.5 Tunnels .184.3 Inventory Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

29、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.4 Deployment .195.0 Adaptive Lighting Operations.195.1 Preventive Maintenance Analysis.195.2 Inventory Analysis .195.3 Work Management Analysis .195.4 Asset Management.205.5 Electrical System Maintenance.205.6 Other Considerations.205.

30、6.1 Asset Tracking .205.6.2 Electrical Safety Equipment .205.7 Power Metering and Monitoring 205.7.1 Tariffs.205.7.2 Flat Rate Billing.205.7.3 Metered Service 215.7.4 Meter Accuracy .216.0 Integration and Commissioning.216.1 Interoperability 216.2 Interchangeability 226.3 Compliance vs. Conformance2

31、26.4 Integration with US DOE “Smart Grid” Compliant Systems 226.5 Integration with Intelligent Transportation Systems .226.6 Integration with Building Automation Systems .23General References23Annex A U.S. DOT Intelligent Transportation Standards .23Annex B U.S. DOT Standard NTCIP 1213 Electrical an

32、d Lighting Management Systems .24Annex C U.S. Department of Commerce / National Institute of Standards and Technology - Smart Grid Interoperability Panel Standards .25Annex D U.S. Department of Energy Municipal Solid State Lighting Consortium 26Annex E TALQ Consortium26Annex F BACnet.27Annex G LonWo

33、rksTechnology.27Annex H Zigbee .27Annex I IMSA Roadway Lighting Technician Courses .27Annex J Interoperability and the OSI 7 Layer Model 28Annex K Glossary .30Annex L General Bibliography .361ANSI/IES DG-28-151.0 INTRODUCTIONElectric outdoor lights are generally controlled in groups via relays (cont

34、actors) and photocells, or controlled individually with photocells mounted on the luminaires. In some cases time clocks are used to control the lighting. Todays digital tech-nology, in both control systems and light sources, offers new potential to better control the lighting system and provide the

35、right amount of lighting when required. These improved controls allow the lighting system to adapt the lighting levels to the ambient conditions. Better lighting controls can result in improved visibility and potential savings in both energy and maintenance costs. The purpose of this Design Guide is

36、 to educate the reader on control technologies, and to advise considerations for their implementation.Before moving forward, it should be understood that these new systems, while bringing the poten-tial to improve visibility as well as considerably reduce both energy and maintenance costs, also brin

37、g a significant and long-term investment. For that reason, the user/designer should understand the functionalities and consequences of the differ-ent technologies, each with its own cost/benefit analysis.The drive to reduce energy consumption, and the related costs, has led to new strategies for lig

38、hting controls. In many cases, particularly in retail areas and parking lots, full light output is not required throughout the duration of the night, after busi-ness hours. In some cases street and roadway lighting can also be reduced as the level of activity is reduced, at specific times during the

39、 hours of darkness. New digital technologies in both con-trols and light sources now enable the user to turn specific individual or groups of lights on or off, or to adjust individual or group light levels up or down as needed. These new control systems enable full customization - from individual li

40、ght points to com-plete lighting systems - in order to meet the spe-cific needs of each user. Adaptive control systems can make adjustments due to changing ambient light levels, pedestrian activity, vehicular traffic and even weather conditions.This Design Guide presents an overview of light-ing con

41、trol technologies, some of which are new and evolving, and others which have a proven his-tory (for examples, refer to IES TM-23-11 Lighting Control Protocols).2.0 GOALS AND BEST PRACTICES2.1 SafetyThis document does not cover safety in detail; how-ever, it does list some specific design considerati

42、ons which can relate to safety. Prior to undertaking any installation where lighting levels are reduced from their current values (or standards) it is recommended that a review and study be undertaken, as further dis-cussed in the Design Section. Additionally, all poten-tial system failures should b

43、e identified and tested to ensure that the system fails to a well-known/designed safe condition. When using a networked system, notice of failures should be sent to operators and maintenance personnel, in a near real-time basis.2.2 Project Planning IntroductionProject planning typically includes det

44、ermination of the user needs for the project, the subsequent refin-ing of those user needs into project specific opera-tional and functional requirements, and lastly the development of a project specific test plan, for verifi-cation and validation. Prior to selection and deploy-ment it is recommende

45、d a project plan be devel-oped and utilized. The USDOT (U.S. Department of Transportation) as well as many states and local agencies require the use of the Systems Engineering Process (SEP) as a project development tool. The SEP contains the following concepts which are examined in subsequent sectio

46、ns of this document: SEP is a structured process for arriving at a final design of a system Analysis determines needs of system Requirements of systems are traced back to user needs User needs and requirements are verifiedSEP Benefits: Guides the development team and manages expectations Reduces sig

47、nificant uncertainties in the cost and schedule Reduces late changes that drive project costs Improves the success rate Unambiguously defines the problem before implementing the solution2ANSI/IES DG-28-15required functionality early in the development cycle, documenting requirements, and then procee

48、ding with design synthesis and system validation while considering the complete problem.”Systems engineering integrates all the disciplines and specialty groups into a team effort forming a structured development process that proceeds from concept to production to operation. Systems engi-neering con

49、siders both the business and the techni-cal needs of all customers with the goal of providing a quality product that meets the user needs.Note that this definition is very broad it covers the project life cycle from “needs definition” to “system disposal”. It includes technical activities like require-ments and design, as well as project activities like risk management and configuration management. Systems engineering provides a systematic process and tools that directly support project management.2.2.1.3 Systems Engineering Pr