API Publication Types From “API Document Format and Style Manual” and “Procedures for Standards Development” the following are “standards” 1. Bulletin.

Slides:

Advertisements

Similar presentations

ASTM OFFICERS CONFERENCE SUBCOMMITTEE CHAIRMENS DUTIES AND RESPONSIBILITIES.

Advertisements

ASTM Officers Training Workshop Subcommittee Chairmens Duties And Responsibilities September 11-12, 2006 Joe KouryChristi Sierk.

Ensuring that building products meet code requirements ICC Evaluation Service, Inc. The ICC-ES Evaluation Committee conducts open public hearings on proposed.

NACE Direct Assessment Standards Office of Pipeline Safety (OPS) Public Meeting November 4, 2003.

THE STANDARDS DEVELOPMENT PROCESS STEP 1 PUBLIC AND COMMITTEE PROPOSAL STAGE PUBLIC AND COMMITTEE PROPOSAL CLOSING DATE FIRST TECHNICAL COMMITTEE MEETING.

SC8 Liaison Report API SC8 – Subcommittee on Drilling Structures & Equipment Chair: Robert Urbanowski Vice-Chair: Mark Trevithick.

Standards and Certification Training Module B – Process B5Consensus Process for Standards Development ASME S&C Training Module B5 Consensus Process for.

Overview of the IEEE-SA Process Maintenance of IEEE standards Soo H. Kim, Program Manager, Technical Program Development NPEC Subcommittee SC-3 Jan 24,

2015 Exploration & Production Winter Standards Meeting SC10 & SC13 Updates January 27-29, 2015 Intercontinental Hotel New Orleans, LA.

Cover graphic should fill and not exceed the defined grey box. June 14 th, 2012 Gary Devlin API SC 18 – Quality Product Life Cycle TG7.

Ontario Overview Dave Short Senior Regulatory Analyst, Regulatory Affairs IESO’s ERO Workshop – June 28, 2006.

Click to add title SABS STANDARDS DIVISION Standards Development Natural Science.

Committee on Refinery Equipment November 2010 Update to the Refining Subcommittee Michael Lubcyik, Chevron Energy & Technology Company, Chair, CRE.

Slide 1 IEEE 802 Response to FDIS comments on IEEE 802.1AS 20 March 2014 Authors: NameCompanyPhone .

OVERVIEW OF ENGINEERING MANUAL, Part 1 Susan Hoyler TIA, Director Standards Development and Promotion.

CIS Training October Subcommittee Structure n The Voting membership is composed of Standards Committee members and non- Standards Committee Members.

SC18 TG5 Development of a Guidance Document for the implementation of API Specification Q2 Objective Create a guidance document for users of the API Specification.

Operational Excellence Quality and Customer Experience Operational Excellence Quality and Customer Experience SC-18 Liaison Report TG-3: Definition of.

WG or TG # SC17 Liaison Report Mohsen Shavandi / Virgilio Garcia Soulé SC17 Liaisons Update from SC18 Summer 2013 Meeting January 2014.

Operational Excellence Quality and Customer Experience Operational Excellence Quality and Customer Experience SC18 Liaison report for SC6 Rick Faircloth.

Subcommittee on Oil Well Cements (SC10) Wednesday June 18 th, 2014: General Meeting  Publication of API Specification 10A “Cements and Materials for Well.

San Francisco, CA. SC8 Liaison Report

Operational Excellence Quality and Customer Experience Operational Excellence Quality and Customer Experience Product Lifecycle Management.

The IEEE-SA Standards Process Dr. Bilel Jamoussi IEEE Standards Education Committee.

Update of API Standards for Supply Chain Management API Standard 20J – Qualification of Distributors.

Operational Excellence Quality and Customer Experience Operational Excellence Quality and Customer Experience SC18 Liaison report for SC6 Rick Faircloth.

Doc.: IEEE /161r0 Submission January 2004 Al Petrick, IceFyre Semiconductor Slide WG Technical Editor’s Report January 2004 Interim Meeting.

External Provider Control

API 19 CI Chemical Injection Devices for Downhole Applications

API 19 CI Chemical Injection Devices for Downhole Applications

CIS Training November 2016.

Task Group API 19SS Sand Screens

Sponsor Ballot Process

