Skip to main content

Florlog Data Model Documentation

This document provides an overview of the data model used in our flower logistics system. It is designed to help non-technical users understand the structure and purpose of the various components of our system. Each section explains the purpose of key concepts in plain language, with an emphasis on how they relate to real-world processes.

Introduction​

In the flower logistics industry, managing orders, locations, transport assets, and movements is crucial. This data model represents the backbone of our system, helping us track every stage of the journey — from the moment an order is placed, to the delivery of flowers, and beyond.

Our model focuses on clarity and scalability, ensuring that we can handle complex logistics scenarios while maintaining a clear record of all entities, relationships, and events.

Key Components of the Data Model​

1. Orders​

An Order represents a request to deliver specific types of flowers (SKU) from one location to another. It includes essential information such as:

  • Buyer and Seller Information: Who is ordering and who is fulfilling the order.
  • References: A unique identifier for the buyer and seller, to ensure clear communication.
  • Locations: Where the order is picked up and delivered.
  • Order Lines: Detailed items in the order, such as the type and quantity of flowers.
  • Dates: The order creation date, confirmation date, and the requested delivery date.

2. Locations​

Locations represent the physical places involved in logistics. These could be warehouses, fields, or distribution centers. Key details include:

  • Coordinates: Latitude and longitude to pinpoint the location on a map.
  • Ownership: The entity that owns the location.
  • Roles: Specific roles a location plays, such as storage or distribution.

3. SKUs (Stock Keeping Units)​

SKUs represent the specific types of flowers in our system. Each SKU includes:

  • A name and description (e.g., "Red Roses, 12-pack").
  • Specific transport requirements, such as the type of transport assets needed.

4. Transport Assets​

Transport assets are the tools and equipment used to move flowers between locations. These can range from trucks and carts to overlays. Each asset is characterized by:

  • Type and Subtype: For example, a "Cart" might have subtypes like "Danish Cart."
  • Reference: A user-friendly identifier for tracking assets.
  • Capacity Requirements: Defined relationships to ensure proper stacking or loading configurations.

5. Transport Moves​

A Transport Move represents the movement of flowers from one location to another. Each move includes:

  • From and To Locations: The starting and ending points of the journey.
  • Type: The method of transport, such as "Truck."
  • Reference: A user-friendly identifier for the move.
  • Dates: Planned and actual start and end dates.
  • Status: Indicates the current stage of the move (e.g., Planned, Started, Completed).

6. Transport Events​

Transport events track the status of assets during a transport move. For example, when a truck departs from a location or arrives at its destination. Key details include:

  • Event Type: Planned, departed, arrived, etc.
  • Location and Time: Where and when the event occurred.
  • Assets Involved: Which transport assets are part of the event.
  • Actual or Predicted: Indicates whether the event has occurred or is expected.
  • Message and Source: A short description of the event and its origin.

7. Relationships​

The data model uses relationships to connect these components:

  • Orders are linked to locations, SKUs, and transport moves.
  • Transport moves connect multiple order lines and transport assets.
  • Events provide a timeline of actions for transport moves and assets.

Real-World Examples​

Example 1: A Flower Shipment​

Imagine an order placed by a distributor to deliver 500 red roses from a farm to a retailer:

  1. The farm is the pickup location, and the retailer is the drop-off location.
  2. The order includes a line item for 500 red roses.
  3. A transport move is scheduled using a truck, starting at the farm and ending at the retailer.
  4. Events such as "Truck Departed" and "Truck Arrived" are logged to track progress.

Example 2: Managing Transport Assets​

A cart used to move flowers between locations might have a reference "Cart-123." It is tracked as part of a transport move and is logged in events like "Cart Loaded" or "Cart Unloaded."

Benefits of This Model​

  1. Transparency: Every detail of the logistics process is clearly recorded.
  2. Flexibility: Handles complex scenarios like partial deliveries or asset sharing.
  3. Scalability: Can grow with your business needs, adding more locations, SKUs, or transport methods.

Conclusion​

This data model is the foundation of our flower logistics system, ensuring every step of the process is accounted for. With clear tracking and detailed relationships, we provide the tools to manage even the most complex logistics scenarios.

For questions or further explanation, please contact our team!