Juvare Exchange – The Future of Interagency Collaboration and Information Sharing

The video introduces Juvare Exchange, a cloud-based solution designed to improve incident management by connecting various government agencies and private organisations. It addresses the challenges of siloed operations and manual data sharing, which can lead to incomplete information. The platform allows users to create secure public or private networks for real-time collaboration, featuring a common operating picture and secure chat functions. A demo showcases the system’s capabilities, including real-time updates and tailored chat topics for different operational areas. Overall, Juvare Exchange aims to streamline communication and enhance decision-making during incidents.

Transcript

Alright. Let’s get started. So Juvare exchange.

So one of the the challenge of responding effectively to emergencies, as, you know, nearly everybody on the call is gonna know being, incident managers, whether they see administrators and and managing all sorts of different, incidents that have occurred is as the message grow in size and complexity, you know, there’s that impact on the responding agencies, and that kind of multiplies as there’s, the complexity isn’t increases. There’s more and more information coming in, and you’re trying to kinda sort through that information, and try and turn it into, you know, intelligence that you can use and, respond to.

One of the things that often occurs is agencies often work from separate emergency operation centers. So, you know, it creates that silo and limited access to that shared data. So each agency knows what they’re doing. Not always does every agency know what other agencies are doing. It often results in having to send liaison officers, two different operation centers, and then they’re jumping into their systems and then trying to connect that data together and feed that back into their own agency so they, you know, know what everybody’s doing and and everybody’s trying to work towards the same, you know, common goals to achieve what’s required in the incident.

And so collaboration across those agencies often relies on, you know, manual data sharing through, you know, often insecure channels, so email, text, certainly apps like WhatsApp or Teams or something like that, phone calls, and, you know, increases the risk that, you know, some of that data is incomplete. It’s been entered inaccurately.

It’s not timely. So, you know, how do you know how long, ago that information was actually added?

And, and then whether you act on it or not and then what that kind of, level of that information is on, you know, is it, validated, verified, that type of thing.

So that’s really where Juvare Exchange comes in. So, you know, it’s cloud based. It it’s, the collaborative incident management solution that connects, like, all your government agencies, departments, the private organizations, corporations. Basically, once you move to, where do you see Nexus, you’ll, automatically have access to JX Exchange, and then we can just configure that. And then you can start sharing data, and setting up your networks and things like that that we’ll go through very shortly. And so, basically, it lets you I mean, the operations teams, eliminate those organizational silos that I spoke about a minute ago. It’s, secure information sharing, has that scalable coordination across your local state and regional and national partners as required, and you can choose and select what boards inside of your system, what incidents, you choose to share with what, agencies and things like that.

And so, you know, is that secure data sharing so, you know, it’s an opt in model.

You can, both create networks, to invite agencies in. You can, open up public networks that anyone can jump in and you can, create secure ones, which I’ll I’ll show you shortly. So they’re completely locked down to just those selected agencies that you would like to, participate, and have access to whatever boards, the board data, and the incidents.

Those network partners can collaborate on the same Webex board, so they can share information backwards and forwards, live. So you’re seeing and responding to the same information that, you know, the HMA or the lead agency as they’re adding data into the system, everybody else is seeing that as well. So they can make those informed decisions, and it provides that common operating picture.

And, you know, it also adds in there, which you’ll see shortly, like a secure chat function. So, you know, one of those big things is not everybody wants to put information inside of an information or activity log or running sheet, whatever you would like to call it, but you need to sometimes communicate with other agencies that are part of the incident.

You might be wanting to ask them things or something like that. Like I said, that you don’t want necessarily date, time stamped inside of an information log. So the new exchange also, provides that chat functionality as well.

Okay. So let’s get straight into the demo, which is probably why you’re online and what you’re all looking forward to seeing.

So at the moment, I’ve got, two WebEOC systems that I’ve got open. So I’ve got some, WebEOC, APAC Nexus two, which I just created this homepage for with, Jake’s Exchange demo as a homepage.

