udom is a long-term practitioner from the community who was at city for a number of years doing as a global head of cloud financial management and he was so excited about this Focus project was the working group that he actually decided to leave city and he's now actually joined the Linux Foundation um full time with us to help push this forward so we're so honored to have udam on the team with us now and thank you for for taking the sleep and for helping to push uh forward this project and we'd love to hear what you're working on with it thank you Jr my name is Adam I've been in this space for a while uh looked at this this problem aside from this is the fourth lens through which I'm looking at it I worked at the cloud vendor then cost management vendor uh then uh at City uh running Cloud financial management and now joining the foundation uh primarily to work work on Focus uh as chairs said uh so when when we say Focus we're not yelling at you to pay attention by the way we just try and tell you about this this specification uh so as you as you see here it is a open source specification for cloud billing data um so we're sort of uh working from the output and then working backwards from there uh the output is really a fan of serviceable data format uh many of you are consumers of the billing data uh and many of you as as we see in the chat and everything are very passionate about the building data and and being able to extract value out of it uh we're working from that backwards to figure out what needs to be in the data in terms of dimensions and metrics and attributes then we're trying to get that into a vendor neutral cross-cloud schema and and more importantly we're also trying to get that terminology to be aligned with fin Ops obviously there's this great framework uh the books the the trainings Etc uh we really need the cloud billing data to line up with what we learn in phenops so that's that's a big goal here as well now as you can see this is for both sides of this uh this equation one side is the cost data producers so your cloud and SAS providers that that generate costs and usage data and then on the other side are the consumers as well as the cost management vendors that that try to provide insights from this data this is a brand new project under the Linux Foundation uh it's sponsored by the Pinups Foundation uh if you recall uh there was a a open billing working group uh last year uh we paused that we handed over all that work to this new project uh and and many of the staff members here Jr and Mike and and Rob and Vaz and others have spent countless days uh you know forming this this new entity uh primarily for for the purpose of ensuring that there's a free open source uh specification for all parties to use the the vendors and providers that that generate this data as well as organizations and consumers of the data that want to use it so that's a very important part for us next slide please so why Focus uh like I said I think I think all the folks that went before me made probably a better case than than I can make uh but but I'll I'll summarize it this way we're trying to build trust uh in the cost uh and usage data or billing data uh because your organizations want to make value-based judgments or decisions about using Cloud about how much Cloud about what to use cloud on Etc and in order to do that they need a comprehensive view uh that about your costs and usage of using Cloud uh to to make those decisions secondly uh our finops practitioners lives are are very complicated today as sanjana just highlighted uh it's impacted by the complexity and the inconsistency in the in the data so and that complexity and inconsistency grows linearly as you add more vendors or providers and that's a fairly common thing as your organization matures you're gonna use more uh more providers uh but also you want to make decisions based on broader information Lauren made a very good presentation in g-spore uh you know including all the shared components uh and and I saw somebody ask you know what about labor costs and Etc so uh your organization as a mature is going to want to make these decisions not just based on one Cloud uh vendors billing data but the overall picture so that's that's where we we come in and and um again I don't I don't need to make the case here that many of you uh have have called that uh this is a problem that that you face uh in in terms of thriving fin Ops uh in in your organization so here's a here's a visual representation of what I'm talking about as you see up top uh you're getting this uh different proprietary formats uh and schema and terminology and the burden is on the practitioner to try to do some magic and put this together uh in the future this is this is what it uh we we think this is going to look like uh where many vendors will lean in and the providers will lean in and produce the data uh in uh Focus specification uh it if you're a brand new uh uh provider you're probably just going to adopt uh this specification rather than try to create yet another proprietary way of providing uh the the billing data if you're an existing vendor you're probably looking to incorporate this uh into your billing data and cost management capabilities today uh and and some sort of um uh providers may not adopt the specification and that's okay we will have the ability to use our finops community uh and the broader Community to create open source connectors uh that convert the data into the focus specification so we can still get the benefit of a lot of the normalization um so yeah that's uh that's that's kind of the reasoning and I can tell you firsthand I mean this is this is the problem that I was solving at uh at City the last few years we had a broad platform across multiple Cloud vendors SAS vendors uh licensing and other internal costs and our thousands of applications that want to use cloud uh they wanted a overall visibility a single bill for their usage uh not you know to do cost Management on every single vendor individually so uh hopefully this is this is a common problem that that many of you are facing as well and and we'll get benefit through this specification next slide uh just tell you a little bit about the roadmap as I mentioned that the team's been working really hard to get focused stood up uh we have the steering committee formed as of uh as of March uh working groups so then we started working on the the contract license uh uh sorry contributor license agreement uh that got published last week uh we've had I think uh seven or eight people that have already gone through the process and gotten their approvals there's probably a dozen or more people that are currently going through the process so a lot of interest we we've kicked off the first working group earlier this week uh there's another meeting happening today to to work on the stuff um and and we're kicking off a second group most likely next week uh both these groups will be working on this initial 0.5 release that we're targeting uh for FNAF sex uh that is targeting a lot of cost reporting and chargeback use cases so I saw the discussion earlier about amortized and and using that for chargeback and all that kind of stuff this is these are exact problems that we're trying to make sure we solve with the specification uh so we're starting with the cloud service providers uh costs and then for v1.0 and Beyond it's really about expanding Beyond false reporting and chargeback to other phenops capabilities as well as uh adding support for more uh data data providers so SAS costs uh third-party and internal costs Etc next slide and finally how to get involved um just the the same pitches as what's been said before these are the early days of this specification uh it's a great opportunity to get involved in and really start helping to form what the specification is doing what problems it solves and how we end up solving those things we are on GitHub that's where you can see our progress see our issues that we're working on how it's organized in diversions Etc uh the contributor license agreement uh that's that's an important part that's also in GitHub uh this is necessary because this is a closed group for contribution uh because we want to ensure that that whole royalty-free uh specification so your employer uh will need to provide you an authorization to come contribute to uh to the specification uh connect with us on chat Dash focus and our website we just updated a bunch of content there uh yesterday so yeah super excited to to see uh all of you uh get get involved uh and contribute thank you Jr here from the finops foundation thank you for watching please go to finnops.org if you want to get plugged into this amazing community and of course hit subscribe right here on YouTube to get all the future content hope to see you soon