An onsite list is just the pack plan but populated with container and wagon numbers for each booking. We send onsite lists daily to Fonterra/CODA to provide a list of what containers are supplied to each of their bookings.
On each pack plan (saved in W: drive) we enter the container number and wagon number associated to each booking into the relevant columns. We then send that pack plan back to Fonterra/CODA as an email attachment the day before packing. Email templates for each site ensure that all relevant parties receive the onsite list, these are located in the W: drive under each packsite’s folder. We will also re-send the onsite list on the morning of packing each day - to verify that everything has arrived to the site as planned, or to notify of any delays to the inbound empties - this is the onsite list confirmation.
For some stores, the onsite list will also confirm the order in which containers/wagons will arrive for packing.
See below for an overview on how onsite lists work by location:
Location
Onsite List Summary
Waikato LCS Export
The bookings team are responsible for sending the LCS onsite list the day before packing as part of the LCS wagon requirements task. The LCS pack plan contains all inbound bookings for the cool and dry stores at Crawford St, as well as the local circuit shunt export sites. These include Te Awamutu, Hautapu and Lichfield (LCHFD only when they operate via the LCS shunt - not the direct service ex TGA). For the purposes of the onsite list, we disregard the cool and drystores at Crawford St (including Canpac) and focus only on the LCS export sites where the containers will be supplied via the local circuit shunts on the morning of packing (TAMTU, HATPU, LCHFD).
Lichfield
When travelling on the LCS shunts, the Lichfield onsite list will be part of the LCS list/pack plan, sent by the bookings team. When Lichfield empties travel on the direct service to/from Tauranga, the Lichfield onsite list will be sent on its own using a separate distribution list; sent by IMEX. We enter the real wagon numbers into this list, rather than the L-wagon 1 etc used when on the LCS shunt.
Whareroa
Currently we send 3 separate pack plans as part of the Whareroa onsite list; one for CFS, one for ‘finished goods’ (dry exports, insulated butter, insulated cheese), and one for CFS (active reefers). We attach all three attachments to the email template. For the CFS and finished goods pack plans; we can send the onsite list as early as two days before packing, since the empties will have departed TGA on their respective services by then – the onsite for these stores is usually sent by the nightshift (following the departure of the C320CFS service ex TGA.) It is also useful to send the onsite list as early as possible so that the yard team have a heads up on how many wagons are coming in and how many need to be cut and shunted into each store. The TSF onsite list will be added and sent the day before packing; once the D534 stow is loaded ex PNTH (usually complete by around midday, departure time 1400).
Pahiatua
Can be sent once the D670 service ex Palmerston North is loaded the afternoon before pack day. This service only travels early on the morning of packing, and can be prone to minor delays. The onsite list confirmation can be updated with an ETA for the service; especially if the service is running late (scheduled ETA is only 08:10 on the morning of packing).
Process Steps:
1.
There is an automated macro that will generate the onsite list emails with the completed pack plans attached (with container and wagon details entered). The attached pack plans should still be double checked before sending. Using the EDI booking query sheet in the Fonterra folder in the W: drive, we can click the appropriate button for each packsite which will automatically generate and fill out the onsite list email for each site, which we can then check and send. Note this also needs to be done in the Citrix environment to allow the macro to work. If not using the automated macro; follow the steps below to complete the onsite lists.
2.
Open the pack plan for the following pack day (on Fridays; the next pack day may be the Monday if the site doesn’t pack over the weekend - Ensure we are in the OPS list tab of the pack plan.
3.
Open the booking data query sheet located in the W: drive - Ensure to open the Citrix environment (required for the macro to run).
4.
Copy all inbound booking numbers from the OPS list of the pack plan into the booking number column of the booking query sheet (ensure the booking number contains the ‘000’ prefix).
5.
Then click “Run Query” in order to populate the list with all of the container and wagon numbers.
6.
If there are issues with the booking query sheet, this will need to be escalated to the digital/IT team to assist. In the meantime, container and wagon numbers can be manually found by entering each booking number into the TRGT screen in Amicus, then copying and pasting from there (unfortunately this will need to be done one booking at a time).
7.
Copy the container and wagon numbers from the booking query sheet or from Amicus, then paste them into the OPS list under the container and wagon columns. For LCS we can just paste only the container wagons and leave the H-wagon, T-wagon etc numbers as-is.
8.
If a wagon number doesn’t show up but the container number does, this shows that a container has been supplied to the booking; but is not loaded onto a wagon. This will need to be checked in CTMS and Amicus to check if the container will still make it to the packsite as planned. We need to be careful with any bookings where a container is gated in and looks supplied; but if it has missed the service it should have travelled on then it will still be a non-supply and recovery may need to be arranged.
9.
In the event that a container is either not gated or will not make it to the packsite in time, we enter “non-supply” into the container column to let CODA/Fonterra know that the container will not be provided on that pack day for their planned packing. A container could be non-supplied for several reasons, e.g:
If a customer or depot issue has caused the container to miss its inbound service (e.g. the depot provide a container after the rail cut-off/departure).
If a customer or depot issue has meant that the booking has not been supplied a container (e.g. a loadout issue means the depot doesn’t provide a container at all to a booking).
If a KR issue has caused a supplied container to not travel as planned, e.g. an incorrectly scheduled booking means that a container travels on the wrong day and misses packing, or an unforeseen delay such as a cancellation or derailment causes the containers not to arrive for packing in time.
10.
Once the pack plan has been populated with all the container and wagon details, we save that copy of the pack plan as the most recent copy, then attach it to the onsite list email using the template located in each packsite folder. Ensure the date in the subject and body of the email are updated to match the correct packdate before sending. We also receive a copy of the email so this can be filed to the appropriate packsite subfolder in the CODA inbox.
