Multiple Object Schemas, why and when?

[Jule Helder]

Hi to the community,

I am currently starting to set up insight in JSM. Now I understood that it makes sense to split object schemas for example having one for each "topic": ITSM Schema, HR for employees and CRM Object Schema for customers and contracts.

What would you recommend in the following two situations:

- I am a softwarecompany, selling Software to my customers and we use JSM for customer service, is one object schema for all customers and contracts enough?

- I am a systemhouse, selling lots of hardware and software to many different companies, would it make sense to create an object schema per customer if the amount of sold hardware and customers with different locations gets to extensive?

Best regards,

Jule