Asset Schema for Software License Tracking

[Mathew Lederman]

Does anybody have a good Assets object schema they can share for tracking software and licenses? 

[Aaron Geister _Trundl_]

@Mathew Lederman 

I have build these before and there is many ways to organize and architect or design these. I would typically keep this flat with all the list of software you have available. Then add the attributes that are most likely to be used and stays constant across all software. I would also link reference to users that use that software. When someone is asking in a ticket for Jira it then adds them as a user of the software. This can be done as a reference. "

The idea is to create DNA map of how users are connect to data and how data is connect to other data or objects. 

Example 

Software	Attributes>>	License renewal date Date picker	Owner   Object - link to User	Service Relationship object	Status
Jira		1/1/26	John Doe	Atlassian	Active
Confluence		1/1/26	Jane Doe	Atlassian	Active
JSM		1/1/26	Pat Doe	Atlassian	Active
Loom		1/1/26	Pat Doe	Atlassian	Active

In the Software Catalog you could have software licensing table then have a software catalog of available licensing that lists what users could pick from.

If you create template ITSM asset scheme it will show you that the idea of adding say Laptops models available and then also which laptops are mapped to which users. This gives you idea of both inventory availability and what users are own which devices. 

You can have multiple top level objects or parent child. If you are using child then you can use inherency which can be helpful but must be static.

I don't have any templates available but you can use the template Atlassian provides.