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

Welcome to the on demand recording of our webinar, Chicago Cubs reenvision incident management. Originally presented on July sixteenth, this session takes you behind the scenes at Wrigley Field to explore how one of Major League Baseball’s most iconic franchises modernized its approach to safety, coordination, and event operations. You’ll hear directly from key stakeholders who led the transformation, sharing how the Cubs replaced legacy processes with a unified digital platform, improved real time decision making, and elevated the fan and staff experience. Through the power of Juvare’s WebEOC Nexus, the team implemented a scalable incident management system tailored for live events, emergencies, and everything in between. Whether you’re in stadium operations, public safety, emergency management, or enterprise security, this conversation offers real world insights you can apply across your own organization.

With that, I’m pleased to introduce today’s special guest and speaker, Nicholas Denhof, who serves as the Assistant Director of Physical Security for the Chicago Cubs. In this role, Nicholas plays a critical part in ensuring the safety and integrity of one of Major League Baseball’s most iconic teams and venues. With a strong background in physical security operations, crisis preparedness, and large scale event management, he brings deep expertise in securing high profile environments.

Nicholas has known for his strategic approach to risk mitigation, his ability to lead cross functional teams under pressure, and his commitment to fostering safe, welcoming experiences for fans, staff, and players alike. Whether it’s managing complex, the game day logistics at Wrigley Field are advancing innovative security protocols behind the scenes, Nicholas consistently demonstrates leadership grounded in vigilance, professionalism, and collaboration. Please join me in welcoming Nick.

Nick, it’s over to you. I’ll stop sharing my screen.

Awesome. Thanks, Ian. I hope to live up to that really nice bio that you shared there.

I should have had a drum roll. A drum roll.

Welcome, everyone. I appreciate this time and everybody gathering here today.

Today, we’re going to talk a lot about, what we see here at Wrigley Field, and what we’ve gone through, with our transition into WebEOC. I know that we have participants, here from all over the world. So a little bit about Chicago Cubs and Wrigley Field. The Wrigley Field is, the second oldest, Major League Baseball stadium in, the United States, second only to Fenway in Boston. So it’s an old facility, a very old facility opened in nineteen fourteen, and has had some major renovations through the years, but the bones of it, as we like to say, are very much true to when it was created.

We’ve used a couple incident management platforms through the years here. I’ve been with the, the Cubs. This is my third season, and we transitioned to WebEOC in two thousand and twenty four, starting on January first of twenty four. Over the last year, we built a, what we think, is an awesome model that is catered to the events industry, baseball and events industry, as well as is customized to our needs and what we need to here to do, at Wrigley Field.

So on this next screen, you’ll see some of the things that we, that we host here. So, in addition to eighty one baseball games a year, we have concerts. We are a pretty large concert venue with forty thousand people in attendance, And we’ve had some really awesome events over the last even five to ten years, including college football games, college hockey games, the NHL’s Winter Classic, which is a one day, NHL, National Hockey League game on the field in an open, open air stadium, which was huge. It was about a two month build, here, and it went off without a hitch.

So here, we use WebEOC with multiple departments, third party organizations, and we’ll get through that in a second.

And today, we’ll talk a lot about how, with the customization integration, and the build that we’ve done in partnership with Juvare, we’re streamlining and maximizing efficiency of my dispatchers. So first question that we always get asked at the show hub Cubs is why? Why we switched to WebEOC? These are the three main reasons.

So customization and configuration, expansion, and cost. One of the things that we were, struggling here with is that we are more than a baseball stadium. We are transitioning into an event space, and how we can capture all of our, activity on, the campus was something that we were struggling to do so and just a mold that was built for baseball. We couldn’t change what we were doing due to the data degradation.

And then the effort to continually grow that dataset, and everything that is happening here on campus and documenting that and managing our incidents, we landed on WebEOC. Partnering with Ian and a number of members of their team, we found that, through that partnership, we were able to, customize every field, every incident, every specific need that we needed to, to both manage our events as well as document our events. Additionally, I’ve never heard the word no from Juvare. So, I don’t mean to say that coy, but, every time we’ve come with an idea to expand, to evolve, to, have a new idea for efficiency or, or something that just makes sense, it’s all hands on deck of making it make sense.

And so, with that attitude to customer service, we were able to, and we’ll talk about this a little bit more, come up with systemic problems that we had had for years that just were time, time that continually bought or used time for my staff or staff in the ballpark or staff on campus.

And to simplify, streamline, and automate those type of processes saved countless hours of time, and we’ll talk about in a bit. And finally, cost. So cost is a big one. It’s a driving factor of the private industry and public industry in that essence.

And so we found that the solution that Juvare provides through WebEOC was cost effective. We were getting exactly what we needed. We were able to customize it to what we wanted, while not breaking the bank. And so, that can’t go without being said that cost was a large factor in doing so and get delivering exactly what we needed for what we thought it was worth.

