Skip to the content
LeaplogicLeaplogic
  • Home
  • About Us
  • Contact
SIGN IN
  • Home
  • About Us
  • Contact

  • Getting Started
    • Before You Begin
    • Creating an Account
    • Logging into LeapLogic
    • Reset Password
    • Quick Tour of the Web Interface
    • LeapLogic in 15 minutes
      • Prerequisites
      • Step 1. Log into LeapLogic
      • Step 2. Create Assessment and Get Insights
      • Step 3. Create Transformation Pipeline and See Results
      • Step 4. Edit or Optimize the Transformed Code
      • Step 5: Complete the Transformation Lifecycle
  • Introduction to LeapLogic
    • Overview
    • High Level Architecture
    • Supported Legacy and Cloud Platforms
    • Key Features
  • Workload Assessment
    • Overview
    • Value Proposition
    • Creating Assessment
      • Prerequisites
      • Step 1. Provide Primary Inputs
        • Automation Coverage
      • Step 2. Add the Additional Inputs
        • Table Stat Extraction Steps
          • Teradata
          • Oracle
          • Netezza
      • Step 3. Update the Source Configuration
      • Step 4. Configure the Recommendation Settings
    • Assessment Listing
    • Understanding Insights and Recommendations
      • Volumetric Info
      • EDW
        • Oracle
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • Vertica
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • Snowflake
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • Azure Synapse
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • SQL Server
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • Teradata
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • Netezza
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • Google Big Query
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • Redshift
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • PostgreSQL
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • Duck DB
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • ClickHouse
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • Exasol
          • Highlights
          • Analysis
          • Optimization
          • Lineage
          • Recommendations
          • Downloadable Reports
        • DB2
          • Highlights
          • Analysis
          • Optimization
          • Recommendations
          • Lineage
          • Downloadable Reports
      • ETL
        • Informatica
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • Ab Initio
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • DataStage
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • Talend
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • SSIS
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • Informatica BDM
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • Oracle Data Integrator
          • Highlights
          • Analysis
          • Downloadable Reports
        • Pentaho
          • Highlights
          • Analysis
          • Downloadable Reports
        • Azure Data Factory
          • ARM Template
          • Highlights
          • Analysis
          • Downloadable Reports
        • Matillion
          • Highlights
          • Analysis
          • Downloadable Reports
        • SnapLogic
          • Highlights
          • Analysis
          • Downloadable Reports
      • Orchestration
        • AutoSys
          • Highlights
          • Analysis
          • Downloadable Reports
        • Control-M
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • SQL Server
          • Highlights
          • Analysis
      • BI
        • OBIEE
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • Tableau
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • IBM Cognos
          • Highlights
          • Analysis
          • Downloadable Reports
        • MicroStrategy
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • Power BI
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • SSRS
          • Highlights
          • Analysis
          • Downloadable Reports
        • SAP BO
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
        • WebFOCUS
          • Highlights
          • Analysis
          • Downloadable Reports
      • Analytics
        • SAS
          • Highlight
          • Analysis
          • Lineage
          • Downloadable Reports
        • Alteryx
          • Highlights
          • Analysis
          • Lineage
          • Downloadable Reports
      • Integrated Assessment (EDW, ETL, Orchestration, BI)
        • Highlights
        • Analysis
        • Optimization
        • Lineage
        • Recommendations
    • Managing Assessment Reports
      • Downloading Report
      • Input Report Utility
      • View Configuration
    • Complexity Calculation Logic
    • Key Benefits
    • Ad hoc Query
  • Metadata Management
    • Overview
    • Introduction to Data Catalog
      • Managing Data Catalog
        • Building Data Catalog
        • Insights to Data Catalog
        • Managing the Repository and Data Source
      • Creating Repository (Repo)
      • Creating Data Source
    • Tag Management
    • Key benefits
  • Batch Processing using Pipeline
    • Introduction
    • Designing Pipeline
      • How to create a pipeline
        • Configuring Migration Stage
          • Schema Optimization
        • Configuring Transformation Stage
          • On-premises to Cloud
          • Cloud-to-Cloud
          • LeapLogic Express
        • Configuring Validation Stage
          • Data Validation
            • Table
            • File
            • File and Table
            • Cell-by-cell validation
          • Query Validation
            • Query Validation (When Data is Available)
            • Query Validation (When Data is Not Available)
          • Schema Validation
        • Configuring Execution Stage
        • Configuring ETL Conversion Stage
          • Ab Initio
          • Informatica
          • Informatica BDM
          • Matillion
          • DataStage
          • SSIS
          • IICS
          • Talend
          • Oracle Data Integrator
          • Pentaho
          • SnapLogic
        • Configuring Mainframe Conversion Stage
          • Cobol
          • JCL
        • Configuring Orchestration Stage
          • AutoSys
          • Control-M
        • Configuring BI Conversion Stage
          • OBIEE to Power BI
          • OBIEE to AWS QuickSight
          • Tableau to Amazon QuickSight
          • Tableau to Power BI
          • Tableau to Superset
          • Tableau to Looker
          • IBM Cognos to Power BI
        • Configuring Analytics Conversion Stage
          • SAS
          • Alteryx
        • Configuring Script Conversion Stage
    • Key Features
      • How to schedule a pipeline
      • Configuring Parameters
  • Pipeline Reports
    • Overview of Pipeline Report
    • Pipeline Listing
    • Reports and Insights
      • Migration
      • Transformation
        • On-premises to Cloud
        • Cloud-to-Cloud
        • LeapLogic Express
      • Validation
        • Data
          • File
          • Table
          • File and Table
        • Query
          • Query Validation Report (When Data is Available)
          • Query Validation Report (When Data is not Available)
        • Schema
      • Execution
      • ETL
        • Ab Initio
        • Informatica
        • Informatica BDM
        • Matillion
        • DataStage
        • SSIS
        • IICS
        • Talend
        • Oracle Data Integrator
        • Pentaho
        • SnapLogic
      • Mainframe
        • Cobol
        • JCL
      • Orchestration
        • AutoSys
        • Control-M
      • BI
        • OBIEE to Power BI
        • OBIEE to Amazon QuickSight
        • Tableau to Amazon QuickSight
        • Tableau to Power BI
        • Tableau to Superset
        • Tableau to Looker
        • IBM Cognos to Power BI
      • Analytics
        • SAS
        • Alteryx
      • Shell Script
      • Common Model
    • Automation Level Indicator
      • ETL
        • Informatica
        • Matillion
        • DataStage
        • Informatica BDM
        • SnapLogic
        • IICS
        • Ab Initio
        • SSIS
        • Talend
        • Pentaho
      • Orchestration
        • AutoSys
        • Control-M
      • EDW
      • Analytics
        • SAS
        • Alteryx
      • BI
      • Shell Script
    • Error Specifications & Troubleshooting
  • SQL Transformation
    • Overview
    • Creating and Executing the Online Notebook
      • How to Create and Execute the Notebook
      • Supported Features
    • Configuring the Notebook
      • Transformation
      • Unit Level Validation
      • Script Level Validation
    • Notebook Listing
  • Operationalization
    • Overview
      • Basic
      • Advanced
      • Cron Expression
    • Parallel Run Pipeline Listing
  • Transformation Source
    • Introduction
    • Creating Transformation Source Type
  • Governance
    • Summary of Governance - Roles and Permissions
    • User Creation
      • Creating a new User Account
    • Adding Roles and permissions
      • How to add Roles and Permissions to a new user?
    • Adding Group Accounts
    • Default Quota Limits
    • Product Usage Metrics
  • License
    • EDW
    • ETL
  • LeapLogic Desktop Version
    • Overview
    • Registration and Installation
    • Getting Started
    • Creating Assessment
      • ETL
      • DML
      • Procedure
      • Analytics
      • Hadoop
    • Reports and Insights
      • Downloadable Reports
      • Reports for Estimation
    • Logging and Troubleshooting
    • Sample Scripts
    • Desktop vs. Web Version
    • Getting Help
  • LeapLogic (Version 4.8) Deployment
    • System Requirements
    • Prerequisites
    • Deployment
      • Extracting Package
      • Placing License Key
      • Executing Deployment Script
      • Accessing LeapLogic
    • Uploading License
    • Appendix
    • Getting Help
  • Removed Features
    • Configuring File Validation Stage
    • Variable Extractor Stage
      • Variable Extractor Report
    • Configuring Meta Diff Stage
      • Meta Diff
    • Configuring Data Load Stage
      • Data Load
    • Configuring Multi Algo Stage
  • FAQs
  • Tutorial Videos
  • Notice