And then, I’ve also got, Nexus Sandpick and, created a home page for that and just added in that on the home page. So when I’m jumping between the two solutions, you can see kind of which one I’m meeting. You can see that kind of information sharing and things like that.

When you or when we, connect you up to Exchange, you’ll for those that are using Nexus and aware of it, you’ll know that you get these icons on the side for your boards and, maps and things like that. You’ll note that, we now also have these little icons down here. So this JX networks is what, you can create through, exchange.

So as an example, there’s this one that’s already in here. It’s private network, mixes to invite only. If If I go to that network, I can see that there’s two members in there. So there’s, APAC mixes Jabari APAC two and then the sandpit that I just showed you a second ago. And I can see in here that we’ve got one shared board, which is the facility status board, and we’re pushing that through, one incident that we’ve shared at the moment.

That, board has been added in here, so we’ve got that facility status, then I’ve already got open so you can see, all that information there. And if I jump back into Nexus and go to the board area, which I’ve already got open, you can see exactly the same board sitting in the two different systems. So if I went, in here and, where this, training facilities and I went and made an edit to that and said that’s now operational, and everything in there is now all fully operational and save that. So that’s now, updated that and put green statuses across all the different columns. And then I go back to here. You can see at the moment as it’s just going to, update. So I’ll just kinda give it a bit of a push.

And then you see here it’s updated automatically so now it’s operational and it’s operational all the way across. Usually, it takes about a minute for that to come through, but rather than just sitting there, and not really saying anything, it’s just easy to do a quick refresh so that you can see that kind of change come through.

So how do we set all this up? So if I go back to the j net, networks, within here, you can see I can go and create a network. So networks can be anything that you like. That could be completely internal. So, you know, again, if I go back to the sandpit, you can see here there’s just an internal one. So you can set up an internal network for an incident.

You’re not needing to share any boards. You’re not really gonna share incidents. You don’t need to invite other members in, but you can go in there and, create a chat, and you can create, unlimited number of chats in there. So, you know, if you’re following the AIMS model or the ICCS plus, you could go in there and literally just create all your operations and and different positions and things like that so you could chat internally inside of, any sort. So let’s say we’ll go and create one for Jake’s demo, and this is gonna be, j x x change.

Demo.

If I could type.

Demo. Never.

I’m gonna hit next on that. So this is your organization. So, you have to at least select this because to make it operational, so this is gonna be API two, which is the the the environment that I’m in. And then I can hit next on it. Here is where, you would see all the other agencies that have a WebEOC solution that had been connected up to Exchange. So because, obviously, these are just internal mainly internal ones for Juvare, so I’ll just, select APAC sandpit, which is the one that I wanna connect to over here and hit next.

Then I can select what type of network is this gonna be. So, is it private? So I will only it will only send an invitation to the sandpit and nobody else will get to see this network at all. I can choose this to be a public one, so it can be seen and joined by anybody.

So it’s just open so agencies can jump in and out as they choose to. Or, again, I can make it public so people, or agencies can see it, but then they have to do a request, to join it. And then that would come to me as the network owner, and then I can choose whether I want to let them in or not. And then I can, finish that.

So, that’s now created this network here. So at the moment, you can see this, only one member, and it’s actually created it up here as well to see that that’s an own network. I haven’t joined any. I’m only the ones that I’ve actually created at the moment.

And within here, you can see these these, general, topic chats if I went in there and saw the chat, but what I can do is go and create other chat topics. So this is where I could go in and create operations and create that.

I could go in there and create, let’s say Intelligence.

Then I’ll create that.

And I might just create those two at the moment, and so that would then open up that operations chat for me to start, adding to, as needed. If I now go over to the Sandpick environment, and I look at networks and see I’ve got one pending, network. So that’s that one that I just created. I can go in and review that.