The last thing I will say is, we chose a big portion of this project with the, idea that in the future, we will be able to and we’ll talk about Nexus. But the familiarity with public and state agencies with WebEOC, a lot of them use Juvare’s products, gives us a leg up in the, future for the expansion that if we were to integrate with other facilities, whether it be in sports teams, whether it be governmental, the option is there. And so by aligning with that poll that platform as well as the ability to continue to develop it, we saw that as a win in the future.

So the Cubs model, and we will I’ll start sharing my screen in a slide or two, but this is the basic overview of how we operate here in Wrigley Field. So we have three facilities. One is Wrigley Field in Chicago. The second is our spring training facility, which is in Mesa, Arizona.

And then we have our training facility in the Dominican Republic. So, we separate things between daily operations, which are a twenty four seven, three sixty five operation in our events. So you think baseball games, you think concert, you think spring training games. And then the Dominican is really more of a training facility that is just daily operation.

We kind of mentioned on a lot of things, but we have programs here. We like to say three sixty five days a year, whether it’s baseball, football, hockey. We’ve hosted a soccer game last year or maybe two years ago, concerts. We have golf, in the ballpark in Winterland.

So, there’s no there’s truly no event that is too outlandish or too bold to think here at Wrigley Field, and WebEOC has given us the ability to, customize every event to document it the way that we see fit as well as the way that we, from a legal perspective, from a safety perspective, emergency management perspective, everything that we need to capture that happens on our grounds, on our property, both mundane and escalated is documented in the same processes, in in the same platform.

So who uses it? So here at in Chicago, we have a joint operation center. So the power users are going to be our full time dispatchers. So, they’re I shouldn’t say full time. That’s their full time role, but they are part time employees that are in our joint operation center.

They’re it is staffed twenty four seven, three sixty five. And then on event days, we bring in four additional staff members, to manage both WebEOC as well as radio traffic. So think of an event. Most everything comes in either radio or phone call, and it’s anything from a medical to a fight to a not that those ever happen, to a ejection to a spilled garbage can to being on a toilet paper.

Anything and everything gets notified in through our joint operation center, and every single thing gets documented in WebEOC. And we’ll talk we’ll talk and show that in a minute. Some of the power users, and I think some of the, the benefits of going to WebEOC are the compatibility as well as the user friendliness for all departments. Again, a lot of I think in the Again, a lot of I think in the in the emergency management, world is buy in.

You have your power users, and I think there’s always the room for expansion, but there’s always going to be a hesitancy to buy in to make sure that everyone’s using the same platform. We push that hard here. Our operations, whether that’s our, logistics, our cleaning, our engineers, our security teams are heavy in our environmental health and safety are heavy in this. But the user friendliness of allowing our seasonal staff, our front of line staff, as well as our third party contractors, whether that’s medical, whether that is our emergency medical services teams, all have access to document in one single silo. It’s not that we need to push the documentation or the reports to a certain person to upload. Everyone has access through a mobile application. Everyone has partitioned access, and we’ll talk about that in a minute, to their specific fields, enable to give the, them access to the platform.

And that’s what our commercial model suits really well, Nicholas, as the if it you can have a huge pool of people in WebEOC, you know, trained, familiar how to use it. And then you have your, you know, based on our commercial model, they’re active monthly users. So as long you don’t go above that number, gives you that massive scope.

Yeah. Absolutely. And for a normal day at Wrigley Field on a non game day, we’re looking at anywhere between fifty to a hundred. On a game day, we’re going to go upwards of two hundred. And that just can kind of gives you the and, again, on the back end of what we see that I don’t think gets, spoken enough is an audit log. Right? So we can see and we can go back and review who is updating what, when, and where.

And, it it’s helpful in the long term.

Boards are really important thing, when it comes to WebEOC, and we’ll go through the layout of our boards here in a second. But, our boards are documented in incidents, requests, activities. So anything you think of an incident is going to be a medical incident. That is where the summary of the incident goes.

Our request is any activity or any, call for service into our joint operation center. So that’s a broken seat. That is a trash can that needs to be emptied. That is water spill.

Activities are going to be what is happening. That is documenting the work that’s being done, whether it’s our environmental health and see safety teams investigations, whether that’s a medical investigation into what happened, and then the notepad is simply for notes.

Data analysis was something that we partnered with Juvare to develop because data is really important to us. We like to look at root causes here, and we like to see what the data stacks up to tell us in our instance. Does it affect our staffing models? Does it affect our response times? Does it affect, where we are seeing a hot bed of issues in the ballpark?

Data analysis and the ability to export the data from WebEOC in a customizable report, that we can provide to any of our internal stakeholders that are looking for specifics, as well as, the broader sense of whether we’re looking at the season, whether we’re looking at the year.

You know, I’m looking at yeah. There you go.

Keeping going, we’re our event creator, our summary report, something that is really important here is for our executives as well as our leadership team, our security team to see a basic overview of what happened. Right? Our events, when we think of incidents, are in a day. Right? One baseball game is going to be a day. One concert is going to be a day. It’s not a longer term, incident if we were going to look at a response to, let’s say, a natural disaster.

