MILK CONTROL module

Introduction

The MILK CONTROL module is a map based Geographic Decision Support System (GDSS). It displays suppliers on a map of the collection and shows the volume and quality of milk available at each supplier. The purpose of the Milk Control module is to display the patterns of milk supply in order to facilitate the milk control process.

Each supplier location on the map has associated with it information relating to milk volume, composition, quality, quota etc. By pointing at a supplier's location on the map (via a mouse or other pointing device) the user can view this information. The size, colour and shape of the symbol displayed at each supplier location can be varied depending on this information so the user can view or print a map showing the distribution of a parameter e.g. butterfat adjusted quota position.

On the map the user can select the suppliers that he proposes to allocate to a particular group (e.g., truck, depot). As the user does this the consequences in terms of volume of milk and milk quality for the group are displayed. As the user switches suppliers between groups the relevant statistics are immediately updated.

Data display

In the MILK CONTROL module it is possible to associate data relating to suppliers’ data with the suppliers’ location on the map and to display it by pointing at the supplier location. A typical example would be to hold information on

Supplier name

Telephone number

Supplier code

Volume collected at most recent collection

Temperature of most recent collection

Butterfat for most recent test

Protein for most recent test

Lactose for most recent test

TBC for most recent test

SCC for most recent test

Total supplies to date

Quota

Reference butterfat

Butterfat adjusted quota position( % of quota used)

Below are these details displayed by the screen for a sample supplier :

Fig. MC1: Typical Information behind Supplier location

For volume, butterfat, and butterfat adjusted quota position it is possible to vary the symbol displayed at a suppliers position on the map to reflect the value of these parameters. This can be done by having the size of the map symbol proportional to the value of the parameter or by colour coding the map points depending on the value of a given parameter at that point. A combination of both these techniques allows two parameters to be displayed at once:

Fig. MC2: Map showing the distribution Protein

The map displaying the distribution of parameter values in this way can be printed.

It is also possible to highlight suppliers that meet certain requirements e.g. butterfat greater than 4.0% and collection volume greater than 2300 litres.

Allocation to groups

The MILK CONTROL module allows the allocation of suppliers to groups. For each group the total volume of milk at last collection, total quota, and average quality( based on last laboratory test result and weighted by last collected volume) is displayed. Suppliers can be allocated to a group or transferred from one group to another simply by selecting them with the mouse. This can be done by pointing and clicking at an individual supplier. Alternatively a number of suppliers can be selected by dragging a circle or rectangler or by drawing a polygon around a number of suppliers.

Fig. MC3: Map showing supplier allocation to groups (colour of symbol) also displaying supplier volume (size of symbol)

Fig. MC4: On screen display of summary information relating to groups

TRANSPORT PLANNING module

Introduction

The TRANSPORT PLANNING module is a map based GEOGRAPHIC DECISION SUPPORT SYSTEM (GDSS ). It is designed to support decisions in the control and planing of milk transport operations.

The TRANSPORT PLANNING module displays the supplier locations on a map of the collection area. Associated with a supplier’s location on the map is information on that supplier in terms of volume, quality, quota etc. By pointing at a supplier's location (via a mouse or other pointing device) the user can display this information. The size, colour and shape of the symbol displayed for each supplier can vary depending on this information so the user can view or print a map showing the distribution of a parameter e.g. butterfat, quota position.

The historical milk collection routes can also be displayed on the map. A summary of the information about the routes can be displayed e.g. volume of milk on each route, length of each route. The user can select the suppliers that he proposes to transfer from one route to another. The consequences in terms of milk volume and quality on the route is immediately displayed. The optimal sequence for collecting the new routes can also be calculated.

Alternatively the user can set up a collection plan from scratch. In this scenario, the scheduler is drawing on his personal experience to manually construct feasible new plans reflecting the numerous and complicated factors involved.

Supporting the Scheduler

The philosophy behind the TRANSPORT PLANNING module is to support the scheduler to more effectively carry out his task. The system supports the situation where the scheduler is modifying an existing collection plan or where he is designing a completely new collection plan.

When modifying an existing plan the scheduler can use the actual volumes collected or can used planned milk volume got by adjusting the historical values by a some % to take account of expected changes in milk volumes.

Where the scheduler is modifying an existing plan the scheduler can display the historical routes on a map of the collection area. He can also display summary information on the route driven:

No of suppliers on route

