Stuff you should do in ServiceNow before installing AssetTrack

AssetTrack works best when you have set up ServiceNow Hardware Asset Management properly. Consider the following to determine if you're ready for AssetTrack for ServiceNow.  

  • A Data Dictionary is created that lists all necessary data fields so stakeholders know where specific data will be stored. This ensure business users, administrators, and AMI are playing to the same sheet of music.
  • Hardware reports are spec’d out (if not already built). This way we can confirm we have all required data fields accounted for and managed.
  • Model Categories established with Asset and CI classes set so that:
    • Discovery doesn’t add VMs into your alm_hardware table
    • Cmdb records are created in the correct table when Hardware is added
  • Models are populated and clean so that:
    • AssetTrack has known models to reconcile assets against
    • Your asset reporting meets stakeholder requirements
  • The Location table is clean and meets reporting requirements.  It isn't overly complicated, has no duplicates, and is easy for your users to navigate.
  • Discovery is configured to match existing Hardware assets by serial number, and doesn’t create duplicate assets in the Hardware table.
  • Advanced Shipping Notice imports are automated.  This is optional, but if you got ‘em, you should get em imported to make receiving far easier on your staff.

AssetTrack is pretty tolerant and can handle improperly configured ServiceNow. However, by laying the right foundation, you can get so much more value for your money.

AMI provides consulting to assist with the items above.  Contact to learn more.

Have more questions? Submit a request


Please sign in to leave a comment.