COMMANDoptimize: Maintaining & Tuning Your System Andrew Dyment [email protected] (905) 870 1410

COMMANDoptimize: Maintaining &

Tuning Your System

Andrew [email protected](905) 870 1410

MGT-002 COMMANDoptimize: Maintaining & Tuning Your System2

• This session is designed for customers that have implemented Optimization in their operations and are looking to keep their costs and configuration current and fine tune their results. This session will also benefit those who have not implemented Optimization yet, but would like to see more of the technical aspects to tuning the system.

Session Objective

Agenda

• Maintaining Your COMMANDoptimize server

• Maintaining your COMMANDseries data

• Tuning Your COMMANDoptimize system

• Tuning OCMI


Maintaining The Server

• Take backups of the COMMANDoptimize server-CSIS folder-Ortec Folder

Given the above , the rebuild is a straight forward and short in duration

• Install Packages Required – CmdFleet, OrtecLicenceServer

• Institute a periodic reset/reboot of your server

• Be on a regular update process


Maintaining The Server

• Enable CSIS’s Queue Monitor


CSIS’s Queue Monitor

• Located on your Optimization server

• Use the same eMail setting as your COMMANDfleet server

• Configuration Program is usually in the CSIS->Configuration folder

• MSMQ’s are used to move COMMANDnetwork messages between CmdSeries and OCMI

• If the messages are being created but not consumed, that is a indication that a module is not running

• Use a threshold of 50 messages to start with


Maintaining The Data

• Loading Speed Setup• Plant Loading Speed• Projects• Item• Resource Attributes• Employee• Truck • Map Pages• Costs



• Loading Speed Setup (CmdSeries Files->Plant and Delivery)

• Load time is calculated Overhead + (LoadSize*Per Unit Time)

• Mix time in Yard is the Post Load Time

• Multiple Loading Speeds Per Plant

• Alternate Speeds for Mixes/Batchman/Mechanical issues

• Be careful and use actual plant performance






Plant Loading Speed


Plant Seniority Group


All drivers and trucks inherit the

seniority group of the plant they are

assigned to

Plant Seniority Group


Pre Load time must align with CM

setting

Plant Map Page


Map Page must match with CM

Currently no two plants can be on the

same Map Page

Important to travel times on Plant’s

Map Page

Plant Map Page


ScheduleCom Company must match

with company id in ScheduleCOm


• Projects-GPS


Project Setup


Project Setup


Defaults into the order


• Projects-Priorities



• Item-Constituent Costs



• Item-Use Order Entry to view



• Resource Attributes CS08 2.13


• Employee



Schedule Driver Vacations Assign Driver Attributes


• Employee Attribute Setup

• Employee Off Time



• Truck Alternate Capacities



• Truck Attributes (CS08 2.13)




Order Entry- Schedule Requirements


Map Pages Setup

- Comm Process to update Map Pages

- Parameters are tuned

- If you move a plant, get new default times

- If you add a plant, get new default times



Costs


Costs

• Base all costs on real data


Costs


Day Costs

• The fixed cost that is attributed to bringing in an additional truck.

• Include Daily benefit charge

• Do not include all the minimum hours

• Include Minimum hours – Ave RTT


Tuning COMMANDoptimize


Tuning Your System

• Need Baselines!

• Need Targets!

• Need a process to bridge your Baselines to your Targets

• Need to tune the Optimizer to reflect our current efficiency

• Need to monitor your results

• If you are not doing the above, Go no further



• Why do we need to continually tune COMMANDoptimize?

• Who should be tasked with the role?

• When should we review the settings?

• Where are all the tuning parameters?

• How do you tune the system?

Tuning Agenda

Who should Tune COMMANDoptimize?

-One person-Champion -Full understanding on what goes into generating the plan


When should we review the settings?

-it is not your settings, but your results that need reviewing.

-if you see an opportunity



Key Field Name Field Description

Y UNIQUE_NUM Unique Number

RECORD_DATE Record Date/Time

ORDER_DATE Order Date

REGION_CODE Region

ORDERS Total # of Orders

ORDERS_SCHEDULED # of Orders Scheduled

LOADS_SCHEDULED # of Loads Scheduled

ORDERS_UNSCHEDULED # of Orders Unscheduled

FOB_ORDERS Total # of FOB orders

QTY_UOM All Quantities UOM

TOT_ORDER_QTY Total Order Yardage

TOT_ORDER_QTY_SCHEDULED Total Order Yardage Scheduled

TOT_ORDER_QTY_UNSCHEDULED Total Order Yardage Unscheduled

TOT_FOB _ORDER_QTY Total FOB yardage

TOT_FOB_LOADS_SCHEDULED Total FOB loads

DISTANCE_UOM Distance UOM

TOT_DISTANCE Total Mileage Driven

NUMBER_OF_PLANTS # of Plants Used

PLANT_CODES List of Plant codes

AVG_LATENESS Ave Lateness