Here’s that, Juvare exchange demo. And so I can accept that invite, and then that will now add it into my join networks. And if I go to that network, which is down here and open that up, you can see I can see the intelligence and operations, chats there. And so I can actually go into that, and, you know, start creating, a chat in there between those, functional areas and things like that.

That they catch up. I think I’ve got, MBM doing some work on my line today, which should be typical.

Skeleton response. And hopefully, I’ve got, Isaac on as well that is hopefully gonna jump into the sandpit and, provide a response for me in a second.

And the good thing about this is, again, you’ve got all your different, widgets down here, so you can change all your tips and things like that. You can add, any files in here or anything that you want as well, so you can just be sharing, backwards and forwards, inside, you know, that particular incident and that, as required.

Okay. So why, I’ll just wait why, I’ll just move on, or should I say, why Isaac’s doing that. So some of the other things that we can do now is I can see, you know, who the members are as part of this chat group. So every single agency would be, listed in here. You can as well out on the outside here if I, you know, wanted to, have a look at it in, like, a card view, and then I can, go to that network again, open it up and and see what’s in there. I can browse different networks, so all the different networks that I would be, part of would be in here as well.

And at the moment, we don’t have any, you know, shared boards or shared instance. So we’ll, walk through those, now and, and see how, that’s kinda set up.

So first thing would be, let’s say we want to share, an incident inside of this JX exchange demo. So as you would do, normally, as a Webex administrator, I can go into the admin area, and I can go to the instance.

And then I can, go in here and create an incident. So let’s call this, Jake’s, demo incident.

Add a group to it so as you would do normally so that, I can actually see it. So I can go in here to the Jake’s collaborate position that I’ve previously created, and add that and then save it.

That’s now gonna add that incident up here, so I can go in and find the, the j x demo incident, which is there. Let that reload.

And then within here, I go to that.

Now you can see it’s added this, select the networks that you want to be able to access this particular incident. So, again, you can share this, incident with as many networks as you want. Like, so you could you could have be in the police and create network with health. You could do it with fire, different agencies.

Because inside of that network, you might be sharing different boards and things like that. So you can share, you know, different boards and different board views, and then you can share that same incident across or you can share multiple instance inside of a, network.

So let me, save that.

Hit save.

And then out here on the outside, I get back to the network and use the Jake’s, exchange demo.

Go to that. Let that, refresh.

And you see now that’s, added an incident in there. And so if we go in there, you can see now that, the JX demo instance being added, It’s owned by me. And if I go over to the sandpit and just let that update, you can see now the shared instance come across. So if I click on that, and it’s not showing me that instance sitting there.

I haven’t subscribed to it yet, so I can, simply go there and subscribe. So this is, you know, for those that may have seen fusion previously, it’s a much nicer process where I can go in here and map it to an incident that’s already in there. So I could actually then link it to an incident that we’ve already got running, or I can go and create, a new one and call it the same incident name as what I’m subscribing to because I haven’t actually started that. And then I can download any historical data.

So any boards that then, I’m gonna subscribe to, if they’ve already got data in there, within this incident, it’ll pull that data across as well, or I can just ignore it and start this incident from, fresh with as a blank incident if I if I wish to do so.

And then I subscribe that, lets me know that I can now go to the admin area where the instance are to assign that to a group. So I can hit done on that, and then same thing again. I’ll just go into the admin area, and I would go to the incidents, and I can see that instance being added. So also I would do then is go to the, group, find that chat to collaborate group, go to the incident, and then add that incident in there. So JX demo incident at that.

Save.

And then I can jump out of the exercise test and go into that JX demo incident. And so now, this, and, Nexus two are now completely linked, via that particular incident.

And, again, you can go, like I mentioned before, I could go in here and add, you know, as many incidents in this, that I like. So if you think about this as sitting at a higher level, you could have three or four incidents running simultaneously.

And because you’re adding, to this network, it would allow you know, if I was pushing those from the nexus environment, it would allow anyone in Sandpick to then just start allocating those incidents to different incident management teams or via the one network, if you needed to do so.

