Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« Oracle Documaker 12 - A feature rich product on the horizon | Main | Oracle Exadata and DataWarehousing Impact - Part II »

Solutions for Linear Asset Management - A Data Model for Definiing the Linear Assets

In my earlier Blog, I have detailed the challenges arising in Linear Asset Management and I like to highlight the possible out of the box or custom solutions to overcome these challenges. This blog primarily explains how a data model can be developed to define the network of linear assets and their attributes using Oracle EAM Asset group attributes.

The first most important challenge in Linear Asset Management is model the network with the linear assets. Linear assets are not specific to a point of geographic location. They have a definite length or area that requires defining with beginning and ending co-ordinates and other attributes. A network of the asset can be split into multiple segments and each segment has a definite start and end point. The end of one segment will be the start of the other part. This relationship will continue for all segments except the first and last part.
Network modelling can be divided into two parts. The first step is to assign the assets to a specific location on map (like Google maps) and secondly to build a network by connecting all such assets.  Defining a suitable data model is critical for establishing the asset network.
Oracle R12 (12.1.1 onwards) allows us to map each of the asset to geographical location on a map. The required setups can be obtained from Metalink Note 779351.1. The second part is to assign them to a network. This can partially be fulfilled by using the Parent child relation of assets where the whole network is defined as parent and each distinct part of the asset can be defined as the child(s) for the parent assembly. This is not a complete out of the box solution from Oracle EAM. In this case the customers may have to integrate these assets to an external application or opt for bespoke development. The bespoke development need to offer the ability to define the asset network, crossovers, dependencies, relationships etc., and once such relationship is established Oracle EAM can be used effectively for maintenance planning and execution of liner assets.
Let me explain how such a typical asset networking model will look like with a schematic diagram and the important characteristics of each segment to build the relationship with similar segments and intersections with other networks (Where other network cross over this network like a road network crosses the rail network).
The below is simple case of 3 networks that intersect at some segments, Cross over at other segments. This example shows how various attributes can be defined for various segments. Each network is a linear asset in this case.

 

Asset Network.jpg 

 

 

Important attributes of each segment can be
Length
Owned by: Network Name (Parent Asset)
Starting Point Latitude
Starting Point Longitude
Starting Point Type: Linear (Connects to the segment of own network) / Nodal (Connecting to Other networks
Ending Point Latitude
Ending Point Longitude
Ending Point Type: Linear (Connects to the segment of own network) / Nodal (Connecting to Other networks
Segment Category
Segment Type: Common / Individual
Approval required from Cross over network: Yes / No

This is a data model for a simple asset network using the asset group attributes. Depending upon the type of network it will be required to configure many attribute groups and define the attributes.

Segment Name Owned by: Network Name (Parent Asset) Magnitude
(Length / height etc.,)
Starting Point Latitude
(DD.MM.SEC)
Starting Point Longitude
(DD.MM.SEC)
Starting Point Type: Linear (Connects to the segment of own network) / Nodal (Connecting to Other networks Ending Point Latitude
(DD.MM.SEC)
Ending Point Longitude
(DD.MM.SEC)
Ending Point Type: Linear (Connects to the segment of own network) / Nodal (Connecting to Other networks Segment Type: Common / Individual Approval required from Cross over network: Yes / No
S1 Network1 100 44.5.32   Linear 44.5.39 11.9.32 Linear Individual No
S2 Network1 105 44.5.39 11.9.32 Linear 44.5.44 11.9.32 Nodal Individual No
S3 Network1 105 44.5.44 11.9.32 Nodal 44.5.47 11.9.32 Nodal Common Yes
S4 Network1 110 44.5.47 11.9.32 Nodal 44.5.51 11.9.32 Linear Individual No
S5 Network1 95 44.5.51 11.9.32 Linear 44.5.55 11.9.32 Nodal Individual Yes
S6 Network1 110 44.5.55 11.9.32 Linear 44.5.59 11.9.32 Linear Individual Yes
S7 Network2 110 44.6.12 11.9.32 Linear 44.6.11 11.9.31 Linear Individual No
S8 Network2 110 44.6.32 11.9.32 Linear 44.5.44 11.9.32 Nodal Individual No
S9 Network2 100 44.5.47 11.9.32 Nodal 44.5.53 11.9.36 Linear Individual No
S10 Network2 112 44.6.32 11.9.32 Linear 44.6.32 11.9.32 Linear Individual No
S11 Network3 115 43.5.32 11.9.32 Linear 44.5.55 11.9.32 Nodal Individual Yes
S12 Network3 105 44.5.51 11.9.32 Nodal 44.5.51 11.9.39 Linear Individual Yes
S13 Network3 110 44.5.51 11.9.39 Linear 44.5.51 11.9.46 Linear Individual No

 

In the next blog we will see how to attach non liner assets to a linear assets network.

 

 

 

Comments

Great information. Many thanks.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles