Digital feature: The standards development process, part 3: Approval, publication and maintenance
This is the final article in our three-part series exploring the American Petroleum Institute’s (API's) standards development process. World Oil (WO) recently spoke with Paula Watkins (PW), Senior Director of Standards Development at API, to gain insights into the intricacies of that process, the role of collaboration and the challenges along the way.
Part 1 covered the preliminary steps for project approval and committee formation. Part 2 focused on the drafting and consensus-building phase. In this final article, we turn our attention to the final stages of this process: the approval, publication and ongoing maintenance of a standard.
REACHING CONSENSUS
WO: What is required for a standard to achieve consensus?
PW: First, consensus is not the same as unanimity. However, consensus does require that the standard receives broad support from all stakeholder categories. These include operator-users of oil and natural companies, equipment and material manufacturers, service suppliers, with those that form the general interest category (e.g. consultants, government agencies, academia, and nongovernmental organizations).
For a ballot to be successful, at least a majority of the voters must return their ballots. Of those, at least two-thirds must vote to approve the standard. This requirement ensures that the standard reflects a balanced view and has gained substantial agreement among the voting members.
WO: How does API handle negative votes and comments?
PW: When a negative vote is cast, the voter must provide a reason. The committee carefully reviews all negative votes and comments and works to resolve them. Sometimes, this involves revising the draft or explaining why a comment can’t be accommodated. The goal is to address all significant concerns while still moving forward with a standard that represents a broad consensus. Sometimes several rounds of balloting and review are required to achieve consensus.
FINAL REVIEW AND EDITING
WO: What happens during the final review and editing phase?
PW: Once a consensus is achieved by the consensus body (voting group), the draft standard undergoes legal and editorial review. The draft is edited for clarity and formatted so that it conforms to API’s Style Guide: there are some fundamental parameters that are used to ensure conformity of style for all API standards. Any queries that the editor might have are referred back to the standards committee for resolution to ensure no inadvertent technical changes are made to the document.
PUBLICATION
WO: What is the process for publishing a new standard?
PW: After the standard’s legal review and editorial work are completed, API publishes it and makes it publicly available through its webstore [https://www.apiwebstore.org/] and authorized global distributors. The publication process may also include communication efforts, such as publication announcements and press releases, which notify relevant stakeholders. API may also publicize the standard’s publication through various communication and marketing channels, such as LinkedIn and trade press articles, and may also provide more information in podcasts and webinars.
IMPLEMENTATION
WO: How does API support the implementation of new standards?
PW: Implementation is a crucial phase where the standard is adopted and applied by industry and other stakeholders. API may provide training and education sessions as well as other tools to aid effective implementation of the new standard. Examples:
- API Training: https://www.api.org/products-and-services/training
- Pipeline Safety Management Systems (SMS): https://pipelinesms.org/
MAINTENANCE
WO: What role does API play in the ongoing maintenance of standards?
PW: Once a standard is published, it is reviewed at a minimum every five years by the responsible standards committee. If the committee determines that no updates are required, the standard is balloted for reaffirmation. If reaffirmed, that date is added to the cover of the standard. However, periodic updates may be needed for the standard – note that API Spec 5L is on its 46th edition!
WO: How are existing standards revised?
PW: Limited substantive changes can be made by issuing an addendum to the standard. These supplements have to be balloted and approved by the relevant standards committee.
When a revision of the entire document is necessary, it follows a process similar to how a new standard is developed. That begins with identifying the need for a revision in a project proposal, followed by drafting, review and balloting. API solicits input from the industry and other stakeholders to ensure that the updated standard continues to serve its intended purpose effectively and meets the needs of the different interests.
Updates to API’s standards can be made through these different mechanisms, ensuring that the standards constantly evolve to meet the needs of the different standards users.
