Friday, February 05, 2021

How Storage Can Help You Digitally Transform in a Hybrid Cloud World

A transcript of a discussion on how consistent global storage models best accelerate and enable pervasive analytics that support digital business transformation. 


Listen to the podcast. Find it on iTunes. Download the transcript. Sponsor: IBM Storage.


Dana Gardner: Hi, this is Dana Gardner, Principal Analyst at Interarbor Solutions and you’re listening to BriefingsDirect.


Our next data strategies insights discussion explores how consistent and global storage models can best propel pervasive analytics and support digital business transformation.


Decades of disparate and uncoordinated storage solutions have hindered enterprises’ ability to gain common data services across today’s hybrid cloud, distributed data centers, and burgeoning edge landscapes.


Yet only a comprehensive data storage model that includes all platforms, data types, and deployment architectures will deliver the rapid insights that businesses need.


Stay with us now as we examine how IBM Storage is leveraging containers and the latest storage advances to deliver the holy grail of inclusive, comprehensive, and actionable storage.


To learn more about the future promise of the storage strategies that accelerate digital transformation, please join me now in welcoming our guest, Denis Kennelly, General Manager, IBM Storage. Welcome, Denis.


Kennelly: Thank you, Dana. It’s great to be here.


Gardner: Clearly the world is transforming digitally. And hybrid cloud is helping in that transition. But what role specifically does storage play in allowing hybrid cloud to function in a way that bolsters and even accelerates digital transformation?


Kennelly: As you said, the world is undergoing a digital transformation, and that is accelerating in the current climate of a COVID-19 world. And, really, it comes down to having an IT infrastructure that is flexible, agile, has cloud-like attributes, is open, and delivers the economic value that we all need.


That is why we at IBM have a common hybrid cloud strategy. A hybrid cloud approach, we now know, is 2.5 times more economical than a public cloud-only strategy. And why is that? Because as customers transform -- and transform their existing systems – the data and systems sit on-premises for a long time. As you move to the public cloud, the cost of transformation has to overcome other constraints such as data sovereignty and compliance. This is why hybrid cloud is a key enabler.


Hybrid cloud for transformation

Now, underpinning that, the core building block of the hybrid cloud platform, is containers and Kubernetes using our OpenShift technology. That’s the key enabler to the hybrid cloud architecture and how we move applications and data within that environment.


As the customer starts to transform and looks at those applications and workloads as they move to this new world, being able to access the data is critical and being able to keep that access is a really important step in that journey. Integrating storage into that world of containers is therefore a key building block on which we are very focused today.


Storage is where you capture all that state, where all the data is stored. When you think about cloud, hybrid cloud, and containers -- you think stateless. You think about cloud-like economics as you scale up and scale down. Our focus is bridging those two worlds and making sure that they come together seamlessly. To that end, we provide an end-to-end hybrid cloud architecture to help those customers in their transformation journeys.


Gardner: So often in this business, we’re standing on the shoulders of the giants of the past 30 years; the legacy. But sometimes legacy can lead to complexity and becomes a hindrance. What is it about the way storage has evolved up until now that people need to rethink? Why do we need something like containers, which seem like a fairly radical departure?


Kennelly: It comes back to the existing systems. You know, I think storage at the end of the day was all about the applications, the workloads that we ran. It was storage for storage’s sake. You know, we designed applications, we ran applications and servers, and we architected them in a certain fashion.

When you get to a hybrid cloud world ... If you're in a digitally transformed business, you can respond rapidly. Your infrastructure needs to respond to those needs versus having the maximum throughput capacity.

And, of course, they generated data and we wanted access to that data. That’s just how the world happened. When you get to a hybrid cloud world -- I mean, we talk about cloud-like behavior, cloud-like economics – it manifests itself in the ability to respond.


If you’re in a digitally transformed business, you can respond to needs in your supply chain rapidly, maybe to a surge in demand based on certain events. Your infrastructure needs to respond to those needs versus having the maximum throughput capacity that would ever be needed. That’s the benefit cloud has brought to the industry, and why it’s so critically important.


Now, maybe traditionally storage was designed for the worst-case scenario. In this new world, we have to be able to scale up and scale down elastically like we do in these workloads in a cloud-like fashion. That’s what has fundamentally changed and what we need to change in those legacy infrastructures. Then we can deliver more of our analysis-services-consumption-type model to meet the needs of the businesses.


