IEEE P1584.1 Working Group Meeting Slides

Transcription

IEEE P1584.1Working Group Meeting SlidesIEEE Guide for the Specification of Scope andDeliverable Requirements for an Arc-FlashHazard Calculation Study in Accordance withIEEE Std 1584 Reno, NVMarch 2, 202010:00 AM - 12:00 PMP1584.1 WG Meeting 2020 ESW Reno, NV1

1. Call to Order / SafetyAnnouncementsDaleep MohlaP1584.1 WG Meeting 2020 ESW Reno, NV2

2. Introductions andAffiliationsMembership UpdateJim Phillips/Ray CrowP1584.1 WG Meeting 2020 ESW Reno, NV3

3. Establishment of quorumJim Phillips / Ray CrowP1584.1 WG Meeting 2020 ESW Reno, NV4

4. Information on RosterGDPR RequirementsRay CrowP1584.1 WG Meeting 2020 ESW Reno, NV5

5. Approval of Draft AgendaPosted on 1584.1 websitehttps://sagroups.ieee.org/1584-1/Daleep MohlaP1584.1 WG Meeting 2020 ESW Reno, NV6

6. Approval of September 7,2019 draft meeting notesRay CrowP1584.1 WG Meeting 2020 ESW Reno, NV7

(Draft of meeting notes and slidesused during the September 7, 2019meeting were posted on the 4.1 WG Meeting 2020 ESW Reno, NV8

7. IEEE-SA Patent SlidesCopyright Policy SlidesNo Recording Policy SlidesDaleep MohlaP1584.1 WG Meeting 2020 ESW Reno, NV9

Instructions for the WG ChairThe IEEE-SA strongly recommends that at each WG meeting the chair or adesignee: Show slides #1 through #4 of this presentationAdvise the WG attendees that: Instruct the WG Secretary to record in the minutes of the relevant WG meeting: IEEE’s patent policy is described in Clause 6 of the IEEE-SA Standards Board Bylaws;Early identification of patent claims which may be essential for the use of standards underdevelopment is strongly encouraged;There may be Essential Patent Claims of which IEEE is not aware. Additionally, neither IEEE, the WG,nor the WG Chair can ensure the accuracy or completeness of any assurance or whether any suchassurance is, in fact, of a Patent Claim that is essential for the use of the standard under development.That the foregoing information was provided and that slides 1 through 4 (and this slide 0, if applicable)were shown;That the chair or designee provided an opportunity for participants to identify patent claim(s)/patentapplication claim(s) and/or the holder of patent claim(s)/patent application claim(s) of which theparticipant is personally aware and that may be essential for the use of that standardAny responses that were given, specifically the patent claim(s)/patent application claim(s) and/or theholder of the patent claim(s)/patent application claim(s) that were identified (if any) and by whom.The WG Chair shall ensure that a request is made to any identified holders of potential essential patentclaim(s) to complete and submit a Letter of Assurance.It is recommended that the WG Chair review the guidance in IEEE-SA Standards Board Operations Manual6.3.5 and in FAQs 14 and 15 on inclusion of potential Essential Patent Claims by incorporation or byreference.Note: WG includes Working Groups, Task Groups, and other standards-developing committees with a PARapproved by the IEEE-SA Standards Board.(Optional to be shown)

Participants have a duty to inform the IEEE Participants shall inform the IEEE (or cause the IEEE to be informed) of theidentity of each holder of any potential Essential Patent Claims of which theyare personally aware if the claims are owned or controlled by the participantor the entity the participant is from, employed by, or otherwise representsParticipants should inform the IEEE (or cause the IEEE to be informed) of theidentity of any other holders of potential Essential Patent ClaimsEarly identification of holders of potentialEssential Patent Claims is encouragedSlide #1

Ways to inform IEEE Cause an LOA to be submitted to the IEEE-SA (patcom@ieee.org); orProvide the chair of this group with the identity of the holder(s) of any andall such claims as soon as possible; or Speak up now and respond to this Call for Potentially Essential PatentsIf anyone in this meeting is personally aware of the holder of any patent claimsthat are potentially essential to implementation of the proposed standard(s)under consideration by this group and that are not already the subject of anAccepted Letter of Assurance, please respond at this time by providing relevantinformation to the WG ChairSlide #2

Other guidelines for IEEE WG meetings All IEEE-SA standards meetings shall be conducted in compliance withall applicable laws, including antitrust and competition laws. Don’t discuss the interpretation, validity, or essentiality of patents/patentclaims.Don’t discuss specific license rates, terms, or conditions. Relative costs of different technical approaches that include relative costs of patentlicensing terms may be discussed in standards development meetings. Technical considerations remain the primary focusDon’t discuss or engage in the fixing of product prices, allocation ofcustomers, or division of sales markets.Don’t discuss the status or substance of ongoing or threatened litigation.Don’t be silent if inappropriate topics are discussed do formally --------------------For more details, see IEEE-SA Standards Board Operations Manual, clause 5.3.10 andAntitrust and Competition Policy: What You Need to Know rust.pdfSlide #3

Patent-related informationThe patent policy and the procedures used to execute that policy aredocumented in the: IEEE-SA Standards Board bylaws/sect6-7.html#6) IEEE-SA Standards Board Operations opman/sect6.html#6.3)Material about the patent policy is available rials.htmlIf you have questions, contact the IEEE-SAStandards Board Patent CommitteeAdministrator at patcom@ieee.orgSlide #4

IEEE SA COPYRIGHT POLICYNOVEMBER 2019

INSTRUCTIONS FOR CHAIRS OFSTANDARDS DEVELOPMENT ACTIVITIESAt the beginning of each standards development meeting the chair or a designee is to: Show the following slides (or provide them beforehand) Advise the standards development group participants that: IEEE SA’s copyright policy is described in Clause 7 of the IEEE SA Standards Board Bylaws and Clause 6.1 of theIEEE SA Standards Board Operations Manual; Any material submitted during standards development, whether verbal, recorded, or in written form, is aContribution and shall comply with the IEEE SA Copyright Policy; Instruct the Secretary to record in the minutes of the relevant meeting: That the foregoing information was provided and that the copyright slides were shown (or providedbeforehand).16

IEEE SA COPYRIGHT POLICYBy participating in this activity, you agree to comply with the IEEE Code of Ethics, all applicablelaws, and all IEEE policies and procedures including, but not limited to, the IEEE SA CopyrightPolicy. Previously Published material (copyright assertion indicated) shall not be presented/submitted to the WorkingGroup nor incorporated into a Working Group draft unless permission is granted. Prior to presentation or submission, you shall notify the Working Group Chair of previously Published materialand should assist the Chair in obtaining copyright permission acceptable to IEEE SA. For material that is not previously Published, IEEE is automatically granted a license to use any material that ispresented or submitted.17

IEEE SA COPYRIGHT POLICY The IEEE SA Copyright Policy is described in the IEEE SA Standards Board Bylawsand IEEE SA Standards Board Operations Manual﹣IEEE SA Copyright Policy, seeClause 7 of the IEEE SA Standards Board laws/sect6-7.html#7Clause 6.1 of the IEEE SA Standards Board Operations man/sect6.html IEEE SA Copyright missionltrs.zip IEEE SA Copyright tml/ IEEE SA Best Practices for IEEE Standards licies/best practices for ieee standards development 051215.pdf Distribution of Draft Standards (see 6.1.3 of the SASB Operations s/opman/sect6.html18

Audio and Video Recording PolicyPublic written transcriptions PolicyIn order to allow the free exchange of ideas,audio and video recording of this meeting isprohibited.Except for personal use or internal companyuse, detailed written transcriptions of theproceedings are also prohibited from beingpublishedP1584.1 WG Meeting 2020 ESW Reno, NV19

8. SA Process and MyProjectsite updatePat RoderP1584.1 WG Meeting 2020 ESW Reno, NV20

9. IEEE P1584.1Subgroup ReportTony ParsonsP1584.1 WG Meeting 2020 ESW Reno, NV21

IEEE Standard Classification IEEE standards are classified as: Standards: documents with mandatory requirements. Mandatory requirements are generally characterized by use of the verb“shall,” whereas recommended practices normally use the word “should” Recommended practices: documents in which procedures andpositions preferred by the IEEE are presented. Guides: documents in which alternative approaches to good practiceare suggested but no clear-cut recommendations are made. 1584. 1 is a Guide22

1584.1 PAR Details Title: Guide for the Specifications of Scope and Deliverable Requirementsfor an Arc-Flash Hazard Calculation Study in Accordance with IEEE Std.1584 Scope: This standard provides guidance for the specification andperformance of an arc-flash hazard study, in accordance with the processdefined in IEEE 1584, Guide for Performing Arc-Flash Hazard Calculations.It provides the minimum scope and deliverable for an arc-flash study. Purpose: The purpose of this standard is to enable stakeholders tounderstand the minimum scope of work and deliverables required for anarc-flash study. Stakeholders are responsible for personnel in facilities andinstallations with electrical energy as a potential hazard to employees andother personnel. Stakeholders include but are not limited to employers,facility owners, operators, and contractors as well as those who areresponsible for the specification or the performance of a study.23

Revision Principles (1) 1584.1 WG authorized the Subgroup to revise the document based on the discussion atthe WG Meeting in Jacksonville (2019 ESW), and in accordance with the approved scopeof the PAR Focus on minimum information required to conduct an Arc Flash study and theassociated deliverables Other docs address short-circuit studies and coordination studies – no need to reinvent thatguidance Take a narrow view of “deliverables” and what we say about them Arc-flash labels are a typical “deliverable” – but they’re covered in NFPA 70E, not IEEE 1584 Another example: one-line diagrams Be consistent with IEEE 1584-2018 Don’t duplicate text/requirements in IEEE 1584-2018 It’s already there Duplication leaves the possibility that the documents get “out of sync” Possible exception: definitions

Revision Principles (2) Technical information needed to perform an incident energy analysisshould be in IEEE 1584 and not IEEE 1584.1 Example: determining specific electrode configuration(s) for a piece ofequipment There is already specific guidance in 1584. Assumption: all equipment is properly installed, operated, andmaintained in accordance with its listings, ratings, manufacturer’sinstructions, etc. To do otherwise opens up too many avenues to get distracted from the Scope There’s already a similar statement in 1584.1-2013 Recommendations for PPE are not a part of 1584.1

Team 1 – Scope & System Address issues around high-levelScope of Work, as well as“system level” data – e.g., utilityinfo and/or Modes of Operation Clause 3 – Arc-flash studygeneral guidelines Clause 4 – Complexity of System Some input to Clause 5 (DataCollection), Annex B (TaskMatrix) Arunkumar AravamudhanPatrick BaughmanGeorge ColeThomas DomitrovichMike FarrellWalter Gonzalez – team editorKen JonesGreg PagelloDavid Rewitzer – subgroup Secretary26

Team 2 - Site Address gathering/verifying dataon the site itself. Componentnameplate data, impact ofassumptions. New inputs? Clauses 5-8, Annex B 5 – Data Collection6 – Short-Circuit study7 – Coordination study8 – Arc-flash hazard locationconsiderations Steve AdamsTerry BeckerDaniel DoanRyan DowneyRobert FuhrLloyd GordonMike LangSteve ParkZarheer Jooma – team editor27

Team 3 - Study Address what is needed withrespect to the deliverables. Whatis an adequate level ofdocumentation to provide in thestudy report? Clause 9 – Equipment Labels (goesaway) Clause 10 – Report, results, andrecommendations Annex C – Equipment label(Other documents address this) Annex D – Deliverables for arc-flashstudy Jim Babcock – team editorKen ChengPaul DobrowskyMark FisherBill GnanJason JonasAlbert MarroquinAdam Reeves28

Current State Completed Draft 2 Incorporated comments based on Subgroup review of D1 Input from Pat Roder, Editorial help from Lisa Perry (IEEE) Much progress in terms of cleanup, consistency in terminology, and overallstructure and content of standard Final structure: 1 – Overview2 – Normative References3 – Definitions4 – Arc-flash analysis General Guidelines5 – System Scenarios and Configurations29

Current State (cont.) Final structure: 6 – Data Collection 7 – *Short-Circuit Study 8 – *Protective Device Coordination Study* Consult other IEEE or IEC standards for these studies 9 – Location Considerations 10 – Report, results Annex A: Arc-flash analysis scope of work considerations Annex B: Task Matrix of work items for arc-flash hazard analysis Annex C: Deliverables for arc-flash study Annex D: Bib

should be in IEEE 1584 and not IEEE 1584.1 Example: determining specific electrode configuration(s) for a piece of equipment There is already specific guidance in 1584. Assumption: all equipment is properly installed, operated, and maintained in accordance with its