Account onboarding is the initial step in the application portfolio management process, enabling the visualization of application inventory and associated resources. This step is crucial for aligning with the common data model, standardazing the application inventory, and identifying opportunities for application modernization.
During onboarding, data is collected from each account, and Delivery Partner (DPs) must configure their data accordingly.
The onboarding phase begins with discovering applications and infrastructure from various sources, such as the CMDB (Configuration Management Database) system, Kyndryl Delivery Platform, and Application Performance Management tools. The system identifies various risks associated with running the application based on the End of Life (EOL) or End of Service (EOS) of underlying components and the urgency of remediation.
Applications are categorized into high, medium and low-risk zones. Risk analysis is based on the technology risk, application and business impact. The priority for application modernization is determined by application complexity, business criticality, and infrastructure size. The overall application migration effort is then analyzed with market-based estimation to project the total business opportunity value.
The onboarding phase aims to project the business opportunities within a client’s context. It involves three stages:
Data configuration files
Business information
Review and submit
Each of these stages is detailed in the subsequent sections.
Application Portfolio supports application data import from standard IT operational systems like ServiceNow CMDB, Dynatrace, and Integrated AIOps. You can use the
IT Operational System
or the
MOIA Standard Data Format
to add configuration files.
If you have custom reports extracted from various IT operational systems, tools like Knime or PowerBI can help translate the data into MOIA's standard format.
Once the data is uploaded and configured, several options become available, such as downloading the sample file, which provides sample file format instructions for IT Operational Systems. If you need assistance during onboarding, there is a ‘‘Need Help?’’ section with instructions. You can also access a guided tour video with instructions for uploading the configuration files.
In the onboarding stage, you are asked to enter specific parameters. Each section is detailed as follows:
Business Units:
A business unit delivers one or more business capabilities and produces goods or services, which have a certain degree of autonomy in decision-making. Enter the name of the business units in the provided box. The names will appear as tags and can be deleted if necessary. Examples include:
Banking
Retail
Healthcare
Life Science
Assign order to criticality:
Criticality is auto-populated from the input files but can be manually added if not defined earlier. Criticality can be sorted in ascending or descending order. This feature allows you to prioritize business services or add criticality values as needed. Example criticalities include:
Low
Medium
Medium High
High
Very High
Crown Jewel
Select or add Business Service(s) from the list:
Business services are derived from the input data files, and criticality will be automatically available in the drop-down menu. You can add a business service and map it to the criticality or search for business services using the search bar. This list also shows the business units mapped to each business service.
Workstream(s):
Add the workstreams defined in the enterprise for handling different application development and maintenance tasks. Each workstream will appear as a tag and can be deleted if not needed. Workstream refers to a distinct, manageable segment of work that is part of a larger project or program. Each workstream typically focuses on a specific area of functionality or a particular set of tasks and is often managed independently, although it remains aligned with the overall project objectives.
Application stakeholder emails:
Insert the email addresses of the stakeholders who need to be notified about the respective applications.
Review screen:
This final screen allows you to review all the configuration details, such as:
Stakeholders
Workstreams
Criticality Order
After confirming that all the information is correct, click
Submit
. If you need to make changes, click
Back
to return to the previous screen. Once submitted, you will see a message saying ‘‘Configuration is now in progress’’. You will receive an email once the configuration is complete. After completion, you will be redirected to the main dashboard, where you can view all your widgets, which are explained in further detail.