Volume collected

Truck capacity

% utilisation

Expected % butterfat based on most recent sample for suppliers on the truck

Expected % protein based on most recent sample for suppliers on the truck

Fig. TP1 shows an example of a typical route display screen:

Fig. TP1: Screen displaying historical routes

The scheduler can see also the consequences of the planned milk volumes for the existing plan. By pointing and clicking he can transfer suppliers from one route to another and see immediately the consequences in terms of the above parameters. Based on the road network MAPS2000 can calculates the optimum sequence to collect the suppliers on the routes and also the distances and times involved. A more detailed look at route 2 above, for example is shown in Fig. TP2:

Fig. TP2: Detailed display of an individual route

This route has been optimised using the road network and the sequence of the route can be displayed and printed (See Fig. TP3)

If the scheduler is calculating a new sequence of routes from scratch then MAPS2000 displays the planned collections on a map of the collection area. Suppliers can be allocated to a route or transferred from one group to another simply by selecting them with the mouse. This can be done by pointing and clicking at an individual supplier. Alternatively a number of suppliers can be selected by dragging a circle or rectangle or by drawing a polygon around a number of suppliers.

Fig. TP3: Display of an optimised route

The system handles multi-compartment trucks and different product types. It will automatically display loading plans for multi-compartment trucks. Truck details can be inputted into the system reflecting all the above variables. An individual truck graphic is created for each truck showing the levels and types in each compartment. Any given route or selection of suppliers can be loaded onto a truck manually or automatically and the change in levels are reflected as the assignment proceeds. Here is an example of a truck graphic displaying levels:

Fig. TP4: Screen showing loading of a multi-compartment truck

Integration

The TRANSPORT PLANNING module links directly with the planning section of the TRANSPORT MANAGER module. Plans developed in the TRANSPORT MANAGER module can be displayed and manipulated in the transport PLANNING module.

TRANSHIPMENT MANAGER module

Introduction

The TRANSHIPMENT MANAGER module is a map based GEOGRAPHIC DECISION SUPPORT SYSTEM (GDSS ). It is specifically designed to support decisions in the control and planning of large scale milk transport operations involving milk transhipment. The motivation for the development of the MILK TRANSHIPMENT module was the complexity inherent in the transport of milk from farms to demand centres via reload depots.

The TRANSHIPMENT MANAGER allows the option to either transport milk directly from a farm to a Dairy (ex-farm collection) or to reload in an intermediate depot location and then tranship it from this location to its ultimate destination.

For any planned transhipment pattern the associated costs are displayed on the screen. The system can calculate a transhipment plan which minimises transhipment costs.

Data Structures

The TRANSHIPMENT MANAGER displays the locations involved in the problem on a map of the region

The locations from which the milk is to be collected, called SUPPLIERS.

The locations of the ultimate destinations of the milk, called DAIRIES/FACTORIES.

The locations of reload points, called DEPOTS

Associated with each of these locations is the information relating to the location.

The data associated with each Supplier location includes Name, Number, Volume of Milk, Collection Route and the Depot/ Factory to which the supplier is assigned.

The data associated with each Depot location includes Name, Number, Capacity, Total Daily ex-Farm Milk Volume In, Volume Remaining ( total volume in, less amount being transhipped ) and the cost of transhipment operation from depot.

The data associated with each Dairy/Factory location includes Name, Number, Capacity, Critical Daily Volume which must be filled, Total Daily Milk Volume In (Ex-farm + transhipped), Transhipped Volume In, Volume required to fill critical level and cost of transhipment operation to the dairy.

In addition, data is held on the links between depots and factories. The static information associated with these links are source depot, destination factory, unit cost of transport and distance. If these links are used then dynamic information on Volume transhipped on link, litre-miles and transport cost is held. A line is drawn on the map whose thickness reflects the volume of milk moving on the link.

Allocation to a Depot / Factory

The TRANSHIPMENT MANAGER allows suppliers to be manipulated in additional ways to that those available in the TRANSPORT PLANNING module.

Suppliers can be allocated to depots. This can be done by selecting suppliers either by pointing at them on the map or by drawing a line around a group of suppliers. The selected suppliers can then be allocated to depot. It is also possible to assign the routes created in the MILK TRANSPORT manager to a depot. This has the effect of assigning all the suppliers on the route to the depot.

