Product Name DRYiCE ROAR
Version Number R4
Release Month December , 2020
Release Summary


The Onboarding module is used to configure the basic details required to setup the application for the user. Following are the feature enhancements in this module:

  • 3 level billing entity definition to incorporate more details and perform necessary reporting:

    The billing entity page defines the business units that have to be charged for various RUs based on their region or country mentioned in the contract. The user will now be able to define the billing entity names up to three levels (i.e., with one field and two sub-fields) to capture more information on the billing entities. For e.g., if a user wants to define a billing entity for Sweden, ROAR will allow the user to represent it as: ROW- EUROPE- SWEDEN. In order to define any other country within Europe, the user will retain the first two fields and replace the third field with the name of the country. This will allow extraction of reports for the rest of the world (ROW) in level 1 and all countries within Europe in level 2.

  • RU Category Option as per Logic (Contractual/ Inclusion/ Exclusion) for auto handling of exceptions:

    A resource unit provides a measurement of the workload or effort required to deliver and support services. It is contractually defined before onboarding a customer. A provision has been made for exclusion categories in a RU definition to include the data specific to non-contractual RU definitions and ensuring that the necessary reporting can be performed. The auto-handling of exceptions will mitigate manual adjustment required to calculate RU counts, significantly reducing processing time while increasing accuracy. Through the reporting feature, account specific inclusion/ exclusion CIs can be identified, enabling the correct counting of billables.

  • Purge job history made available

    The purge function allows the user to delete all the input data from previous job executions to run a fresh data cycle and avoid data discrepancies. Through this feature, a user will now be able to view the history of purge jobs executed in the application between a specific time period for a company and class combination. The user can view the date and time of job execution, along with its success/ failure status.


The Normalization module validates incoming data and replaces the alternate representations of CI information with standard values. Following are the feature enhancements in this module:

  • Validation job will be executed on company and class combination rather than for all the classes together:

    The validation job verifies data completeness against the mandatory checks defined in ROAR. Till now, the validation job had to be executed based on company name for all the classes together. This restricted progress to the next step of data normalization for a class if validation of another job was under process. Now,  the validation will be executed on a combination of company and class. This will enable the user to normalize data for a class if validation of some other class is still under process.

Overall product enhancements

  • Customer role landing page to be introduced: A new landing page has been introduced for customers to view when they login, providing an overview of all processing steps in ROAR

  • Manual job dashboard to view all jobs processed in the application:

    The dashboard will enable users to view all the jobs executed in the application. Jobs are classified at 1st level based on status and at 2nd level based on type. The users can view the required information by selecting the relevant class and company combination to gain a real-time view of all jobs from a single dashboard.

  • Jobs status log made visible in processing history for historical jobs executed in the application:

    The history of all jobs previously executed in the application will now be visible. Details that would be visible are job execution start and end date/time and the number of records available and processed. These records can be filtered based on the company name, class name, job type and status and can be extracted for durations of 1,7,15,30 and 90 days.

  • Increased import file size limit to 100MB:

    The users can now upload data source files of up to 100MB to enable the processing of huge volumes of data on ROAR (The earlier limit was 60MB).

  • Ability to resume automation job after application start up:

    The automation module executes the ROAR cycle end-to-end without human intervention by providing the capability to configure the rules for running jobs beforehand. The users will now be able to resume interrupted jobs in the Automation module after the application restarts, significantly saving the user’s time and effort.

  • Additional date formats included in User Profile section:

    Additional date formats have been included in the User Profile section allowing the users to select a date format based on their country and preference. The reports will be downloaded in this default date format only.

  • Improved performance of Purge and Validation Job:

    Several changes have been introduced in the backend to improve the performance of purge and validation jobs in terms of time and efficiency.

  • Performance Optimization:

    Conducted regular performance testing and system update to enhance the application performance.

About ROAR

DRYiCE ROAR delivers data quality by integrating and reconciling data from a broad range of sources automatically and consistently to create a single-source-of-truth. It is an industry-agnostic solution that has multi-role capabilities across the enterprise value chain. The data processed by DRYiCE ROAR can be used for populating downstream applications in billing, service management, software, and inventory management.


For product-related inquiries, please reach us at [email protected]