Home   »  Pipeline Reports   »  Automation Level Indicator  »  ETL Automation Level Indicator

ETL Automation Level Indicator

This topic contains information about the logic used to calculate the automation level indicator of ETL sources including:

  • Informatica
  • Matillion
  • DataStage
  • Informatica BDM
  • SnapLogic
  • IICS
  • Ab Initio
  • SSIS
  • Talend
  • Pentaho

Informatica

Automation Level Indicator provides the automation conversion coverage of the Informatica ETL conversion. It is calculated based on the average of automation level indicator of all components.

Automation Level Indicator = Sum of automation level indicator of all components/ Total number of components

For instance, if there are 5 components with automation level indicator of 100%, 100%, 50%, 95%, and 100% respectively, then the automation level indicator is calculated as the average of automation level indicator of all these components. Therefore, the automation level indicator is 89% ((100 + 100 + 50 + 95 + 100)/ 5).

Next let’s see how to calculate the automation level indicator of each component.

The automation level indicator of each component is calculated based on:

  • Successfully converted component: Automation level indicator of a successfully converted component is 100%.
  • Failed component: Automation level indicator of a component that is failed to convert is 0%.
  • Partially supported component (successfully converted components with ToDo message): Automation level indicator of a partially supported component or successfully converted component with ToDo message is 90% by default (configurable).
  • Merged component (main and dependent sections): A merged component refers to a component with two sections: main and dependent, where the main section contains the core functionality and the dependent section provides additional information, input, etc., to the main section. Automation level indicator of a merged component is average of the main and dependents sections of the component. The merged components such as aggregate, union, lookup, and router have two sections – main and dependent. In such scenarios, if the main and dependent sections are successfully converted without the ToDo message, then the automation level indicator is 100%. Whereas, if the main and dependent sections are successfully converted with ToDo message, then the automation level indicator is 90%. The automation level indicator of the merged component is average of main and dependent sections.

