Latest / Speaking of Supply Chain / Breaking Down SAP Signavio: Process Insights vs. Process Intelligence

Transcript

Breaking Down SAP Signavio: Process Insights vs. Process Intelligence · Speaking of Supply Chain

• 0:06
  Speaker 1: You're listening to Speaking of Supply Chain, a meboch podcast.
• 0:10
  Speaker 1: This is a show for logistics professionals looking to learn
• 0:13
  Speaker 1: more about the latest innovations in supply chain. Each episode
• 0:17
  Speaker 1: will feature a conversation on topics such as mitigating supply
• 0:19
  Speaker 1: chain disruption and reducing risk, current automation trends, sustainability initiatives,
• 0:25
  Speaker 1: and more. Let's dive right in.
• 0:29
  Speaker 2: Hello, and welcome to Speaking of Supply Chain, where we
• 0:32
  Speaker 2: explore trends, current events, and innovations impacting the logistics and
• 0:35
  Speaker 2: supply chain industries. I'm your host, Ellen Wood. Process optimization
• 0:40
  Speaker 2: isn't just theory, it's real rold action. Join us as
• 0:43
  Speaker 2: we sit down with my guest host, Christina Schulea at
• 0:47
  Speaker 2: Logimat to explore how SAP Signavio supports smarter decisions at
• 0:52
  Speaker 2: every project phase. You'll hear firsthand use cases, honest insights
• 0:56
  Speaker 2: about common implementation hurdles, and a warehouse health chain that's
• 1:00
  Speaker 2: redefining what long term success can look like. If you're
• 1:04
  Speaker 2: ready to connect design with reality, this one's for you.
• 1:11
  Speaker 3: So Philip, Day three of Logimat, it's been exhausting, at
• 1:16
  Speaker 3: least we're sitting doing.
• 1:16
  Speaker 4: This podcast finally I'm sitting.
• 1:18
  Speaker 3: Yes, sir, Yeah, We've seen a lot of different things here,
• 1:22
  Speaker 3: but I think one of the most interesting things, obviously
• 1:25
  Speaker 3: is signavio. So yeah, so let's talk a little bit
• 1:28
  Speaker 3: about process optimization, warehouse optimization, and sap zignavio. And we've
• 1:36
  Speaker 3: brought some or you have brought some very interesting use cases,
• 1:40
  Speaker 3: but I think before we dive into the use cases,
• 1:42
  Speaker 3: let's talk a little bit about what is signavio and
• 1:47
  Speaker 3: what can it do for you.
• 1:48
  Speaker 4: First of all, I want to say thank you for
• 1:50
  Speaker 4: having me, thank you that I'm allowed to sit. I've
• 1:54
  Speaker 4: been standing for three days at my feet hurt, but
• 1:57
  Speaker 4: thank you.
• 1:59
  Speaker 3: Okay, So tell us a little bit about signavio before
• 2:03
  Speaker 3: we dive into any use cases and what what it
• 2:06
  Speaker 3: can do for.
• 2:09
  Speaker 4: If you, if you remember the logo that I brought,
• 2:13
  Speaker 4: that I opened up with, like you have this circle.
• 2:16
  Speaker 4: And I always always when I when I talk about
• 2:19
  Speaker 4: process analysis and when I try to lean into okay,
• 2:22
  Speaker 4: what is actually signavio, I always have to define what's
• 2:24
  Speaker 4: the vocabulary? Like what are we talking about? Because each
• 2:28
  Speaker 4: of these modules is so different in its use case
• 2:32
  Speaker 4: and so different in expectations that I always have to
• 2:36
  Speaker 4: they are. They are all basically called signavio signo, but
• 2:43
  Speaker 4: they always do so different things. And that's why I
• 2:45
  Speaker 4: spent the first ten minutes defining, Okay, what is Signavio,
• 2:48
  Speaker 4: what are we talking about, and how can it help?
• 2:52
  Speaker 3: Sounds perfect?
• 2:54
  Speaker 4: So yeah, you basically the circle that I that I
• 2:59
  Speaker 4: open up with, and I keep calling it a circle.
• 3:01
  Speaker 4: I know it's a keyhole. It's supposed to be a keyhole.
• 3:04
  Speaker 4: The circle is then defined in like your you have
• 3:08
  Speaker 4: your free categories, your your outside areas, and they all
• 3:14
  Speaker 4: gather in the middle you. You have your collaboration hub.
• 3:16
  Speaker 4: It's like your your entry point to to think now
• 3:19
  Speaker 4: you when you log in, you you land on the
• 3:21
  Speaker 4: collaboration hub. You land on the first page of your
