It's not crystal clear in the documentation how this is achieved, but here's the basic version and how I understand it. It's best to read this with the documentation next to you:
https://docs.servicenow.com/bundle/rome-it-business-management/page/product/application-portfolio-management/task/associate-application-service-software-models.html
It makes the assumption you have Software Asset Management (SAM) pro installed with Application Portfolio Management (APM) and ITOM Discovery.
ITOM provides the discovery of the installed software on the operating systems, SAM provides the software & hardware models, the vendor lifecycles and the mappings between the two, APM provides the linking between the Application Services and the software models (this is what you need for the Technology lifecycle management dashboard).
If you don't have SAM pro or discovery, things get a little harder as you have to provide that data from somewhere else and/or map the software/hardware models to the application services manually.
If you have discovery and SAM pro up and running:
the doco might explain it better.
In the Business application (Business Applications view) there's a UI button "Manage Technology Models" in the header. This will take you to the application services (if you have them related) under the Business Application. Then you can right click each row and "Fetch Product Models". With SAM pro you can do both Hardware and Software & force a full check rather than just a delta. Without SAM Pro, you just get the hardware option.
After executing the "Fetch Product Models" action it'll query the related hosts in CMDB for their product models and give you a list of Retrieved software models (under the "Technology Models Retrieval view" for the application service).
You can then select which Retrieved Software Models you want to associate to the Application service in the TPM view and whether or not they contribute to the risk calculation (Ignore Technical Risk). I guess it's done this way as it'll find ALL software and as an application owner you're not really concerned with the version of the antivirus client versus the database that actually runs the application service. If you look at my example, I've only checked the Vault software model, not Symantec as i know that's the Symantec AV client.
If you have don't have discovery or SAM pro:
This becomes more time consuming as you have to at provide software models & the lifecycle data yourself & map each model yourself, you can't rely on the system to provide you with a discovered list to choose from, you have to know whats installed on your Application Service.
In this case you can go to the Application Service (and the "Application Service software models" related list) and directly add whatever software models you want by clicking the "New" button.
The data is stored in this table [sn_apm_tpm_service_software_model]
I hope this helps, it took me some work to sort all this out.
