Attachment 8 Tab C Technical Library 20230327.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

DEPARTMENT OF THE AIR FORCE

AIR FORCE RESERVE COMMAND

, 2020

MEMORANDUM FOR 94 LRS

FROM: 94 LRS/CC

SUBJECT: Documented Cargo Delivery Wrecker Recovery Response Times

1. Required delivery times for routine and Priority Documented Cargo within the confines of Dobbins Air Reserve Base will be as indicated below:

Required Delivery of Due-Out Released (DOR) Material is as follows

Delivery of Expedite Issue Requests Delivery priority 01/02 MICAP...........NLT 30 min Delivery priority 03-15....................... Next Scheduled Sweep*

* If MICAP, receipt processing of due-out released (DOR) time of 1 hour, includes receipt of property once received from carrier.

recker Recovery response times for requests will be no later than 60 minutes in the case there is a vehicle blocking an airplane. For normal requests, the response times will be 60 minutes during the normal duty day and 120 minutes outside normal duty hours.

Response times for these services are established and approved IAW AFI 24-301, Ground Transportation and are applicable to military, civilian and contractor personnel performing these services. Please direct all inquiries to the Transportation Accountable Officer, CHRISTOPHER A KAIGHEN, Maj, USAF Commander

KAIGHEN.CHRISTOPHER.

A.1096802478

Digitally signed by

KAIGHEN.CHRISTOPHER.A.1096802478

Date: 2020.11.02 12:52:47 -05'00'

Sheet1

UDI Fleet

Mgmt Code Description

B102 SDN CMPT 4PAX CL II

B102 SDN CMPT 4PAX CL II

B103 SDN MIDSIZE 5PAX CL III

B110 HYBRID SEDAN

B121 BUS SCH 25-29 PAX 4X2 DE

B130 BUS SCH 42&45 PAX 4X2 DE

B185 TRK CRL 4X2 8 PAX

B188 TRK CRL 4X2 7 PAX

B192 TRK CRL 4X2 15 PAX

B204 TRUCK, 1/2T REG CAB 4X2

B222 TRK P/U 4DR 4X4 9200 GVW

B222 TRK P/U 4DR 4X4 9200 GVW

B261 TRK STK 4X2 1 T 7000 GVW

B265 TRK S&P 4X2 10000 GVW

B265 TRK S&P 4X2 10000 GVW

B361 TRK TRAC 6X4 44.5K-46K GV

B361 TRK TRAC 6X4 44.5K-46K GV

B409 STLR LB 20T 40 FT

B415 STLR LB 35T

B423 STLR VN 30FT, 12T & OVER

E956 TRK FL 10K 463L

Vehicle Management Guidebook

Vol. 1, Version 1.7 27 September 2021

Forward:

In support of the Secretary of the Air Force and Chief of Staff of the Air Force’s “2017 Air Force Directive Publications Reduction Initiative”, the Vehicle Management (VM) Guidebook was established. The directed initiative to review and streamline Headquarters Air Force directive publications resulted in the removal of internal “process steps” and other duplicative information from AFI 24-302, Vehicle Management.

The information relocated to the Vehicle Management (VM) Guidebook, and other vehicle management related guidebooks (e.g., Transaction Request Tool (TRT) Guidebook, Defense Property Accountability System (DPAS), Maintenance & Utilization (M&U) and Warehouse (WH) Guidebooks), deals with internal processes and use of the system used by Air Force personnel for vehicle management. The Air force Instruction (AFI) appropriately directs use of this system, but guidance on how to use the system and purely internal matters of similar nature concerning internal process uses is appropriately covered in the VM Guidebook.

Send suggested process changes to this VM Guidebook to the 441st Vehicle Support Chain Operations Squadron (VSCOS) (441VSCOS.AF.VehMgt@us.af.mil).

Note: Part 1: Chapter and paragraph references contained in the VM Guidebook are associated with AFI 24-302 chapters and references.

Part 2: Fleet Management processes and practices are further explored to provide a broader perspective on the purposes behind them.

SUMMARY OF CHANGES

This document has been updated and must be completely reviewed. Major changes include:

removing references to “Online Vehicle Interactive Management System” and inserting Fleet Management Information System (FMIS), Accountable Property System of Record (APSR) and Defense Property Accountability System (DPAS) references as needed; removing “watercraft” management type language; updating Materiel Control with FMIS Warehouse Module instructions; instituting Vehicle Management Operating Procedures versus Operation Instruction; clarifying tool marking procedures for VM functions. Also, this guidebook directs the implementation of the Joint Light Tactical Vehicle (JLTV) Requirements Integration Office within the 441 VSCOS.

mailto:441VSCOS.AF.VehMgt@us.af.mil https://static.e-publishing.af.mil/production/1/af_a4/publication/afi24-302/afi24-302.pdf

Table of Contents Part 1:

Chapter 2 The Objectives, Responsibilities, Organization and Principles of

Managing the Air Force Fleet

2.3.3.12. Processing LTIs.

2.9.5. Vehicle Buy Process

2.9.13.2. Provide WRM Requirements per WRM Vehicle Validation Template

2.18.3. Monitor and Manage Repetitive Maintenance, Warranty, Contract, and Authorized Repairs

2.18.10. Vehicle Determinations

2.18.11. Establish, Execute, Initiate and Conduct All Vehicle Recalls

2.18.19. Reimbursable Maintenance Program

4.1.4. Ensuring Economical Vehicle Repairs

2.18.25. Accident and Abuse Work Order Processing

2.18.26. Depot Maintenance Processing

2.18.28. Develop and Manage the MEL and the VPRL

2.18.29. Review and Verify Nuclear Certified Vehicle Data-Plate and Records

2.18.34.2. Manage TCTO, Service Bulletin, Manufacture Recalls and OTIs

2.18.35. Review, Validate and Process Vehicle Authorization Requests

Chapter 3 Vehicle Management Contingency Operations

3.12. Home Station Survival