Gardner: And on that economic front, digitally transformed organizations need data very rapidly, and in greater volumes -- with that scalability to easily go up and down. How will the hybrid cloud model supported by containers provide faster data in greater volumes, and with a managed and forecastable economic burden?


Disparate data delivers insights

Kennelly: In a digitally transformed world, data is the raw material to a competitive advantage. Access to data is critical. Based on that data, we can derive insights and unique competitive advantages using artificial intelligence (AI) and other tools. But therein lies the question, right?


When we look at things like AI, a lot of our time and effort is spent on getting access to the data and being able to assemble that data and move it to where it is needed to gain those insights.


Being able to do that rapidly and at a low cost is critical to the storage world. And so that’s what we are very focused on, being able to provide those data services -- to discover and access the data seamlessly. And, as required, we can then move the data very rapidly to build on those insights and deliver competitive advantage to a digitally transformed enterprise.


Denis, in order to have comprehensive data access and rapidly deliver analytics at an affordable cost, the storage needs to run consistently across a wide variety of different environments – bare-metal, virtual machines (VMs), containers -- and then to and from both public and private clouds, as well as the edge.


What is it about the way that IBM is advancing storage that affords this common view, even across that great disparity of environments?


Kennelly: That’s a key design principle for our storage platform, what we call global access or a global file system. We’re going right back to our roots of IBM Research, decades ago where we invented a lot of that technology. And that’s the core of what we’re still talking about today -- to be able to have seamless access across disparate environments.

A key design principle for our storage platform, what we call global access or a global file system, goes back to our roots at IBM Research. We invented a lot of that technology. And that's at the core of what we're talking about -- seamless access across disparate environments.

Access is one issue, right? You can get read-access to the data, but you need to do that at high performance and at scale. At the same time, we are generating data at a phenomenal rate, so you need to scale out the storage infrastructure seamlessly. That’s another critical piece of it. We do that with products or capabilities we have today in things like IBM Spectrum Scale.


But another key design principle in our storage platforms is being to run in all of those environments -- bare-metal servers, to VMs, to containers, and right out to the edge footprints. So we are making sure our storage platform is designed and capable of supporting all of those platforms. It has to run on them and as well as support the data services -- the access services, the mobility services and the like, seamlessly across those environments. That’s what enables the hybrid cloud platform at the core of our transformation strategy.


Gardner: In addition to the focus on the data in production environments, we also should consider the development environment. What does your data vision include across a full life-cycle approach to data, if you will?


Be upfront with data in DevOps

Kennelly: It’s a great point because the business requirements drive the digital transformation strategy. But a lot of these efforts run into inertia when you have to change. The development processes teams within the organization have traditionally done things in a certain way. Now, all of a sudden, they’re building applications for a very different target environment -- this hybrid cloud environment, from the public cloud, to the data center, and right out to the edge.


The economics we’re trying to drive require flexible platforms across the DevOps tool chain so you can innovate very quickly. That’s because digital transformation is all about how quickly you can innovate via such new services. The next question is about the data.


As you develop and build these transformed applications in a modern, DevOps cloud-like development process, you have to integrate your data assets early and make sure you know the data is available – both in that development cycle as well as when you move to production. It’s essential to use things like copy-data-management services to integrate that access into your tool chain in a seamless manner. If you build those applications and ignore the data, then it becomes a shock as you roll it into production.


This is the key issue. A lot of times we can get an application running in one scenario and it looks good, but as you start to extend those services across more environments – and haven’t thought through the data architecture -- a lot of the cracks appear. A lot of the problems happen.


You have to design in the data access upfront in your development process and into your tool chains to make sure that’s part of your core development process.


Gardner: Denis, over the past several years we’ve learned that containers appear to be the gift that keeps on giving. One of the nice things about this storage transition, as you’ve described, is that containers were at first a facet of the development environment.


Developers leveraged containers first to solve many problems for runtimes. So it’s also important to understand the limits that containers had. Stateful and persistent storage hadn’t been part of the earlier container attributes.


How technically have we overcome some of the earlier limits of containers?


Containers create scalable benefits

Kennelly: You’re right, containers have roots in the open-source world. Developers picked up on containers to gain a layer of abstraction. In an operational context, it gives tremendous power because of that abstraction layer. You can quickly scale up and scale down pods and clusters, and you gain cloud-like behaviors very quickly. Even within IBM, we have containerized software and enabled traditional products to have cloud-like behaviors.