• 3:25
  Speaker 4: of your process house, and then you can dive into
• 3:30
  Speaker 4: the into each module and get to where you want
• 3:34
  Speaker 4: to be. The modules are categorized as you have your
• 3:38
  Speaker 4: modeling and your process management, which is where signal you're started.
• 3:43
  Speaker 4: You have your technical analysis things. You have your process insights,
• 3:47
  Speaker 4: process intelligence which where I feel at home where you
• 3:50
  Speaker 4: do the process analysis what we talked about earlier. And
• 3:55
  Speaker 4: you have your process covenance things like when you have
• 3:57
  Speaker 4: your system house set up, and you have your you
• 4:00
  Speaker 4: are happy with the value chains, with the BP menst
• 4:02
  Speaker 4: you define, then you can define workflows on Okay, what
• 4:08
  Speaker 4: happens when I want to make changes? How many eyes
• 4:10
  Speaker 4: do where I need to have the things approved?
• 4:13
  Speaker 3: Sounds good? So, and then can you elaborate a little
• 4:17
  Speaker 3: bit on the process analysis, because I think that's kind
• 4:20
  Speaker 3: of what we focus here. One thing that I had,
• 4:25
  Speaker 3: I admit I had a little difficulty to understand in
• 4:28
  Speaker 3: the beginning was the difference between insights and intelligence. And
• 4:32
  Speaker 3: I built this little bridge for me. So insights is
• 4:37
  Speaker 3: when you analyze all the data that is inside of SAP,
• 4:42
  Speaker 3: but you don't necessarily have to have the whole suite
• 4:46
  Speaker 3: of SAP to make use of signavio, right, so you
• 4:50
  Speaker 3: can also you can also pull in data from other systems,
• 4:56
  Speaker 3: and that's when process intelligence comes to place, comes into play.
• 5:00
  Speaker 5: Right.
• 5:01
  Speaker 4: So exactly, the signavio wasn't very useful in its naming
• 5:07
  Speaker 4: because insights and intelligence they are roughly the same vocabulary.
• 5:12
  Speaker 5: Right, Your bridge is actually very useful.
• 5:15
  Speaker 4: Like, as long as you're moving in SAP standard content,
• 5:20
  Speaker 4: process insights is.
• 5:20
  Speaker 5: Your go to.
• 5:21
  Speaker 4: It gives you your broad overview Okay, how is my
• 5:25
  Speaker 4: SAP system performing, How is my e C c AS
• 5:28
  Speaker 4: for E W M t M.
• 5:29
  Speaker 5: How are they how are they doing?
• 5:33
  Speaker 4: How are how good is our company in SAP standard
• 5:38
  Speaker 4: And maybe if you're if you're transforming, like process insights
• 5:42
  Speaker 4: gives you an analysis on which features you use and
• 5:46
  Speaker 4: which features are interesting, and maybe you want to get
• 5:49
  Speaker 4: some insights. Okay, in my ECC I'm doing DCN DSE
• 5:51
  Speaker 4: transaction codes, and then it can tell you, okay, look
• 5:54
  Speaker 4: at these as four features that maybe you should start
• 5:58
  Speaker 4: investigating if you are on that journey, if you want
• 6:02
  Speaker 4: to step outside s A P or if you want
• 6:05
  Speaker 4: to start digging deeper instead of just having the broad overview,
• 6:08
  Speaker 4: and you want to like you you found your pain points,
• 6:11
  Speaker 4: you found your issues that you want to tackle. Then
• 6:15
  Speaker 4: you come with process intelligence and you can either plug
• 6:18
  Speaker 4: it into the process insides data like you don't you
• 6:22
  Speaker 4: don't need a secondary data trans extraction feature. You can
• 6:29
  Speaker 4: just plug pros intelligence on process insights and then use
• 6:32
  Speaker 4: that data to drill deeper. Or you can do like
• 6:35
  Speaker 4: a true mining where you have your data extraction which
• 6:40
  Speaker 4: is in the same network as your ecc as for
• 6:43
  Speaker 4: whatever and basically extract the process data that you want
• 6:47
  Speaker 4: to look at, and then you can define the rules
• 6:50
  Speaker 4: and the KPIs the metrics or your or your scripts.
• 6:55
  Speaker 4: You can define yourself with process insights. You're stuck with
• 6:58
  Speaker 4: what you get Like it's a click of a button.
• 7:01
  Speaker 4: It's super easy, but you're stuck with pros intelligence. It
• 7:04
  Speaker 4: takes a few days to get set up, but then
• 7:07
  Speaker 4: you can actually use it the way you need it.