Alright. So then we want to, you know, share, some boards. So, again, I’ll go back to, the nexus view, go into my admin area, go to the, workflows with boards, And then here, I want to go and, share, the sheltered’s board. So I’m gonna grab the sheltered board, and then down here, you can see there’s this jay to publish.

So I can just hit the publish. And then here again, I just go, what networks do I wanna share this board? I don’t wanna send it to Nexus two. I just wanna send it to the j x exchange demo, because I know that’s got Sandvik in there.

So I can, save that. And then down here, what it’s gonna do is show you all the different views that, contain inside of that board. So this is where as the agency publishing the board, you can select which one of these you or or how many of these you would like to share with that particular agency.

So you don’t have to give, another agency all the views. So if you’ve created a board or you might create a board as an example that has a list view that only has five out of the ten fields that you use on your view, and you could publish that across and they would subscribe to it. So they only see the information, at that point in time that they’re allowed to see on that particular board.

Later on in a in a future release, of JX will be data mapping. So you just actually choose what data fields inside the board you wish to, share. But at the moment, you can select what views you want to to send across. So at the moment, I’m just gonna select all of them, and I’m gonna share that.

And so if we go back outside again, and again let that, play catch up, you see now that’s, changed to shared boards and it’s showing me that, the shareholders board, shared shared by me, and the whole board is being shared across. If I wanted to at any point in time, I can stop sharing. So I can, you know, if I choose that I don’t wanna now share share that board, if I hit that stop sharing, it would actually remove it from, the sandpit environment. So over here, what we’re gonna do is go into the, shared boards and just let that again play catch up.

You see here it’s added that available board, telling me that whole board’s come across, and I have this ability now to, just subscribe to it. So I can just go in there, hit subscribe.

And, again, similar to, the instant data, do I wanna pull all the data that’s already in that board with it, or do I wanna start it as, a a clean board and don’t, bring any of that with me? So, yes, I do because it’s a shareholders board, so I wanna see what those shoulders are so I can subscribe to that. Same thing again. It tells me it’s now available in groups, for me to go and allocate that to whatever groups and positions I want to have access to that board, so I can close that. And then same thing again, I’ll go into that, group area.

I’d select the group that I want to give access to that board, go to the board, and then if I look into the board area, there’s now that shelter shelters board.

So I can assign that, any board permission tags that I want to, add in there as well.

Let that load.

Save that.

And then if I go back to our normal board view, it’s now added the shelters, shelters. So if I went to the board over here in, Nexus, Okay. No need to funnel the Internet today.

Get Isaac to have a look why that board’s not loading in the background. Hopefully, over here, it is loading. So bang. That’s what I’m supposed to see in the actual area that I just sent and published the board. So, you know, I’ve now got that whole, board with all the data in there has now been added. So if I make an update to any of these, that will would come through here, if I didn’t have the spinning wheel of death for some reason.

Let me just go and just make sure that, we’ll assign that and unassign that again. So let’s go to groups and see if we can fix why that’s doing that. I’m just doing it right. Boards.

Remove.

Save.

Let’s go and reload it.

Okay.

So, you can see now this is in APAC. Nexus, got all those, different shelters there, and I’ve got exactly the same board sitting now in, sandpit.

You’ll know, of interest like, you know, this is pointing to an Australia map inside that board. I push that board across, but sitting over here in the map that it came from is a is a different map view. So they, you know, in Sandpip, there wouldn’t be a map called Australia. So, you know, your admins would just go in there, put the create in Australia map.

You know? And that’d be a great thing that you could use the chat for. Hey. We just pulled this shelter’s board across.

What’s the map called? It’s called Australia. Just go and create one. Create a map called Australia, and it would actually load the map exactly the same as well.

But if I go into this, Alexandra, Hills Community Shelter, and we’ll go in there and edit it, And we’ll say that, this is now closed.

Occupancy is zero.

