Voted Best Answer
Jan 24, 2019 - 03:20 AM
* Document what's in scope and more importantly what is excluded.
* Clarify the business driver for tracking the asset, if no one really cares don;t waste effort tracking. e.g. tracking keyboards or even monitors.
* High level information you will track per asset type. Keep this to a minimum or it will not get updated.
* Asset tagging strategy (I recommend using the device serial number)
* Reconciliation and Audit policy. WIthout this your asset register will get stale and become useless
* Stores Strategy. Where assets are managed when not deployed
The HAM Policy is critical and needs to be agreed early as it dictates the scope and budget later.
* If it's one person and you don't refresh the list often a spreadsheet on SharePoint might be ok.
There are lots of low cost Asset Registers. SNIPE-IT is opensource or hosted, AssetPanda is more functionali, an online database like database like KNACK or Zoho you can build your own.
* Reports can be done by exporting to excel.
* You need to draw up a 1 pager to start for the key processes (JML,, Stores, Lost/ STolen and Disposal)
* Have a look at SAMCharters processes which have been reviewed on ITAMreview for more details
You are going to have to collect this from various sources (SCCM, scans, Finance, etc). Key here is to have the longest list possible. You can always reduce the Active list down over time. Keep in mind that data in an asset register never gets deleted, just marked as Disposed or Lost (Stolen)
Maintaining an asset register will take time so make sure you schedule it in (or a team member). You also need to ensure you have the tasks documented, a monthly reconciliation in place and KPIs. Other wise it will go stale.