As suppliers are assigned to a depot the consequences for the depot in terms of milk volume are automatically updated. This updated information is displayed on the screen by means of a bar chart at the depot location( See Fig. TS1).

It is possible to review on the screen the data associated with the depot, the supply situation for all depots or to see a list of all suppliers allocated to a particular depot (See Fig. TS1).

The same functionality also exits for Dairies/Factories. Suppliers whose milk is to be delivered ex-farm can be assigned to the appropriate dairy. In order to distinguish them from depots dairies/factories are represented on the map using a pie-chart (See Fig. TS2). The size of the pie-chart reflects the processing capacity of the dairy.

Fig. TS1: Allocation of suppliers to reload depots

The example we are showing is the Athy Depot. On the map we can see the locations of the 46 farms currently allocated to Athy. There is a list of these farms and also a list of all depots showing the number of suppliers associated to each and the total volume of milk for each.

Transhipment

A transhipment plan is inputted by indicating for those depot/dairy links that are to be used the amount of milk that is to be transported on that link. This is easily done via the screen (See Fig. TS2). Before creating the link the system checks that the transfer it is feasible given the volume of milk at the depot and the capacity of the dairy.

A line is drawn on the map between the depot and the dairy whose thickness is proportional to the volume of milk being transferred. The consequences of the transfer for volume at the depot and the dairy are immediately displayed on the screen. The implications for transhipment costs is also displayed (see Fig. TS2). If required, the system will produce a transhipment plan that minimises cost.

Fig. TS2: Transhipment links and costs

ROUTE ALLOCATION module

Introduction

The ROUTE ALLOCATION module is for optimally allocating milk collection routes between a number of processing plants so as to meet the requirements of the plants at minimum transport cost.

The system can handle the reloading of the ex-farm tankers into reload tankers for transhipment over long distances. It will determine the best allocation of ex-farm routes to processing plants and reload locations and the best allocation of loads from reload locations to plants.

The system takes account of the restrictions at processing points in terms of the maximum and minimum volumes that can be delivered, the type of vehicle that can be handled, and opening times. It takes account of the restrictions on each route in terms of the feasible delivery locations for the route. It also takes account of the resources available at each reload site.

The user can set up additional restrictions, to be taken into account in the optimisation, on the volume of milk that a plant is to be supplied with. The optimal solution is displayed on a map of the collection area. The user can manipulate the solution after the optimisation process is completed.

The Problem

The ROUTE ALLOCATION module takes as an input all the ex-farm routes to be delivered on a day and the possible delivery locations for each route. This information can be inputted by the user. Alternatively if the user provides for each ex-farm route details of

· the location where the load becomes available (e.g. last supplier on the route, the depot),

· time available to make a delivery,

· the location where the truck has to be at the end of the delivery ( e.g. first supplier on the next route, depot ),

the system will determine the possible delivery locations taking into account the drive time to the location, the time to make the delivery and the time to drive to the next location for the truck .

The third option is to use as a base an actual day as stored in the MILK MANAGER module. The system will then determine the feasible delivery locations for the routes driven on that day. The user can adjust the volume on each route to reflect changes in milk volumes since the base day.

Information Stored

The system allows the user to enter for each processing plant

Name

Number

Location

Details of Milk Supply Contracts

Target Delivery

Maximum Delivery

Minimum Delivery

Opening time

Closing time

Number of discharge bays

It is also possible to store delivery window data by day of the week.

For each reload location the user can enter details on:

Name

Number

Location

Number of Tankers, their capacity and running costs

For each ex-farm route the module stores information on:

Depot/haulier

Truck Reg

Truck Type

Milk Volume on route

Last Supplier on route identification

Time at last supplier

Geographic location of last Supplier

Available time to make delivery.

Required location at end of delivery (e.g. First supplier on next route, depot )

Geographic Map Base

A feature of the ROUTE ALLOCATION module is the geographic base for the system. This environment allows the various locations involved in the problem to be displayed on a map of the region.

The items located on the geographic map include :

The locations from which the milk is to be collected, called SUPPLIERS.

The locations of the ultimate destinations of the milk, called DAIRIES/FACTORIES.

The locations of reload points, called DEPOTS

Associated with each of these locations on the map, information relating to the location can be displayed using such functionality as ZOOM and POINT.

The data associated with each Supplier location includes Name, Number, Volume of Milk, Collection Route and the Depot/ Factory to which the supplier is assigned.