BAT’s journey to a single company-wide SAP system

When one of the world’s biggest tobacco companies decided to bring all its entities onto the same enterprise resource planning system, there were some challenges along the way. Zanders brought its expertise to bear, to help design, test and go live with the chosen system - and ultimately make the SAP implementation a success.

British American Tobacco (BAT) was founded in 1902 as a joint venture between the UK’s Imperial Tobacco and the American Tobacco Company. In its 110 years of business, BAT has grown considerably through acquisition to become the world’s second largest tobacco firm and a top 10 FTSE 100 company with 183 companies around the world. One of the biggest acquisitions of recent years was the purchase of Rothmans International in 1998. Its biggest brands include Lucky Strike, Pall Mall, Dunhill and Kent cigarettes.

Gavin O’Dowd was the Project Lead for the Treasury part of the SAP implementation project based at BAT’s London headquarters. He says: “Until now, BAT had never integrated their business cohesively into a single model within our financial operating system. We therefore decided to launch two programs to achieve this.” The first of these programs was to roll out a single ‘Target Operating Model’ (called project ‘TOM’), while at the same time supporting this with a single SAP system across the company (called project ‘One SAP’). BAT treasury has been using SAP since 1999, but different business units were using different versions of the application. These two projects were combined and became a single global program called TaO (Tom And One SAP). Tao is the Chinese word for ‘path’ or ‘way’ - which is apt since China is BAT’s biggest single market, and has 40 percent of the world’s smokers.

As a system becomes more bespoke, it also becomes more complicated to update and maintain

Gavin O’Dowd - (BAT - Project Lead for the Treasury implementation)

Designing project TaO

The aim of project TaO was to create a template for all of BAT’s operations. It was a complex, multi-pronged project involving several departments across the group, not just treasury. The other departments involved in the project included financing, operations, and marketing. BAT’s Dutch entity had been a Zanders client for several years prior to project TaO, so the consultancy was asked to join and began working on the design phase of TaO in April 2011. While the TaO project involved a company-wide SAP implementation, the Zanders team worked exclusively on the SAP Treasury & Risk Management, Bank Communication Management (BCM), and In-house Cash elements of the project. Judith Wissink is a Zanders consultant who managed the implementation of the SAP Treasury & Risk Management module and worked closely with the BAT treasury team throughout the project. She says that the team had to work quickly to understand what was needed: “One of the biggest challenges was that BAT had been thinking about the new system and how they wanted to work for 18 months before the actual project started. So we had to get up to speed quickly. We needed to fully understand BAT’s requirements before we could begin designing the system.”

Zanders worked with BAT on designing the future software architecture for all of BAT’s entities. First of all they created the templates for this. BAT’s O’Dowd says: “The first challenge was to define the overall goal of the project. What did treasury want to achieve? We had to consider the structure of our treasury, as BAT has some huge foreign currency exposures because we function in pound-sterling, although we make relatively little profit in our operations in the UK.” He adds: “The next thing was to be clear on the benefits for treasury and to always make decisions with that in mind. All the benefits were quantified and were considered in terms of risk reduction.”

Creating a bespoke but balanced system

While SAP was BAT’s chosen system, it didn’t provide all the functionality that the group required. Some custom development and design were therefore needed. O’Dowd explains: “The second challenge was that SAP did not give us all the capabilities that we needed and so we had to create some bespoke functionality. We needed to strike the right balance though - as a system becomes more bespoke, it also becomes more complicated to update and maintain.”

There were several enhancements to be made during the implementation project. One of these was the part of the system called Deal Optimiser. Zanders was responsible for the system design of the bespoke elements of the system and it collaborated with developers on the realization of that part of the project. BAT had a very specific vision of what it wanted to achieve through the TaO project and this made certain aspects of realizing the project quite challenging. The build phase began in September 2011 and involved customizing the standard SAP system and building the bespoke part. This also posed a challenge because treasury was part of the bigger company-wide project. At various stages during the build phase, this required close alignment between the treasury workstream and the other ‘workstreams’ within the TaO project, as a lot of processes were interdependent. As well as the Treasury Module, SAP In-house Cash and BCM also needed to be customized. The customization of In-house Cash and BCM was managed by Zanders’ Mark van Ommen. Both Deal Optimiser and In-house Cash had a large geographical spread and the latter has now been completely rolled out across the company. Deal Optimiser is also live across 90 percent of its target end users.

The ‘fit-gap’ analysis

The treasury system template was designed to fit the needs of global treasury in which most of BAT’s treasury activities take place. To make sure the template also fitted the end market’s requirements, BAT Malaysia was chosen as a pilot company. Once the template design was complete, the template needed to be evaluated against the exact needs of the Malaysian company, one of BAT’s top 10 end markets. This phase of the project was referred to as the ‘fit-gap’ phase and its aim was to see if the template would meet the company’s specific needs and if any changes to the template would be necessary. Wissink explains: “After the fit-gap analysis we started to actually build the system for the entities in scope. This was our first proof of concept for the designed template.”

Ironing out the bugs

Both the design and the testing phase were key stages of the project. Once the system had been designed, customized and built, three rigorous testing cycles were carried out. These consisted of an initial technical test cycle carried out by Zanders consultants (unit testing); an integration test cycle conducted by the consultants and BAT’s staff; and the user acceptance testing stage with BAT’s key users testing by themselves.

O’Dowd says: “During the testing phases we got rid of a lot of bugs - to the point where there were none.” BAT’s key users were the group’s central treasury and central accounting departments based in London, the Romanian shared service center, the treasury and shared service center in Malaysia, as well as other end markets. After these testing cycles, the design and build of the system was signed off.

At each stage of the project, there was a strong focus on documentation and support. Wissink explains: “During each phase, we documented all the settings that we made, and explained the logic behind the settings for the future support team to be able to maintain the system. We also produced training material and user manuals.”

Team work

The go-live date was the third of September 2012. O’Dowd notes that there were no major issues with the SAP systems after go-live (during the after care phase): “We had done so much testing that this went smoothly.” However, there were other challenges during the pre-go-live phase for treasury in Malaysia. O’Dowd explains: “It was a challenge to get bank connectivity ironed out in Malaysia. In the end, the banks resolved any problems in a satisfactory way.”

A team of 14 Zanders consultants worked on the project, while BAT had a team of 25 in place for the testing phases of the projects. Deepak Aggarwal was the overall project manager for Zanders and both Judith Wissink (who managed the SAP Treasury & Risk Management implementation) and Mark van Ommen (the In-house Cash and Bank Communication Management modules) and their teams reported to him. O’Dowd says: “Zanders were a young and dynamic team. Deepak Aggarwal had some fantastic experience, which really boosted the design process. Judith van Paassen, partner at Zanders, was also involved and was able to influence at a high level at BAT, which helped us enormously. All the consultants showed great expertise in the areas of In-house Cash, bank connectivity, and the SAP Treasury module.”

Ambitious plans

BAT is ambitious for the future implementation of the TaO program. Over the next three years, it intends to roll out the SAP system to more than 120 countries. The In-house Cash module has already been rolled out to 62 countries and is now processing 60,000 transactions per month. Deal Optimiser is live in 25 countries.

O’Dowd says: “Overall, the program has been a roaring success. The smoothness of the go-live was second to none. The attention to detail during the design, testing, and pilot cycles really paid off, so I would really emphasize this to people starting out on a similar project.”