Extending Genome Administrative Control to Placed Equipment Objects

[DCIM_Support]

Currently in DCO you can add/remove User Permissions for Administrating the Genome Library; however once someone with base Asset Provisioning rights uses an object from the library, all fields for that placed object become editable leading to inconsistencies against what has been standardized (forced) within the Genome Library.

At a minimum, it would be nice if the Manufacturer and Model Name fields could be read-only once pulled from the Genome to reduce variations of equipment types in the database. It makes auditing, reporting, and life-cycle management challenging, as well as creates issues when syncing with outside configuration and asset repositories. 

At a maximum, it would be very nice if a Genome Library Administrator could chose at a global level which fields would be read-only vs. write for non-library administrators, once objects are pulled from the Genome Library. 

I know there are considerable complexities in this request, so I offer a glimpse into the administrative pain with the below graph showing the distribution of unique equipment types within my database vs. a count of their use. That long-tail is something we constantly have to control with 40+ end-users having write access.

(CID:90899545)

[DCIM_Support]

Hi Jeff,

Thank you very much for the insight into your challenges in Genome administration. There are some complexity as you describe, however we will take note of the request.

Just to be sure you mean that fields e.g. model name and manufacturer should be read-only also when added to the model it self

Meaning only editable by admins in Genome Library, Genomes and the model? 

(CID:90899559)

[DCIM_Support]

Correct, I believe you have captured it right. Admins of Genome Library would only be allowed to edit specific fields in either the Genome Library, Genomes, or the model. Extended that functionality beyond 'model name' and 'manufacturer' would be be very nice to have, but at a minimum locking those two fields is needed to help deal with asset management and data synchronization issues. -Jeff

(CID:90899614)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.