Each Center shall establish a baseline TAV. This means ensuring only an optimal mix of vehicles is assigned and maintained. Having the right size vehicle fleet is an OMB concern; therefore, Agencies should not miss potential opportunities for savings. The following process/factors should be considered as each Center develops its vehicle baseline:
Require each customer to submit a written justification for each additional assignment using NASA Form 971. Evaluate each submission, focusing on what the vehicle is used for in terms of passenger movement, cargo movement, material movement, or mission essentiality of the vehicle. Look at why requirement can not be met with other means of support; i.e., POV, taxi, bus or pool vehicle. Determine mission impact based on Form 971 input. A decision table is provided that will aid the CTO in determining whether a vehicle should be assigned.
Condition, age, and downtime are factors that should be included in the analysis and documented on the Form 971.
Analyze past and expected utilization: if only 25% of average utilization is currently being met, continued assignment may not be warranted.
Develop preliminary TAV based on evaluation of the data captured on each Form 971, showing current and recommended levels.
Coordinate findings with customers and offer opportunity for rebuttal, especially if recommendation is to reduce assignments.
Consider customer recommendations and then make final decision on baseline mix.
Retain this TAV level and only adjust when mission changes warrant adjustments.
Once the customer baseline TAV is established, develop a baseline TAV for pool vehicles if applicable.
Note: CTO’s who already have an established and approved baseline in place are not required to re-establish the baseline. However, baselines must have been based on measurable and meaningful data.
Each NASA Center shall conduct an annual review of fleet vehicle utilization during the third quarter of the fiscal year. The review will first identify fleet units that fail to meet minimum utilization goals and then recommend disposition of the subject vehicle(s) according to the procedures stated.
Beginning the first of each calendar year, the CTO will generate a utilization report for every vehicle in the Center’s fleet. The report should be created in a spreadsheet software program (for example, MS Excel) to allow calculations to be performed on the data. Use the format shown in the following example:
|
BOAC |
Type |
License # |
Year |
Make |
Model |
Organization |
Average Annual Usage (Miles) |
|
807000 |
Sedan |
4567 |
2003 |
Ford |
Taurus |
Research |
6,157 |
|
807078 |
Truck less than 12,500 pounds GVWR |
7654 |
2001 |
Ford |
F-150 |
Facilities |
9,496 |
Calculate the average annual usage by vehicle type for the Center. The result should be similar to this example:
|
Motor Vehicle Type |
Average Annual Usage for 2004 |
|
Sedans/Station Wagons |
8,600 miles |
|
Ambulances |
2,400 miles |
|
Buses: |
|
|
Intercity |
14,280 miles |
|
City |
12,966 miles |
|
School |
16,440 miles |
|
Trucks |
|
|
Less than 12,500 pounds GVWR |
10,766 miles |
|
12,500-23,999 pounds GVWR |
8,654 miles |
|
24,000 pounds GVWR and over |
6,448 miles |
Calculate the “Utilization Target Point” for each type of vehicle by multiplying the average usage by 25% (.25) for each type. For the example above, the Utilization Target Points would be:
|
Motor Vehicle Type |
Utilization Target Point |
|
Sedans/Station Wagons |
2,150 miles |
|
Ambulances |
600 miles |
|
Buses: |
|
|
Intercity |
3,570 miles |
|
City |
3,241 miles |
|
School |
4,110 miles |
|
Trucks |
|
|
Less than 12,500 pounds GVWR |
2,691 miles |
|
12,500-23,999 pounds GVWR |
2,163 miles |
|
24,000 pounds GVWR and over |
1,612 miles |
Identify the individual vehicles within each type whose usage fell below the Utilization Target Point during the respective year. Label these vehicles in the report as “under-utilized.” This list constitutes the “Utilization Target List.”
During the 3rd quarter of the Fiscal Year, the CTO will notify organizations with vehicles on the Utilization Target List by letter (copy to NASA Center Director or designee) that their vehicles are on the list and will be evaluated for possible actions that include:
Removal from the fleet
Re-assignment within the Center
Exchanged for another vehicle of a similar type with higher miles
Exchanged for a different type of vehicle that better suits the mission
Retention with proper justification
Turned in to GSA
Organizations with vehicles on the Utilization Target List must submit a new Form 971 to the Vehicle Management Office (VMO) at least two weeks before the end of the 3rd quarter of the Fiscal Year.
The VMO organizes and reviews all inputs, including late 971 submissions; the objective is to finalize a report to the VURB by the end of 3rd quarter of the Fiscal Year.
The VURB will meet as soon as possible in the 4th quarter of the Fiscal Year to review the responses from organizations with vehicles on the Utilization Target List. One of two possible actions must result:
When the VURB approves continued use of the vehicle, the CTO will send a report to the NASA Agency Transportation Manager and notify users of the final action where necessary.
When the VURB disputes the using organization’s recommendation, the NASA Agency Transportation Manager is notified. The CTO provides final results to the users.
Vehicles that have undergone a complete dispute resolution process and were approved for retention are exempt from further identification as vehicles on future Utilization Target Lists for a period of 3 years. However, such vehicles should still be considered for exchange with higher mileage units of a similar type whenever possible in order to “balance” utilization for the overall fleet. Where applicable, excess GSA vehicles shall be turned in to GSA as soon as possible. The NASA Agency Transportation Manager shall be notified when this action is complete and records have been updated.
The CTO should promote full utilization of each vehicle. This may involve rotating or exchanging vehicles to ensure each vehicle achieves its programmed life usage. Rotation should be considered for any vehicle for which utilization consistently falls below the average for that type of vehicle at that Center.
Alternatives to owning or leasing vehicles through GSA should be considered when vehicles are under-utilized. Such alternatives include use of sub-pool vehicles, shuttle buses, on-site taxi service, POV’s, increased sharing between organizations, and establishment of on-demand short-term rental contracts.
Vehicle users may request exemptions to the minimum mileage specified for assignment or retention of a fleet vehicle. Other utilization goals such as passengers or tonnage carried or hours used should be applied if mileage is not an accurate measurement for a particular vehicle’s mission. Mileage accumulated on these types of vehicles should not be included in the annual mileage target for the fleet. See 41 CFR 101-39.301 for further guidance.
Link to 41CFR101-39.301: http://www.access.gpo.gov/nara/cfr/waisidx_02/41cfr101-39_02.html.
|
GSA Utilization Guidelines from 41 CFR 101-39 |
|
|
Passenger-carrying vehicles |
Min. of 3,000 miles/quarter or 12,000/year |
|
Light truck and General Purpose Vehicles £ 12,500 lbs (GVWR) |
Min. of 10,000 miles/year |
|
Trucks and General Purpose Vehicles >12,500 lbs GVWR £ 24,000 lbs (GVWR) |
Min. of 7,500 miles/year |
|
Heavy Trucks and General Purpose Vehicles > 24,000 lbs (GVWR) |
Min. of 7,500 miles/year |
|
Truck Tractors |
Min. of 10,000 miles/year |
Types of assignments for each customer shall be based on the specific requirements of each customer. Therefore, assignment of Government-owned or leased vehicles may be permanent or temporary.
Vehicles shall be assigned only to those Centers that have an approved allowance and shall be supplied through new procurement or the most cost effective means. This includes vehicles acquired through GSA where practical.
The CTO will exercise management and control over all assigned vehicles. This includes periodic evaluations of existing assignments as well as reviewing new requests for transportation support.
The CD or a designated representative (in writing) shall play an active role in the management of vehicle resources. This means supporting decisions to reassign or eliminate assigned vehicles where utilization clearly does not warrant further retention.
The VURB must meet at least annually to identify low utilization vehicles as well as other requests and make recommendations for retention and withdrawal of assigned assets.
Each Center will maintain an approved list of vehicle assignments as part of their Table of Vehicles (TV). This list shall also include contractor-furnished vehicles that are assigned, operated, and maintained by the contractors. NASA Headquarters will review each Center’s TV annually to monitor changes in fleet size and track such changes to show at least five years’ history. Any acquisitions that exceed the approved TV must be approved in advance of the acquisition by NASA HQ Agency Manager of Transportation Programs.
A Form 971 will be maintained for each assignment and will be customer-generated and forwarded to the CTO for consideration. When several vehicles of the same type are used for the same purpose, one Form 971 will suffice as long as the number of vehicles authorized is stated on the form. The CTO will process all Form 971s for the annual review and will also handle the forms for new requests. Existing vehicle assignments listed on the TV are exempt from additional Form 971 requirements.
Centers are strongly encouraged to maintain a zero growth policy. This means that additional vehicle assignments must be related to mission change and supported with valid justification (Form 971). See paragraph 4.1 “Note.”
Vehicles approved for customer support will remain as permanent assignments unless the annual review warrants reassignment.
Request to use fleet vehicles for commuting purposes shall not be entertained.
Where applicable, Centers will evaluate the cost effectiveness of a radio-dispatched taxi service in lieu of authorizing a permanent vehicle assignment.
bus services are encouraged, where practical and cost effective, to move personnel between various locations on and off the Center.
An alternative to furnishing a Government-owned or leased vehicle is to compensate individuals to use their POV’s. Used effectively, this can be a valuable tool in reducing the number of Government-owned or leased vehicle assignments. However, individuals cannot be forced to use their POV’s. A cost-benefit analysis should be conducted on a case-by-case basis.
The CTO should encourage the use of sub-pools as a means of reducing the number of Government-owned and leased vehicle assignments.
The CTO has authority to deny any requests where insufficient justification has not been provided. See Chapter 3 on official usage.
When the CTO or higher authority denies an individual’s request for vehicle assignment, the customer may submit additional justification, along with an impact statement, to further support the request. Once received, the CTO will make a final review and determination.
The CTO will ensure sufficient data is collected and maintained to properly monitor fleet usage. Policies pertaining to vehicle assignments must be enforced.
Travel logs are a tool fleet managers can use to help evaluate vehicle utilization. Their use is encouraged in sub-pools and where appropriate, but is not mandatory. Transaction data that includes check out date and time, and check in date and time are highly recommended.
Each Center is encouraged to develop a vehicle charge-back system to ensure users are aware of the costs of vehicle ownership and operation. Assistance with the development of charge-back rates and procedures is available by contacting the NASA Agency Transportation Manager. It is especially important to charge for the costs associated with accident and abuse.
See http://www.gsa.gov (home> services> vehicle leasing) for access to current GSA rates.
Vehicles will be operated in accordance with this handbook and state and local laws as applicable.
Personnel operating Government-owned motor vehicles must comply with motor vehicle traffic laws of the State and local jurisdiction as outlined in 41CFR102-34.250.
Operating a Government-owned motor vehicle while under the influence of alcohol and/or illegal drugs is strictly prohibited. Moreover, personnel will not consume alcohol or illegal drugs while operating Government-owned motor vehicles.
As stated in paragraph 4.3.7.3, POV’s may be used for official business for short trips and incidental travel, subject to Federal Travel Regulations.
Generally, Government vehicles will be parked at each customer’s work place in a secure location, with the keys and credit card removed and the vehicles locked and windows rolled up. Exceptions should be coordinated through the CTO.
Operators will report loss of or damaged property to the CTO via their supervisor. Whenever Government vehicles are lost, damaged, or stolen, the CTO will ensure an investigation is accomplished. This also includes GSA assigned vehicles.
Operators will coordinate with the CTO for replacement keys and cards. The responsible department will ensure a memorandum is written to explain the circumstances of the loss and action taken to prevent reoccurrence. The CTO maintains spare keys in the Vehicle Management Office (VMO).
Lost plates for Government-owned and GSA vehicles will be reported to and handled by the CTO. See 41 CFR 101-38.202-7.
Wearing of seat belts is mandatory for all vehicle occupants. See 49CFR 571 for specific details on occupant restraint devices.
Use of tobacco products including smokeless tobacco in GSA and Government vehicles is prohibited.
Operators of GSA and Government vehicles will not operate cellular phones while the vehicle is in motion or on the traveled portion of a roadway.
Center Transportation Management shall have an understanding of the rules and regulations governing the transport of hazardous cargo movement. See 49CFR, Part 177 for specifics on transporting hazardous cargo over the public highway.
The National Highway Transportation Safety Administration has issued repeated rollover warnings to users of 15-passenger vans. NASA policy prohibits carrying more than 9 people including the driver in 15-passenger vans. NASA policy also requires drivers of 15-passenger vans to be experienced drivers with valid Commercial Driver’s Licenses. Procurement and use of these vehicles is highly discouraged. See http://www.nhtsa.dot.gov/cars/problems/studies/15passcustomer-advisory.htm.
Warning: Where used, safety recommendations on 15-passenger vans must be strictly adhered to, including ensuring vans are only operated by trained and experienced drivers, including a review and understanding of the safety advisory.
FAST is a web-based system developed to measure the compliance of Federal agencies with the Department of Energy’s Energy Policy Act (EPAct) of 1992, the Energy Conservation Reauthorization Act of 1998, and Executive Order 13149 - Greening the Government through Federal Fleet and Transportation Efficiency. NASA Centers are required to populate the FAST database annually and submit the data to the NASA Agency Transportation Manager in accordance with the required schedule for review and final submission. NASA personnel or contractor assistants will populate the data through the web interface at http://fastweb.inel.gov. Contractors who operate Government-owned vehicles shall be required to assemble and report FAST data annually, no later than October 15 of each calendar year. See NPR 6200.1B paragraph 3.1.23.9.
NASA personnel should use the GSA Fleet Drive-Thru web portal that allows GSA customers to report vehicle mileages, generate vehicle inventory reports, and input information and accounting classifications for vehicles to expedite billing. Use http://drivethru.fss.gsa.gov/drivethru/drivethru/ to access this portal and login using the assigned password.
FMIS that track vehicle asset records, maintenance history, mileage, and many other fleet management details are important management tools that are used extensively in the commercial fleet sector. Each Center’s CTO should assess the need for such systems and coordinate with the NASA Agency Transportation Manager to determine the best approach for acquiring such systems in order to provide critical functionality and management consistency throughout all NASA Center.
Page: 4. Asset Management - Chapter View
Last Updated:08/23/2005 10:44 AM