We were able to quickly move to a scalable, cloud-like platform very quickly using container technology, which is a tremendous benefit as a developer. We then moved containers to operations to respond to business needs such as when there’s a spike in demand and you need to scale up the environment. Containers are amazing in how quickly and how simple that is.

We have been able to move to a scalable, cloud-like platform very quickly using container technology, which is a tremendous benefit as a developer. We then moved containers to operations to respond to business needs to scale up and down. Containers are amazing in how quickly and how simple that is.


Now, with all of that power and the capability to scale up and scale down workloads, you also have a storage system sitting at the back end that has to respond accordingly. That’s because as you scale up more containers, you generate more input/output (IO) demands. How does the storage system respond?


Well, we have managed to integrate containers into the storage ecosystem. But, as an industry, we have some work to do. The integration of storage with containers is not just the simple IO channel to the storage. It also needs to be able to scale out accordingly, and to be managed. It’s an area we at IBM are focused on working closely with our friends at Red Hat to make sure that’s a very seamless integration and gives you consistent, global behavior.


Gardner: With security and cyber-attacks being so prominent in people’s minds in early 2021, what impacts do we get with a comprehensive data strategy when it comes to security? In the past, we had disparate silos of data. Sometimes, bad things could happen between the cracks.


So as we adopt containers consistently is there an overarching security benefit when it comes to having a common data strategy across all of your data and storage types?


Prevent angles of attack

Kennelly: Yes. It goes back to the hybrid cloud platform and having potentially multiple public clouds, data center workloads, edge workloads, and all of the combinations thereof. The new core is containers, but you know that with applications running across that hybrid environment that we’ve expanded the attack surface beyond the data center.


By expanding the attack surface, unfortunately, we’ve created more opportunities for people to do nefarious things, such as interrupt the applications and get access to the data. But when people attack a system, the cybercriminals are really after the data. Those are the crown jewels of any organization. That’s why this is so critical.


Data protection then requires understanding when somebody is tampering with the data or gaining access to data and doing something nefarious with that data. As we look at our data protection technologies, and as we protect our backups, we can detect if something is out of the ordinary. Integrating that capability into our backups and data protection processes is critical because that’s when we see at a very granular level what’s happening with the data. We can detect if behavioral attributes have changed from incremental backups or over time.


We can also integrate that into business process because, unfortunately, we have to plan for somebody attacking us. It’s really about how quickly we can detect and respond very quickly to get the systems back online. You have to plan for the worst-case scenario.


That’s why we have such a big focus on making sure we can detect in real time when something is happening as the blocks are literally being written to the disk. We can then also unwind to when we seek a good copy. That’s a huge focus for us right now.


Gardner: When you have a comprehensive data infrastructure, can go global and access data across all of these different environments, it seems to me that you have set yourself up for a pervasive analytics capability, which is the gorilla in the room when it comes to digital business transformation. Denis, how does the IBM Storage vision help bring more pervasive and powerful analytics to better drive a digital business?


Climb the AI Ladder

Kennelly: At the end of the day, that’s what this is all about. It’s about transforming businesses, to drive analytics, and provide unique insights that help grow your business and respond to the needs of the marketplace.


It’s all about enabling top-line growth. And that’s only possible when you can have seamless access to the data very quickly to generate insights literally in real time so you can respond accordingly to your customer needs and improve customer satisfaction.


This platform is all about discovering that data to drive the analytics. We have a phrase within IBM, we call it “The AI Ladder.” The first rung on that AI ladder is about discovering and accessing the data, and then being able to generate models from those analytics that you can use to respond in your business.

We're all in a world based on data. AI has a major role to play where we can look at business processes and understand how they are operating and then drive greater automation.That's a huge focus for us -- optimizing and automating existing business processes.


We’re all in a world based on data. And we’re using it to not only look for new business opportunities but for optimizing and automating what we already have today. AI has a major role to play where we can look at business processes and understand how they are operating and then, based on analytics and AI, drive greater automation. That’s a huge focus for us as well: Not only looking at the new business opportunities but optimizing and automating existing business processes.


Gardner: I’m afraid we’ll have to leave it there. You’ve been listening to a sponsored BriefingsDirect discussion on how consistent and global storage models best propel pervasive analytics and support digital business transformation.


