RFC: Transportation Management System

[max3903]

Migration and refactoring of Jarsa TMS modules.
v15 sources: https://github.com/ursais/stock-logistics-transport/tree/15.0-jarsa
Credits: @alan196

TMS #130

• Menu items:

  • Dashboard: Teams (Kanban, Timeline, Activity)
  • Operations: All trips (List, Form), Odometers
  • Master Data: Vehicles, Drivers, Locations, Contracts, Services
  • Reporting: Trips (Graph, Pivot), Costs
  • Configuration: Settings, Teams, Stages (for Travel, Driver and Vehicle)

• Groups:

  • TMS / Administrator: Access to all menu items
  • TMS / User (dispatcher): Access to all menu items except Configuration
  • TMS / Driver: portal user?
  • Technical / Use TMS Teams

• Settings: Activation of advanced features via groups or modules

  • Fleet options
  • Activate Teams (a team shares the same process/stages)
  • Activate Crews (a crew shares the same vehicle)
  • Activate Driver License Expiration + Number of days
  • Activate Vehicle Insurance Expiration + Number of days
  • Integrations: GPS, Maps, Marketplaces, Telemetry

• Basic models:

  • Stages (tms.stage)
  • Teams (tms.team)
  • Vehicles (fleet.vehicle): cargo or passengers, type, capacity
  • Drivers (res.partner)
  • Locations (res.partner)
  • Routes (tms.route)
  • Travels (tms.order)

• Dependencies: fleet

TMS - Sale #134

To sell trips by quantity, volume, weight, quantity of a specific product, distance (miles, kilometers, nautic miles)

• Dependencies: tms, sale

TMS - Expenses #133

To manage expenses of a trip: hotel, tolls, fuel, etc.

• Dependencies: tms, hr_expense

TMS - Account #137

To invoice trips to the customer and create vendor bills to the drivers and other suppliers

• Dependencies: tms, account

TMS - Product #136

• Add a boolean "Is a vehicle" on the product.template

TMS - Purchase #135

To create:

• vehicles when purchasing them

• purchase requests for the driver(s) and other suppliers of a trip

• Dependencies: tms_product, purchase

TMS - Account - Asset #138

To manage depreciation of vehicles

• Dependencies: tms, account_asset

TMS - Maintenance

To manage preventive maintenance

• Dependencies: tms, maintenance

TMS - Skills

To manage driver skills and licenses

• Dependencies: tms, hr_skills

TMS - Air

To manage transportation by air (airlines, air cargo):

• Vehicles: planes, helicopters, drones

• Locations: Airports

• Dependencies: tms

TMS - Water

To manage transportation by water:

• Vehicles: boats, tankers, barges, ferries, container ships

• Locations: Ports

• Dependencies: tms

TMS - Rail

To manage transportation by rails:

• Vehicles: Trains, Wagons

• Dependencies: tms

[pedrobaeza]

We already have our TMS: https://github.com/Tecnativa/tms pending to be moved to OCA.

cc @sergio-teruel @carlosdauden

[max3903]

We already have our TMS: https://github.com/Tecnativa/tms pending to be moved to OCA.

cc @sergio-teruel @carlosdauden

Can I get a demo?

[pedrobaeza]

I'm afraid we don't have any public instance prepared.

[rousseldenis]

@pedrobaeza Do you plan to demo it on OCA days? It should be a good entry point to the migration to OCA.

[pedrobaeza]

Yes, I can demo it at OCA days, but it seems @max3903 is taking another path in #130

[max3903]

We built a demo of Pedro's TMS modules and came up to the conclusion that Jarsa's ones are more advanced.

The intent is to implement a common ground for everyone in 17.

[marcelsavegnago]

Just to try to contribute some information to the preparation of tms_sale.

We are working on implementing Odoo in a transportation company that will be selling transportation services. Below are some key data points and necessary fields that we have identified to meet both the operational and fiscal requirements in Brazil:

Taker (partner_invoice_id): In the Electronic Transport Document (CT-e), the taker represents the entity responsible for paying for the service upon its completion.

Recipient (partner_shipping_id): The one who receives the goods at the end of the transport route, which can be an individual or a legal entity.

Sender (field name suggestion: partner_sendering_id): Responsible for sending the goods, usually the issuer of the NFe.

Receiver (field name suggestion: partner_receivering_id): The actor who receives the goods. They are considered an intermediary between the issuer and the final recipient.

Dispatcher (field name suggestion: partner_shippering_id): The one responsible for delivering the cargo to the carrier when the shipment is not carried out by the sender.

[marcelsavegnago]

@max3903 @santiagordz for asset management (fleet), I have this proposal in version 14, and we can implement it in version 17.0 as well."

OCA/account-financial-tools#1802