Interpretations and Code Cases
Topics Covered Interpretations Intent Interpretations Code Cases
Interpretations: Routine and Always Acceptable Traditional Inquiries: A simple clarification or restatement of code requirements that may be considered vague, inconsistent or slightly difficult to apply. These interpretations do not amount to changes to the Code requirements, therefore a simplified approval process is permitted.
Intent Interpretations: Routine and Always Acceptable Intent Inquiries: Used when Code text does not adequately convey the intention of the Standards Committee. An intent interpretation provides a statement of the Standards Committee’s intent and simultaneously corrects the requirements to reflect the stated intent. As a result , Code requirements must be revised, therefore the full consensus process must be employed for approval.
Committee Process for Interpretations Assigned to subcommittee to develop a response Presented at an A17 Standards Committee meeting For Intent Interpretation both response and revision simultaneously presented and voted upon. Approved by A17 Standards Committee Requires 2/3 approval of members present at meeting
Receiving Inquiries Requests must be submitted through ASME website: go.asme.inquiry Staff reviews requests for interpretation for formatting and nature of questions If acceptable open a record and submit to the committee
Question and Reply Interpretations are written as a question about a requirement and then the answer The answer is in Yes/No format
Inquiries Typically Not Accommodated Consultation (“How do I…”?): ASME committees traditionally decline to provide technical consultation to code users on successful implementation of the Code. Is it NOT demonstrated that the Code rules are vague or inconsistent? Does the inquiry ask “why” (the philosophy or basis of the Code)?
Inquiries Typically Not Accommodated Training: ASME committees traditionally decline to address inquiries based solely on an inadequate understanding of the Code. There exists an opportunity for code users to improve their general understanding of ASME Codes through ASME’s Training and Development products.
Code Cases
Cases Cases represent alternatives or additions to existing rules Written in question and reply format Intended for incorporation into the next edition Typically requires a separate revision to be opened
Approval Process Ballot using the method described for technical revisions Requires ASME Public Review Cases may be used once Board Approved Do not require ANSI Approval