ESPO in a Global Environment

[Dave B]

One of my clients will be expanding overseas this year and will have operations in several countries. Some business functions will be global while others will be local. Does anyone have any experience of using ESPO in a multi-country environment? Do you use one global instance of ESPO or multiple instances per country or region? What challenges have you faced? My client uses the SAAS version so we don't have access to the developer capabilities, but have extended the system considerably using the entity manager and workflows.

Thank you in advance for any advice

[shalmaxb]

Hi, either proceeding will have its pros and cons.

If you use one instance, which would e.g. change the necessary fields depending on the country, you will perhaps have alot of conditional configuration, perhaps also lots of fields, that you use for one country, but not for the other. It depends on the differences between the conditions in the respective countries and the amount of entities and fields you will have. So you should decide considering that. If there are few differences, I would prefer this scenario.
If there are lots off differences, in my opinion it would be better to have instances for each of the countries. But this is much more maintenance work and if you want to work with many data, that you will use globally, there could occurr the problem of non consistent data.

In genereal I would incline mor to the first solution, well thought it would be easier in the end.

[Dave B]

Thank you - yes, my inclination is to go for the single instance as we would like to keep things as aligned as possible across countries