In that wrap up of that, we are able to look at all of the activity that happened, whether it’s instance request activities, notes, drones, we’ll get to in a second, all of them that happened within a certain time period, and we’re able to roll that into a preformatted report that we can send on a moment’s notice. And what we have found is things happen. Times change.

Nothing goes according to script. So we’re we have the ability to send that report as needed and when we want to as opposed to an automatic send, which is a huge win for us, because in baseball, we have rain delays. We have, you know, a lot of different things that go into effect when it comes to our event going off on a set time frame, and those things change. And so the ability to send those reports when we are officially done and closing out an incident or event is huge for us.

Finally is checklist. It’s something that we leverage here, because, again, we’re using this with our front of house staff. We’re using this with our, our seasonal staff, and they have the ability to look through their application, their app, and see exactly what they need to do, exactly when they need to do it by, mark when it’s done, which is time stamp, and then, like we see here, show in a dashboard what has been completed and what needs to be completed, and everything can be managed at a higher level to show that we are game day or concert day ready.

Before we go to the next slide, Nick, there’s a question in from Jack Gibson.

Your primary leverage in WebEOC for managing planned events and operations, I expect most of us in this call will be reacting to unplanned emergencies and natural disasters. Do you have workflows in place that would help wriggly in the case of a large scale emergency, and go Cubs go?

Yeah. That’s a great question, Jack. So, we have set our foundation into unplanned events. So our daily operation has the workflows built in to accommodate for any type of, one off or unexpected, whether it’s a large scale or minor incident.

We have the workflows that in an escalation tree as well as our steps in place for any type of elevated incident. And the for the most part, they are mirrored for an event day versus a daily operation. There are definitely nuances based on who’s on-site and what available resources we have, but our foundation is always going to be daily operations. Right?

Eighty one baseball games and, let’s say, a hundred and ten events, major forty thousand people events is still leaving upwards of two hundred days where we have staff on-site. We have a historic ballpark that we have to safeguard.

And so that foundation is laid in that daily operation so that my staff, the seventy or so campus security that are on-site at twenty four seven, three sixty five, know exactly how to manage that staff, whether it’s two in the morning, two in the afternoon, on an event day, non event day.

Very good. Next question before we move on. Square MLB specific requirements sorry. Where MLB specific requirements are driver here to invest in a unified platform? My understanding is that MLB was hesitant toward an all star game directly until upgrades and improvements were made to security, and an all star game would be more than pay for it.

Yeah. So, Major League Baseball has their own set of standards. And by no means did Major League Baseball drive here a lot of our choice in doing so. A lot of teams use a lot of different platforms. What we were doing here was trying to leverage the best platform for our needs. And so doing so, we have to meet the set standards that Major League Baseball provides as it relates to, incident management and record keeping. But, again, in a in a facility like this, in an environment like this, we are looking for not just to meet requirements, but to exceed those requirements.

The last thing here I’ll touch on before I start to share my screen is notifications. Something that we found in other platforms that we, researched and looked at were the type of notifications. A good amount of it was staff driven, and we were finding one of our gaps was an instantaneous report would go out or notification would go out. It would be blank.

And so, with the customization of WebEOC, we were able to drive how those notifications are driven. We’ve got, incidents where we don’t need the notification right away. If it’s a low stake incident or, something that happens that we just need to document, I still want to know, but I want that report to be completed before it’s notified to me. If it’s something that’s happening in the neighborhood that is, for instance, something that could be very dangerous, I want the automatic notification push notification on the spot that I get a phone call, a text, and an email that says, this is happening.

Call our joint operation center. The sky’s the limit, when it comes to these notifications. We have things that where we my personal is what I can see every time a incident is updated. So if we’re getting more and more witness statements, I’m getting notify notified via email.

I’ve got ones that go directly if there’s a medical incident, goes directly to our human resources and our legal department.

And continual is kind of what I touched on is I can see when it’s open, when it’s updated or closed. I can see if there’s something that I want to know that just when it is complete completed, what the full summary is. And this was different than what we had found. Right?

They had not other platforms had not nailed down notification component, and the targeted notification where only people that need to see certain things see them, which was big for us. This is what WebEOC looks like from the Chicago Cubs side. And I think one of the biggest wins for us was, in something that I get feedback on often, is the ability to have multiple tabs. A lot of different systems have segments, where you’re either in a specific tab or specific window.

You either have to save, exit out, and transition. Here, you can see all of our different tabs. And like I mentioned earlier, we use a daily operation, to document as well as events. So you’ll see here, all of our different tabs, our drone integration, our checklist.

But, again, most people almost all people, when they log in to the system, will see the same home page, which can be customized whether it’s a dashboard, whether it’s a message on an event day. We will post every applicable staffing update, staffing numbers, anything that’s happening that day. And that pushed to all WebEOC users, and it’s super helpful when referencing throughout a game. In the right hand corner, you’ll see these are just all of our positions.

And by that, I mean, that utilize this on a on a ongoing basis from parking to our Mesa team, health and safety, guest services, facilities, so on and so forth. And each one of these is customized to show what they are allowed to be seen. We have to abide by certain laws, regulations as it relates to medical information, and this is how we restrict access to that information is through positions, to give people access to only what they are needing to see. From here, we have our incidents or events that we call them, which will be all of our baseball games.

