-
By Technology
- APIs
- Microservices Architecture
- B2B
- ESB
-
By Integration
- Salesforce
- SAP
- SWIFT
-
Consulting Services
- Architecture Design
- Implementation
- Performance Tuning
- Training
-
Support
- Premium Support
- Support Portal
-
Success Stories
- Aboitiz Power
- Commercial Bank of Africa
- Delware North Companies
- US Coast Guard
-
Featured Resources
- Whitepapers
- Analyst Reports & Product Reviews
- Press Releases
- Case Studies
- Blog
-
Customers
- Customers
- Case Studies
-
Partners
- Partners
- Partner Network
Home > Resources > Case Study > ElektroBit
Driving the future of Auto-Mobility with Fiorano
Elektrobit is a global leader in automotive software. EB‘s software powers over 1 billion devices in more than 100 million vehicles and offers flexible, innovative solutions for connected car infrastructure, human machine interface (HMI) technologies, driver assistance, electronic control units (ECUs), and software engineering services.
Driving the future of Auto-Mobility with Fiorano
Elektrobit is a global leader in automotive software. EB‘s software powers over 1 billion devices in more than 100 million vehicles and offers flexible, innovative solutions for connected car infrastructure, human machine interface (HMI) technologies, driver assistance, electronic control units (ECUs), and software engineering services.
USE CASE
Integrate tools of different business departments
BENEFITS
Reduced production timing
INDUSTRY
Manufacturing
KEY PRODUCT COMPONENTS
Fiorano ESB, Fiorano SOA
Business Challenge
Elektrobit is using a server infrastructure based on Windows Server & Linux platforms. In service production they use both in-house developed services as well as third party SaaS-services. They have a large end-user base of about 1500 and counting, accessing their technology across geographies and time-zones.
In 2007, as they were planning a renewal of their financial processes & tools, Elektrobit realized that they required a centralized messaging infrastructure which would unify the existing landscape of disparate applications. The selected accounting tool was a web-based SaaS-service and all financial subsystems were to be integrated with it, hence a web service-capable integration platform was required.
At the inception of the application architecture plan, Elektrobit had established that an Enterprise Service Bus would be the middleware solution of choice. They had decided not to implement one massive ERP-solution, but rather a flexible mesh of applications, where a number of old legacy applications and a selection of new applications would communicate simultaneously through a single integration channel.
Their architectural blue print thus envisaged a framework providing independent connectivity to all tools, enabling change of business processes on-demand, without service breaks. Flexible application architecture was expected to bring savings in shorter implementation and change schedules. An ESB would also make it possible to change tools on the go, without redesigning the whole process again. Reusability would bring crucial benefits for rapid application integration and once developed, solutions could be easily reused in new integration processes.
The primary goal was to find a product which would enable integration of internal finance and HR tools and to return transaction data from the accounting system back to the reporting data warehouse. They were also looking for the ability to integrate third party web tools with internal systems. Working on a tight schedule, Elektrobit required a flexible and easily scalable environment which would reduce their time to production.
Further, Elektrobit did not have a dedicated middleware developer on their team, and therefore required a platform that was easy to learn and did not require too much training for implementation. They expected highly responsive support from their chosen vendor as well.
1,000,000,000
DEVICES on 100 mm vehicles
Fiorano ESB, Fiorano SOA
Business Challenge
Elektrobit is using a server infrastructure based on Windows Server & Linux platforms. In service production they use both in-house developed services as well as third party SaaS-services. They have a large end-user base of about 1500 and counting, accessing their technology across geographies and time-zones.
In 2007, as they were planning a renewal of their financial processes & tools, Elektrobit realized that they required a centralized messaging infrastructure which would unify the existing landscape of disparate applications. The selected accounting tool was a web-based SaaS-service and all financial subsystems were to be integrated with it, hence a web service-capable integration platform was required.
At the inception of the application architecture plan, Elektrobit had established that an Enterprise Service Bus would be the middleware solution of choice. They had decided not to implement one massive ERP-solution, but rather a flexible mesh of applications, where a number of old legacy applications and a selection of new applications would communicate simultaneously through a single integration channel.
Their architectural blue print thus envisaged a framework providing independent connectivity to all tools, enabling change of business processes on-demand, without service breaks. Flexible application architecture was expected to bring savings in shorter implementation and change schedules. An ESB would also make it possible to change tools on the go, without redesigning the whole process again. Reusability would bring crucial benefits for rapid application integration and once developed, solutions could be easily reused in new integration processes.
The primary goal was to find a product which would enable integration of internal finance and HR tools and to return transaction data from the accounting system back to the reporting data warehouse. They were also looking for the ability to integrate third party web tools with internal systems. Working on a tight schedule, Elektrobit required a flexible and easily scalable environment which would reduce their time to production.
Further, Elektrobit did not have a dedicated middleware developer on their team, and therefore required a platform that was easy to learn and did not require too much training for implementation. They expected highly responsive support from their chosen vendor as well.
1,000,000,000
DEVICES on 100 mm vehicles
Fiorano ESB, Fiorano SOA
"Our target was to enable a flexible mesh of applications, where the legacy apps and new SaaS Services could independently communicate on one channel. We chose Fiorano for its flexibility, built-in scalability, insightful development environment & easy-to-use message transformation tools."
Timo Impiö, Specialist, Global IM, Elektrobit
"Our target was to enable a flexible mesh of applications, where the legacy apps and new SaaS Services could independently communicate on one channel. We chose Fiorano for its flexibility, built-in scalability, insightful development environment & easy-to-use message transformation tools."
Timo Impiö, Specialist, Global IM, Elektrobit
Solution
As the selection process was kicked-off, Elektrobit went through product demos and visited several major integration solution vendors. After short-listing a set of vendors, they set up a Proof-of-Concept which required the integration of four different types of applications. They picked up data schemas, provided sample data files with real data and gave vendors two weeks to implement the POC Scenario. During the POC, Fiorano outperformed others in implementation speed, performance and product support, being the first vendor to provide a working solution.
Timo Impiö, Specialist, Global IM explains "Fiorano was confident of its product and backed it up with an efficiently executed POC delivered in time with high quality support during the process. We got all the example integrations done; that experience built trust and gave us confidence in the vendor from a long-term perspective. Meanwhile, some of the other POC participants could not even get the integrations done despite a larger outlay of resources for the POC."
Fiorano ESB was selected to be the backbone for messaging and application integration at EB. He goes on to add "Of course we were wondering what might happen to the support quality after the deal was closed, but to our pleasant surprise found that the support requests are handled efficiently even afterwards."
Solution
As the selection process was kicked-off, Elektrobit went through product demos and visited several major integration solution vendors. After short-listing a set of vendors, they set up a Proof-of-Concept which required the integration of four different types of applications. They picked up data schemas, provided sample data files with real data and gave vendors two weeks to implement the POC Scenario. During the POC, Fiorano outperformed others in implementation speed, performance and product support, being the first vendor to provide a working solution.
Timo Impiö, Specialist, Global IM explains "Fiorano was confident of its product and backed it up with an efficiently executed POC delivered in time with high quality support during the process. We got all the example integrations done; that experience built trust and gave us confidence in the vendor from a long-term perspective. Meanwhile, some of the other POC participants could not even get the integrations done despite a larger outlay of resources for the POC."
Fiorano ESB was selected to be the backbone for messaging and application integration at EB. He goes on to add "Of course we were wondering what might happen to the support quality after the deal was closed, but to our pleasant surprise found that the support requests are handled efficiently even afterwards."
Fiorano Deployment Architecture at Elektrobit
Reusability & Fiorano Product Support
Fiorano SOA offered consistent reusability features allowing Elektrobit to use components developed once across new integration flows, so that servers could be quickly added without much rework or performance trade-off.
Solutions once developed and tested were easily re-used in new integration process flows. This became a very important benefit for rapid application integration as the efficiency of designing new flows increased linearly. In Fiorano, most of the integration processes were ready to use a few hours after the installation process.
Due to a tight schedule and adoption of a new technology, Elektrobit expected that there would be heavy utilization of product support during the project start up phase and further down the road in the overall integration lifecycle. Elektrobit received extensive and reliable support during implementation and creation of application integration processes.
Integration out-of-the-box
Since Elektrobit's environment incorporated several applications, there was a need for several connectivity methods, message transformation, content filtering, xml support and web service support, all of which were provided by the Fiorano ESB. Testing was also a key benefit as automated tests were generated for schemas and data.
Fiorano delivered sophisticated message transformation logic, customized content filtering and solid web service support with XML compatibility. Being platform independent and consisting of an extensive set of connectivity methods enabling integration out of the box, it was an ideal choice for Elektrobit. To accelerate scalability, Fiorano SOA offered consistent reusability features allowing Elektrobit to use components developed once across new integration flows, so that servers could be quickly added without much rework or performance trade-off.
Fiorano Deployment Architecture at Elektrobit
Reusability & Fiorano Product Support
Fiorano SOA offered consistent reusability features allowing Elektrobit to use components developed once across new integration flows, so that servers could be quickly added without much rework or performance trade-off.
Solutions once developed and tested were easily re-used in new integration process flows. This became a very important benefit for rapid application integration as the efficiency of designing new flows increased linearly. In Fiorano, most of the integration processes were ready to use a few hours after the installation process.
Due to a tight schedule and adoption of a new technology, Elektrobit expected that there would be heavy utilization of product support during the project start up phase and further down the road in the overall integration lifecycle. Elektrobit received extensive and reliable support during implementation and creation of application integration processes.
Integration out-of-the-box
Since Elektrobit's environment incorporated several applications, there was a need for several connectivity methods, message transformation, content filtering, xml support and web service support, all of which were provided by the Fiorano ESB. Testing was also a key benefit as automated tests were generated for schemas and data.
Fiorano delivered sophisticated message transformation logic, customized content filtering and solid web service support with XML compatibility. Being platform independent and consisting of an extensive set of connectivity methods enabling integration out of the box, it was an ideal choice for Elektrobit. To accelerate scalability, Fiorano SOA offered consistent reusability features allowing Elektrobit to use components developed once across new integration flows, so that servers could be quickly added without much rework or performance trade-off.
Results
With relationships with leading carmakers and suppliers including Audi, BMW, Daimler, Ford, GM, Volkswagen Group, Volvo, allows Elektrobit to stay on top of new innovations and to incorporate their technology into our products early in the development phase. It is important for them to stay on the cutting edge.
For this they need flexibility and responsiveness in their business processes which was enabled by the Fiorano infrastructure.
Flexibility: The Fiorano ESB architecture allows live changes to be made made to running business process without interrupting any of the other services. Independent applications as well as flows were modified on the go without having to re-design the whole process. This not only decreased development time but also allowed automated tests to be generated for schemas and data flows.
Fast Time to Production & responsiveness: Even though they were working on tight project schedule, Elektrobit found that Fiorano was very easy to deploy and setup for internal use. It quickly accommodated changes in business logic and adapted the existing process to match these changes efficiently.
Minimal Training and Resources Required: With Fiorano, there was no need for massive training or a large number of senior consultants for application integration. The Fiorano Studio enables a drag-and-drop based approach to building integration flows, hence product training required was minimal. Currently only one experienced developer takes care of over 40 live application integration processes.
Results
With relationships with leading carmakers and suppliers including Audi, BMW, Daimler, Ford, GM, Volkswagen Group, Volvo, allows Elektrobit to stay on top of new innovations and to incorporate their technology into our products early in the development phase. It is important for them to stay on the cutting edge.
For this they need flexibility and responsiveness in their business processes which was enabled by the Fiorano infrastructure.
Flexibility: The Fiorano ESB architecture allows live changes to be made made to running business process without interrupting any of the other services. Independent applications as well as flows were modified on the go without having to re-design the whole process. This not only decreased development time but also allowed automated tests to be generated for schemas and data flows.
Fast Time to Production & responsiveness: Even though they were working on tight project schedule, Elektrobit found that Fiorano was very easy to deploy and setup for internal use. It quickly accommodated changes in business logic and adapted the existing process to match these changes efficiently.
Minimal Training and Resources Required: With Fiorano, there was no need for massive training or a large number of senior consultants for application integration. The Fiorano Studio enables a drag-and-drop based approach to building integration flows, hence product training required was minimal. Currently only one experienced developer takes care of over 40 live application integration processes.
Subscribe For Updates
© 2019 Fiorano Software and Affiliates. All Rights Reserved. Privacy Statement | Terms of Use
© 2019 Fiorano Software and Affiliates. All Rights Reserved. Privacy Statement | Terms of Use