Enterprise Architect - TPM

surya123
Mega Guru

Hi all,

I am working on enabling TPM for client.How I understand reading the documents is -

1. Service Item association table should be populated. 

2. Based on SW installs it creates TPM discovered technologies. Basically its the SW product whose lifecycle info is used to show when its associated with the Application service hardware. 

What I am struggling to understand is, we need to associate internal disposition with the SW and HW models. And I read that SW models arent used as part of TPM anymore. Should this be handled separately in SW and HW models ? How will client know which SW product is associated with whim SW and HW models and what is the inetrnal disposition against it? And do these internal disposition run anything or its just the SW product which we see on the TPM discovered technology and the lifecycle of taht product what affects the technology risk?

 

Thanks

Surya

2 REPLIES 2

yogesh41
ServiceNow Employee
ServiceNow Employee

Hi Surya

 

Below article will help you getting started with TPM 

 

Technology Portfolio Management - Getting Started... - ServiceNow Community

 

The "Example setup of a demo or proof of concept data set" section explains configuring TPM without Discovery or SAM/HAM Pro setup. 

 

Yogesh

Hi Yogesh,

 

Thank you for your reply. I have gone through the document but I have some queries, may be very basic but I am extremely confused here.

1> In The Technology lifecycle, I see Software product, Product model in the list view. The software products refer to sw_samp_product table and have lifecycle info. The Product model rather directs to Hardware model table. But SW product table refers to SW product and not SW model. 

2> If the HW and SW are normalized, then only we get the lifecycle info? If its not normalized, what the cons? we  see the TPM lifecycle info but without the obsolescence info ??

3> Each SW product can have multiple SW models? So, all the lifecycle info for all SW models is associated with the SW product? Meaning the SW product necessarily contains all the lifecycle info for all versions (SW models)? What about the HW product? I see its at Hw model level and lifecycle there itself. Unless I am completely wrong which I can be. HOw can I see HW lifecycles at product level? Does it even matter from TPM prespective?

4> In the video, it says that we can create the TRM products using a script. So, all the products HW and SW in TPM lifecycle as created, we will consider it to create TRM products? And the lifecycle of these product will have multiple versions of the product and the phases ? So, is it like at one point of time for a particular phase it will be approved and others wont be?

 

Thanks

Surya