How IT4IT Turns IT into a Business that the Business Can Then Use as a Transformational Service
How IT4IT Turns IT into a Business that the Business Can
Then Use as a Transformational Service
Transcript of a sponsored discussion on the business beneﬁts of transforming IT organizations
into agents of change for businesses.
Listen to the podcast. Find it on iTunes. Get the mobile app. Sponsor: The Open
Dana Gardner: Hello, and welcome to a special BrieﬁngsDirect thought leadership panel
discussion coming to you in conjunction with The Open Group 2016 San Francisco event in
January. We'll now delve into the business beneﬁts of transforming IT
organizations into agents of change for businesses.
The Open Group IT4IT initiative, a new reference architecture for
managing IT as a business, grew out of a need at some of the world's
biggest organizations to make their IT departments more responsive, more
agile. We’ll learn now how those IT departments within an enterprise and
the vendors that support them have reshaped themselves, and how others
can follow their lead.
And so to learn more about how IT4IT fosters change, we're joined by Michael Fulton, Principal
Architect at CC&C Solutions; Philippe Geneste, a Partner at Accenture; Sue Desiderio, a
Director at PricewaterhouseCoopers; Dwight David, Enterprise Architect at Hewlett Packard
Enterprise (HPE); and Rob Akershoek, Solution Architect IT4IT at Shell IT International.
So let me start with our panel and just go down the line. Philippe, tell me where you think the
most progress has been made in terms of making IT4IT a mature reference architecture.
Philippe Geneste: The two innovations that we have in the IT4IT Reference Architecture -- the
Service Backbone and the Request to Fulﬁll (R2F) value stream -- are the two greatest novelties
of the Reference Architecture.
Are they mature? They're mature enough and they'll probably evolve in their level of maturity.
There are a number of areas that are maturing, and some that we have in design. The IT Financial
Management, for instance, is one that I'm working on a little bit, and the service costing within
that, which I think we'll get a chance to get ready by version 2.1. The idea is to have it as
guidance inversion 2.1.
The value streams by themselves are also mature and almost complete. There are a number of
improvements we can make to all of them, but I think overall the Reference Architecture is
usable today as an architecture to start with. It's not quite for vendor certiﬁcation, although that’s
upcoming, but there are a number of good things and a number of implementations that would
beneﬁt from using the current IT4IT Reference Architecture version 2.0.
Gardner: Sue, where do you see the most traction and growth and what would you like to see
Sue Desiderio: I agree with Philippe’s statements. Also picking up on what Lars said earlier this
morning, it's an easy entry point to start with Detect to Correct, which is often where we see it,
because it’s one of the value streams that’s a little bit more known and
understood. So that’s an easier point of entry for the whole IT4IT value chain,
compared to some of the other value streams.
The service model, as we've stated all along, is deﬁnitely the backbone to the
whole IT value chain. Although it's well-formed and in a good, mature state,
there's still plenty of work to do to make that consumable to the IT
organizations to understand all the different phases of the life cycle and all the
different data objects that make up the Service Backbone. That's something that we're currently
working on for the 2.1 version, so that we have better examples. We can show how it applies in a
real IT organization, and it’s not just what’s in the documentation today.
Gardner: And same to you, Rob, positive and negative?
Rob Akershoek: I don’t think it’s about positive and negative in this case, but more about
areas that we need to work on in more detail, like deﬁning the service-broker role that you see in
the new IT organization, for example how you interface with your external
service providers. We've identiﬁed a number of areas where the IT
organization has key touch points with these vendors, like your service
catalog, you need to synchronize catalog information with the external vendors
and aggregate it into your own catalog.
But there's also the fulﬁllment API -- how do you communicate a request to
your suppliers or different technology stacks and get the consumption and cost
data back in? I think we deﬁne that today in the IT4IT standard, but we need to
go to a lower level of detail -- how do we actually integrate with vendors and our service
So interfacing with the vendors in the eco-system sits on many different levels. It’s on the
catalog level and the request fulﬁllment, that you actually do provision, the cost consumption
data, and those kind of aspects.
Another topic is still the linking in to security and identity and access management. It's an area
where we still need to clarify. We need to clarify how all the subscriptions in a service link in to
that access management capability, which is part of the subscription and, of course, the
fulﬁllment. We didn’t identify it as a separate functional component.
Gardner: Dwight, where are you most optimistic and where would you put more emphasis?
Dwight David: I'll start with the latter. More emphasis needs to be on our approach to Detect to
Correct. Oftentimes, I see people thinking about Detect to Correct as in the traditional mode of
being reactive, as opposed to understanding that this model can be applied even
to the new changing user-friendly type of economy and within the hybrid type of
IT. A change in thinking in the application of the value streams would also help
Many of us have a lot of gray hairs, including myself, and we revert to the old
way of thinking, as opposed to the way we should be moving forward. That’s the
area where we can do the most.
What's really good, though, is that a lot of people understand Detect to Correct. So it’s an easy
adoption in terms of understanding the Reference Architecture. It’s a good entry point to the
IT4IT Reference Architecture. That’s where I see the actual beneﬁt. I would encourage us to
make it useful, use it, and try it. The most beneﬁt happens then.
Gardner: And Michael, room for optimism and room for improvement?
Michael Fulton: I want to build on Dwight’s point around trying it by sharing. The one thing
I'm most excited about, particularly this week, is the Management Guide -- very speciﬁcally,
chapter 5 of the Management Guide. I hope all of you got a chance to grab your
copy of that. If you haven’t, I recommend downloading it from The Open Group
website. That chapter is absolutely rich in content about how to actually
And I tip my hat to Rob, who did a great piece of work, along with several other
people. If you want to pick up the standard and use it, start there, start with
chapter 5 of the Management Guide. You may not need to go much further,
because that’s just great content to work with. I'm very excited about that.
From the standpoint of where we need to continue to evolve and grow as a standard, we've
referenced some of the individual pieces, but at a higher level. The supporting activities in
general all still need to evolve and get to the level of detail that we have with the value streams.
That’s a key area for me.
The next area that I would highlight, and I know we're actively starting work on this, is around
getting down to that level of detail where we can do data interoperability, where we can start to
outline the speciﬁcs that are needed to deﬁne APIs between the functional components in such a
way that we can ultimately bring us back to that Open Group vision of a boundaryless
Gardner: Picking up on that, when we ﬁnished our main panel in the plenary this morning, just
before lunch, one of the last points made was how we bridge the divide between a cloud provider
or a series of providers and have IT in a brokering role within the organization. As the broker,
they're going to be held responsible for the performance, regardless of where those services
originate and how they interoperate or not.
What do we see as needed in order to make that
boundarylessness extend to this idea of a brokered IT
organization, a hybrid organization, but still able to produce a common approach
to support quality of service across IT in that particular organization? Again, let’s start on one
end of the panel and work our way along. How do we get to that hybrid vision, Philippe?
Geneste: We'll get there step-by-step. There's a practical step that’s implementable today. My
suggestion would be that every customer or company that selects an outsourcer, that selects a
cloud vendor, that selects a product, uses the IT4IT Reference Architecture in the request for
proposal (RFP), putting a strong emphasis on the integration.
We see a lot of RFPs that are still silo based -- which one is the best product for project and
portfolio management, which one is the best service management tool -- but it’s not very
frequent that we see the integration as being the topnotch value measured in the RFP. That would
be one point.
The discussions with the vendors, again, cloud vendors or outsourcers or consulting ﬁrms should
start from this, use it as an integration architecture, and tell us how you would do things based on
these standardized concepts. That’s a practical step that can be used or employed today.
In a second step, when we go further into the vendor speciﬁcation, there are vendors today, when
you analyze the products and the cloud offerings that are closer to the concepts we have in the
Reference Architecture. They're maybe not certiﬁed, maybe not the same terminology, but the
concepts are there, or the way to the concepts is closer.
And then ultimately, step 3 and 3.5 will be product vendor certiﬁed, cloud service offering
certiﬁed, hopefully full integration according to the RA, and eventually, even plug-and-play.
We're doing a little bit about plug-and-play, but at least integration.
Gardner: What sort of timeframe would you put on those steps? Is this a two-year process, a
four-year process, to soon to tell?
Geneste: That’s a tough one. I suppose the vendor should be responding to this one. For the
service providers, for the cloud service providers, it’s a little bit trickier, but for the consulting
ﬁrm for the service providers it should be what it takes to get the workforce trained and to get the
concepts spread inside the organization. So within 6 to 12 months, the critical mass should be
there in these organizations. It's tough, but project by project, customer by customer it’s
Some vendors are on the way, and we've seen several vendors talk about IT4IT in this
conference. I know that those have signiﬁcant efforts on the way and are preparing for vendor
certiﬁcation. It will be probably a multiyear process to get the full suite of products certiﬁed,
because there is quite a lot to change in the underlying software, but progressively, we should get
So, it's having ﬁrst levels of certiﬁcation within one to two years, possibly even sooner. I would
be interested in knowing what the vendor responses will be.
Gardner: Sue, along the same lines, what do you see needed in order to make the IT department
able to exercise the responsibility of delivering IT across multiple players and multiple
Desiderio: Again, it’s starting with the awareness and the open communication about IT4IT and,
on a speciﬁc instance, where that ﬁts in. Depending on the services we're getting from vendors,
or whether it's even internal services that we are getting, where do they ﬁt into the whole IT4IT
framework, what functions are we getting, what are the key components, and where are our
Have those conversations upfront in the contract conversations, so that everyone is aware of
what we're trying to accomplish and that we're trying to seek that seamless integration between
those suppliers and us.
Gardner: Rob, this would appear to be a buyer’s market in terms of their ability to exercise
some inﬂuence. If they go seeking RFPs, if there are fewer cloud providers than there were
general vendors in a traditional IT environment, they should be able to dictate this, don’t you
Akershoek: You mean who dictates it? In the cloud world, the consumer would not dictate at all.
That’s the traditional way that we dictate how an operator should provide us data. That’s the
problem with the cloud. We want to consume a standard service. So we can't tell the cloud
vendor, send me your cost data in this format. That won't work, because we don’t want the cloud
vendor to make something proprietary for us.
That’s the ﬁrst challenge. The cloud vendors are out there and we don’t want to dictate; we want
to consume a standard service. So if they set up a catalog in their way, we have to adopt that. If
they do the billing their way, we have to adopt it or select another cloud vendor. That’s the only
option you have, select another vendor or adopt the management practices of the cloud vendor.
Otherwise, we will continuously have to update it according to our policy. That’s a key
That’s why managing your cloud vendor is really about the entire value chain. You start with
making your portfolio, thinking about what cloud services you put in your offerings, or your
portfolio. So for past platforms, we use vendor A, and for infrastructure and service, vendor B.
That’s where it starts. Which vendors do I engage with?
And then, going down to the Request to Fulﬁll, it’s more like what are the products that we're
allowed to order and how do we provision those? Unfortunately, the cloud vendors don’t have
IT4IT yet, meaning we have to do some work. Let’s say we want to provision the cloud
environment. We make sure that all the cloud resources we provision are linked to that
subscription, linked to that service, so at least we know the components that a cloud vendor is
managing, where it belongs, and which service is consuming that.
Fulton: Rob has a key point here around the expectations being different around cloud vendors,
and that’s why IT4IT is actually so powerful. A cloud vendor is not going to customize their
interfaces for every single individual company, but we can hold cloud vendors accountable to an
open industry standard like IT4IT, if we have detailed out the right levels of interoperability.
To me, the way this thing comes together long term is through this open standard, and then
through that RFP process, customer organizations holding their vendors accountable to
delivering inside that open standard. In the world of cloud, that’s actually to the beneﬁt of the
cloud providers as well.
Akershoek: That’s a key point you make there, indeed.
David: And just to piggyback on what we're saying, it goes back to the value proposition. Why
am I doing this? If we have something that’s an open standard, it enables velocity. You can
identify costs much easier. It’s simpler and it goes back again to the value proposition and
showing these cloud vendors that because of a standard, I'm able to consume more of your
service, I'm able to consume your service easier, and here I'm guaranteed because it’s a standard
to get my value. Again, it's back to the value proposition that the open standard offers.
Gardner: A couple of other threads that we heard earlier today were the idea that this standard
makes more sense, at least now, for large organizations than say startups or small and medium-
sized businesses (SMBs), and that automation is essential and that manual processes are a bug.
How do you react to that? Is that wisdom and truth for you that automation is king and that this is
designed for large, complex organizations? Again, we'll start on one side with Philippe.
Geneste: It will take more work for a large organization to deploy the full Reference
Architecture than it will be for a smaller organization. Those organizations that today use a lot of
DevOps or Agile practices that are close to the concepts that we have -- Service Catalog, Service
Backbone -- should be able to get it straight very quickly, including with vendor products and
things that aren’t necessarily fully certiﬁed, but at least for which the concepts are quite close to
what we are recommending here.
So, the large organizations will have a different set of challenges, which is that there is a massive
legacy that we need to transform along the concepts. So it’s possible. We heard recommendations
that start with B2C or do it one way or another, but the smaller organizations can get it right by
simplifying some of the implementations, getting the right tools, and moving faster onto new
I view it as two different challenges, but not necessarily inappropriate for the smaller
organizations. It’s a set of very good practices that are implementable and the description is in
the books that have just been published.
The ones for which I see an extra challenge perhaps, or at least that I see today in the industry,
are the big outsourcers -- those long-term contracts, data-center outsourcing, ﬁve years network,
and so forth. Companies that use those should plan before their contract renegotiation, exactly
what I said for the RFPs for vendor products.
When you're planning a year ahead, two years ahead, even three years ahead, to renegotiate your
outsourcing contracts, introduce the Reference Architecture and use it as a benchmark for who
you're going to contract with. If you know that you're going to re-negotiate with the same vendor,
try to inﬂuence them enough that you can have these concepts and these architectures in place.
Gardner: Sue, how about this issue of automation? Is it essential to be largely automated to
realize the full beneﬁts of IT4IT or is that more of a nice-to-have goal? What's the relationship
between a high degree of automation in your IT organization for the support of these activities
and the standard and Reference Architecture?
Automation is key
Desiderio: I'm a believer that automation is key, so we deﬁnitely have to get automation
throughout the whole end-to-end value chain no matter what. That’s really part of the whole
transformation going into this new model.
You see that throughout the whole value chain. We talked about it individually on the different
value streams and how it comes back.
I also want to touch on what’s the right size company or ﬁrm to pick up IT4IT. I agree with
where Philippe was coming from. Smaller shops can pick it up and start leveraging it more
quickly, because they don't have that legacy IT that was done, where it's not built on composite
services and things. Everything on a system is pinpointing direct servers and direct networks,
instead of building it on services, like a hosting service and a monitoring response service.
For larger IT organizations, there's a lot more change, but it's critical for us to survive and be
viable in the future for those IT shops, the larger ones in large organizations, to start adopting
and moving forward.
It's not a big bang. We, in a larger IT shop, are going to be running in a mixed mode for a long
time to come. It's looking at where to start seeing that business value as you look at new
initiatives and things within your organization. How do you start moving into the new model
with the new things? How do you start transitioning your legacy systems and whatnot into more
of the new way of thinking and looking at that consumption model and what we're trying to do,
which is focus on that business outcome.
So it's much harder for the larger IT shops, but the concepts apply to all sizes.
Gardner: Rob, the subject of the moment is size and automation.
Akershoek: I think the principle we just discussed, automation, is a good principle, but if you
look at the legacy, as you mentioned, you're not going to automate your legacy, unless you have a
good business case for that. You need to standardize your services on many different layers, and
that's what you see in the cloud.
Cloud vendors are standardizing extremely, deﬁning standard component services. You have to
do the same and deﬁne your standard services and then automate all of those. The legacy ones
you can't automate or probably don’t want to automate.
So it's more standardization, more standard conﬁgurations, and then you can automate and
develop or Detect to Correct as well, if you have a very complex conﬁguration and it changes all
the time without any standards.
The size of the organization doesn’t matter. Both for large and smaller organizations you need to
adopt standard cloud practices from the vendors and automate the delivery to make things
Desire to grow
David: Small organizations don’t want to remain small all the time; they actually want to grow.
Growth starts with a mindset, a thinking mindset. By applying the Reference Architecture, even
though you don't apply every single point to my one-man or two-man shop, it then helps me, it
positions me, and it gives me the frame of reference, the thinking to enable growth.
It grows organically. So, you don't end up with the legacy baggage that most of the large
companies have. And small companies may get acquired, but at least they have good discipline
or they may acquire others as they grow. The application of the Reference Architecture, IT4IT, is
just not for large companies, it’s also for small companies, and I'm saying that as a small-
business owner myself.
Akershoek: Can I add to that? If you're starting out deployed to the cloud, maybe the best way is
to start with automation at ﬁrst or at least design for automation. If you have a few thousand
servers running in the cloud and you didn't start with that concept, then you already have legacy
after a few years running in the cloud. So, you should start thinking about automation from the
start, not with your legacy of course, but if you're now moving to the cloud design, build that
Fulton: On this point, if you were with us yesterday, you might have participated in a maturity
model conversation. If you were here this morning for Ryan's plenary speech, he referenced an
emergence model. We've just started work within the forum on this topic. Potentially one of the
directions we're heading is to ﬁgure out this very issue, what of the Reference Architecture
applies at what size and evolution in a company’s growth.
As I mentioned, I think I made this comment earlier, the entire Reference Architecture applies
from day one for companies of any size; it's just a question of whether it's explicit or implicit.
If it's implicit, it's in the head of the founder. You're still doing the elements, or you can be still
doing the elements, of the Reference Architecture in your mind and your thought process, but
there are pieces you need to make explicit even when you are, as Charlie likes to say, two people
in a garage.
On the automation piece, the key thing that has been happening throughout our industry related
to automation has been, at least in my perspective, when we've been automating within
functional components. What the IT4IT Reference Architecture and its vision of value streams
allow us to do is rethink automation along the lines of value streams, across functional
components. That's where it starts to really add a considerable value, especially when we can
start to put together interoperability between tooling on some of these things. That’s where we're
going to see automation take us to that next level as IT organizations.
Gardner: Okay, one more question from me, before we take some questions from the audience.
This goes a little bit into the future, a little bit of the hypothetical. As IT4IT matures and becomes
adopted and serves both consumers and providers of services, it seems to me that there will be a
similar track with digital business of how you run your business, which is going to be more a
brokering activity at a business level, that a business is really a constituency of different
providers across supply chains, increasingly across service providers.
Is there a dual track for IT4IT on the IT side and business for business management of services
through a portal, through dashboard, something that your business analyst and on up would be
involved with? Should we let them happen separately? How can we make them more aligned and
even highly integrated and synergistic? I hope you understand what I'm getting at. Again, we'll
start on the panel and with Philippe.
Geneste: I'm looking at your question as, we have such best practices in IT4IT that the
businesses themselves can replicate that and use that for themselves. I suppose certain companies
do that a little bit today; if you take the Ubers and the Airbnbs and have these disintermediation
connecting with private individuals a lot of the time, but have some of these service-oriented
concepts today effectively, even though they don’t use IT4IT.
Just as much as we see today, we have cases where businesses, for their help-desks or for their
request management, turn to the likes of HPE for service-management software to help them
with their business help-desk. We're likely to see that those best practices in terms of
individualization and speciﬁcation of individual conceptual service, service catalogue, or
subscription mechanisms. You're right; the concepts could very easily apply to businesses. As to
how that would turn out, I would need to do a little bit more thinking, but I think from a
concept’s standpoint, it truly should be useful.
Desiderio: We're trying to move ourselves up the stack to help the businesses in the services that
they're providing and so it’s very relevant as we're looking at IT4IT and how we're managing the
IT services. It’s also those business services, it’s concurrent, it’s evolving and training and
making the business aware of where we're trying to go and how they can leverage that in their
own services that they are providing outward.
When you look at adopting this, even when you go back down to your IT in your organization
where you have your different typical organizational teams, there's a challenge for each IT team
to look at the services they're providing and how they start looking at what they do in terms of
services, instead of just the functions.
That goes all the way up the stack including the business, the business services, and IT’s job.
When we start talking about transformation, we must be aligned with the business so we
understand their business processes and the services that they're trying to serve and then how are
we truly that business-enabler.
Gardner: Great, thank you.
Akershoek: I interpret your question like we discussed this morning about shadow IT, that there
is no shadow IT. Some IT management activity is performed by the business, and you mentioned
as well, the business needs to apply IT4IT practices as well. As soon as IT activities are done by
the business, like they select and manage their own software-as-a-service (SaaS) application,
they need to perform the IT4IT related activities themselves. They're even starting to conﬁgure
SaaS services themselves. The business can do the conﬁguration and they might even provide the
end-user support. Also in these cases, these management activities ﬁt in the IT4IT reference
structure model as well.
Gardner: Dwight, we have a business scorecard, we have an IT scorecard, why shouldn’t they
be the same scorecard?
David: I'm always reminded that IT is in place to help the business, right? The business is the
function, and IT should be the visible enabler of business success. I would classify that as
catching up to the business expectations. Could some of the principles that we apply in IT be
used for the business? Yeah, it can be, but I see it more the other way around. If you look at a
whole value chain that came from the business perspective being approached, being applied to
IT, I still see that the business is driven, but really IT is becoming more seamless in enabling the
business to achieve their particular goals.
Application of IT
Fulton: The whole concept of digital business is actually a complete misnomer. I hate it; I
think it’s wrong. It’s all about the application of information technology. In the context of what
we typically talk about with IT4IT, we're talking about the application of information technology
to the management of the IT department.
We also talk about the application of information technology to the transformation of business
processes. Most of the time, that happens inside companies, and we're using the principles of
IT4IT to do that. When we talk about digital business, usually we're talking about the application
of information technology into the transformation of business models of companies. Again, it’s
still all about applying information technology to make the company work in a different way. For
me, the IT4IT principles, the Reference Architecture, the value streams, will still hold for all of
Gardner: Well, great. We have time for one or two questions from our audience. Let’s start with
the gentleman right there in the black shirt.
Speaker: A comment was made that you can start with Detect to Correct as an entry point into
the value chain, and then I also heard that you don’t have to implement all the functional
components. Does that imply that you can do just some of the value streams and not all, and
people can kind of pick and choose what they think will help their organization the most?
David: At a certain point, it can be Detect to Correct, but as Sue mentioned earlier, it’s where in
your business is the pain point. Evaluate the entire value chain because all of the value streams
map that to your business activity, identify where you have exactly one of your main pain points,
and start there.
Certainly, if you go to Detect to Correct and maybe your shop doesn’t have a problem type of
practice, there are certainly options that you can leave out, if that’s not a particular pain point for
you. Again the size of the company and level of maturity will determine where you actually start
and what you use. But what we do have in the Reference Architecture will help any size of
company across the breadth of that particular organization to use and apply the architecture.
Akershoek: My opinion is that you don’t start with a speciﬁc value stream, because you focus
too much on a single value stream. You still look at the overall picture ﬁrst. So, even if you can
optimize Detect to Correct, it doesn’t make sense if you don’t have requirements to deploy very
well organized or you even don’t have your service portfolio management in order.
In that sense, you shouldn't try to optimize a value stream by itself. Most organizations have
something in place in all value streams. If you don’t have any (or have a very immature)
capability in Strategy to Portfolio, you probably should start with Strategy to Portfolio. Deﬁning
what services we start to offer. What investments are needed? So it's best to start there.
But of course, most often you are not in a green-ﬁeld situation. So you hope that you have some
portfolio management capability in place. If not, maybe you need to start there, because
otherwise, you can't link your CIs to services; you have no concept of what a service is. So you
look at the entire value chain and you select the things that you need to mature ﬁrst.
Train your workforce
Geneste: One suggestion that we're testing at the moment with the global clients is starting
with the past, starting with the platform-as-a-service (PaaS) thing. Train your IT workforce ﬁrst.
They need to understand all these concepts before they move it to the business. IT will source its
own services, my development service, my test service and so on.
Once you have piloted that, move on to everything that you develop in all of those digital
solutions or solutions for the digital which typically are newer based on these metaphors and
have tools that are easier to make work along those concepts. Then, progressively, as these will
not work in isolation, they will need to work with some of your legacy, some of the data you
have in your existing data sources, and so on. You can bring those on, designing them as
services, as standardized APIs and progressively bring in more and more business services in that
fashion and try to take over the legacy of the IT progressively like this.
Gardner: I am afraid we will have to leave it there. We’ve been talking about the business
beneﬁts of transforming IT organizations into agents of change for businesses.
And we’ve heard how The Open Group IT4IT initiative, a new reference architecture for
managing IT as a business, grew out of a need at major IT vendors themselves to make their IT
departments more responsive, more agile.
I’d like to thank our panelists, Michael Fulton; Principal Architect at CC&C Solutions; Philippe
Geneste, a Partner at Accenture; Sue Desiderio, a Director at PricewaterhouseCoopers; Dwight
David, Enterprise Architect at Hewlett Packard Enterprise (HPE); and Rob Akershoek, Solution
Architect IT4IT at Shell IT International.
Also, a big thank you to The Open Group for sponsoring this discussion. And lastly, a big thank
you to our audience for joining us.
This is Dana Gardner, Principal Analyst at Interarbor Solutions, your host and moderator
throughout these Enterprise IT Thought Leadership panel discussions. Thanks again for listening,
and do come back next time.
Listen to the podcast. Find it on iTunes. Get the mobile app. Sponsor: The Open
Transcript of a sponsored discussion on the business beneﬁts of transforming IT organizations
into agents of change for businesses. Copyright The Open Group and Interarbor Solutions, LLC,
2005-2016. All rights reserved.
You may also be interested in:
• Steve Nunn, The Open Group President and CEO, Discusses the Inaugural TOGAF User
Group Meeting and Practical Role of EA in Business Transformation
• A Tale of Two IT Departments, or How Cloud Governance is Essential in the Bimodal IT
• Securing Business Operations and Critical Infrastructure: Trusted Technology,
Procurement Paradigms, Cyber Insurance
• Enterprise Architecture Leader John Zachman on Understanding and Leveraging
Synergies Among the Major EA Frameworks
• Cybersecurity standards: The Open Group explores security and safer supply chains
• Explore synergies among major Enterprise Architecture frameworks with The Open
• Health Data Deluge Requires Secure Information Flow Via Standards, Says the Open
Group's New Healthcare Director
• The Open Group Amsterdam Conference Panel Delves into How to Best Gain Business
Value from Open Platform 3.0
• Healthcare Among Thorniest and Yet Most Opportunistic Use Cases for Boundaryless
Information Flow Improvement
• Gaining Dependability Across All Business Activities Requires Standard of Standards to
Tame Dynamic Complexity, Says The Open Group CEO
• Big Data success depends on better risk management practices like FAIR, say conference