We keep these active so that we can view them throughout the season, but this can be cleaned up postseason, so that you’re only seeing upcoming events. We have our daily operations for all of our three facilities, our analytics where we can pull all of our reporting, and then all of our games that we’ve had or concerts for this year. One of the big things that I’ve alluded to is drone detection. One of our first things that we did with Juvare was had an open conversation about their integration ability with, other platforms and API.

Here at Wrigley, we are really trying to drive, a single silo solution, minimize the amount of tabs and programs that we’re using in drive through one common use, and that’s going to be WebEOC for us. With drones in the US, we have a temporary flight restriction, so there cannot be any drones flown within three nautical miles of the ballpark on a game day, one hour prior to one hour post game. And what we are finding because we’re in such an urban dense neighborhood, we were having drones that we were we couldn’t keep up with the amount of drones that we’re having, whether it’s on a game day or not a game day.

And so by automating our drone detection, every drone that happens, is automatically categorized, and we are able to choose what event it will be triggered to. So you can see these are games that we’ve had recently and how many drones within that radius we have. And if we go to one, it pulls everything. Everything from this was a game day, and we could see the map that this drone flew around Wrigley Field, a clear violation.

Chicago Police Department is dispatched to make contact with that drone operator. Most people don’t know the rules, of what it our a temporary flight restriction is. But drones are an ever present, threat around the world, as we see. And so by doing so, we get notified instantaneously when a drone is there.

It will tell us what zone it is in to show the proximity to the ballpark. It pulls all of the data that is readily available, whether it’s a DGI drone or a remote ID, which identifies the drone of any drone, I believe, post two thousand and three, that is not DGI, the altitude speed, and when it is. And this was a huge win for us, and this is able for us to, compile all of the data for drones that we see that can negatively impact a game day. If one were to, be over the ballpark, whether it’s in the batter’s eye, whether it’s it lands in the stadium, there are videos out there.

This at Major League Baseball season started with a drone incident this year. And so by doing this, it has saved my team countless hours of not reformulate formulating, dragging, and dropping data from a separate system and having it automated here.

Another requirement that Major League Baseball has is the ability to text. So, we have to, ingest, any it’s like a if you see something, say something line. And so in doing so, we have leveraged Twilio to be able to absorb those texts, that if somebody in the ballpark sees something, they can text my dispatchers, and we will dispatch services to them.

Beyond that, again, getting back to the single silo, we are able to push those conversations into WebEOC. So you’ll see this is a communication request that comes in. These are all the types of requests that came in on a game day. And what we have here is basically that there this seat was missing a bolt.

Somebody texted us that there was an issue with that seat. We notified our engineering team. We put in a work order, and then that conversation is logged as a comment. So we can see this is the text from the number that happened.

We responded. We’ll pass along to the proper staff. Thank you. My staff then will facilitate that repair.

So, again, a requirement by Major League Baseball to have that ingesting of data as well as support for fans in the stadium and how we integrated it into WebEOC.

I will say a future state here is we are looking at integrating potentially our, video management system. We use Genentech here with Wrigley Field, as well as weather. So weather is always a concern. I know Juvare’s got some great weather integrations as well as great partners that they use. Our solution, is different from them, and that’s not to say that it’s better or worse. But the solution that we use, we would like to harness their alerts for lightning, wind, and rain so that we know when that is coming so that any impact to the game or a non game, we’re getting notified in WebEOC, and then we are making the necessary, steps to address it moving forward.

Yeah. Makes sense. Put all one dash one common operating platform.

I will say so kind of what you see here, and I will go to an incident.

These are all fields that we found were really important to us. So we took stakeholder feedback from our internal departments, whether it’s health and safety, our legal team, our human resources team, our security team, and all of this was customized for our needs, on an event day and a non event day. So you’ll see here, this was a disorderly conduct, where somebody was behaving or violating our code of conduct. And you can see everything from an associated person. We were able to add a statement if someone was to witness it. All of this was preformatted, with Juvare and or not preformatted, was customized by Juvare to be included in these records. Let me get out.

Medical details, vehicle details, police details, witness, all of these things that are important in certain instance that are not. And what we were finding was they we were having these massive reports with where something wasn’t applicable, you’d have a blank field. So by having this toggle, it allows us to hide, and I’ll show an example later too, hide things that are not as important when we pull this data.

Our incident type, you can see all of our dis different incidents, and these are controlled by lists on the back end that can be customized by a power user. Anything that’s important to you can be list and sub listed, in, the admin view of WebEOC. All of your groups are going to be able to be, assigned to you. And, also, I should say, the red asterisk shows a requirement. Again, customize. Some things we need to know, and we force the operator to get the answer. Other things, like an agency I incident number is going to be for certain incidents and not others.

Time stamps, really important for us. It shows when they happen, when they were created, basically, when it was called into us, when it was dispatched, when it was closed.

