Tuesday, March 20, 2018

Pay-As-You-Go IT Models Provide Cost and Operations Advantages for Northrop Grumman

Transcript of a discussion on how pay-as-you-go models have emerged as an advantageous way to align information technology needs with business imperatives at a global aerospace and defense integrator.

Listen to the podcast. Find it on iTunes. Get the mobile app. Download the transcript. Sponsor: Hewlett Packard Enterprise.

Dana Gardner: Hello, and welcome to the next edition of the BriefingsDirect Voice of the Customer podcast series. I’m Dana Gardner, Principal Analyst at Interarbor Solutions, your host and moderator for this ongoing discussion on digital transformation success stories. Stay with us now to learn how agile businesses are fending off disruption -- in favor of innovation.

Gardner
Our next IT business model innovation interview explores how pay-as-you-go models have emerged as a new way to align information technology (IT) needs with business imperatives. We’ll now learn how global aerospace and defense integrator Northrop Grumman has sought a revolution in business model transformation in how it acquires and manages IT.

Here to help us to explore how cloud computing-like consumption models can be applied more broadly is Ron Foudray, Vice President, Business Development for Technology Services at Northrop Grumman. Welcome, Ron.

Ron Foudray: Thank you for having me. I appreciate it.

Gardner: What trends are driving the need to change how IT is acquired? People have been buying IT for 40 or more years. Why a change now?

Foudray: Our customers, who are primarily in the government sector across the globe, understand the dynamic nature of how IT and technology innovation occurs. It can be a very expensive investment to maintain and manage your own infrastructure as part of that.

Foudray

In parallel, they see the benefits of where technology is going from a cloud perspective, and how that can drive innovation -- and even affordability. So there is a cultural transformation around how to do more relative to IT and where it’s going.

That gets to the things you were just using in your opening comments as to how do we transform the business model and provide that to our customers, who traditionally haven’t thought about those business models.

Gardner: I suppose this is parallel to some creative financing trends we saw 10 or 15 years ago in other sectors – manufacturing and transportation, for example – where they found more creative ways of sharing and spreading the risk of capital.

As a service or buy?


Foudray: I think it’s a great analogy. You can look at it as if you are going to lease a car instead of buying one. In the future, maybe we don’t buy cars; maybe we just access them via Uber or Lyft, or some other pieces. But it’s that kind of transformation and that kind of model that we need to be willing to embrace -- both culturally and financially -- and learn how we can leverage that.

Gardner: Ron, tell us about Northrop Grumman and why your business is a good fit for these new models.

Foudray: I have been in the aerospace and defense market for 36 years. Northrop Grumman clearly is a market-leading, global security company, and we focus primarily on building manned and unmanned platforms.

We have as part of our portfolio the sensors that go along with those platforms. You may have heard of something called C4ISR, for Command, Control, Computers, Communications, Intelligence, Surveillance and Reconnaissance. It’s those types of sensors and systems that we bring to the table.

In my portfolio, on the technology services side, we are also providing differentiated capabilities for how we support, maintain, upgrade and modernize that infrastructure. That includes the capabilities of how we can provide the services more broadly to our customers. So we focus primarily on five core pillar areas: autonomous systems, strike platforms, logistics, cyber-security, and C4ISR.

Gardner: You are not only in the delivery of these solutions, but you are an integrator for the ecosystem that has to come together to provide them. And, of course, that includes IT.

Foudray: Exactly. In fact, sometimes when I go talk to a customer, it’s like we’re Northrop Grumman Information Technology. They are trying to connect the dots. So, yes, I think of Northrop Grumman not only as the platforms, sensors and systems, but the enterprise IT infrastructure as well..
The edge for our war fighters is anywhere that their systems and sensors are being deployed.

That comes with the digital transformation that’s been ongoing inside of our war-fighting apparatus around the world for some time. And so when you hear about the [transformation] of things in the data center or at the edge -- well, the edge for our war fighters is anywhere that their systems and sensors are being deployed.

We need to be able to do more of that processing, and that storage, in real time, at that closer point-of-need. We therefore need to be driving innovation with enterprise IT on how to connect into and leverage that all back across those systems, sensors, and platforms.

