<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>The Manufacturing PLM blog</title>
    <link>https://manufacturing.co/plm/blog/</link>
    <description>Notes on product lifecycle management — configuration, the ERP seam, and AI in engineering data.</description>
    <language>en</language>
    <lastBuildDate>Fri, 21 Aug 2026 13:00:00 GMT</lastBuildDate>
    <atom:link href="https://manufacturing.co/plm/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Your bill of materials has no single answer</title>
      <link>https://manufacturing.co/plm/blog/bom-has-no-single-answer</link>
      <guid isPermaLink="true">https://manufacturing.co/plm/blog/bom-has-no-single-answer</guid>
      <description>A BOM is not a list. It is a question that returns different correct answers depending on the date, the configuration and the revision you asked about — and most integrations forget to ask.</description>
      <pubDate>Fri, 21 Aug 2026 13:00:00 GMT</pubDate>
      <category>Configuration management</category>
      <dc:creator>Samuel Edwards</dc:creator>
    </item>
    <item>
      <title>What an AI agent should not be allowed to do</title>
      <link>https://manufacturing.co/plm/blog/what-an-agent-should-not-do</link>
      <guid isPermaLink="true">https://manufacturing.co/plm/blog/what-an-agent-should-not-do</guid>
      <description>The interesting design question for AI in a PLM is not what the agents can do. It is what they are structurally prevented from doing, and why each limit is worth its cost.</description>
      <pubDate>Fri, 14 Aug 2026 13:00:00 GMT</pubDate>
      <category>AI in engineering</category>
      <dc:creator>Samuel Edwards</dc:creator>
    </item>
    <item>
      <title>The duplicate item nobody created on purpose</title>
      <link>https://manufacturing.co/plm/blog/the-duplicate-item-nobody-created</link>
      <guid isPermaLink="true">https://manufacturing.co/plm/blog/the-duplicate-item-nobody-created</guid>
      <description>Duplicate identity is the most expensive data condition a PLM can hold, and it is invisible by construction: both records are correct, nothing is malformed, and no validation fires.</description>
      <pubDate>Thu, 06 Aug 2026 13:00:00 GMT</pubDate>
      <category>Data quality</category>
      <dc:creator>Samuel Edwards</dc:creator>
    </item>
    <item>
      <title>Who owns the part number?</title>
      <link>https://manufacturing.co/plm/blog/who-owns-the-part-number</link>
      <guid isPermaLink="true">https://manufacturing.co/plm/blog/who-owns-the-part-number</guid>
      <description>Almost every failed PLM implementation fails at the same seam, and it is not a technical one. It is that nobody wrote down which system is the master before both started creating records.</description>
      <pubDate>Wed, 29 Jul 2026 13:00:00 GMT</pubDate>
      <category>PLM and ERP</category>
      <dc:creator>Samuel Edwards</dc:creator>
    </item>
    <item>
      <title>Approved is not effective</title>
      <link>https://manufacturing.co/plm/blog/approved-is-not-effective</link>
      <guid isPermaLink="true">https://manufacturing.co/plm/blog/approved-is-not-effective</guid>
      <description>A change has three dates and most systems record one. The gap between approval and effectivity is where nine weeks of obsolete material gets ordered by people acting in good faith.</description>
      <pubDate>Wed, 15 Jul 2026 13:00:00 GMT</pubDate>
      <category>Configuration management</category>
      <dc:creator>Samuel Edwards</dc:creator>
    </item>
  </channel>
</rss>