MAX_LATENESS Max Lateness

AVG_STARTUP_MINS Ave Startup Tm

AVG_ONJOB_WAIT_MINS Ave Wait Tm

AVG_UNLOAD_MINS Ave Pour Tm

AVG_WASH_MINS Ave Wash Tm

AVG_SHUTDOWN_MINS Ave Shutdown Time

AVG_RTT_MINS Ave RTT

NUMBER_OF_TRUCKS # of trucks used

AVG_TRUCK_CAPACITY Ave Truck Capacity

AVG_MATL_COST Ave Material Cost

TOT_DRIVER_HOURS Total Driver Hours

KPI Table

OCMI


Break Push Out

– Minimum amount of time before a tasked truck is available

- 5 minutes is a good starting point

OCMI


Maximum Route Distance- Any plants further away will be excluded

Closest Plant will not

OCMI


End Of Day Tasks

– Tasks that will cause the truck to be taken out of service

OCMI


Minimum Status Age

– Any status older than this time will not be forwarded to CM

OCMI


Deadhead Time

– Time the truck will be dedicated to the deadhead plant

OCMI


Delay Availability

– Driver will no assigned call in time will have a unavailability based on this parameter

OCMI


Plant Locking

– Determines the amount of time the Optimizers suggested plant for a truck is locked in

CM-INI Files

INI files – Optimization Server

Tips.iniTipsLocal.ini


TIPS.INI

Parameter: MaxFreeVehicleTime

This parameter determines that amount to yard time a truck may have until it starts to calculate a cost. The tuning of this parameter will mitigate washing local trucks out and deadheading foreign trucks into yard.


TIPS.INI

Parameter: WeightRestVol

This parameter specifies the factor applied to the remaining quantity of an order once CM starts to consider the order’s next load. It is based on the idea that it is preferable to spread the delivery of an order over a smaller number of trucks even if this would mean waiting for larger trucks, so that final “under-sized” loads are minimized. If the parameter is set below 0, CM will focus more on getting the current load scheduled


TIPS.INI

Parameter: WeightFollowUpDelivery

This parameter specifies the factor applied to the lateness cost for loads that are not the first of an order. This parameter is based on the idea that once deliveries have begun on an order, subsequent loads should be subject to even higher lateness penalties than usual. The higher this parameter, the less CM accepts lateness between deliveries of an order.


TIPS.INI

Parameter: NOrderForMatching

This parameter specifies the number of ‘next’ loads that are taken into account when deciding which truck and plant should be scheduled for the current load. This parameter highly influences performance – the higher the number the slower the performance


TIPS.INI

Parameter: LatenessSteps

LatenessSteps: The number of steps to factor into the lateness

calculations

LatenessStartPointX:LatenessValueX:Values used to plot lateness graph and calculate

lateness amount to be used in calculations


TIPS.INI

Parameter: LatenessSteps


1 2 3 4 5 6 7 8 9 10111213141516171819202122232425260.00

200.00

400.00

600.00

800.00

1000.00

1200.00

1400.00

1600.00

1800.00

Priority # 1

Priority # 2

Priority # 3

TIPS.INI

Parameter: CorrectionCostCostPerHour

Factor used to multiply hourly cost for rental trucks in real-time scheduling to decrease usage of rental trucks once they report in service.


TIPS.INI

Parameter: IgnoreFixedCostPeriodRealTime

When this value is set to 1 the daily fixed cost will be ignored for the current day plan.


TIPS.INI

Parameter: MaxMortarAge

All plants that would cause the concrete to exceed the set age will be excluded (except the closest plant)


TIPS.INI

Parameter: CostForNewOrderForTruck

Cost applied to vehicles that has not been to the jobsite already. The higher the value, the more trucks that have been to the jobsite will be favoured


TIPS.INI

Parameter: ExpectedRoundtripDelay

With this parameter an expected delay (in min) in delivering the loads can be specified and will be used to extend the Wash Time at the jobsite, as long as unloading is not finished.


TIPS.INI

Parameter: DelayForBusyTruck

This parameter specifies the minimum time that CM calculates for a truck’s return time.


CM System Administration

Parameter: Call in Report – Driver prepare time

Amount of time that the call in times must compensate for a driver to be inservice from the call in time.


CM System Administration

Parameter: Time from which home location will must be taken into account

This is the time of the day where the Optimizer will put more emphasis on bringing trucks back to their home yard.



Please Complete Your Evaluation

• Be sure to circle the session you are evaluating on the back of your card– MANAGEMENT (Track Name)– MGT-002 (session code)– Maintaining and Tuning COMMANDoptimize (session title)

• Thank You!

• All breakout session materials can be accessed at: www.commandalkon.com/cc2011/update/index.htm

http://www.commandalkon.com/cc2010/update/index.htm

Documents

COMMANDoptimize: Maintaining & Tuning Your System Andrew Dyment [email protected] (905) 870 1410