Software Model Versioning effect of EA

[KellyL]

Can someone tell me the advantages and disadvantages of creating software models with only the major version. I want to know how does that affect the enterprise architecture TPM and TRM if a software model contains multiple discovery models with different life cycles. 

[mikesisson]

Then how do you get software models installed on desktops traversed up to TPM.  I thought there was a way to utilize the discovery model.  We have SAM PRO not sure if that plays in.  I'm coming up to speed on knowledge of the Product Model table and its visibility and use across the platform.  Appreciate your insight.  Trying to ingest this documentation and translate to see if the service mapping is truly needed.  For the tables listed in the above documentation is that assuming the use of service mapping?

Thanks.

[Mathew Hillyard]

Hi @Mike,

You need some way of populating the tech stack from Business Application to the Application CI. You don't need Service Mapping but you need some way of building out that stack, and you need something to populate software (and for completeness, hardware) product lifecycles - you have SAM Pro, which of course works for the software portion. 

So, in your case, so long as you are populating the tech stack you should be able to switch on (I believe the "Populate TPM Discovered Technologies and Lifecycles" scheduled job is already active, at least it is in my PDI) and use TPM.

Of course, if you're not already populating the tech stack, then you'll need to evaluate the most suitable option for doing so for your use case - which could be Tag-based or Calculated App Services, but may well be Service Mapping.

I hope this helps!

Mat

[meganfisher]

What if the software products are typical desktop products such as Visio, SnagIt etc that aren't going to be associated to a business application and really are just end-user applications. We wouldn't need to do any kind of service mapping for those correct? I understand the need for Service mapping for your business applications and their software components but not sure on the end-user desktop products that are not a component of a business application.

[mikesisson]

@meganfisher Thanks for bringing back to the problem where we are trying to identify standards for desktop software.   @mcastoe @Mathew Hillyard does EAW, TRM or TPM look into the Software installed on Desktops for any standard or to identify software that is installed on desktops that are non standard?

[Mathew Hillyard]

Hi @mikesisson 

EA looks after infrastructure software standards, which is what EAs (as in Enterprise Architects) would be responsible for. In addition, CSDM Services (where there is an app in scope) should always have a Business Application; however a Business Application is explicitly not  desktop software as per the CSDM white paper.

Desktop software versioning is usually the responsibility of End User Compute. I believe SAM contains options for approved vs non-approved desktop software versions - for example: https://www.servicenow.com/community/sam-blog/understanding-restricted-software-ensuring-compliance-...

This is where I would expect management of desktop software, including versioning, to be managed.

I hope this helps!

Mat