Technology Category
- Application Infrastructure & Middleware - Data Exchange & Integration
- Application Infrastructure & Middleware - Middleware, SDKs & Libraries
Applicable Industries
- Automotive
- Construction & Infrastructure
Applicable Functions
- Human Resources
- Product Research & Development
Use Cases
- Construction Management
- Leasing Finance Automation
Services
- Cloud Planning, Design & Implementation Services
- System Integration
About The Customer
The Dürr Group is one of the world's leading mechanical and plant engineering firms with extensive expertise in automation and digitalization/Industry 4.0. Its products, systems and services enable highly efficient and resource-saving manufacturing processes in different industries. The Dürr Group consists of the three brands Dürr, Schenck and HOMAG, as well as five global divisions. It serves a variety of customers in different industries, including automotive manufacturers and suppliers, woodworking companies, machine manufacturers, chemical and pharmaceutical companies. The Dürr Group generated sales of €3.32 billion in 2020.
The Challenge
The Dürr Group, a leading mechanical and plant engineering firm, faced several challenges in aligning its IT with its company-wide OneDürrGroup strategy. The company's consistent expansion and diverse customer base resulted in a complex IT infrastructure, characterized by different integration solutions and a hybrid application landscape. The company aimed to implement its OneDürrGroup strategy across all locations and divisions, which naturally impacted its own IT. The diverse range of solutions—on-premises, Integration-Platform-as-a-Service (iPaaS) and Software-as-a-Service—meant more cost and effort and required more expertise in different technologies, as well as a mass of redundant interfaces. The company believed that an integrated architecture could achieve significant streamlining in the HR landscape alone.
The Solution
To address these challenges, Dürr Group chose webMethods from Software AG as the leading integration platform, in addition to SAP PO and the Microsoft® Azure® Service Bus Integration. The webMethods solution not only simplifies complex problems and connects hybrid application landscapes, but it also builds a bridge between internal and external communication and can connect innovative services via an API portal. All new projects will be integrated through the platform, providing a fast and smooth basis for integration. The company also plans to gradually introduce APIs as the basis for new digital customer services. The integration team launched a workshop series to clarify specific questions about this challenge for all of the different divisions. The platform’s advantages became clear in project workshops—for example, when planning the new CRM solution’s target architecture.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
IoT System for Tunnel Construction
The Zenitaka Corporation ('Zenitaka') has two major business areas: its architectural business focuses on structures such as government buildings, office buildings, and commercial facilities, while its civil engineering business is targeted at structures such as tunnels, bridges and dams. Within these areas, there presented two issues that have always persisted in regard to the construction of mountain tunnels. These issues are 'improving safety" and "reducing energy consumption". Mountain tunnels construction requires a massive amount of electricity. This is because there are many kinds of electrical equipment being used day and night, including construction machinery, construction lighting, and ventilating fan. Despite this, the amount of power consumption is generally not tightly managed. In many cases, the exact amount of power consumption is only ascertained when the bill from the power company becomes available. Sometimes, corporations install demand-monitoring equipment to help curb the maximum power demanded. However, even in these cases, the devices only allow the total volume of power consumption to be ascertained, or they may issue warnings to prevent the contracted volume of power from being exceeded. In order to tackle the issue of reducing power consumption, it was first necessary to obtain an accurate breakdown of how much power was being used in each particular area. In other words, we needed to be able to visualize the amount of power being consumed. Safety, was also not being managed very rigorously. Even now, tunnel construction sites often use a 'name label' system for managing entry into the work site. Specifically, red labels with white reverse sides that bear the workers' names on both sides are displayed at the tunnel work site entrance. The workers themselves then flip the name label to the appropriate side when entering or exiting from the work site to indicate whether or not they are working inside the tunnel at any given time. If a worker forgets to flip his or her name label when entering or exiting from the tunnel, management cannot be performed effectively. In order to tackle the challenges mentioned above, Zenitaka decided to build a system that could improve the safety of tunnel construction as well as reduce the amount of power consumed. In other words, this new system would facilitate a clear picture of which workers were working in each location at the mountain tunnel construction site, as well as which processes were being carried out at those respective locations at any given time. The system would maintain the safety of all workers while also carefully controlling the electrical equipment to reduce unnecessary power consumption. Having decided on the concept, our next concern was whether there existed any kind of robust hardware that would not break down at the construction work site, that could move freely in response to changes in the working environment, and that could accurately detect workers and vehicles using radio frequency identification (RFID). Given that this system would involve many components that were new to Zenitaka, we decided to enlist the cooperation of E.I.Sol Co., Ltd. ('E.I.Sol') as our joint development partner, as they had provided us with a highly practical proposal.
Case Study
Integral Plant Maintenance
Mercedes-Benz and his partner GAZ chose Siemens to be its maintenance partner at a new engine plant in Yaroslavl, Russia. The new plant offers a capacity to manufacture diesel engines for the Russian market, for locally produced Sprinter Classic. In addition to engines for the local market, the Yaroslavl plant will also produce spare parts. Mercedes-Benz Russia and his partner needed a service partner in order to ensure the operation of these lines in a maintenance partnership arrangement. The challenges included coordinating the entire maintenance management operation, in particular inspections, corrective and predictive maintenance activities, and the optimizing spare parts management. Siemens developed a customized maintenance solution that includes all electronic and mechanical maintenance activities (Integral Plant Maintenance).
Case Study
Splunk Partnership Ties Together Big Data & IoT Services
Splunk was faced with the need to meet emerging customer demands for interfacing IoT projects to its suite of services. The company required an IoT partner that would be able to easily and quickly integrate with its Splunk Enterprise platform, rather than allocating development resources and time to building out an IoT interface and application platform.