Moving of a serial objects between sites/companies while maintaining same object ID/serial No.
Hi all,
We have a Client with IFS App10 implemented for a single Site that uses Rental Contracts. Now other Sites are being created for the same Company and there is a need to distribute the Serial Objects to the new Sites.
The Core Application is incapable of handling moving of a serial objects between sites/companies while maintaining same object ID/serial No. However, this is a customer request that we must fulfill.
Changing the site may affect functional flows and analysis data such as financial transactions, material transactions, PM actions, WO and Historical WO.
There are some limitations to overcome when delivering a solution for this issue such as, Since the site is a crucial part of the key for an object and its ownership, changing it might loss the tracking information of a serial object.
I would like to know if anyone has already created a solution through Events or even Customization and can share this solution because the Client needs an urgent solution and a customization requires more time than is available.
Best Regards
Page 1 / 1
Hello @E.Mamcasz - This has been a known concern Core APP10 application. It surely has the Serial Move capability, however with some limitations. Object ID & Site combination, being the logical keys, Object Site field cannot be changed during the move. Hence latest/true site is not reflected in the Object Site field once it is moved.
For example, If we have an equipment structure (Parent-Child) like below in Site 1
Object 1, Site 1, --- > Object 11, Site 1,
Object 11 can be moved to the Parent Object 2 in Site2 (of the same Company.)
Object2, Site 2, ---- > Object 11, Site 1
This is the problem as we see it. Even though the Object 11 is moved as a child of Object2, Site 2, its site value is still kept as Site 1. Hower all reference information is intact (not missed) given that Keys are unchanged.
Could this be an acceptable workaround by the customer, given the urgency?
NOTE:
In IFS Cloud (from 23R1 onwards) in order to get rid of the restrictions, we have introduced a new Equipment Object Key (Equipment Object Sequence) instead Object ID & Site. That solution provided a good flexibility of moving serials between different sites/companies.
Hope this would help.
Hello @Mayura Wasantha
Exactly, that's the point. The Client needs the Site of the moved Object to be the same in the new location, in your example Site 2 for Object 11.
Applying the IFS Cloud solution through a customization for IFS App10 could be a solution. However, this involves everything related to the Object: Active Work Orders, Work Tasks, OS History, Maintenance Plans, Object Measures and others that need to be mapped.
Best regards
Thanks @E.Mamcasz , good to be on the same page.
The Cloud solution design has considered all related information around the object. For example,
There is a prerequisite to Close all Work Tasks before a moving or shipping.
A new PM Revision(s) is allowed to create in the new Site. (maintaining same Maintenance Plans)
Latest measurements at the point of move/ship is done, Historical measurements are carried through.
Work History of the previous site(s) is visible to new site users.
If you are interested, the following activity diagram along with all its descriptions will give good amount of information (pre-requisites, system effects) around this.
@Frank Sveen - I have a vague memory of you trying to resolve this one of our customers in APP10. Do you have any thoughts, please add,
Hi @Mayura Wasantha
The Client has chosen to customize a solution similar to IFS Cloud. So, we have a long journey ahead of us.
.