Event markers, this shows us again, we have to follow-up on numbers of incidents in in the industry, that we work in. A lot of people reference innings. A lot of people reference things not in relation to time. So, another way of us tracking when things are happening, another dataset as well as a dashboard to show where our fluctuation of the incidents happen.

Do we see more incidents towards the end of the game or the end of the concert versus the beginning? Our seating locations, which is, again, in our venue, all of these are customized. One will trigger the next. So if I were to select that something happened in the, concession stand, that will preformat every concession stand as a section.

So you can do that triggering effect so that you’re not having these massive lists in an environment like we have here.

Some specific questions as it relates to our, our legal team that we would fill out. But, again, all of this was customized for us. Super helpful. And let me show you another thing that we did.

So if we go to a medical incident, we have these linked record records at the top. So I will get out of this quickly, but those linked records, allow us to show that when we have, as I alluded to earlier, an incident, an activity, and a request, all of the those three things are contingent on one another. So they are all related. They’re all linked.

And we know that if we pull up one, we know that there is additional information about this, whatever happened, in a different field within. And we’re able to go to that, navigate, launch it from the record, which shows us, when we need to pull that information at a later date to get the full picture.

And finally, I will let me see if I can find one really quickly.

So I believe this was, vandalism. So, this is vandalism. Attachments were big for us. So, we are able to attach anything from a document to a photo.

It lives within WebEOC. It’s downloadable to the if you have the permissions to do so. And so by adding something, we can I will say comments here? If anything is updated, you can add a comment, which is time stamped, and the user is prepopulated to show who made the comment.

And then our attachments here, again, all of this is pulled in a format for our notifications as well.

As you can see, our daily operations, if we go to our daily operations incident, our twenty four seven, three hundred sixty five day a year staff live in these boards. And, right, they log in, and they’re going to see a customized field. I’m in administrative view. But if you were to go in, they were going to see their three boards. And let me switch just so that you can see.

Their boards that they are important to them. Right? It’s user friendly. It populates at the front their daily operations here, for Wrigley Field.

So if they’re sitting there and they’re addressing, you know, phone call or a radio call, something that’s happening, they know an incident’s going to come, they’re going to go to that board, and they’re going to document. So we have lightning. We have alarms, drones, medicals, crime. Anything and everything is going to be living in our daily operations board, whether it’s requests, activities, or instance.

The way we populate here is when we bring in those additional resources, for a game day, a large scale event, and we are, plus in up our staff members, we’re going to switch into event mode. The separation lets us allow the data perspective to show what is happening on a daily basis and what it is happening directly in relation to a concert, a game, so on and so forth. So we’re going to go to a specific incident.

Which we will say is a Cubs game, and then we’re going to use our event specific boards.

Again, a lot of this is going to be when you’re doing if you were to go into a rollout and working with Javaris to develop this, a lot of this is going to be a plug and play. So it’s going to be an export of what you created as what you want as your home board, which is going to be your foundation, and you’re able to they will be able to export that board, reimport that board, and change the name. So you can start with that foundation however many times and manage it however many sites you want. But then once you get into the customization, you can figure out where you want that to live on specific boards. So if we were to go into the incident board for this event, now only the incidents, requests, and activities are going to be specific to that event are going to be categorized here. Again, all of this lives in an incident dependent event board. And when we get to the end of a game, we would go to our and let me switch my position one more time.

We’re going to get to our event creator board. So how we create these events that you see in this drop down is going to be through an event creator board. And you can see we have baseball, concerts. If I go back to before the season, our Cubs convention, our spring training, Winterland, which is an a winter event here that goes all the way from Thanksgiving to New Year’s in in here in the US, rental, Northwestern.

Again, anything from our winter classic, which is the NHL game, all of them are created the same way. And when we create a new event, these drop downs are how we customize. So we start with what type and event name this will automatically populate with what the incident is which is called, our facilities of where this is going to be, our category of what it’s going to be. And, again, as we choose that, the customization allows us to report to be, targeted to what type of event it is.

As you can see, we can show high. These are the things that we saw. Campus activities, these are baseball specific. These will be for a baseball game only, and we can hide those if we’re going to do something smaller, if we’re going to do something larger.

We have events ranging from fifty people to forty thousand, in every step along the way. Some things are going to have a large staff contingent. Others are going to have three people here and have, and, again, we want to document things that are important as well as important to our specific departments. And thus, by able to hide these, we can send this report out to specific stakeholders that need to know the information.

You can really make it your own.

We absolutely did, and this was a big win for us. So let me show you what one would look like. So at the end of a game, we can generate this report, which comes in a PDF form. And, again, customized by Juvare for us, these can be customized for a specific venue, whether it’s, a incident, whether it’s an event.

These this is really just the boards talking to one another, and you can see all of this is important, and all of this is exportable into an Excel. So our actual start times, our actual event times matter, how long a game is, ticket scan, tickets sold, what those active activations are going to be, how many staff are here, who is here, what type of data that we’ve collected, and then those boards speaking to one another is what was important. So we can report this to whoever needs it within our organization, which gives a summary of everything that happened on a specific event. And this is really important to us to show in reference, to show what type of activity, how much activity we had on a game day.

