1 / 43

AN OVERVIEW ON BEING A STANDARDS COMMITTEE CHUCK PIEPER NOVEMBER 2008 CODE WEEK

AN OVERVIEW ON BEING A STANDARDS COMMITTEE CHUCK PIEPER NOVEMBER 2008 CODE WEEK. 2. GUIDING DOCUMENTS FOR THIS PRESENTATION. Revision 13 of ANSI approved procedures* Your Supplement Other BPV practices (Admin Guidelines) * Current status: approved by CBO of BOD.

gaston
Download Presentation

AN OVERVIEW ON BEING A STANDARDS COMMITTEE CHUCK PIEPER NOVEMBER 2008 CODE WEEK

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AN OVERVIEW ON BEING A STANDARDS COMMITTEECHUCK PIEPER NOVEMBER 2008 CODE WEEK 2

  2. GUIDING DOCUMENTS FOR THIS PRESENTATION • Revision 13 of ANSI approved procedures* • Your Supplement • Other BPV practices (Admin Guidelines) *Current status: approved by CBO of BOD

  3. REALIGNED BOILER CODE ORGANIZATION • BPV standards committees (BPVSC) • Technical Oversight Management Committee (TOMC) • BPV Administrative Committee (BPVAC)

  4. TOMC • Reports to and advises BNCS and BPTCS in assuring that BPV Code remains state of the art and appropriately consistent. • Current BPV members invited to serve. Future appointments by Boards. • BPVSC chairs or their alternates are ex-officio members. • No limit on maximum number of members.

  5. TOMC DUTIES • Review and comment on BPV actions. • Advise on strategic issues and R&D. • Supervise SC-D, SC-SVR and other similar groups that may be established in the future. • Maintain Foreword of the Code • Provide other input requested by the Boards.

  6. BPVAC • Members are Chairs of the 10 BPVSC’s and the TOMC • Addresses admin issues affecting all BPVSC’s and their relationship with each other. • Meeting times and locations • Polices and procedures • Publishing issues • Honors and awards

  7. BPVSC DEFINITIONS • Standards Committee = Members + Delegates • Consensus Committee = Members • Alternate = Person appointed to serve in place of a member or delegate for an extended period • Representative = Someone sitting in for a member at a meeting

  8. BPVSC DUTIES • Maintain your section of the BPV Code in accordance with approved procedures. • Provide interpretations. • Vote on personnel and administrative items. • Hold hearings in response to appeals.

  9. BPVSC APPOINTMENTS • Members, Delegates, and Alternates are recommended by the consensus committee and appointed by the supervisory board. (Term = 5 years) • Representatives may be seated if accepted by the Standards Committee Chair.

  10. BALANCE OF INTEREST • Only applies to Consensus Committee. • No more than 1/3rd of Members from any Interest Category. • Interest Categories must be approved by the supervisory board. • No more than one member from any organization except under special circumstances (maximum = 2).

  11. DUTIES OF BPVSC MEMBERS • To thoroughly consider & vote on all actions for your section. • When requested, to review and to comment as needed on actions before other BPVSC’s. • To contribute your expertise. • To advise on personnel appointments. • To address other administrative items relative to operation of your committee.

  12. ADHERANCE TO ASME C&S POLICIES Members and their Alternates or Representatives of Standards Committees, subordinate groups, and project teams shall comply with society policies P-15.7, ethics; P-15.8, conflicts of interest; and P-14.6, society name, seal, emblem, initials, titles, identification, and certificates.

  13. OFFICERS OF BPVSC • Chair and Vice Chair elected by Consensus Committee & confirmed by Supervisory Board for a term of 3 years (maximum of 2 terms). • Nominations by weighted ballot method from among those both eligible and willing to serve. • Secretary appointed by C&S Directorate.

  14. SUBORDINATE GROUPS • Start off with current groups • Possible reorganization in the future. • New groups established by vote of the Consensus Committee. • Members appointed by Consensus Committee per supplement.

  15. SUBORDINATE GROUPS • Members of groups reporting directly to BPVSC’s nominate and elect their own Chair and Vice Chair subject to confirmation by the Consensus Committee (3 year terms; 2 terms maximum) Supplement will need to be revised. • Chair and Vice Chair of lower tier groups appointed by Consensus Committee (5 year term).

  16. ACTIONS AND VOTES • Types of actions • Technical revisions • Editorial revisions • Personnel, admin, or related to policy or ASME position • Types of votes • Approved • Disapproved • Abstention • Not voting

  17. TECHNICAL & EDITORIAL REVISIONS DEFINITIONS First consideration vote: a recorded vote by the Standards Committee & review and comment by: • Other affected Standards Committees • Conference Committee • Marine Conference Group • International Interest Review Group • TOMC • Supervisory Board (BPTCS or BNCS) • The general public (via the ASME website)

  18. TECHNICAL & EDITORIAL REVISIONS DEFINITIONS • Second consideration vote: A recorded vote by the Consensus Committee after first consideration negatives and substantive comments are addressed. • Recorded vote: A vote recorded in C&S connect.

  19. APPROVAL REQUIREMENTS • First consideration: (1) No negatives from Standards Committee and no substantive comments from others; and (2) 2/3’s of the Consensus Committee votes approved. • Second consideration: (1) No more than 3 negatives from consensus committee; and (2) 2/3’s of the Consensus Committee votes approved.

  20. PROJECT TEAM ACTIONS AFTER FIRST CONSIDERATION VOTE • Provide responses with no change to the action. • Make editorial changes to action & submit for second consideration. • Make technical changes and resubmit for first consideration. • Withdraw action. Note: A TOMC Member can record response to project team’s response to his comment.

  21. SECOND CONSIDERATION VOTE • Not needed if all negatives and comments are withdrawn. • May be taken at a meeting with 2 week period afterward for final vote. • Must occur no later than 2 meetings after the first consideration ballot closes.

  22. PERSONNEL, ADMINISTRATIVE, OR RELATED TO POLICY OR ASME POSITION • Approval requirements: • Majority vote of the Consensus Committee, or • Majority vote of the Consensus Committee Members at the meeting provided a quorum (50%) is present (at the Chair’s discretion).

  23. INTERPRETATIONS • Special Committee: No Objection of proposed wording by all Members required • Consensus Committee: No Objection of proposed wording by 3/4 of Members voting but no less than 2/3 of entire committee required

  24. OTHER RESOURCES • C&S Training Modules

  25. COMMITTEE ACTIONS:THE CARDINAL RULE • Your committee only has a consensus vote if the action results in changes to either your Section of the Code or your Code Case.

  26. ACTIONS TO BE DISCUSSED • Changes only your Section or Code Case • Changes to multiple Sections (except new/revised Code Case involving multiple Sections) • Code Case applicable to more than one Section • Actions in transition on February 1, 2009

  27. CHANGES ONLY IN YOUR BOOK OR CODE CASE • Action sent to other affected committees and/or one of their subordinate committees for review and comment during 1st consideration ballot. • Substantive comments are treated the same as substantive comments from Conference Committee, TOMC and Board members, i.e. require a written response.

  28. CHANGES ONLY IN YOUR BOOK OR CODE CASE Examples: • Revision to allowable stresses in Section II Part D. • Revision to the notes in stress tables in Section II Part D. • Adoption of a Section III Code Case for a new material.

  29. CHANGES ONLY IN YOUR BOOK OR CODE CASE More examples: • Revision to Section IX that significantly affects construction Section. • Significant exception by construction section to a requirement in Section V.

  30. CHANGES ONLY IN YOUR BOOK OR CODE CASE Some unsolicited advice: “If you have any question as to whether a particular committee should have the chance to review and comment, include them in the process.”

  31. CHANGES IN MULTIPLE SECTIONS (EXCEPT NEW OR REVISED CODE CASES TO MORE THAN ONE SECTION) • Requires or desires simultaneous changes to more than one section. • Examples include: incorporation of a material code case or updating a reference to another standard (e.g. SNT-TC-1A).

  32. CHANGES IN MULTIPLE SECTIONS (EXCEPT NEW OR REVISED CODE CASES TO MORE THAN ONE SECTION) • Each Committee Consensus votes part of action going into its Section and other involved Committees review and comment. • Project team should have representatives from all affected committees.

  33. CHANGES IN MULTIPLE SECTIONS (EXCEPT NEW OR REVISED CODE CASES TO MORE THAN ONE SECTION) • Each Section has its own tracking number. • Tracking numbers are linked. • TPM keeps track of linked items. • C&S Connect warns if publication is attempted prior to approval of all linked actions. • Simultaneous voting not necessary.

  34. CODE CASE APPLICABLE TO MORE THAN ONE SECTION • Applies to adoption of new Case or revision of existing Case. • Only one record number required. • Project Team should include all affected committees.

  35. CODE CASE APPLICABLE TO MORE THAN ONE SECTION • Should be consensus voted simultaneously. • Each affected committee must meet consensus requirements.

  36. CODE CASE APPLICABLE TO MORE THAN ONE SECTION Bottom line: Better to have one Case rather than two even if separate references for the different Sections are required. Having one tracking number ensures nothing proceeds to publication until all affected committees vote.

  37. ACTIONS IN TRANSITION Applies to: • Actions that are placed on BPV Standards Committee ballot for 1st consideration after November Code Week and receive negatives or substantive comments. • Actions from ballot after August Code Week having negatives or substantial comments that are not addressed at the November Code Week

  38. ACTIONS IN TRANSITION Also applies to • Actions that have received a Board Procedural Objection or have not proceeded to publication for some other reason (e.g. Public Review Objection).

  39. ACTIONS IN TRANSITION • Assign new tracking number linked to old number. • Old number is closed. • Address negatives and comments. • Submit to affected Committee(s) for first consideration vote or review and comment, as applicable, and process according to new procedures and practices.

  40. ACTIONS IN TRANSITION Bottom line: If the action is published in the 2010 Edition or later, it must receive consensus approval from the new Standards Committees.

  41. QUESTIONS AND DISCUSSION 42

More Related