Business application form

  • Release version: Australia
  • Updated March 12, 2026
  • 6 minutes to read

    • Enterprise Architecture helps system admins add any business application to assess and track its costs, usage, business value, functional fitment, and risks.

    Business Application Form fields

    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 for which the application is used.
    Portfolio Name of the portfolio to which the application belongs.

    This field appears when you install the PPM Standard (com.snc.financial_planning_pmo) plugin.
    Application type Type of application. This field indicates whether the application is custom or commercial.
    • Homegrown: Application that is built in-house.
    • Commercial off-the-shelf (COTS): Application is a commercial application purchased from another company.
    • SaaS: Application is a cloud application managed by 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 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 with 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 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

    Auditing is enabled. Thus, whenever a user updates the value in this field, the Activities field in 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.
    Life-Cycle Stage Status Status of the 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 using the applications.

    Auditing is enabled. Thus, whenever a user updates the record in this field, the Activities field in the Activities tab displays the update.
    Active user count Number of active users out of the overall user base. Auditing is enabled for the field.
    Last change applied date Date on which the application was last updated. Auditing is enabled for the 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 is entered in the Installed field.
    Retired Date when the business application is going to be retired.
    Monitor Select the check box to track the status and performance of the business application.
    Description Unique description of the application.

    You can also elaborate or shorten the content in this field using Now Assist. For details, see Elaborate or shorten content in form fields.
    Model ID Product model ID of the business application.
    Table 1. 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 2. Planned Disposition section form fields
    Field Description
    Planned Disposition Planned disposition of a business application. Use the following options:
    • Invest-Business Application is targeted for additional investment. Useful especially once you bring SPM into the fold to drive decision making on demands, projects, and programs.
    • Sustain-Business Application is slated for continued operation, but investment is only at a level to keep it operational. No new growth plans targeted for it at this time.
    • Migrate-Business Application has been targeted for migration off it, based on strategic or other decisions. Users or stakeholders are migrated to a new or different application providing same or similar capabilities. Sometimes precedes Retire, but may also be used for Business Applications migrating from on-prem to cloud or vice a versa.
    • Retire-Business Application is due to retire. Users have either already migrated off the application, or business is divesting out of capabilities it provides, with no replacement planned.
    Migration Strategy Migration strategy for the business application. This field appears only when Migrate is selected from the Planned Disposition field. Use the following options:
    • Rehost-Typical lift & shift – moving the application as-is to a new host.
    • Replatform-Similar to lift & shift, but also involves minor changes of apps to optimize use of cloud or on-prem or hybrid capabilities.
    • Repurchase-Also known as drop and shop. Generally used for migration to cloud while abandoning classic licenses and repurchasing cloud-based licenses.
    • Refactor-Re-architecting the app as part of the migration process. Significant changes planned to it.
    Target Business Application Name of the business application for which you’re adding the planned disposition. This field appears only when Migrate is selected from the Planned Disposition field.
    Reasoning Reason for the planned disposition decision.

    You can also generate, elaborate, or shorten the content in this field using Now Assist. For details, see Elaborate or shorten content in form fields.
    Table 3. Owners section form fields
    Field Description
    Portfolio manager Owner of the portfolio, typically from IT.

    This field appears when you install the PPM Standard plugin (com.snc.financial_planning_pmo).
    Business owner Person who owns the application from the business side. Every application should have an assigned business owner.
    Managed by

    User responsible for overall management of the business application, including maintenance, upgrades, and lifecycle decisions.
    Managed by group

    Group responsible for overall management of the business application, including maintenance, upgrades, and lifecycle decisions.
    IT Application owner Person who owns the application from the IT side.

    The business application must have an owner assigned to it.

    If you’re designated as the IT Application owner, then you can view all the applications for which you’re the owner in the My Applications menu.
    Last updated by Person who last updated the application record.
    Supported by

    User responsible for providing day‑to‑day support for the business application.
    Support group

    Group responsible for providing day‑to‑day support for the business application, such as incident resolution and user assistance.

    For example, for a HR application where employees raise access or usability issues, the HR IT Support group is selected as the support group.
    Table 4. Compliance section form fields
    Field Description
    Business criticality How critical the application is to the business. Auditing is enabled for the 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.

    Auditing is enabled for the field.
    Certified Status of the application that it meets requirements or complies with the policies of your organization.
    Table 5. Activities section form fields
    Field Description
    Work notes Work notes entered by you.