Skip to main content

Hi Experts

One of our oil and gas clients is currently working exclusively with functional objects, without any serial objects in their system. However, they’re now interested in converting some of these objects into serial objects while preserving all past transactions linked to them. I’d like your expert feedback on the approach we're considering for this request and to know if any of these options should be reconsidered. We’re looking at around 40 objects, all of which include measurement details, PM actions, and WOs, but no financial transactions.

 

Here are my proposed options:

  • Create manual serial objects: Reuse the same functional object ID and migrate historical transactions from functional objects via DR script.
  • Scripted Conversion: Develop a script to directly convert functional objects to serial objects (uncertain about feasibility).
  • Migration Script: Use a comprehensive migration script to transfer data (though I feel this could be more complex than the above options, given the multiple scripts involved).

Please feel free to add any suggestions or alternatives you think would be effective.

Thanks in advance
Kushan Jayasinghe

Hi Kushan,

I might not be the best person to comment on the proposed options. However, I am interested to know the use case behind this. Could you please provide some more context into this customer requirement?

Thanks & Best Regards,

Pubudika

As a customer in the Oil & Gas industry, we're also currently in the implementation phase of IFS ERP. One of the challenges we encounter is the Functional/Serial Object concept. I'd like to expand on the use case mentioned by @Kushan Jayasinghe where we also have similar issue.

We have critical equipment like pumps that may undergo motor replacements (not from inventory to equipment, but from equipment to equipment). For example, if Motor of Pump A has a maintenance history of 10 entries and is subsequently installed in (moved to) Pump B for some reasons, its maintenance history should also be transferred to Pump B. Otherwise, even with the motor installed in Pump B (previously from Pump A), we'll still see the maintenance history of the old, dismantled motor. This can lead to issues with maintenance history traceability of motors.

If the motors are defined as Functional Equipment during implementation phase, then customer of @Kushan Jayasinghe must have faced the similar issues I think.

As a customer in the Oil & Gas industry, we're also currently in the implementation phase of IFS ERP. One of the challenges we encounter is the Functional/Serial Object concept. I'd like to expand on the use case mentioned by @Kushan Jayasinghe where we also have similar issue.

We have critical equipment like pumps that may undergo motor replacements (not from inventory to equipment, but from equipment to equipment). For example, if Motor of Pump A has a maintenance history of 10 entries and is subsequently installed in (moved to) Pump B for some reasons, its maintenance history should also be transferred to Pump B. Otherwise, even with the motor installed in Pump B (previously from Pump A), we'll still see the maintenance history of the old, dismantled motor. This can lead to issues with maintenance history traceability of motors.

If the motors are defined as Functional Equipment during implementation phase, then customer of @Kushan Jayasinghe must have faced the similar issues I think.

Exactly, that's the primary issue my customer is experiencing. During the implementation phase, all objects were defined as functional objects. It was only much later, after encountering the challenges mentioned, that the customer realized this approach wasn't suitable.

Reply


Terms & ConditionsCookie settings