Changes for page Business case

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-crashcourse-apigw-exercises-businesscase
	1	+Business case

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.eMagiz
	1	+XWiki.etorken

Content

...	...	@@ -1,11 +1,12 @@
1		-{{container}}{{container layoutStyle="columns"}}(((
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 the Crash Course Platform Course. In the following exercises, we will guide you step by step through the platform so you can learn how to use it.
3		-
	1	+{{container}}
	2	+{{container layoutStyle="columns"}}(((
	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	4	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5	5
6	6	== 1. Prerequisites ==
7	7
8		-* None
	9	+* Read the following: ** [[API Gateway>>https://www.youtube.com/embed/oeXcppmaRzs||target="blank"]]
9	9
10	10	== 2. Exercise ==
11	11
...	...	@@ -15,29 +15,14 @@
15	15
16	16	**Read and understand the following business case**
17	17
18		-Transport INC is your typical medium-sized logistics provider fighting to stay ahead of the competition. To keep profits up, they are required to boost sales or reduce costs. While Transport INC is not a big player, it has a loyal customer base. However, it is precisely this customer base that is chewing up the operational budget, as many of the orders are still placed by phone. To reduce its costs, Transport INC sees an opportunity to integrate with its customer base and remove costly and error-prone phone orders.
	19	+As eMagiz Ltd. we want to directly receive & send information from/to an internal system responsible for the primary process. It concerns the OMS (Order Management system) that handles the Orders that are incoming from clients. eMagiz Ltd. has decide to expose API operation to their clients so that the message traffic is standardized and less manual intervention is required for the backoffice. See below for specifications.
	20	+
	21	+* OMS
	22	+ ** Retrieve carrier information. This information is relevant to understand what color the truck is on which the order is placed.
	23	+ ** Send order. Clients can directly submit orders to eMagiz Ltd. in a digital manner
19	19
20		-To reduce operational costs, Transport INC can implement a standard integration layer, which requires their customers to do a lot of implementation themselves. Besides, it also forces customers to provide orders in a predefined format, which means they may have to perform a transformation. A second option is to hire an integrator that will build a custom integration fitting precisely to the current needs of Transport INC. This option seems just right. However, it is very costly and will scale poorly in the future because any adaptions to the process of Transport INC will require new investments. That is why Transport INC choose the third option, eMagiz. eMagiz provides business engineers with the tools to build integrations that are scalable and easy to manage.
	25	+eMagiz Ltd. has two large clients that would start to use these operations. ACME requires the ability to submit orders, retrieve invoices and carriers. Street Smart requires access to all operations. Both clients can work with API keys for authentication purposes.
21	21
22		-After choosing for eMagiz, Transport INC started by taking up their requirements for their process. The process they currently have is that Customers can call the service desk of Transport INC to place an order. The service desk will input the order into their transport management system, where a planner can plan the order. After it has been planned, the customer is notified by phone that the order is planned.
23	23
24		-For this basic case, we want to ensure that the first part of this process is implemented in eMagiz correctly. With the first part, we mean automatically storing customer orders in the Transport Management System (TMS) of Transport INC. The following information about this process is given:
25		-
26		-“The first customer that Transport INC would like to integrate is CAPE. CAPE is one of their biggest customers and sends an average of 10-20 orders per day. CAPE is a company that sells its products in the local markets. So it only requires local milk runs. This means that their orders can be processed until noon each day.
27		-
28		-The orders are sent in real-time, requiring that eMagiz constantly check if new orders have been provided. Each order will be delivered separately, so no batch processes are required. Since CAPE sends out an average of 10-20 orders per day, the service manager of Transport INC has also determined that he would like to receive a notification when orders have not been provided over the last day at noon. Their orders are delivered in the form of XML messages. These orders can be put in a local folder. Using the eMagiz platform, these orders are picked up and sent to Transport INC, where they are sent to their back office transport management system.“
29		-
30		-
31		-== 3. Solution ==
32		-
33		-* Understand that the integration consists of two parts
34		-** Retrieve information from a folder on which CAPE places its orders
35		-** Provide input to the Transport Management System (TMS) of Transport Inc.
36		-
37		-* Before you continue please check out the following videos for some introduction into the various patterns of eMagiz
38		-** [[Messaging>>https://www.youtube.com/embed/41SK59S4GcY||target="blank"]]
39		-** [[API Gateway>>https://www.youtube.com/embed/oeXcppmaRzs||target="blank"]]
40		-** [[Event Streaming>>https://www.youtube.com/embed/H9e2zg78Pco||target="blank"]]
41		-
42		-
43		-)))((({{toc/}}))){{/container}}{{/container}}
	28	+)))((({{toc/}}))){{/container}}
	29	+{{/container}}