3.15. Temporary Mission Support Kit

3.17. Training

3.24. Facilities

3.28. Mobile Maintenance

3.33. Vehicle Triage

3.43. Vehicle Deployment Processing

Chapter 4 Fleet Management & Analysis

4.1.19. Fill Vehicle Authorization with Most Suitable Asset.

4.1.22. Manage Awaiting Disposition Vehicles

4.1.23. Processing LTIs

4.1.35. FM&A Quick Reference Listing

4.5. Performing Analysis

4.9. Processing Commercial Sales Slips

4.10. Vehicle Custodian Responsibilities

4.11. Vehicle End-Of-Life (EOL) Determination

4.15. Vehicle License Plate Program

4.16. Federal Motor Vehicle Registration System (FMVRS)

4.21.3. Non-Cataloged Vehicle Request Actions

4.27. Vehicle Redistribution (RDO)

4.31.1.1. Specific Key Supporting Documents required for asset load.

4.31.3.1. (FIAR) Date of Last Inventory (DOLI) Procedures and Timetable

4.31.4. (FIAR) Annual Inventory

4.37. Manage Vehicle Status Code.

Chapter 5 Materiel Control

5.1.7. Materiel Control and DPAS Inputs

5.3. Common Publications, Reports and Listings

5.4. Use of Reports and Listings

5.5. Supply Discipline

5.6. Priority System

5.7. Adjusted Stock Levels

5.8. Identifying the Requirement

5.10. NMCS Verification Procedures

5.11. MICAP and NMCS (AF Requisitions).

5.15.1.1. Manage Delayed Work Order Folders

5.15.1.2. Monitor Delayed Work Orders.

5.15.1.3. Ensure Received Parts

5.15.1.4. Valid Work Orders and Backorders.

5.21. Working Stock.

5.24. Time Compliance Technical Orders

5.25. Tool Accountability and Issue Procedures.

5.26. Tool Crib Operations

5.27. ITK Procedures.

5.28. CTK Procedures

Chapter 8 441 VSCOS

8.5.5. Provide RDO/Disposition Support

8.13.4. Pre-VV Actions by Installation FM&A

8.25. Prioritization Model Preparation for Planning and Execution.

8.26. Vehicle Must-Buy Justification Requirements

8.28. First Article Testing (FAT).

8.29.7. Product Evaluation Types.

Chapter 10 Vehicle Energy

10.17. Purchasing Sources and Procurement Standards.

Attachment 3 Air Force Surplus Vehicle Sales Program

A3.4. Vehicle Eligibility Criteria.

A3.5. Presale Eligibility Determination/Procedures.

A3.6. Post Auction Procedures.

CHAPTER 2

2.3.3.12. Processing LTIs.

Process requests for repair authority and disposition instructions for vehicles to the using

AFTO Form 91, Limited Technical Inspection.

Guidelines for determining repair allowances and approval levels are in TO 36-1-191.

All LTIs for disposition/maintenance repair consideration are sent to 441st VSCOS via upload to the LIMS-EV Vehicle View/Transaction Request Tool (TRT) for decision.

Only direct labor and parts costs for actual repairs related to serviceability/functioning of asset are used to determine if a vehicle is economically repairable. Do not include aesthetics such as corrosion control, paint complete, etc.

441st VSCOS forwards all LTIs for M-Series vehicles in Awaiting Disposition status to Robins AFB, SE&V for disposition action.

To request disposition instructions for Air Force Office of Special Investigations (AFOSI) vehicles, FM&A forwards AFTO Form 91, Limited Technical Inspection-Motor Vehicle to HQ AFOSI email:lg.office@ogn.af.mil. AFOSI Command Fleet Manager submits LTI for disposition instructions through the TRT, then forward instructions to the local requesting

FM&A.

Within 10 duty days of requirements, process LTI for acceptance, disposition action and repair decisions. LTIs for shipping are completed as soon as practical in order to meet RDO requirements (refer to AFI 24-302, Vehicle Management, paragraph 8.5.5).

Make all repairs not reflected on the initial LTI prior to shipment, if parts are removed or additional discrepancies are identified during or after RDO instructions are received the losing units are held responsible for reimbursement.

When a vehicle is shipped, it is the losing FM&A responsibility to contact the gaining FM&A and provide date shipped, document number, asset ID and mode of shipment. It is the gaining FM&A responsibility to follow up on vehicles in shipment. In transit, visibility should be through normal shipment modes not LIMS- EV VV.

2.9.5. Vehicle Buy Process.

Robins AFB SE&V is the central procurement agency for all AF vehicle purchases.

AF agencies should not purchase vehicles without prior coordination and written approval from Robins AFB SE&V Program Manager.

Annually, the following actions are completed.

o Robins AFB SE&V:

• Provide 441st VSCOS with specific vehicle buy submission instructions/guidelines.

https://static.e-publishing.af.mil/production/1/afto/form/afto91/afto91.pdf https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/bookshelf.aspx https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/LIMS-EV.aspx https://lims-ev.cce.af.mil/vehicles-trt/Main.html#/dashboard

• Review and approve specifications, purchase options, purchase descriptions and standards for procuring AF vehicles.

• Coordinates shipment of assets acquired.

• Specification Review:

o Robins AFB SE&V forwards the vehicle specifications as needed to 441st

VSCOS for coordination through the lead command, if needed, for use during the following FY buy process.

o The lead command is usually the dominant user of a specific vehicle type.

o Robins AFB SE&V does not review specifications for: Vehicles bought through

GSA, M-SERIES vehicles or vehicles on an optional or multi-year contract for the follow-on FY.

o 441st VSCOS:

• Compile and prioritize AF and ANG vehicle requirements via LIMS-EV Vehicle View Prioritization Model (refer to AFI 24-302, Attachment 5).

• Works with Robins AFB SE&V to resolve any inventory data discrepancies.

• Provides Robins AFB SE&V with special specification requirements.

