Database Answers Tracking Shipping (Click for Web Site)
Printer Printer-friendly version

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

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.

The Requirements Have been derived from Wikipedia

Step 1 - From a review of Wikipedia we identify that the 'Things of Interest' include :-
  • Clients
  • Documents
  • Locations
  • Services
  • Ships
  • Staff
  • Step 1 Data Model
    Step 2 - 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 3 - 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 4 - 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
    Step 5 - The Lifecycle of an Asset
    An Event-oriented Approach
    The Lifecycle of an Asset - Step 5
    Step 6 - Create a Subject Area Model for Equipment Step 7 - Create a Subject Area Model for Equipment
    Step 7 - Create a Subject Area Model for Services Step 7 - Create a Subject Area Model for Services
    Step 8 - Create the draft final 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'.
    Draft Data Model for Tracking Shipping
    Step 9 - Create the final Top-Level Model
    Finally, we replace the Locations Entity with 'Schedules'so that we include Schedules, 
    which can be Dated, Un-Dated or Executed.
    We have also created separate Subject Area Models :-
    
  • Assets
  • Clients
  • Equipment
  • Events
  • FOI
  • Maintenance
  • Overhaul
  • Repair
  • Services
  • Data Model for Tracking Shipping
    Step 10 - Finally, 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 Tracking Shipping


    Barry Williams
    Principal Consultant
    Database Answers Ltd.
    London, England
    March 5th. 2014


    © DataBase Answers Ltd. 2014
    About Us Contact Us