For instance, if the main section of Lookup component is successfully converted, then the automation level indicator is 100% and if the dependent section is failed to convert, then the automation level indicator is 0%. Therefore, the automation level indicator of Lookup component is 50% (average of main and dependent sections ((100+0)/2)).

Component Main Dependent Average (Auto-conversion percentage of a merged component)
aggregate1 100 90 95
aggregate2 90 90 90
union 100 90 95
lookup 100 0 50
router 100 100 100

Matillion

Automation Level Indicator provides the automation conversion coverage of the Matillion ETL conversion. It is calculated based on the average of automation level indicator of all components.

Automation Level Indicator = Sum of automation level indicator of all components/ Total number of components

For instance, if there are 5 components with automation level indicator of 100%, 100%, 50%, 95%, and 100% respectively, then the automation level indicator is calculated as the average of automation level indicator of all these components. Therefore, the automation level indicator is 89% ((100 + 100 + 50 + 95 + 100)/ 5).

Next let’s see how to calculate the automation level indicator of each component.

The automation level indicator of each component is calculated based on:

  • Successfully converted component: Automation level indicator of a successfully converted component is 100%.
  • Failed component: Automation level indicator of a component that is failed to convert is 0%.
  • Partially supported component (successfully converted components with ToDo message): Automation level indicator of a partially supported component or successfully converted component with ToDo message is 90% by default (configurable).
  • Merged component (main and dependent sections): A merged component refers to a component with two sections: main and dependent, where the main section contains the core functionality and the dependent section provides additional information, input, etc., to the main section. Automation level indicator of a merged component is average of the main and dependents sections of the component. The merged components such as aggregate, union, router, etc., have two sections – main and dependent. In such scenarios, if the main and dependent sections are successfully converted without the ToDo message, then the automation level indicator is 100%. Whereas, if the main and dependent sections are successfully converted with ToDo message, then the automation level indicator is 90%. The automation level indicator of the merged component is average of main and dependent sections.

For instance, if the main section of Union component is successfully converted, then the automation level indicator is 100% and if the dependent section is partially supported, then the automation level indicator is 90%. Therefore, the automation level indicator of Union component is 95% (average of main and dependent sections ((100+90)/2)).

Component Main Dependent Average (Auto-conversion percentage of a merged component)
aggregate1 100 0 50
aggregate2 90 90 90
union 100 90 95
router 100 100 100

DataStage

Automation Level Indicator provides the automation conversion coverage of the DataStage ETL conversion. It is calculated based on the average of automation level indicator of all components.

Automation Level Indicator = Sum of automation level indicator of all components/ Total number of components

