{"id":20573,"date":"2024-04-08T14:26:10","date_gmt":"2024-04-08T12:26:10","guid":{"rendered":"https:\/\/www.dynamiclicensecontrol.com\/?page_id=20573"},"modified":"2024-04-09T09:32:42","modified_gmt":"2024-04-09T07:32:42","slug":"success-story-herrenknecht","status":"publish","type":"page","link":"https:\/\/www.dynamiclicensecontrol.com\/en\/success-story-herrenknecht\/","title":{"rendered":"Success Story Herrenknecht"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Success Story Herrenknecht<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Herrenknecht increases IT efficiency through the use of BatchMan Workload Automation<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Management Summary<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Herrenknecht, a technology leader in mechanized tunnelling for the construction of underground infrastructure, faced significant IT challenges caused by the limitations of the standard SAP job scheduler. The introduction of BatchMan Workload Automation provided a bespoke solution that enabled complex schedules to be managed efficiently, avoiding job overlaps and implementing a proactive alerting system for job aborts.<\/p>

The software enabled Herrenknecht to significantly optimize IT processes, reduce manual effort and increase process reliability. This enabled the company to continuously improve its operational processes.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Herrenknecht\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Branche:<\/strong> Mechanical engineering<\/p>

Use Case: <\/strong>Optimization of SAP background processes<\/p>

Advantages:<\/strong> Time saving, error reduction and alerting<\/p>

Product:<\/strong> BatchMan<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t
\n
\n
\n\n\nDownload (PDF)<\/span>\n<\/span>\n<\/a>\n<\/div>\n<\/div>\n<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Challenges with standard SAP job control<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The use of the standard job scheduler in SAP offered Herrenknecht only limited possibilities, especially when planning regular tasks.<\/p>

At Herrenknecht, for example, material and parts lists are created in an external system for the standard background processes and then transferred to SAP and enriched there. The result should be available in SAP as quickly as possible, but the jobs should not work in parallel. jobs should not work in parallel, however, and objects that have been left behind should be reprocessed after 15 minutes at the latest.<\/p>


This was only possible in the SAP scheduler with special solutions and manual effort and repeatedly led to errors, e.g. due to missing notifications from the system.<\/p>

The search for an efficient, flexible and user-friendly workload automation solution led Herrenknecht to BatchMan, a product that stood out for its practical development and continuous improvement.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Specific requirements and solutions: why Herrenknecht relies on BatchMan<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Flexible time windows for job execution:\n<\/h4>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The need to schedule jobs within specific time slots, for example every hour between 06:00 and 17:00, proved to be cumbersome with the standard SAP scheduler, as separate jobs had to be scheduled for each hour.<\/p>

  • By introducing BatchMan, Herrenknecht was able to significantly reduce the number of processing steps, in some cases by up to 90%. This also reduced the risk of making mistakes when maintaining redundant jobs in the SAP system.<\/strong><\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
    \n\t\t\t
    \n\t\t\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t

    Complex schedules with less manual handling:<\/h4>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Herrenknecht needed the ability to run jobs according to complex schedules. Previously, if the first day of the month was a Wednesday, the job had to be started manually by the specialist departments so that the jobs were not executed multiple times.<\/p>

    • By mapping complex rules in BatchMan within a job, Herrenknecht was also able to schedule special rules, such as every Wednesday plus the first of the month, without risking duplicate executions.<\/strong><\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
      \n\t\t\t
      \n\t\t\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t

      Avoidance of overlaps with long-running jobs:<\/h4>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      The SAP standard scheduler could not guarantee freedom from overlaps, which required additional programming effort to control job execution.<\/p>

      • BatchMan offers a simple checkbox here to indicate whether parallel execution should be granted or not. This means that overlaps without manual activities can be avoided as early as the job planning stage.<\/strong><\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
        \n\t\t\t\t\t\t
        \n\t\t\t\t\t
        \n\t\t\t
        \n\t\t\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t

        Exclusive use of resources for parallel versions:<\/h4>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        For jobs that required the same resources exclusively, lock objects would have had to be set up manually and checked in manually and checked in each job to avoid conflicts.<\/p>

        • BatchMan offered Herrenknecht various options for parallel execution. BatchMan already included the locking mechanisms so that parallel scheduling across different jobs and processes was also possible without any problems.
          <\/strong><\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
          \n\t\t\t
          \n\t\t\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t

          Flexible and frequent program execution:<\/h4>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          A specific program, which had variable processing times, was to be executed as often as possible within a defined time frame, which was only possible to a limited extent with the SAP scheduler and led to overtaking.<\/p>