AIAI20-110

AIR INTELLIGENCE AGENCY INSTRUCTION 20-110

12 DECEMBER 1980

HQ AIR INTELLIGENCE AGENCY

Logistics

INITIAL PROVISIONING

This regulation establishes ESC policy and responsibilities for initial provisioning of systems, subsystems, and end articles of equipment. It adds to DOD, Air Force, and NSA procedures that apply to the Air Force Cryptologic Support Center (AFCSC) and this headquarters.

Corrected copy of ESC REGULATION 65-3

This revision changes OPR for provisioning from LGX to LGS and establishes levels of logistic management responsibility and related functions.

USAFSSR 65-3, 25 June 1971.

LGSS

MSgt J. A. Campbell

Col Carl S. Kelley

Jane L. Weddle

5

M; X: AUL/LDEA (1); AFISC/DAP (1)

1. Applicability. This directive applies to all systems, subsystems, and end articles of equipment for which AFCSC will be assigned Primary Inventory Control Activity (PICA) or Weapons Integrated Materiel Management (WIMM) responsibilities or for which HQ ESC is the operating or using command or Service Cryptologic Element (SCE).

2. Policies. Provisioning data requirements (provisioning technical documentation (PTD) and supplementary provisioning technical documentation (SPTD)will be determined by the Command Data Management Review Board based on the following:

2.1. Logistics concept established for the system and end articles.

2.2. In-use quantity and deployment.

2.3. Programmed operational life.

2.4. Any other information which will assist the review board to logically determine logisticmanagement responsibilities and associated data-support requirements.

3. HQ ESC Responsibilities:

3.1. DCS/Logistics(LG). LG will make sure that the actions in paragraphs 3 and 4 are followed and will determine the personnel required (quantity and function) to:

3.1.1. Represent ESC at conferences with AFLC, NSA, industry, and DOD activities involving coordination and implementation of improved and unified provisioning policies and procedures.

3.1.2. Act as command representatives at guidance and provisioning conferences for systems and end articles of equipment for which HQ ESC is or will be designated as the operating or using command.

3.2. Director of Supply (LGS). LGS will:

3.2.1. For ESC-used systems or end articles of equipment managed by AFCSC or other SCEs:

3.2.1.1. Develop policies and procedures for timely and adequate initial provisioning of new and modified systems or end articles of equipment.

3.2.1.2. Supervise the AFCSC initial provisioning program to make sure that it follows DOD, NSA, and USAF directives.

3.2.1.3. Serve as the control point of contact for final review (approval or disapproval) for all requests for deviation (except for technical documentation which will be coordinated with LGXY and AFCSC/MMLP) from an established contract covering AFCSC provisioning requirements.

3.2.1.4. When required, resolve differences and disagreements involving NSA, AFCSC, and other USAF provisioning personnel.

3.2.1.5. Review, write, or provide input as applicable to logistic support plans and initial logistic support plans and make sure that the plan provides for initial provisioning data requirements as determined by the Command Data Management Review Board.

3.2.1.6. Include PTD or SPTD requirements with all purchase requests and military interdepartmental purchase requests (MIPR) initiated by HO ESC or AFCSC for system and end articles of equipment procurements when AFCSC has been assigned PICA or Secondary Inventory Control Activity (SICA) responsibilities.

3.2.1.7. Make sure that quality control systems are carried out within the AFCSC provisioning area that will ensure that logistic support is established for all new systems and end articles of equipment being introduced into the AFCSC Inventory.

3.2.1.8. Give the AFCSC Provisioning Branch an annual projected provisioning planning schedule based on programmed HO ESC system and end article procurements for each forthcoming fiscal year period and update this schedule quarterly as program changes occur.

3.2.2. For ESC-used systems and end articles of equipment managed by other DOD activities:

3.2.2.1. Supervise the ESC Initial provisioning program to make sure that It follows DOD, NSA, and USAF directives; take part in guidance or provisioning conferences and ground support equipment (GSE) review board meetings.

3.2.2.2. Make sure that quantities provided are compatible with ESC maintenance and operational requirements.

3.2.2.3. Make sure that quantities for base stockage are according to Air Force policies in AFM 67-1.

3.2.2.4. Make sure that known program changes are Incorporated In provisioning action.

3.2.2.5. Make sure that peculiar stockage requirements are made known to conferees and are considered in provisioning actions.

3.3. Director of Logistics Plans (LGX). LGX will set up a Command Data Management Review Board according to AFR 310-1 and ESCR 310-1. This is an in-house, data-review board that Is made up of representatives of each functional office within ESC and AFCSC. The board members are responsible for recommending to the Command Data Management Office (CDMO) the documentation needed to support their specific functional areas of responsibility. LGXY ensures that the policies and procedures of the data management program are applied for all technical documentation including provisioning. As chair of this board, LGXY is responsible for working directly with DOD agencies, offices of primary responsibility, and contractors in resolving questions or interpreting ESC data requirements and data items for all functional areas.

3.4. Director of Maintenance (LGM). For ESC-used systems and end articles of equipment managed by DoD activities other than AFCSC or SCEs, LGM will ensure that:

3.4.1. There is participation in guidance or provisioning conferences and GSE review board meetings.

3.4.2. Source and expendability, recoverability, repairability, cost (ERRC) codes assigned to items are consistent with ESC maintenance capabilities.

3.4.3. Test equipment lists are matched to ESC maintenance requirements.

3.4.4. Requirements for local manufacture do not exceed units' capabilities.

3.4.5. Direct and indirect maintenance concepts are developed for the system and end article being provisioned.

3.5. All ESC Staff Offices: As the operating or using command, ESC personnel and functions will:

3.5.1. Consider, in conference actions, design changes authorized by known engineering change proposal actions.

3.5.2. Eliminate equipment duplication by consolidating contractor furnished equipment and single-purpose items Into multipurpose items when feasible.

3.5.3. Eliminate luxury-type Items.

3.5.4. Ensure that requests for advance Information or documentation from contractor agencies are coordinated with the conference chair to determine if such requests are within the scope of the contract; that is, that the Air Force can get the requested information without additional cost.

4. AFCSC Responsibilities:

4.1. AFCSC Commander (CC). The Commander, AFCSC, is responsible for:

4.1.1. The overall initial provisioning function for all systems or end articles of equipment when AFCSC has been assigned PICA or SICA responsibilities.

4.1.2. Ensuring that current DOD, NSA, AF, and ESC initial provisioning policies and procedures are followed.

4.2. Directorate of Materiel Management (MM). MM will:

4.2.1. Make sure that initial provisioning policies and procedures are kept current.

4.2.2. Set up and maintain adequate management controls to ensure:

4.2.2.1. Timely scheduling and conducting of guidance and provisioning conferences.

4.2.2.2. Effective performance of initial provisioning actions for systems and end articles of equipment when AFCSC has been assigned PICA or SICA responsibilities.

4.2.3. Make sure that the Provisioning Branch (MMLP) is the sole point of contact within AFCSC for all matters and communications (written or oral) pertaining to Initial provisioning.

4.2.4. Provide a qualified provisioning specialist to serve as the AFCSC provisioning chair or contracting officer representative for AFCSC-administered guidance or provisioning conferences. The provisioning specialist will serve as the AFCSC team leader for all guidance or provisioning conferences chaired by an acquisition element other than AFCSC and as PICA or WIMM chair when this logisticmanagement responsibility has been assigned to AFCSC.

4.2.5. Ensure that the provisioning specialist maintains administrative control of all conference functions and the representatives comprising the AFCSC provisioning team. Resolve problems concerning policy and procedures involving provisioning or source coding actions including differences and disagreements between conferees or contractor. Refer such problems (with all the facts) which cannot be adequately resolved to ESC/LGS.

4.2.6. Make sure that the contractor understands the PTD and SPTD requirements specified in the DD Form 1423, Contract Data Requirements List, for the system or end articles being provisioned.

4.2.7. Ensure that all PTD or SPTD is received from the contractor or acquisition element within the time established in the provisioning performance schedule (PPS). Revisions to the PTD or SPTD requirements or PPS submission dates are to be taken thru the HQ ESC CDMO.

4.2.8. Make sure that AFCSC/MMLP reviews, edits, evaluates, and either accepts or rejects all PTD or SPTD received from the contractor or acquisition element. When AFCSC/PMO is the acquisition element, formal acceptance or rejection of all PTD or SPTD will be made thru the HQ ESC CDMO. When the acquisition element is NSA or an SCE, only formal PTD or SPTD rejection notification will be taken thru the HQ ESC CDMO since acceptance is done by the acquisition element provisioning representative.

4.2.9. Compute initial spare and repair part requirements according to AFCSCR 57-3.

4.2.10. Start prompt procurement action of all spare and repair-part requirements (including increases, decreases, corrections, or cancellations) thru the appropriate acquisition element. Process investment-type spares (nonconsumables) being procured thru NSA or an SCE thru HQ ESC/LGS for validation of funds and MIPR assignment.

4.2.11. Assign applicable item management codes according to DOD 4140.26M, Volume I.

4.2.12. Establish initial supply support lists (ISSLs) or war readiness spares kits (WRSKs) for all systems or end articles of equipment provisioned by AFCSC.

4.2.13. Appoint qualified representatives to the HQ ESC Command Data Management Review Board according to ESCR 310-1. The AFCSC Provisioning Branch will act as the AFCSC Data Management Office and is responsible for consolidating and submitting AFCSC data requirements to the HQ ESC CDMO according to AFCSCR 310-1.

4.2.14. Give HQ ESC/LGS/LGX/LGM copies of all guidance or provisioning conference minutes.

4.2.15. Assign procurement-method codes and procurement-method suffix codes according to AFR 57-6.

4.2.16. Determine Service Item Control Center(SICC) requirements when another SCE is the WIMM and get SICC requirements when AFCSC is the WIMM.

4.2.17. Based on the program information provided by HQ ESC/LGS, develop a monthly schedule of guidance or provisioning conferences for the month ahead. Provide AFCSC/MAVC/MAVS a copy of both the annual and monthly schedule.

4.3. Directorate of Maintenance (MA). MA will:

4.3.1. Provide a qualified technical-services equipment specialist (ES) for the AFCSC provisioning team. The ES will act as team leader if the provisioning specialist is absent during conference periods.

4.3.2. Request technical-services representation from other AFCSC/MA activities as required for provisioning-team support.

4.3.3. Formulate depot maintenance concepts for systems or end articles of equipment being provisioned.

4.3.4. Make sure that AFCSC/MAV is the sole AFCSC action activity for assigning and changing maintenance repair level (MRL) codes, source codes, ERRC codes, demilitarization (demil) codes, and maintenance percentage factors.

4.3.5. Make sure the provisioning team members and contractors understand the maintenance concept, maintainability and reliability requirements, and level of repair applicable to the system or end article being provisioned.

4.3.6. Make sure the contractor understands general Air Force source coding and MRL procedures.

4.3.7. Make sure the contractor understands the breakdown level of repairable assemblies and the relationship of the maintenance manual parts list and PTD or SPTD.

4.3.8. Assign source maintenance recoverability and demil codes. Make final code determination and arbitrate all disagreements related to these codes.

4.3.9. Set up replacement, condemnation, and wear-out percentages or rates for applicable spare and repair parts.

4.3.10. Identity those spares and repair parts and the incremental range of those items required to set up ISSL and WRSK requirements.

4.3.11. Appoint a qualified representative to the HQ ESC Command Data Management Review Board according to ESCR 310-1.

5. Form. DD Form 1423, Contract Data Requirements List.

WILLIAM R. CARROLL

Lt Col, USAF

Director of Administration