• Monitors due-ins via LIMS-EV Vehicle View (Due in).

2.9.13.2. Provide WRM Requirements per WRM Vehicle Validation Template.

441st VSCOS provides the WRM Vehicle Validation (VV) template and requests C-

WRMOs and A4RV to complete form.

Command WRM Officers and A4/RV reviews and update vehicle requirements using the

WRM VV template and returns to 441st VSCOS.

441st VSCOS inputs data into the Fleet Management Decision Support System (FMDSS).

FMDSS creates report listing required and excess assets.

441st VSCOS sends reports to C-WRMOs to revalidate.

2.9.22. Manage Awaiting Disposition Vehicles. Vehicles awaiting disposition are vehicles, no longer having a local authorization, which cannot be redistributed to fill vacant authorizations, or be reassigned to replace less serviceable and/or maintainable (usually older) vehicles eligible for replacement. 441st VSCOS approval is required for Awaiting Disposition assets used for deployments or special projects.

FM&A controls ALL vehicles pending disposition direction.

Vehicles in this status are not assigned to organizations waiting approval for additional vehicle requirements.

https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/LIMS-EV.aspx

VM retains physical possession of these vehicles. All awaiting Dispo assets are securely located in VM compound.

Assets are not rotated back into service without 441st VSCOS approval.

When authorization is no longer warranted, and reassignment to another base activity is not possible, request vehicle be moved to 048??EG authorization via the TRT. Refer to current copy of TRT Guidebook.

o ASC 048??EG is assigned and Use Code is “B”.

Other status codes for Awaiting Disposition vehicles are as follows:

o D -- Disposition instructions received, pending shipment, maintenance, transfer to

Defense Logistics Agency-Disposition Services (DLA-DS), sale, etc.

o E -- Vehicle is unserviceable. Maintain accountability until transfer to DLA-DS.

VFM/VMS may authorized cannibalization actions prior to transferring to DLA-DS;

update LTI as needed.

o I -- Vehicle is awaiting LTI. Vehicle is unserviceable and disposition instructions requested from 441st VSCOS.

o N -- Vehicle is awaiting disposition instructions from 441st VSCOS. LTI and/or justification request for special retention submitted.

Accomplish the LTI and forward it to 441st VSCOS requesting disposition instructions within 30 calendar days from the date the vehicle became surplus.

Initiate follow-up action 30 calendar days after the date the LTI submitted to 441st VSCOS.

2.18.10. Vehicle Determinations.

Local FM&A’s provide assistance to users seeking assets that meet certain mission requirements and specifications.

There is a slide show outlining specific roles/responsibilities, publications/guides and the overall determination process on the VM Neighborhood (link below).

o https://usaf.dps.mil/sites/AFVehicleFleetMgt/VMA/Lists/Vehicle%20%20Equipment%20

Determinations/AllItems.aspx

2.18.11. Establish, Execute, Initiate and Conduct All Vehicle Recalls. Incorporate vehicle redistribution plans in the transportation annex to the basic plan as applicable. (The VPRL serves as the recall tool to use for short-term vehicle needs)

2.18.19. Reimbursable Maintenance Program.

Ensure Reimbursable Units are Identified Correctly in the Fleet Management Information

System (FMIS). See M&U Guidebook for process.

https://usaf.dps.mil/sites/AFVehicleFleetMgt/VMA/SiteAssets/Vehicle%20Determinations20190515.pptx https://usaf.dps.mil/sites/AFVehicleFleetMgt/VMA/SiteAssets/Vehicle%20Determinations20190515.pptx

Receive Responsibility Center/Cost Center (RC/CC) code for reimbursable units from Finance.

FM&A validates RC/CCs with the Finance Office and provide updates to 441st VSCOS annually for required updates in DPAS.

Monitor reimbursement via resource advisor and/or Financial Budget Office.

For OCONUS locations where civilian labor is paid for by host-nation support, FM&A deletes all affected civilian labor transactions before submitting data to Financial Budget Office for reimbursement.

Only reimbursement is for parts and appropriate civilian labor.

2.18.25. Accident and Abuse Work Order Processing. Refer to AFI 24-302, Vehicle

Management, paragraph 1.12. for program instructions. The following takes place when the shop receives a vehicle with actual or suspected accident or abuse damage:

Customer Service Center (CSC) personnel notifies the VFM/VMS and opens “Accident or Abuse” work order using the appropriate Work Order Reason Code, then initiate the appropriate work/parts “estimate”. Use “estimate” to estimate accident/abuse repair cost only. When computing estimated cost for repairing accident damage, indirect cost is included only to determine one-time repair limitations. See current M&U Guidebook for use of accident/abuse Work Order Reason Codes.

Actual repairs start when the organization of responsibility “releases” the vehicle for repairs.

Only document accident or abuse related repairs on the “actual” work order. Complete any other unscheduled repairs or scheduled services on an unscheduled or scheduled maintenance work order to follow. See current M&U Guidebook for use of accident/abuse Work Order Reason Codes.

FM&A prepares repair cost estimates when requested by owning organization or the Surveying Officer.

2.18.26. Depot Maintenance Processing. To accurately document vehicle downtime, retain vehicle record in master file while vehicle is undergoing depot rebuild. See current M&U Guidebook for work order process.

Downtime begins when vehicle is removed from service and shipping LTI is accomplished (a “DEPO” Reason and Action Code work order remains “open”). Downtime ends after the vehicle returns from depot, acceptance LTI is accomplished and the vehicle is available for use. Vehicle not returning to originating base do not draw downtime and should use the Work Order State Code of "RADM". See current M&U Guidebook for instructions.

Capture depot rebuild cost in DPAS at the Sub Work Order Parts tab and establish contract warranty information. The cost includes transportation and actual depot repair costs. Robins AFB SE&V provides Depot cost to 441st VSCOS, which subsequently forwards the cost data https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/bookshelf.aspx https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/bookshelf.aspx to the base. Contact servicing DDF for the shipping cost to depot. Use this same shipping cost for the return cost from depot. See current M&U Guidebook for work order processing.