And we’ve learned how IBM Storage is leveraging containers and the latest storage advances to deliver inclusive, comprehensive, and actionable data. So please join me in thanking our guest, Denis Kennelly, General Manager, IBM Storage. Thank you so much, Denis.


Kennelly: Thank you, Dana.


Gardner: And please look forward to when Denis joins me again for the next discussion in this three-part series. We’ll delve beneath the covers to learn more about the actual technologies enabling IBM’s vision for the future of data storage.


A big thank you as well to our audience for joining these BriefingsDirect data strategies insights discussions. I’m Dana Gardner, Principal Analyst at Interarbor Solutions, your host throughout this series of IBM Storage-sponsored BriefingsDirect discussions.


Thanks again for listening. Please pass this along to your IT community, and do come back next time.


Listen to the podcast. Find it on iTunes. Download the transcript. Sponsor: IBM Storage.

A transcript of a discussion on how consistent global storage models best accelerate and enable pervasive analytics that support digital business transformation. Copyright Interarbor Solutions, LLC, 2005-2021. All rights reserved.


You may also be interested in:

Thursday, January 14, 2021

How Capgemini Optimizes Contingent Workforce Agility Using SAP Fieldglass

Transcript of a
discussion on the growing importance of contingent workforces for businesses around the world to satisfy their skills and information technology needs.

Listen to the podcast. Find it on iTunes. Download the transcript. Sponsor: SAP.

Dana Gardner: Hi, this is Dana Gardner, Principal Analyst at Interarbor Solutions, and you’re listening to BriefingsDirect.

Our next digital business innovation discussion explores the growing importance of contingent workforces. As more businesses look to external workforces and services to satisfy their skills and information technology (IT) needs, the ability to manage those workers and services is lagging.

Even as upward of 42 percent of workforce spend is now going to external workforces, many organizations lack visibility into the nature of that spend. As a result, they can’t manage the productivity, nor the risk.

Stay with us now as we hear from a contingent workforce expert at Capgemini on managing the processes that best procure and support talent and skills agility.

o learn more about making the most of a diversified portfolio of workers, please join me in welcoming Andreas Hettwer, Vice President and Group Procurement Category Director at Capgemini in Berlin. Welcome, Andreas.

Andreas Hettwer: Hello, Dana.

Gardner: Andreas, what’s driving the need for external workforce management -- and specifically the role of contingent workforce workers -- there at Capgemini?

Hettwer: We are a big company with roughly 250,000 employees worldwide. At Capgemini, as a consulting digital transformation company, we innovate and address the entire breadth of client opportunities in the evolving world of cloud, digital, and platforms.

And that means we have a huge variety of roles, skills, and capabilities that we need to deliver to fulfill all of these kinds of projects. There are constraints in both capacity and in the niche capabilities needed. Our contingent workforce is part of our strategic component of making sure that we deliver great projects to our clients. This is why we need a contingent workforce program globally.

Gardner: And is the use of IT skills and workers a leader in this field? Is there something about IT specifically that lends itself to a contingent workforce?

IT contingency makes progress

Hettwer: Yes. First of all, from the skills perspective, we are an IT consulting company and therefore this is our major skill set that we purchase from the market. But, again, the variety is huge and therefore we need to make sure that we address all of the different sources to make sure that we have the right capabilities and capacity ready.

Gardner: And how long has this been going on? How long have you been working to perfect and improve the use of such a contingent workforce?

Hettwer: Quite a long time. We began in 2016. At first, we knew our spend of contingent workforce but we didn’t have a clue really about the numbers -- the headcount or the tenure of engagements.

We didn’t know what kind of external capabilities we had acquired from the market, including the roles and skills. We didn’t even know anything about the fulfillment rate or how long it took to source the right capabilities. We didn’t know if we had missed some opportunities to deliver the right projects to our clients.

On the other side, we were not able to understand what we had paid for the individual roles, skills, and levels per country, and whether this was a good price compared to the market. We didn’t know if that helped drive competitive bids toward our clients or not. Given this environment, we decided we needed to change. This is why we then began our global program.

Gardner: Of course, human resources (HR) organizations have had systems of record and processes to manage ongoing, full-time workforces. But when things are project-based and ad hoc, like you are describing, they are often funded from a variety of different budgets and from different elements within the organization.

Keeping track of that is very daunting. Why do you view this less as a HR task and more of a procurement task? How does that help to bring a unified view of all of these different worker spends?