When you put it in that context, the digital interconnectedness that we have -- not just a society -- but in a war fighting sense as well, it becomes more and more clear as to why an integrator, a company like Northrop Grumman, wants to drive enterprise IT innovation and solutions. By doing so, we can drive essentially the three things I think all customers are looking for, which are mission effectiveness, mission efficiency, and affordability.

Gardner: The changes we have seen in IT and software over the past decade -- of Software-as-a-Service (SaaS) and other cloud-driven models -- make a lot of sense. You pay as you consume. You may not own the systems; they are in somebody else's data center, typically referred to as the cloud.

But I’m going to guess that in your business, public cloud isn't where you are going to put your data centers – this is probably more of an on-premises, close to the point of value, if you will, deployment model. So how do you translate SaaS consumption models and economics to an on-premises data center?

Control and compliance in the cloud?


Foudray: You are astute in pointing that out, because government customers traditionally have had a greater need for a level of control and compliance. With those types of data and applications -- whether it's the clearance level of the information or just the type of information that’s being collected -- there is sensitivity.

That said, there are still some types of information -- back office type of things – that may be appropriate for a public cloud that you could commingle with today. But very clearly there is more and more of a push for that on-premises solution set.

When our customers begin thinking about cloud -- and they are modeling their enterprise on a cloud capability -- they tend to use the model of, “Well, how can I get the same affordability outcomes that a public cloud provider is going to be able to offer?” They are amortizing their cost and those elements across all those other customers versus an on-premises solution that is only theirs.
The business model innovation is that consumption-based, on-premises solution that gets more creative on how you look at the residual values.

And so the business model innovation that we are talking about and driving is that consumption-based, on-premises solution that gets more creative on how you look at the residual values. And in our space, there’s a lot of digital data that won't come back into the equation that is not able to realize residual value. It's like when you bring back the leased car, that we talked about earlier, if you go over 30,000 miles, it still has value after your lease period.

In a lot of cases in the government environment, depending on where it lives, those digital fingerprints are going to have to stay on the customers’ side or get destroyed, so you can't assume that into the model.

There are a lot of different variables driving it. That's where the innovation comes in, and defines how you work as an integrator. With partners -- like we see with Hewlett Packard Enterprise (HPE) and others in the marketplace -- we can drive that innovation.

Gardner: In a case where there’s a major government or military organization, they may want to acquire on a pay-per-use basis, but the supply chain that supports that, they might want to be paid upfront on a CapEx basis. How are you able to drive this innovation in end-pricing and in economics for entire solutions that extend back into such supply chains? Or are you stuck in the middle?

Trusted partners essential


Foudray: That hits on a very core part of the challenge, and why having a partner that is going to help you provide the IT infrastructure is so important -- not just in terms of managing that supply chain holistically but in having a trusted partner, and making sure that the integrity and the security of that supply chain is maintained. We haven't talked about the security element yet, but there is a whole cybersecurity piece of that supply chain from an integrity perspective that has to be maintained as well.

The more trust you build up in that partnership, and across those relationships with your downstream suppliers, the better. That trust extends to how they are getting paid and the terms associated with that, with working those terms and conditions and parameters upfront, and of getting those laid in so that the desired expectations are met. Then you must work with your customer to set the right expectations on their terms and conditions to provide them a new consumption-based model. It’s all from an agreement perspective, all very closely aligned.

Gardner: Is there something about newer data center technology that is better tuned to this sort of payment model change? I’m thinking of software-defined data center (SDDC) and the fact that virtualization allows you to rapidly spin-up cloud infrastructure applications. There’s more platform agility than we had several years ago. Does that help in being able to spread the risk because the IT vendors know that they can be fleet and agile with their systems, more than in the past?
Hardware clearly is an enabling feature and function, but software is what's really driving digital transformation ... not just on the technology side, but also on the business side and how it's consumed.

Foudray: We do a lot from a software perspective as a systems integrator in the defense market space. Software is really the key. Hardware clearly is an enabling feature and function that’s driving that, but software is what’s really driving digital transformation. And that element in and of itself is really what’s helping to transform the way that we think about innovation -- not just on the technology side, but also on the business side, and in how it’s consumed.

