1 / 6

CAPACITY FLEET MANAGEMENT: Vehicle Visibility: Scope Requirements

Vehicle Visibility: Objectives

orien
Télécharger la présentation

CAPACITY FLEET MANAGEMENT: Vehicle Visibility: Scope Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. CAPACITY (FLEET) MANAGEMENT: Vehicle Visibility: Scope & Requirements Paul Claessen, Business Change Management, DSV Road A/S

    2. Vehicle Visibility: Objectives & Solution Concept Objectives: Maximize the use of DSV controlled vehicles Minimize empty kilometers / re-positioning of vehicles Minimize chartering out to 3rd parties (if internal alternative does exists) Solution concept: Create visibility of planned / DSV controlled vehicles to other planners (In principle) from all countries to all countries Within a specifiable timeframe and area / traffic lane Provide an easy to use search & selection tool Minimal changes in current way of working: Vehicles stay ownership of originating planner The initiative for matching is with the planner owning un-allocated cargo The decision for matching is with the planner owning the vehicle Conditions are based on planner-to-planner communication The potential benefits are to be proven out in a pilot with limited scope

    3. Vehicle Visibility: Requirements Business Requirements: Pilot to prove financial / operational impact of the initiative Pilot results available Q2/2010 Relevant (destination- and transit-) countries to participate: DK/SE/UK/BNL/GER/FR Non-Cargolink countries to be included (not for pilot phase) Preferably use existing system / platform Preferably short roll-out / limited training efforts required Initial costs < 100 KEuro

    4. Vehicle Visibility: Requirements Systems Requirements: (Quasi) real-time: pilot phase on nightly run Data of max 1 week ahead Max 20 data elements in interface Potential of connecting 10.000 users Potential of handling > 50.000 trucks (= weekly max) DSV controlled user base, no access to 3rd parties Able to interface with different DSV Road operational systems No 2-way communication required at pilot stage 2-way communication in further roll-out t.b.d.

    5. Vehicle Visibility: Requirements Data Requirements: Truck / trailer ID (unique number for communication) Type of vehicle (defining dimensions / weight limits) Loading Date / Loading Time (EDL / ETL) Unloading Date / Unloading Time (EDA / ETA) Loading and Unloading Country and Postal Code (2-PC) Owner of the Truck / Trailer (planner contact details) DSV Hubs in routing Operational Limitations / Requirements Further details: see specs of preferred solutions

    6. Fleet management / Planning system Meeting Minutes January 14th, 2010 Bjarne N. Eriksen Paul Claessen

More Related