Hettwer: You raise a good point. There is always the question of who owns the contingent workforce. Is it procurement, HR, or maybe the business unit itself? Or is it maybe another function in the company?

It was important that HR had a big focus on our own employees, with our employer brand, and to make sure that we attract the right talent from the market to deliver to our clients with our brand and across our portfolio.

From our perspective, it was important that HR had a big focus on our own employees, with our employer brand, and to make sure that we attract the right talent from the market to deliver to our clients with our brand and across our portfolio.

Contingent workforce for us was a bit of a minor labor component. We are talking about 6 to 7 percent of the complete population of our delivery capacity globally. Therefore we mostly wanted to address cost and risk. Procurement took the lead and came back with the right problem statement, delivered a solution and created the right business case to get executive approval for the global program. That’s how it evolved. We began this program and now procurement owns it.

But again, it’s a good question. It could also be through a different function. But at Capgemini we evolved it and own it right now.

Gardner: Andreas, it strikes me that you are a better organization in terms of fulfilling your mission and supporting your customers when you can find labor best where it exists rather than where you wish it were. How flexible can you be with a contingent workforce? Is this literally an addressable market that extends all over the world? Has the COVID-19 pandemic opened people’s eyes to the potential for more remote and flexible workforces?

Hettwer: Yes, absolutely. First of all, the contingent workforce has increased in the market. If you look at different research -- and even from the Capgemini Research Institute -- you see that the number of contingent workforce participants has increased over the last few years, starting with North America but also in Europe, and even now in Asia-Pacific and in India.

We needed to address this accordingly with some kind of innovation. We therefore developed a global program to make sure that we gain the best contractors in the market and that we use them recurrently.

Looking to the COVID-19 pandemic, we have seen dramatic changes. Suddenly, more clients are open to remote work. Our own organization has been open to remote work. We at Capgemini were able in a few weeks to have more than 95 percent of our own population working remotely. That helped us to really change this work environment and to have more contractors working remotely. So this is something that we need to address further in the future.

Gardner: Yes, COVID-19 has been a motivator and an eye-opener as organizations go more digital, with the ability to use workers regardless of their location. That will become more prominent, I expect.

Andreas, when we use contingent workforces, what are the benefits? What has it done for you at Capgemini?

Remote work benefits

Hettwer: From our perspective, we have four major categories of benefits. The first one is business impact improvement. It’s about fulfillment, making sure that we have the right talent on board and that we can fulfill the needs of our clients. We can therefore make sure that the clients are happy and that our projects will be delivered on time with the right quality.

The second aspect is cost-optimization. It’s always a very challenging market, and we need to be very competitive. Whenever you need contractors, be it for niche or core capabilities to be embedded in our projects, we need to make sure we do it correctly, with the right pricing, so it’s a win-win situation. When we are competitive in using the right contingent workforce at the right price, then it’s also possible to deliver the best pricing for our client. So cost-optimization was a second big aspect here.

hird -- and not a negligible issue -- is risk mitigation. More and more labor laws are coming up right now. And there are many tax-related topics, too. So whenever we can gain more visibility, we can better control our contingent workforce. We can also be sure that risk associated with the use of that labor can be mitigated across markets.

And then the fourth benefit is process efficiency. Bringing in contractors, or services from our suppliers, needs to be seamless -- from getting the right capabilities in, to invoicing, approval, and all what’s necessary. And that must be very efficient, because in an organization like ours, which is global in roughly 50 countries worldwide, we need to have proper, seamless processes end-to-end. Otherwise it’s an administrative burden that you can’t afford.

Gardner: And how about the issue of speed and agility? Oftentimes when it’s a full-time position, it can take months, if not longer, to go through the process of defining the role, hiring, vetting, and onboarding. Is there something about contingent labor that increases the speed and agility when you are satisfying your customers on a project-basis?

Suppliers increase speed-to-hire

Hettwer: Yes, absolutely. And I think this is also the beauty of contractors. You really have the chance to reach out to the market to identify the right contractors on time. And this is also why contractors from time to time come in, because it’s much easier and quicker to get them in, up to the moment until we recruit maybe somebody permanently.

And, for sure, we do this through a preferred supplier base, and this is part of the service-level agreements (SLAs) that we negotiate with our preferred supplier base. This is the speed, quality, and the pricing aspect.

