Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Inside SAP Cloud ERP

Inside SAP Cloud ERP artwork

Inside SAP S/4HANA Episode 93: Syntax Accelerating High-Performance Batteries and Mobility Customers with Cloud ERP

Sep 6, 202327 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Show Notes: Download transcript as PDF file

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Welcome to our podcast Inside Saps for HANA. There's no Customer success without Product Success and Project Success. Today we talk about how SAP Partner Syntax accelerates companies around high performance batteries and mobility business with SAP Asana Cloud Public Edition. My name is Mark Sertel and I'm honored to have Roman Freider, Global Center of Excellence, Leader Manufacturing Industry and Director of Presales from

SAP Partners Index on the show today. Welcome to Roman and how are you feeling today? Thank you, Marcus. Great to be on your show today and it's pretty warm outside. We have 31 degrees already, 9 degrees Fahrenheit. How is the weather at home? Where you live, it's also very hot. We have about the same temperature today. It rained a little bit this morning, but the temperature is climbing. Again, Roman, I know you're an expert in driving digital transformations in cloud EP and

digital manufacturing projects. And before joining, actually consulting at the syntax, you worked for an SAP customer and I know you like NASCAR and what else would you like to share in our beginning? Yeah, my background basically starts in manufacturing. So I worked several years for SAP customers, global SAP customers in the automotive sector. I'm a motorsport enthusiast, like watch Formula One yesterday. And then of course NASCAR is also a passion from my side. And a little secret what I could tell you is this is my first

podcast ever and it's a new experience. But I'm also a little bit nervous to be honest. Thanks for sharing someone. I did not notice that you actually were nervous. Maybe before we start to go further into the topic, you can say what syntax stands for and what actually your company does. Thanks. Today's syntax is a leading managed cloud provider from mission critical applications. With our approach, we would like to act as a partique at scale with offices worldwide and over 1000 customers across all business segments.

Syntax has deep and diversified customer based with long standing relationships developing companies and manufacturers. We can also call them Gigafactories or high performance. Battery cells and applications in the vehicle and mobility segment are becoming more and more strategically important. In today's world. We can see improvements and charging capabilities for example or high temperature stability and safety also maybe a lot of Oem's. So the original equipment manufacturers have a big

interest in becoming CO2 neutral at least by 20-30 with local production and supply of material with a low CO2 footprint. Can you maybe share your experience with us how you see the market shifting not only from the classical engine to battery cells, but maybe from the overall market perspective? So the global demand for batteries are increasing dramatically. If we see the forecast for 20-30, it's just rapidly how quick those Gigafactories has to let's say build up from the

Greenfield and with the Greenfield, I mean building a new factory, founding a joint venture etcetera where currently no manufacturing is ever. If we just see how quickly battery sell manufacturer was established the last one or two years, this journey was just the beginning what what we saw. Also what we see where we often is that especially with EV better resells and module, the time to market is very crucial. What does it mean? So in the past if we talk about

our classical big OEMs, they got long journey production implementations like creating a new car takes years of development until serious production. With the EV space, we talk about days and weeks and months. We don't talk about years anymore. How is this so different. So big OEMs, what we all know from the whole world, they founding joint ventures in order to start Greenfield factories or they change their business

dramatically. One of the best example is one of our battery sell projects we've implemented last year. So comparison. To the classical project implementation, we could say in error it was maybe six months of sales cycle and then maybe 9 to 12 months of a project implementation. Nowadays we talk about one to two months in sales and just 90 days of the whole project implementation. This was just possible because of a clear a child approach and focusing on standardization.

And why is that very important if we compare for example typical OVM? And how many variations or how many configurations you have? In a German premium brand configuration you can define 6 rims, 10,000 seat options, etc. If you go to the new EV companies, let's say the car companies, you maybe have ten options. So that means also from that complexity from the manufacturing process and from those options they also go back to less complex manufacturing process in order to drive.

Cheap manufacturing and to be more effective for us as a client. Maybe you can also give us more insights and the important factor within the organizations we heard at speed, maybe the size of the company. The important factor starts within the organization. If you think about a classical OEM with X factories around the globe and very complex processes and integration, the speed is just not within the innovation. Even if the company forgets all the internal topic, it would still not be fast enough.

Also, the approach within the battery cell companies is different. One example is that they will focus on their key businesses manufacturing battery cells modules and not running an IT department with 50 or more employees. Currently we have labor shortage and for the future it would not just be right to build up that big IT department just to manage IT systems. Therefore, it's very important to go with software as a service solution in order to be future proved and out-of-the-box ready

for new requirements. What will come from our customers, Customers Syntax has great success implementing as a PSO on a cloud public edition in the high performance batteries market. Now I'm asking myself and probably a lot of listeners, how do you do it? What is your secret that you're successful? I think the secret sauce is our employees and the mindset of our employees. But I would like to give you our 5 golden rules in order to drive the journey of S for HANA Public

