 Hi, I'm Mark Bodman. I'm the IT for IT co-chair for the forum And I'm also the outside new product management at service now So IT for IT is a standard in the industry and it's really for the business Operating model of IT. It's a functional reference model that a lot of IT organizations use to look at how they run things from end to end the nice thing about IT for IT is that it enables insights from strategic planning to Developing new capabilities to be able to put those capabilities out there to be consumed And then last but not least is to operate on those capabilities and those are all services That's we call it the service model back on so IT for IT is very Compelling as an IT operating model because it strings everything together you need to do to run an IT shop from end to end So a little bit more about IT for IT as a standard What we've found is it breaks down the silos that typically exist in the big IT organization a lot of times You've got the development teams that are developing new apps to be used by the customers or internally And then you have operations teams that are really focused on the Operations of those applications and infrastructure to make sure they're up and running for example and What IT for IT is does is help bridge the gaps between those teams and help flow the work that happens from that Strategic planning point of view to construction to all the way to operations Good thing about IT for IT. It doesn't replace existing standards It really incorporates them and what we found in the industry is that you'd have to learn a lot of individual Standards from cobit to PMI and prints and agile methodologies and operational methodologies And it's just too much for one small company especially to learn and put together It's a tool agnostic framework as well so that you can actually buy tools that plug into this framework And you can string along these integration points so that the work does flow and everything does connect between the different teams So just like any other business IT is becoming more part of the business as IT becomes bedded in products And just like product efficiencies have helped organizations grow and conquer markets IT has become a big part of that and so the efficiencies in IT to be able to understand where those Gaps or are from the work that needs to flow the redundancies if you have ten different solutions that do the same thing And IT why you have to question that and I think the big part of that is to kind of match that model that the business has with the IT Systems and the processes that match the business model to deliver outcomes that the business is really looking for So the great thing about the IT for IT standard and reference architecture is that we found that it's been very useful When organizations are looking at the tooling that it takes to run those IT processes from an end and many organizations they've grown organically and they've either acquired other companies and they brought them together and If you don't really rationalize on a continuous basis You start to get these redundancies and disconnects where you have a tool and I used in isolation for a certain thing But it's since it's not integrated anything the flow of work stops it gets caught in and it's really hard to see where that is What we've been able to find is that using IT for IT a lot of our customers the folks that download the standards They're applying it in rationalizing what those tools do how they fit how they integrate. What's the data model behind them? Are they generating the metrics to measure the value of IT? So so the IT for IT framework as a standard being used in a IT tools rationalization use case Was I recognized as a very common a common use case So recently we just last week published a new guidance document that takes you through How do I take IT for IT as a reference architecture and I rationalize the tools that you're using in IT? And there's a lot of different tips and hints and things that you need to know to make that happen And IT for IT is part of the equation But there's a lot of other things that aren't necessarily expressed in the standard that this guidance helps to identify So for example identifying not only what applications are using in each of these functions, but how much they cost Are they integrated do they have the data model that matches what IT for IT is talking about in its standard? And also what how do people like those tools? Do they actually provide the functionality and they did deliver the results that your business and even internal users are looking for? So the IT for IT standard is really in a reference architecture that takes the key functions in IT and Standardizes what they are and also tells you how they were integrated Behind that is a data model and the service model backbone that really forms what IT for IT is as a standard It's being formed as a Architecture that is used in operating models for many of the IT organizations that we talked to many of the customers So it's been really useful there and also proving able to provide guidance around how to use it We're able to solve a lot of business problems that have Traditionally not been solved within the IT organizations so another key deliverable that we went through just recently is Producing a reference model in the Archimate standard the IT for IT architecture wasn't developed with a Architecture modeling notation in mind But now we have this architecture model in Archimate so that you can just download and implement it in your own Archimate tools For the IT for IT rationalization use case What we have is organizations that collect all their tools that they have for each functional component Once they get them collected and they understand let's say you have 10 different tools for monitoring You're able to look at each of those tools and the guidance provides ways of looking at which one's better to keep Overses the one that you want to get rid of and in many cases There's many tools being used for the same thing when we when customers first do that do this And now it's a bit of a game to actually understand which ones do you want to get rid of by what criteria? Is it going to be cost? Is it going to be usability is it going to be your relationship with those companies that you're dealing with? So IT for IT is now provided in an Archimate model, which is a standard notation that enterprise architects use This guy was just published and it allows you to download the Archimate model start using it right away within your IT shop Since it's tools agnostic you can use it in any tool doesn't matter and we provide that as part of the standard deliverable So we invite you to download the Archimate model of the IT for IT standard The great thing is you can get that up and running in whatever Archimate compatible tool that you're using We also invite you to download the guidance documentation on IT tools rationalization Most IT organizations get value out of these guides right away, and I'm sure you will as well