PubSec Curator User Group

Right. I think we're pretty much good to start. Thinking about getting going. So welcome, good afternoon for those people who have been able to join us today. Once again, if you do have any questions, your lines will remain muted throughout the duration of the workshop, but please feel free ask questions, via the Q and A or the chat facility. We're delighted that you are here join us, please keep an eye out on our other upcoming events. We have specifically tailored toward the public sector. With that, I'm gonna pass you over to Max, one of our analytics consultants, who is going to be leading today's session. So over to you, Max, Thanks, Vicky. Hi, everyone. Great for everyone to join. So welcome to the public sector curator, Usubra. Today, we're, we're aiming to discuss within this session, just around the information. I mean, we're gonna be sharing information here from various different avenues of our our, public sector, client base. So there's a few different guest speakers that we've got that we'll talk about, when we get to our agenda shortly. And really a focus here is to kind of get to know some more faces of people within the public sector that are using the product and, and have analytic spaces that are leveraging, particularly into voice curator, but also other solutions as well, and looking to collaborate in gains of knowledge across the the wider, public sector landscape. So often it feels like what we're doing is incredibly bespoke. I find with, with with a lot of the implementations that my leverage curator. And, I think sorry. Let me just get those get smooth. There we go. And often, I think more and more, I feel like most of the clients that I work with particularly can be summed up within about a sixty percent similarity. So there's probably more that are we're aligned across in terms of our goals with, our data visualization platforms, our data analytics solution at the back end as well the curator front end as well. So there's a real value in having these sessions I find in kind of learning from each other while discussing them in this wider audience. We work closely with lots of the attendees that I can see today. So great to see you so many faces and familiar, familiar names with Lyft. So welcome everybody. And we have a really stacked lineup of, curator goodies to get through today. So first off, let's introduce the team before running through the agenda of, of today's call. So, a lot of these cases hopefully are familiar to you. Let's quickly introduce, who we've got here. So myself, I'm I'm Max. I'm, an account lead for a lot of our public sector clients, as well as a solutions architect here at, at Interworks, and using Tableau for a very long time, and lots of curator, installs and, and skidding and, and, of included curator and lots of solutions that we've prepared for clients. So you're, yeah, you're in you're in good hands with, for me, from a curator point of view. We've also got, Roan here as well. Rowan, do you want to introduce yourself? Yeah. Hi. Apologies from Dan as well. He's on another call that he couldn't get away from. But, he and I lead up to public sector work that we have together and, very excited to be in create and become a part of that, in addition to the other technologies that we work with, Tableau and Snowflake and Dataiku and all the rest. So, yeah, I won't take up any more of your time. Thanks, Max. Yeah. Amazing. See if we've, over ruined is gonna be, familiar to to a lot of people as well. So, yeah, apologies from Dan as well who's, who's who's at another event and we can, can make it. We've also got Patrick, but Ruth Patrick is in the attendees rather than Vable. So I'm sure Patrick sense his, his warmest regards to everybody who's also on the commercials team. And we've got Mohammed who we will, chat to later on. Romamed, to us around some of the, technical features that we, that we can implement, within the curated product. So it's more from more data. We do have the Q and A section. We have a we have a chat section as well. So I thought it'd be nice to to hear from people who have, have joined the call appreciate that we do have muted lines, unfortunately, some managing lines when we kind of scale these calls out becomes more and more tricky. So that said, we love to hear from you and chat So, if one person, at least from every organization, could take a second to introduce themselves in the chat, and hopefully get a feel from the range of the the different attendees that we have on the call. So yeah, just ping a quick message in the chat while we go, beloved to hear from you, who you are, what your organization does, what it uses curator for, that'd be that'd be excellent to hear. So while people are doing that, I'm sure, frantically, starting on their keyboards to try and, try and write some, some useful an introductory, sentences about themselves. Let's quickly go through the, structure of today's user group. So this is a very rough guide in terms of the times we're expecting to hear, and we can be verifiable here often something is running over that you expect be short and some things that are short tend to tend to take a long time. So, we can kind of move these around as we go, but just as a list of ordered content that we expect to cover off today. We're gonna start with me chatting like this for a bit, which we have pretty much come to the end of. You'll be least a year. We're gonna talk about today's user group and talk about the agenda that we're looking to to get through, as well as then, moving into our first of our guest speakers. Today we've got two different organizations within public sector that are gonna be providing guest content for for a session. The first being, Chris Jenkins is a marketer from Southern Health, NHS for trusks. So that's, the first one that we're expecting to get to in around sort of five, ten minutes. And then, obviously, we've got the Q and A section. As we go throughout our guest speaker, conversations, please feel free to be checking questions in the chat and then I'll monitor those and I can bring them up, as we finish the section just to make sure that we're not interrupting people throughout the flow, but, we will cover off your questions whether it's live, in the in the chat and q and a session. Or if you have anything else after the fact, we'll we'll get back to you. We don't even into their session. Then we've got a little bit of a section from myself and Mohammed. So the inter work section is kind of sandwiched in the middle of our guest speakers here. We're gonna be talking a little bit about why we embed generally how, you know, the the focus of curator is doing bad analytics and and other things within or, within our web platforms. So we're gonna be talking about the why we do that. Then we're gonna be looking at demo microsite. So, a site that you can all leverage is publicly publicly available. If you want to show people the curator platform, it's NHS specific, so public sector friendly, and, it's all mocked up, to to be convenient for if you want to show somebody that curator thing that you were talking about. So, we'll also be then leading into our new features and some features that you might not necessarily know about. And Mohammed's gonna take us through that who's, part of our technical team, on the curator side of things within your Then we've got Peter Cunningham. The cabinet office is gonna help us, to to to go through a presentation of how the cabinet office have implemented, the curator. We're gonna be looking at some really cool content that peers prepared for us around how they've run through POCs, the network considerations from a technical point of view and how they've ultimately got to where they are today, using the curator and, and tablet generally. So another really great conversation there. And then finally, we're gonna wrap up doing a quick feedback session, any desired features. Again, if you want to check things in the chat, it's gonna wait till the end and please feel free to check-in, any comments and feature requests that you have, and we can discuss them as we go. And then finally, we'll just wrap up and do some next steps. So as I said, in the start, can be flexible. We'll we'll probably move this around, as we, as we continue through today's session. Hopefully, that sounds good. See there's three things in the chat already as we've, been rabbitting on there. We've got in reverse order as it's near the bottom of my screen. We've got Caroline. Hi, Caroline. Nice to meet you. You've got Southwest London, and since George's Mental Health Trust. Great to have you on the call, Caroline. Welcome. And we've got Harry, Harry Paul, So data manager, one care quick to speak to you, Harry, largest GP federation in the UK. Don't currently use Intuitants, but looking at developing our resources to potentially integrate, into our usual process. Very welcome. Hopefully you'll get something, from today's call. Hi, and if you want to reach out to us after the call, then please feel free. And we've got an at, roch deal, pencil, creating dashboards, great, and good company, and love creating dashboards. So, both welcome, everybody. And, yeah, please feel free to continue using the chat as we go. So without further ado, we have Chris and Mark NHS Foundation Trust. They're gonna take us through, their, presentation. We've got, in fact, oh, but you do your own introductions. If that's okay, Chris, I don't want to butcher it. I'm sure you're more than capable. Would you, would you like me to stop sharing so you could one of you can share your screen? Yeah. That'd be helpful. Thank you. Max, if you're really good. Perfect. Start sharing here. We also, Mike, if you wanna go first. Yeah. I'll if you want to, that's that's cool. So, yeah, well, thank you everyone. Thank you for joining us here, and thank you for giving us this opportunity to kind of showcase some of what we've done. So, my name's Mark Kate. I'm head of data and insights at Southern Health, and I'll let Chris just introduce himself. Then we'll talk a little bit about the organization. And I'm Chris. I'm Mark Stepty. They're not when it comes to curator. Oh, right. Next slide, please. Helen, I will get the technology going. There you go. So who who are we? Because I think it helps to provide some some context. So we're Southern Health, and we provide mental, physical, and public health services across Hampshire. That includes things like mental health acute inpatient units, physical health community nursing, health visiting, for the newborn children, etcetera. So kind of a really diverse range of services. I think that's important because it talks about in when you'll see later why your age has been really important to us because we're dealing with so many different, like, diverse groups of of users, if you like. We serve a population of about one point seven million It's about to rise fairly considerably because we're currently going through a merger, with two other local trusts. That we're working through. And again, we're really hopeful that curators gonna be absolutely pivotal to that because we can effectively, you know, bring through analytics from the different organizations prior to merging it all into the, you know, platform. So it seems seamless for users before they actually, you know, we we do do full mergers. It's a diverse geography. So right from inner city, Southampton, right person live with us, you know, there are areas of deprivation to kind of some of the most affluent areas of the country and sort of like the rural, new forest area. With information team, are actually now rebranded to data and insights team. Because we think it much more kind of says about what we do and kind of Tableau Center of Excellence. We've been using Tableau for about ten years, and our curator instance was launched about a year ago. So that's kind of where we are. Group of analysts, kind of data translators, so working with our services to understand the information, and data warehouse developers. And I think we're all about trying to promote what kind of learning and development culture and hopefully some of that comes through in, the way we've tried to roll out the the the kind of curator platform. Thanks. Next slide, please. I hate saying that now. So we're over four curator. So, we we kinda have dashboards across a load here as our trust business or clinical activity. So things that are sort of operational nurses, doctors would like to look at HR information that's perhaps relevant to managers, finance, information about incidents that can be managed by our quality teams, customer experience so we can kind of understand how we're doing. As well as some kind of public health data to help with planning, but that was a bit so we probably weren't great, to be honest. Fairly high usage about two thousand six hundred regular users, and about a hundred and one thousand views over the kind of ninety day period. And we were set when when I did this slide, seven years working with Tableau. So this was this is still clearly been taken from when we were trying to procure the product and hasn't been updated. So We'll move on. So, just to mention when we, there was a lot of debate when we launched as to what we call the product. So we went with insights on the end because we felt it kinda gave us that that really clear one word kind of phrase of what we were trying, to achieve. And notice there's a kind of lab there, and that's because of our branding. So, what we've done, pop on. That's fine, Chris. Thank you. What we've done is whenever we do a presentation with our staff, we always start with the, chart on the left hand side. The first question I will ask is does anybody know who created this dot diagram? And, of course, it was, the lady on the right Florence Nightingale, and this often surprises a lot of our clinical staff because they would say, you know, we we know, you know, Florence is the lady with the lamb, but of course, she actually spent the majority of her career as a kind of public health consultant and with a massive advocate of data, and probably was one of the kind of pioneers of data visualization. And she was sort of one of her phrases was, you know, we must use this kind of data to, you know, get through the word proof ears of for politicians who, you know, don't understand. And and the diagram here was all about her, trying to show that people in, the bowel war were dying from actually infection and not from wounds. So they were coming back to a hospital, and dying there. So it kind of is threaded throughout the stuff that we do. And it's all about trying to show how the data is being used for care and improving care and not just for, you know, commissioning and working out what we're doing and trying to be more productive, you know, all important things, but that's exactly what it's about. Right? Next night. So why do we need curator? So One of the problems we had was we had said we had all these diverse services. Some of the dashboards that we have are relevant to everybody, perhaps like a sickness monitoring, something like that, but actually they're a lot. They're very specialist. We had them all in one project as it was in Tableau, and it was just a complete kind of mess of trying to find what you needed. And one of the things we really like with curator is your ability to be able to embed the same thing in about twenty different places, and it look as if every user's getting a bespoke experience, The other problem we had is, and it's probably something that it'll be interesting public sector people that are on the call is how, you kind of engage guidance for people, because we often find that, yeah, some of our users need quite a lot of guidance to get started. It was kind of we had something in shared point and something else in the Tableau server, and and, you know, never the two ever met, and it was kind of a real challenge from that perspective. Talked a bit about population health. There's a ton of stuff out there that NHS Digital and other colleagues probably on the call produce and and and use. But it it doesn't ever get looked at because it's something else, again, that somebody needs to go and find. So can we embed that within curator? Yes. Absolutely. Design to drive a customer engagement, so create this culture data literacy. So again, with, you know, that the Florence theme and some other bits of kind of fun stuff that we do that we can show. And and this has been part of a kind of key, Adam to consolidate performance management and performance management indicators of bringing everything together, into one place. And at this point, I think we can flip onto our demo. So I'll give Chris a moment too. Let's close that there we go. That's okay. So hopefully this is familiar to some people and it's kind of a set up and layout. So I'll I'll just talk a little bit about so this is our home page. So it's a bit of a mixture of some text from a technical point of view, I think, isn't it, Chris, and, dashboards. So we've got some got a couple of dashboards embedded in there. The the top dashboard is really to try and give an indication around the trust that all the relevant data sources, have updated for that day. And oh, yeah. And we you're looking at the most current data, essentially. Oh, so do those faces get sadder as the data gets. Yes. Oh, that's great. I love that. Yeah. Yeah. So there's kind of three signals there. And we were finding one of the things again was our our keeping complaint or question from people as well. I looked at this and it's not And it, you know, we've just not there's been a failure somewhere and we've not received our training data or something like that. So this gives me a really quick guide to see that. The bit below again, we just wanted to celebrate what the trust does. So this is a live dashboard, which just picks up our warehouse what we did yesterday. So we provided care to four thousand four hundred and twenty eight unique service users. I mean, there are six hundred and twenty eight people in our inpatient units overnight. So it just gives a bit of an indication of where we are below, we've got a kind of rolling, thing. So this is another embedded element of kind of icons. To kind of just showcase things that are happening at the moment. So, bottom left one's actually quite interesting. So, just clicked through on there. So we're part of a local kind of data and analytics center excellence kind of similar to this user group. We had a kind of summer celebration event, So just again, gives people a chance to see some of that. It's just something a bit different, you know, a bit of a break in the day. This is actually a winning power BI dashboard from somebody in. One of our door sit, neighbors produced for the competition, the, so we gave a a challenge with rider the dataset then they had to actually, do think this was the winning, the winning design, which has created quite a buzz, across the, across the community in Samantha, actually, showcased it on a on a webinar similar to this, last week. So, yeah, it just gives a kind of little fun introduction. Majority of what we do is, on the left hand side, so we've got a menu with all of our different areas. So one of our sections, specifically is guidance and support. And within here, we've got a number of you know, different bits to quickly get to, what you need to. So how do I getting started insights? It's quite interesting. This is a thing of actually trying to embed how do I how do I do certain things and what are the tools that help me to do it? So if I want to understand my caseload, and for one to understand my team's training compliance, what are the various different reports and ways that I can do that? So they have a kind of guided experience to the things that, that need to happen. And this can be quite kind of agile, I guess, in terms of things to be added, taken away as different things come into the trust, the the need to kind of kind of happen. Where are we gonna go next, Chris? I think it was mine. Myself. It was, wasn't it? There we go. Yep. In Texas well rehearsed. One of the things we were keen to do was was my son, Chris, do you wanna just mention how this this works So we've gone directly into the port. We've done no filtering, but it knows who you are. Yeah. So we've we've gone through an exercise of linking everybody's active directory accounts to their, EHR kind of profile and their ESR profile, which is the, HR kind of profile. And then surface that in Tableau to try and give a more personalized experience. So what should happen is when you look I mean, to look at your yourself you can either look at your clinical activity or you can look at things like your training compliance. And I've got some training to do, but the dear and the premise of around this was trying to give this personalised service to people within the trust rather than having them unpack for what they needed on a day to day basis. So, yeah, that's what we've done in the Tableau report around myself. Then we don't know if there's anything else you wanted to mention in there, Mark, at all. I don't think so. I think it's not. I don't think we see it. It's something where it's gonna be a catch all for everything. But it's, I think one of the the problems we have very busy, you know, nurses, particularly our community nurses that they're out and about in people's homes You know, if they there are really important things around training and outstanding actions and things that just looks at things like their no progress, no things that they need to outcome or care plans they need to update so they can quickly get to it without having to go through, you know, as few as clicks possible. So this was really the idea. We've got a team version as well, Hamwig. Yes. If you're a team manager, you can get everybody in your team, from that perspective. Okay. Then we were gonna talk about my service. Yeah. So I think this comes back to that concept, doesn't it being able to so a number of our reports are universal, so like our case load reporting, our training, but actually we can embed some of that into every area here. So we've got, community services. It's quite a good one as in services. Again, nurses, they're out seeing people in their homes so we can embed everything that's relevant to this, and Chris, do you want to explain explain quickly how we did this? Yeah. So I think when we first configured curator, we kinda used the kind of menu structure out of the box. And then I think we quickly decided actually the best way to go with this was to assign keywords to all the content, and then off the back of the pay of constructing pages, we could then bring in, like, the the tiles that you see using those keywords and present the kind of I guess the reports in that fashion rather than your your traditional kind of menu structure. Very nice. Yeah. I love that. Just adding keywords that people don't necessarily see, but using it as a selection for the kind of dynamic page picker of content. Right? Correct. Correct. Then, Mark, are you gonna talk about the different content we've got in? Yeah. Some of this stuff is and one of them is very new and has a broken thumb now we need to look at, which is interesting. So we've got a number of bits will be tablet reports. Some of it is SSRS, I think, as well, isn't it not in this particular area, but we've got some who run a child health team that all they do is check up treat children come in, they tick them up a list and jabbed them for a flu jab. So they just want lists of kids in a school so that kind of serves that purpose We also have other NHS trusts and sort of data teams around, we'll probably know they spend half of their year doing benchmarking side, and then it never gets used. So what we've tried to do is embed, you know, external content. If you click through on that, the actual benchmarking reports that you get back from the benchmarking networks is where everyone across the country submits their information and now all directly embedded, within the product again, it's not, say, if somebody wants to get some intelligence, they're not having to go off and find this on the benchmarking networks website and having a log in those kind of things. It's just directly embedded here, for people to to use specifically. Just take us back to the home menu and then our trust. Yeah. So I guess this is more of a kind of managerial level area where I'm not working in a specific service, but I'm wanting oversight of kind of everything. So HR workforce is a really good idea, so if I was in our our workforce team, or I was managing a division, so one of our local divisions of of services, all the things that I might need, a kind of contained here by themes, if I want to look at HR workforce types up around vacancies, etcetera. It's all available. In this particular area. We've got information about benchmarking there. So again, that's all about things being in two places. If you're doing benchmark across the whole organization, every keyworded and also embedded here. So, you've got everything together in in in one place. Then we should spend some time, custom insights. No should explain what was going on here. So The analyst will produce what we call customer ad hoc reports, and they're not reports that we really want to, fifth in the kind of overall structure of insights. But what we've done here is we've actually created a a page. And in the background in Tableau, we've kind of created a project folder where the analyst go and drop their report in there, and then it will automatically sort of beef, sir, fifth in this custom insights area. It doesn't obviously have the look and feel, of the rest of insights, but it just means if I've got a report that is only gonna, you know, be available for a couple of weeks because for a certain project, we might just kind of surface it in here and then they can click through and actually just view the report in Tableau server itself. But if we do send them to Tableau server, we turn off the ability navigate effectively. So that was kind of our compromise with with the team around. Yes. We don't want to clutter up. The main offering with all these reports, but we need somewhere where we can surface these reports for that for those short term on earth projects. Do you know that people clicking on these are gonna have permission to see that report? Or is that a bit of a So generally speaking, the permissions that dealt within Tableau server itself because of the very specific projects, it tends to be only a certain certain kind of audience will get access to those reports anyway. Yeah. Yeah. Yeah. If you are right, Max, that's one of the things probably it it doesn't quite do at the moment because it wouldn't respect that. But, well, the the permission would be respected, but you the report could appear here and anybody's clicked through effectively. You're absolutely right. So Yeah. So it's it's something we do, and the teams kind of manage in individually. But I think the thing we would say is, you know, you you'd be given a a thing to come in here. You shouldn't it's not something you would come and sort of be digging around necessarily. Right. No. It's really cool. I've not seen people do that us has been because we we we we spent ages and we saw brainstorming how to solve the problem of not create because we didn't wanna create a minister a massive kind of bit in in in curator itself for it because it would just get really messy, so it just helpful to do it, do it this way. Want to have a clear path further resources? Yeah. So this is where we kind of bring in other stuff throughout the kind of things. The population health is kind of massive, if you like. Now We said before, didn't we at the start, but we don't really do enough, enough, or we don't have enough kind of resources. So wherever there's a resource out there, we've shamelessly embedded it within the website. So this is NHS England's registered GP practice. So we used to consume all the GP practice data and produce a report and practice populations. It's like, well, that's your perfectly good one. That's out there for NHS England do. So this is directly embedded, so people need to see it. It's it's here, directly for them to to access, you know, and they're not having to pivot and go and find it in Google in search for anywhere else. So I think there are things that people kind of are amazed. Like, wow, this is brilliant. It's like, yeah, they it's been there for ten years or something. It's just never been utilized. There's other things in there like the local councils, JSNA, so joint strategic needs assessments, which are, you know, where they've yes, it takes you just out to an external website. It's really simple, but again, it's another way of getting to that information that is kind of relevant to you. What did you like? Do we just wanna touch on the, our kind of communications form as well? Chris? Yeah. So, along with introducing insights as well, we've changed the way that people contact us. And I mean, it'd be interesting, Max, maybe because, I know you guys probably use a data manager for keeping some of this information, but we decided to use a Microsoft form and embed that into the the page. So we we do have a form where people contact us, and that's just part of the site essentially. And yeah, it's just really giving us a bit more control rather than just all the analysts getting individual emails in. We're now sort of centralizing how people kind of contact us essentially. Again, it's just something that curators allowed us to do by allowing you to embed different types of content into your pages. I I think it is it's helped as well with the fact that, you it's very guided, isn't it? So if you are say I've got a problem. I want a piece of new analysis, and then it guides with questions about what what thing are you looking for? What's your problem? What do you think is wrong? Some, we limited success in people answering it and putting the information in, but it is improving to don't just get a, you know, a blank email of my insights doesn't work or Yeah. Things like that and then trying to work out what what's going on. So, it's been really helpful from from that perspective. Like your your red asterisks on everything there. Yeah. You've got validation. We want some information here. Do not quite go. Yeah. Yeah. We make them work for it, you see. You know, we we don't. The people are trying to waste the time. We've not quite got to the point where you kind of put in various various answers and it says, just gives you some random. We're not able to help you with that query. Please go and Alright. Yeah. We can we can dream. No. I think that was everything we wanted to talk through, wasn't it? Sorry. I don't think there's anything we're happy to obviously take any any questions. I think, yeah, next and next steps for us to probably, accept this this project that we're doing at the moment, to merge three locus are emerging with a local kind of trust that works in the beginner city areas and the isle of White. So they are from a community and mental health perspective. So they will bolt systems that, you know, they use at the moment and will need to be used, still used in the short term, what we think of know, a longer term data warehouse solution. So we're really hoping to be able to work out the permissions, which will be the key bit, so that basically everybody can access insights, and we can have different, you know, menu options for our other white colleagues, our selling colleagues. And then as things merge together, they're just slowly change the keywords in the links so that the, you know, a different report appears one day, and and and it can kind of appear more seamless for the staff as opposed to having to say, oh, you need to go to this whole new link. Now you gotta do this. I think that's gonna be up. Our next big project That's really helpful. I I've got lots of questions in comments. So, jump straight in, but as a callback. I've, I've got it covered here in terms of questions. One comment that I, I wrote down right at the start your your smiley faces at the top. It's great how seamlessly that fits in. When you were, when you were telling me to start there that this is a dashboard, this is a dashboard, this is a dashboard, might not be obvious to people without curator, but just just to kind of touch on that a little bit more and and let me know if I get any of this wrong, but, the this we've got dashboards here. Right? Is this all one dashboard or is it several? No. There's two dashboards effectively going on here. Yeah. So maybe we've got a one here and then we've got another one here. This one here. Yep. Yeah. Amazing. You you would know. Right? It's, that's that's, super, super useful. And a nice way of getting the output that you want, it doesn't it shouldn't actually matter where that iframe is rendering from, whether it's hosted on the courier instance in HTML or whether coming from Tableau from JavaScript API. It shouldn't matter. We just want this to be displayed, and we can get there by a goodbye group. I think that, and that works really well, especially with your up to date data that you're that you're that you're showing on your how many people you've, serviced, yeah, I mean, service users in, in the past six days, I guess, in your six twenty eight in patients. Yeah, it's it's great. There was also the, the the the the foreign floor is mine. Gail stop Bloomberg. I don't want to interrupt you in the start, but this is brilliant. Have no idea. This is completely new to me, but I'm gonna steal that and and use it for sure. And the the chart that you had in that introducing insights the, I guess, it's, like, a sunburst chart. Right? Like, it's quite tech, even for nowadays. It's Yeah. Yeah. Yeah. Yeah. I think it was just referred to as a Coxcombe chart at the time. There's if even if there is a fantastic book, and I can't remember the name you can buy, which has got the full history of everything she did, wasn't, I I will try and find the detail. Let me look at those American chat who who created it. Mean Yeah. No. Amazing. She worked with. I think it was William Far, who was a, mathematician at the time. And there was that it was based at Somerset House in London, Right. They produced a lot of this stuff from there, and used it quite a lot in the other campaigns. Yeah. I know. Before before her time, like, people would just try and convince decision makers with tables. And, you know, which is the same thing we spend our time doing now, like, hundreds of years later, like, I don't know, get out of excel or something to able to make a charge because that's what works. Yeah. She was literally one of the first data visualization, records of data visualization anywhere. And, yeah, she was an incredible woman. Lots of campaigning for worker sex worker's rights and lots of other very impressive stuff. So, yeah, That's yeah. My daughter's name's up there. So there there you go. Wow. We've also got Napoleon's advances into Russia as well. In the chat. Thanks, Harry. I'm gonna definitely look at that. That looks similarly old school in style. Looks like the grade blog education dot national geographic dot org. Yeah. Extra information for anyone that, as a as a late afternoon, so that's a power bi dashboard as well. Great. I'll be I'll be giving that a read for sure. Alright. That's that's fantastic. Other questions yeah, I I got notes on the the the keywords of pages, the selections. We're gonna be touching on that a little bit, more later as well as the kind of the the concept of finding the analysis that you you mentioned. You also mentioned duplicating, having things in more than one place as a deliberate strategy. Is that? How does that work? How do you where where do you stop? Do you just put the same link twenty times and hope somebody finds one of them? Or how how do you so I think the the idea is, I'm I'm trying to think of it as a caseload is a really good example. So everybody's on one clinical system. So you have one report that analyzes cater loads and numbers of people must report. So what previously would have been in a project somewhere, and and the the the the Tableau issue is if you have a separate project folder for children's, adult's mental health, you have to duplicate the report into Tableau seven multiple times, but here exists in its licked into curator once. It's but we just keyword it against every single service. So it's only in insights once. If you search for it, it will only appear once in the search bar. But everybody can see it. So everybody thinks they're getting a kind of personalized experience, which they they are, I guess, but actually no dashboard is ever in the system more than once. It's just that it's surfacing in in all different places. Right. And you'd avoid I'd I'd avoid that. Yeah. If to to have, sorry, to in Tableau server having multiple dashboards that should be exactly the same, just so that you can put them in two different folders. Yeah. Is. Yeah. Yeah. And we do and that's what we never did. We we had one big folder of everything that, of course, you it was a hundred plus dashboards and you couldn't find anything. Of course. Yeah. Yeah. I think the referrals the referrals and appointments dashboards, another example where it cuts across every service. So you end up having that under every menu item. That's good. I presume this view is also different for you as a super user admin who's got can see everything. That when people come in, that that's gonna be less trusted, there'll be less menu links, less dashboards based on what they can see. Yeah, but potentially, yes, we've got a fairly flat position structure. So, we we have a kind of kids or identifiable group. So if you need access to identify all information within a report or reports, that's our separate group. Everybody else kind of quite open, then we don't put identifiable information into reports. But it it's a really good question actually, Ron. It's something we're having to think about with the merger. In terms of maybe changing some of that. So, yeah, it will be something we'll probably need to explore. Yeah. It's really useful. It's not even really a feature just a a quirk, emergent quirk of the way the rest of the API works, right, or the way that your your login credentials actually surface things in Tableau is that you don't ever see anything in a list item that that you don't have permission to see within Tableau or the other supported products as well. That even goes up the chain as well. So if you've got a folder or a NAND item that has nothing in it because your permissions don't allow you to, then you don't see the, you don't see the nav item above. So it just tends to kind of clean everything yeah. But again, the the flatter your permission structure, the less that has an impact. Yeah. Amazing. Any more questions? That was brilliant. Thanks so much, Chris. This is Mark. Thank you very much. Great to see and say your your instance there. Let me quickly share my screen. Hopefully everybody can see that. What we're doing for tagging, looking looking pretty good. Yeah, it's it's perfect. Okay. So that was Kristen Mark. Thanks, thanks again. I'm sure everybody shares my gratitude. Yeah, really useful talk and really, really great to see how sort of impactful, your career instances. The more you see these in the wild, the more you can see how they kind of diverge from each other and how much, cool interesting things people are doing with it. Like your bespoke worksheets there, though, listing how to upload dashboards, this is miscellaneous, any other stuff really cool, as well as your, yeah, your, your use of keywords and the kind of structured tiling content as well, which is great. Love it. So, I want to take us through a little bit very quickly on, some of the more kind of interworks side of things, So I want to touch very quickly on why we embed, why we we use curator at all. Right? And I know this is gonna be singing from the same hint sheet as a lot of people, that already have curator. Some people that don't have curator might kinda highlight some of the extra benefits that we might have And then we're going to talk all about, some of the demo sites that we've got very quickly again. And then, Mohammed's going to take us through some of the new features and some of those features that you mentioned necessarily know we're available, incubator. So we'll start us off by just thinking about, again, why we actually embed? And as how we get value from our data visualization products generally as well. So we've kind of got this beginning mess of a platform, a data platform that doesn't. Really reflect anybody in particular, honest. So hopefully this picture resonates from that kind of platform overview perspective, and it kind of feels a little bit like most people's analytics landscapes. We've got that raw data on the left hand side and those bits that say data. Those raw data, they come in various different repositories It could be file based. It could be coming from APIs. It could be coming from databases that somebody else manages and I'm giving you access to. And we tend pushing these data into data warehouses, data lakes, data lake houses, and when to do that, we might use again APIs, OTBC, JDBC, direct file uploads, NTP, FTPS, it just gets ridiculous after a while. Right? And everything just kind of blows up. It's all of this complex nuance of stuff that happens on the road. And generally, we get Tableau and PowerBI and other, competitor products. Whoops, here we go. Over here in this section, and these products kind of help us get a bit more sense, make a bit more sense of that that landscape by kind of reducing all that noise a bit of who I'm saying, but these are all just connections. It's up to you to now put a governance layer so that people can actually find the data coming from those connections. In, into, your data visualization platform. Now, their goal there is, obviously, so that you have everything within Tableau. You have everything within RBI, you have everything within look at your thought spot or any of the other ones that are on the market as well. And even if your data is fully organized, it's it's generally gonna be confusing even if you're staying in one one of those projects as you grow out and as you scale. So, the difficulty then is as we get larger as an organization, NHS, a great example of this is of I've been meaning that we even looked at, the ability to embed other products even within, within Southern Health Administration there. We've got PowerBI in there. Difficulties that as you scale out in all of our enterprise customers that we work with have more than one visualization product for various different reasons, but we have this overhead on users now that to get information about topic a, they've got to log into this URL and get information about top b, you've got to log into that URL. And it's difficult for them to kind of reconcile that and understand where they'd go to get which information. And then you just end up with this Oops. I just touched my microphone. That's not good. You end up with this kind of big long list of bookmarks that you then save of different stuff that you need to go to to different places, and then you've got other stuff, and kind of related stuff. And then we've actually even got, a website that we use internally called tools where it shows you all that tools that you might have to use for different solutions because actually it's really difficult to, keep track of all that stuff. And that's just into work as a small company. So it gets worse as you get become a bigger company. So a common goal of embedding a lot of the time is to kind of take that headache out of things, so make sure that you're a embedded solution reducing that kind of knowledge overhead, making it easier to have that one endpoint where you can go to to, if not reduce entirely minimize the number of different products and different HTML pages that you have to go to in order to get the information that you need. So one site to govern various different data tools and embed lots of different potentially links in there to extra content that you might have that you find interesting in in related avenues. And again, so many help that I have great examples of that, where you've actually just brought in dashboards that are publicly available from PowerBI and some of the products, and kind of nested it alongside all the other ones. Right? So you don't have to have links and all these sorts of things that sort of take you out of that experience but kind of seamlessly integrating it. Now that's not all we need to do with embedding. Right? There's lots of other things that are great about having that embedded, that that embedded platform we also have, you know, that that cross platform silo data content. I guess that's pretty similar to to what we have just discussed. But on top of that, we've got the branding and white labeling, making users kind of feel like they're at home within, within the tool that they're accessing. This kind of ties into the fact that we can reduce exposure functionality and that learning will go ahead now. And what what do I mean by that? Well, reduced to functionality doesn't sound great. And that's not what I mean. I don't mean to deliberately reduce functionality. If anything, we're increasing the amount of available functionality, But we're reducing the learning overhead for logging into that tool by having it being a more friendly experience. Now whenever we show clients that maybe don't use capitals, for instance, the Tableau environment. This is Tableau cloud in the bottom here, and people will be familiar with this as a very straightforward, project structure, but it can be a bit daunting for people that've never used Tableau before. And that's kind of not being, but because it's got huge amounts of functionality available within it, and this is just for the navigation, you've got external assets, you've got schedules, you've got groups, you've got recommendations, you've got collections, personal spaces, it just has grown and blown up over time based on the fact that lots of different organizations of different sizes and shapes use the same product. And some of these are pivotal to some organizations and completely unused by others. So you have this kind of expansion of a product like Tableau and we don't really need that, for for our, solution. We can be a bit more customized and we can develop things using the functionality that's inside Tableau Power BI hotspot, and expose that in a way that is gonna suit our organization best. It could be side nav, top nav, could be completely different project structure to the functional projects that we might have within our Tableau cloud, suite. We also want to integrate analysis within our business workflow. Really good book on this sort of concept is, actually my boss's book. Called, embedded analytics. That's right. So this is a bit by Donald Farmer and Jim Harper who's an inter worker, and you've been stopping us through this recently. And it's probably about an analytics because it really does it discusses the reasons that we, want to have, our analytics embedded in other products. And it's not about curator. It might be why you might want to embed a dashboard alongside your, your CRM product, for instance, might want to have it as an object within your CRM product, which we do internally as well. And it's really about making sure that the number of sort of touch points within your business workflow or whatever that workflow might be. It might be contacting somebody based on something else or maybe filling in some part of a system somewhere based on some information you can elsewhere. So whatever that workflow looks like is trying to minimize those sort of friction points and those sort of resistance areas that you might have that are taking up time and actually drawing you out of that kind of flow, that you might have. So again, Kuwait is great for this because you can you can embed multiple different things in there. You can embed right back forms like we saw previously with Southern Health, in terms of getting contact and, you know, you've got a request for board, well, instead of going out to Jira or something like that, why not just fill in this form that's right next to it? And you can link it on the bottom of the dashboard to say, won't see something else? Click here by you go. So all these sorts of little things can evolve to become, a much more, a much more tidy workflow and and and allow you to kind of curate how people use your your solution. We can also leverage bespoke functionality, so we talk about reducing functionality earlier. Conversely, I'm gonna talk about adding functionality. So we've got great people at Mohammed and the curated team that are building on top of the out the box functionality that Tableau might give us or the other supporting products might give us in order to build things like the report builder or, like, global filters and global parameters that can follow you around the the different dashboards that you put into your site. So these these are these are great, but they're not available out the box with Tableau. It's custom development that we've done over the top of that, we've bridging the back end, functionality that that Table has given us like for SDPI, JavaScript API, the SDK that they provide, and we've got people that are working on building functionality that is not supported by Tableau. So there's lots of cool stuff that we can we can talk in, talk about there. Before we jump into Mohammed's discussion, I want to just highlight and drop this in the chat. The page that we, that that I just showed on that last slide. So this is send this to everyone. There we go. This is NHS demo, dot tools dot interwork dot com. So this is, again, publicly available and you'll be logged in as demo user to begin with. You wouldn't have to remember any credentials here. Before I add this to your, ever expanding listed bookmarks that I mentioned earlier, you're more than welcome to. So this is just a demonstration, demonstrative NHS based branded, curator instance, where we've got dashboards, in, great demonstration there. We've got dashboards nested into the homepage where we could explore the number of GP pharmacy practices. In here, yep, we can look at the rest of the, you know, the rest of Yorkshire. And we can perform all the filtering and capabilities that Tableau gives us and explore lists of different, places that you might have. You might want to look at we've also got, the ability to navigate around different dashboards that are in here. For instance, cancel wavelengths, we can click on and that should take us out to our cancer wait time dashboard. Also, these are all available underneath the, that analysis menu here. As well as, lots of other stuff that we've got up here. If you want to explore again, some useful content that might not necessarily beat top of the dashboards, which is all stored in that analysis menu. Everything else will be user session videos, maybe predictive information based on a ai and ML from Snowflake, for instance, that we think would be useful for people. And also just worth mentioning that this is, not official NHS debt. Site and the data that we've used, we've kind of collaborated and pulled in from different public's, areas, but it's not an analytics towards a demonstration tool. So here, again, we've got report builder, where we can actually pop these things out and schedule them to export every Monday morning with the filter selection that we've used so we can build up PowerPoint reports based on the analytics content that we've got and even schedule. I'm sure that's familiar to most people. They fill a demonstration of it at some point. Give me a share. We've also got global filters. So if I want to filter this down to be, let's take back the Northeast as an ICB, we'll then be pushing that into our URL at the top here, and that gives us the flexibility to be able to then, go to a different dashboard that's in a completely different workbook. And, use and enforce the safety filter, so that functionally kind of follows us around that entire site. All this one renders, it's actually given us a disclaimer here that is kind of telling us that this is for demonstrative purposes. Now this is usually used as tutorial section. So if you've got a dashboard that might be a little bit more difficult to use, or maybe you want somebody to have to look through a little tutorial also that they're not scared, you can enrich this with animated gifts. You can put anything in here to, make sure people are aware of how the dashboard uses, is used, and then you can tell them if they want to never see it again. Click don't show again. So, familiar interactions that you would see from other websites. Right? Now I can see that even without using that filter, we've got the NHS bath, and and, Northeast Somerset, ICB has been chosen by default, even though it's nothing to do with the other content that we had in their biggest share, the same name as the field and the same metadata values of the system. Again, it don't work to take too much time to show you this, but, hopefully that's useful for people. And, again, have a have a quick look through, lots of different links to different sessions in the air. And sort of, nice, demonstrations that we've created, as part of that NHS demo. So no questions on that, and I can always come back to them later if, we want, then over to you Mohammed. Cool. Thanks Max. Cool. I think, yeah, you've done a good job already demonstrating some of those features. But I will just I'll just highlight some some features. Some of them are already existing, but we've updated them, you know, with some new features. And I think they would be useful to highlight. And then some of them, are new features. I won't take up too much time. How are we doing with time max? I know we have another another session. You're all good. I think we've got about five minutes. So Five. Okay. Cool. I'll I'll I'll quickly jump to this. Let me share my screen. Google Chrome. That should be the right one. It's Let me know if you can see my screen. I can. Yeah. Okay. Cool. Probably had this. Yeah. Okay. So first feature I wanted to walk through is, the feedback feature. So this, this is, basically a form that can be embedded on on dashboards, and and that allows your allows your customers to basically, just, you know, give you some feedback. You can then use if you like that data, on your dashboard as a data source, if you wish. So I'll really quickly show you how that's configured on got the zoom controls on the screen. So if we so, yeah, that uses our data manager feature. The data manager really briefly is basically a form manager, so where you've got data groups those are forms. And then where you've got data attributes, those are fields. So, you know, if you wanna do a contact us form, that kind of thing, that's the data manager. But not only that, you could then, as I mentioned, it gives you some information that allows you to then connect to that data as a data source so you can then take that to Tableau or to your other analytics platforms and use that as a data source really quickly that feedback feature, if you're already using curator, that is enabled on the settings, Tableau, Tableau server settings. You'll have the option there. It's pick which feedback form you want. So that's really quickly on that future. The second thing I wanted to go through was the ExplorerView. This, This this has been around for a while, but we've updated the kind of look and feel more recently. So you'll see that we've added the we've added, like, sort drop down here. But really, what what the I think what the Explorer review is is is useful for is, mainly for getting sort of that most of you. While it's good to have, like, a home page where you choose the content that you want your your customers to see, This is used more like so if I'm logged in as this user, for example, this would show me every dashboard that I have access to. And I can, like, filter by keywords. I could search. And the good thing as well is it's not limited to to just dashboards. Still you could combine your pages that you've created on Curator. You can combine files and that kind of thing. So it's a it's a really good way to kind of see all the content that that is available to you. Really quickly on the back end, That is on yeah. So there's nothing there, Mo. I use it all the time. So this is, this is a, this is actually all the products support it into works. And within the solutions team, we, we've got to kinda hone reasonable knowledge on all of these. So if you do type in, I know, tab or something in the search demo, and and just filter it out to anything that contains the keyword tab. And then it takes a tab. Yeah? Yeah. Just tab. So there should be things that are kind of a rent table. Right? Like, yeah, it it's so quick for me to be able to type something in here and learn a little bit more and especially with those filtered keywords at the top there. Again, none of these are actually dashboards. These are all just things that we need to be able to get quick access to. I might be on a call and somebody wants to talk about, I don't know, a Tableau server migration. I can just type in cloud migration in here, and it'll just pop up, and I can open that in the background and pretend that I know everything about it. It's really that quick, which is which is really useful. But anyway, sorry to throw up my No worries. No worries. I think that's, yeah, that's useful useful information. Okay. So really quickly, that, that explorer view, if you're not using it already, that is on the page builder. So you will see an explorer element. I won't go through all the settings, but, yeah, That's where you find it. And then the last thing I wanted to go through is a new feature. It's more of a of a performance improvement. That is our if I can find it on am I allowed into the back end? No. Okay. Yeah. So there is a new cash warming feature, which, essentially, allows you to select a group of users, that could be your Tableau group, or it could be a manually created group on curator. Sort of like your priority users of up to two hundred users. And what that will do is that will automatically warm the cash for them. In the morning or every hour on a schedule, which means when they come into curator, the initial load is much faster. So, really quickly if I still have this up, So usually on, like, a non cash I mean, this this website, I think, is already quite fast because there isn't much content in there. But, if you have a lot of, you know, content and it's checking that those permissions and so on, So you can see, like, the initial view, I've got about almost three seconds, almost four seconds. If we were to use that cash warming feature, I think I can kick that off manually really quickly. And let's do that. And then you will see on the queued processes that it will then warm up the cache for those users that you've selected. And I think it's done. So what that means is, like, the second time or when I go to access it, actually, let's say I'm coming in the morning and I access it, my cache has already been warmed up. So you can see that went down to one second. And, you know, in a bigger portal, the gain would be much bigger. And so I think that's something that's that's really useful. But I think, yeah, I think that's that's all me. So I'll head back to you, Mike, and we can continue. Amazing. Thanks, Mohammed. That's really good. And, yeah, that new cache broadband feature would be great. I mean, even if it is, just one second over to of people every day. If they're all accessing the platform, then that's a lot of time. You're doing that. Right? So Yeah. Yeah. Exactly. Yeah, thanks for having us. That was brilliant. Next up, we have, Peter. Peter Cunningham from the cabinet office. Either, Peter. Me hear me? Yeah. Can you hear me? Amazing. Yeah. I'll, again, I'll let you do your introductions here. We've got please slide here covering off who you are, but it'd be great if I could give you share a screen. And, and yeah, please feel free to tell everyone who you are and, share what you're gonna share. Yep. Let me just share the screen. It's just thinking about it. There we go. Share the screen that doesn't have government secrets on it. Perfect. There you go. We can see. Yeah. There we are. So hi, Bob. I'm Keith Cunningham. Head of Texas analysis and research for government people group, we're part of common office. Effectively, we sit under self-service human resources what our job is government people group is to effectively use digital solutions to drive decisions across the civil service. So being part of the carbon office, we sit absolutely centrally and it's our job just for everyone else in doing bed jobs, and it's basically impossible. We're gonna go through sort of a journey what we've done here through analytics. First, I think I'll outline the challenge we sort of had. When I first joined, my current goal, we found that, they needed centralized reporting. And as you're probably or familiar with in most organizations. Data sources are highly fragmented. Some people are using spreadsheets. Some people have got servers. Some people have got off the shelf, systems of software and all of this data somehow needs to come together, but usually there's manual processes in there. Even when you do pull it all together and you finally build the report you want, often you end up emailing it because if you try and share a dashboard, like certainly we deal with the home office administrator defense about really stringent, firewalls, the technology actually blocks it or you send them as file and their PCs don't allow wings it, you just get any sort of technology issues. So we need to overcome that barrier and have something that can truly sort of transcend that and share across government. To make a big impact as well, we also needed something that could bench press sensitive data in the background. So this means something that we can put sort of personal data from the background diversity data, and we could be confident in them access controls and then handling, and then also from a cyber security point that it's secured it's ever being attacked, we're happy. To be relevant as well, we also need this data to be shared in a timely manner. Some of our reports we were looking at they'd collect the day a monthly, take maybe eighteen days to crunch it, and then it would finally get to the decision maker at which point it's too late. So our aim was to try and get everything updated, you know, within a couple of if possible. It obviously depends on the candidate's health you're updating your data sources. And to be achievable, solution has to be easy to use. We have to scale across a lot of teams. It isn't just one data team that we're dealing with, and it needs to be affordable beads and that we can roll out which is in the break the bank. So we had to prove the case for change. And at this point, we were coming up and we just had this viral concept that we were gonna fix the problem We didn't really have a budget, so we needed something that could deploy rapidly. We needed something that could handle all these multiple data sources. We needed the data visualization to be on point. So I needed to also be able to do complex computation in the background. And again, we needed be accessible. It needed to be able to provide access to all them cross government users. We went through a procurement process, but we sort of looked at all the different vendors and everything and we landed on interworks and they also sort of subcontracting and giving us access to Tabo on the back end. So it was a combination of inter world's creator tableau that we found the best fit for us. Originally, the proof of concept, we just needed to prove to people that everything worked. So what we did is we have a analysis team of six people and we said here's Tableau server, interscope's running training for us. So we attended that skilled them on pretty quickly. They also then gave us an overview and, they came in and helped us, to configure our intralokes, create a system, and get it mixed up with the server as well. As part of the onboarding. We then deployed the dashboards using Tableau server. So because they were all trained, that was fairly similar process and we shared the dashboard. I think this whole end to end process was about three weeks in total. Everything moved pretty rapidly because it's a simple setup. At this point, there was nine data sources for four different dashboards and just twelve users because we just needed to prove that it was, it was going to work. And it works very helpful on this because when we explained as a proof of concept and we didn't have much money, they were able to be, a little bit flexible during our unbonding period and working with us and changing sort of the licensing just so we could get it from them to period to showcase it. It was so well received that we able to put together a business case and we rewarded, in the region of two million pound for funding to scale up the wider project. This isn't just into Works and Tableau, but this was then a full data lake solution that sits behind it and all the staff involved. So when it sounds a lot of money, rest assured this was an interworks licensing cost. This is all my staff. This is all my servers. It's all the development consultants, everything. And what we did is we reconfigured the whole thing to put the AWS sort of data warehouse in the background. Our Amazon web services actually has a load of data pipelines now it can connect to any digital system. It pulls it in and then we we put it into that one central database and that's accepted serviceable then by Tabo Server. If users want, they can still add in CSV files. They can still link to, Google Drive. They can still link twenty other data source they want. Primarily be tried to centralize it. This then seems to links into curator and then that handles it to our users. The primary reason that we use this setup is with Intuit's creator is it really simplifies that user journey. They just see something that's really simple. And we moved away from having one team for that data warehouse. To now, we have might solve eight zero nine analysis teams that are building on our platform. When we've got these sixty four data sources and forty seven dashboards, I won't actually know what most of them do and what we've built here is a framework that allows analytics to sort of be deployed generically across multiple teams and multiple business units, but based on one set of infrastructure, and we've currently got six hundred and one users we're still in the beta stage. We haven't even rolled out sort of, on mass just yet. So we'll just show you a little bit what our our sort of system looks like, a bit differently. So I I I mentioned the data sources. I quickly just jump into Tableau server so here's an example of one of our databases. There's loads of tables here and I can see that they've built up some queries where they're just using in this case SQL and building a load of tables together. And the real great thing about sort of Tableos and analytics tool is you can build all these sort of data models, and you can build this from the desktop or the server and pass it through, but then this all goes straight through to tablet desktop. And we've got quite a good, you can put filtering at the top like the user access controls. So go and find an example here. I'll first log out and just show one of the things that we've also done in the previous presentation. This is all we use AB group we've got our authentication embedded. We use Google. And again, curator supports that. So if I click on my government email here, curator passes it off to our other this allows us to authenticate ourselves and hand back in and that's authenticating everything with Creator and then dealing with all the legwork to the server in Tableau as well. I'm trying to think of a dashboard that has, department level filtering. So I'm going to search one up here. So I'm going to select latency tracker two. So what this one is is if you've heard of civil service drops, it does most of the civil service recruitment, this has a live feed to it. Now what popped up here is creator allows you to do like little tutorial pop screens for your user and you can close that. You can always come back to it here if you need to another feature they showed you actually is we also use that dashboard feedback button because if someone doesn't work or they want changes, we do get quite a few people coming into that. I'm just gonna type in the word officer now and what it does is it has the entire government recruitment database behind it. So I can see this is all the recruitment it thinks I work for DCMS and that's not a mistake, although I'm cabinet office staff because I own the platform. I've actually told it here, you can probably see there we are DCMS. It's in this case, I've typed myself as DCMS staff for testing, but it shows that that low level security is working. And they renamed themselves so it's picked up the two versions of the department, and we'll just show that this is a dashboard. I think they did a sankey chart for this one. Now this is bench pressing in the back millions and millions of records. So what this is is just so you're one of our recruitment campaigns and it's showing all the people through the stages. It's showing the diversity buckets of the bomb and it's pulling in Google Analytics. So it's pulling in two to three data sources here and just merging it together. And any vacancy holder can just type in a reference go and see a real time where they're their campaigns up to where the people are and if I like hover over to these six past people here, what it's going to do is it's gonna filter the diversity and the Google Analytics there. It's just sort of like a little self-service one there. But if I jump back to the main menu here, all of these dashboards here, as I say, they're owned by different teams and they can actually go in. We have a custom backend where they can choose who can access them. So if I was, some users only have two bus fields, some people only have ten, and we have like a custom backend here where depending on what technical projects are linked to them, all of this filters through to creator and it will only show them the content they're authorized for. And you'll notice ours looks quite plain, but that was off like another point that was done is We want to just keep everything simple when we've got so many users and so many teams. We need something that just works and is absolutely bulletproof. So for this, because we don't know what every team's needs is, it has one main job, and the first one's to be secure. And with creator, we look the fact that it's called one click upgrades, So if I were to go into the background now, there was a new update I think yesterday, I can upgrade this entire portal in about ten seconds, but also we do penetration testing every week where ethical hackers come in and attack the system and there's a lot of sort of advanced security features that we're using. So although it looks like quite a simple implementation of curator, we're actually taking advantage of a lot of back end features. As a business, we're also pivoting over to use power of the eye and the gift of this is Qator is able to show Tableau dashboards alongside power bi ones and the user would be able to drill in and see both of them also it has load balancing. So if we were to get many, many users like thousands, thousands, creator will help us distribute them users between our services as well. So I think that sort of, comes that up. Oh, I guess I should point it as well that with another thing with dashboards that you often get is because we're hosting this server, any user and government can actually come up to our platform. And they can self register if I log out. And when they self register here by this sign up, it will actually go and issue them, viewer permissions automatically. And within seconds, they can then start viewing dashboards if they've got commissions. So the whole flow of the user signing up to viewing content, everything is automated end to end. So we don't need to actually even manage the registration or the issuing the licenses. Because we're we're tabbed up server, that's all handled automatically for us. And the main reason for that is we get users in different departments we don't know when they're going to have access, and we didn't want to maintain the people of onboarding them. Data driven decision making. So we've got our radar centralized data warehouse here and we work within the digital professions, build all them connections out. We've kind of lent on the digital professional in government to to help bring these data sources together. We figured that was their problem and then create a sort of sits and support the analysis function the great thing with Tableau is it sports things like Tableau so they can run Python or they can use the advanced sort of Tableau logic in the background and then they've got full access to their own curator accounts to make that that content available and a lot of these pipelines we can set them up If you say we need this data feed in this dashboard, it's really only the time it takes to build the dashboard. We can then deploy it and all of that data normally it's refreshing every sixty minutes. So if the user sits there on watches and refreshes their screen, they'll see the updates almost in lifetime, and that's the difference of from before usually nine weeks was the average. Again, it's accessible. So we've done accessibility testing across all of this as well. So, with curator, we've had people go a bit to accessibility tools like jaws and things like that, and we're working all the time in the background with our dashboards as things you can do with TAVA just to make sure that actually accessible users can use the tools to go in as well. And we're starting to use slide's email alerts whereby when certain triggers or thresholds are passed in our data, it will email the relevant user and say you have to go look at your dashboard now. Some things have heard. So these are sort of core, capability to How am I doing for time? I've got a few minutes. So I've gone through three main components. We had AWS and I'm just calling out the features are three parts of our soft stack. We use Amazon web services because it allows us to do our own authentication flow. People can self register like I showed you it works with our single sign on. We can have them automated pipelines managed by that massive system and that means our data on average is updated every hour now. We've then had the Tableau server aspect which sits in the middle and this enables them to build the complex dashboards with ease. It's scalable. We can support thousands of users If our license gets capacity, we just ask them to work to run a license and, the more we scale, the better a deal, Intworks is able to handle this there in terms of pricing. We secure tested and proof handling your official sensitive data. So because we have like a walled garden, it's Tabos seven. We host it ourselves. We can put on those sensitive data there. Been tested and approved. And again, as we showed you, we have those data flows there. And at the back end, we had curator So that's the user friendly user experience. Everybody comes in. It's slightly gov uk themed. It's what I use is expect to see. They want to how to use it. There's nothing complex there. We've never had a single query on how to access a dashboard or how do I do this. It's basically iPhone Ece is the terminology we use. Seamless integration, like I said, it works with our AWS authentication perfectly. So we don't have to go and build a hold overhead of login accounts or user accounts just for it. It works with what we've got. It's advanced security features, so I won't go into the details there, but I'll pen test if I had a right go at it. I never got in again, the scalability because if we do want to bring in BabBI, it will scale sideways and sort of support the products and if we want to have thousands users, it will then have the load balancing to send it to a different service so it scales sort of vertically and horizontally. And unparalleled customer support when we don't have to do something, we go to orange work sort of you've got a Slack channel with them and an account manager and we'll find they'll say, actually, did you know we've written a user guide on this or actually we'll link you to your team or if we can't do it, we'll link to each other. They always know who to go to and it feels like a personal relationship with them where many of our big contracts it's one business to another so that the business support gets a bit stale and it's really great that we don't have that it it really feels personalized to us. And that's it. Thank you. Easy. No. That was that was fantastic. So much for that, Peter. That was, yeah, that was really, really interesting. And, I mean, there's a few things that I, I I pulled out. That one, like, to than something else on previous as well. But if anyone's got any questions, please feel free to throw them in the chat as we go, while I, ask mine. So, yeah, you you you were taken from, I think you said it was, nine weeks data refresh rate down to sixty minutes. Is that being something that was was that just, again, a facet of automation, or was it, is has the business changed in line with this? Yeah. Effectively it's because the technology's been there to enable everything before a lot of time that we spent on the data collection, but then there'd be the date's preparation in the middle, and then just trying to visualize it. Remember, we didn't have the online dashboard in, so we'd have to email it to people, email addresses would be wrong, and everything just used to go wrong at every stage. So now because the collection is being automated, the transformation is being automated, and then the data sharing might say people consult register. There's no barrier to entry. As long as the person who owns the data gives them access to it, everything's instantaneous. And I think it's basically just removing the manual overheads to the intern process. This is cheaper. Yeah. Absolutely. Just removing everything manual, including the the actual creation of the content itself. So you've just you're cookie cutting it every time or you're not even using new stuff. You're just feeding the old stuff with new data, just even more yeah, absolutely perfect. Oh, this is Tom and Claire talking as well. Thanks, Tom. What was, what was your timeline for, introducing this model? Yeah. It was a question per, for Peter from Thongy and Clark. So once we finish the proof of concept, the end to end thing for everything is we gave ourselves a year. But remember, we had to build out a data warehouse and pipelines and infrastructure on AWS from scratch. So I'd say probably eighty percent of all our effort was in the AWS domain and it was only the remaining twenty percent that needed to go towards Tableau and creator. Because they're preconfigured or or most of the work is done for us. For them, it's just configuration work, and there were teams on hand that almost help us or walk us through that. So it was a year, but most of that was business change, in government, we have what's called the GPS service standards, so we have to do all the user research and everything. So so long ago in our process to make sure we're building the right thing rather than just a thing for for a reason because we could. That makes sense. And actually, that was in line with my expert of how long those, those things would take. I mean, I think you already said something like three weeks or something to get your whole analytics infrastructure sorted, including training, platform, or tablet server, set up, curator, all that. I mean, that's that's an aggressive timeline, I would say, for all of those things. For, for curator, you know, a couple of weeks, one week, two weeks for enablement is we would be, it would be great, for example, server, in three weeks, Well done. That's very impressive. Yeah. We had the team run them in parallel, and we're a hybrid analysis digital team, so that that's why we're able to do that. It was it was pretty up to the wire, but it worked quite well. Lovely. When we ran everything, it went green and it ran. Amazing. Great. Yeah. Really interesting. Thanks again, Peter. That was fantastic. I appreciate where we're coming. Somewhat up to time, we've got about seven minutes left together. Again, please feel free to chuck any questions in the chat as we, as we as we wrap up here. But I wanted to just kind of glean some extra feedback on the on the call today, around, I wanted to feedback that any desired features that you might have had, just as we've got everybody together here, it'd be great kind of see, just gauge the feeling on, if you think anything is potentially, missing maybe from, from the product that you would love to see. Also when people use curator, what sort of things do you hear? We we've heard from, we've heard from Peter, Chris Mark, around their experiences and and how they've been developing things and and what they've found resonates with users. But yeah, what what have you found in your So please feel free to chuck any of the answers to these in the chat. I appreciate typing takes a while. Unfortunately, we can on mute lines, but, as well as what what feature results see as I've mentioned, is there anything that you think is is missing there? One thing that may phone particularly, I I hope that we get some interesting answers to this one is that is is there anything that you'd like to be able to embed into curator that you can at the moment or you don't It might be that you've tried and bailed. It might be that you know that it's impossible. But yeah, is is there anything that you're looking to embed? We've seen even today per BI roosting, Microsoft forms as well. I've actually just done a proof of concept with a customer, private sector where and we had that contact us form, and we actually just use use an iframe from their website to to put their contact us form from the website into curator. So that it feels again very seamless. And the advantage there is that you don't have a separate form, a separate answer is that feeds a separate mailbox. You've actually got the just a window exactly informed, which is, you know, something that's really simple. So yeah, is there anything that you want to be able to embed that you don't know if you can? And also, what do you generally use curator support for? So really honest, answers to this, or when do you when you're getting in touch with Mohammed and his team, are you helping, are are they helping you to test out new features and and new goodies that you found interesting? Are you asking, blah blah, I heard about this data manager, but I'm not really sure what's going on. I'm gonna get a call. Are you, finding understanding new features, are you asking more general questions if I'd like to do something like this, but I don't know what this is. Can can curate or help are you reporting bugs and problems that you found and issues with the curator instance, or are you fixing instance specific problems, unique to your infrastructure. And I've added this one at the end there because I know where the public sector can be a little bit more sort of nuanced in terms of the platforms that we're setting this up on, you know, lots more, on premise solutions that are required a lot more sort of firewall tweaking and active direct group understanding and that sort of fun stuff. And so is there something unique to your instance that you're finding you're spending a lot of time solving those, as as problems? So yeah, the chance very quiet, but if anyone does have any, any answers to the questions or any just general points as we wrap up in the last four minutes, we would love to hear them. As as we seriously again type into that chat box, I'm sure. Just a quick I was gonna say, sorry, Max, that they welcome to you're welcome to raise your hand. We'll put you off mute as well. Is that a few other go that way? I think if we want to take off mute, we have to make people panelists, which is the only issue. Maybe I think I've got a button that says a lot to talk So Alright. Cool. Okay. Well, please feel free to try that and let's do it. Yeah. Just raise your hand if you wanna answer in person or if you'd rather not type. One does. Everyone's everyone's finished for three minutes to work there, so I appreciate them asking a lot of people as they're just about to run out. Let's get a cup of tea. Yeah. As as we we don't wanna run over. So I will, layer off that your good people are typing away, then please feel free to to drop it in. Just a quick note at the end here, we've talked about lots of different facets of how Intuitworks can help, but, I've had a couple of conversations recently with a lot of people from public sector that didn't realize that we were, for instance, an AWS partner or, usually we have things like alteryx on here, and a lot of people use altrics. So if there's any other partnerships that you're looking to expand, from a technology point as you, then please get in touch, especially if they're aligned with, what you see on screen. If even if they're not, then please let us know, if you're looking to, expand your your platform in the data analytics frame and we can we can have a look and talk things through and help you out. Generally, again, thanks very much for your attention today. Thanks very much for all the guest speakers that we had today. Yeah, lots of digest as Harry has dropped in the chat. We'll be in touch with additional questions. Thanks very much, Harry. I'm messing with you even though we haven't been able to hear from you, but, thanks very much for dropping things in the chat. And your your interaction. And yeah, likewise to everyone else who he's spoken to and who's joined the call. Thanks from us, from everyone on the green hat into works and more. And hopefully everyone found that useful. And again, special thanks to everyone who's spoken, from, from an external point of view. Thanks very much. So yeah. Thanks everybody. Enjoy the rest of your day, and, we'll be in touch. Sure. Thanks everyone. Thanks everyone. Bye bye.