For instance, if there are 5 components with automation level indicator of 100%, 100%, 50%, 95%, and 100% respectively, then the automation level indicator is calculated as the average of automation level indicator of all these components. Therefore, the automation level indicator is 89% ((100 + 100 + 50 + 95 + 100)/ 5).

Next let’s see how to calculate the automation level indicator of each component.

The automation level indicator of each component is calculated based on:

  • Successfully converted component: Automation level indicator of a successfully converted component is 100%.
  • Failed component: Automation level indicator of a component that is failed to convert is 0%.
  • Partially supported component (successfully converted components with ToDo message): Automation level indicator of a partially supported component or successfully converted component with ToDo message is 90% by default (configurable).
  • Merged component (main and dependent sections): A merged component refers to a component with two sections: main and dependent, where the main section contains the core functionality and the dependent section provides additional information, input, etc., to the main section. Automation level indicator of a merged component is average of the main and dependents sections of the component. The merged components such as aggregate, union, router, etc., have two sections – main and dependent. In such scenarios, if the main and dependent sections are successfully converted without the ToDo message, then the automation level indicator is 100%. Whereas, if the main and dependent sections are successfully converted with ToDo message, then the automation level indicator is 90%. The automation level indicator of the merged component is average of main and dependent sections.

For instance, if the main section of Union component is successfully converted, then the automation level indicator is 100% and if the dependent section is partially supported, then the automation level indicator is 90%. Therefore, the automation level indicator of Union component is 95% (average of main and dependent sections ((100+90)/2)).

Component Main Dependent Average (Auto-conversion percentage of a merged component)
aggregate1 100 0 50
aggregate2 90 90 90
union 100 90 95
router 100 100 100

Informatica BDM

Automation Level Indicator provides the automation conversion coverage of the Informatica BDM ETL conversion. It is calculated based on the average of automation level indicator of all components.

Automation Level Indicator = Sum of automation level indicator of all components/ Total number of components

For instance, if there are 5 components with automation level indicator of 100%, 100%, 50%, 95%, and 100% respectively, then the automation level indicator is calculated as the average of automation level indicator of all these components. Therefore, the automation level indicator is 89% ((100 + 100 + 50 + 95 + 100)/ 5).

Next let’s see how to calculate the automation level indicator of each component.

The automation level indicator of each component is calculated based on:

  • Successfully converted component: Automation level indicator of a successfully converted component is 100%.
  • Failed component: Automation level indicator of a component that is failed to convert is 0%.
  • Partially supported component (successfully converted components with ToDo message): Automation level indicator of a partially supported component or successfully converted component with ToDo message is 90% by default (configurable).
  • Merged component (main and dependent sections): A merged component refers to a component with two sections: main and dependent, where the main section contains the core functionality and the dependent section provides additional information, input, etc., to the main section. Automation level indicator of a merged component is average of the main and dependents sections of the component. The merged components such as aggregate, union, router, etc., may have two sections – main and dependent. In such scenarios, if the main and dependent sections are successfully converted without the ToDo message, then the automation level indicator is 100%. Whereas, if the main and dependent sections are successfully converted with ToDo message, then the automation level indicator is 90%. The automation level indicator of the merged component is average of main and dependent sections.

For instance, if the main section of aggregate1 component is successfully converted, then the automation level indicator is 100% and if the dependent section is partially supported, then the automation level indicator is 90%. Therefore, the automation level indicator of aggregate1 component is 95% (average of main and dependent sections ((100+90)/2)).

Component Main Dependent Average (Auto-conversion percentage of a merged component)
aggregate1 100 90 95
aggregate2 90 90 90
union 100 0 50
router 100 100 100

SnapLogic

Automation Level Indicator provides the automation conversion coverage of the SnapLogic ETL conversion. It is calculated based on the average of automation level indicator of all components.

Automation Level Indicator = Sum of automation level indicator of all components/ Total number of components

For instance, if there are 5 components with automation level indicator of 100%, 100%, 50%, 95%, and 100% respectively, then the automation level indicator is calculated as the average of automation level indicator of all these components. Therefore, the automation level indicator is 89% ((100 + 100 + 50 + 95 + 100)/ 5).

Next let’s see how to calculate the automation level indicator of each component.