We also invested in our Freelancer Gateway by Capgemini. That means we are addressing contractors directly. We have created the possibility for contractors to check the opportunities that we have on the contingent workforce side and apply accordingly.

But we also invested last year in our Freelancer Gateway by Capgemini. That means we are addressing contractors directly. We have created the possibility for contractors to check the opportunities that we have on the contingent workforce side and to apply accordingly to be part of our extended workforce.

This is very beneficial because more contractors don’t want to go through an external third-party; they want to reach out to us directly. And for us it’s a benefit because we can create an external workforce. We want to build a recurring workforce so that we have a relationship with the contractor market and to make sure that the right people work for us regularly.

Gardner: Now, we mentioned that procurement is the force through which you are operating here, and you have been in procurement for many years. Tell us about your procurement background and why you think the procurement legacy and approach to managing processes and costs lends itself to a contingent workforce management.

Total workforce management

Hettwer: I joined Capgemini in 2004, quite a long time ago. Before I had been a consultant for different companies. And, to be honest, during the initial years it was an immature market. The contingent workforce had not really been addressed during this time. We really started from scratch.

Now, in 2020, things have changed completely. We have technologies. We have managed service providers. We have really mature organizations that can help. The technology has evolved dramatically.

For example, for our Freelancer Gateway, we use technology from partners like SAP Fieldglass. We use artificial intelligence (AI) and automation to make this attractive process as easy as possible. The technology can help so much right now; it helps dramatically.

And as HR is on one side focusing on the permanent labor, we are focusing on the contracting side, but we are merging our capabilities through our Capgemini brand. This is exactly where we want to go, and this leads us to total workforce management.

Gardner: How has the SAP portfolio, in particular Fieldglass, helped you get a more repeatable and understandable process and move toward total workforce management?

Hettwer: When we began in 2016, we needed the right technology to support this because we couldn’t do everything manually. We need to have the right solution. And during this time, for sure, we did proper request for proposals (RFPs) and checked the market. SAP Fieldglass convinced us because, first of all, the technology had the right functions about what we wanted. It’s really also an end-to-end solution.

Secondly, we wanted a solution that has a global footprint. If you just come, for example, from North America, you don’t understand how Europe works -- or vice versa. It’s quite difficult. So we said we needed a global footprint with references in the different key regions. This was also why SAP Fieldglass was chosen because of this global footprint and the experience that they had. This really helped us in deploying our global program.

Thirdly, SAP Fieldglass was a strong provider with the right development capabilities because we wanted to be able to evolve. We didn’t want to have just one solution. We knew the technology would evolve and our program would evolve as well. Therefore, we needed to have a partner who can go with this program with us over several years. It’s not just a 12-month exercise, this is really something that needs to evolve.

And lastly, we needed somebody who could help us integrate a cloud-based solution into our IT systems landscape. It’s difficult when you have some cloud solutions and some on-premises solutions, you need to connect them accordingly. And that has worked. These were the reasons we selected SAP Fieldglass and since then we have worked very tightly together, and it works great.

Gardner: It seems like Capgemini is in a great position to be a leader in this field and to innovate because of your emphasis on IT, your understanding of systems, the need for flexibility, and your global footprint. You are an early adopter, but also a bellwether of where things can go with contingent workforce management.

How you have further innovated your Freelancer Gateway and trusted contractor programs?

Replace face-to-face trust

Hettwer: Like many others, we began with the contingent workforce functionality of SAP Fieldglass. This was the main purpose first of all -- to get this done. 

Then we moved to the next topic, which was delivery-based services, but this is more specific to areas where you have bigger spend areas to control. So you have to create governance.

But then we came to the direct-sourcing piece with our Freelancer Gateway to make sure that we use AI and automation to attract contractors directly and make sure that we have the best recurring extended workforce.

As I said, the pandemic was also an accelerator for this, and the use of remote contracting. And this is quite difficult because, remember, when you try to get contractors in, you need to do some interviewing. At a certain moment, people who seem to be good contractors and consultants who want to work for us would come on-site and we would get to know each other and then relationships start.

When you do these things remotely only, you never have a personal interaction with people, it's just video conferences. At a certain moment people need to have access to systems. Otherwise there is uncertainty about their capabilities and the security levels.

But when you do these things remotely only, you never have a personal interaction with people, it’s just video conferences. At a certain moment people need to have access to systems. If you don’t know these people, other than from the interview and the video conferences, there is uncertainty about their capabilities and the security levels.

