ASME PTB-12-2017 pdf download.Guidelines for Addressing Data Gaps and Recordkeeping for ASME B31.4, B31.8 and B31.8S for Pipeline Integrity Management.
3 COMPANY PIPELINE INFORMATION DATABASE It is recommended that each operator maintain a chief source of pipeline system information, so they can make auditable, repeatable, and trustworthy decisions such as those needed for fitness-for-service calculations and risk assessments. The authors of this guideline recommend a practice of maintaining digital source records directly linked to specific pipeline components within an operator’s GIS. This recommendation is based on a philosophy of providing the operator’s Decision Makers easier access to the source records. This system might not fit every operator’s system. There may be some operators that can provide their Decision Makers ready access to all source records in a way that can be as efficient as directly linking the source records within GIS. This could be the case for a very small operator where records are always immediately retrievable for the entire system (and where it may not be practical to invest in the required network infrastructure and software considering the benefit). This section describes guidance on how to create a company pipeline information database with digital source records linked within GIS. The guidance below is drawn from the authors’ and the industry’s experience working with pipeline system materials records in the past half-decade to calculate design pressures as part of verifying MAOP. In many cases, the philosophies provided in this guidance could be extended beyond materials and applied to other data types as well (e.g., SCADA, soil resistivity/moisture levels). The Work Flow Process Diagram in Section 3.3 summarizes the process described. If an operator elects not to maintain this type of database, there may be many parts of this section that will not apply. However, as long as the operator maintains a chief source of pipeline system information (e.g., master alignment sheets) most of the guidance in subsequent sections will apply. This operator must know that when the authors reference the “company pipeline information database.
3.1 Locations and Formats of Pertinent Data The first steps in preparing a database of digital source records are to identify the types of records that are expected to be included and imported in the records database and to identify the locations of these records during a “pertinent data search,” so they can be organized for import systematically. A key step in this process is recognizing which records are, or are not, pertinent or relevant. This, and other key steps, should maximize the value (amount of information identified as pertinent) relative to the effort required to retrieve and review records. When identifying records that are expected to be imported and included, an operator should target locations of records that are essential to material properties verification. The locations may be buildings that serve as maintenance hubs or offices that belonged to a primary project manager (or project management team) for construction projects. The locations may also include record storage locations (either vendor or company owned). The search team should research how the records have been stored and transferred through the history of the organization. Some key events that impact record locations are mergers and acquisitions (both of companies and of assets), closing offices down, or moving branch offices or headquarters.ASME PTB-12 pdf download.