So let’s change that. Go and save it. So now it’s updated, the status on closed and availability, is it, full with, zero percent in there. I go, back over to, Nexus, and I’ll just quickly, update it.

And you’d see that status changed, and it’s changed all those figures. So and, you know, that’s, as you can see, bidirectional. So this was the board that I published from this environment, but in the environment where you subscribe to it, you know, any changes in there will update into this view. Any updates on this view will, update back, as well.

Same thing again. If you’ve got, you know, if you didn’t want to particularly send, a board across that’s already got information in it. So, you know, if I quickly, create one here and go, metro and jurisdiction, such as Perth, road name, freeway, top of road, state.

I’ll just put that I found the map. Save that.

And I said close medium, and that would do.

So that’s added that record in there. So, at the moment over here, you know, in the board’s area, there is no, road closed board. So I can again go in here, grab that particular board, so it goes to workflow, find the road closures board, and go down here and then publish it. So, again, the network is to that JX Exchange demo. Save that.

What views do I want? So I just wanna give them the list view. I’m not gonna give them read, write only because I want them to be able to, add to this board as well. Share that, head back out, go to the network, and just make sure that that’s, loaded.

So if I go in there, you can now see the road closures. Whole board is being shared. If If I go back over to, the sandpit environment, go to that same network, and you see that’s already loaded. So I’ve got ahead of me this time of skip, and there’s that road closures board ready for me to subscribe.

Again, I can download historicals, data, so I don’t want to. I’m not interested in that banana, freeway incident at the moment, so I’ll subscribe to that. Again, it tells me I can go to my, panels. So I’ll go in there, go to my, groups, go to Jake’s Collaborate, go to boards, and I’m gonna go and add that road closure board.

It’s already loaded that list because I only gave that one list, so that list read only didn’t load because I didn’t allow that to come through. So it’s already, determining what, views I can provide and then I can go in there, grab whatever board permissions are relevant to that particular, view, Save that. That’s now added that in there. I can then, save that to that group, go back, and, that road closures board has now loaded, and you can see, like, there’s no data in there at all. So now if I went, back over to, the Nexus and, I went and created another incident.

Let’s say it’s in the metro again. Let’s put Perth. We’ll put road name. We’ll put another freeway. Why not?

Go to my Matthew. This time, I’ll zoom in, and we’ll say, that we’ve got, you know, I don’t know, some type of incident that’s going all the way down here.

Save. And it’s closed.

Alright.

That’s all we’ll put in for now.

Time required. Yes. Save that. So it’s added that second, incident. So we’ve got two incidents on this particular board at the moment.

And then if I go across here and hopefully get that to, update, You can see now it’s at that one that I just added, and same thing again. I can go, because it’s saying big map, I can now go and see that, on the map as well and zoom in, or I could actually hit the map zoom and zoom straight into that location and see where that particular incident ends as well. And then if I, you know, went and updated this as an example, and we’re in there and say, yeah, time time closed. It’s from there to, you know, here or whatever. Cross street is from, you know, highway to road.

That’ll do.

And there’s no there’s no detail. You got nothing. You’re gonna have to stay in traffic. And save that. So that’s added that, update to it.

And so over here, again, you know, just waiting for it to play catch up.

You can see now it’s updated that particular record, as well.

I’d say that at any given time, you know, depending on if you’re subscribed or it’s being published, I can go to my network.

I can go to this, JX Exchange network.

I can see what shared boards are in there. I can see the shared incident. And at any given time, I can go there and say and I could stop, sharing with this. If I, stop sharing and say, no. You’re not allowed to have the road closures board anymore, so I’ll get rid of that. It now removes it from that view.

Over here in the, environment, I go to that, you can see shared boards has dropped down to one, and it’s actually removed the road closures board. So, no more data is gonna come through onto that board through that particular incident. You can do that with any incident. You can do it both ways, I.

E. From, Nexus, I can stop that as a as a shared board, or over here, you can unsubscribe to a board. You can turn around and say, yeah. I don’t really want any more information.

