AN ORIGINAL KPIs for OpsTruck (concepts and requirements)
From UG
(Difference between revisions)
(→Parent Mantis) |
(→Requirements) |
||
| Line 7: | Line 7: | ||
== Requirements == | == Requirements == | ||
| - | + | === Glossary === | |
| - | + | * '''KPI''' (Key Performance Indicator) - see http://en.wikipedia.org/wiki/KPI | |
| + | * '''Arden Trucking Project''' - this is an evolving project of supporting Transportation and Supply Chain needs for Arden. Some components that have been added to CT2 for this project: | ||
| + | ** [[:New Arden Trucking Project]] | ||
| + | ** [[:Category:Cybertrax 2.1 Client]] | ||
| + | ** [[:EDI to TMS]] | ||
| + | |||
| + | === Core need === | ||
| + | |||
| + | Core need. It is to provide a number of '''KPI'''s for Arden management for '''Arden Trucking Project''' | ||
| + | |||
| + | === Phase 1 === | ||
| + | |||
| + | We agreed to provide the following KPIs for Phase 1: | ||
| + | |||
| + | * Cost: | ||
| + | ** Cost per pound | ||
| + | ** Total cost analysis | ||
| + | |||
| + | * Time: | ||
| + | ** Created to Approved | ||
| + | ** Created to Hold | ||
| + | ** Approved to Routed | ||
| + | ** Routed to Pick Up | ||
| + | ** Pick up to Delivery | ||
| + | ** On hold | ||
| + | |||
| + | === Design === | ||
| + | |||
| + | '''Drill down.''' Should have several levels. Start at a top level (on a dashboard level with a minimal info) and be able to drill down to more finite details (down to the load / CT). | ||
| + | |||
| + | '''Standardization.''' For every KPI approach to UI design should be similar in principle and as standard as possible. | ||
| + | |||
| + | '''Report types.''' For every KPI provide the following report types: | ||
| + | * dashboard version | ||
| + | * KPI as a function of time | ||
| + | * KPI as a function of various variables such as CT fields | ||
| + | ** bar layout | ||
| + | ** pie layout | ||
| + | ** map layout | ||
| + | |||
| + | '''Filters.''' Provide set of standard filters. Ideally every CT field should be represented by a multiselect filter. | ||
| + | |||
| + | '''Fields on CT/Load version'''. On this type of report ideally: | ||
| + | * list columns should cover all CT fields | ||
| + | * user should be able to manage order of columns and what columns are included and what are excluded | ||
== Design Ideas == | == Design Ideas == | ||
Revision as of 18:21, 22 November 2010
Contents |
Parent Mantis
2488: [Arden KPI]......... <proj>
Requirements
Glossary
- KPI (Key Performance Indicator) - see http://en.wikipedia.org/wiki/KPI
- Arden Trucking Project - this is an evolving project of supporting Transportation and Supply Chain needs for Arden. Some components that have been added to CT2 for this project:
Core need
Core need. It is to provide a number of KPIs for Arden management for Arden Trucking Project
Phase 1
We agreed to provide the following KPIs for Phase 1:
- Cost:
- Cost per pound
- Total cost analysis
- Time:
- Created to Approved
- Created to Hold
- Approved to Routed
- Routed to Pick Up
- Pick up to Delivery
- On hold
Design
Drill down. Should have several levels. Start at a top level (on a dashboard level with a minimal info) and be able to drill down to more finite details (down to the load / CT).
Standardization. For every KPI approach to UI design should be similar in principle and as standard as possible.
Report types. For every KPI provide the following report types:
- dashboard version
- KPI as a function of time
- KPI as a function of various variables such as CT fields
- bar layout
- pie layout
- map layout
Filters. Provide set of standard filters. Ideally every CT field should be represented by a multiselect filter.
Fields on CT/Load version. On this type of report ideally:
- list columns should cover all CT fields
- user should be able to manage order of columns and what columns are included and what are excluded
Design Ideas
Cost per pound analysis
Total cost analysis
Average times
See Average times
Maps
See Maps