So you have all of your incidents. You have all of your requests, everything that happened in the ballpark on a specific day, all of your act activities, which will be our investigations. It pulls our notepad, which is just basically things that we noted that didn’t have a specific place that we wanted to take record for. In this day, we didn’t have any drones.

Our drones that are categorized to a specific event come in a log form, and we see exactly how many we had on a specific game day.

So the event creator as well as the summary report was a big build in partnership with WebEOC and Juvare. And, again, the customization of what we found with other platforms was building something for one thing does not fit all, and that was the model that we needed to accommodate here was how can we accommodate everything from a small scale event to a baseball game to an NHL major televised national event to, just our daily operations. And everything is fits into this this mold.

One of the last things that I’ll touch on are our analytics. And something that I’ve talked about kind of explicit not explicitly, but, in-depth is having the ability to export, our data in raw form and customize to the needs of every specific department is something that we found really valuable. In previous platforms, we would had to just batch query, basically, all of our data and then farm out what specific things people were looking for to specific individuals. So based on position, our reports can be, and let me get into this real quick.

Based on position, we have the ability to look at our analytics for an entire year. So if we were to go into our incidents, our daily operations, that’s not a good example.

That’s activities. But if I go into event incidents, I can look by the simple drop down every incident, in it always mix the terms incident and event, but for us, they’re called incidents in WebEOC. We call them events. Every event that we have will prepopulate the data.

So if I get it sent on a wild goose chase per se of something that happened on a specific day, the ability to comb through these incidents in WebEOC specifically is super helpful. So this dashboard as well as these incidents show us what happened, throughout all of our games and then every specific game. And these are built for every specific board so we can look back. From there, we’re able to export.

So, again, going based on partitions, based on what privileges we’ve given to specific departments, then individuals can go through specific days or whatever is relevant to them, find a specific incident, and then export it into Excel format. Again, we’ve fed this information to our legal team, our strategy and analytics team, our HR team. And, again, it’s more so for our records of going back. A lot of guest recovery that we do is after the fact when we hear something or get notified of something, and we need to find what that is.

We get tidbits of information that we need to then go searching for, and what we didn’t have was this ability to quickly, similarly to the tabs, the ability to quickly comb through thousands of incidents, to find whether it’d be based on a filter, a location, a time, a person. Any of that has given us the ability to search this massive database. And then at the end of the season, we can pull all of this data for our end of season statistics. The last thing that I will really touch on is really what’s next for us, with the Cubs.

So, we’ve been in this this platform for about a year and a half. And, again, I will say that the, opportunities here are endless, and I wish I had more time to divest into really what we’re looking at for the future. But some of the big things from a enterprise level are we’re a safety act certified facility. So, in, the US, we follow standards put in place by the Department of Homeland Security to be a certified facility.

And as we meet those standards, it creates a lot of different requirements that we have. And so in doing so, we have a pretty extensive business continuity plan as well as emergency response plan. So what we’re starting in in Ian, if you want to touch a little bit about, your COOP or COOP, vertical. But we’re beginning to build out our business continuity and emergency response plan within WebEOC and how it ties specifically to events.

So how it will one thing will trigger another thing, and every step notification that needs to be made, every documentation component is followed to a t. As now, we are figuring it’s based on legacy knowledge, which we are trying to eliminate. It’s people that have been here long enough that know these documents inside and out.

In in an environment where there’s turnover, you want things to legacy things to be documented, as well as just to have those records. Right? Rather than have things in different places, we want to silo both our business continuity and our emergency response plan for elevated incidents into individual boards. And so, Ian, anything that you’d want to add on the coop boards and process for?

We have we have a robust group builder. We’ve got a business continuity module. I’m happy to follow-up and, you know, get deeper dive into that along with the team. Nick, there are there are a bunch of questions in here. Do want to do you wanna dive into that now, or do you want to continue?

No. Absolutely. Let’s do some questions.

Okay. Very good. Jack is asking again, do the Cubs also use GIS and our enterprise asset management software to help document and analyze infrastructure, resources, and related work at Wrigley and other sites? If so, are you integrating that with WebEOC or, sorry, are you integrating with WebEOC to provide situational awareness across the board, or are you attempting to use WebEOC as a catch all solution to those needs?

No. That is something for the future. Right? Our asset management system, we’re not using WebEOC to do so.

It’s driven by our engineering team. We document everything as a redundancy in WebEOC for our records and the overall records of the organization. But I will say I’ve been here for three seasons. The estimates asset management system here predated me.

It was spent years customizing by our engineering team. And so that’s a down the road pipeline that we would like to potentially silo, asset management and GIS into WebEOC. We’re just not there yet.

Very good. Another question is where does the drone information come from? And I may have missed it, but did you mention which product was used to monitor drones? Two questions.

Yeah. So we use, AirSight as a company. AirGuard is the platform. So we have a Aeroscope sensor here, as well as a remote ID upgrade. So we have a back end platform that we use as drone monitoring. The antenna is here on-site, and that data is fed from the AirGuard system directly through the API into WebEOC.