Thank you very much. I’ve had enough of that. So, you can just unsubscribe and same thing again with incidents. I can either, unsubscribe from an incident or, again, over here in, the environment that published it, I can go in here and stop sharing and so it’ll unlink that incident as well.

And I think from memory, if I go in here, let that load.

So yeah. So Isaac was able to jump in there, and so he, you know, sent me, a response back. So, you know, between the two different systems, you can have, you know, any of your functional teams sending, information backwards and forwards. Or as I mentioned at the beginning, you can, also do that just internally. You don’t need you can create a network that’s just for an incident for people to, or your people to chat on inside of that incident, and this is all, you know, available on the mobile app as well. So, yeah, extremely powerful.

That’s about it from me.

I don’t know if we’ve got any questions at all. I can’t see any questions on there.

If there’s no questions, I think most of you know me. By all means, feel free to reach out. Happy to answer any questions. Oh, we do have a question. Here we go. Alright.

Let me let’s see.

I can find you. Hang on, Kath. Let’s see if I can unmute you. Yeah.

See if that works. Can you talk?

Yes. Hi, Phil.

Can you hear me? Yes. I can.

Yep. Great. Just wondering, thanks very much for the presentation. It was really good. We haven’t seen much in access, so it was very useful. But can you give a quick, roundup of the selling points for, Jake’s Exchange chat versus Teams chat. I mean, I’ve got a few, obviously, in my head, but, can you just quickly run through those?

Oh, I think the obvious one is going to be that it’s sitting inside of your WebEAC system as your incident management system, and it’s accessible and reportable. So, you know, rather than, and I’ve certainly heard it from some agencies that at the end of an incident, there was an inquiry, and then they found out they were using either, like, WhatsApp or Teams. And then somebody’s had to spend, like, two months crawling through that to try and pull out all the information to put it into report to ensure that there wasn’t information in there that was extremely relevant to the incident and somebody should have responded to that people put it inside of a chat instead of, you know, realistically, it probably should have been inside of a board.

But at least if it’s in the chat inside of, Exchange, it’s sitting there in the incident and people are monitoring it because they’re using the system to to respond to the the incident. And that it’s also probably that second point as well. Just in case somebody does put something on there like, I don’t know, I’m an executive person and I just go and add a throwaway comment in a chat of, hey. I made a decision.

We’re gonna do x y zed, but nobody sees it. You know? Again, at least in here, it’s sitting inside of your chat, and, you know, you can access it and see inside of the incident.

Yeah. I I certainly had the security and the containment within the one system as, you know, the top of my list as well. I’m wondering how it would work, and this might be a nexus thing that I just don’t understand yet. But, if say at the end of a shift and the chats are assigned to groups as part of that network thing, does that mean that it’s very easy for the next person that comes in, says their ops officer, just to slip into that chat via their, WebEOC position?

Yeah. So you because you’re setting these up inside of that chat and then you’re giving that, you’re allocating that network to, yeah, whatever kind of groups you want, you can then lock that down so that everybody that’s in that intel position would see that kind of chat. And so, yeah, if I jumped out and walked away and then you came in and took over the afternoon shift, then you can just jump in there and start adding to that chat as well.

Yeah. Okay. Great. Thanks a lot, Phil.

Pleasure.

Yeah. Okay. So as I was saying, feel free to send me an email. More than happy.

If you want any further information, if you want another, you know, specific demo to an internal group, again, more than happy to, facilitate that, and, you know, we can start getting, you know, agencies connected up, on exchange. So it’s there. It’s part of your Nexis solution.

Very simple then to connect you up, and then, again, you can start building, or setting up whatever, networks you like, both internal and external as required.

So, yeah, if there’s no other questions, thank you very much for your time and attention, and look forward to catching up with you soon.

Request a Demo of WebEOC

Find out how to leverage the world’s most widely-used, battle-tested critical incident management technology to prepare for and respond to emergencies.

REQUEST A DEMO