Skip to content

Reports

A report is organized, detailed information of a project, hosts, and processes which includes executive summary, about customer, discovery findings, host classifications, complexity calculations, technology stacks, application distributions, topology, and node information available to you.

Types of Reports

CHAI™ provides two types of reports:

1. DART Report

DART (Discovery, Assessment and Rationalization Tool) report.

2. Practitioners Report

Practitioners are teams in the customer's IT organization that are responsible for working on initiatives that will deliver the modernization and/or application transformation, and they typically are people who are intimately familiar and passionate about the success of the transformation initiative. The information they seek and the value they derive from the practitioners report is much more detail about applications and the technical details.

Report Actions

You can perform multiple actions on reports such as editing the report and downloading a PDF copy of the report.

Prerequisite

Reports can only be generated when the discovery is complete. If this prerequisite is not met, Generate CXO Report and Generate Practitioner Report buttons are disabled.

Recommendations

Before you start, we recommend you complete the below actions to capture maximum data in the report:

  • X-ray
  • Host classification

View Report

  • CXO Report here
  • Practitioners Report here

Containerization Complexity

The final goal of the Discover and Transform stages is to build a container out of each OS process and its internal and external dependencies. The complexity of the containerization process, termed as containerization complexity, is calculated (High/Medium/Low) as follows. The process metadata and internal/external dependencies for process containerization are detected at the Discover stage and used for complexity calculations.

Overall complexity = Base complexity + Weighted average of the complexity of each specific parameter mentioned in recommendation report against each process

Example: 32-bit library/package dependency, hard coding of IP address detected

Base Complexity

The base complexity (High/Medium/Low) is influenced by:

  1. Choice of base container
  2. Adding the appropriate package dependencies for the process along with its versions and its availability for base container image
  3. Adding the process binaries selectively into the container at an appropriate location
  4. Adding the process env variables, port, start command and so on in order to get the process started in the container

Specific Parameter Complexity

For each specific parameter, the complexity (High/Medium/Low) is calculated based on the following criteria. This is purely based on CHAI™ containerization experience. Also, the efforts assumed are manual.

  1. The nature of work: Whether it is a single-line change or multi-line change. Whether it is standards-based change or application-specific change
  2. The efforts involved: Whether any R&D is involved to get it to work or enough documentation is available for making the change
  3. External dependency: Should the logic take path A or path B based on the external dependency. Example: on-premises database connection vs. local database connection
  4. Efforts beyond image creation: Changes needed in container runtime to make the container run in Kubernetes environment
  5. Application code changes if any: Changes required to make the container work in Kubernetes environment