• 7:10
  Speaker 3: Okay, that's interesting. So so bottom line is you don't
• 7:14
  Speaker 3: need to have the full SAP suite to make use
• 7:18
  Speaker 3: of this. You could have an external warehouse control system
• 7:21
  Speaker 3: and you could have other things plugging in and as
• 7:24
  Speaker 3: long as you can access the data, you can analyze
• 7:27
  Speaker 3: that data as well.
• 7:30
  Speaker 4: To analyze process data, you basically only need an event lock.
• 7:34
  Speaker 4: An event loock is you have your events that are
• 7:37
  Speaker 4: taking part like opening a sales document, and that event
• 7:41
  Speaker 4: has a time stamp and as long as we have
• 7:44
  Speaker 4: that connection, we can analyze it. Okay, and if that's
• 7:49
  Speaker 4: an SAP or if that's another system.
• 7:52
  Speaker 3: Sounds good. So Ben, let's talk about the first use
• 7:56
  Speaker 3: case where you see big benefits of of using signavio.
• 8:02
  Speaker 6: Sure, well, first use case for us is a typical
• 8:06
  Speaker 6: sap E WM implementation full implementation cycle. So we're going
• 8:12
  Speaker 6: from discover to in the end to go life before
• 8:16
  Speaker 6: we dive deep into the different stages or phases of
• 8:21
  Speaker 6: a project, maybe just you know, to give a hint
• 8:24
  Speaker 6: on what kind of problems s ap zignavio solves for
• 8:28
  Speaker 6: WM projects. It's like things or problems that happen during
• 8:34
  Speaker 6: a project which no one really talks about, but which
• 8:38
  Speaker 6: are common in every project. Especially we as a consultancy
• 8:41
  Speaker 6: who do a lot of these projects, notice them basically
• 8:44
  Speaker 6: in every project, things like, you know, how you get data,
• 8:47
  Speaker 6: how you can prepare the data to analyze it to
• 8:51
  Speaker 6: get a result. And then also stuff like documentation, documentation
• 8:55
  Speaker 6: and every project you know, it's always a it's always
• 8:59
  Speaker 6: pain let's say it like that. And then yeah, as
• 9:03
  Speaker 6: the last point is changes to for example, documentation and design,
• 9:07
  Speaker 6: how do you get it back into the original design.
• 9:10
  Speaker 6: So all of these things are solved by sapsic navio
• 9:14
  Speaker 6: or at least supported. This is why you know, for
• 9:20
  Speaker 6: projects it's extremely useful. The only problem or the fact
• 9:25
  Speaker 6: that I see today is that since there's at least
• 9:29
  Speaker 6: according to my knowledge, nothing similar or a combination of
• 9:34
  Speaker 6: products that are similar to SAPSG navio or that solves
• 9:38
  Speaker 6: the same problems. It's still something new, but the problem
• 9:42
  Speaker 6: and the use cases are there. It's you know, it
• 9:44
  Speaker 6: solved the problems and the use cases that are there.
• 9:47
  Speaker 6: But since it is new and no one really done
• 9:49
  Speaker 6: it before, using sapsic navio still feels like a luxury
• 9:53
  Speaker 6: for a project. So you can do it, but you
• 9:57
  Speaker 6: don't need to do it. You can work around it somehow.
• 10:01
  Speaker 6: But I think if more companies will using now you
• 10:05
  Speaker 6: in the future, and more companies will recognize the what
• 10:10
  Speaker 6: is useful about SAPSG now You, then it will get
• 10:14
  Speaker 6: or it will move from a can use it to
• 10:16
  Speaker 6: a must use it to stay you know, or to
• 10:21
  Speaker 6: to execute project SAP projects with a lot of quality
• 10:26
  Speaker 6: and small durations. But yeah, that's just as a as
• 10:31
  Speaker 6: an introduction to the to the project phases themselves.
• 10:35
  Speaker 5: Okay, great, So if we look at.
• 10:37
  Speaker 6: The different phases in the project, you know, for a
• 10:41
  Speaker 6: need to BM project, at least start off with a
• 10:43
  Speaker 6: discover phase where you try to well get as much
• 10:47
  Speaker 6: data from the from the customer as possible. You try
• 10:51
  Speaker 6: to get a feel for what the customer wants to
• 10:53
  Speaker 6: solve and you prepare organization data, et cetera. Here you're
• 11:00
  Speaker 6: the key fact where s appeasing now you can help
• 11:03
  Speaker 6: is getting data data mining, because usually we would have
• 11:06
  Speaker 6: to get that data from customer documentation and interviews. Getting
• 11:10
  Speaker 6: that data directly from the system is very helpful, especially
