Solutions for Linear Asset Management - Data Model for defining the non liner assets and associating them to the linear assets
In my earlier blogs I have explained the data model to define the linear assets as part of the linear asset management solution. Any network will have both linear assets and non linear assets. It is important to build the relationship between the linear asset network and non linear assets.
Every segment of linear asset of a network can have one or more non linear assets and in the same way every non linear asset can be share by more than one linear asset segments or networks. Such examples are train station (Junction) in the railway network, substations in case of electrical transmission lines, pump houses or storage tanks in water or gas pipe lines. In all these examples, the station is at a fixed location and will be shared by more than one asset network. It is important to build this relationship so that all assets of a region or location can effectively be planned for maintenance and apportion the costs over the networks of the assets.
In the previous blog we have see the various attributes that are required to define the linear assets. In the similar way non linear assets too requires a set of attributes to be defined to build the one to many (One non linear asset shared my many linear asset network) and many to one (many non linear assets can be associated with one linear asset network).
Let us refer to our own network picture with some non linear assets this time.
In this example, we have T1 to T5 are the terminals that are referred as Non linear assets. These terminals are either owned by one segment (in turn by a network) or shared by multiple segments of multiple segments. As part of the maintenance, of a network it is better to plan the maintenance of these terminals and associated assets. Sometimes as part of the maintenance of the location or region it is better to plan and carry the maintenance of all linear and non linear assets of that location.
In this blog we will list all the critical attributes that are required to define the non linear assets so that they can be integrated to linear asset networks.
Department
Shared Asset: Yes/No
Hosts multiple asset networks (Hub): Yes/No
Cost Sharing: Yes/No
Longitude of the asset:
Latitude of the asset:
| Non Linear Asset | Department | Shared Asset (Yes/No) | Hosts multiple asset networks (Yes/No) | Longitude of the asset | Latitude of the asset |
| T1 | Property Mgmt | No | No | 11.9.32 | 44.5.32 |
| T2 | Property Mgmt | Yes | Yes | 11.9.32 | 44.5.44 |
| T3 | Property Mgmt | Yes | Yes | 11.9.32 | 44.5.47 |
| T4 | Property Mgmt | Yes | Yes | 11.9.32 | 44.5.51 |
| T5 | Property Mgmt | yes | Yes | 11.9.39 | 44.5.51 |
The important consideration of the solution is to associate the non linear assets to a project and a task. It is much easy to recognise the costs and transfer the costs to the shared networks (linear assets).
This relationship will help us to consolidate the maintenance work and effective notification to the related assets.
We will see the linear assets maintenance algorithm in the next blog.
