Applying APDM To Pipeline Integrity Management At Petrochina

By Yi Li, Xianjun Tan, Lijian Zhou, and Haichong Yu, PetroChina Pipeline R&D Center, Langfang, Hebei, China | March 2009 Vol. 236 No. 3

Although PODS describes in extensive detail the content and structure of a pipeline database, it also includes many items of content which are not in accordance with actual requirements of PetroChina, such as U.S. regulatory compliance. PODS ESRI Geodatabase was proposed in early 2007, but remains in its formative stages. What’s more, PetroChina engineers can be aware of actual requirements of PetroChina pipeline and can build the Geodatabase by using Case Tools. PetroChina PIM also needs to define the content and structure of its table according to its own requirements. APDM is the best choice for PetroChina based on the current situation.

APDM is not a “standard” in the traditional sense. It is a template that requires specific core classes to be implemented in a standardized fashion and intentionally designed to allow for extendibility. This provides operators with flexibility to customize their own requirements. Petrochina extends APDM published at ESRI’s Website according to its actual requirements of PIM and classifies related pipeline data into 11 parts such as Centerline, Cathodic Protection, Encroachment, Operation, Facility, Event Support, Inspection, History, SheetGen, Risk and Landbase. Figure 1 shows working procedure circulation and data flow circulation of PIM.

Working procedure circulation and data flow circulation of PIM.
Figure 1: Working procedure circulation and data flow circulation of PIM.

PetroChina's PIM software system based on APDM.
Figure 2 shows PetroChina’s PIM software system architecture based on APDM. As the PIM software system architecture shows, PetroChina develops a series of software units to implement PIM.

Application Of APDM

The second software layer includes data collection and data management software. Data collection is the basis of other work of PIM. The standards of data collection for PIM shall be determined once APDM is customized by PetroChina. It should be in accordance with enterprise related to data standards as much as possible to facilitate interoperability among other systems.

PetroChina’s historical pipeline data storage cannot satisfy the requirements of PIM. For example, data documented on paper including as-built sheets, operation records and inspection reports and preserved separately in subsidiary companies cannot satisfy PIM requirements.

APDM can integrate, organize and store these historical data into a Geodatabase to meet requirements of PIM, thus PetroChina needs software based on APDM to collect pipe data. PetroChina customizes its contents and standards of data according to requirements of PIM, and develops the data collection software. Figure 3 shows collection data by data import software. At the beginning of a project, a PIM Geodatabase needs to be built.

Subsidiary companies shall collect pipeline data by the data collection software and the template database with subsidiary companies’ pipeline centerline released by headquarters, and then submit the completed local Geodatabase to DBA in the headquarters. The pipeline data from the subsidiary companies is checked before being imported to the PIM Geodatabase.

Data collection software
Figure 3: Data collection software.

Data Management