This is why we needed to do something different, rather than just identifying and validating the contractors and then letting them work remotely. It’s about bringing in a level of trust that we have the proper qualifications and proper experience with people before they can work remotely for us.

And this is exactly something that we are figuring out right now. We are not completely done yet, but this is something that’s on the agenda as part of the “New Normal.”

Gardner: Andreas, when you have that digital, remote relationship rather than a more tactile, human relationship, you have to go on metrics and key performance indicators (KPIs). You need data that’s verifiable and repeatable. And in doing so you develop a greater understanding of your workers, your contingent workers, and the work itself. 

Is there something about going to a data-driven, digital-type of engagement that will pay dividends when it comes to the greater understanding through data-driven and metrics-driven definitions of your process?

Hettwer: Yes. I think it’s a combination of both, right? On the one side you need to have the technology and the right data. But when we started thinking about the new right taxonomy -- to understand and identify certain roles and skills -- it’s very difficult. We created a rate card structure to make this happen, to begin to talk to each other and understand the roles and skills across North America or in China or maybe in India. But we know that there is a bandwidth of skills that can be categorized over there.

So, we needed to have certain technology to help us identify the capabilities of individuals, and on the other side, matching this with the job postings, with the needs that we have.

The technology helps us to make these kinds of matches, and all of this data will drive to even more AI to get proper and quicker matching so that the quality of this matching process will increase. And this is also why, for example, we are focusing on recurrently used contractors because it forms loyalty that will lead to a win-win situation between the external market and our clients. This is exactly where we want to go. 

Gardner: And I certainly understand that building those taxonomies and creating the way in which you would measure the quality of the relationship for both parties is an ongoing process. But so far, just using the contingent workforce management and SAP Fieldglass to this point, tell us a little bit about what you have gotten.

Are there metrics of success, or key indicators that you can point to that demonstrate a return on investment or a rationale for why this makes sense?

Measures of success

Hettwer: Yes. First of all, we needed to have the spend coverage of 85 percent in a reasonable time. It took us some time to get there, but we are right now at the 85 percent. We recently went live in India with fully integrated solutions, and now we are at this level there, too. 

For sure, there are different countries still where we have not full coverage yet, but we do it with a light version of the solution so we at least have the chance to identify individual external workforces.

A second measure that is very important for us is the fulfillment rate. We are now at 80 percent of fulfillment rate on eligible demand. “Eligible” means there is always some kind of demand in the contractor environment that cannot be filled because it’s not needed anymore or it’s maybe that some things change and that means our own people can take care of this one.

So this is why we always say “eligible” demand is something that really needs to be fulfilled and here we are at 80 percent. And I think this is quite good, and we are further ahead of where we were some time ago. 

Another metric is the quality of job postings and aging, because if you have a job posting for contingent workforce that is in your system for 12 months, it just dilutes the KPIs and nobody is working on it anymore anyway.

e are right now at a level of below 30 days. That means whenever something is not filled within 30 days, it needs to be rechecked as to whether or not it is still needed, which means we always have proper demand so we can perform better toward our business goals.

Also quite important is time to fill positions; we have decreased this significantly. Currently we are on below 10 days from the job posting until the creation of the work order. So that means whenever there is really high demand for contracting site, we are able to fill this within 10 days. And, as you mentioned earlier, this is much quicker than recruiting people from the external market.

For sure, this will change with the “New Normal” because we have the possibility of a global remote workforce. There will be changes in what we need externally and what needs to be delivered from the internal side, and this is something that will evolve over the next weeks and months.

Gardner: And, of course, a very important measure of success these days is the perception of the customer -- the customer experience. Have you gotten any feedback as to how well your support of contingent labor works from your customers’ vantage point?

Hettwer: Yes, exactly. For sure, everything is client-driven for us. This is most important and there are some environments where you are not allowed to go with an external workforce. Others think more about the delivery-based environment and there we need to make sure that the right teams are available to deliver what we have promised.

There is always the question about if the contingent workforce needs to be engaged, and how can you ensure you select the right people, that you have the right suppliers in place, and that you are able to deliver what you are promising.

When we came up with our approach and showcased the suppliers -- the client base was very impressed. We even go out to our clients’ site, explain what we do, and how we do it. We even have clients thinking about how to adopt this contingent workforce management approach internally. So I think this is the best thing, if clients ask us to do similar things for themselves.

