Business application form

Using the business application form, you can add any business application to assess and track its costs, usage, business value, functional fitment, and risks.

Table 1. Business application form

Field	Description
Name	Name of the business application.
Number	A unique, auto-generated identification number with a configurable prefix for the business application record.
Business process	Business process that the application is used for.
Application type	Type of application. This field indicates whether the application is custom or commercial. Homegrown: The application is built in-house. End-user computing (EUC): The application is used by end users to perform their daily tasks. Commercial off-the-shelf (COTS): The application is a commercial application purchased from another company. SaaS: The application is a cloud application managed by a third-party vendor.
Publisher	Name of the application publisher.
Architecture type	Type of application architecture. 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 that are 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 host. In this case, the business application relies on the platform for standard operations such as development tools, execution services, and data services.
Platform host	A hardware or software that hosts the business application. This field is required if you select the Platform Application value in the Architecture type field.
Install type	Type of install. Use the following options: On Premise Cloud Hybrid Third Party Hosted
Platform	Applications hosted by platform.
Business unit	Business unit that is associated with the selected business application.
Department	Department that is associated with the selected business application.
Installed	Date and time when the application was installed.
Status	Operational status of the application. Use the following options: Implementing In Production Pilot Retired Under Evaluation Auditing is enabled for this field. Thus, whenever you update the value in this field, the Activities field on the Activities tab displays the update.
Life cycle stage	Life-cycle stage of the application. This field is auto-populated based on the value selected in the Status field. The data is fetched from the life-cycle mapping [life_cycle_mapping] table.
Application scoring profile	The profile used to calculate the application score for strategy.
Application category	The application purpose and function. Use this information to rationalize or consolidate applications.
Application family	A set of related applications that have a common platform or vendor.
Technology stack	Technology stack on which the application was built.
User base	Number of users that are using the applications. Auditing is enabled for this field. Thus, whenever you update the record in this field, the Activities field on the Activities tab displays the update.
Active user count	Number of active users out of the overall user base. Auditing is enabled for this field.
Last change applied date	Date on which the application was last updated. Auditing is enabled for this field.
Accessibility level	Accessibility level of the business application. Use the following options: A (lowest) AA (mid-range) AAA (highest)
Age in months	Age of the business application, in months. This field is auto-populated when the date and time are entered in the Installed field.
Description	Unique description of the application.
Model ID	Product model ID of the business application.

Table 2. Contract section form fields

Field	Description
Vendor	Vendor details of the application.
Support vendor	Vendor who currently supports the application.
Contract end date	Expiry date of the subscription contract or the support contract. Auditing is enabled for the field.

Table 3. Planned disposition section form fields

Field	Description
Planned disposition	Planned disposition of a business application. Use the following options: Invest Sustain Migrate Retire
Reasoning	Reason for the planned disposition decision.

Table 4. Owners section form fields

Field	Description
Business owner	Person who owns the application from the business side. Every application should have an assigned business owner.
Managed by	User managing the business application.
Managed by group	User group managing the business application.
IT application owner	Person who owns the application from the IT side. The business application must have an owner assigned to it.
Last updated by	Person who last updated the application record.
Supported by	User supporting the business application.
Support group	User group supporting the business application.

Table 5. Compliance section form fields

Field	Description
Business criticality	Determines how critical the application is to the business. Auditing is enabled for this field.
Emergency tier	Actions or plans executed for the application in an emergency situation.
Data classification	Security level for the data in the application. This attribute determines which Governance, Risk, and Compliance (GRC) policies are applicable to the application. Use the following options: Confidential Highly Sensitive Internal Public Auditing is enabled for the field.
Certified	Status of the application that meets your requirements or complies with the policies of your organization.

Table 6. Activities section form fields

Field	Description
Work notes	Work notes entered by you.

Related tasks

• Edit business application details