What actually is an "Application Model" ?

[markterringon]

Hello,

Does anyone know what is the actual definition of an "Application Model" within EA/ServiceNow?

There is a lot of documentation of how to add one to a Value Stream or create one from the "Product Model", but the documentation is really sparse on definitions.  This seems to be a pattern.

We have a lot of "Application Models" in our instance but I feel they are incorrect.  So do we have an SN definition of what an "Application Model" is, and have examples?

I have a link: Model form fields • Australia IT Asset Management • Docs | ServiceNow

Which provide a list of fields - so from this, it appears to be specific to the manufacturer of an application.  But this has confused me more as the example of the name is "Field Agent Laptop", and an associated field may be the Edition, such as "Professional".

What confuses me further  is why there is a link between a "Value Stream" and the "Application Model". 

Why ?

A Value Stream has stages, each stage will have a value proposition and an entrance and exit criteria.

That value stage will be supported by 3 levels of capabilities 1) Primary Capabilities, 2) Supporting Capabilities, and 3) Enabling Capabilities. 

Each Capability will provide Services that are underpinned by the business applications.   So if anything the Value Stream Stages should be linked to a Business Capability. 

So Why are Value Streams linked to Application Models, and What actually is an Application Model ?

Thanks for your help in advance.

Mark

[chinook2]

Me Too! 🙂
I "think" the secret lies in the Reference of Model ID from a Business application to the Application Model.
Documentation seems to indicate that multiple Business Applications can refer to a single Application Model (through a Model ID that points to the Application Model).

So - the Application Model could be used for a more "generic" and re-usable configuration to create like Business applications. And - then to minimize the work to change a common characteristic contained or specified in the Application Model.

I imagine (and have not done it yet) that in a Value Stream - this minimizes the work IF the Application can be referenced in the Value Stream along with the Business Processes - and not be convoluted by individual detail from each of the Business applications.

At one point - I thought I saw a reference to an Application Model being created for every new Business Application - but that (in current context) is NOT CORRECT - and not the case.

And... would seem like (in Ent Arch) if multiple BusApps were linked to the same Application Model, then the grouping key for the comparison of the Business apps is already in place (again - haven't done that yet).

Great topic - look forward to hearing if others use and have found value in the use.