<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Asset Management on ESM Guide</title><link>https://esm-guide.com/en/tags/asset-management/</link><description>Recent content in Asset Management on ESM Guide</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://esm-guide.com/en/tags/asset-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Choosing an ITSM platform: the criteria grid</title><link>https://esm-guide.com/en/blog/choosing-an-itsm-platform/</link><pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate><guid>https://esm-guide.com/en/blog/choosing-an-itsm-platform/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt;&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Six criteria genuinely separate ITSM platforms, and functional richness is not among them.&lt;/li&gt;&#10;&lt;li&gt;On core processes, incident, request and change, every serious platform performs alike.&lt;/li&gt;&#10;&lt;li&gt;The billing unit, technician or end user, weighs more on five-year cost than any single feature.&lt;/li&gt;&#10;&lt;li&gt;The service catalogue is written before the consultation, not after: it is what makes demos comparable.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="what-to-settle-before-looking-at-any-tool"&gt;What to settle before looking at any tool&lt;/h2&gt;&#10;&lt;p&gt;Most tenders start with a feature grid sent to vendors. That is the reverse of the order that produces a good decision. Until scope is written down, every vendor answers on its own ground and the answers are not comparable.&lt;/p&gt;</description></item><item><title>Automated IT inventory: the methods compared</title><link>https://esm-guide.com/en/blog/automated-it-inventory/</link><pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate><guid>https://esm-guide.com/en/blog/automated-it-inventory/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt;&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Three collection methods coexist: agent, agentless, network discovery by scanning.&lt;/li&gt;&#10;&lt;li&gt;The agent returns the most complete software inventory and works outside the corporate network.&lt;/li&gt;&#10;&lt;li&gt;Network discovery is the only method that detects unmanageable equipment.&lt;/li&gt;&#10;&lt;li&gt;A real estate almost always combines all three, at different collection frequencies by device type.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="why-manual-inventory-does-not-hold"&gt;Why manual inventory does not hold&lt;/h2&gt;&#10;&lt;p&gt;An IT estate moves constantly: workstations replaced, software installed on user initiative, virtual machines created then forgotten. A manually maintained &lt;strong&gt;IT inventory&lt;/strong&gt; is wrong the day it is published. The question is therefore not whether to automate, but by which method.&lt;/p&gt;</description></item><item><title>CMDB: what it is for and how to feed it</title><link>https://esm-guide.com/en/blog/cmdb-explained/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><guid>https://esm-guide.com/en/blog/cmdb-explained/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt;&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;A CMDB records configuration items and, above all, the dependency relationships linking them.&lt;/li&gt;&#10;&lt;li&gt;Its primary use is impact analysis, before a change or during a major incident.&lt;/li&gt;&#10;&lt;li&gt;An inventory lists assets, a CMDB adds dependencies: they are two different objects.&lt;/li&gt;&#10;&lt;li&gt;Manual population always drifts: automated collection is the only sustainable option.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="what-a-cmdb-actually-contains"&gt;What a CMDB actually contains&lt;/h2&gt;&#10;&lt;p&gt;A &lt;strong&gt;CMDB&lt;/strong&gt;, for Configuration Management Database, records the configuration items of an information system: servers, workstations, applications, services, contracts. But the list is not the point. What separates a CMDB from a spreadsheet is the &lt;strong&gt;relationships&lt;/strong&gt; between those items: which server hosts which database, which database feeds which application, which application delivers which business service.&lt;/p&gt;</description></item></channel></rss>