The automation level indicator of each component is calculated based on:

  • Successfully converted component: Automation level indicator of a successfully converted component is 100%.
  • Failed component: Automation level indicator of a component that is failed to convert is 0%.
  • Partially supported component (successfully converted components with ToDo message): Automation level indicator of a partially supported component or successfully converted component with ToDo message is 90% by default (configurable).
  • Merged component (main and dependent sections): A merged component refers to a component with two sections: main and dependent, where the main section contains the core functionality and the dependent section provides additional information, input, etc., to the main section. Automation level indicator of a merged component is average of the main and dependents sections of the component. The merged components such as aggregate, union, router, etc., have two sections – main and dependent. In such scenarios, if the main and dependent sections are successfully converted without the ToDo message, then the automation level indicator is 100%. Whereas, if the main and dependent sections are successfully converted with ToDo message, then the automation level indicator is 90%. The automation level indicator of the merged component is average of main and dependent sections.

For instance, if the main section of Union component is successfully converted, then the automation level indicator is 100% and if the dependent section is failed to convert, then the automation level indicator is 0%. Therefore, the automation level indicator of Union component is 50% (average of main and dependent sections ((100+0)/2)).

Component Main Dependent Average (Auto-conversion percentage of a merged component)
aggregate1 100 90 95
aggregate2 90 90 90
union 100 0 50
router 100 100 100


IICS

Automation Level Indicator provides the automation conversion coverage of the IICS ETL conversion. It is calculated based on the average of automation level indicator of all components.

Automation Level Indicator = Sum of automation level indicator of all components/ Total number of components

For instance, if there are 5 components with automation level indicator of 100%, 100%, 50%, 95%, and 100% respectively, then the automation level indicator is calculated as the average of automation level indicator of all these components. Therefore, the automation level indicator is 89% ((100 + 100 + 50 + 95 + 100)/ 5).

Next let’s see how to calculate the automation level indicator of each component.

The automation level indicator of each component is calculated based on:

  • Successfully converted component: Automation level indicator of a successfully converted component is 100%.
  • Failed component: Automation level indicator of a component that is failed to convert is 0%.
  • Partially supported component (successfully converted components with ToDo message): Automation level indicator of a partially supported component or successfully converted component with ToDo message is 90% by default (configurable).
  • Merged component (main and dependent sections): A merged component refers to a component with two sections: main and dependent, where the main section contains the core functionality and the dependent section provides additional information, input, etc., to the main section. Automation level indicator of a merged component is average of the main and dependents sections of the component. The merged components such as aggregate, union, router, etc., have two sections – main and dependent. In such scenarios, if the main and dependent sections are successfully converted without the ToDo message, then the automation level indicator is 100%. Whereas, if the main and dependent sections are successfully converted with ToDo message, then the automation level indicator is 90%. The automation level indicator of the merged component is average of main and dependent sections.

For instance, if the main section of aggregate1 component is successfully converted, then the automation level indicator is 100% and if the dependent section is partially supported, then the automation level indicator is 90%. Therefore, the automation level indicator of aggregate1 component is 95% (average of main and dependent sections ((100+90)/2)).

Component Main Dependent Average (Auto-conversion percentage of a merged component)
aggregate1 100 90 95
aggregate2 90 90 90
union 100 0 50
router 100 100 100

Ab Initio

Automation Level Indicator provides the automation conversion coverage of the Ab Initio ETL conversion. It is calculated based on the average of automation level indicator of all components.

Automation Level Indicator = Sum of automation level indicator of all components/ Total number of components

For instance, if there are 5 components with automation level indicator of 100%, 100%, 0%, 85%, and 82% respectively, then the automation level indicator is calculated as the average of automation level indicator of all these components. Therefore, the automation level indicator is 73.4% ((100 + 100 + 0 + 85 + 82)/ 5).

Next let’s see how to calculate the automation level indicator of each component.

The automation level indicator of each component is calculated based on:

Automation Level Indicator of each component = Automation Base Percent + (100 – Automation Base Percent) * Supported Properties Count / Total Properties

By default, the automation base percentage for a component is 75% (configurable) if the component is auto-converted successfully. The remaining 25% is calculated based on the conversion support of properties in the graphs. For instance:

  • If you have 10 properties for a particular component and all the 10 properties are auto-converted successfully, then the automation level indicator is calculated as the Automation Base Percent + (100 – Automation Base Percent) * Supported Properties Count / Total Properties; i.e, 75+ (100-75)*10/10 = 100%
  • If you have 10 properties for a particular component and only 5 properties are auto-converted, then automation level indicator is calculated as the Automation Base Percent + (100 – Automation Base Percent) * Supported Properties Count / Total Properties; i.e., 75+(100-75)*5/10=87.5%

