<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Mappalink — Blog</title><description>Notes from the floor: root causes, integrations and the data model underneath mixed robot fleets.</description><link>https://website.mappalink.com/</link><language>en</language><item><title>One model across five brands</title><link>https://website.mappalink.com/blog/one-model-across-five-brands/</link><guid isPermaLink="true">https://website.mappalink.com/blog/one-model-across-five-brands/</guid><description>Every vendor names the same event differently. Unifying that vocabulary is unglamorous, and it is the whole job.</description><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><category>data</category><category>root cause</category><author>Senne Van Baelen</author></item><item><title>Why a stop needs a cause</title><link>https://website.mappalink.com/blog/why-a-stop-needs-a-cause/</link><guid isPermaLink="true">https://website.mappalink.com/blog/why-a-stop-needs-a-cause/</guid><description>Fleet software tells you a robot halted. It rarely tells you why, and the difference is what a shift costs.</description><pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate><category>root cause</category><category>operations</category><author>Senne Van Baelen</author></item></channel></rss>