We are putting a lot of energy into software transformation, as part of the digitization aspect -- not just in terms of how quickly we can provide those drops from an agile development, DevOps, development-security-operations (SecOps) perspective, but in terms of the type of services that are delivered with it, and how you look at it.

Changing the business model in parallel needs to avoid offending engineering principle 101: Never introduce more than one key change at a time. You have to be careful that culturally, depending on the organization that you are interacting with, that you are not trying to drive too much change and adoption patterns at the same time.

But you are right to hit on the software. If I had to pick one element, software is going to be the driver. Next is the culture -- the human behavior, of where someone lives, and what he or she is used to. That’s also going to be transformative.

Gardner: For mainstream enterprises and businesses, what do you get when you do this? What are some of the payoffs in terms of your ability to execute in your business, keep your customers satisfied, and maybe even speed up innovation? What do you get when you do this acquisitions model transformation thing right?

Scale in, scale out, securely


Foudray: First, it’s important to recognize that you don’t lose control, you don’t lose compliance, and you don’t lose those things that traditionally may have caused you not to embrace [these models].

What you get is the ability to leverage innovation from a technology perspective as it happens,
because your provider is going to be able to scale in and scale out technology as needed. You are going to be able to provision more dynamically in such an environment.
You get the ability to leverage innovation from a technology perspective as it happens.

If you have the right partner in your integrator and their provider, you should be able to anticipate and get in front of the changes that drive today’s scalability challenges, so you can get the provisioning and get the resourcing that you need. You are also going to be in a much better predictability state of where you need to be for the financial elements of your system.

There are some other benefits. If you implement it correctly, not only are you going to get the performance that you need, your utilization rates should go way up. That’s because you are not going to be paying for underutilized systems as part of your infrastructure. You will see that added affordability piece.

If you do it right, and if you pick integrators who are also tying in the added dimension of security, which we very much are focused on providing, you are going to get a high level of compliance with the National Institute of Standards and Technology (NIST) Risk Management Framework (RMF). On the US side, there is also the National Defense Authorization Act, which requires organization and agency heads to certify that their enterprise is at a certain level of hygiene. If you have implemented this correctly, you should be able to instrument your environment in such a way that at any given time you know what level of security you are at, from a risk perspective.

There are a lot of benefits you get for cost, schedule, and performance -- all of that tied together in a way that you never would have been able to see from an ecosystem perspective, all at the same time. You may get one or two of those, but not all three. So I think there are some benefits that go along those lines that you are going to be able to see as a customer, whether you are in the defense space or not.

Gardner: Yes, I think we’re going to see these models across more industry ecosystems and supply chains. Clearly vendors like HPE have heard you. They recently announced some very innovative new flex-capacity-types of pricing, and GreenLake-branded ways to acquire technology differently in most markets.

I’m afraid we will have to leave it there. We have been exploring how pay-as-you-go models have emerged as a powerful way to align technology needs with business imperatives. And we have learned how global aerospace and defense integrator Northrop Grumman has sought a revolution in business model transformation in how it acquires and manages IT.

So please join me in thanking our guest, Ron Foudray, Vice President, Business Development for Technology Services at Northrop Grumman.

Foudray: Thank you. I appreciate it.

Gardner: And a big thank you to our audience as well for joining us for this BriefingsDirect Voice of the Customer digital transformation success story. I’m Dana Gardner, Principal Analyst at Interarbor Solutions, your host for this ongoing series of Hewlett Packard Enterprise-sponsored interviews.

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

Listen to the podcast. Find it on iTunes. Get the mobile app. Download the transcript. Sponsor: Hewlett Packard Enterprise.

Transcript of a discussion on how pay-as-you-go models have emerged as an advantageous way to align information technology needs with business imperatives at a global aerospace and defense integrator. Copyright Interarbor Solutions, LLC, 2005-2018. All rights reserved.

You may also be interested in:

Wednesday, February 21, 2018

A Tale of Two Hospitals—How Dynamic Healthcare Economics in Belgium Hastens Need for Modern IT Efficiency

Transcript of a discussion on how two Belgian hospitals are adjusting to dynamic healthcare economics by leveraging the multilevel benefits of composable infrastructure and pay-as-you-go buying options for data centers.

