yes sir. per base maximo design, any single Location record can be attached to multiple maximo systems.

If a tag no is entered into the location, how can it be attached to multiple plant systems? One tag can only belong to one system at any one time. So I don't get your idea here.

If a tag no is entered into the location, how can it be attached to multiple plant systems? One tag can only belong to one system at any one time?
- - - - - - - -
The wording above must first be dissected so that we are clear.

Tag no == is a serialized asset

Nameplate data == is on a serialized asset

Location == is a pedestal or foundation or room or place for the asset

Operations refers to this particular asset/equipment on the foundation
as FW#1 -- but this really is a location per maximo termiology.

The maximo asset can only belong to one system at a time.

But a maximo location can belong to multiple systems. This is std maximo functionality.

Even a maximo location can belong to multiple systems (can be done ITwise), this doesn't mean physically the asset belongs and functions to multiple systems. Pls give examples where this functionality is useful.

Do you mean a pump can belong multilple systems ike seawater system, cooling water system, firefighting system, etc simultanouesly?

I still don't understand the idea.

A good system identifier could be the P&ID number for a system, which by design contains many different asset classes. This could be a good way to use downtime effectively by seeing how many assets within that system - P&ID drawing number - with active work requests/work orders exist in the system. But, with a good lacation hierarchy, that should also do the same thing.