Database Answers Asset Lifecycle
Printer Printer-friendly version

Home Ask a Question Best Practice Careers Contact Us Data Models Search Site Map
Data Model for Asset Management   

An Access Database is available.

We might also design a Data Mart which is very useful for providing data for Reports and Business Intelligence.

We would be glad to have your comments.

If you are new to Data Models, this page of my new Tutorial will help you understand the Data Model.

Click here to see the Requirements that have been derived from a review of the Wikipedia entry for Asset Management
Click here for the Proof-of-Concept and here for the End-2-End Data Models.

Step 2 - Define Reference Data
Our Assset Management Service is primarily planned for Utilities including 
Electricity, Gas, Water and Transport, such as Airport, and Rail.

Step 1 - Start with our Canonical Data Model
Canonical Data Model
Step 3 - Asset Register Conceptual Data Model

Getting Started Conceptual Data Model for Asset Management
Step 4 - Asset Register Logical Data Model

Getting Started Conceptual Data Model for Asset Management
Step 5 - Asset Register Physical Data Model

Physical Data Model for Asset Management

Step 6 - Define Sample Data
A. Asset Hierarchy :-
1. Category, eg Domestic
2. Supertype, eg Cutlery
3. Type, eg Spoon

B. Lifecycle Phases :- 
These can be common to all types of Assets and typically include :-
1. Acquire
2. Use
3. Maintain
4. Dispose

C. Status :-
1. Needs Maintenance 
2. OK
3. Ready for Disposal


Step 2666666666666666666 - Create the 'Business-friendly' Semantic Model
This is specifically designed to be the 'Business-friendly' and to provide a vehicle for 
communication with business users and Subject Matter Experts.

We have not shown the 'Rabbits-Ears' to keep the diagram simple and easier to understand.


Final Semantic Data Model for Asset Management
Step 3 - Create the Top-Level Model

When we think about our final draft, we realise that all the Entities are Hierarchies.
For example, the Services are grouped on Categories, Staff are in Organisation Hierarchies 
(where people usually report one-level up), and so on.

We show this in our Model as self-referencing Relationships for each Entity, which we call
Recursive or Reflexive Relationships, or 'Rabbits-Ears'.

In this Model, the Life Cycle of an Asset is shown as Services that cover the 
typical Phases of :-
  • Acquisition
  • Usage
  • Maintenance
  • Finally the Disposal of an Asset. We have also created separate Subject Area Models :-
  • Assets
  • Clients
  • Equipment
  • Events
  • Maintenance
  • Overhaul
  • Parties, Roles and Customers
  • Repair
  • Services

    Data Model for Asset Management


  • Review the material below here

    Step 11 - From a review of Wikipedia and the Lloyd's Register Web sIte,
    we identify that the 'Things of Interest' include :-
  • Clients
  • Documents
  • Locations
  • Services
  • Ships
  • Staff
    Data Model for Asset Management
  • Step 12 - Adding Many-to-Many Services are offered to Clients
    Many Services can be offered to the
    same Client and the same Service can be
    offered to many Clients.
    Therefore we need a Many-to-Many Relationship.
    Step 1 Data Model
    Step 13 - Adding Vessels
    The Services apply to Vessels that belong to Vessels
    Therefore we need a Many-to-Many Relationship,
    which will look like this - Step 3 Data Model
    Step 14 - Adding Documents, Locations and Staff
    The Documents will include Reports and results
    of Assessments and ISO Certifications
    and generalise Vessels to Assets.
    Step 4 Data Model


    Barry Williams
    Principal Consultant
    Database Answers Ltd.
    London, England
    May 11th. 2017


    © DataBase Answers Ltd. 2013
    About Us Contact Us