• 11:14
  Speaker 6: since the data is also modeled in a good way
• 11:16
  Speaker 6: so you can analyze it very quickly and easily.
• 11:19
  Speaker 3: Would you say that's the most elaborate phase in the
• 11:24
  Speaker 3: in the entire circle, or well, it sounds like a
• 11:28
  Speaker 3: lot of work getting this data together, is it, or
• 11:31
  Speaker 3: is that just my impression?
• 11:32
  Speaker 6: Well, this data for a discover phase is usually more
• 11:36
  Speaker 6: on a high level, so it's actually a good fact
• 11:39
  Speaker 6: that you brought it up. Where this gets into well
• 11:43
  Speaker 6: more details is the next two phases prepare and explore.
• 11:47
  Speaker 6: So yeah, discover is like, well a first step in
• 11:50
  Speaker 6: a project you just you know, try to get a
• 11:52
  Speaker 6: feeling for what the customer has.
• 11:57
  Speaker 5: But yeah, I mean second phase would be.
• 11:59
  Speaker 6: Prepare phase where it gets a little bit more detailed.
• 12:03
  Speaker 6: This is usually based on the goal to define a scope.
• 12:08
  Speaker 6: And if you want to have a scope, you need
• 12:09
  Speaker 6: to have the s is data prepared and you need
• 12:12
  Speaker 6: to define at least the way or the goal that
• 12:17
  Speaker 6: you want to achieve for your warehouse. Here also again
• 12:24
  Speaker 6: we can use the possibilities of sapsic Naviga to get
• 12:29
  Speaker 6: data but also start and model data in sapsgnawvio.
• 12:36
  Speaker 3: So can I imagine it like I just I have
• 12:38
  Speaker 3: all this data and I just kind of push a
• 12:40
  Speaker 3: button and then the model is created.
• 12:42
  Speaker 5: For me or kind of. That's like at least the
• 12:46
  Speaker 5: first step.
• 12:47
  Speaker 6: So usually you know when you do that, when you
• 12:49
  Speaker 6: get the data from signavio, and then you can create
• 12:52
  Speaker 6: process flows documentation in signavio.
• 12:56
  Speaker 5: It will be a good start.
• 12:59
  Speaker 6: But you know there's always changes or process specifics that
• 13:04
  Speaker 6: you cannot see in the system. So what you would
• 13:07
  Speaker 6: have to do is take these processes and then you know,
• 13:10
  Speaker 6: detail them in interviews with customers.
• 13:13
  Speaker 3: Right, because I'm only seeing the traces and the system,
• 13:18
  Speaker 3: and I'm not seeing anything that physically happens or who
• 13:23
  Speaker 3: does it or when is it done?
• 13:26
  Speaker 6: Okay, you know, the system is especially if you come
• 13:29
  Speaker 6: from a legacy.
• 13:31
  Speaker 5: System, what is in the system is one thing and.
• 13:34
  Speaker 6: Then what actually happens physically in reality is a different thing.
• 13:38
  Speaker 6: So this is why you have to check them moving
• 13:43
  Speaker 6: on in our project faces would be the explore phase
• 13:46
  Speaker 6: where we are moving on from a scope and prepared
• 13:50
  Speaker 6: definition to really define the two B processes in detail.
• 13:56
  Speaker 6: Here again, we can use the s IS processes that
• 13:58
  Speaker 6: we created earlier as a baseline for you know, how
• 14:03
  Speaker 6: the warehouse, how the processes in the warehouse are going
• 14:05
  Speaker 6: to look in the future. And then as a second step,
• 14:09
  Speaker 6: we would.
• 14:10
  Speaker 5: Model these two B processes.
• 14:12
  Speaker 6: And usually what we like to do when we do
• 14:16
  Speaker 6: WM projects, especially for form projects and warehouses, we don't
• 14:22
  Speaker 6: just you know, create a to be process and then
• 14:25
  Speaker 6: say all right, that's the it concept, that's where we
• 14:27
  Speaker 6: want to go. We use like a last step in
• 14:31
  Speaker 6: the explore phase too, basically break our own design, you know, soundest, Yeah,
• 14:39
  Speaker 6: we basically try to find way too. You know, we
• 14:42
  Speaker 6: had ideas, we had a design, but you cannot really
• 14:45
  Speaker 6: be sure that your design works if you you know, don't.
• 14:49
  Speaker 5: Try to break it in the end. Okay, So you're
• 14:53
  Speaker 5: you know.
• 14:54
  Speaker 3: Basically it's kind of you challenge it or you test it.
• 14:56
  Speaker 6: Okay, yes, okay, I see you played Devil's Advocate and
