Series 2
SAP BRIM
Acuiti Talks - Episode 02
The Anatomy of BRIM Implementation.
In this episode, Rishi Singh, Head of SAP Practice at Acuiti Labs, dives deep into the technical side of BRIM implementation. He explains the key components that drive a successful BRIM rollout, including system architecture, integration with existing processes, and workflow optimization. Rishi also discusses the practical challenges companies face during implementation and provides insights into streamlining the process for better efficiency and effectiveness. Whether youâre looking to understand the intricate details of BRIM or need strategies for overcoming technical hurdles, this episode offers valuable takeaways from a seasoned expert.
Subscribe to our channel
Transcript
Hello and welcome viewers to another episode of our podcast series, Acuiti Talks, your go to podcast, where we delve deeper into some creative and very interesting insights about the world of business finance transformation in this series and this episode particularly, we are continuing our conversation with our special guest, Rishi, who is the lead and head of SAP Practice at Acuiti Labs. So welcoming Rishi, once again.
Thanks Rhea, always excited, to get into this conversation with you.
That’s great. So I think throughout the episode one, we covered a lot about BRIM, which is SAP BRIM in somewhat details, but I think now the next step would be to give our viewers an insight about the more technical aspects of, you know, BRIM, and what goes around when you do think about a BRIM implementation for a certain company. Would you like to shed some light on that?
Definitely. When we talk about transformation, we should talk about implementation as well. And for SAP engagements, including SAP BRIM, SAP recommends activate methodology.Which we definitely have custom made for BRIM because BRIM is a major transformation for any business. And we’ll talk about this in detail. When we talk about the different phases, typically any implementation would have five phases, starting with the Prepare. And as the name suggests, it’s more about setting up the template for the entire engagement. This will involve, setting up the goals, setting up the governance, defining the project standards and defining product charts, and then identifying the right people who should be engaged and, not only from the consulting side, but also from the business side and then defining their roles and responsibility, because one of the secret sources for a successful implementation is, I think, business involvement from day one.
So if the roles in responsibility is clearly defined, it definitely helps along the way. Yeah. All right. So the prepare would start at, kickoff. Basically to let the entire organization know that we are into this journey. then after prepare, it’s more about explore.
And as the name suggests, it’s exploration of what the current business is doing.So, and this is where we are activate plus comes in. We are a little different to how other companies operate. So rather than running through workshops, definitely, we also do workshops. But our way of running the workshop is a little different. So what we do differently is, that we have all those accelerators in our system. Right? Or if customer is ready with then system, we try to implement to one end to end, scenario in their system, or we utilize our system to do that.
So when we go into the workshops or if we are not talking on the slides, so we are not having this frame conversation, we use the system to demonstrate how the things would look in the system.That makes the conversation very engaging because the business is looking at. You know, how the new system would look like. And also they get the confidence that these guys are aware of the process. They can if they can show this, they can build it. So this is where we get more value from those conversation. So it’s more about defining fit-to standards.
We are not talking about the entire, scheme of work. We’re talking about. There is something we already implemented or Delta we need to do. Right. That definitely gives a heads start, for us on implementation time is little smaller than other engagements. So just because we use those accelerators or, our way of doing explore. Yeah, we are on able to optimize the entire delivery plan.
So explore would typically have those fit to standard workshops, solution validation. Because once we have defined and solution is the key. Yeah. Right. So that validation is very important. Then it’s more about refining the requirements. What delta has to go in. Yeah. And then basically at the end of the explore, we understand what will be the quantum of work. What is the scope of work. Yeah. And, will it be a right approach to go a big bang for all the line of businesses or we should, have it phase wise? Yeah, right. And, that all is discussed. We decided in collaboration with the business because finally they have to take that ownership right after the go rollout.
So after this, it’s realized. All right. So at the end of prepare phase, we have a refined backlog, right, of what has to be done. We have got the likes of a very technical word in SFP that talks about what delta configuration or system will we have to do. Yeah. When we get into the realized phase, this is where, actual configuration and action will happens. So the establish a solution landscape wherein now we start developing the solution on incremental build approach. And when I say incremental build approach and about we do us a bit which can be demonstrated to the customer. We do demos, of those scenarios to the customer. So that very early in the journey they get to see what their to be solution is and if they have any observation with respect to that or any debug, that all is taken refined and next time and come back, they can see that happening.
So they are more engaged. They are giving that input. So that is one of the thing during so realize is where a lot of tests happen just to ensure that the component is working. Then we get into a system integration test, which is end to end, because, if we talk about usage based billing. The users will be coming from somewhere, correct? Correct. So that integration also has to be tested. It’s just an example. If we go into our actual scenario, there could be multiple system to which SAP BRIM would be talking to, we do have experience of integrating CPQ not only from SAP but any of those CPQ.
On political engagements we have, integrated with Salesforce as well, because there are companies who are using Salesforce for their contract management. So we have experience of integrating that seamlessly that with BRIM, which is again, very niche. Very few SIs might have done it. We have experience, but then we also strategize and start working on data migration. And the plan around the customer so typically realize phase would be a long phase in which we are building the solution on a incremental basis for the customer. Once we are done with, it’s more of a deploying. And as the name suggests, we are deploying. So we are moving. Well, the production will be set up, will move all the code configuration to the production system, and then, it can be migration administrator, it’s customer mostly done transaction of data and then a customer as well.
But in, customer doesn’t have to pay for dedicated resources. So what we have seen is they are engagement, which are, typically heavy on the finance side. There could be engagements which are complex on the contract side. So depending on the nature or where the complexity lies, customer doesn’t need to have dedicated resources even though they are not they are not much issues to deal with.
And this is where our offering in this space is also very innovative in a way. I would say, because what we agree with the customer is, a baseline FTE mode based on that committed FTE business based on their requirement can request for let’s say more on the finance side, less on the contract side. So they have that flexibility depending on.
And also let’s say when we are towards the financial closer on month end, definitely the focus will be more about financial closer. Right. So at that point in time they can request for more people or more availability of people. On the finance side, whereas through the month, if they are talking about more of customer acquisition, they can request.And so that all can be planned. So customer in a way is not paying for dedicated resources. They are paying optimally for what they are using. Right. So the way we are talking about usage based model. So something very similar in the aim is offering for mind.
That’s interesting. I think in a way you very beautifully captured the entire Acuiti approach towards, you know, our implementation services and overall. So thank you for that. That was really great. I think moving on. What we can cover is probably for the viewers, the, let’s say the technical people and CFOs of the world who are actually maybe looking to implement BRIM. Maybe if you could shed some light over the key components of BRIM, because I think we have covered lots from the implementation perspective.
But if we want to get into more technicalities, would you like to shed some light on the key components of BRIM?
If we talk about, The entire BRIM suite, it will have 5 or 6 components to it. It starts means.There is a module which is called subscription order management. As the name suggests, it’s to manage on the contract lifecycle. Not only managing. It also tracks the services usage. It’s specifically designed to support order process, for a combination of, physical good services subscription which enables the transition from a product based on to a service based model. This is what we are trying to achieve through,
BRIM implementations. Right? It would also support your, different type of product modeling and pricing modeling.
It also maintains a master service agreement, which you need to be done with all the customers. It also supports, quoting and capturing the order and the system, and then also has functionality for revenue sharing because, every organization have for subcontractors or agencies working for and BRIM also facilitates revenue sharing.
So let’s say for a customer, you use someone else’s service or you don’t want, we want to track it. Right? So if you’re talking about process automation, even that should be automated, right. So what service customers avail and what your third party or vendor have service to the customer. Everything is getting captured. And what is their revenue share is automatically calculated the moment the services provided. So when we talk about the process optimization we are not talking only from the company per say, but also anyone means any vendor engaged in also becomes part of that automation process.
Then on the second component is Convergent charging. Very powerful tool. It’s a no code tool which is designed to manage customer pricing, and also supports partner revenue share. It operates at a very low latency. High volume and is highly available. Correct. It also offers allowance or allowance management for the service and product because we are talking about not only B2C, it would be to be as well, but an on the progress could be complex. And they even in B2C scenarios right there are allowance that is which all gets on managed sources. Very strong very powerful tool for any type of pricing you want to build in with no code required. It’s a strong third component, is basically convergent invoicing, which is as the name suggests, it’s a invoicing tool, which enables billing and invoicing.
Of all the price of charged item, which has come mostly from convergent charging. It facilitates the creation and distribution of consolidated and personalized invoices. Correct. We talked about B2C and B2B, right. When we talk about B2C, you can have a generic invoice going to the customer. But if you if you are referring to B2B, every customer can have their own aggregation or grouping logic, all that is visible or using CI.
So if you have different contracts, if business is looking for a different grouping rules or all can be customized, within year. Okay. Also has a very powerful, process, which is called performa invoice from preliminary invoice, which is a stage before the actual invoice. So that again, B2B scenario within, we have to be very careful about, what we send to the invoice.
Because if the invoices are of, let’s say $1 million. Yeah. We need to review it carefully. Otherwise if it gets into dispute, then DSOs will get impacted. Right. So, very powerful because you get to assess, the components of that invoice and then know that this feature actually, the chances of disputes reduces significantly. And, just on the off track, even the dispute management system in BRIM is very powerful. So, when we talk about this B2B scenarios, the invoices could be of million dollars if there is a dispute for, let’s say, one service or two service, we should not hold the entire invoice. Correct. And BRIM comes with Dispute management also has been customer can dispute on the line items. Right. So that at least only that is disputed.
And customer can pay for the entire money, which is good for the business as well because the entire invoice is not outstanding. Right. The the next component is, contract accounting, which primarily is the ledgering system. So once they voices are done, all the other business processes from their accounting to the payments facilitation, payments would mean on the online payments, the funds, payment failures like returns then write offs all means debt collection process. Everything is managed through a module within BRIM. Then we all this we are talking about this usage thing, right? BRIM is not meant for, usage. Usage will definitely be coming from a different system. It could be a terminal operating system, for example, for a port industry, it could be a AODB for, airport industry.
So we have got a middle layer which is called convergent mediation. Which is primarily for, data acquisition. And again, it’s a very powerful tool. Do it’s from DigitalRoute, but it integrates with BRIM, as if it’s a native product of SAP. So a lot of enrichment, a lot of validation can happen, can be enabled within, convergent mediation, because of which the data which is coming to the system for charging, billing, are validated and we are getting correct mature data. Where in the chances again of reducing on disputes or error invoices reduces significantly. So these are primarily the modules within, SAP BRIM from the offering perspective depending on business requirement. Right. Everyone talks about value for money. So SAP is also have been offering modular way. Or you can even say I like our way of selling things.
So not necessarily we need to buy the entire full suite of BRIM. We can pick and choose what we want. So there are organization for only, let’s say using CI. There are organization who are using only FICA. So it’s CC, CI, FICA. So all sort of combination is available. Totally depends on what a customer wants. So that they are not paying for what they’re not using. Like oh. And then BRIM sits over S4. So one of the basic integration requirement is that FICA acts as a sub ledger. And as a standard integration process, to the FI every day and we consolidate or whatever has been invoiced within the system, whatever payment has been received in the system and only the consolidated entries pass to the main FI ledgers. And so that way, the volume of data flowing from the sub ledger to the main ledger is controlled.
Yeah, I think that is a very interesting sort of approach or thing that we are currently following. And if you think about it, the Acuiti labs, the leaders in BRIM. So I think it reflects very nicely how you portrayed the entire process and the component and also the fact that, you know, we have a few unique approaches that we follow when we do look at different clients.
So that I think that was very insightful. Thank you for that. And I think I wouldn’t call it an end, because we do plan to call you again and talk about another, you know, kind of expanding on this topic that we are currently talking about and maybe talk more about the challenges that, you know, companies might face during the implementation stage and probably where the future of this product is headed. So very excited to have that conversation with you. But I think until then, it was really great to have you on board today.
Thank you. Rhea, thanks. Thanks a lot. A good conversation and hope to see you again in the next episode.
So with that viewers, we call an end to our episode two of our series, Acuiti Talks. We will definitely come back with another episode for this series, which will highlight more of the challenges and, you know, the future of where BRIM is headed. As well as what Acuiti is going to bring to the table. So until then, we’ll see you soon. I’m your host, Rhea. Goodbye. Thank you.