API SC19 HPHT Template (Proposed as SC19TR1)

Definitions and Generic Procedures

Attestation Concept additional explanation and implementation proposal

Accredited Standards Committee C63® - EMC

Prepared by Rand E Winters, Jr. ASR Senior Auditor October 2014

API SC 10, Work Group 3 Update:

Global Industry Services

UNIT V QUALITY SYSTEMS.

API SPRING MEETING May , 2016 Chicago, IL

Task Group API 19SS Sand Screens

2017 Amendments to the INCITS Organization, Policies and Procedures

Submission Title: [Task Group 4 Low Rate WPANS Closing Report]

Submission Title: [Task Group 4 Low Rate WPANS Closing Report]

Submission Title: [Task Group 4 Low Rate WPANS Closing Report]

The Standards Development Process

Setting Actuarial Standards

Standards Development: An Overview

IEEE P Motions at the July Plenary EC Meeting

Paul Boase, Chair, Transport Canada Jill Collins, CSA Val Todd, CCMTA

Specification on float equipment

TGp Closing Report Date: Authors: July 2005 Month Year

IEC Maintenance Committee Report

API SC 10, Work Group 3 Update:

TVWS Coexistence Study Group Extension Request

Interpretations and Code Cases

Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [A Brief Overview of Draft Approval.

Staff Report SEMICON Taiwan 2012

PROCEDURE FOR ANNUAL CORPORATE MEETING

API SC 10 WG15 Stage Cementing Collars

Author’s Name Company Address Phone Oliver Holland

IEEE P Motions at the July Plenary EC Meeting

TG 1 November Session Opening Report

OIE’s standard setting process

DRAFT ISO Revision Overview Quality management systems — Guidelines for the application of ISO 9001 in local government ISO/TC176 TG 01.

IEEE P Motions at the July Plenary EC Meeting

2018 Exploration & Production Winter Standards Meeting Subcommittee 10

Presentation transcript:

API Publication Types From “API Document Format and Style Manual” and “Procedures for Standards Development” the following are “standards” 1. Bulletin and Technical Report: Technical information on a topic generally issued on a one-time basis. Not a standard and is not addressed by the API Procedures for Standards Development requirements. 2. Code: A document intended for adoption by regulatory agencies or authorities having jurisdiction. 3. Recommended Practice: A document that communicates recognized industry practices. Recommended practices (RPs) may include both mandatory and non-mandatory requirements. 4. Specification: Documents that are written in such a way as to facilitate communications between purchasers, manufacturers, and/or service suppliers. Specifications may include datasheets that may be used in industrial transactions. 5 Standard: Standards typically include elements of specifications and recommended practices. 6. Draft Standards: A document that has been developed under these Procedures and is distributed for additional comment. Most draft standards are not published; however, with the approval of the appropriate committee, draft standards may be published for a specified period of time to obtain more widespread circulation to interested parties.

API Document Format and Style Manual See http://mycommittees.api.org/standards/copm/Meeting%20Materials/2015/COPM%20presentation%20%20-%20API%20Style%20Guide%20Spring%202015.pdf

API Document Format and Style Manual (normative means required – informative means useful)

API Publication Development Process Both API Standards Meetings and Standards Developments is governed by: Procedures for Standards Development API FIFTH EDITION, APRIL 2016 ALL SC13 OFFICERS AND TG CHAIRMEN SHOULD BE FAMILIAR WITH AND COMPLY WITH THIS DOCUMENT (Quorum, meeting minutes, voting records etc)

SC13 API Publications Work Flow process (part 2)

Publications are required to be maintained under one of these options Revision with changes after the required 5 year review from publication date Can have one 2 year extension without ballot (7 yr from date of publication) Reaffirmation (balloted with no changes to document) gives 5 more years from date of reaffirmation ballot vote After an Edition published and reaffirmed (unchanged document in effect for 10 years) then the next review & ballot can be extended to be a maximum of 10 years after the reaffirmation publication date – rarely allowed Withdrawal (ballot) Under 1 & 2 any publication that is not revised, reaffirmed, or withdrawn by SC13 ballot at the end of a maximum 7 years will be withdrawn by API NOTE: Technical Reports do not require a SC Ballot although not required SC has adopted a 5 year review