Business context mapping

business unit and business service mapping with criticality the system allows users to manage information about business units, business services, and their criticality during the onboarding process in the application portfolio users can add, modify, or delete this information before final submission, but can't update it afterward, which may lead to inaccurate records outside of onboarding, users can view and manage business units, business services, and criticality mappings at any time, giving them control over the information feature capabilities view captured data the system makes it easy for users to display business units, services, and criticality values users can see all captured values on the business units and services page, providing a sense of ease and convenience add a business unit admin users can add and save a new business unit, which then appears in the list and is stored in the system modify an existing business unit a user can update and save details of an existing business unit changes will be reflected in the list and stored in the system delete a business unit an admin user with the appropriate permissions can delete a business unit, which removes it from both the list and the system add or update a business service with criticality mapping admin can add or modify a business service and assign a criticality value, which will be saved with the service assign priority order to criticality changing the priority for criticality values will save the order and apply it wherever criticality appears map business services to business units admin can map a business service to a business unit, and the mapping is saved and displayed correctly entity id and metadata enrichment a unique identification number has been assigned to each entity, facilitating consistent identification across bridge services this will enhance metadata management and integration across systems such as c2e, inventory, and devsecops a standardized identifier will address issues caused by varying source ids, ensuring accurate recognition and mapping of entities throughout the system these entities are managed by the application and business service portfolio as the kyndryl platform's system of record they use a universal identifier for cross app correlation, which may be stored for future reference entities include application deployment component (internal) business unit business service correlation covers lifecycle and update events entity created entity deleted entity updated the normalization process removes special characters and spaces, converting all text to lowercase roles viewer users with viewer roles can view both entityid and entitycrn fields (read only) on application or business service foundation entities entity id and entity crn are generated and maintained as system managed backend identifiers for all entities these identifiers are visible in the ui for applications, business services, and business units to support consistent identification and traceability for component entities, the entity id and entity crn are generated and stored in the backend for correlation and integration purposes but are not exposed in the user interface review and submit this is the final verification stage review the following information uploaded source files business unit assignments criticality mappings business service relationships if changes are required, users can return to previous stages using the stepper when complete, select submit outcome successful submission users are redirected to the application inventory dashboard, where onboarded applications become available for analysis and visualization submission failure the affected step is marked incomplete validation errors are displayed users can correct data and resubmit notifications notifications automatically dismiss after a few seconds users may see temporary system notifications such as manual upload required a required source file has not been uploaded processing previous upload the platform is processing a previously uploaded file getting help for assistance use the feedback panel available on every page create a support ticket from the page footer submit a service request from the validation screen for technical issues