Application Type values

[RichieP]

Hi All,

Looking for community input on something minor.

The default Application Type field has the following values

• COTS
• EUC
• Home Grown
• SaaS

Have folks added Open Source as an option where they have built something on top of an opensource platform with little to no custom modules/components on top, or categorised these as Home Grown and used the software components in the CMDB to explicitly call out when something is/is not open source?

My initial thought is if we have CoTS listed, fully contained Open Source applications should probably be called out at this level too?

Or have folks taken an entirely different approach?

Thanks

[DarinH]

This isn't a direct reply to the OP, but very related to replies as we're just starting our APM journey and trying to implement data elements as close to out-of-the-box as possible, and Application Type seems like a mess. The product documentation states that it's intended purpose is to distinguish between homegrown and commercial, but EUC is neither, and SaaS is generally redundant with COTS. I'm going to recommend that we limit the choices to Homegrown and Commercial for this field, and use other fields to distinguish between SaaS and Self-Hosted, maybe Install Type, and to distinguish between EUC and ???, maybe via Application Portfolios. I'd appreciate any feedback and examples of what you've done in your organizations. 

[MEBoatman]

We have 2 choices for Application Type: COTS and Homegrown. We are essentially differentiating between homegrown applications and all others. Yeah...COTS doesn't exactly fit every use case in the "all others" but it's working for us. We use Architecture type, Install type, and Platform to further distinguish.  EUC falls under "COTS" (unless we built it but that's super rare for us). 

[Justin Docken]

With regards to Architecture Type, the current OOB values are:

• Architecture Type:
  • Client Server: Application structure that divides tasks between the service providers and service requesters.
  • N-Tier: A multi-layered architecture where presentation, processing, and data management exist as physically separate layers.
  • Web-based: Applications accessed over a network connection.
  • Other: Any other type of architecture.
  • Platform Host: Hardware or software that hosts the business application.
  • Platform Application: Application that runs on a platform and can be associated to a Platform Host. In this case, the business application relies on the platform for standard operations such as development tools, execution services, and data services.

Which field do you recommend we utilize to indicate whether a particular business application follows a SaaS, PaaS, or IaaS model ... and many other " " aaS's as well (over 50 in fact!). Thank-you!

[Justin Docken]

• Install Type:
  • On Premise
  • Cloud
  • Hybrid
  • Third Party Hosted

I suppose we could modify Install Type to include SaaS, PaaS, IaaS, etc?

[DarinH]

I agree this is where SaaS should be represented, and likely what "Cloud" was meant to capture in the existing model. IMHO, with respect to Install Type, On Premise and IaaS are very similar. Other missing Install Types would be Client (desktop software), and PaaS / Platform Extension (i.e. low code environments provided by vendors like Salesforce, Workday, ServiceNow).