Hello community,
the best practice in ServiceNow OT context is to define an Equipment Model in hierarchical representation fitting the needs of your Equipment. ISA 95 defines it as Site-Area-... and so on. By import or mapping, the CI's are then mapped to this model. From visibility point of view you can define access on site level which is always referring to Equipment Model records that have no parent.
In quite a few scenarios we got the request to restrict visibility on a lower level, for example someone is responsible for all CI's assigned/mapped to a certain area and not the complete site. ServiceNow does not include this feature out of the box. It is only possible on site level. Creating then this structure without the parent/child relations would fail the concept of an Equipment Model so that you have to work with ACL's.
Did someone encounter this problem/requirement? How was it solved? Am I overseeing another possibility? Thanks