Create a TRT request to update the depot rebuild return date that is used to update the EOL for the asset. See current copy of TRT Guidebook.

Prior to departure for depot, remove AF license plates from vehicles. License plate(s) are stored in the vehicle‘s records jacket (or in FM&A if vehicle records are stored electronically). Ship plates via registered mail to new location if transferred after depot completion. Refer to T.O. 36-1- 191, Technical and Managerial Reference for Motor Vehicle Maintenance.

Vehicle Shipment to Depot Repair. Local Traffic Management Flight should assist with guidance on funding the transportation costs associated with an Redistribution Order (RDO) as provided in AFI 24-302. Criteria for these vehicles are contained in TO 36-1-191, Chapter

9. 441st VSCOS provides shipping instructions for vehicles scheduled for depot repair.

Three vehicle status codes apply to depot shipments. Status codes “B” and “G” (accountability not retained by the shipping base) and Status code “R” (vehicle programmed for return to the base).

Submit a TRT "Update" request and annotate the DEPOT date and status code "A" to be reflected on Logistics Installation and Mission Support Enterprise View, Vehicle View (LIMS-EV VV) (See current copy of TRT Guidebook).

2.18.28. Develop and Manage the MEL and the Vehicle Priority Recall Listing (VPRL). In conjunction with using organizations, vehicle MELs are established by vehicle type/LIN/TAMCN to include any substitutes to reflect the minimum number of vehicles needed in service to complete the user's mission.

Develop MEL formulas for peacetime authorizations only. Do not use “Use Code D” pure War Reserve Material (WRM) (integrated or stored) assets in MEL formulas.

Annually, using organizations and the vehicle management activity verify MELs.

It is not realistic to have 100% of any vehicle type in any organization listed as the MEL.

Make allowances for scheduled maintenance, normal breakdowns, etc.

Using organizations provide justification data to support requested MEL to vehicle management.

FM&A reviews request, analyzes utilization data and maintenance history and provides the

VFM/VMS with recommendations. The VFM/VMS reviews proposed MEL with the using organization Vehicle Control Official (VCO) before Mission Support Group (MSG) Commanders approval and final publication of the list. The MSG Commander is the final authority for an unresolved MELs.

The approved MEL list serves as the vehicle maintenance priority repair list when the vehicle types identified are below the MEL.

https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/bookshelf.aspx https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/bookshelf.aspx https://static.e-publishing.af.mil/production/1/af_a4/publication/afi24-302/afi24-302.pdf

FM&A manages and executes vehicle priority recalls for the base.

Vehicles listed on the VPRL are grouped by unit and vehicle type and consists of vehicles that exceed the MEL required for a unit to accomplish its mission. This listing serves as a recall tool to use for short-term vehicle needs.

2.18.29. Review and Verify Nuclear Certified Vehicle Data-Plate and Records. FM&A validates, documents and ensures the accuracy of nuclear vehicle certification status by completing the following actions:

During initial acceptance inspection of new vehicles:

o FM&A verifies nuclear certification status by comparing the vehicle data plate, shipping documents, National Item Identification Number (NIIN), make and model information against the Master Nuclear Certification List (MNCL).

o If the vehicle is nuclear certified, FM&A annotates "N" on the Nuclear Certified drop down when submitting a "New Load Request" via TRT. 441st VSCOS updates the record to reflect "N" status.

o Schedule annual Nuclear Certified Equipment (NCE) Data Plate Inspections in DPAS M&U using DPAS Work Code 43AN.

During scheduled NCE Data Plate Inspection actions:

o Re-validate data plate information and ensure the data matches vehicle information contained on the MNCL and is properly coded in DPAS.

o Review LIMS-EV Vehicle View to ensure correctly identified nuclear certified status of the vehicle.

o Review the permanent portion of the records jacket/file for documentation concerning nuclear certified vehicle modification request, DULL SWORD reporting and subsequent certification actions (e.g., “Restricted Use”).

o For damaged, missing or illegible data plates, or for data plates with erroneous information, refer to T.O. 36-1- 191, Technical and Managerial Reference for Motor Vehicle Maintenance, or contact 441st VSCOS for direction. 441st VSCOS in-turn forwards the information the appropriate AFLCMC-WNZ office for corrective action and relay information to requestor.

Foreign made vehicles that are Nuclear Certified (IAW AFI 91-103, Air Force Nuclear Safety Design Certification Program) may not have "Data Plates" affixed when delivered new. In this instance, and thereafter during scheduled or un-scheduled maintenance, FM&A verifies nuclear certification status by comparing the available documentation against the MNCL. Secure Robins AFB SE&V and 441st VSCOS approval before locally manufactured data plates are applied to Nuclear Certified vehicles/equipment (see T.O. 36-1-191, Technical and Managerial Reference for Motor Vehicle Maintenance, para. 1.5.4.1.3, NOTE).

mailto:441VSCOS.AF.VehMgt@us.af.mil https://wwwmil.nwc.kirtland.af.mil/MNCL/index.cfm

For individual vehicles that have been listed on the MNCL by vehicle asset ID as “not authorized" for use during nuclear operations by the Air Force Safety Center (AFSC), FM&A submits an "Update" request via TRT to have the “N” designator for that asset ID. If the AFSC removes the vehicle‘s “not authorized” status from the MNCL, then the “N” designator is resubmitted via TRT.

The use of the “NUC IND” field in LIMS-EV Vehicle View is for maintenance reference/decision purposes only by Vehicle Management personnel.

Document all DULL SWORD through Joint Deficiency Reporting System (JDRS) for Deficiency, Warranty and Unsatisfactory reports. Additionally, courtesy copy all DULL SWORD packages to 441st VSCOS for situational awareness.

