This requirement came from some implementations like the Noble project for the US Navy needing the tools to have structures which you can’t do with the new tool/equipment functionality. I still think you should be able to connection functional equipment objects as well.
Thanks for your answer but it does not respond entirely 
Fisrt I think we can have a structure with the resource structure, it depends on what are needs in kind of structure… If you want to have it for costs well I understand. That’s always difficul to let customers understand why at one moment we speak about parts, another one then objects and o third one tools…
Nothing better letting them lost
This can’t be resolved with a resource structure. I’m sure I’ve been in front of more customers than you have doing EAM and yeah, this wasn’t thought through when they made the change...just tell them the truth.
Hi,
I agree, in the maintenance context both Serial Object and Tool are same class citizens. Both are available for preventive (PM, PM Programs, measurements) and corrective (WO) maintenance activities. In fact Serial Object had this from the beginning whilst “Tools” were enabled in APP9/APP10 tracks.
However, still the purpose of these 02 entities are different and that has never been changed even after 21R1. Serial Object is a site bound entity used in Asset Administration. It can be moved between different positions/sites by the requirement. Tools on the other. ideally site independent (or multi site) entity that can be used in work planning and execution.
If you are thinking of the Serial Object -Tool connection that has been reintroduced from 21R2 release. This is to achieve specific business requirement explained below (It cannot be resolved by Resource Structures as mentioned by Jerry). Please read the back ground below,
●In work planning and execution, different types of Tools are used. When it comes to the service industry, it's usually a single tool with a simple purpose such as meters, scopes, and gauges. However, in heavy maintenance industries, the tools required can be complex with many different sub assembly levels. These are commonly termed as ‘Support Equipment’.
●The Tool/Equipment business object is a Generic Resource in IFS Cloud that does not support building and maintaining sub-assembly levels.
●Hence, there is a reasonable need to provide a better solution to manage such ‘Support Equipment’ in order to build its sub assembly structure and maintain them.
New Connection enables the serial object to act as a place holder to reflect the Support Equipment sub-assemblies and thereby carry out maintenance on them.
I hope this would help you.
Hi @Mayura Wasantha thanks for this clear clarification. However as far I understannd even if a tool is multi site, then if we connect it to an object it becomes more restrictive to only a single site
Hi @Mayura Wasantha thanks for this clear clarification. However as far I understannd even if a tool is multi site, then if we connect it to an object it becomes more restrictive to only a single site
If a tool is multisite connected, regardless of the serial object connection it can be planned in other sites as well. When it comes to the execution, the serial object will have to move physically, which is a possibility from 22R1 onwards.