Very good. We got a question from Kevin. Nicholas, you mentioned Genentech. Does your platform integrate with, Genentech? If yes, can you discuss how you’re using them? Next question about is from Doug. You mentioned a few of your requests at Ty and WebEOC with your video platform.

Does WebEOC currently support integration with Genentech?

Yeah. Absolutely. So I would say that we’re in the preliminary stages of Genentech. Ina and I both have had conversations separately.

I think for us, we leverage Genentech and our video management system for a lot of different things. I think one of the benefits for us would definitely be alarms. We use line detection and things of that nature to in analytics to, help our staff manage such a large facility. So, one of the pushes that we’ll have in the future is looking at how we can integrate our alarms and notifications from Genentech into WebEOC.

We just haven’t gone down that road yet.

Coming soon.

Yeah. Absolutely.

Question from CMAT. Was it challenging to train your staff with the daily use, or how long did it take to train your to take for your staff to pick up these processes?

Really impressive. Thank you. Onslow County.

Yeah. Absolutely. It’s a great question. So we did it in a, I would say, a sprint model.

And so Ian was there along the journey for me or with me, and Juvare has a lot of great training modules, videos, platforms, resources to do so. A lot of what we had to do was get in front of people. We started with our power users, our dispatchers who are going to be maintaining this from a, a enterprise system at a computer, and then we started segmenting what our departments needed to use it. So for, you know, those that are using it on the mobile application, what are their use cases going to be in everyday life, and focusing on what is that before.

Because, again, this can be a little overwhelming when you first open it up and you don’t have the explanation of what it is. But if you go through step by step process, I would say we had our staff up and operating We were up and operating within on the hard turn changeover on January first of twenty four. I would say within a week, we were fully operational of, every type of incident and report filled out. And I would say within a month, our overall larger scale larger scale staff were using it on a day to day basis.

And that’s just due to the nature of our environment, the type of time of year it was.

But, again, if you have a lot more runtime and lead time into when you do that cutover from a previous system to a new system, you can absolutely do it on a day’s notice.

I recall closing the contract. It was the end of November, and then we had a conversation the following day. Oh, we got to be game ready by, what it was, January one or something like that, and it was, yeah, it was a lot of fun.

Yeah.

I don’t know if fun was the right word, but we do We’ll call it fun.

We’ll call it fun. Next question from Tim Watts. Hey, Tim. Good to see you. Hi, Nick. Do you utilize WebEOC to record building security rounds for your twenty four seven security staff?

Yeah. Tim, I see that ghost socks underneath that, so I’ll move past that.

We do. So if we were to go and I’m Ian, I’m still sharing. Correct? You can see? Sure. Yeah. If we were to go into our daily operations drop down into a campus security officer.

This is how we monitor everything that’s happening. So these are live. Right? These are current patrols that are going on, where our staff are, post patrols, lunch breaks, everything. So you can see we have fifteen hundred seventy one records here.

That’s from this year. We our dispatcher will categorize and capture every single thing that every officer is doing, where they’re posted, what their role is, and then that patrol is able to access their patrol and input anything. We have, obviously, a preset, formula and format that we do so, but everything is captured here, in our activities.

Good stuff. Next question from anonymous is how long did it take to work with Juvare to customize this to meet your needs before it went live with the organization?

Yeah. I would say, a sprint was probably three weeks of really sitting down and dedicating all of my time partnering with Juvare of the build itself.

But I would say anyone that is considering this, have a lot of your documentation ready. We had a good amount of exported Excel files, lists, locations, types, a lot of different things already ready to go, and that makes your life a lot easier.

Okay. The next question is from Caleb Dixon. What function does the share symbol serve on the list view?

So, when a staff member logs in, so for our events crew, a specific department, they’re able to see and this is from a managerial perspective. So they will see this is what the manager will see. They’ll see what type of game it is. These are the start times.

So they can activate a checklist, and this is what they will see. So, pregame, twelve hours before a game, every broken down by time, what they need to do, and then on the, activated checklist. And this is what you can see. So that day, they did ninety percent ninety seven percent of that checklist.

This is the one that was activated. You can see when it was completed, who it was done, no notes given, so on and so forth. And you go through, everything.

This was we have a something that’s not applicable for that day. We didn’t need to do so. So not a hundred percent sure on the share, but I just want to give that brief overview of how checklists are helpful for us. And, again, the templates are all really easily customized, and we have a million of them so that only the specific one for that game is activated.

Very cool. And a question from Michael meet McPeak. Is the analytics a prebuilt function in this version of WebEOC or a specific build the Cubs have done?

I would say that this it’s combination. A lot of the back end was something that was available.

We partnered with, the developers within Juvare to make it both user friendly and accessible for us. So I would say that, know what you want, and what helps or works with your environment, and then talk to them about what whether it’s just mass exporting, whether it’s mass searching, like, whatever is important to you from the analytics perspective, bring to them, and then they can customize the front end so it’s user friendly.