FM&A notifies the 441st VSCOS NCE Program Manager of vehicles requiring MNCL or removal actions. Send an unclassified e-mail with asset ID and pictures, as needed, along with short narrative justification describing desired actions and rationale for restricted use or removal to 441st VSCOS.

2.18.34.2. Manage TCTO, SB, Manufacture Recalls and OTI.

Manage TCTOs differently than regular TOs. Requisitioned individually and as a series identified for automatic distribution. TCTOs, SBs and OTIs are managed in accordance with the following procedures:

o Robins AFB SE&V or Fuels Support Equipment (FSE) Item Managers notifies 441st

VSCOS of newly released TCTOs, SBs and OTIs. 441st VSCOS provides base-level Vehicle Management a list of vehicles/FSE requiring the TCTO, SB or OTI action.

o Units ensure they are on TO distribution listing for each TCTO series. These series are listed in the “-36” index for the type of vehicle they pertain to. The TO monitor must review the “-36” index on receipt and ensure that for each type of vehicle assigned, if there is an applicable TCTO series that it is on distribution. This ensures units receive TCTOs published under that series.

o FM& date stamp each TCTO, SB or OTI once received (electronically dated e-mail/message traffic is sufficient); determine TCTO, SB or OTI action and/or parts kit requirement by reviewing the TCTO, SB or OTI cover page for affected vehicle asset ID’s; and notify Materiel Control to order required parts kits after determining and verifying base requirements.

o Robins AFB SE&V requires verification that correct TCTO or SB part(s) have been ordered before parts(s) are released for shipment. Through 441st VSCOS, contact the appropriate Program Manager or Equipment Specialist for the affected vehicle type by telephone, fax or electronic mail, provide vehicle asset ID’s and requisition due-in document numbers, obtained from Materiel Control, to enable part(s) release.

o Take continuous supply follow-up actions until kits are received.

https://wwwmil.nwc.kirtland.af.mil/MNCL/index.cfm https://wwwmil.nwc.kirtland.af.mil/MNCL/index.cfm https://lims-ev.cce.af.mil/vehicles-trt/Main.html#/dashboard https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/LIMS-EV.aspx https://www.jdrs.mil/ o Complete TCTOs, SBs and OTIs actions as soon as possible, before the required completion (suspense) date. TCTO, SB or OTI not completed by the “completion date” are considered "outstanding" and places the vehicle’s serviceability in jeopardy.

o Remove vehicles with “outstanding” actions from service until the subject TCTO, SB or OTI is accomplished when directed by the Robins AFB SE&V.

o 441st VSCOS collects completion/compliance reporting via LIMS-EV Vehicle View monthly data files for completed TCTOs and SBs. Urgent action TCTO and SB completion reporting is included with all others, however they may require manual completion reporting depending on time constraints and fleet safety concerns. 441st VSCOS notifies applicable units and AFRC or NGB as the need arises.

o Maintain active master TCTO, SB and OTI files. Maintain a rescinded file when needed for special programs and projects. Obtain rescinded TCTOs by following the procedures in TO 00-5-1-WA-1 , Air Force Technical Order System.

o The master file consists of active and inactive sections. Subdivide into four sections:

TCTOs, Service Bulletins, One-Time Inspection Letters/ Messages, and Recalls/Campaigns (separate binders for each type may also be used). The active section contains an index of all active items and include document number (TCTO number, bulletin number, or date/time group), document title/description, and status. Purge inactive files 1-year after rescission date. Electronic files are permissible.

o Verify TCTO status via LIMS-EV Vehicle View monthly. The TCTO view depicts four separate, but linked, TCTO requirements by vehicle counts. The available data views are by vehicle numbers and percent completed. By toggling between the views, the viewer should have an informed look at an individual TCTO or the status of a larger TCTO program completion level within a filter set. Coordinate discrepancy resolution with 441st VSCOS. (See current M&U Guidebook for instructions on opening TCTO/SB/OTI work orders) o Access LIMS-EV Vehicle View and click the TCTO tab.

Data points and definitions.

o Total required. Depicts the sum vehicles required to have a TCTO completed on them within the filter set. Source of the vehicle count is a sum of the asset ID’s listed in the TCTO table that matches the filter set.

o Complete. Depicts the sum of vehicle asset ID’s listed within the filter set that have a “TCTO COMPLETED DATE” listed.

o Due/On-Time. Depicts the sum of vehicle asset ID’s in the result set that require a TCTO be completed that has not passed the “MUST BE DONE DATE”. Should be reflected when within 60 days of due date.

o Overdue. Depicts the sum of vehicle asset ID’s in the result set that require a TCTO be completed that has passed the “MUST BE DONE DATE”.

https://www.tinker.af.mil/Portals/106/Documents/Technical%20Orders/AFD-082216-00-5-1.pdf https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/LIMS-EV.aspx

2.18.35. Review, Validate and Process Vehicle Authorization Requests.

Considers the following to address additional vehicle authorizations:

o Use of vehicles from the U-Drive It (UDI) fleet, priority recall, or short term lease/rental to satisfy short duration or sporadic mission requirements.

o Types and quantities of vehicles should clearly be the minimum number to accomplish the mission.

o Do not authorize vehicles for reasons of grade, prestige, personal convenience or to individual persons.

o Use LIMS-EV Vehicle View to review vehicle utilization. See AFI 24-302, Vehicle Management, Attachment 4 for LIMS-EV Vehicle View navigation details) o The AS is a seven-digit code which describes the AS used, Base Code and User Code.

For example, the AS Code for a registered fleet vehicle (010) belonging to Langley AFB (LA), Logistics Readiness Squadron (LRS) Vehicle Mgt Flt (EG) would be: “010LAEG”.

o All additions or changes to vehicle authorizations, require an authorization requests processed through 441st VSCOS. Use Auth Change Request User Guide for all additions. To request a new authorization, or to request updates to an existing authorization, send request to 441st VSCOS via LIMS EV Vehicle View. 441st VSCOS works with FM&A for clarification as needed.