• 14:59
  Speaker 6: then just you know, try to be more safe and
• 15:02
  Speaker 6: maybe change some things that you designed. In the beginning,
• 15:05
  Speaker 6: and that might have changed when you came to the
• 15:08
  Speaker 6: end of the design.
• 15:09
  Speaker 3: Okay, reminds me of system testing, and then you you
• 15:13
  Speaker 3: enter all kinds of weird stuff that you shouldn't be
• 15:16
  Speaker 3: enter and see what happens.
• 15:18
  Speaker 6: Exactly morey on a theory level. So but yeah, it's
• 15:22
  Speaker 6: something similar, Okay, I understood. Yeah, And then I think,
• 15:27
  Speaker 6: you know, when we have this discover, prepare, and explore,
• 15:31
  Speaker 6: you are, like with getting data and modeling data, you
• 15:34
  Speaker 6: are you have a good baseline for the next phase,
• 15:38
  Speaker 6: which is the realized face. Where As the name suggests,
• 15:41
  Speaker 6: we realize what we designed earlier and implement the solution
• 15:46
  Speaker 6: in the system, customizing of different storage types, the overall
• 15:50
  Speaker 6: warehouse layout, different process steps, and then also customer or
• 15:54
  Speaker 6: custom developments for specific needs of the warehouse. Now, when
• 15:59
  Speaker 6: you do that in an WM project, what always happens
• 16:03
  Speaker 6: is that when the customer can actually you know, get
• 16:07
  Speaker 6: a look and feel for the system and do small
• 16:10
  Speaker 6: functional tests or we do small functional tests, we often
• 16:14
  Speaker 6: realize that at this stage there will be changes to
• 16:18
  Speaker 6: the original design. Because designers on a theoretical level and
• 16:22
  Speaker 6: then you actually see it in the system. Sometimes you know,
• 16:25
  Speaker 6: that's not coherent. So what we need here from SPC
• 16:31
  Speaker 6: NOWVIO is a way to get all of these changes
• 16:34
  Speaker 6: back into the original design where you know the different
• 16:39
  Speaker 6: modules of SPCC now you can help us to achieve
• 16:42
  Speaker 6: that goal faster and more easy. Okay, well, I think
• 16:45
  Speaker 6: from a discovered to realize point, that's about it. In
• 16:49
  Speaker 6: the last two phases, sapsing now you can help, but
• 16:52
  Speaker 6: it's not that strong. The last two phases would be
• 16:54
  Speaker 6: deployed where we have usually like user acceptance tests where
• 17:00
  Speaker 6: we prepare the goal life and you know, if you
• 17:04
  Speaker 6: have like automation, you also try to do system integration
• 17:07
  Speaker 6: testing where you you know, combine different systems together and
• 17:13
  Speaker 6: then you know, once you have the final confirmation that
• 17:17
  Speaker 6: the system works as expected, you you know, let the
• 17:21
  Speaker 6: warehouse become reality and have the goal life, which would
• 17:24
  Speaker 6: be the last phase to run phase where we have
• 17:27
  Speaker 6: the go life and then also a small goal life
• 17:29
  Speaker 6: support phase afterwards for two weeks for example. And yeah,
• 17:34
  Speaker 6: as I said, in these two phases, we usually see
• 17:38
  Speaker 6: the advantages of sapsing now vi're from the earlier stages
• 17:42
  Speaker 6: because if you try to do user acceptance test or
• 17:46
  Speaker 6: even a goal life training you know, for your users,
• 17:49
  Speaker 6: it gets much more or much more efficient and easy
• 17:53
  Speaker 6: if you have a proper documentation, if you build your
• 17:55
  Speaker 6: solution on existing data, and you can actually you.
• 17:59
  Speaker 3: Know, benefit from all that has been previously created. And okay,
• 18:05
  Speaker 3: I see, okay, very interesting.
• 18:08
  Speaker 6: And that's I mean, that would show a typical WM
• 18:12
  Speaker 6: project and the you know, the possibilities that you have
• 18:16
  Speaker 6: with spz Navia for these and I think it is
• 18:19
  Speaker 6: a good use case to show and explain customers on
• 18:25
  Speaker 6: how they can get advantages out of SPC.
• 18:28
  Speaker 3: Yeah, thank you very much. This was a very detailed
• 18:30
  Speaker 3: description of all the phases and I think it is
• 18:33
  Speaker 3: now this was this was great so much for the
• 18:37
  Speaker 3: implementation of it and using Zignavio. But we also have
• 18:41
  Speaker 3: another use case which I think is just as interesting
