Application number: A unique number of the application.

Input field:

Text

box.

Application type: Application type refers to the classification of the application based on the application runtime environment.

Input field:

Single-select dropdown list.

Application group: Application group refers to a closely related group of applications providing the same business services. This field is defined via the application’s onboarding file.

Input field:

Single-select dropdown list.

Type of client: The client using the application is internal or external.

Input field:

Single-select dropdown list.

Internet facing: Field to capture if the application is internet facing or not.

Input field:

Radio button.

Is this a Crown Jewel application: Field to mark the application as business critical.

Input field:

Radio button.

Description: Field to identify the application’s functions and purpose.

Input field:

Text box.

Key Stakeholders: The stakeholders who are responsible for or have accountability for the application. The list of key stakeholders is listed under this field.

Input field:

Multi-select dropdown list.

Workstream.

Input field:

Multi-select dropdown list.

Workstream Lead.

Input field:

No selection, this field maps the workstream lead.

Technical Owner: The person responsible for overseeing the technical aspects of the application throughout its lifecycle.

Input field:

Multi-select dropdown list.

Business Group: A Business Group/Unit delivers one or more business capabilities and produces goods or services which has a certain degree of autonomy in decision-making.

Input field:

Single-select dropdown list.

Business Criticality: This defines the criticality of the application from a business perspective, based on the number of business services that directly or indirectly depend on it.

Input field:

Single-select dropdown list.

Business Services.

Input field:

Multi-select dropdown list.

Regulatory.

Input field:

Text box.

Data.

Input field:

Text box.

Data classification.

Input field:

Multi-select dropdown list.

Compliance issue.

Input field:

Text box.

Vulnerability issues.

Input field:

Text box.

Others.

Input field:

Text box.

Security.

Input field:

Text box.

Name:

Input field:

Text box.

Component type: A component type refers to a category or classification of a software component based on its functionality, role, or structure within an application. Components are modular parts of a system that encapsulate specific functionality and interact with other components to form a complete application.

Input field:

Single-select dropdown list.

Technology stack: A technology stack, or "Tech Stack", refers to the combination of programming languages, frameworks, libraries, tools, and technologies used to develop and run a software application. It includes both the front-end (client-side) and back-end (server-side) technologies and may also encompass other tools for testing, deployment, and maintenance.

Input field:

Single-select dropdown list.

Version: The version of the technology stack.

Input field:

Single-select dropdown list.

Description.

Input field:

Text box.

Environment Info:

Environment name: An application environment refers to the specific setup in which a software application is developed, tested, deployed, and run.
Input field:
Text box.
Environment URL: An environment URL is a specific web address (URL) that points to a particular environment where an application is hosted.
Input field:
Multi-line Text box.
Last deployed date: The latest date on which the application was deployed.
Input field:
Date picker.

Servers:

Server name.
Input field:
Text box.
Components: Components are an integral part of the application code, or any third-party code, framework, technology, or library which is required to run the application. It encapsulates either functional or technical tasks forming the application.
Input field:
Multi-select dropdown list.
Technical components
perform technology-specific tasks that are not dependent on any particular application. For example, a graphical user interface control would be considered a technical component.
Business components
encapsulate specific pieces of business functionality.

Availability:

Available From: Date from which the Application is available.
Input field:
Date picker.
Country: The Country in which the application is hosted.
Input field:
Single-select dropdown list.
RTO (in minutes): RTO, or Recovery Time Objective, is the maximum acceptable amount of time that a system, application, or process can be down after a failure or disaster before negatively impacting the business. It is a key metric in disaster recovery and business continuity planning.
Input field:
Text box.
RPO (in minutes): RPO, or Recovery Point Objective, is a critical metric in disaster recovery and business continuity planning. It defines the maximum acceptable amount of data loss measured in time. RPO determines the point in time to which data must be recovered after a disaster or failure.
Input field:
Text box.
Load balancer: Load balancing is a method used to distribute incoming network traffic across multiple servers to ensure no single server becomes overwhelmed, which enhances application availability and reliability.
Input field:
Radio button.
Load balanced by: How load balancing is done, or which methods or tools are used for load balancing.
Input field:
Text box.
Description: Field to consider any remarks.
Input field:
Text box.

Usage:

