Skip to Content

Changes for page Business Case

Last modified by Erik Bakker on 2023/05/01 10:59
From version 4.1
edited by eMagiz
on 2023/04/04 14:21
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
Content
... ... @@ -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
10 +* Access to integration model that has access to an Event Streaming license & deploy rights
11 +* 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,12 +14,7 @@
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.
18 -Secondly, as eMagiz Co. we want to receive alerts in our control tower when a vehicle event of a certain type (i.e. Fueling) is triggered. This way we can link the event to a bank transaction within our control tower and see real time the fuel efficiency of our fleet.
19 -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. Ensure that the topic properties for the topic are configured correctly.
20 -As eMagiz Co. we want to filter our events based on the event type. If the event type is Fueling, we want to place an alert message on a topic for our control tower to consume. In other cases, we want to filter out the event.
21 -Additional business requirement is that we want to keep the alert retained for a period of 6 hours. During this time, we expect 600 messages at an average size of 1kb.
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).
22 22  
23 23  
24 -
25 25  )))((({{toc/}}))){{/container}}{{/container}}