AN ORIGINAL KPIs for OpsTruck (concepts and requirements)

From UG

Revision as of 21:04, 15 November 2010 (edit) Alex (Talk | contribs) (→Cost per pound REQ) ← Older edit		Revision as of 18:28, 16 November 2010 (edit) (undo) Alex (Talk | contribs) (→Requirements) Newer edit →
Line 8:		Line 8:
	There are number of reports required. See below.		There are number of reports required. See below.
		+
		+	The concept is to make them layered: to start at a top level and be able to drill down to more finite details.
	=== Cost per pound analysis ===		=== Cost per pound analysis ===
Line 13:		Line 15:
	See [[Cost per pound analysis]]		See [[Cost per pound analysis]]
-	=== Total cost REQ ===	+	=== Total cost analysis ===
		+
		+	See [[Total cost analysis]]
	===== Functionality & Summary =====		===== Functionality & Summary =====

---

Revision as of 18:28, 16 November 2010

Contents 1 Parent Mantis 2 Requirements 2.1 Cost per pound analysis 2.2 Total cost analysis 2.2.1 Functionality & Summary 3 Design Ideas 3.1 Cost per pound DESIGN 3.2 Total cost DESIGN 4 Detailed Design 5 APPENDIX Old version of this wiki 5.1 Core needs 5.2 Reports 5.2.1 Exceptions report 5.2.2 Hold Bucket Measure Report 5.2.3 Time frames Report 5.2.4 Cost per pound Report 5.2.5 retroactive analysis 5.3 Types of output 5.3.1 Graphical Pie Chart Bar Etc report 5.3.2 Interactive maps 5.3.3 Excel files 5.3.4 Dashboard 5.3.5 Misc 6 History 6.1 Original ver

Parent Mantis

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

Requirements

There are number of reports required. See below.

The concept is to make them layered: to start at a top level and be able to drill down to more finite details.

Cost per pound analysis

See Cost per pound analysis

Total cost analysis

See Total cost analysis

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:
  • The average number for the total costs
  • Shipper CT_bo#Pick_Up
  • Consignee CT_bo#Export_Delivery_To
  • Lanes: Origin Company's Name, City, State & Zip, CT_bo#Pick_Up & the Destination Company's Name, City, State & Zip CT_bo#Export_Delivery_To
  • Carrier CT_bo#Pick_Up_Trucker
  • Utilization Commodity#Plts or Commodity#Loose_Pkgs

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