AN ORIGINAL KPIs for OpsTruck (concepts and requirements)

From UG

(Difference between revisions)
Jump to: navigation, search
(Functionality & Summary)
(Functionality & Summary)
Line 37: Line 37:
* The Second Layer, would list the various components that make up the average total cost. These components consist of the following:
* The Second Layer, would list the various components that make up the average total cost. These components consist of the following:
-
** Shipper [[CT_bo#Pick_Up]]
 
-
** Consignee [[CT_bo#Export_Delivery_To]]
 
-
** Planner [[CT#Authorized_By]]
 
-
** PO Issued By [[CT#PO_Issued_by]]
 
== Design Ideas ==
== Design Ideas ==

Revision as of 16:43, 12 November 2010


Contents

Parent Mantis

2489 0002489: [BI / KPI] (BA) create proposal for Arden

Requirements

There are number of reports required. See below.

Cost per pound REQ

Core Need

This report would allow Arden to compare their actual costs vs. their cost per pound rates for their budgeting purposes. As well as assist them in shaping their vendor decisions.

Functionality & Summary

The concept for this is report is layered, to start at a top level and be able to drill down to more finite details.

  • Top Level or First Layer, would list an average number for the cost per lb. This average is based upon the total costs for the total number of shipments being reported on.

Total cost REQ

Functionality & Summary

The concept for this is report is very similar to the cost per pound report; in that it is layered, starting at a top level and being able to drill down.

  • Top Level or First Layer, would list an average number for the total costs. This average is based upon the total costs per truck load, for the total number of shipments that are being reported on.
  • The Second Layer, would list the various components that make up the average total cost. These components consist of the following:

Design Ideas

Cost per pound DESIGN

Total cost DESIGN

Detailed Design

Denise with help of Alex or Andrei

OR

Alex or Andrei

APPENDIX Old version of this wiki

Core needs

  • domestic KPI dashboard/reporting tool)
  • Shape our vendor decisions (Babushak)
    • example: can we find supplier closer to EM (consumer) who can fulfill supply needs (this reduces transp cost, transit time)
  • What is it costing us?
  • time frames
  • separation of exceptions between usual .... day to day
  • Simon: desirable output for this report would be a graphical view of origin/destination pairs and “hot spotting” of the main points, with the ability to drill-down to a granular level of detail.
    • need main points (major supplier). On the map.
    • Cluster analysis
    • frequency of ship froms
  • data analysis

Reports

Exceptions report

  • High delta from create to approved
  • ... Unusually high charge
  • Spike / acceleration of monthly cost on trade line
  • ...

Hold Bucket Measure Report

  • average time in hold bucket
  • include value of shipments

Time frames Report

  • Created to approved
  • approved to dispatch
  • dispatch to pick up
  • pick up to delivery

Cost per pound Report

  • Look at cost per LB before dispatching?
    • Include cost per LB in calibration?


retroactive analysis

Types of output

Graphical Pie Chart Bar Etc report

Interactive maps

Excel files

Dashboard

Misc

  • columns on Marc's spreadsheet (output/filters)
    • Cost per LB
    • shipper
    • consignee
    • Lanes
    • carrier
    • Dates
    • ultilisation


History

Original ver

http://mantis.jaguarfreight.com/mediawiki-1.15.0/index.php?title=BI_and_KPIs_for_OpsTruck&oldid=16496