cloud implementation. One is of course the speed of the implementation by using standard processes for example known as best practice or sub model company. This is very important because SAP has over 800 standard best practice scenarios what you could use out-of-the-box. So why do you need to define a special process when there is a standard defined already for you? Second golden rule is you don't have any effort in the upgrades. You don't need to do a five month project in your annual or

BI yearly updates you will get in the past every quarter. Nowadays you get it every half year, some updates and just for example within the February release is a peak game. Customers, over 600 new features, API, new best practices where you as a company can use out-of-the-box. So that means on Saturday there will be the update performed by SAP and on Monday morning, 8:00 AM you start work and 12:00 AM and lunchtime you have the new process maybe already in your production system. I mean this is now a little bit

very easy speaking, the reality looks maybe a little bit different, but that's how cricket could be achieved. The third topic is. That the business value driven implementation of integration and extensions. So that means we don't need every time an IT colleague for making a specification, for making that addition add on etc. Because there are a lot of no code, no code add-ons available where you can build your own report, where you can create your own dashboard, where you don't need to make whatever A5

day specification and you basically have to jump down in four hours by yourself. The fourth option is of course we could reduce our partner or SAP implementation efforts by reusing the capabilities, the best practice scenarios because everything what we learn from a customer can be in the kind like reused. Of course not the specific for this company, but the overall achievement of As for HANA public cloud implementation is basically on the next project

just accelerating because we already know how we've done it. We could reuse the standard documents and can basically accelerate even more. At the last point, we have multiple customer projects already lives in less than 90 working days. And this is very important because we have defined within our HR approach that we have a step by step approach in order to hand over the existing features, what the customer, AIA for example, need. To the business and then continue adding more and more

features and functions in regards to the standard best practice scope items. Those 5 golden rules help us to accelerate, to work with customer, to onboard the customer and basically be rapid, fast, perfect. Holman, thanks for sharing those 5 golden rules. Very impressive. If we look at the most technical challenges in your projects, how did you solve them together with your customers in the high performance batteries market? What do you think? SAP can still improve SAP Aswana

Cloud Public Edition in that market segment? Looking back five years since Svana Public Cloud was available in the old days, called Essential now Public as the product name, I think SAP made significant effort and investment to make the product better. If we look back how we start with customers 19 and 20, we have probably no idea how we solved some of those critical things where there was no technical solution there back in

the days. Nowaday we just can smile and think about how do we solve it back in the days. And there is an hour standard solution since we started this journey with S for HANA Public Cloud. SAP delivered thousands of new features, APIs, best practices, helps us within all of our customer implementation because every customer who runs on the public option gets this new feature and functions. So that means some application or workaround we have implemented back in the days

where we have not a technical solution and maybe now implemented in the standard of the SAP portfolio and we could right now just basically remove the workaround. And use it within the standard. One example is back in the days when we start with our customer smart press shop that were not Prts available for the production order. So that means we got a quick workaround and once 21 this feature was available generally for everyone in February. Then we basically just removed the workaround and we used the

standard feature in less than two days. Also something where I think that SAP can improve. Is especially if we're talking about manufacturing companies and we have in Germany love creative manufacturing from ETO engineering to order to make to order to configure to order all kind of processes out there. And especially if we're talking about high performance batteries, maybe in the beginning there is only one phone factor and one battery to

prove that you can assemble and manufacture the battery and the quality, but. In a very short term you will get more and more complexity and new form factors where you need an PLM system in order to map the design and of course the manufacturing. And therefore I would like to point out two things. One is of course the full engineering to order support where we have order complex and VIP changes etc. And of course one of my favorite features is the external PLM integration.

Looking forward to get my hands on the test system. To see what will be shipped out with the new release. But this is let's say one feature where currently the customer landscape maybe got an SAP PLM, maybe an external. But now with this feature of connecting external Plms, you have the full flexibility and process integration from design to manufacturing and later on of call to shipping like supporting the complete process designed to operate Google. And I also learned that at a later phase you implemented SAP

digital manufacturing. What are the main processes or capabilities that are used with our product and what is the best approach for fast and successful implementation there for the high performance battery industry? Thanks that you mentioned the sub DM product. One of our sweet spot is of course the combination of S for HANA Public Cloud in combination with SUB, DM and other apps like SAP SAC. Or QER because we define ourselves as a boutique at scale where we can help our customers

with our deep knowledge, especially of integration. Top floor to shop floor and very important since we made the journey from the on Prem to the cloud world, the UI looks more or less the same. We have Fiori overall within all the apps, so that means unique user experience for shop floor worker is very important because. Why do I need to log into five different system if I have one job? We can't explain this to the