o Once AF 601 request is approved by 441st VSCOS, retrieve documentation from TRT (See current copy of TRT Guidebook) o Process authorization requests applicable to USCENTCOM AOR through USAFCENT/A4RV, IAW USAFCENT VM Pamphlet 24-302.

o Authorized quantity increase due to mission change. Requests to increase vehicle fleet size should be supported by a verifiable mission change, e.g., OPLAN, Provisional Plan (PPLAN), Executive Order (EXORD), Fragmentary Order (FRAGO), base layout, operation moved to a different location on base, added a ramp, etc.

o All new or increased authorizations are coordinated with functional community. If approved, functional community requests vehicle procurement funding for the initial validated vehicle requirements and advocate additional funding in the out-years of the Program Objective Memorandum (POM) for increased vehicle buy replacement dollars.

o Offset any non-mission change increase by adjustments to other vehicle authorizations to preclude an overall increase in authorizations. Even if an offset authorization is provided, the requesting vehicle management activity should provide sufficient justification to support changing the authorization by answering the questions in AFI 24- 302, Vehicle Management. Ensure requested vehicle types are in line with the using organization’s “core set” of authorizations.

Vehicle Management ensures requirement has:

o Valid authorization, https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/LIMS-EV.aspx https://www.my.af.mil/vehicles-trt/vehicles-trt/Main.html#/dashboard https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/bookshelf.aspx o Current vehicle is replacement eligible, or o Vacant authorization.

Vehicle Management works with 441st VSCOS to ensure requirement is procurable (not on Robins no buy list.)

Vehicle Management obtains sample Military Interdepartmental Purchase Request (MIPR) from 441st VSCOS and provides (with instructions) to requesting unit RA/FM for completion. One MIPR per National Stock Number (NSN) request.

After authorization is validated, asset is deemed procurable, Vehicle Management forwards completed MIPR to 441st VSCOS for processing.

441st VSCOS works with Robins to complete order.

LIMS-EV Vehicle View, Due-In screen tracks vehicle due-ins until arrival.

Offset authorization(s) are equal to, or greater than, the purchase price of the requested authorization(s). The purchase price to be used for comparison is the unit cost listed in the LIMS EV Vehicle View for the Interchangeability and Substitutability (I&S) NSNs of the authorizations being compared, regardless of whether the authorization is for a government owned or lease vehicle.

Purchase price for offset authorization request is not considered if the authorization being requested is more environmentally friendly than the offset authorization and of similar/smaller size/type.

Authorization Analysis. The objective of the analysis is to validate the requirement and determine whether a more effective avenue, such as short-term leasing or co-utilization of assets, can satisfy the requirement without adding additional authorizations. The VFM uses the conclusions of the analysis to make approval/disapproval.

Justification Requirements. The following data is required on all new authorizations and change requests. Any request that does not contain all required data available should be returned for completion.

o Indicate if the request is for new, increase, reduction or deletion.

o Stock Record Account Number (SRAN) o Org and Shop Code o Document Number for existing authorization adjustments.

o NSN (Prime NSN only, no asset NSNs) and standard price from the Vehicle Management

Index File (VMIF).

o Use Code o UTC (for Use Code A authorizations).

• Increment Code for Use Code C and D authorizations.

o For use code “C”, populate with two- digit Base Code and two-digit User Code.

o For use Code “D”, populate with two-digit Base Code and an Org code of “BS” (for BEAR) or “WM” (for WRM).

o Acquisition Item Description (AID) o Authorization Standard (AS). ASs prescribe the required authorizations for vehicles to accomplish functional and organizational missions. ASs constitute authorization and approval authority for vehicles.

o AS information contained in request should match the as is information loaded in LIMS- EV Vehicle View and Air force Equipment Management System (AFEMS). If requesting 012, state if lease is General Services Administration (GSA) or commercial.

A cost comparison study accompanies the commercial lease request indicating the cost of the commercial lease is more cost effective than GSA. Refer to AFI 65-501, Economic Analysis and DoDM 4500.36, Appendix 2 for cost comparison study requirements and procedures. Clarification should be requested for missing or mismatched AS information. Review AFI 24-302, Table 4.2, Authorized Vehicle AS Codes, for ASs used for vehicle authorizations.

o Current In-Use Quantity (should match what is in LIMS-EV Vehicle View, see AFI 24- 302, Attachment 4).

o Current Authorized Quantity (should match what is in AFEMS). New Authorized Quantity.

o Number Required.

o Registration Number. The asset ID (registration) number is needed when increasing or adding authorizations and an on-hand asset should be used to fill. Provide registration number, and document number where vehicle is currently postured.

NOTE: Once authorization questions have been answered (601 complete), business rules applied, and no clear owned or leased authorization determination has been made, the unit works with their FM community to accomplish a Cost Benefit Analysis (CBA) to make the final determination. Upload all documentation into LIMS-EV authorization validation along with the other 601 supporting documents.

o Refer to the Mgt Code Picture Book for a list of suitable NSNs to fill an authorization.

o Submit a "Move/Rotate" transaction via LIMS-EV Vehicle View/Transaction Request

Tool (TRT) to move/rotate assets to fill the desired authorization.

https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword=10-2503&isObsolete=false&modID=449&tabID=131 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/450036m.pdf https://static.e-publishing.af.mil/production/1/af_a4/publication/afi24-302/afi24-302.pdf https://usaf.dps.mil/sites/AFVehicleFleetMgt/SitePages/LIMS-EV.aspx https://static.e-publishing.af.mil/production/1/af_a4/publication/afi24-302/afi24-302.pdf https://static.e-publishing.af.mil/production/1/af_a4/publication/afi24-302/afi24-302.pdf https://usaf.dps.mil/sites/AFVehicleFleetMgt/VMA/Lists/PictureBook3/Main1.aspx

CHAPTER 3

3.12. Home Station Survival. The following paragraphs give Vehicle Fleet Manager (VFM)/Vehicle Management Superintendent (VMS) possible options to mitigate the impact of heavy deployment tasking(s). Ensure leadership is informed and approves implementation of any operational changes.