Gardner: Of course, those clients would let you know pretty quickly if things weren’t working out and so you have the ability to be reactive and agile as you adjust. It’s a feedback loop.

Before we end, Andreas, let’s look to the future. We mentioned the idea of establishing trust and understanding, the relationship and the qualitative and quantitative value of work, but it seems to me that what we are talking about as contingent workforce expands is really a redefinition of a corporation or a business. The barriers of that business become fuzzy, even permeable.

Do you see the nature of business changing as we look to less of a walled garden and more of an expanding universe of skills?

The future is not fuzzy

Hettwer: Yes, I would say so. As I said, we call it global resourcing or global capabilities, and this is exactly where it will lead. It’s not that everything can be done remotely, but it will increase, and this will give us opportunities -- not only Capgemini – but also more from our contractor side. And this is exactly the right thing to address right now because only when we have the right people in place -- when we have the right contractors in place -- then we can do these kinds of things.

There will always be some deviation, right? As you see, more and more tax regulation will come, more and more labor laws will come in the different countries. And this needs to be addressed. There is a difference between external services and internal services, and this needs to be addressed.

I think it will not be as fuzzy as it looks initially so that you can’t differentiate anymore between an employee and a temporary contractor. It will always be a differentiation there from my perspective because of all these kind of tax, legal, and statutory requirements. But you can do things in a more homogeneous and more aligned way -- and this is exactly what it will lead to.

Gardner: What advice would you share with others who are interested in increasing the amount of contingent workforce utilization and management?

Hettwer: There is so much to learn that I could talk for hours. But the first thing that I have is whenever you want to start some kind of contingent workforce program, think about the pain points in your company.

Is it compliance risk? Is it a cost issue? Is it a fulfillment issue? What are the pain points that you have in your organization and start from there, create, then solutions, and then finally a business case. Because without a business case that is not approved by the senior business you will never succeed. So that is my first recommendation.

Whenever you want to start some kind of contingent workforce program, think about the pain points in your company. Start from there then create solutions and finally a business case. Without as business case approved by the senior management you will never succeed. 

The second one is getting clarity from the executive level about who owns such a program. This links very much to the questions that you had earlier; is it procurement, is it HR, is it somebody from the business? But there needs to be an owner, because otherwise you start a program and then you immediately start fighting about who owns it, right?

The third aspect is, if you want to go in such a global program, what about the governance? You need to have the right stakeholders in place. First of all, to get their buy in, and secondly, it’s about crowd intelligence. You are never the one who has the knowledge about everything. So if you get the right people on board from the different countries, from the different functions, then you will have all the intelligence that you need to create a program.

Then, you need to make sure that you have proper steering committees in place, because there will always be discussions and escalations, so make sure that you don’t get only the approval from the executive committee but also that you have regular decision points where these kinds of things will be discussed and decisions will be taken.

And last, but not least, prioritize. You will never be in the position to have a global program and make sure that in 12 months you have covered the globe; this will not happen. So, prioritize, make sure you start where you have the biggest pain points, you start there because initial success creates demand for deployment and will lead to its acceleration. So get success as quickly as possible in areas where really success is needed, talk about this one and that will help you really to accelerate.

Gardner: Well, very good, I’m afraid we will have to leave it there. You have been listening to a sponsored BriefingsDirect discussion on the growing importance of contingent workforces. And we have learned why managing those workers and services better enables businesses to further leverage external workforces and services to satisfy flexibly their growing skills and IT needs.

So a big thank you to our guest, Andreas Hettwer, Vice President and Group Procurement Category Director at Capgemini. Thank you so much, Andreas.

Hettwer: You are welcome. Thank you very much.

Gardner: And a big thank you as well to our audience for joining this BriefingsDirect digital business innovation discussion. I’m Dana Gardner, Principal Analyst at Interarbor Solutions, your host and moderator throughout this series of SAP-sponsored BriefingsDirect discussions.

Thanks again for listening. Please do come back next time, and feel free to share this information across your IT and business communities.

Listen to the podcast. Find it on iTunes. Download the transcript. Sponsor: SAP.

Transcript of a discussion on the growing importance of contingent workforces for businesses around the world to satisfy their skills and information technology needs. Copyright Interarbor Solutions, LLC, 2005-2021. All rights reserved.

You may also be interested in: