Activity Definitions

This page is accessed via Shipment Management > Power Data > Calendar > Activity Definitions.

Activity Definitions define the types of transportation related actions that can occur at a location. Associate activities with calendars and use them to define what can occur during a particular time period. For example, define a location with the activity Office Hours between 8 a.m. and 7 p.m. each day.

Note: The following is a list of valid activities you can use when creating a calendar. You can create new ones, but they would be for information only and would not impact planning.

• Activate indicates a time period during which an itinerary is valid. This activity is only used on annual calendars.

• Note: If the calendar will be used on an itinerary, you must have an Activity of ACTIVATE.

• All when used in location capacity, matches all shipment activities when finding applicable shipments for the capacity constraint and when determining the capacity of the shipment.

Note: This is only for use with location capacity and does not mean 'ALL Activities'.

Note: 'ALL' should not be used to define driver availability, only Driver Work is checked for driver availability.

• Closed not used.
• Depot: activity is only used to define a type of location capacity. For example, if the location can handle at most 10 depot shipments at a given time bucket, you can set a location capacity with an activity of Depot.
• Dispatch not used.
• Driver Work is the only activity checked to determine if a driver is available. Note that the "ALL" activity does not imply driver's availability.
• Free Hours allows you to indicate that time is free of a demurrage charge when associated with a calendar used in calculating chargeable days for demurrage rules.
• Liveload not used.
• Load indicates that the location is open for loading goods onto equipment. This activity cannot be used with interim legs.
• Office Hours is used by the service provider to indicate that the location is open for receiving phone calls, email, faxes, etc. The office hours for the location are considered when routing pickups and deliveries. The tender time out clock does not run against the location during non-office hours. For example, if Oracle Transportation Management tenders a load at 11:00 p.m. to a location with office hours of 9:00 a.m. - 5:00 p.m., then the tender time out clock does not start running until 9:00 a.m. the next morning. Also, if a load was tendered to the same location at 3:00 p.m., then 2 hours would be taken off the tender time out clock that day, and the rest would be taken off starting at 9:00 a.m. the next morning.
• Other means interim stop or via point stops; no pickup or dropoff at these stops. Interim stops model border crossing points as such. Via points are for arbitraries where on one shipment there could be more than one service provider.
• Pickup is used in calendars for Day Duration service time. The PICKUP time is the latest time the service provider can pick up goods for transport.
• Receive indicates that the location is open for receiving goods. This activity cannot be used with interim legs.

• Rushhours is used to handle congestion around metropolitan areas. To make it work, you can set up an accessorial (e.g.: "RUSH_HOURS-NE") on locations such as NYC, Boston, Washington DC., then on some rate service (e.g. TL-RateService), set up rate service accessorial time with accessorial code ("RUSH_HOURS-NE": note the accessorial code on rate service should match that on location), a calendar defining rush hour time period (e.g., 4pm-7pm), activity ID ( e.g.: "RUSHHOURS") and accessorial time (e.g.: 2 hours). Note: the activity ID in the calendar that defines rush hour times should match the activity ID that is defined in rate service accessorial time. For example, if a shipment leaves or arrives in NYC between 4pm-7pm, add 2 hours to its total transit time. (Defined in Public domain.)

Depending on what business object you associate your calendar with, different activities should be used.

• When determining the arrival time and departure time at a stop, the planning logic uses the LOAD and RECEIVE activities in calendars on locations.
• For dock scheduling, the activities that work are LOAD and RECEIVE.
• When calculating "Day Duration" service time, the PICKUP and RECEIVE activities are used. The PICKUP time is the latest pickup time and the RECEIVE time is the guaranteed delivery time. For example, FEDEX overnight may have a pickup time of 5:00 p.m. and a receive time of 10:30 a.m.
• OFFICEHOURS is used by the contact for a service provider to indicate that the location is open for receiving phone calls, email, faxes, etc. The location determines how to route pickups and deliveries. The tender time out clock does not run against the location during non-office hours. For example, if Oracle Transportation Management tenders a load at 11:00 p.m. to a location with office hours of 9:00 a.m. - 5:00 p.m., then the tender time out clock does not start running until 9:00 a.m. the next morning. Also, if a load was tendered to the same location at 3:00 p.m., then 2 hours would be taken off the tender time out clock that day, and the rest would be taken off starting at 9:00 a.m. the next morning.
• CLOSED, DISPATCH, and LIVELOAD are not used.