What is the purpose of COE in HR Service Delivery?

[rutva]

What is the purpose of COE in HR Service Delivery?
Why do we need a COE based architecture and rather not have a structure without COE where in I have a case created on General Case table and categorized based on Topic Category and Topic Detail(refer screenshot attached).
Would like to understand the advantages of COE based architecture over non COE in terms of scalability, performance, visibility restrictions and costing in HR Service Delivery.

[rutva]

Hi Ajay

Thanks for your explanation. 

I have gone through the documentation link and videos provided, understood the functional concept of COE. But would like to know more from architectural perspective. Does COE model have any benefits on performance of the system? How scalable is the COE structure. Is it possible to add new COE. Because as per my conversation with Servicenow team , to add a new COE we need Servicenow intervention. 

As an alternative, we are planning to remove COE data model and keep just one General HR Case table(sn_hr_core_case) to which all the Topic Categories ,Topic Details and HR Services will be mapped. So just want to understand how feasible this alternate solution is in terms of scalability , performance and security. Will it have any impact on performance or data retrieval. 

Regards

Rutva

[Dsinghal]

But would like to know more from architectural perspective. Does COE model have any benefits on performance of the system?

The parent table is SN_HR_CORE_CASE. Each COE has a table of its own which is a chid of SN_HR_CORE_CASE. The way forward is totally dependent upon your requirements. - How many cases do you create every day / week / month? - Do you have to purge them regularly? - Do the various CoEs' map with your topic category / detail design? - Do you have a security requirement which can be delivered easily by using CoEs (case workers are divided by the CoE and should not see any other CoE cases?)

If the number is cases is huge, performance would certainly be better via CoEs as you get different tables for each CoE. 

How scalable is the COE structure. Is it possible to add new COE. Because as per my conversation with Servicenow team , to add a new COE we need Servicenow intervention. 

Adding new CoE should not be a problem. You can find various community posts on it. Whether you create them or ServiceNow depends on the competency of the inhouse team.

As an alternative, we are planning to remove COE data model and keep just one General HR Case table(sn_hr_core_case) to which all the Topic Categories ,Topic Details and HR Services will be mapped. So just want to understand how feasible this alternate solution is in terms of scalability , performance and security. Will it have any impact on performance or data retrieval. 

This should be fine if it meets your requirements. We use the same model, mainly as we do not have huge number of cases and our case workers work on all types of cases. We also purge them regularly, which prevents the case table from becoming too big to have any performance impact. I know of another big customer (~70000 employees) who do not use the CoE model either.