Skip to Content

Changes for page Business Case

Last modified by Erik Bakker on 2023/05/01 10:59
From version 3.1
edited by eMagiz
on 2023/04/04 14:20
Change comment: There is no comment for this version
To version 7.1
edited by Eva Torken
on 2023/04/13 14:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -crashcourse-eventrstream-exercises-businesscase
1 +Business Case
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.etorken
Content
... ... @@ -1,4 +1,5 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
1 +{{container}}
2 +{{container layoutStyle="columns"}}(((
2 2  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.
3 3  
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
... ... @@ -7,6 +7,8 @@
7 7  
8 8  * Have read the business case as the first exercise
9 9  * Completed the previous microlearnings of this crash course
11 +* Access to integration model that has access to an Event Streaming license & deploy rights
12 +* Configured proper access to the training Event Broker - please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
10 10  
11 11  == 2. Exercise ==
12 12  To kickstart your journey into the eMagiz platform, we have selected a set of exercises linked to the Crash Course Platform course that will guide you through the platform in building and validating your first integration. To start things off, we will introduce the business case in this exercise that will be used to model out the correct solution in eMagiz.
... ... @@ -14,7 +14,8 @@
14 14  ===2.1 Business Case===
15 15  **Read and understand the following business case**
16 16  
17 -As eMagiz Co. we have a fleet of trucks 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. This to increase our efficiency in planning.
20 +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).
18 18  
19 19  
20 -)))((({{toc/}}))){{/container}}{{/container}}
23 +)))((({{toc/}}))){{/container}}
24 +{{/container}}