Franziska Nothofer:
Hello and welcome to today’s webinar on how to Drive Alert Relevance as part of our supply chain optimization webinar series. My name is Franziska and I’ll be your host today. And I’m joined by our expert presenter, Roy Van Monfort senior Solutions consultant here at Everstream Analytics with a wealth of experience in the supply chain risk management space.
And he’s joining us from the Netherlands today. Just a quick note before we start. All attendee lines are in listen only mode, but if you have any questions throughout today’s session, we’d love to hear from you and please pop them in the q and a box at the top of the GoToWebinar panel and then we’ll cover as many as we can towards the end of today’s session.The full recording will be sent within 24 hours straight to your inbox. Alright, with that we can get started. Roy, over to you. Thank you.
Roy van Montfort:
Thank you very much Franzi for the nice introduction. Welcome everybody to today’s webinar about driving alert, relevance, and um, we really would like to explain, educate a little bit more on why that is important. And it is also primarily driven by a lot of customer feedback we have received in the past from, uh, from our customers of course. So if we talk about relevance. What actually sort of needs to happen is that the challenge, or maybe even problem, what we quite often have seen in the past is that. The feedback we received is that we get too much information, it is not relevant. We don’t know where to start and and if we take a look at the screen right now where it says customer roles and responsibilities, this is actually where it starts in order to be able to create that relevance. What we quite often do with an Everstream is we, we ask a lot of questions to our customers, our customers to be, and uh, and that’s for a reason of course. The platform, what we offer the solution is, is highly configurable, and that’s for a specific reason. One of those reasons is in order to create actually relevance. And it’s not only about notifications that are being sent, it’s about what’s behind those notifications. How are those notifications as an example, triggers or what kind of views can I built myself as an example within the platform, or what kind of dashboards can I slice and dice in order to see what’s relevant to me? Because everybody on this particular call, presumably has a certain role with certain responsibilities within, uh, within your organization. So you would like to be informed about what is relevant to you, right?
So you might be a supplier manager, a category manager, commodity manager. Et cetera. So, um, so what we do as Everstream is we start asking questions about how is your organization actually structured? How does your example given risk management department look like? Or how is procurement built, right?So what are you responsible for? And what we typically see is that from a everstream platform point of view, we see these three areas, right? So we talk about end user, super users, and on the right hand side we see a co OE. Which is a center of excellence, right? So, um, and the center of excellence to start with, on the right is more or less the higher organization. It’s the umbrella organization overseeing your operations. And within those operations, we typically see a breakdown on end users and super users. Like a supervisor as an example, that’s responsible for certain departments, for certain category managers, et cetera. So it’s key to understand how that is structured, and that’s also for yourself.
If you’re looking into procuring a risk management solution, take look at your own organization and am I lined up for this? Right? That’s basically the question you should ask yourself because if you are, and we know about this. We have the options and the possibilities in order to be able to drive that relevance. Everybody is looking for. Essentially what you don’t want to happen is you go to work, you open up your laptop or your pc, you open up your, your Outlook client or any auto mail program. And and there’s a big, bold, printed number with, uh, with new messages just from the Everstream platform, right?
So, because then you will ask yourself: Where do I start? Right? So that’s why it’s important to understand how am I organized? How am I structured? Do I have this particular. Breakdown in place, as an example, et cetera. So we talk, for instance, about a center of excellence. Uh, what we see typically in, in quite larger organizations. It doesn’t have to be, it’s about how are you structured and what are your responsibilities. So that needs to mimic this slide, what I’m actually showing on screen right now. And once we have identified that once we as everstream as an example. Understand how that works on your side. Then we can talk about, okay, so who needs to receive which information at what time, right?
And that rollout process essentially is sort of structured as follows, right? So, uh, so we call this rolling out, rolling out the alerts and the, uh, UI to the business. And, um, and it should be done in a very manageable way, in a controlled manner, right? So, um, and if we talk about best practices from an Everstream point of view, what we see with other customers is that we sort of recommend to do it by, by user groups, right? So, because as I mentioned on the previous slide, each that everybody has. Their own responsibilities. You are working in a certain department, you have your responsibilities within that department, and that can be, you know, commodity, strategic sourcing. Um, you might also work on logistics because risk also applies to logistics, of course.
What we also offer, and if we then take a look at the four pillars, basically we talk about, communicate, identify champions, drive relevancy, and then have the mass rollout. And that’s important to understand because this essentially is the basis in conjunction with the capabilities the Everstream platform offers in order for you to get relevant alerts only. Now I talk a lot about alerts because that’s primarily what we see happening, what our customers want, and it’s always finding that balance of getting alerts. Uh, you don’t want to miss out on those of course, but you also do not want to be overwhelmed with particular information and that can be a challenge. Absolutely. Right? So, um, but you do need to have a solution in place that is supporting you in order to achieve that goal. So, um, so hence we say, okay, everybody needs to be aware within your organization. So communicate, right, so that you are going to do this, or already doing, or are you changing this? So leverage your senior stakeholders, right Inform your employees, inform the particular departments, and how are you going to do this? And the departments might have their requirements. So listen to those departments, listen to those people, how it works in a day-to-day business maybe. You need to identify therefore champions in your organization.And those champions are basically the leading person in that organization who is the first point of contact in order to understand this is how we would like to receive alerts. This is when we would like to receive alerts all for you to be able to create that relev. Which is basically the third vertical drive for relevancy, right?
And that’s something we do together, right? So, um, so together with Everstream Analytics primarily if we do a new implementation, the implementation team, we would speak to you, we would speak to your people, we would need to understand your operations, et cetera. And, um, all in order to get a proper view of how things work on your side. And what we then do is we basically translate that and how can we convert that into the functionality or into the configuration options of the solution. And then we have, on the right hand side, we have what we call the rollout. And the rollout is typically we go to turn on the button. Now with live people are getting scheme modifications. It also can be, for instance, a trigger that go try an API into your system where you would like to have risk information. As an example. We also educate people on how to use. Views within the application, how to slice and D dashboards in order to create that relevancy. ’cause if I’m an employment employee of a company, responsible as a category manager, I’m only basically interested in what is happening in my area, right? So it’s my comfort zone. That’s all I need to know about, and that’s what I’m responsible for. Maybe a little bit black and white, but essentially that’s, that’s how it works. That’s the message I would like to deliver, that we actually can do that, right? So, um, but once you have gone through this particular process in order to determine how does my organization look like?
What is it we would like to receive on information when we like to receive that and real time, a daily summary, a weekly summary, a combination of those, depending on the severity of the, uh, of the disruption, right? We all can set it up. This is an ongoing process because your organization might change, your operations might change, your suppliers might change, et cetera. It’s never a static environment. It’s quite a dynamic environment, as I presume everybody would agree to on this particular call. And that’s why it says on the mass rollout run ever stream’s, continuous relevance improvement cycle. And that’s basically, if we take a look at the next slide, imagine you are.
Onboarded as a customer with an everstream, then we would go through all of that, what I just explained to you, right? So we would need to understand how does it work on your side, and we ultimately come to a joint goal. This is how we are going to set up the solution. Typically what we see after the implementation, we have a hypercare phase where we can still fine tune things, but essentially there’s going to be a moment where you say, yes, I’m happy with this. This is the information I need. I’m not overwhelmed, and I’m also not missing out on certain information because that’s basically the key, the key message of what we call relevance, right? So if we then start on the top right hand side, on the right hand side, you can see, monitor and update, right? So customer and everstream monitor outgoing alerts.
So we talk about it, right? Are these alerts, right? Is this us according to expectation, et cetera, et cetera, right? So, um, and if something is not right, then uh, then we interact on it, right? So, uh, we still have the possibilities to fine tune it to your specific desire. If we take a look at this circle, if we go to 1, 2, 3, et cetera, we end up at the green box on the left hand side on the top, and essentially you, you would need to take a moment in your organization where you say, we need to review this because as mentioned, if we have set this up and it all works great, but if something changes on your side that needs to be reviewed.Now if you are an Everstream customer, you will get direct access to a value realization manager. You can communicate this with him or her. It can be done in Q bs. You can set a yearly appointment for that. It really is up to you how you would like to do that, but we, of course, we um, we sort of promote the urge in order to do it on a more frequent basis because your environments are quite dynamic as mentioned.
Now, we spoke a lot about the organizational structure on your side that we need to understand that. And now is of course the question, why do we need to understand that? Because now we sort of need to translate this into the solution capabilities, right? So, um, and if we talk about those solution capabilities, essentially if we identify a incident that is supply chain relevant, that is potentially disrupting your supply chain.
Whether it is your supplier, your logistics operations, your warehouses your materials, et cetera. These incidents, they come into our backend within Everstream and agent. Every incident, first of all, is human validated, and that’s key because if it’s not human validated, we can’t. Offer additional information like shape, industry, entity tagging, et cetera, right? So the boxes you basically see on screen right now, I’m going to explain to you a little bit more in detail what that actually means, and then we’ll go into the solution itself in order to show you some examples on how that actually looks but which you quite often see is on the left hand side to start with.
On the geolocation alerting is quite often based purely on the location. So, so where is that incident happening? It really depends on what kind of incident. So if it is an, if it is a fire at a certain industrial zone or at a certain location, then that’s, that’s very location driven, of course. And what you typically see is that, uh, that solutions then sort of take a look at, hey, it’s happening in this area. But you might have multiple. Facilities in that particular area, and you don’t want these facilities to be impacted. You want to know exactly where is that fire, right? And how is that impacting my supply chain disruptions, think about an insolvency, and insolvency is very company specific, right? And um, and you don’t want to have just a geolocation tied to insolvency. You want to know what company is it about? Is it about a specific site? Is it about a specific group, et cetera, et cetera. So that’s what our people, we call them the intelligent solutions wizards.
That’s what our people actually do, uh, before we actually publish an incident and make it available to our customers using our solutions, right? So, uh, so we add the geolocations, the shapes. We also see if we can identify is this particular event or incident relevant to a certain industry, right? Or is it impacting a certain industry, I should say. Yes. Then our people will add that information to the particular event. Also, can we identify to which particular legal entity is this type? Right? I just gave the example of the insolvencies and the insolvency of course, quite often is relevant to a certain, uh, to a certain company. And then we also need to have the possibility about.
Frequency, right? So how would you like to be alerted? And you need to be able to make the decision yourself, and I’m going to show you in the solution actually how that works. But if we take a look at these boxes, let’s take a closer look at what is our baseline. So if we take a look at at at, at this particular screen, we’ll see that in the old days, as I like to call it, we had. A standard way of filtering for all platforms. So, uh, so the upstream solution works with what we call incidence profiles. And an incidence profile basically says these are the particular risk types or risk categories I’m monitoring. And if, if a certain risk type, like a port congestion, which you can see on screen on the top top right hand side, if a port congestion occurs, then that needs to be scored. So the everstream solution scores from one till 25. But what our people do in the backend is basically once the incident comes in, they take a look at the incidents. They have playbooks, right? So they have scenarios available in order to determine the impact of the incident, and they assign what we call a severity level.
Minor, moderate, severe, and extreme. That severity level then translates into a score and each, every customer can have. His or her input on, how would you like to have that be interpreted? So because customer A might say severe is for US score 20. Where another customer might say, severe is for us score 21.So all of that is very customer specific and this a starting point of relevance. But if we talk about a port congestion in this particular example, and. What’s typically happens is that solutions work with a radius. Think about a circle and we pinpoint the part, uh, particular port, but we don’t know exactly where in the port maybe.
So we apply a radius, right? So we’re just in this particular example, 10 miles. It’s adjustable, it’s configurable, but this is a baseline, right? So overall it’s a solid solution and it’s really a starting point as we see it. And we did mention some challenges with this approach, right? So, uh, as I just, just giving in the example you had, you, you will have an emphasize for event impacting a geographic region, right?There is no industry information yet tied to it. And it typically fails to deliver for procurement centric categories. Also, also think about commodities as an example, right? So this is purely a baseline where it says port congestion as per the example, which is part of my incidence profile. And if a port port congestion applies, the solution needs to score and it needs to be in a radius of 10 miles.
In this example. Now that’s the base. Now, I was explaining to you on the previous slide, this, this order. Areas we have in order to drive relevancy. And now this is actually where it gets sort of interesting. So we’ve got what we call shape base alerts and the shape base alerts. You can already see it on the screenshot example on the top right hand side, right? So in this particular case, we as Everstream, our team in the background is actually applying multiple geo coordinate. In order to define that shape. And it can be a very random shape as you see. And what the solution then basically does is in within that shape, is there a supply chain of you present that also applies to the particular conditions of the incidence profile, right?
But the shape based alert will overrule what I have explained on the previous slide, right? So, um, and uh, and that’s basically the four bullet point over here. One shapes of tied to an incident. Our standard way or the base methodology I was was explaining per profile is not going to get triggered.Or else you would get non-relevant information maybe. And that’s what we call the incident alert fatigue. So this is, this is already one of the benefits it starts to apply on, I also spoke about the industry relevance, right? So within the Everstream solution, you can indicate which industries are not relevant to you, and we will then eliminate all those industry relevant incidents.
To score against your supply chain network, right? So if you have, or if you are present in the automotive. Then you would not like to be notified about incidents that are relevant to the food and beverage industry, as an example, right? So this is an additional topic. What we, our people do add to the incidents if possible.Of course, if they can identify the industry can also be multiple industries. Be careful. What we do is we add it to the particular incidents before we publish it into the solution. And you can use that industry relevance, uh, in order to understand if this is relevant to you, yes or no. And we do that together. We, we ask our customers, is this relevant to you, yes or no? And the other one, what we talk about is the organizational tagging, right? So we really go into company information if we find an information or an incident about a certain company. And in this particular case, I’ve got, uh, I’ve got an incident listed, uh, about an automotive, uh, company.Of course. Automotive manufacturer maybe better set. And, um, and they plan to close seven production plans globally by 2027. So, um, now underneath Nissan Motors. A lot of different entities, and you would like to understand, is this relevant to my entity? Right? So think about production plans that get closure.
So, the network is, for instance, the suppliers which you are responsible for, right? Or the logistics routes you are responsible for, the shipments, et cetera. Those networks, I would like to get a realtime notification if you are responsible for the network identifying risk. And there. I also would like to have real time notifications.
We also categorize events if they are major, yes or no. And in that case, you can say, I want to have a daily, and you should, you should be able to turn this off as an example, right? And see the categories and the industries, what we talk about, the commodity risk, all these criteria which we use to create additional.
Information that ultimately creates more fine-tuned relevance. All that information you can be informed about in different ways. So if there’s a real time risk in your network for a particular supplier, you’re responsible for, you get a real time message. But if there is an industry relevant. Incident, you can say, okay, I only want to have a daily summary about that.
So, um, so those are sort of the, the possibilities what we have. And I would like to give you some insights and uh, go a few minutes to the solution and then we have a little bit of room for questions. Of course. Um, so if I would pull the, um. The solution for Everstream Analytics.
Apologies. Here we go. If I would pull the solution for Everstream analytics, and this is one of the, the screens, if I would log into the solution where you can see, uh, a variety of different incidents, right? So, um, so these are all of our incidents. You can see already, okay. A little bit of analytics on top of that.
If you’re not interested, you can. Get rid of that. Of course. Right. And you have a little bit of a larger view, but typically what you see over here is these risk types. The severity, what I explained, right, and this is quite important to, uh, to understand. Because if we would take a look at a particular incident and I can sort of take any kind of, uh, of, of incident, if I would take a look at that particular incident, I can see, for instance, okay, this is the information Everstream has added on the right hand side, as you can see, right?
So, um, this is the incident for the Japan, uh, based Nissan Motor Company as an example. So we have these multiple incidents and you can build your own views. Like the triage window. I can also say I’m only interested, for instance, in floodings, that’s also a possibility. So if I’m interested in floodings only lemme refresh my screen for a moment here.
If I’m interested in floodings only, then you would like to understand, okay, what is actually impacted. Floodings are typically one of those incidents that go with this shape, right? So, um, so you can now see there’s one facility impacted. And why is that? Why is that relevant? Why am I showing you to this?
Right? So in this particular case, I created the markup supplier, the not so lucky supplier because he’s impacted by the incident, right? So, um, but if I would go back, for instance, to the incidents or I would search actually for that particular solution. Sorry, that particular supplier within the solution, I could say, okay, now show me all of my suppliers that have lucky.
So I’ve got not so lucky supplier and I’ve got a lucky supplier. So if I would go to the not so lucky supplier and I would open my map. And I obviously can see that, that not so lucky supplier is actually in that particular area, right? So it’s located over here and this is where that rainfall and Pakistan is happening at the moment.
But if I would say, Hey, now show me that other one. Right? So because you had uh, two and they were very close to each cello. And I apply the filters. I actually can see that they are very close to each other. But this is the level of detail what Everstream actually provides, right? ’cause this one is right on the border and it’s potentially impacted by that heavy rainfall. And this one is just outside of that boiler. So this is the lucky supplier and this is the not so lucky supplier, right? So, um. So this is just to inform you on how do we make things relevant, actually, right? So, um, think about the industry. Think about the, the, the the tagging, et cetera. There’s a lot of information in there, and because on average we have approximately 1500 incidents live on a day-to-day basis, but not all of those 15 hundreds will impact your business, right? So, um, the last thing I would like to show you is how are you going to be informed as an example? So if you are interested in what we call workflows and I have created a, a workflow over here, what we call the webinar, and I have created a particular scenario for that. I’m working in procurement. I need to be alerted where my core criteria are only locations, suppliers located in Germany and only suppliers that supply electronics only and then that are production relevant only.
I can build that as such, right? So I can create a work profile. I can go actually to my production categories. I can say to these production categories, yes, I’m interested in all of these as an example, but in the in the industrial zone, I’m only interested if it’s medium and false. EU only interested if it’s high supply material shortage and workplace conditions also interested if it’s high. So that’s my first criteria. I’m going to say, inform me about these risk types. If there are certain severity levels associated, and now I’m going to tell only do that for my de suppliers and electronics, right? So I’m going to create a rule, right? And that particular rule, if I create it, I can add it. Now, I can now say within the solution, only tell me, or show me my suppliers that are located in Germany, right? I’ll save that. And only show me my suppliers that are responsible for, uh, electronics as per the, uh, example, right? So, um, electronics as an example. So now we’ve got two suppliers in Germany where I procure electronics from, right?
So, basically what I told the solution is. For these suppliers, because they meet my criteria, I only want to be informed in case we find a network incident that is in the production area, operational product, unavailability or workplace condition. With the severity levels, and now I can say I only want to receive them myself, or I want to be sending this to a group. And I can also say, send this to another additional person within my organization. So that’s how easy it actually is to set up these particular, uh, particular email notifications. And you can do that for yourself. We can do that on corporate level, we can use a combination, we can use that for WaPo configurations, API, triggering, et cetera, et cetera. So that’s all a possibility. We have a few minutes left and I think it’s time that we go through some questions, if that’s okay with everybody.
Franziska Nothofer:
Perfect. Thanks Roy. Yes. We’ve already had a few questions come through. Great ones. So the first one is how do you fine tune alerts for specific industries or regions?
Roy van Montfort:
Exactly. Exactly. So Regions is, um, is, it’s all about our team, our solutions intelligence with team. So of course we apply a lot of big data, a lot of ai, we buy data as an example. We have our proprietary data, but the people behind that are. Absolutely key, right? So you, you can’t deliver proper information without the people. It’s a very manual process quite often. And they assign that to the particular incidents so that you can use it in the, uh, in the solution.
Franziska Nothofer:
Perfect. Thank you. Okay, onto the next one. What’s your experience with shape based versus traditional geolocation alerts and their operational impact?
Roy van Montfort: Yeah, that’s a good one.The, the shape dish. Very good question. Indeed. So the shape based one is actually basic. It’s the example I’ve shown where I said we’ve got the lucky and the unlucky supplier. So the traditional approach, you would have a circle and that lucky supplier probably would also be hit by that incident. That would mean you would need to, to review two of your suppliers or any other supply chain participant, right?
The shape based one. Really goes into the nitty gritty of the geolocation. Where is this incident actually happening on a geographical scale? Mm-hmm.
Franziska Nothofer:
That’s very helpful. Thank you Roy. I’m just conscious of time now because we’re almost at the end of today’s session. So yeah. Thank you, Roy, for a great presentation and demo today. And thank you to all our attendees as well for being here with us today. We will follow up on the remaining questions. We couldn’t get to one-on-one. Okay. And now that wraps up the session. If you’d like to get in touch with our experts directly, please email us at info at everstream ai and you will also receive the session recording in your email inbox within the next 24 hours.Okay. Thanks again. Have a great rest of your week, and goodbye everyone. Thank you.
Roy van Montfort:
Goodbye everyone.