tracking

[Ruth]

Hi

We shipped product from various locations to various locations.

We have a data base in excel that keeps tracks of trips. In it we have a
trip number, load location, and unload locations with the dates and times
that a voyage is taking place. The schedule changes everyday, at least once
a day, there are 15 vessel to keep track of. Due to traffic, weather etc.
we switch the schedule, but we keep the trip numbers sequencial.

Looks like this

Trip No Name load load Unload
Unload 001 MIS 02-08-08 12:00 SAR 02-09-08
02:00 MEL
002 MIS 02-10-08 14:00 STO 02-10-08 21:00 MRB
001 SUE 02-07-08 07:00 KGV 02-07-08 23:00 FHA
002 SUE 02-04-08 06:30 KGV 02-04-08 20:00 FHA


We need to have a way to track when a trip has moved, what date it started
and the date it was moved to, but the trip number has to remain sequential.
We also need to keep track as to why it changed.

I was thinking of adding columns, one with a trip tracking number which
would be the same as the trip number when it was created, and seperate colums
for reasons. That way we can see when it first was scheduled and when it was
actually completed. Is this a good idea? Is there a better way? Is there a
way that can keep track of all the moves and the reasons for the moves?

 

[iliace]

When you have a database, it is best to have separate tables to
identify your entities, or objects. It seems like you have two things
going on - shipments, and shipment schedules. Each data row in the
shipments table should identify information regarding shipment only,
not about its schedule. The schedule, in turn, should identify the
shipment and the time during which it was scheduled. Any rescheduling
action should be reflected as a new record in shipment schedules. You
can then pull out the latest date for any particular shipment.

As far as a "better way" is concerned, I would recommend an Access
database rather than a spreadsheet. You can find many template
databases online that handle tracking for this kind of scheduling/
rescheduling activities. They may not be designed for exactly your
industry, but it's fairly easy to adapt one of the existing ones
simply by renaming a few form controls and field names in tables.

 

[Ruth]

Thank-you!
--
Thank-you!
Ruth

When you have a database, it is best to have separate tables to
identify your entities, or objects. It seems like you have two things
going on - shipments, and shipment schedules. Each data row in the
shipments table should identify information regarding shipment only,
not about its schedule. The schedule, in turn, should identify the
shipment and the time during which it was scheduled. Any rescheduling
action should be reflected as a new record in shipment schedules. You
can then pull out the latest date for any particular shipment.

As far as a "better way" is concerned, I would recommend an Access
database rather than a spreadsheet. You can find many template
databases online that handle tracking for this kind of scheduling/
rescheduling activities. They may not be designed for exactly your
industry, but it's fairly easy to adapt one of the existing ones
simply by renaming a few form controls and field names in tables.