<?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, 20 Oct 2026 09:50:44 GMT</pubDate>
    <lastBuildDate>Tue, 20 Oct 2026 09:50:44 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 Stays When the Senior Engineer Leaves</title>
      <link>https://www.vericorr.com/Insights/Post/240/What-Stays-When-the-Senior-Engineer-Leaves</link>
      <description>&lt;p&gt;The integrity discipline is losing senior engineers faster than it can replace them. What the platform captures is not their judgment but the case record their judgment was built on, held durably for the team.&lt;/p&gt;
</description>
      <category>Cathodic Protection</category>
      <category>Institutional Knowledge</category>
      <category>Integrity Management</category>
      <category>Pipeline Integrity</category>
      <category>Pipeline Intelligence</category>
      <guid isPermaLink="true">https://www.vericorr.com/Insights/Post/240/What-Stays-When-the-Senior-Engineer-Leaves</guid>
      <pubDate>Wed, 29 Jul 2026 22:39: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=240&amp;w=144&amp;h=96&amp;c=1&amp;key=522dff37-57af-4f04-b8be-6f99c0b3ec13" />
      <blog:publishedon>2026-07-29 22:39: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>