Listen to the podcast. Find it on iTunes. Get the mobile app. Download the transcript. Sponsor: Hewlett Packard Enterprise.

Dana Gardner: Hello, and welcome to the next edition of the BriefingsDirect Voice of the Customer podcast series. I’m Dana Gardner, Principal Analyst at Interarbor Solutions, your host and moderator for this ongoing discussion on digital transformation success stories. Stay with us now as we learn how agile businesses are fending off disruption -- in favor of innovation.

Gardner
Our next data center agility interview explores how two Belgian hospitals are adjusting to dynamic healthcare economics to better compete and cooperate. We will now learn how a regional hospital seeking efficiency -- and a teaching hospital seeking performance -- are meeting their unique requirements, thanks to modern IT architectures.

Here to help us understand the multilevel benefits of composable infrastructure and software defined data center (SDDC) in the fast-changing healthcare field are our guests, Filip Hens, Infrastructure Manager at UZA Hospital in Antwerp, Belgium. Welcome, Filip.

Filip Hens: Thanks.

Gardner: We’re also here with Kim Buts, Infrastructure Manager at Imelda Hospital in Bonheiden, Belgium. Welcome.

Kim Buts: Thank you.

Gardner: What are some of the top trends disrupting the healthcare industry in Belgium? Filip, why do things need to change? Why do you need to have better IT infrastructure?

Hens: That’s a good question. There are many up-and-coming trends. One is new regulations around governance, which is quite important. Due to these new rules, we are working more closely together with other hospitals to share more data, and therefore need better data security. This is one of the main reasons that we need to change.

Hens

In Belgium, we have many hospitals, with some of them only a few kilometers apart. Yet there have been very few interactions between them.

New demands around augmentation of services means patient data are a growing concern. So it’s not only the needs of new governance but also the demand for providing better medical services across hospitals.

Gardner: Kim, how are the economics of healthcare -- of doing more with less -- an ongoing requirement? How are you able to conserve on the costs?

Buts: We are trying to do everything we can across the financial possibilities. We are constantly looking for good solutions that are affordable. The obligation to work in a [hospital] cluster provides us with a lot of new challenges.

A major challenge for us was around security. We have invested hugely in security. Many of the new applications are now shared across the hospital cluster. So we chose to take on the role of innovator. And to continue innovating, we have to spend a lot of money. That was not foreseen in the annual budget. So we took advantage of Hewlett Packard Enterprise’s (HPE’s) new financial services approaches, to make things happen much faster than usual.
How HPE Digital Solutions
Support Healthcare
And Life Sciences
Gardner: We’ll get back to some of those services, but I’d like to help our readers and listeners better understand this interesting combination of needing to compete -- that is to attract patients -- but at the same time cooperate and share data across hospital cluster. Filip, tell us about UZA and how you’re unique compared to a regional hospital. What makes you different?

Sharing is caring, and saving


Hens: Our main focus remains patient care, but for us it is not necessarily general medicine. It is more the specialist cases, for such things as specialized surgery. That is our main goal. Also we are a teaching hospital, so we have an emphasis on learning from patients and from patient data.

Gardner: You have unique IT and big data requirements from your researchers. You have more of an intense research and development environment, and that comes with a different set of IT requirements?

Hens: Yes, and that is very important. We are more demanding of the quality of the data, the need to gather more information, and to provide our researchers a better infrastructure platform.

That is one difference between a general hospital and a university hospital. A teaching facility has more complex patient analytics requirements, the need for complex data mining and stuff like that.

Gardner: Kim, how are you in your healthcare cluster now able to share and cooperate? What is it that you’re sharing, and how do you that securely to creating better healthcare outcomes?

Buts: A big difference for us is financial. Since we are a smaller hospital, we must offer a very broad portfolio of treatments. That means we need to have a lot of patients to then have enough income to survive. The broad offering, that portfolio of treatments, also means we are going to need to work more together with the other cluster members.

Buts
We are now trying to buy new IT equipment together, because we cannot afford to each buy for every kind of surgery, or for every kind of treatment. So we have combined our budgets together and we are hosting different things in our hospital that are then used by the other cluster members, too.

Financially, due to the regulations, we have less income than a university hospital. The benefits of education funding do not get to us. We only get income from patients, and that is why we need to have a broad portfolio.