Target users: Target users of an application refer to the relationship between the users and the organization that develops or manages the application.
Input field:
Single-select dropdown list.
Accessed from (countries): Indicate the countries from which this application is accessed.
Input field:
Multi-select dropdown list.
Average usage: The average usage of an application refers to the typical amount of time or frequency with which users interact with the application.
Input field:
Single-select dropdown list.
Number of users: Indicate the total user range for the application.
Input field:
Single-select dropdown list.
Peak usage volume: Peak usage of an application refers to the periods when the application experiences the highest level of activity. It is measured based on the highest number of users actively using the application at the same time.
Input field:
Single-select dropdown list.
Peak usage time period – From (24-hour format).
Input field:
Number spinner.
Peak usage time period – To (24-hour format): Peak usage times refer to the specific times of day when user activity is at its highest.
Input field:
Number spinner.

Development & Release:

Development method: Development methods refer to the approaches and practices used to manage and guide software development, such as Waterfall and Agile.
Input field:
Single-select dropdown list.
Management tools: Management tools help teams and organizations plan, track, and manage their projects and workflows.
Input field:
Multi-select dropdown list.
App Development tools: Application development tools help developers design, build, test, and deploy software applications.
Input field:
Multi-select dropdown list.
Reason for release.
Input field:
Text box.
Release cycle: Release cycles refer to the phases through which a software product progresses from development to deployment and maintenance. They can vary based on the development methodology, the complexity of the project, and the organization's goals.
Input field:
Single-select dropdown list.

Deployment & Maintenance:

Deployment tools: Deployment tools help automate and manage the process of deploying software applications to various environments, such as development, staging, and production, such as Jenkins.
Input field:
Multi-select dropdown list.
Deployment process: The deployment process involves strategy and methods to move software from development to production.
Input field:
Single-select dropdown list.
Maintenance window: A maintenance window is a designated period during which scheduled maintenance activities are performed on systems, applications, or infrastructure. This time is planned to minimize disruption and ensure that updates, fixes, or enhancements can be applied effectively.
Input field:
Date picker.
Outage impact: Outage impact refers to the consequences and effects of an interruption in the availability of a service, system, or application.
Input field:
Single-select dropdown list.
Support: Different levels of application support coverage cater to varying needs based on factors like application criticality, user base, and organizational requirements.
Input field:
Single-select dropdown list.

Backup:

Capacity (GB): Backup in capacity refers to managing and planning the storage needs associated with backup processes. This involves ensuring adequate capacity to store backups and manage data efficiently.
Input field:
Number spinner.
Enabled: Backup enabled refers to the feature or functionality that allows systems, applications, or data to be backed up regularly to ensure data protection and recovery.
Input field:
Radio button.
Type: Backup type refers to different methods of creating and managing data backups.
Input field:
Single-select dropdown list.
Retention in days: Backup retention refers to the policies and practices for how long backup copies of data are kept before they are deleted or archived. Proper backup retention ensures you can access historical data for recovery and compliance purposes while managing storage resources efficiently.
Input field:
Number spinner.
Schedule: A backup schedule outlines when and how often backups are performed to ensure data protection and recovery. Effective backup scheduling is crucial for minimizing data loss and optimizing storage use.
Input field:
Single-select dropdown list.

Deployment Bundle:

Build version: Build version refers to a specific iteration or release of software. It typically includes a set of changes or updates from the previous version and is used to track and manage different states of the software throughout its development lifecycle.
Input field:
Text box.
Components version.
Input field:
Multi-select dropdown list.
Platform name: Platform name is the name given to a generic service that extends services by adding hosting capabilities. A platform is a service that can host other services by providing a mechanism to do that by exposing APIs. Platforms and services come together to form a product.
Input field:
Single-select dropdown list.
Platform type: Platform type refers to the category or nature of a computing environment or service that supports application development, deployment, and management.
Input field:
Single-select dropdown list.
Platform version: Platform version refers to a specific release or iteration of a platform, including its features, functionalities, and any updates or changes made since previous versions.
Input field:
Single-select dropdown list.
Platform service pack: Platform service pack refers to a collection of updates, patches, and fixes released for a specific platform version. These service packs are designed to improve the platform's stability, performance, and security by addressing known issues, adding minor enhancements, and sometimes including cumulative updates.
Input field:
Text box.
Platform patch level: A platform patch level refers to the specific update or incremental change applied to a platform to fix bugs, address security vulnerabilities, or make minor improvements. It indicates the platform's current state in terms of applied patches and updates beyond its initial release or main version.
Input field:
Text box.
Platform Admin: Platform Admin is an individual responsible for managing, configuring, and maintaining a platform.
Input field:
Single-select dropdown list.
Cluster deployment: Cluster deployment refers to the process of setting up and managing a group of interconnected servers or nodes that work together as a single system to provide high availability, scalability, and reliability for applications or services.
Input field:
Radio button.