1. Enter future fleet size changes into the Planning Calendar. These changes include:
a. Anticipated purchases of new units.
b. Anticipated sales of existing vehicles.
c. Temporary additions or subtractions of units
d. Anticipated transfers of vehicles from one location to another. (One-way RAs and Non-Rev tickets automatically update the fleet on the Planning Calendar.)
e. Counter-balancing entries to reverse previously entered adjustments.
f. Edits to previously entered adjustments.
2. Reset the fleet size carried in the Planning Calendar to the actual number of units on hand.
The "Default" option erases scheduled changes and sets the vehicle count to the number of units currently on hand at each location.
3. Update the Planning Calendar for a future new Vehicle Class that is added to the fleet.
When a new Class is planned to be added to the fleet and there is a desire to set it up in advance so that reservations can be taken against the new class, it is necessary to update the Planning Calendar. To do so, perform the following steps
Set up the Class in Edit Vehicle Class codes.
Enter a record here for the location with the date that the units are expected as the Start Date. Use the "ADD" operation in Field 4.
Run the Recalculate Class Needs program.
An extensive discussion of the Planning Calendar logic and the affect this program has on the calendar can be found in the chapter of the manual titled Introduction to Fleet Planning. The concepts presented in that chapter should be read prior to using this program.
WARNING: A field in the Edit Misc. Control Fields record can turn on a feature where the vehicle grounding date or
eligible date is used by the planning calendar (Class Availability) to
mark the unit's exit from the available fleet. If this feature is used, units should NOT be deducted from the planning calendar based on their grounding or eligible date using Change Class Availability. Doing so will double the reductions.
To
access the Change Class Availability program, type CHGFUT (RET) at any menu "OPTION:" field or the appropriate line number on the Fleet
Planning menu. The screen will
then display:
| OPTION: __ CHANGE CLASS AVAILABILITY 1 Location TUS 2 Class 3 Start Date 11-01-11 4 Buffer Date 5 End Date 6 Operation ADD 7 Amount 8 Description 1BEGIN 2 3 4 5BACKUP 6 7HELP 8 |
Enter data as follows:
|
1. LOCATION |
Enter up to 6 alphanumeric characters to indicate an individual Location code. EXAMPLE: Type TUS (RET) User tip: Although the Planning Calendar reporting is generally done at the Location Group level, the Planning Calendar data itself is stored on the individual Location level. Therefore, if a Group Code is used in this field, the adjustment will affect every location in the group. For example, if 50 compact cars are added, 50 cars will be added to each location in the group. It is, therefore, recommended that an individual Location Code be used in this fie1d. |
|
2. CLASS |
Enter up to 4 alphanumeric characters to indicate the vehicle class affected. EXAMPLE: Type CCAR (RET) |
|
3. START DATE |
Enter the date that the change in fleet size will occur. Press RET to default to today's date. For records with a start date and no End Date (see Field 7), once the Start Date has been passed, the record will not be read by the system any more. It is assumed that the expected addition or subtraction has actually happened and so the actual fleet itself now has been impacted by the change. EXAMPLE: Type 112515 (RET) Modifying a record: If there is already a record with the location, class, and start date, the record will load so that it can be edited. This is noted with the message MODIFYING EXISTING RECORD at the bottom of the screen. To cancel a record, enter zero in the "Amount" field. |
| 4. BUFFER DATE | This field along
with Field 3 above define a range of dates during which the action is expected to take place. That is:For ADDs: new units are expected to be received into the active fleet between the Buffer Date and the Start Date. Although for Planning Calendar purposes, the expected units cannot be reserved until after the date defined in field 3, if a new unit of the class defined in Field 2 at the Location defined in Field 1, has it's in-service date set to a date that falls between these two dates, the system assumes that the new unit is one of the expected units defined here. As a result, the number of expected units in Field 7 will be decreased by one. For more, see the screen illustrations and explanations at the end of this chapter. EXAMPLE: Type 111515 (RET) |
| 5. END DATE | This field is used when the additions or subtractions should be temporary. Use the date in Field 3 to define the start of the period and the date in this field to define the end of the period. As of the End Date, the temporary addition or subtraction will be dropped. |
|
6. OPERATION |
ADD = Vehicles will be added to the location. SUBTRACT = Vehicles will be subtracted from the location. DEFAULT = Vehicle counts in the Planning Calendar will be reset to the current number of units on hand. All future purchases and sales that have been entered by the ADD/SUBTRACT options will have their impact erased for the time being.
EXAMPLE: Type ADD (RET) |
|
7. AMOUNT |
Enter up to 3 numeric characters to indicate the number of vehicles involved in the change. If the "DEFAULT" operation was selected in Field 6, this field is then left blank. EXAMPLE: Type 10 (RET) |
| 8. DESCRIPTION |
Enter up to 20 alphanumeric characters for a description which is shown on the Print Fleet Adjustments Report. EXAMPLE: Type WINTER FLEET (RET) |
PRESS "F1" AT "OPTION:" TO BEGIN THE OPERATION.
MORE INFORMATION ABOUT THE BUFFER DATE LOGIC
| OPTION: __ CHANGE CLASS AVAILABILITY 1 Location TUS 2 Class CCAR 3 Start Date 11-25-15 4 Buffer Date 11-15-15 5 End Date 6 Operation ADD 7 Amount 10 8 Description WINTER FLEET 1BEGIN 2 3 4 5BACKUP 6 7HELP 8 |
This record indicates that 10 additional class CCAR units are expected at Location TUS by November 25th. The first of these may arrive as early as November 15th as part of the Winter fleet purchases.
If a CCAR is in-fleeted at location TUS on 11/16/15, with it's in-service date between 11/15 and 11/25, the system will assume that it is one of the 10 expected during that period. Not only will the new unit be added to the working fleet, but the system will then subtract one from the 10 in the above record to reflect that now only 9 more are expected. As the order trickles in during mid November, this record will continue to be adjusted down. If no record is found in this file for a unit that is in-fleeted, no adjustment is made to this file.
Note: The key to this logic is the In-Service date. If for an example, the vehicle was infleeted into the LAX location yet the In-Service date is not set, the adjustments for LAX in this file are not changed. If after being prepped at LAX the unit is then moved to the TUS location and at that time, the In-Service date is set, the adjustments for TUS are decremented by one on that date.
Units put into service before the Begin Date are assumed to NOT be part of the expected order.
| OPTION: __ CHANGE CLASS AVAILABILITY 1 Location TUS 2 Class CCAR 3 Start Date 04-25-16 4 Buffer Date 04-01-16 5 End Date 6 Operation SUBTRACT 7 Amount 6 8 Description WINTER FLEET REDUCTION 1BEGIN 2 3 4 5BACKUP 6 7HELP 8 |
This record indicates that 6 units of class CCAR units are expected to be removed from the fleet at Location TUS by April 25th. The first of these may be sold as early as April 1st as part of the Winter fleet reduction.
If a CCAR is sold at location TUS on 4/16/16, with it's sale date between 4/1 and 4/25, the system will assume that it is one of the 6 expected to be sold during that period. Not only will the unit be removed from the active (reservable) fleet as of the sold date, but the system will then subtract one from the 6 in the above record to reflect that now only 5 more are expected to be sold. As more units are sold in April, this record will continue to be adjusted down. If no record is found in this file for a unit that is sold, no adjustment is made to this file.
Units sold before the Buffer Date are assumed to NOT be part of the expected order.When entering anticipated transfers of vehicles from one location, two entries are required:
The first entry should SUBTRACT vehicles from their present location.
The second entry should ADD the vehicles to the new location.