Hens: Unlike a general hospital, we have income from the government and we also have an income flow from scientific research. It is huge funding; it is a huge amount. That is really what makes us different. That is why we need to use all of that data, to elaborate on scientific research from the data.

If not an advantage, it is an extra benefit that we have as university hospital. In the end, it is very important in that we maintain and add extra business functionality via an updated IT infrastructure. 
If we maintain those clusters well -- the general hospitals together with university hospitals -- then those clusters can share among themselves how to best meet patient needs, and concentrate on using the sparest amount of the budget.

Robust research, record keeping, required


Gardner: You are therefore both trying to grapple with the use and sharing of electronic medical records (EMR) applications. Are you both upgrading to using a different system? How are you going about the difficult task of improving and modernizing EMR?

Buts: One big difference between our hospitals is our doctors; they are working for the hospital on a self-employed basis at Imelda. They are not employees of the hospital as at UZA. The demands of our doctors are therefore very high, so we have to improve all of our facilities -- and our computer storage systems -- very fast.

We try to innovate for the doctors, so we have to spend a lot of money on innovation. That is a big difference, I think, between the university hospitals because the doctors are employees there.

Gardner: How does that impact your use of EMR systems?
How HPE Digital Solutions
Support Healthcare
And Life Sciences
Buts: We are in the process of changing. We are looking for a new EMR system. We are discussing and we are choosing, but the demands of the doctors are sometimes different from the demands of the general hospital management.

Gardner: Filip, EMR, is that something you are grappling with, too?

Hens: We did the same evaluations and we have already chosen a new EMR. For us, implementing an EMR is now all about consolidation of a very scattered data landscape, of moving toward a centralized organization, and of centralizing databases for sharing and optimization of that data.

There is some pressure between what physicians want and what we as IT can deliver with the EMR. Let’s just say it is an opportunity. It is an opportunity to understand each other better, to know why they have high demands, and why we have other demands.

That comparison between the physicians and us IT guys makes it a challenging landscape. We are busier with the business side and with full IT solutions, rather than just implementing something.

It is not just about implementing something new, but adaptation of a new structure of people. Our people rethink how everybody’s role is changing in the hospital, and what is needed for interaction with everybody. So, we are in the process of that transformation.

Gardner: What is it about the underlying IT infrastructure that is going to support the agility needed to solve both of your sets of problems, even though they are somewhat different?

Filip, tell us about what you have chosen for infrastructure and why composable infrastructure helps solve many these business-level challenges.

Composable confidence


Hens: That is a good question, because choosing a solution is not like going to the supermarket and just buy something. It is a complex process. We still have separation of data storage and computing power.

We still separate that kind of stuff because we want to concentrate on the things that really bring added value, and that are also trustworthy. For us, that means virtualization on the server and network platforms, to make it more composable.

A more software-defined and composable approach will make us more independent from the underlying hardware. We have chosen for our data center the HPE Synergy platform. In our opinion, we are ready because after many years as an HPE customer -- it just works.
For me, knowing that something is working is very important, but understanding the pitfalls of a project is even more important.

And for me, knowing that something is working is very important, but understanding the pitfalls of a project is even more important. For me, the open discussion that you can have with HPE about those pitfalls, of how to prepare for them and how to adapt your people to know what’s to come in the future -- that is all very important.

It’s not only a decision about the metal, but also about what are the weaknesses in the metal and how we can overcome that -- that is why we stick with HPE, because we have a good relationship.

Gardner: Kim, what are you doing to modernize, but also innovate around those all-important economic questions? How are you using pay-as-you-go models to afford more complex technology, and to give you advancement in serving your customers?

One-stop shopping


Buts: The obligations of the new hospital-cluster regulations had a huge impact on our IT infrastructure. We had to modernize. We needed more compute power and more storage. When we began calculating, it showed us that replacing all of the hard drives at one time was the best option, instead of spreading it over the next three to four years.

Also the new workload demands on the infrastructure meant we needed to replace it as fast as possible, but the budget was not available at our hospitals. So HPE Financial Services provided us with a solution that meant we could replace all our equipment with very short notice. We exchanged servers, storage, and our complete network, including our Wi-Fi network.

