What is the value of defining "platform host" Business Applications

[Tom Sienkiewicz]

Hello Everyone,

can anyone please help me see the value of defining the "platform host" type of Business Apps?

My understanding is that for EA/design, the "platform app" level is most critical since those are the ones used for TCO/Rationalization/Capability mapping?

It also does not seem necessary from operations perspective, since any platform-level task can be handled via App Service.

What value or usage do you see if you are currently using this setup?

Many thanks!

[shubhamseth]

@Tom Sienkiewicz 

Defining “Platform Host” type Business Applications in ServiceNow adds value by helping model technical platforms (e.g., middleware, OS, cloud services) that support multiple business apps.

While “Platform Apps” are used for TCO, capability mapping, and rationalization, “Platform Hosts” are key for:

• Service Mapping and accurate CMDB modeling
• Tracking shared dependencies
• Supporting ITOM, risk, and operations use cases
• Enabling impact analysis when the host platform affects multiple apps

It’s especially useful when apps share the same infrastructure or are deployed on common platforms like containers, app servers, or cloud PaaS services.

[Kelli Fellows]

When would you recommend creating a ServiceNow Business Application as a Platform Host then creating a Business Application for each module we have that are Platform applications versus just creating the module Business Applications and populating the Platform on those records as ServiceNow?  What is the benefit of having the platform business application record and how does it impact APM?

[Robert Campbell]

I think it would look like this.

[Mathew Hillyard]

Hi @Tom Sienkiewicz 

If you have Enterprise Architecture then you have various ways to identify app structures:

• Platform choice list
• Platform Host/Platform Application Architecture type
• Application Family reference

My preference is to use Platform Host/Platform App for known COTS platforms where you can clearly map out a single hierarchy below a known Host. ServiceNow is a good example - you can then decide either to have high level child Apps (e.g. ITSM, ITOM, SecOps) or go down to the operational applications (e.g. Incident, Problem, Change, Discovery, Security Incident). My recommendation is the second option as they're likely to have different (process) owners and potentially support.

Use Application Family where you need to express more of an Ecosystem of products - some SAP products can be like this, where the structure may be multi-layered and a regular Host/Application structure doesn't really work.

The other alternative is not to build any relationships and just identify Platform Business Applications with the Platform choice list. This works well if you don't want/need to show parent/child relationships.

In the end none of these choices affect logic within the platform - it's really just for comparing apps during app rationalisation in the Bubble Chart (or the List view) in EA Workspace. So ultimately it depends on how your organisation wants to report on apps when comparing them for rationalisation.

I hope this helps!
Mat

[Kelli Fellows]

Do you see Planview as a COTS platform?