colleagues, so therefore it's important that maybe an app is in As for to be executed another app, for example is it the DM sector executed and talking about especially for battery cells. In the future, every battery cell company in the world has to follow the Battery Passport which is a kind like ID from the mine. To the OEM and back to recycling. So that means it's like your Facebook of the batteries, your diary, everything, what will be assembled, raw material etc has

to go in and therefore it's very important because the machine who builds that products with the chemicals with the raw materials, this will be a high speed production process. So that means there will be no human being interacting, everything will be serialized and all of those data will be collected via the sub DM application. Will be then forwarded of course to the Asforhana cloud in order to have the data for shipping etc start and maybe all the data goes to the Catina X or other battery apps.

What will be developed nowadays? And therefore it's very important to have the combination to support your enterprise with the Asforhana public and of course to support your shop floor. With the sub DN we set it nicely from top floor to shop floor and let's move from there. More on the subject of extensibility and how do you handle extensibility in your projects? Maybe not even only in your high performance batteries projects, but also in other Saps or high cloud public edition

implementations. Something what was a myth in the past and probably still in a lot of brains, basically like engraved. The myth is that. As for HANA, Public Cloud only works for small companies. It's not flexible enough for my needs. We can't modify this. It's not that flexible and modifiable as a classical As for implementation or also known as As for HANA Cloud Private Edition. If we talk about this, I think my clear is absolutely different

because since last year, especially when SAP released a lot of new. And on our extension possibilities, my view is clear. If you wanna have a state-of-the-art cloud European, there is no way, why not put S for HANA cloud for your future European system. If we're looking to the innovations and the cycles what SAP put in, I think this would be my horse where I put my money on. If we compare it to NFL. We talked about sports earlier. Marcus, if we talk about S4,

this is Tom Brady. A very good quarterback, you will probably win everything. But As for Hana Cloud is maybe pet Mahomes. So that means yes, he won the Super Bowl, maybe you throw some interceptions. What means not everything is perfect at the beginning, but every year when we grow, the product will be better and therefore you need sometimes some creativity to use some fields. What are existing? One example is for example if we talk about logistics.

And we have a fixed handling unit because we have engraved number on our handling units. Problem in the standard is you create a handling unit and the system will automatically create a dynamic handling unit number for us all for the client. How did we help? We basically created a handling unit with the random number what was created and we created a plant maintenance equipment number. And this plant maintenance equipment number will be fixed every time and then we map the. The handling unit and the equipment number together that we have the fixed number, what

is engraved at the handling unit physically and we have the variable number, what was generated by the system so we could use all the standard apps. We have a lookup table for the real engraved number and everyone was happy. So that means customer was happy, we were happy at this workaround, cost us a couple days of work and let's say brain knowledge and basically it solved exactly customer needs. Nevertheless, we also find out that some of those apps are maybe not just specific for one customer, where we put in some

syntax IP in order to help customers to be better, faster, etc. And I would like to point out three apps, what we have created in the past and what will be enhanced every quarter basically with new features and functions. The first one we call it internally Logismal. This is a BTP app what makes every logistics workers. State tasks easier. We have created a very intuitive mobile screen optimized for mobile barcode scanners. We use the Fiori but our big buttons are basically triple

size of the normal Fiori buttons you know from the Uis. This also helps support by using those device basically driving on a forklift and of course wearing a glove where you maybe need bigger buttons because you don't hit the detail button. Perfect. The second app is that we have also some customers. They basically after the end of the manufacturing run they need to confirm the yield and scrap within the sub DM application. They also need to do the logistics booking and probably also have a quality inspection

by end of the day. So that means the reality would be that you have 4 apps, DM S for HANA, EWM and maybe a quality app. What we have done with this small app is that we create a small app. You scan this physical handy unit with a bar code in our case for scanning. Then you have a single button of confirming the good parts. If you want to confirm basically a quality, you need to basically check the radio button from value one to value 2 and also press this button.

So that means it's very intuitive also for high speed manufacturing in order to do all the material bookings within the system with basically one scan and one click. The last point is basically integration As for on a public cloud within the Microsoft ecosystem. With this I want to talk about for example integration of workflows, approval of transports, approval of budget etc, whatever you have as a workflow defined, even we can do the side by side. So that means you can create a record in System A and can confirm or approve or deny this

in the software B and then vice versa. And with those, let's say acceleration package, we combine basically SAP products like sub DM like S for HANA Public Cloud with Teams, Outlook or other products of the Microsoft Suite. Very good, very impressive. You as SAP partner if you had a wish from SAP or in your opinion, where should SAP invest a lot of its money in SAP S for HANA Cloud Public Edition? What is your point of view? I have two wishes, 1 wishes for

