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
Here is a summary of What Wikipedia says :-
"Asset management, broadly defined, refers to any system that monitors and maintains things of value to an entity or group.
It may apply to both tangible assets [that you can see and touch] (such as buildings) and to intangible assets such as human capital, intellectual property, goodwill and/or financial assets). Asset management is the process of maintaining assets."
For our purposes, we define Asset management as "Storing physical items, such as furniture, for customers for a fee and recording details of what it in store and for long and producing an appropriate invoice for payment by the customer".
Click here for the Proof-of-Concept
and here for the End-2-End Data Models
and here for the Tutorial.
Step 1 - Define POC Tables
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
Step 3 - Asset Register Conceptual Data Model
|Step 4 - Asset Register Logical Data Model
|Step 5 - Asset Register Physical Data Model
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 :-
C. Status :-
1. Needs Maintenance
3. Ready for Disposal
Step 2B - 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.
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 :-
Finally the Disposal of an Asset.
We have also created separate Subject Area Models :-
Parties, Roles and Customers
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 :-
|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 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 14 - Adding Documents, Locations and Staff
The Documents will include Reports and results
of Assessments and ISO Certifications
and generalise Vessels to Assets.
Database Answers Ltd.
May 11th. 2017
© DataBase Answers Ltd. 2013