# Laying the Foundation for FNHP’s Next Big System

# Day 1

Today marks the very first development entry for **Transolix**, FNHP’s modern Transport Management System (TMS). The aim is simple and ambitious: give dispatchers a clean, powerful, and intuitive tool that handles planning, routing, and shipments without the heavy complexity of legacy systems.

Here’s what we achieved on Day 1.

---

* ## 1\. Vision & Direction
    

We defined what TransPilot is — and what it isn’t.  
The system will be:

* Web-based, modern, and fast
    
* Driven by React on the front end for interactivity
    
* Powered by Laravel and MariaDB on the backend
    
* Deployable both online and on-premise
    
* Clean enough for small companies, scalable enough for growing ones
    

This sets the tone for the architecture and long-term roadmap.

---

* ## 2\. Architectural Decisions
    

We locked in the technical pillars:

* **Backend:** Laravel (clean, predictable, perfect for structured business logic)
    
* **Frontend:** React (snappy UI for drag-and-drop planning)
    
* **Database:** MariaDB (stable and already configured in the dev environment)
    

This gives us a future-proof, maintainable foundation.

---

* ## 3\. First Domain Entities
    

We created the initial functional core of the system:

### **Shipments**

* Metadata (weight, size, complexity)
    
* Multiple partials per shipment
    
* Support for customer-specific pickup/dropoff addresses
    

### **Vehicles**

* Basic profiles and soon capacity rules
    

### **Drivers**

* Driver information, availability windows planned later
    

These entities will feed directly into the planner logic.

---

* ## 4\. Shipment Creation Flow
    

We built the first feature for dispatchers:

* A “+” button in the shipments view (mirroring the users module)
    
* Modal overlay for creating new shipments
    
* Upload functionality for PDF or image Auftrag documents
    
* Choose or create a customer on the fly
    
* Saved addresses per customer
    

This is the beginning of the real workflow.

---

* ## 5\. Routing & Map Planning
    

We researched the mapping stack:

* **OSRM** selected as the routing engine
    
* Clear reasons why big TMS vendors don’t rely on OSRM directly
    
* Options to enrich OSRM with premium real-time traffic & incident data
    

This will become the heart of the planning board.

---

* ## 6\. Staging Setup Planning
    

Because the dev environment runs on Windows, we’ll prepare a **setup script (.sh)** for staging on the FNHP server once the core components are ready.

It will automate:

* Pulling the code
    
* Installing dependencies
    
* Migrating the DB
    
* Building the frontend
    
* Configuring Nginx
    

Clean and repeatable deployments = less stress later.

---

* ## 7\. TransPilot Logo
    

We designed a **geometric cargo icon** with forward direction, clean lines, and a transparent background.  
It symbolizes:

* shipment
    
* movement
    
* structure
    
* precision
    

Exactly what TransPilot stands for.

---

* ## End of Day Summary
    

**Day 1 accomplished:**

* Vision set
    
* Architecture agreed
    
* Domain model started
    
* Auth foundation applied
    
* Shipment creation flow implemented
    
* Routing engine selected
    
* Logo designed
    

Tomorrow: Magatunga in the morning, TransPilot in the afternoon.

TransPilot is officially underway.