all of our customer who listen to podcast and one wish of course for SAP. So my wish for all the customers is take that risk to move your existing European, whatever it is an SAP European or non SAP European and take the risk to move to S 400 public cloud. As I said, this is for me absolutely strategic cause where I would put my money on and then work very closely with SAP and syntax together to close those gaps or identify those gaps. So we have a lot of projects.

We have a very close relationship where we work with the sub development together to understand what are the gaps. Are those gaps on the roadmap, Can we wait one or two releases or can we bring this release onto the sub roadmap. This is very important because our lessons learned was absolutely that SAP is open to discuss very creatively with the customer to find also solutions for those gaps and then also solve it within the project lifetime.

My second wish for SAP where I hope that SAP invests a lot of money. As you asked before Marcus, I would like to have complexity reduction. I don't want to talk about products or integration scenarios. Basically if we talk about scheduling, just scheduling of orders, of parts of Labor of whatever, There are currently a lot of products in the market, sub or non sub and currently some of those products have also overlap or also a feature restriction.

My wish for the future is that we simplify or SAP simplify this to make it easier for the customer to jump on and of course for SAP to save development resources. Thanks for your feedback. Most of the high performance batteries companies are new to SAP as their startups. And how is your feedback from your customers on user experience? Do they like to work in SAPS? Partner. Cloud public edition. If we talk about let's say new customers, I mean the persons

are not new, even if it's a startup, they not just hiring young colleagues from the university with no experience, the people have also some experience from their previous job, maybe with or without SAP as an ERP system. I think the way of getting trained into the S 400 public cloud, especially since last August when SAP released the Horizon theme, the way of how to work within the apps and the information comes to you is absolutely different than if you

worked in the past with the ECC and you know every T code basically out-of-the-box and you typed it in. So therefore the people demand this new UI and from my point of view SAP especially with the UI have to be as easy as an Apple iPhone. That means there should not be a manual available because everyone knows intuitive how to work with it. By the way, Marcus, have you ever found out if Apple has a manual for their phones?

It's a good question. I've never used one because it's that easy and that's also important for moving forward. It has to be easy. No manuals, No 10 clicks that everyone can use it. Very good. Let's keep this in mind before we come to the end. One last question. If you had one wish, what would it be? Thank you, Marcus. From my side, no open questions. I basically throw it out a second ago with my manual idea. I think all the investments what we saw at the Sapphire also with the new AI integration, I think

my last wish would be that if we can combine this new AI technology and the SSAP technology to do like ASAP, Can you show me where I lose money? What is the highest demanding cost center as one idea and the system shows you exactly, well, Romans Presale cost Center is the highest cost center in the company. You need to look at labor, Just one example. Another idea is can you please create a report for me with the sales figures of the last

quarter and I would like to point out the top 10 customers and the system automatically builds through that report and you just have to say safe. Sounds very good. I like your creativity. I like your ideas. I really enjoyed this podcast with you. Thank you so much Roman again for your great insights today. Marcus, thanks also from my side. It was great to talk to you about battery S for HANA. So text and SAP. Thanks Roman, and as always,

feel free to drop us an e-mail via inside S4 at sap.com and let us know which topics are of your interest. In next time and be inside SAP S for Han.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. TechEd #10: How Joule Studio and n8n Orchestrates Enterprise AI

    Nov 20, 202616 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets into one of the most significant partnerships in the SAP ecosystem right now. Host Yannick speaks with Vladimir Shakhov, Strategic...

    • Apple Podcasts

    Credit the people on this episode

  2. TechEd#9: How AI Transforms Cloud ERP Migrations

    Nov 18, 202614 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode takes a refreshingly grounded, practitioner-first look at what AI in SAP really means in the field today. Host Fernanda speaks with Wouter Lemaire, independent...

    • Apple Podcasts

    Credit the people on this episode

  3. TechEd #8: The Benefit of Laying the Groundwork for AI

    Nov 16, 202615 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP brings something the series hasn't had yet: the perspective of an actual large enterprise customer architect, not a consultant or partner....

    • Apple Podcasts

    Credit the people on this episode

  4. TechEd #7: The Hidden Risk in Every SAP Transformation — Organizational Change Management

    Nov 13, 202618 minAudio

    Recorded live at SAP TechEd, this episode of Inside SAP Cloud ERP zooms in on the dimension of SAP transformations that gets the least attention - and causes the most damage when ignored: Organizational Change...

    • Apple Podcasts

    Credit the people on this episode

  5. TechEd #6: Five Days to a Working AI Solution — Inside SAP's Forward Deployed Engineering Model

    Nov 11, 202623 minAudio

    Recorded live at SAP TechEd 2026 in Berlin, this episode of Inside SAP Cloud ERP gets to the heart of what the autonomous enterprise actually looks like when it's working. Host Yannick speaks with Sindhu Gangadharan,...

    • Apple Podcasts

    Credit the people on this episode