<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02364nab a2200181   4500</leader>
  <controlfield tag="005">20260520001752.0</controlfield>
  <controlfield tag="008">260224s2010    xxu                      </controlfield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Potential benefits of data integration for pipeline integrity management programs</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">abr. 2010</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">14/06/2010 ; 10/06/2010</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">4 p. ; 17-20</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor. Pipeline integrity management programs are a requirement under Annex N of CSA Z662.07. Annex N requires that data from many sources and details be collected, integrated and analyzed on a continuous basis. The stated goal is to provide guidance for developing, documenting and implementing pipeline integrity management programs, which provide safe, environmentally responsible and reliable service(1). If executed properly, there should be improved pipeline integrity with measurable improvements and benefits. An important step in reaching this goal is risk assessment, which requires continuous data input to maintain valid integrity assessments. This dynamic process of data collection and integration enables continuous analysis and potentially leads to a more proactive integrity management system. The biggest problem for most operating companies in creating a dynamic and proactive integrity management program (IMP), compliant with Annex N, is in handling the significant data issues. Indeed, the data collection, integration and analysis are the most daunting tasks of the program. A software solution that accepts data from the many activities involved in the lifecycle of a pipeline system would be potentially beneficial. Application of integrated software tools in the oil and gas industry will result in improved integrity management, greater confidence in our pipeline infrastructure and economic benefits. We will review some of the data requirements of Annex N of CSA Z662.07 and identify the components of the program that may differ from your existing management plan. The nature and detail of data to be managed will be presented. Finally, we will provide an example of the role that software tools can play to assist in meeting the requirements of this challenging regulatory initiative.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">4</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Journal of Canadian Petroleum Technology</subfield>
    <subfield code="g">49</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Fehr, D.</subfield>
    <subfield code="9">42516</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">170903</subfield>
    <subfield code="d">170903</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">238722</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-05</subfield>
    <subfield code="j">200045759</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200045759</subfield>
    <subfield code="r">2026-03-05 15:13:16</subfield>
    <subfield code="w">2026-03-05</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
