Checklist for Splitting Models

(((

In this microlearning, we'll explore when it might be beneficial for an organization to split its eMagiz models into multiple, more manageable parts. To help you determine if this approach is right for your situation, we’ve provided a checklist that covers key considerations, such as system grouping, the number of critical processes, and the complexity of monitoring and managing your models. By evaluating these factors, you can make an informed decision on whether to maintain a single model or move towards a multi-model environment.

5

6

Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].

7

8

== 1. Prerequisites ==

9

10

* Intermediate knowledge of the eMagiz platform

11

12

== 2. Key concepts ==

13

14

In some cases, it can be useful for organizations to have multiple eMagiz models. More about such a multi-model environment is explained [[here>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-explained.WebHome||target="blank"]].

15

This microlearning contains a checklist with points that indicate when it may be useful to split models.

16

17

== 3. Splitting of models checklist ==

18

19

* **1. Can systems in your model be grouped?**

20

//Check in your model whether there are evidently groups of systems whereby the interaction is limited to only these systems. For example, are these finance and transport management business processes into a single model? Or can you categorize systems per business department?//

21

** No, no categorizations of systems can be made

22

** Not sure whether systems can be categorized

23

** Yes, several categorizations of systems can be made

24

* **2. What is the number of systems in your model?**

25

//The number of systems should represent the total number of systems that are present in your model. A high number of systems could indicate a situation where business processes are mixed and the interdependency of systems becomes large.//

** 0-40

** 40-80

** >80

* **3. What is the number of critical processes in your model?**

30

//A critical process is a complete set of flows that interact jointly in your model and which is deemed critical for business continuation of the client. Not that the number of critical streams is dependent on the size of an organization. Critical streams should be recognized as critical by the client.//

** 1

** 2-4

** >4

* **4. How many business owners are responsible for your model?**

35

//Business owners are the people that are responsible for the functionality of your model. These business owners are not direct users of the eMagiz platform but are more the ones that own the business process in the client organization. More business owner can indicate more diverging priorities, different release schedules, etc.//

** 1

** 2-4

** >4

* **5. How much time is involved in the daily monitoring of your model?**

40

//Daily monitoring concerns checking upon the functionality of your system, e.g. checking for errors. It does not include the time it takes to resolve those errors. More errors spread over many systems in the integration landscape means that specific domain knowledge is required for eMagiz users.//

41

** 10-15 minutes per day

42

** >30 minutes per day

43

** >60 minutes per day

44

* **6. Is there a rhytm in the number of deployments that you have per sprint?**

45

//A release cycle is the sum of stages of development of a model ranging from its initial development to its release.//

46

** Yes, there is a fixed rhythm including hotfixes

47

** Yes, there is a fixed rhythm

48

** No, there is no rhythm at all

49

* **7. Do you experience many delays in delivery of new and modified flows due to external and internal dependencies?**

50

//External and internal dependencies concern the communication with developers or stakeholders of the model. For example, do you have to wait a lot for a response of a developer or stakeholder before you can continue working on your model?//

51

** Not really

52

** It's increasing in the last 2 months

53

** Basically a daily discussion and issue

54

* **8. Is there a good balance of time spent on technical debt versus time spent on functionalities within your sprint?**

55

//Technical debt represents additional rework that needs to be done.//

56

** About 20/80 balance

57

** About 10/90 balance

58

** There is no balance

59

* **9. Do you have insight in your production incidents?**

60

//Production incidents are problems in your model that negatively impact the business.//

61

** Yes, it is clear what production incidents there are and I have control over them

62

** Yes, it is clear what production incidents there are but I do not have control over them

63

** No, it is not clear what production incidents there are and I do not have control over them

64

65

== 4. Key takeaways ==

66

67

Several key points can be used to indicate whether it is useful to split models in eMagiz.

68

69

== 5. Suggested Additional Readings ==

70

71

* [[Fundamentals (Menu)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]

72

** [[Multi-Model Explained (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-explained.WebHome||target="blank"]]

73

** [[Multi-Model Best Practices (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-best-practice.WebHome||target="blank"]]

74

* [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]]

75

** [[Data Handling (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.WebHome||target="blank"]]

76

*** [[Communication Between Models (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-communication-between-models||target="blank"]]

77

* [[Documentation (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=multi-model||target="blank"]]

)))

(((

)))

author	version	line-number	content
		1	{{container}}
		2	{{container layoutStyle="columns"}}
		3	(((
		4	In this microlearning, we'll explore when it might be beneficial for an organization to split its eMagiz models into multiple, more manageable parts. To help you determine if this approach is right for your situation, we’ve provided a checklist that covers key considerations, such as system grouping, the number of critical processes, and the complexity of monitoring and managing your models. By evaluating these factors, you can make an informed decision on whether to maintain a single model or move towards a multi-model environment.
		5
		6	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
		7
		8	== 1. Prerequisites ==
		9
		10	* Intermediate knowledge of the eMagiz platform
		11
		12	== 2. Key concepts ==
		13
		14	In some cases, it can be useful for organizations to have multiple eMagiz models. More about such a multi-model environment is explained [[here>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-explained.WebHome\|\|target="blank"]].
		15	This microlearning contains a checklist with points that indicate when it may be useful to split models.
		16
		17	== 3. Splitting of models checklist ==
		18
		19	* 1. Can systems in your model be grouped?
		20	//Check in your model whether there are evidently groups of systems whereby the interaction is limited to only these systems. For example, are these finance and transport management business processes into a single model? Or can you categorize systems per business department?//
		21	** No, no categorizations of systems can be made
		22	** Not sure whether systems can be categorized
		23	** Yes, several categorizations of systems can be made
		24	* 2. What is the number of systems in your model?
		25	//The number of systems should represent the total number of systems that are present in your model. A high number of systems could indicate a situation where business processes are mixed and the interdependency of systems becomes large.//
		26	** 0-40
		27	** 40-80
		28	** >80
		29	* 3. What is the number of critical processes in your model?
		30	//A critical process is a complete set of flows that interact jointly in your model and which is deemed critical for business continuation of the client. Not that the number of critical streams is dependent on the size of an organization. Critical streams should be recognized as critical by the client.//
		31	** 1
		32	** 2-4
		33	** >4
		34	* 4. How many business owners are responsible for your model?
		35	//Business owners are the people that are responsible for the functionality of your model. These business owners are not direct users of the eMagiz platform but are more the ones that own the business process in the client organization. More business owner can indicate more diverging priorities, different release schedules, etc.//
		36	** 1
		37	** 2-4
		38	** >4
		39	* 5. How much time is involved in the daily monitoring of your model?
		40	//Daily monitoring concerns checking upon the functionality of your system, e.g. checking for errors. It does not include the time it takes to resolve those errors. More errors spread over many systems in the integration landscape means that specific domain knowledge is required for eMagiz users.//
		41	** 10-15 minutes per day
		42	** >30 minutes per day
		43	** >60 minutes per day
		44	* 6. Is there a rhytm in the number of deployments that you have per sprint?
		45	//A release cycle is the sum of stages of development of a model ranging from its initial development to its release.//
		46	** Yes, there is a fixed rhythm including hotfixes
		47	** Yes, there is a fixed rhythm
		48	** No, there is no rhythm at all
		49	* 7. Do you experience many delays in delivery of new and modified flows due to external and internal dependencies?
		50	//External and internal dependencies concern the communication with developers or stakeholders of the model. For example, do you have to wait a lot for a response of a developer or stakeholder before you can continue working on your model?//
		51	** Not really
		52	** It's increasing in the last 2 months
		53	** Basically a daily discussion and issue
		54	* 8. Is there a good balance of time spent on technical debt versus time spent on functionalities within your sprint?
		55	//Technical debt represents additional rework that needs to be done.//
		56	** About 20/80 balance
		57	** About 10/90 balance
		58	** There is no balance
		59	* 9. Do you have insight in your production incidents?
		60	//Production incidents are problems in your model that negatively impact the business.//
		61	** Yes, it is clear what production incidents there are and I have control over them
		62	** Yes, it is clear what production incidents there are but I do not have control over them
		63	** No, it is not clear what production incidents there are and I do not have control over them
		64
		65	== 4. Key takeaways ==
		66
		67	Several key points can be used to indicate whether it is useful to split models in eMagiz.
		68
		69	== 5. Suggested Additional Readings ==
		70
		71	* [[Fundamentals (Menu)>>doc:Main.eMagiz Academy.Fundamentals.WebHome\|\|target="blank"]]
		72	** [[Multi-Model Explained (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-explained.WebHome\|\|target="blank"]]
		73	** [[Multi-Model Best Practices (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-multi-model-best-practice.WebHome\|\|target="blank"]]
		74	* [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome\|\|target="blank"]]
		75	** [[Data Handling (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.WebHome\|\|target="blank"]]
		76	*** [[Communication Between Models (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-communication-between-models\|\|target="blank"]]
		77	* [[Documentation (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=multi-model\|\|target="blank"]]
		78	)))
		79
		80	(((
		81	{{toc/}}
		82	)))
		83	{{/container}}
		84	{{/container}}

Wiki source code of Checklist for Splitting Models

Navigation