So we actually started with a completely brand new data center thanks to the financial services of HPE.

Gardner: How does that financing work? Is that a pay-as-you-go, or are payments spread over time?

Buts: It’s spread over the coming five years. That was the only solution that was good for us. We could not afford to do it any other way.

Gardner: So that is more like an operating costs budget than an upfront capital outlays budget?
We actually started with a completely brand new data center thanks to the financial services of HPE. We could not afford to do it any other way.

Buts: Yes, and the other thing we wanted to do was do everything with HPE -- because they could offer us a complete range of servers, storage, and Wi-Fi networking. That way we could reduce the complexity of all our work, and it guaranteed us a fast return on the investment.

Gardner: It is all more integrated, upfront.

Buts: Yes, that is correct.

Gardner: At UZA, what are you doing to even further modernize your infrastructure to accommodate more data, research, sharing, and security?

Hens: It is not about what I want to deliver; it is about what the business wants that we can deliver, and what we can together deliver to the hospital. So, for me, the next step is the EMR program.

So, implementing the EMR, looking for the outcomes from it, and offering something better to end-users. Then those outcomes can be used to further modernize the infrastructure.

That for me is the key. I will not necessarily say that we will buy more HPE Synergy. For me, the key to the process, as I just described, that is what will set the margins of what we will need.

Gardner: Kim, now that you have a new data center, where do you take it next in terms of people, process or even added technology efficiencies? Improved data and analytics, perhaps?

Cloud in the Cluster?


Buts: That is a difficult one because the cluster is very new for us. We are still looking at good ways to incorporate and decide where the data is going to be placed, and what services are going to be required.

It is still brand new for us, and we have to find a good way to incorporate it all with the different hospital cluster members. A big issue is how are we going to exchange the critical patient data, and how we are going to store it safely and securely.

Gardner: Is cloud computing going to be a part of that?

Buts: I do not know. Everything is “cloud” now so, maybe. I am not a huge fan of public cloud. If you can stay in a private cloud, yeah, then okay. But public cloud, I do not know. In a hospital, regulations are so strong and the demands are so high.

Gardner: Maybe a shared private cloud environment of some sort?

Buts: Yeah. I think that could be a good solution.
How HPE Digital Solutions
Support Healthcare
And Life Sciences
Hens: For public cloud in general, I think that is a no-go. But what we are doing already with our EMR, we can work together with a couple of hospitals and we can choose to build a private cloud at one of the sites at our hospitals.

You do not need to define it as a cloud. Really, it’s like public Internet cloud, but you have to make your IT cloud-aware and cloud-defined inside the walls of your hospital. That is the first track you need to take.

Buts: That is why in our hospital cluster, we chose to host a lot of new applications on the new hardware. It gave us the ability to learn and adapt quickly to the new innovations. And for the other hospitals, we are now becoming a kind of service provider to them. That was for us a big change, because now we are more a service level agreements (SLA)-driven organization than we used to be.

Gardner: I’m afraid we’ll have to leave it there. We have been exploring how two Belgian hospitals are adjusting to a dynamic healthcare and economics environment. They are both competing and cooperating. And we have learned how multi-level benefits of composable and software-defined data centers are helping them to meet many of their transformation requirements.

So please join me in thanking our guests, Filip Hens, Infrastructure Manager at UZA Hospital in Antwerp. Thank you.

Hens: Thank you also.

Gardner: And Kim Buts, Infrastructure Manager at Imelda Hospital in nearby Bonheiden, Belgium. Thank you.

Buts: Thank you very much.

Gardner: And a big thank you as well to our audience for joining us for this BriefingsDirect Voice of the Customer digital transformation success story. I’m Dana Gardner, Principal Analyst at Interarbor Solutions, your host for this ongoing series of Hewlett Packard Enterprise-sponsored interviews.

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

Listen to the podcast. Find it on iTunes. Get the mobile app. Download the transcript. Sponsor: Hewlett Packard Enterprise.

Transcript of a discussion on how two Belgian hospitals are adjusting to dynamic healthcare economics by leveraging the multilevel benefits of composable infrastructure and pay-as-you-go buying options for data centers. Copyright Interarbor Solutions, LLC, 2005-2018. All rights reserved.