• 18:45
  Speaker 3: for our customers because this once you have it up
• 18:49
  Speaker 3: and running, you're not necessarily done yet.
• 18:53
  Speaker 1: Right.
• 18:54
  Speaker 3: You brought the example of the e w M health Check.
• 18:59
  Speaker 3: I really like this example and the name of it.
• 19:03
  Speaker 3: So yeah, let's talk about the health check.
• 19:06
  Speaker 5: Sure.
• 19:08
  Speaker 6: So yeah, as you said, we have like a spot
• 19:13
  Speaker 6: consulting solution that we call the EOBM Warehouse health Check
• 19:17
  Speaker 6: and same you know, as we talked before, same as
• 19:20
  Speaker 6: going to a doctor. You go to a doctor if
• 19:23
  Speaker 6: either you feel pain, if something goes really wrong, or
• 19:27
  Speaker 6: as we you know, usually suggest you go to the
• 19:30
  Speaker 6: doctor on a regular basis for a check exactly to
• 19:35
  Speaker 6: be sure that nothing happened.
• 19:36
  Speaker 5: You know. Now, if we, you know, put that to.
• 19:42
  Speaker 6: The concept of warehouses or EOBM, you would have, for example,
• 19:47
  Speaker 6: a project that ended goal life is done, and now
• 19:52
  Speaker 6: you want to be sure and identify if the expected
• 19:55
  Speaker 6: goals were achieved. So the warehouse actually does what you want.
• 20:00
  Speaker 6: It creates the numbers that you want to have and
• 20:03
  Speaker 6: everything works as expected, and whether.
• 20:06
  Speaker 3: You follow the standard process just as you as you
• 20:11
  Speaker 3: imagined you.
• 20:11
  Speaker 6: Would exactly if we as a consultancy together with the partner,
• 20:17
  Speaker 6: that everything the right way, let's say it like that,
• 20:20
  Speaker 6: and as I said, that makes sense, same as a
• 20:22
  Speaker 6: doctor if something is not right and if everything seems
• 20:26
  Speaker 6: fine and you just want to get a confirmation that
• 20:29
  Speaker 6: it is fine.
• 20:31
  Speaker 3: But it would also make sense. Let's say if your
• 20:33
  Speaker 3: your business changes or you're I don't know, out of
• 20:37
  Speaker 3: a sudden, you're shipping way more e commerce orders and yeah,
• 20:44
  Speaker 3: your your your volumes are are different, et cetera. You
• 20:48
  Speaker 3: could use this to make sure that everything is still
• 20:52
  Speaker 3: set up in the best way.
• 20:56
  Speaker 6: I mean, if you know, if if a company grows,
• 20:58
  Speaker 6: they say, somehow have to you know, I have to
• 21:00
  Speaker 6: check that everything, every process that they created in the
• 21:02
  Speaker 6: warehouse still works as expected with the new volume and data.
• 21:06
  Speaker 5: So yeah, good point.
• 21:07
  Speaker 3: Yeah right, I like this. So how often should you
• 21:10
  Speaker 3: go to the doctor?
• 21:11
  Speaker 6: Well, let's not use this example because I'm not a doctor.
• 21:17
  Speaker 6: Usually what we well suggest this depends on what you
• 21:22
  Speaker 6: did before. If you had a big project before, try
• 21:26
  Speaker 6: and do it maybe six months even ten months after
• 21:29
  Speaker 6: implementation was completed. If you're already running a warehouse for
• 21:34
  Speaker 6: a longer time, you know, definitely if you see something
• 21:37
  Speaker 6: goes wrong or on a regular basis, maybe once every
• 21:43
  Speaker 6: two years. Yeah, this is what we usually suggest to customers.
• 21:48
  Speaker 3: Okay, thank you very much for this. Yeah, thank you,
• 21:52
  Speaker 3: detailed description and I think it was very useful.
• 21:56
  Speaker 5: Happy to help.
• 21:57
  Speaker 3: Let's let's see how many customers as we can convince
• 22:02
  Speaker 3: to to do a health check. And yes, good luck
• 22:06
  Speaker 3: in the future. And I'm very I'm looking forward to
• 22:09
  Speaker 3: speaking about any use cases and references and spaghetti plates
• 22:15
  Speaker 3: that you untangled. Where you made the process look lean
• 22:19
  Speaker 3: and clean again.
• 22:20
  Speaker 5: Yeah.
• 22:22
  Speaker 3: So, now that we learned about the theoretical approach and
• 22:25
  Speaker 3: the different steps that you that you go through during
• 22:28
  Speaker 3: this process, where do you see the biggest challenges and