Manpower:

o Augmentation. Explore the use of civilian over hires, or Air National Guard (ANG) and

Air Force Reserve (AFR) backfills. Contact Base Civilian Personnel Office for guidance on civilian over hires. Contact nearest ANG or AFR base for possible augmentation.

Additionally, contact Major Command (MAJCOM) Point of Contact (POC) for Individual Mobilization Augmentee (IMA) support. Request Manning Assistance through the MAJCOM as well. Requesting unit is responsible for funding Temporary Duty (TDY) costs. A contingency Emergency and Special Program (ESP) code may be available for reimbursement.

o Training. Prior to deployment, accelerate 5-level upgrade training while the majority of trainers are still available. Compensate for reduced capability by training non-deploying members in critical shop operations. This helps maximize shop productivity during heavy deployment periods.

Shop Operations:

o Parking Plan. Fleet Management & Analysis (FM&A) develops and implements vehicle-parking plan when required. Identify parked serviceable, non-essential vehicles.

Identification method could be from across the base, focused on deploying unit‘s vehicle fleet, commander‘s or equivalent‘s option or by number/type of mechanics deployed.

Compute the total number of vehicle equivalents earned by the deploying mechanics, if last option is selected, then park the proper fleet mix based on the total vehicle equivalents. Extensive coordination with base leadership occurs before implementing any type of parking plan.

• Use the following guidance when implementing a Parking Plan:

o The vehicles are to be stored in a controlled and monitored environment.

o Assets are “parked” for the duration of the deployment.

o Use of optional “parking plan/map” o Preserve parked vehicles to the appropriate storage level IAW TO 36-1-191, Technical and Managerial Reference for Motor Vehicle Maintenance o Parked vehicles are not “cannibalize”.

o Focus on quality of maintenance performed.

o Use the approved vehicle Minimum Essential Levels (MEL) and AFI 24-302, Vehicle Management, paragraph 3.31, as a gauge to develop maintenance priorities and establish in-house mission capable (MC) rate goals. Brief established goals to the commander for approval.

Contract Maintenance. Preplanning potential contract maintenance is crucial. Contact local Contracting Office to set up Blanket Purchase Agreements (BPA) or short-term maintenance contracts. Maximize use of ESP codes for funding support.

Inter-Service Support Agreements (ISSA). If available, contact local Department of Defense (DOD) components or government maintenance operations. Discuss establishing an ISSA for Vehicle Management support during contingencies and/or Air and Space Expeditionary Force (AEF) rotations. Ensure any ISSA address AF unique requirements for priority, types of maintenance and quality of services.

3.15. Temporary Mission Support Kit (TMSK).

If physically possible, individually assembled, boxed, TMSKs and shipped within the cab, trunk, and truck bed or on the forks of each vehicle. If this is not feasible, consider placing the most critical items (Technical Order (TO) and critical parts) in the cab or other vehicle compartments. If items shipped inside the vehicle are not readily visible (e.g., inside high reach or telephone maintenance truck compartments), identify location with a prominently placed label. Over-sized kits are be shipped to ensure the kit arrives at the same location with the vehicle.

Each assembled TMSK supports one-vehicle for 30 days with common and high-use items in the event of minor malfunctions before the establishment of supply chain and/or shop stocks at the deployed/forward location. Refer to VM Neighborhood for an example listing of possible TMSK items (this list does not include R-11’s or aircraft cargo loaders).

3.17. Training.

Repair Operations: Although difficult to predict the actual operating environment at a contingency location, it is possible to exercise personnel in a simulated or practice deployment. Prepare deployable personnel for flexible operations under adverse conditions.

Train them in the use of all tools and shop equipment. Pre-deployment training is not required unless specifically addressed via tasking “Line Remarks”.

Contingency Environment: Operations in a contingency environment may expose vehicle maintainers to many situations and problems not encountered in normal peacetime operations. Training provides the required knowledge and skills to plan for, respond to, and recover from conventional and irregular warfare Chemical, Biological, Radiological, Nuclear, and High-Yield Explosives (CBRNE) events.

To complement the training, installations may include realistic exercises and scenarios demonstrating the level of proficiency required for operating in a contingency environment and for evaluation purposes. Refer to AFMAN 10-2503, Operating in a Chemical, https://usaf.dps.mil/sites/AFVehicleFleetMgt/ https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword=10-2503&isObsolete=false&modID=449&tabID=131

Biological, Radiological, Nuclear, And High-Yield Explosive (CBRNE) Environment, for additional training information.

3.24. Facilities.

The Vehicle Management facility is a component of the Allowance Standard “159” Basic

Expeditionary Airfield Resources (BEAR) Order of Battle, Vehicle Maintenance/Operations Unit Type Code (UTC) (XF*VC). It comes in two different configurations, either Air (XFAVC) or Surface (XFSVC). It is specifically for Vehicle Maintenance, Ground Transportation and Management Operations. This UTC comes with one small shelter. For “maintenance” operations task two each 4K Dome UTCs (XF*AB - also comes in Air or Surface) along with AM-2 Matting (XF*AM) for flooring.

When geographically feasible, facilities should be accessible to the key functions supported (e.g., sortie-generating and Air Terminal Operations Center). It may be necessary to establish dispersed Vehicle Management locations.

A separate facility for refueling vehicles is highly desired. Some contingency locations may not have the capability to establish a separate Refueling Maintenance facility. Those operating locations may combine maintenance operations. Conduct combined maintenance operations under strict adherence to the following guidelines:

o Applies only to vehicles transporting diesel or aviation fuel.

o Properly train all assigned personnel in fuels management safety procedures.

o Maximum of one fuel truck inside shop at any time. Repairs and service are limited to the actual prime mover only (chassis, exterior, drive train, etc.).

o Properly ground vehicle using the vehicle’s static discharge grounding reel.

