KPI
From UG
Info
Mantis
Mantis:
- parent: 0003545
- category: DR/KPI:ph1
Environments
- QA/SIT/UAT:
Good account to test with:
- name: KPI_User@com.com
- pwd: Admin1234
SVN
- /branches/DR_KPI
Team
- Sponsor: Simon
- UAT/Prod Manager: Marc
- Lead SA/PM/SIT: Alex
- Lead Dev1: Sasha
- Dev2: Kostya
- Graphics: Vic
- QA: Roma
Email groups:
alex@jaguarfreight.com; a.pivniak@elcosol.com; k.ushakov@elcosol.com; v.makhankov@elcosol.com; r.lakhno@elcosol.com;
Glossary
- BI - Business Intelligence
Requirements
- This Phase One should include first portion of DRs/KPIs delivered
- Must be production quality
- This phase is for Arden primarily (all MOTs) but also for Sales Dept to show possibilities to prospects and existing Clients
- This project is very important top visibility project
- Also right tool/lib should be evaluated/selected for the future (example: LogiXML vs ZK API/other Java APIs)
DR1 and DR2
Moved to DR KPI Phase One DR1 DR2
DR3 Cost per unit KPI by Shipper Consignee Carrier Lane
DR3 Layout
It consists of the following sections:
- title
- main menu
- KPI panel
- left panel
- top right panel
- bottom right panel
See also Figure below:
Title and Main Menu
Title: Cost per unit KPI by Shipper Consignee Carrier Lane
Main Menu:
- Client Company - single select, list restricted by user visibility
- MOT - single select
- View type - controls what is displayed inside panels. Options:
- Main View
- Shippers View
- Consignees View
- Carriers View
- Lanes View
KPI Panel
- label: cost per kg (KPI type and unit of measurement)
- currency: USD
- number: actual value of KPI
- arrow change indicator: comparatively to previous period defined by "timeframe" (up red, down green)
- percentage: change in % comparatively to previous period defined by "timeframe"
- timeframe: options: weekly, monthly
- traffic light: indicates tolerance level, see #Tolerance levels parameters
Tolerance levels parameters
- this is a list of parameters managed by user in user profile
- controls what is considered green vs yellow vs red zone for KPI
Left panel, Top right panel, Bottom right panel
Content on these panels is controlled by "View Type" selector. See details below.
Main View
See mockup below:
Left panel
Left column:
- this year weeks to date (w1, w2, .... )
- arrow indicator - change from previous week
- gage indicator
Right column:
- KPI value
Top right panel
Axis X: this year weeks to date (w1, w2, .... )
Axis Y:
- plot A: KPI this year
- plot B: KPI last year
Bottom right panel Tab 1
- Type: bar/pie
- Axis X: top 20 for Shippers
- Axis Y: KPI
Bottom right panel Tab 2
- Type: bar/pie
- Axis X: top 20 for Consignees
- Axis Y: KPI
Bottom right panel Tab 3
- Type: bar/pie
- Axis X: top 20 for Carriers
- Axis Y: KPI
Bottom right panel Tab 4
- Type: bar/pie
- Axis X: top 20 for Lanes
- Axis Y: KPI
Carriers View
See mockup below:
Left panel
Left column:
- Carriers
- arrow indicator
- gage indicator
Right column:
- KPI value
Top right panel
Axis X: top 20 Carriers
Axis Y: options:
- Total weight (kg)
- Total Cost (USD)
- Shipment Count
- Average weight (kg) per shipment
plot A: this year
plot B: last year
Bottom right panel Tab 1
- Type: bar/pie
- Axis X: top 20 Carriers
- Axis Y: Total weight (kg)
Bottom right panel Tab 2
- Type: bar/pie
- Axis X: top 20 Carriers
- Axis Y: Total Cost (USD)
Bottom right panel Tab 3
- Type: bar/pie
- Axis X: top 20 Carriers
- Axis Y: Shipment Count
Bottom right panel Tab 4
- Type: bar/pie
- Axis X: top 20 Carriers
- Axis Y: Average weight (kg) per shipment
Consignees View
Same data/layout as in #Carriers View but for Consignees.
Shippers View
Same data/layout as in #Carriers View but for Shippers.
Lanes View
Same data/layout as in #Carriers View but for Lanes.
DR3 Misc
MOTs
- FCL (two FCL modes combined)
- LCL (two FCL modes combined: LCL/Client Consol)
- Truck (all 3 truck modes combined)
YTD average line
This is a horizontal line on top right plot indicating "YTD average" for KPI, say cost per kg.
Top Bottom X selector
This is a single select for bottom right panel indicating by how many items to group. See full list below:
- top 10
- top 20
- bottom 10
- bottom 20
Mappings
Shippers:
- same for all MOTs
- maps to Ct#Shipper
Consignees:
- same for all MOTs
- maps to Ct#Consignee
Carriers:
We have two fields for Trucking company: Export Pick-up Trucker, Delivery Trucker. So if one shipment has both fields set then I assume both companies get credit as far as shipment count and weight.
Lanes:
- Ocean = origin/destination terminals
- Air = airport of departure / airport of arrival/destination
How to calculate cost:
- cost for EA DOM - see Ph1A section.
DR3 Phase 1A: EA DOM Portal only
In this case:
- we report only on Arden USA Domestic shipments that are handled "with a help of TMS"
- E0 = "EA DOM Portal"
- NOTE: we need to add "flag" into the system that clearly defines what CTs are handled through TMS and what are not - see #TMS flag. This is important because cost is calculated / stored differently in our DB for TMS related and other records.
- MOT = "Trucking Domestic"
- let user select this,
- if they select say "Air" with "EA DOM Portal" obviously 0 records would be found. In this case system should display message in red bold "No data found". I suggest post it above menu or in pop-up.
- replace kg with lb in this case
- Tolerance levels parameters:
- in case connected to TMS/ASN is On the I suggest to define #Tolerance levels parameters as Clint Company specific and define these params there
DR3 ph 1A Mock up Main View
TMS flag
In Client Company profile add check box to "Part A. General":
- label: connected to TMS/ASN
Questions
- when/how load cost arrives into CT2 DB?
- A: With Load plan XML? NOTE: this is estimated cost from TMS tariffs not actual billed cost!
DB for load
- tblLoad
- sql/load.properties
Date
use Actual Deliver Date
Company City Note
- show Company
- City Note on Hint
Misc
Some related code is in the system. Please re-use! See Cost_per_pound_KPI_(TMS_based_Arden_)_(solution) .
DR3 Phase 1A1: EA DOM Portal only Main View only
This is a sub-phase of phase 1A.
It characterized by:
- Main View only
- Some features implemented not accordingly to spec:
- weekly / monthly switch (controls axis X on Top Right panel and NOT KPI panel)
- not all admin related functionality is in place
- Carrier logic is different (Pick Up and Delivery segments are presented separately)
DR3 1A1 Admin
On internal:
On Client:
TBD
DR3 Phase 1A2 Dates View
Dates View General Info
- this DR is on additional tab
- name "Lead times" (aka Dates View)
- in user profile it should be defined/managed separately
Dates View Title
Lead Times by Shipper Consignee Carrier Lane.
Dates View Main Menu
- client company E0
- MOT
- specific dates KPI - time ranges between known CT dates, options:
- created to delivered
- approved to delivered
Dates View KPI panel
Dates View Left panel
Dates View Top Right panel
Dates View Bottom Right panel
- mapping:
- created CT date
- delivered CT date
Dates View Mock Up
Work breakdown structure and Change Requests
Sequence
- first 3567, 3575 in parallel
- next 0003583
- next 0003595
3567 DR1 Simple Shipment count DR
- Sasha: Java/SQL
Spec: #DR1 Simple Shipment count DR
3575 Evaluate LogiXML
- Kostya, Vlad
0003583 DR2 Complex Shipment Data per Client per Year DR, PART A
- kostya: SQL, Java b-end
- sasha: b-end, f-end
spec: #DR2 Complex Shipment Data per Client per Year DR, PART A
0003595: [DR/KPI] DR3 Phase 1A: EA DOM Portal only
spec: #DR3 Phase 1A: EA DOM Portal only