• 22:31
  Speaker 3: the biddle the biggest hurdles that you need to overcome
• 22:36
  Speaker 3: in your projects.
• 22:39
  Speaker 6: Well, if you look at reality, you know, at e
• 22:41
  Speaker 6: WM project or implementation projects, as I said in the beginning,
• 22:45
  Speaker 6: the problems that we can solve with s a PC.
• 22:50
  Speaker 6: Now you you know, the customers are also we usually
• 22:54
  Speaker 6: you know, don't don't focus on these on these problems.
• 22:58
  Speaker 6: It would be things like the data that you get
• 23:02
  Speaker 6: from either the customer or the system that is always
• 23:05
  Speaker 6: you know, problematic because a lot of the time, the
• 23:11
  Speaker 6: the timelines and deadlines in a project are tight. So
• 23:16
  Speaker 6: if you need to prepare information, or if you need
• 23:19
  Speaker 6: to get information as a customer from your colleagues and
• 23:22
  Speaker 6: so on, and you're running low on time you hit
• 23:26
  Speaker 6: a deadline, then at some point you don't really focus
• 23:31
  Speaker 6: on good results of that information anymore. So you know,
• 23:35
  Speaker 6: just you know, be quick about it, get some information,
• 23:38
  Speaker 6: just push it over to the consultancy and then we're good.
• 23:41
  Speaker 6: We as a consultancy base our whole design on the
• 23:43
  Speaker 6: information that we get.
• 23:44
  Speaker 3: So we actually need good exact quality of data otherwise
• 23:48
  Speaker 3: it makes perfect sense, right, I mean, this is.
• 23:51
  Speaker 6: Why it makes sense to focus on this topic and
• 23:54
  Speaker 6: you know, get support from signal early on and yeah,
• 24:00
  Speaker 6: but then basically what we get from that data, what
• 24:02
  Speaker 6: we create as a result, documentation is you know, I
• 24:06
  Speaker 6: think a lot of people who have done SEP projects
• 24:09
  Speaker 6: in every module can agree is also, you know, a
• 24:13
  Speaker 6: thing that I think projects should focus on more in
• 24:17
  Speaker 6: the future, because documentation is the baseline for a lot
• 24:23
  Speaker 6: of phaces and things that you do in a project.
• 24:25
  Speaker 6: Let it be testing, let it be training, or just
• 24:28
  Speaker 6: you know, in general, if you want to find something,
• 24:30
  Speaker 6: find some information about the development, you need a good documentation.
• 24:34
  Speaker 6: And usually without SAPSIC, Novio customers know they have to
• 24:40
  Speaker 6: document and that's it.
• 24:42
  Speaker 5: You know.
• 24:43
  Speaker 6: We try to help them in the beginning and try
• 24:45
  Speaker 6: to set up a strategy for documentation, but there's not
• 24:50
  Speaker 6: really a focus on it. And if you use SAPSIC
• 24:53
  Speaker 6: now you don't really need to focus on it because
• 24:55
  Speaker 6: the system does it for you and it's a great
• 24:57
  Speaker 6: baseline for everything you know that comes afterwards. So these
• 25:01
  Speaker 6: two things you know, are in my opinion, problems that
• 25:05
  Speaker 6: do occur in every project, but which need definitely need
• 25:09
  Speaker 6: more focus.
• 25:11
  Speaker 3: Okay, so what do you think are typical challenges when
• 25:14
  Speaker 3: you first start a project and you dive into the
• 25:17
  Speaker 3: process analysis.
• 25:18
  Speaker 4: And that's a very good question because actually I had
• 25:23
  Speaker 4: that one in one of my last projects, because, like usually,
• 25:28
  Speaker 4: the main issue is that when when doing a Signalire project,
• 25:31
  Speaker 4: it sounds a lot like a business topic because you
• 25:33
  Speaker 4: have your processes, you want to model them, you want
• 25:35
  Speaker 4: to put put your center of excellence, you want to
• 25:37
  Speaker 4: build that up. But for the process analysis, when it's
• 25:41
  Speaker 4: a it's a data topic, right, you need to invoive
• 25:44
  Speaker 4: it very early. And we had to issue that. It
• 25:48
  Speaker 4: was like the last person to get the information. Okay,
• 25:52
  Speaker 4: we want to install new features here, we need an extractor.
• 25:56
  Speaker 4: That extractor needs to be connected to our ECC, which
• 25:58
  Speaker 4: raised a lot of red flags. They were like, we
• 26:01
  Speaker 4: have to we have to send tickets, we have to
• 26:05
  Speaker 4: build servers, we have to install things. So you need
