Hi ​@Cindyhutchins 

As per my recollection this was developed in order to support a specific scenario for few customers who wanted move functional objects while updating the object level. Enabling this will allow you to have greater flexibility when moving functional objects where you can move a functional object into a new parent without considering its object level. In addition to that this will allow you to update the object level as part of the functional object move as well.

The con would be that after enabling this, object level definition will not enforce pre defined hierarchy levels for your equipment object structures so the object level would have less power to dictate where a functional object can be moved into as a child. (ex: System level functional object can be moved as a child to a parent object which is has the object level Subsystem)

Hi Cindy,

While I don’t have any insight to offer regarding this option in IFS, we came from a legacy system that did not enforce any object level hierarchy, so I was very intrigued when I saw this option. We didn’t have any issues with the freedom of hierarchy levels in our legacy system. With that said, we haven’t enabled the feature yet for similar reasons like you mentioned due to the warning of being unable to reverse the change. I am interested in any experiences you may come across with utilizing this feature!

Thanks,

Evan Edwards

Probably reason for somewhat of a scary message is once the object level validation is ignored at a point there is no way to enforce it again since the existing structures will already have objects that defy the object level hierarchy. Therefor its not possible to enable it again since that may break some functionalities in object movements :).

However as ​@eedwards mentioned if you are not fussy about maintaining functional structures aligned to a certain object level hierarchical order, enabling this option would provide greater freedom in functional object movements