<?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</title>
    <link>https://www.vericorr.com/Insights/locale/en-US/Blog</link>
    <description />
    <pubDate>Thu, 28 May 2026 12:54:40 GMT</pubDate>
    <lastBuildDate>Thu, 28 May 2026 12:54:40 GMT</lastBuildDate>
    <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" rel="self" type="application/rss+xml" />
    <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>
    <item>
      <title>Adding an Intelligence Layer Without Disrupting the Workflow</title>
      <link>https://www.vericorr.com/Insights/Post/237/Adding-an-Intelligence-Layer-Without-Disrupting-the-Workflow</link>
      <description>The corrosion engineer's workflow does not need to change for VeriCorr to add value. The correlated view is built to support and enhance the judgment the engineer already brings, not to substitute for it.</description>
      <category>asset integrity</category>
      <category>correlated view</category>
      <category>Decision Support</category>
      <category>integrity engineering</category>
      <category>integrity workflow</category>
      <category>Pipeline Integrity</category>
      <guid isPermaLink="true">https://www.vericorr.com/Insights/Post/237/Adding-an-Intelligence-Layer-Without-Disrupting-the-Workflow</guid>
      <pubDate>Tue, 12 May 2026 17:18: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=237&amp;w=144&amp;h=96&amp;c=1&amp;key=baef71f0-883c-45ac-9988-a436f7993183" />
      <blog:publishedon>2026-05-12 17:18:00Z</blog:publishedon>
    </item>
    <item>
      <title>The Connection Problem Was the Hard Part</title>
      <link>https://www.vericorr.com/Insights/Post/224/The-Connection-Problem-Was-the-Hard-Part</link>
      <description>&lt;p&gt;Operators have known for two decades that integrity decisions live in the relationship between data sources, not inside any one of them. The connection problem itself was hard. VeriCorr&amp;#39;s architecture is the first to solve it in a form operators can use at the moment a decision needs to be made.&lt;/p&gt;
</description>
      <category>asset integrity</category>
      <category>correlated view</category>
      <category>data integration</category>
      <category>Decision Support</category>
      <category>integrity architecture</category>
      <category>Pipeline Integrity</category>
      <guid isPermaLink="true">https://www.vericorr.com/Insights/Post/224/The-Connection-Problem-Was-the-Hard-Part</guid>
      <pubDate>Fri, 01 May 2026 15:03: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=224&amp;w=144&amp;h=96&amp;c=1&amp;key=cc49cd5f-e6d2-4a6f-8db1-42e00d50ff60" />
      <blog:publishedon>2026-05-01 15:03:00Z</blog:publishedon>
    </item>
  </channel>
</rss>