• 26:09
  Speaker 4: to really reach out to it to include them early,
• 26:13
  Speaker 4: very very early, to.
• 26:16
  Speaker 3: Let them know about the technical needs that you have
• 26:19
  Speaker 3: exactly exactly.
• 26:21
  Speaker 4: Then one of the issues. It depends really on the
• 26:25
  Speaker 4: age of the system. Like we had a customer who's
• 26:29
  Speaker 4: in a pre phase four AS four, Like they wanted
• 26:32
  Speaker 4: to understand what are they doing currently and where do
• 26:34
  Speaker 4: they need to improve before they can start the transformation.
• 26:38
  Speaker 4: So they had an ECC. ECC is okay, but that
• 26:41
  Speaker 4: ECC was running on an Oracle database, which is like
• 26:45
  Speaker 4: the last update they installed was ten years ago. The
• 26:50
  Speaker 4: data extraction for process intelligence runs on ESQL scripts. The
• 26:55
  Speaker 4: Oracle database did not like Western Acher with the ESQUAL scripts,
• 27:01
  Speaker 4: like they destroyed it, and the extraction scripts, which are
• 27:06
  Speaker 4: supposed to run for like three hours, suddenly took four days.
• 27:10
  Speaker 5: Oh per table.
• 27:12
  Speaker 3: And now we're talking about timelines again.
• 27:14
  Speaker 5: Now we're talking time exactly.
• 27:16
  Speaker 3: Okay.
• 27:17
  Speaker 4: In the usual order to cash, you were looking at
• 27:20
  Speaker 4: like twenty tables with big your your sales ordered tables,
• 27:25
  Speaker 4: and they take forever. And if you suddenly want extractions
• 27:30
  Speaker 4: running for like fifteen seventeen days and you have your
• 27:34
  Speaker 4: workshop scheduled, your ESS's workshops in like three weeks, you
• 27:38
  Speaker 4: start to.
• 27:38
  Speaker 3: Sweat, Okay, So you have to pretty much take into
• 27:42
  Speaker 3: consideration where you're pulling data from and kind of incorporate
• 27:48
  Speaker 3: this into the timeline that there could be also technical
• 27:51
  Speaker 3: struggles that I would not make it as easy as
• 27:55
  Speaker 3: it sounds when we just talked about.
• 27:57
  Speaker 4: This exactly and ever since then, I started as the
• 28:00
  Speaker 4: customers what their database is running on? Okay, I want
• 28:03
  Speaker 4: to prepare them. If it's OURCA, maybe schedule four weeks longer.
• 28:08
  Speaker 3: Good, that's good insights here inside haha intelligence. Yeah, thanks
• 28:15
  Speaker 3: for sharing. You're welcome, all right, Well, thank you very much, Philip,
• 28:20
  Speaker 3: Thank you very much, Ben for joining me in this
• 28:22
  Speaker 3: podcast here. I really enjoyed this. I'm looking forward to
• 28:27
  Speaker 3: another one. Thank you very much for listening, Thanks for
• 28:31
  Speaker 3: watching this, and talk to you soon.
• 28:38
  Speaker 2: That brings us to the end of this episode. Some
• 28:41
  Speaker 2: great insights today into warehouse process optimization. Thank you so
• 28:46
  Speaker 2: much to Christina and our guests from Westernoker for sharing
• 28:50
  Speaker 2: their amazing insights from the show floor at Logimat this year.
• 28:53
  Speaker 2: I'm sure there are many listeners out there who found
• 28:56
  Speaker 2: this discussion hugely beneficial. If you have a suggestion for
• 29:01
  Speaker 2: a topic, or I would like to be a guest
• 29:02
  Speaker 2: on the show, we'd love to hear from you. Contact
• 29:04
  Speaker 2: me at podcast at mebok dot com at any time.
• 29:08
  Speaker 2: As always, Thank you for listening to Speaking of Supply Chain.
• 29:11
  Speaker 2: If you've enjoyed our show, please rate and review us
• 29:13
  Speaker 2: on whichever podcast platform you prefer. We're on Apple Podcasts, Spotify,
• 29:18
  Speaker 2: and Apple Music, and be sure to tune in next time.
• 29:27
  Speaker 1: You've been listening to Speaking of Supply Chain, a meboch podcast,
• 29:30
  Speaker 1: keep connected with us by subscribing to the show in
• 29:33
  Speaker 1: your favorite podcast player. If you like what you've heard, please.
• 29:36
  Speaker 5: Rate the show.
• 29:37
  Speaker 1: That helps us to keep delivering the latest in supply
• 29:39
  Speaker 1: chain information. Thanks for listening. Until next time.