This article describes a method to distinguish between different templates created for the various third party asset inventory tools and provides guidelines for identifying the source or origin of discovery data imported using the ServiceAide Asset Converter. Examples of the various sources or origins might include Microsoft Systems Management Server (SMS) 2003, Microsoft System Center Configuration Manager (SCCM) 2007, Altiris Inventory Solution, BMC Configuration Management (formerly Marimba), LANDesk Inventory Manager, Tivoli Asset Management or BDNA Insight. Within various tools, there is often more than one method used for software inventory. An example is Microsoft SCCM Add/Remove Programs or Asset Intelligence.
The source or origin of discovered assets is tracked by the ServiceAide ITCM/SCM Content Team and is also displayed in ServiceAide IT Client Manager and in ServiceAide Software Compliance Manager. Further, additional planned functionality in SwCM depends on the source or origin of asset inventory data. It is also important to identify the source of inventory data in a consistent manner.
These guidelines will also improve the quality and transparency of our integrations and the custom solutions/reports that we provide to our customers.
Identifying the Template
After you have built your template and you know that it works, you should add a number of identifications into the template to tell them apart.
Origin and Trust Level
Origin is the official method to distinguish discovery data sources.