Note:

If a component is failed to transform, then the automation level indicator is zero.


SSIS

Automation Level Indicator provides the automation conversion coverage of the SSIS ETL conversion. It is calculated based on the average of automation level indicator of all components.

Automation Level Indicator = Sum of automation level indicator of all components/ Total number of components

For instance, if there are 5 components with automation level indicator of 100%, 100%, 0%, 85%, and 82% respectively, then the automation level indicator is calculated as the average of automation level indicator of all these components. Therefore, the automation level indicator is 73.4% ((100 + 100 + 0 + 85 + 82)/ 5).

Next let’s see how to calculate the automation level indicator of each component.

The automation level indicator of each component is calculated based on:

Automation Level Indicator of each component = Automation Base Percent + (100 – Automation Base Percent) * Supported Properties Count / Total Properties

By default, the automation base percentage for a component is 75% if the component is auto-converted successfully. The remaining 25% is calculated based on the conversion support of properties in the graphs. For instance:

  • If you have 10 properties for a particular component and all the 10 properties are auto-converted successfully, then the automation level indicator is calculated as the Automation Base Percent + (100 – Automation Base Percent) * Supported Properties Count / Total Properties; i.e, 75+ (100-75)*10/10 = 100%
  • If you have 10 properties for a particular component and only 5 properties are auto-converted, then automation level indicator is calculated as the Automation Base Percent + (100 – Automation Base Percent) * Supported Properties Count / Total Properties; i.e., 75+(100-75)*5/10=87.5%

Note:

If a component is failed to transform, then the automation level indicator is zero.


Talend

Automation Level Indicator provides the automation conversion coverage of the Talend ETL conversion. It is calculated based on the average of automation level indicator of all components.

Automation Level Indicator = Sum of automation level indicator of all components/ Total number of components

For instance, if there are 5 components with automation level indicator of 100%, 100%, 0%, 85%, and 82% respectively, then the automation level indicator is calculated as the average of automation level indicator of all these components. Therefore, the automation level indicator is 73.4% ((100 + 100 + 0 + 85 + 82)/ 5).

Next let’s see how to calculate the automation level indicator of each component.

The automation level indicator of each component is calculated based on:

Automation Level Indicator of each component = Automation Base Percent + (100 – Automation Base Percent) * Supported Properties Count / Total Properties

By default, the automation base percentage for a component is 75% if the component is auto-converted successfully. The remaining 25% is calculated based on the conversion support of properties in the graphs. For instance:

  • If you have 10 properties for a particular component and all the 10 properties are auto-converted successfully, then the automation level indicator is calculated as the Automation Base Percent + (100 – Automation Base Percent) * Supported Properties Count / Total Properties; i.e, 75+ (100-75)*10/10 = 100%
  • If you have 10 properties for a particular component and only 5 properties are auto-converted, then automation level indicator is calculated as the Automation Base Percent + (100 – Automation Base Percent) * Supported Properties Count / Total Properties; i.e., 75+(100-75)*5/10=87.5%

Note:

If a component is failed to transform, then the automation level indicator is zero.


Pentaho

Automation level indicator provides the automation conversion coverage of the Pentaho ETL conversion. It is calculated based on the average of automation level indicator of jobs and transformations.

Automation Level Indicator = Sum of auto conversion percentage all jobs and transformations / total number of jobs and transformations

For instance, if you have three jobs or transformations with 88%, 100%, and 100% auto-conversion percentage respectively. Then the overall automation level indicator is calculated as sum of auto conversion percentage all jobs and transformations / total number of jobs and transformations, i.e., 88+100+100/3 = 96%.

Next, let’s see how to calculate the automation level indicator of each job or transformation.

The automation level indicator of each job or transformation is calculated based on the average of successfully converted components in the job/ transformation.

Automation Level Indicator of a job/ transformation = (Number of successfully converted components / total number of components) * 100

For instance, if there are 25 components, out of which 22 components are successfully converted to target equivalent, then the Automation Level Indicator is calculated as (Number of successfully converted components/ Total number components) * 100; i.e., (22/25) * 100 = 88%


To learn more, contact our support team or write to: info@leaplogic.io

Copyright © 2025 Impetus Technologies Inc. All Rights Reserved

  • Terms of Use
  • Privacy Policy
  • License Agreement
To the top ↑ Up ↑