Version 3 (modified by hemmecke, 9 years ago) ( diff )


BluePrint: Vehicle Routing


<Briefly describe the solution?> <What problem is this solution solving?> <How will this solution add value to Sahana?> <Name any similar existing solutions>


<Who will be the users of the solution?> <Who else will be affected by this solution? eg. Developers, Users of Existing Functionality that may be changed?> <How will stakeholders be affected?> Tip: Engage these stakeholders in the development of your BluePrint.

User Stories

<> <A good User Story should answer the following questions:> <* Who the user is> <* What they want the solution to do for them?> <* Why they want it to do that? (goal)> <eg. A <type of user> wants the solution to <do something for them> so that <can achieve a goal>.>


<Group requirements in subsections, e.g. etc.> < requirements> <Identify different types of requirements:>





System Constraints


<Where relevant include alternative design options>

Data Model

(e.g. EER or class diagrams)


<Diagrams or Pseudocode>

Site Map

<for User Interface solutions>


<for User Interface solutions>


Current Implementation

<Leave open for a list of existing implementation of this solution in Sahana Eden:> <*a brief description of the implementation (date/time, name, design options chosen)> <*a link to the code> <*list of deployments of the implementation> <*links to case studies> <*short analysis of achievements/problems>

Planned Implementation

<List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on>

Base case:


  • a transportation network with known status of availability
  • a set of suppliers, having a fleet of vehicles of given capacities, and a warehouse of goods
  • a set of demands (who, what, when)


  • sufficient vehicles
  • sufficient drivers
  • sufficient fuel
  • vehicles transport all the fuel they need for transport


  • satisfy all demands within their time windows
  • minimize total distance (assume for the moment that this also minimizes delivery time)

Future Extensions

<List of features which could be included, but are outside of the scope of this extension>

Potential features:

i) delivery time windows (I have already included them into the base case) ii) minimize fuel consumption iii) maximize the number of demands satisfied iv) handle routes that suddenly become unavailable v) re-optimization of plan if routes become available again, without sending vehicles home vi) handle different types of routes (street, air, water, protection required, ...) vii) handle case of too few vehicles to transport all in one shot viii) low fuel at start ix) low fuel availability within the network to refuel vehicle x) handle time for loading/unloading xi) handle breakdowns of vehicles xii) online version with new demands coming in over time xiii) assignment of drivers to vehicles

Outstanding Questions

<Questions about the features or design that haven't been (and need to be) answered>


<Links to external resources>


Note: See TracWiki for help on using the wiki.