<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Mainte Insights</title>
  <subtitle>Maintenance engineering, incident analysis and reliability research.</subtitle>
  <link href="https://mainte.ai/insights"/>
  <link rel="self" href="https://mainte.ai/insights/feed.xml"/>
  <id>https://mainte.ai/insights</id>
  <updated>2026-10-29T00:00:00+10:00</updated>
  <author><name>Mainte</name></author>
  <entry>
    <title>Completion, verification, authorisation: three decisions before a machine goes back to work</title>
    <link href="https://mainte.ai/insights/three-decisions-before-return-to-service"/>
    <id>https://mainte.ai/insights/three-decisions-before-return-to-service</id>
    <published>2026-10-29T00:00:00+10:00</published>
    <updated>2026-10-29T00:00:00+10:00</updated>
    <category term="Maintenance practice"/>
    <summary>A job marked complete, a machine that has been tested, and a machine someone has decided can be used are three different states. What each involves, who owns it, and what regulators keep finding after maintenance.</summary>
  </entry>
  <entry>
    <title>Downtime cost figures: which ones hold up</title>
    <link href="https://mainte.ai/insights/what-breakdowns-cost"/>
    <id>https://mainte.ai/insights/what-breakdowns-cost</id>
    <published>2026-10-29T00:00:00+10:00</published>
    <updated>2026-10-29T00:00:00+10:00</updated>
    <category term="Maintenance economics"/>
    <summary>The breakdown and downtime figures that get quoted, traced to their source and graded, and a practical way to work out what an hour of downtime costs on your own plant.</summary>
  </entry>
  <entry>
    <title>Lost maintenance history in four public inquiries</title>
    <link href="https://mainte.ai/insights/when-the-history-is-missing"/>
    <id>https://mainte.ai/insights/when-the-history-is-missing</id>
    <published>2026-10-29T00:00:00+10:00</published>
    <updated>2026-10-29T00:00:00+10:00</updated>
    <category term="Operational knowledge"/>
    <summary>Buncefield, Texas City, Piper Alpha and Havelock North: what investigators found about faults that were never logged, handovers that dropped the detail, and history that was forgotten.</summary>
  </entry>
  <entry>
    <title>What six incident reports say about defects that were already known</title>
    <link href="https://mainte.ai/insights/defects-found-not-fixed"/>
    <id>https://mainte.ai/insights/defects-found-not-fixed</id>
    <published>2026-10-29T00:00:00+10:00</published>
    <updated>2026-10-29T00:00:00+10:00</updated>
    <category term="Incident analysis"/>
    <summary>Australian regulator, court and coronial reports in which the defect had been noticed before anyone was hurt, and what each says about the steps between reporting a defect and dealing with it.</summary>
  </entry>
</feed>
