<?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 - Pipeline Integrity</title>
    <link>https://www.vericorr.com/Insights/term/56/locale/en-US/Blog-Pipeline-Integrity</link>
    <description />
    <pubDate>Tue, 21 Jul 2026 21:41:11 GMT</pubDate>
    <lastBuildDate>Tue, 21 Jul 2026 21:41:11 GMT</lastBuildDate>
    <category>Pipeline Integrity</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=56" rel="self" type="application/rss+xml" />
    <item>
      <title>What Changed, and Why the Correlated View Is Now Ready</title>
      <link>https://www.vericorr.com/Insights/Post/239/What-Changed-and-Why-the-Correlated-View-Is-Now-Ready</link>
      <description>&lt;p&gt;&lt;/p&gt;</description>
      <category>asset integrity</category>
      <category>Cloud Compute</category>
      <category>correlated view</category>
      <category>Data Architecture</category>
      <category>Decision Support</category>
      <category>Pipeline Integrity</category>
      <guid isPermaLink="true">https://www.vericorr.com/Insights/Post/239/What-Changed-and-Why-the-Correlated-View-Is-Now-Ready</guid>
      <pubDate>Fri, 29 May 2026 17:53: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=239&amp;w=144&amp;h=96&amp;c=1&amp;key=49d1b2ab-9f8f-42fb-b93b-f85ed1761f03" />
      <blog:publishedon>2026-05-29 17:53:00Z</blog:publishedon>
    </item>
    <item>
      <title>Vendor Neutrality as an Architectural Commitment</title>
      <link>https://www.vericorr.com/Insights/Post/238/Vendor-Neutrality-as-an-Architectural-Commitment</link>
      <description>Vendor neutrality in pipeline software is often a marketing claim. In the VeriCorr architecture it is a structural constraint. Your CP database, ILI deliverables, SCADA historian, and GIS platform remain exactly where they are. The intelligence emerges from the alignment. This article explains what that means in practice and what happens to your data if you ever decide VeriCorr is no longer the right partner.</description>
      <category>asset integrity</category>
      <category>Corrosion Engineering</category>
      <category>CP</category>
      <category>GIS</category>
      <category>ILI</category>
      <category>Pipeline Integrity</category>
      <category>Platform Architecture</category>
      <category>SCADA</category>
      <category>Vendor Neutrality</category>
      <guid isPermaLink="true">https://www.vericorr.com/Insights/Post/238/Vendor-Neutrality-as-an-Architectural-Commitment</guid>
      <pubDate>Wed, 20 May 2026 14:57: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=238&amp;w=144&amp;h=96&amp;c=1&amp;key=0257f600-fe9a-4325-824e-f482eb12878c" />
      <blog:publishedon>2026-05-20 14:57:00Z</blog:publishedon>
    </item>
  </channel>
</rss>