Since its creation over 150 years ago, ARaymond has grown into a leading manufacturer of fastening and assembly solutions. The company provides specialist parts for the automotive, industrial, agricultural, pharmaceutical and energy sectors, and has 25,000 assembly solutions currently in production. Most vehicles globally contain on average 500 ARaymond components.
ARaymond has a truly global presence, with 6,500 employees in 26 manufacturing sites across four continents and generates more than 1 billion euros in annual revenues — a figure that almost tripled between 2004 and 2016. With over 1,600 patents and 6% of annual turnover invested in research and development, ARaymond is committed to innovation and engineering excellence.
Manufacturers of specialized products such as cars, pharmaceutical products and industrial machinery require suppliers to provide rapid, reliable services 24/7. That’s why ARaymond, one of the leading manufacturers of assembly solutions, set out to evolve its IT infrastructure with SUSE Linux Enterprise Server (SLES) for SAP Applications and the SUSE® Linux Enterprise (SLE) High Availability Extension. By strengthening stability and availability, these solutions help ARaymond maintain its long-held reputation for excellent customer service.
To maximize productivity and minimize waste, manufacturers in the automotive, industrial and pharmaceutical industries typically work to a just-in-time production model. For assembly lines to run smoothly and cost-effectively, suppliers to these manufacturers must deliver precisely on schedule — or face significant financial penalties, not to mention reputational damage.
Jérôme Rézé, infrastructure director at ARaymond, comments: “For companies that run lean assembly operations, waiting for components is simply not an option. Our business success at ARaymond is dependent on our continuing ability to produce and distribute fastening devices and assembly solutions quickly and efficiently. Any delay in delivery could lead to a very costly break in manufacturing for our customers, potentially triggering penalty clauses and negatively impacting ARaymond’s reputation as an industry leader.”
To support the company’s commitment to exceptional customer service, ARaymond created an internal IT services division — ARaymond IT Technology — with 170 employees supporting a total of 130 applications for 4,500 internal users. Key to centralized service provided by ARaymond IT Technology are SAP ERP applications, which are offered as standard to all the parent company’s global business units.
With SAP set to withdraw support for all other databases, ARaymond IT Technology decided to move early to the SAP HANA database, giving itself time for a smooth, non-disruptive migration of key business systems.
Marc Coste, SAP technical leader at ARaymond, comments: “We knew we needed to make the migration to SAP HANA within a few years, and we decided to reduce the risk and disruption by starting the process early. This approach allowed us to take our time and build up experience in migrating less critical systems before we tackled the all-important production landscape.”
He adds: “Moving ahead with the migration to SAP HANA was also a way to address some performance issues that had emerged in our SAP Business Intelligence landscape. We had upgraded to SAP BI 4.0, and users were complaining that reports that previously took 30 seconds were now taking several minutes to complete. We upgraded to SAP BI 4.1 and spent a good deal of time trying to optimize the solution. However, we eventually hit the limits of the architecture, and the only answer was to migrate to SAP HANA.”
“The bundling of the SUSE high-availability component offered an economic way to support our requirements for always-on SAP systems, compared with competitive offerings.”
To support its new SAP HANA database servers, ARaymond chose SLES for SAP Applications together with the SLE High Availability Extension.
Rézé comments: “We initially considered implementing Red Hat Enterprise Linux on a larger scale, as we have been using this solution for some non-SAP applications for a number of years. However, when we worked with our partner, TeamWork, to consider the plus and minus points of each distribution, we quickly saw that the vast majority of the SAP market is on SUSE Linux Enterprise, which implied a very strong ecosystem for SAP software around the SUSE operating system. The commercial offer for SLES for SAP Applications was also more attractive, and we liked the idea of having a release specifically tailored to the demands of SAP solutions.”
Coste adds: “Moreover, because SAP develops its own software on the SUSE operating system, we believed that we would stand to benefit from the synergy between the two solutions. Equally, the bundling of the SUSE high-availability component offered an economic way to support our requirements for always-on SAP systems, compared with competitive offerings.”
As the first step in its global migration plan, ARaymond migrated its SAP business intelligence landscape from Oracle Database on Microsoft Windows to SAP HANA on SLES for SAP Applications. In technical terms, the migration presented a number of challenges. ARaymond needed to change its server hardware, operating system and database, and do so quickly, with minimal disruption to ongoing business.
“Tackling the SAP BI landscape gave us an opportunity to build up our experience and test our migration plans with a noncritical system,” says Rézé. “It also enabled us to address user concerns around degradation in reporting speed and to demonstrate that SAP HANA would offer improved performance over the previous database platform.”
To maximize flexibility and scalability, particularly in its data storage infrastructure, ARaymond chose the SAP TDI (Tailored Data Center Integration) approach. This enables SAP HANA to be deployed on existing hardware rather than on the prebuilt appliances required when SAP HANA first launched.
“The TDI approach enables us to invest in data storage resources that can be shared with other software landscapes,” comments Coste. “We prefer to have infrastructure that we can manage ourselves, rather than black-box solutions. We also saw that the trend in the SAP market is toward TDI.”
He adds: “We were very pleased with how smoothly the migration of the business intelligence landscape ran, and this positive experience continued as we went into production, confirming the validity of our plan to move the rest of our SAP environment to SLES.”
Building on the success of this initial migration, ARaymond has turned its attention to migrating other non-core SAP applications to SAP HANA, including HR and CRM. With these projects under its belt, the organization will be well prepared to complete the migration of its production SAP ECC environment to SAP HANA.
ARaymond is currently running four production instances of SAP HANA — one for each group of mission-critical SAP applications. Rézé comments: “SAP publishes a matrix of compatibility to show which applications can share the same SAP HANA instance. Because of the mix of applications we run, we need to have four multi-tenant instances in production, and we have further instances for testing and development. Of course, it’s really two sets of four production instances, because everything is replicated in our second data center.”
To enable rapid recovery in the event of a disaster and to facilitate planned shutdowns for system maintenance, ARaymond uses server clustering within each data center (powered by the SLE High Availability Extension), and it replicates SAP data at the level of the SAP HANA database between the two data centers. Rézé comments: “We handle the DC-to-DC replication at the database level because this enables faster restarts. Without the SAP HANA data replication, in the event of a restart, we would have to allow an extra 15 or 20 minutes to get all of the SAP database into memory in the second data center.”
The infrastructure in the two ARaymond data centers are identical; if any workload is restarted in another center, the organization will continue to run it there until the next failover exercise. This means both data centers can support the SAP production workload at any given time.
For any major migration project, it is common to bring in external support in key areas, and ARaymond’s SAP HANA migration was no exception. The company continues to work with two partners: TeamWork and Delaware. “We worked initially with TeamWork to plan the project, to procure and install the new server and storage hardware, and to procure the SUSE licenses,” says Rézé. “The configuration and setup of SAP HANA was mostly in collaboration with Delaware — although TeamWork also has competence on the software side and provided training for our technical teams in managing SLES.
We have had a positive experience working with both partners, as well as directly with SUSE in pre-sales — everyone we’ve encountered has been highly professional and a pleasure to work with.”
Knowing the migration to SAP HANA would add significantly to its virtual server landscape, ARaymond planned from the outset to deploy SUSE Manager to simplify the implementation and management of virtual machines (VMs). The company is currently managing around 100 SLE VMs (running on the VMware hypervisor across 12 physical servers).
Coste comments, “SUSE Manager is easy to use and is saving us time in deploying new virtual servers. It also helps us manage the standardization of configurations across servers, which helps with reducing the complexity of our SAP landscape.”
ARaymond is successfully forging ahead with its strategic migration to SAP HANA on SLES for SAP Applications with the SLE High Availability Extension. The SUSE technologies help keep costs under control, simplify system management, and provide a stable platform for the continued growth of the SAP landscape.
“With SUSE, all the components we need to run SAP HANA are included in the single license for SLES for SAP Applications,” comments Coste. “This helps keep costs low as we expand our SAP landscape, while reduced administration frees up staff resources to focus on migration activities and on optimizing our business services.”
Thanks to the SLE High Availability Extension, ARaymond’s SAP HANA landscape is very stable — an important consideration for a global business serving manufacturers in just-in-time industries. Indeed, as part of ongoing technical discussions with SUSE, ARaymond is planning to implement SLE Live Patching. This technology should further reduce scheduled downtime by enabling ARaymond to apply kernel fixes without service interruptions.
Coste says: “Our experience suggests that SLE will provide a stable, secure and reliable platform for our entire mission-critical SAP landscape — both the applications and the SAP HANA databases.”
Naturally, adopting the in-memory SAP HANA database has already significantly improved performance, eliminating delays in running SAP BI reports. This helps give users an early indication of the longer-term strategic value of the migration.
Rézé comments: “The improved SAP BI performance is of course nice to have, but the real value of the migration will come later, when we are able to look at deploying the new SAP S/4HANA applications in areas such as finance and logistics. We’re still really just at the first step, getting the future platform in place and making sure it’s stable.”
For ARaymond, the introduction of SLE alongside Microsoft Windows Server has gone smoothly — so much so that the organization is now looking outside of the SAP environment at other candidates for OS migration. “We have some other systems in the migration pipeline now because our experience suggests that Linux is generally stabler and easier to manage than Windows,” says Rézé. “Before the SAP HANA project began, perhaps 2% of our servers were on Linux, whereas today we are at about 20%. At the end of the process, we expect the proportion to hit 35%, making SLE a truly strategic platform for ARaymond.”