Cost KPIs (cost per unit) (concepts and requirements)
From UG
Contents |
Info
0003034: [Intern&Extern DRs/KPIs]......... <proj>
Business Analysis and Requirements
Summary
The system will have to calculate the total cost and divide it by each unit defined below, so we can provide cost per unit KPI's.
This cost per unit, will be used with additional KPI's that will be added.
Details
Calculating the cost
The total cost for the shipment = the sum of all sales invoices issued against the individual CT record or the group shipments.
This sum should be of sales invoices to a pre-determined bill to party that is linked to the client company viewing the KPI.
Take this total cost and divide it by the desired unit (units listed below) to determine the cost per unit KPI.
Unit fields
- Quantity
- If multiple line items have been created AND the quantity field has been filled in for each, the piece price for each item should be broken out to match these details. The item description and/or SKU and/or PO should be listed as part of this report.
- If a single line or multiple lines with the quantity field only filled out on a single line, then a single piece price is good.
- Pallets
- Packages
- Kilo's chargeable weight
- Kilo's actual weight
- Pounds chargeable
- Pounds actual
- Cubic meter
- TEU
Controlling these reports
We need to offer flexibility in admin, so these reports can be personalized to each users needs.
The reports should be controlled in an admin section created for KPI's.
Operators should be able to enable or disable individual reports or all reports to a specified Client Co.
We will need to create a way to link the E0. Client Company that is viewing these reports, to a specific bill to party. This should not have any effect on any other allowed viewing that is currently set up in the system. This will only be to determine which sales invoices should be included in the total to calculated the cost per unit.
- Operators will have the ability to add or remove related bill to parties.
- Once this link is created, it can only be used for the calculation of the KPIs for shipments that the client company viewing the KPI is the client company of the CT record. We want to make sure we do not open visibility of cost's for shipments that this client company is not involved in.
Explanation Shipments move under specific sales terms, known as incoterms (please see http://en.wikipedia.org/wiki/Incoterms for more information). If the E0. Client company that is viewing the KPI is not paying for all movements of the shipment, they should not be advised of what the other parties cost is. In order to avoid one client from viewing the other clients rates, we cannot include the charges being billed to another party in the total cost calculation
For Example: If the terms are FOB this means the shipper is paying all of the charges until the shipment is on board the vessel. The shipper is ABC Company and they are paying all of the charges to the vessel. The Consignee/Client is XYZ Company and they are paying for the remaining charges. They are also checking the KPI for the piece price. This shipment is 10 pieces Invoice # 1 Bill to: ABC Amount: 25.00 Invoice # 2 Bill to: ABC Amount: 15.00 Invoice # 3 Bill to: XYZ Amount: 100.00 Invoice # 4 Bill to: XYC Amount: 50.00 Invoice # 5 Bill to: ABC Amount: 10.00 Invoice # 6 Bill to: XYZ Amount: 50.00 When XYZ is looking at the KPI for this shipment it should show: Average Cost per piece: 20.00 (This is because we should only be using the sum of the invoices billed to XYZ) (200.00) / (the total pieces) 10.00 = 20.00
These reports will need to be controlled in an Admin section for KPI's. Since we will be providing an average cost per unit, we would need to restrict the system from including shipments that have only part of the cost's billed. Including these incomplete costs would reflect inaccurate information, lowering the average cost per unit. In order to avoid this, we will need to be able to control when these charges are to be calculated. This will be done by using a number of days combined with an action. This should be flexible and able to be changed by each user and for each report.
For Example: Manually entering the number of days and an event date such as arrival date: _#_ Days before or after (radio button) actual arrival date (drop down) Since we will be using this as a standard filter for setting up KPI's, it should include all date fields that are in Cybertrax.
Operators should also be able to set what the time frame for "current" KPI listed on the dashboard, by one of the following.
- Daily (Current should be the result of the previous day starting at 12:00 am and ending at 11:59 pm
- Weekly (Current should be the week before starting Monday 12:00 am - Sunday 11:59 pm)
- Monthly (Current should be the previous month starting on the 1st at 12:00 am and ending on the last day on the month at 11:59 pm
- Quarterly (current should be the previous quarter following the same as above)
- Yearly (current should be previous year following same rules as above)
