<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:blog="http://dnn-connect.org/blog/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Blog - Midstream</title>
    <link>https://www.vericorr.com/Insights/term/69/locale/en-US/Blog-Midstream</link>
    <description />
    <pubDate>Sat, 05 Sep 2026 00:17:37 GMT</pubDate>
    <lastBuildDate>Sat, 05 Sep 2026 00:17:37 GMT</lastBuildDate>
    <category>Midstream</category>
    <generator>DotNetNuke Blog RSS Generator Version 0.0.1.0</generator>
    <ttl>30</ttl>
    <atom:link href="https://www.vericorr.com/DesktopModules/Blog/API/RSS/Get?moduleid=463&amp;tabid=39&amp;term=69" rel="self" type="application/rss+xml" />
    <item>
      <title>A Prudent Path for the Pipeline Integrity Asset Class</title>
      <link>https://www.vericorr.com/Insights/Post/241/A-Prudent-Path-for-the-Pipeline-Integrity-Asset-Class</link>
      <description>&lt;blockquote&gt;
&lt;p dir="ltr"&gt;IBM&amp;#39;s end of base support for Maximo 7.6.1.x reopened the question of where pipeline integrity data belongs. What each path preserves, and what it does not.&lt;/p&gt;
&lt;/blockquote&gt;
</description>
      <category>asset integrity</category>
      <category>EAM Carve-Out</category>
      <category>Integrity Intelligence</category>
      <category>Maximo Migration</category>
      <category>Midstream</category>
      <category>Pipeline Integrity</category>
      <guid isPermaLink="true">https://www.vericorr.com/Insights/Post/241/A-Prudent-Path-for-the-Pipeline-Integrity-Asset-Class</guid>
      <pubDate>Thu, 13 Aug 2026 18:11:00 GMT</pubDate>
      <media:thumbnail width="144" height="96" url="https://www.vericorr.com:443/DesktopModules/Blog/BlogImage.ashx?TabId=39&amp;ModuleId=463&amp;Blog=1&amp;Post=241&amp;w=144&amp;h=96&amp;c=1&amp;key=fff415d9-2207-4e97-8781-26ba2fd35c34" />
      <blog:publishedon>2026-08-13 18:11:00Z</blog:publishedon>
    </item>
  </channel>
</rss>