1 / 23

API Standard Paragraphs

API Standard Paragraphs. Spring Meeting Orlando. API Std. Paragraphs Task Force Members. Don Kautz – Dow - Chairman Richard Lewis - Consultant Richards Thomas - Consultant Albert Kuo – Fluor Jim Bryant - KBR Glenn Grosso - DR Jim Hudson - GE Jim Lawson - Solar John Kocur - Exxon-Mobil

keon
Download Presentation

API Standard Paragraphs

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. APIStandard Paragraphs Spring Meeting Orlando

  2. API Std. ParagraphsTask Force Members • Don Kautz – Dow - Chairman • Richard Lewis - Consultant • Richards Thomas - Consultant • Albert Kuo – Fluor • Jim Bryant - KBR • Glenn Grosso - DR • Jim Hudson - GE • Jim Lawson - Solar • John Kocur- Exxon-Mobil • Peter Rainer – Rolls-Royce • Morg Bruck – Consultant • Clive Parsons - MMS • Bob Eisenmann - BP

  3. API Std. Para.Spring Meeting Orlando • Agenda • Std. Para. Work Process (JB) • Use of Recommendations (DT) • Guidelines for “Notes” (DT) • Use of “Unless Otherwise Specified” (JB) • Placement of Definitions (DK) • Coupling Guard Material (JB/MB) • Remote Witnessing of Shop Tests (DT)

  4. How Standard Paragraphs TF Operates • TF web meeting every other week • TF Publishes updates annually • Latest publication is available from the standard paragraphs folder in SOME SharePoint. • Also publish a version showing changes from previous publication.

  5. API Std. Para.Spring Meeting Orlando • Use of Recommendations • Text • Definitions • Notes

  6. API Std. Para.Spring Meeting Orlando • Guidelines for “Notes” Per API Document Format and Style Guide January 2009 • Notes after paragraphs cannot contain recommendations/requirements/instructions • Notes within tables cannot contain recommendations/requirements/instructions • Footnotes within tables may contain requirements

  7. API Std. Para.Spring Meeting Orlando • 6.7.5 Footnotes • Footnotes to the text give additional information; their use shall be kept to a minimum. A footnote shall not contain requirements or any information considered indispensable for the use of the document. Footnotes to tables and figures follow different rules

  8. API Std. Para.Spring Meeting Orlando • B.2.4 Notes to Tables • Notes in tables shall be treated independently from notes integrated in the text (see 6.7.2). They shall be located within the frame of the relevant table and shall precede table footnotes (see the following example). A single note in a table shall be preceded by “NOTE,” placed at the beginning of the first line of the text of the note. When several notes occur in the same table, they shall be designated “NOTE 1,” “NOTE 2,” “NOTE 3,” etc. A separate numbering sequence shall be used for each table. • Notes to tables shall not contain requirements or any information considered indispensable for the use of the document. Any requirements relating to the content of a table shall be given in the text, in a footnote to the table or as a paragraph within the table. It is not necessary that notes in tables are referenced in the body of the table.

  9. API Std. Para.Spring Meeting Orlando • B.2.5 Footnotes to Tables • Footnotes to tables shall be treated independently from footnotes to the text (see 6.7.5). They shall be located within the frame of the relevant table, and shall appear at the foot of the table (see the example in B.2.4). • Footnotes to tables shall be distinguished by superscript lowercase letters, beginning with “a.” The footnotes shall be referred to in the table by inserting the same superscript lowercase letter. • Footnotes to tables may contain requirements. (Refer to API 614 Table 1, 610)

  10. API Std. Para.Spring Meeting Orlando • EXAMPLE • Dimensions in millimeters • TypeLengthInside DiameterOutside Diameter • A l1 a d1 • Bl2d2 b c • A paragraph containing a requirement. • NOTE 1 Table note. • NOTE 2 Table note. • aTable footnote. • bTable footnote. • cTable footnote.

  11. API Std. Para.Spring Meeting Orlando

  12. API Std. Para.Spring Meeting Orlando • Use of “Unless Otherwise Specified” • API Style Guide Page 24: “Bullets appear when the wording “when specified,” “if specified,” or “the purchaser will specify” appears in the paragraph. A bullet is not required for “unless otherwise specified” or when a decision has been previously made and the phrase “when XXX has been specified” is used.”

  13. API Std. Para.Spring Meeting Orlando • SP R2014, 6.1.7 Discussion: The term "Unless otherwise specified" implies another alternative may be indicated by the purchaser. In most cases "Unless otherwise specified" has been introduced when a bullet has been eliminated.

  14. API Std. Para.Spring Meeting Orlando • Some History: • 20 to 25 years ago API standards made extensive use of BULLETS • API are minimum standards so bullets identified “enhancements” that one could consider • Left “API” equipment with broad ambiguity • Project Managers required justification for bullets • Leadership directed to minimize bullets • Since a higher default was “not a consensus”, unless otherwise specified was introduced

  15. API Std. Para.Spring Meeting Orlando • Why bother to have “Unless otherwise specified”? • In 1992, OSHA got more aggressive and issued the Process Safety Management Standard: The employer shall document that equipment complies with recognized and generally accepted good engineering practices (i.e., industry accepted standards such as API). • If not, the burden of proof for a safe design falls on the facility owner • “Unless otherwise specified” softens that burden when there is a reason to do “otherwise”.

  16. API Std. Para.Spring Meeting Orlando • Placement of Definitions and Symbols in Rotordynamics Section • Propose moving all definitions to beginning of section • Propose leaving symbols within section where used

  17. API Std. Para.Spring Meeting Orlando • Coupling Guard Material • Use of the term “Non-sparking” • Very few materials are truly Non-Sparking under all possible conditions • Std Para prefers the term “Spark Resistant” • Many users consider pure aluminum and aluminum alloys with a maximum content of 2 % magnesium or 0.2 % copper, all copper, and copper-based alloys (e.g. brass, bronze) to be spark-resistant. However, local standards, such as EN 13463-1, might not allow aluminum or non-metallic materials within potentially explosive atmospheres.

  18. API Std. Para.Spring Meeting Orlando Proposed new Section 7.3 Guards 7.3.1 All exposed shaft areas including between drivers and driven equipmentand the area between bearing housing and seal glands shall have a safety guard. 7.3.2 Unless otherwise specified, guards shall be supplied and mounted by the vendor with unit responsibility. 7.3.3 Each guard shall enclose the exposed rotating components to prevent personnel from contacting moving parts during operation of the equipment train. 7.3.4 Allowable access dimensions shall comply with specified standards, such as ISO 14120, EN 953 or ANSI/AMT B15.1 7.3.5 Guards be constructed of steel, brass, aluminum or non-metallic (polymer) materials, as suitable and be fabricated from sheet (solid or perforated), plate, or expanded metal. Coupling guards of woven wire shall not be used, but woven wire may be applicable for shaft areas between bearing housing and seal gland.

  19. API Std. Para.Spring Meeting Orlando New Section 7.3 Guards - continued ●7.3.6 If specified, guards shall be constructed of an agreed spark-resistant material. ●7.3.7 If specified for guards with potentially explosive atmospheres, an ignition hazard assessment (risk analysis) in accordance with EN 13463-1 shall be conducted and a suitable report provided. 7.3.8 In addition, guards for couplings shall meet the following requirements: a. be removable without disturbing the coupled elements; b. be constructed with sufficient stiffness (rigidity) to withstand a 900 N (200 lbf) static point load in any direction without the guard contacting moving parts. 7.3.9 In addition, guards for the area between bearing housing and seal gland shall meet the following requirements: • sufficiently vented to prevent the accumulation of seal emissions, liquid or vapor; • allow visual inspection of the seal “region” without removal of guard.

  20. API Std. Para.Spring Meeting Orlando New Section 7.3 Guards - continued ● 7.3.3.1 If specified, guards to allow for other customer requirements such as: • providing access for VOC emissions testing; • protection from environmental elements (for example rain, sand); • provide protection from directional spray in event of significant seal leakage; • special venting/draining arrangements. • Limit skin temperature of guard Any such options shall be explicitly stated by the purchaser.

  21. API Std. Para.Spring Meeting Orlando • Remote Witnessing of Shop Tests • With today’s technology should remote witnessing of shop tests be allowed? • Pros – Eliminate pre-test; reduce travel expense • Cons – Hands on experience; Union issues; Confidential Equipment

More Related