AN ORIGINAL KPIs for OpsTruck (concepts and requirements)

From UG

Revision as of 21:02, 26 October 2010 by Alex (Talk | contribs)
Jump to: navigation, search


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

Reports

  • Exception reports
  • Measure Hold Bucket 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
  • Look at cost per LB before dispatching?
    • Include cost per LB in calibration?
  • retroactive analysis?
  • columns on Marc's spreadsheet (output/filters)
    • Cost per LB
    • shipper
    • consignee
    • Lanes
    • carrier
    • Dates
    • ultilisation


Detailed Requirements

Retrieved from "https://wiki.jaguarfreight.com/AN_ORIGINAL_KPIs_for_OpsTruck_(concepts_and_requirements)"
Personal tools