o No smoking, spark or flame within 50 feet of vehicle or shop area. A truck or trailer mounted refueling system should not be opened inside the main shop. Accomplish refueling system repairs in designated area/shop.

o Drain refueling system’s fuel storage tank as much as possible prior to entering shop to reduce mass spill potential. If the storage tank/system is not possible, and before entering the shop, ensure fuel system is completely closed and there are no leaks. Comply with all installation spill containment procedures.

3.28. Mobile Maintenance.

Mobile Maintenance can be used to perform PM&I and Special Inspections on vehicles not easily brought to or unable to enter the maintenance shop due to size. Advance coordination is essential for proper planning and scheduling.

The Mobile Maintenance truck may be equipped with a tow attachment, a battery booster and power plant, per Allowance Standard (AS) 457. The truck may carry tools (AS 403 and 457) and spare parts so that full PM&I and routine unscheduled work can be done. This truck may be two-way radio and/or cell phone equipped.

The VFM/VMS have the option to expand Mobile Maintenance to include performing minor maintenance at selected units. It may be desirable to send a mobile maintenance truck to large organizations (Civil Engineer Squadron (CES), Security Forces Squadron (SFS), Aircraft Maintenance, etc.) on a scheduled frequency to perform minor repairs. The VFM/VMS determines, and then justifies, the number of Mobile Maintenance trucks required.

If the required repairs are beyond Mobile Maintenance capabilities, request wrecker assistance from Ground Transportation. During other than normal operating hours, Ground Transportation delivers the disabled vehicle to the Vehicle Management parking area. The AF Form 1800, Operators Inspection Guide and Trouble Report, reflects the vehicle‘s problem and should accompany the vehicle. During the next duty day, the using organization formally turns the vehicle in to Vehicle Management.

3.33. Vehicle Triage.

Triage is the process of assessing damage, putting the priority vehicles first, and cannibalizing or doing whatever it takes to return vehicles back to service. Waive TO 36-1- 191, Technical and Managerial Reference for Motor Vehicle Maintenance, standards as necessary during active conflict. Field repairs may be the norm. Many vehicles can still do their mission without a fender or non-critical part/component. Refer to T.O. 36-1-191, Technical and Managerial Reference for Motor Vehicle Maintenance for additional reference information.

3.43. Vehicle Deployment Process.

Review the following source documents requirements:

o Schedule of Events (SoE).

o Any document the Unit Deployment Manager (UDM) submits that includes the UTC and the deploying vehicle.

o Submit a TRT request to change the Use Code to “L” if applicable.

o Collect and prepare all the following documents into an envelope.

o Sign for current day, AF Form 1800, Operator’s Inspection Guide and Trouble Report, or

AF Form 4427, Operator’s Inspection Guide and Trouble Report Fuel Servicing Vehicles & Equipment.

o Vehicle Waiver Card o DD Form 518, Accident Identification Card o AF Form 1297, Temporary Issue Receipt https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword=1800&isObsolete=false&modID=449&tabID=131 https://lims-ev.cce.af.mil/vehicles-trt/Main.html#/dashboard https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword=1800&isObsolete=false&modID=449&tabID=131 https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword=4427&isObsolete=false&modID=449&tabID=131 https://www.esd.whs.mil/Portals/54/Documents/DD/forms/dd/dd0518.pdf https://www.e-publishing.af.mil/Product-Index/#/?view=search&keyword=1297&isObsolete=false&modID=449&tabID=131 o Standard Form 91, Motor Vehicle Accident Report o Copy of vehicle LTI o Vehicle Historical Data Records o Signed DD Form 1348-1A, Issue Release/Receipt Document (copy #2). Keep copy #1 for FM&A files. Ensure deploying equipment custodian signs DD Form 1348-1A in the appropriate block.

o Issue a signed copy of AF Form 1297, Temporary Issue Receipt, to the deploying equipment custodian and retain signed original for FM&A files.

Instruct deploying equipment custodian to tape envelope on inside of vehicle window with registration # showing outside of window; do not block out the driver’s vision.

Fill out the actions processing log for deploying vehicles.

If vehicles are being permanently shipped process request via the TRT.

Before sending a Work Order to the shop, the FM&A Workload Controller should:

o Review the Upcoming Work Report, Repetitive Maintenance Work Order Inquiry, and the Wrnty/Svc/Sub Work Order tab. See current M&U Guidebook for instructions.

o Determine if new vehicle warranty, previous contract, vendor or other parts warranty covers discrepancy.

o All warranty provisions are input/tracked in DPAS M&U regardless of cost. See current M&U Guidebook for instructions.

Procedures for Processing Contract Maintenance Repairs:

o FM&A keeps active and inactive files on contract maintenance work order correspondence, coordinates with the VFM/VMS and the maintenance team lead, plans the workload, monitors the funding status and keeps files on work specifications.

o FM&A initiates work order and funding documents, i.e., AF Form 9, Request for Purchase, or Government Purchase Card (GPC) purchases request form, for all work done commercially. Documents include work specifications and other data as needed.

Send completed documents to the VFM/VMS, or designee, for review and signature. See current M&U Guidebook for processing contract repair work orders.

o Vehicle down time for contract work orders, including awaiting contract action, is Non- Mission Capable Maintenance (NMCM) time. See current M&U Guidebook for instructions for capturing NMCM.

o After the funding documents are certified or signed, retain one copy o FM&A arranges vehicle/component transport to the vendor o FM&A monitors contracted requirement and informs the VFM/VMS if requirement/timeline has changed https://www.gsa.gov/forms-library/motor-vehicle-accident-report https://www.acq.osd.mil/dpap/ccap/cc/jcchb/Files/FormsPubsRegs/DoD_Funding_Documents/dd13481a.pdf https://static.e-publishing.af.mil/production/1/af_a4/form/af1297/af1297.pdf https://lims-ev.cce.af.mil/vehicles-trt/Main.html#/dashboard…