Skip to Content

Changes for page Business Case

Last modified by Erik Bakker on 2023/05/01 10:59
From version 8.1
edited by Erik Bakker
on 2023/05/01 10:59
Change comment: There is no comment for this version
To version 6.1
edited by eMagiz
on 2023/04/04 14:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Business Case
1 +crashcourse-eventrstream-exercises-businesscase
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Content
... ... @@ -1,5 +1,4 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}(((
1 +{{container}}{{container layoutStyle="columns"}}(((
3 3  With this exercise, we start our journey into the eMagiz platform. This exercise will explain the business case used throughout all exercises linked to this Crash Course. In the following exercises, we will guide you step by step through the platform so you can learn how to use it.
4 4  
5 5  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
... ... @@ -17,10 +17,7 @@
17 17  ===2.1 Business Case===
18 18  **Read and understand the following business case**
19 19  
20 -As Money Monkey Co. we have a fleet of trucks that hold board computers that continuously send out events. We want to utilize this information to steer our planning functionality. As a result we want something that can inform our planning system of the current status per vehicle. With this information the planners can optimize how our trucks filled with money transport it from and to locations across Europe. This will increase the efficiency of our planning solution based on all the different types of events that are processed by the system.
19 +As eMagiz Co. we have a fleet of trucks that hold board computers that continuously send out events. These events all have different types (i.e. Fueling, Driving, Waiting, Loading, Unloading, Off duty). We want to use those events to inform our planning system of the current status per vehicle in order to increase efficiency in planning. As eMagiz Co. we want to retain all vehicle events for 3 days. In this time period we expect to receive 15000 message per day at an average size of 1,35 kb per message (JSON).
21 21  
22 -We expect the following data traffic coming from our fleet of trucks in a three day period. In this time period we expect to receive 15000 message per day at an average size of 1,35 kb per message (JSON).
23 23  
24 -
25 -)))((({{toc/}}))){{/container}}
26 -{{/container}}
22 +)))((({{toc/}}))){{/container}}{{/container}}