Very good. Second question, do you graph the incidents and events within your analytics boards to see if there are any specific time frames with high incidents of events?

So we that’s normally what we pull in a different department. So while we do I don’t normally do that in WebEOC specifically. There are some really great dashboard, customizations that you can look at from within WebEOC that can map a lot of your data. It’s just I’m not the best person to speak to it from within our organization, and thus, they are using different platforms.

Question from Eric. What happens when someone calls nine eleven? Is your EOC notified?

We don’t have automatic notification. That’s part of our emergency response plan. So, step one, if necessary, nine one, which is new normally called by us. But if not, then second notification is to our EOC.

Question from Sarah. Yes. The webinar is recorded. We’ll be sent to you after. Question from Dennis.

Excellent briefing. Two questions. Do you have the ability to do a search based on keywords, and can you share your experience with WebEOC support, coordination with nonprofit agencies, partners during mass care or sheltering operations?

Yeah. Absolutely. So, keywords, yes. If you were to and this is a function that is available in everyone. So, your keyword text, that is in any board, in any function, you’re able to keyword search if you’re searching for an incident, or anything for that matter. We have not had the, thankfully, to knock on wood, the need to partner with, let’s say, Red Cross in the US or anything like that.

But I will say that is one of the reasons we chose. A lot of the nonprofits as well as a lot of the state federal agencies are familiar with WebEOC. So we have the ability for future integrations through Nexus should we choose to set up whether it’s integration linking of records, whether it’s sharing data.

We wanted the option to be able to do so. So when the opportunity presents itself, if we so choose, we can.

Very good. And Holly Rose is asking, have you coordinate or plan in future with states the Cubs play that also utilize same system to coordinate data or coordinate further?

It’s something that is on our radar. So it’s something that, again, it kind of goes back to the last sentiment of the if the if other teams or other organizations begin to use WebEOC, it is something that we have the ability to do so. So whether that is whether that is, you know, high or escalated incidents that like, whether it’s Major League Baseball or some other entity may want to know that we’ve agreed upon, again, I’m not the one who’s going to make those decisions. We want the ability. And so, that is something that, absolutely, we have built we’re built for the future.

Next question. Would Nicholas be willing to have follow-up conversations on how they do things how they do things if I think it would be a I think we could incorporate a lot of this in our operations. That is from Mark Michael.

So the short answer is absolutely.

Think Ian and I both, but, specifically, if anybody has specific questions for events industry, how we utilize it here, how we utilize the platform, why we chose it again, and I’ll kick to Ian here. But long way to say yes.

We got our contact information here. We’ll send this out, so feel free.

Do we have time for a few more questions?

How stable has the WebEOC platform been for you? Has there been any downtime while using WebEOC, and do you need to host the platform on your IT or cloud? Is cloud based, Chris this is from Chris Mike Mikolaski?

We’ve had no issues. The platform has been extremely stable. I will say one of the benefits of WebEOC is their customer support and something that we saw lacking in a ton of other platforms that we looked at and what we had.

We have a unique relationship that I don’t know that again, like, we work with some really great people so that if I needed something and I can call, I think Ian would rather we go through the proper channels. But if we call, something will be addressed on the spot. And they know that when we’re in a baseball game, this platform cannot fail. And similarly, in in large scale mass incidents across the world, these things can’t fail.

They need to be ready to readily fix them at a moment’s notice. And that’s how they’ve done it for us. We’ve had it one time where we and it was cosmetic. It was not anything that was dropping or anything like that.

It was a field that was not populating in a report. They fixed it within five minutes. So, I can’t say enough, about that.

Good stuff. Appreciate it. It’s been a pleasure. Question from Caleb Dixon. Is everything built and maintained by Juvare, or do you have on-site developers or third party?

We’re fortunate to have on-site IT, but they don’t touch most of this. The most, collaboration we’ve done was our SMS, pass through from our SMS platform Twilio into WebEOC. But for the most part, everything is run through Juvare developers, and we partner with them to do it between myself, my department, and Juvare.

And from Dennis, he’s obviously with TSA. I have to go. Great briefing. Thanks so much. Go, Cubs. I think that’s the we got to the questions.

Future webinar, managing hurricane season on July twenty ninth with WebEOC and WeatherOptics. It’s overview of WeatherOptics, WeatherOptics integration with WebEOC and live demonstration. You’ll see and hear about the key benefits and user weather optics and real world use cases. Sorry.

And his contact details is here. We’ll send you this out. Feel free. Give us a call.

Any event spaces, feel free to call Nick and have a chat, and, you’ll hear it all. But we really appreciate you, Nick, for taking the time with your busy day, and, look forward to the collaboration and working together.

Yeah. No. Again, can’t say enough good things. We’re extremely happy here in in Chicago. The platform is exactly what we needed.

And, again, Juvare has been a great, organization to work with to meet our needs here. I can only see things getting better in the future. And, again, my contact information is there if you’re in the industry or not in the events industry and just work in emergency management or anything like that. Don’t hesitate to reach out.

We’re happy to chat through.