AFI 21-116/AIA Supplement 1 Attachment 12 20 August 1995

AFI 21-116/AIA Supplement 1 Attachment 13 20 August 1995

AFI 21-116/AIA Supplement 1 Attachment 14 20 August 1995

AFI 21-116/AIA Supplement 1 Attachment 15 20 August 1995

AFI 21-116/AIA Supplement 1 Attachment 16 20 August 1995

AFI 21-116/AIA Supplement 1 Attachment 16 20 August 1995 Attachment 12 (Added)MISSION CAPABILITY (MICAP) REPORTING PROCEDURESA12.1. Overview. This attachment provides MICAP reporting procedures and describes use of the AIA MICAP Notification, RCS: AIA-LGS(AR)9501. MICAP reports are required to advise 67 SPTS/LGS of conditions resulting in equipment outage due to lack of parts and status of related parts requisitions.A12.2. Materiel Control Responsibilities. Material Control will:A12.2.1. Submit reports only on end items with MICAP reportable SRDs listed in REMIS.A12.2.2. Submit MICAP notifications by priority message within 24 hours after start of the MICAP condition.A12.2.3. Submit only verified backorders with UND 1 or J; do not report UND A requirements.A12.2.4. Advise 67 SPTS/LGS (with info copy to HQ AIA/LGSW) of MICAP receipt, downgrade, or cancellation within 24 hours of the change in status to close the MICAP incident.A12.3. MICAP Notification Procedures. Material control prepares and submits MICAP report and notification messages to identify parts requisitioned to restore mission equipment to full mission capability (FMC) to 67 SPTS/ LGS (with info copy to HQ AIA/LGSW) using format in Figure A12.1.A12.3.1. Report up to three MICAP incidents in each message. Number data elements (1 through 16) separately for each incident.A12.3.2 Provide an information copy of the notification message as applicable to HQ AIA/LGMY/A for airborne outage, HQ AIA/LGMY/G for ground system outage, and SA-ALC/LTMC for parts managed by SA-ALC/LT (previously AFCSC) (Source of Supply FPD).A12.4. MICAP Termination (Receipt, Downgrade, Cancellation) Procedures. Use the format in Figure A12.2 to terminate any number of MICAP incidents. Number data elements (1 through 4) separately for each incident. Use the appropriate MICAP deletion code to indicate the reason for termination on each incident.A12.5. Special Procedures.A12.5.1. If a piece of mission equipment is required to restore full mission capability, follow procedures in AFI 23-110.FROM: ORGANIZATIONTO: 67SPTS KELLY AFB TX//LGS//INFO: HQ AIA KELLY AFB TX//LGSW//INTERMEDIATE GROUP//LGM/LGS// HQ AIA KELLY AFB TX//LGMY(A)/LGMY(G)//(AS APPLICABLE) SA-ALC KELLY AFB TX//LTMI// (IF APPLICABLE)(CLASSIFIED ACCORDING TO USAFINTEL 201-1, PARA C-105C - IF APPLICABLE)SUBJ: AIA MICAP NOTIFICATION, RCS: AIA-LGS(AR)9501 REPORT1. MICAP CONTROL NUMBER. Enter the five-digit numeric MICAP control number assigned sequentially each calendar year. Example: 96-001.2. MICAP CAUSE CODE.3. STANDARD REPORTING DESIGNATOR (SRD).4. SOURCE OF SUPPLY; THAT IS, FPD, S9E, DET 2, DET 4, WR-ALC/LRL (Previously DET 8), as appropriate.5. PRIORITY AND URGENCY JUSTIFICATION CODE (UJC) OF THE REQUISITION (Example: 02/1E, 02/JE).6. QUANTITY AND UNIT OF ISSUE.7. FULL NOMENCLATURE OF PART REQUISITIONED, THAT IS, Auxiliary Signal Processor, NOT Aux Sig Proc.8. NATIONAL STOCK NUMBER (NSN) OF THE REQUISITIONED PART.9. PART NUMBER OF THE REQUISITIONED PART. (For parts ordered from Det 2, 4, or WR-ALC/LRL (previously DET 8), enter the applicable part number only, not the pseudo stock number.)10. MAJOR END ITEM OF EQUIPMENT.11. POSITION OF EQUIPMENT INDICATOR (POEI).12. REQUISITION NUMBER. ENTER COMPLETE REQUISITION NUMBER FOR THE PART REQUIRED; THAT IS, FB5004-8201-0054, FX7029-8102-0005.13. DATE AND TIME OF MICAP. Enter calendar date and local military time when the asset was backordered or upgraded.14. TECHNICAL ORDER NUMBER, FIGURE, INDEX AND PAGE/MAINTENANCE SERVICE BULLETIN NUMBER.15. NEXT HIGHER ASSEMBLY/SUBASSEMBLY.16. REMARKS. Enter any specific remarks about the particular MICAP condition or outage that 67 SPTS/LGS should know, that is, lateral support, partial receipt, or any other pertinent data.NOTE: All MICAP messages will reflect the proper security classification as outlined in the appropriate security classification guide. Message traffic not meeting the criterions of the classification guide will be sent as EFTO (ENCRYPT FOR TRANSMISSION ONLY), as a minimum.Figure A12.1. Sample AIA MICAP Notification Message.FROM: ORGANIZATIONTO: 67IW KELLY AFB TX//LGS//INFO HQ AIA KELLY AFB TX//LGSP//INTERMEDIATE GROUP//LGM/LGS//HQ AIA KELLY AFB TX//LGMY(A)/LGMY(G)// (AS APPLICABLE)AFCSC KELLY AFB TX//MMIII// (IF APPLICABLE)UNCLAS E F T OQQQQSUBJECT: AIA MICAP (RECEIPT/DOWNGRADE/CANCELLATION) TERMINATION1. MICAP CONTROL NUMBER. Enter the number used in the original MICAP Notification Message.2. DELETE CODE. (AFI 23-110, Volume II, Part Two, Chap 17)3. DATE AND TIME THE PART WAS RECEIVED, DOWNGRADED, OR CANCELED. Same format as used in the original MICAP Notification Message.4. REMARKS. Figure A12.2. Sample MICAP Termination Message.Attachment 13 (Added)UNIT CATEGORY DESIGNATION AND FUNCTIONAL ALIGNMENT

Cat I Units Cat II Units Cat III Units Cat IV Units

10 IS ISG MSS AFIWC/MSL Center Dets

48 IS 68 IS 23 IS

93 IS 381 IS 26 OSF

97 IS 390 IS 39 IS

301 IS 488 IS 94 IS

303 IS 324 ISFunctionally Supported Maintenance Activity (FSMA)

AFSMA Supporting Activity

33 IS 67 IG

OL-RS, 488 IS 488 IS

Det 1 67 IG (31IS) 43 ISTable 13.1. Unit Category Designation.CAT I MAINTENANCE COMPLEX ORGANIZATIONAL CHARTNOTES:1. Includes Administration and the Maintenance Superintendent.2. Maintenance Support may include Logistics Support, or Logistics Support may be aligned as a separate function directly under the Chief of Logistics.3. Includes Job Control and Materiel Control.4. When authorized to support special systems.5. When required to support airborne missions per AIAI 11-402.6. For proper span of control, one or more maintenance supervisors may be authorized by the Chief of Logistics. Not more than one supervisory level will exist between the production workcenter and the Chief of Logistics.Figure A13.1. Cat I Maintenance Complex Organizational Chart. CAT II MAINTENANCE COMPLEX ORGANIZATIONAL CHARTNOTES:1. Includes the Maintenance Superintendent and may include Administration.2. Maintenance Support provides some functions (reporting, controlling, etcetera) of the Job Control in Cat I units. Maintenance Support may include Administration, Logistics Support, and Materiel Control. 3. Materiel Control may be combined with FB/FX Supply if directed by the Chief of Logistics.4. Logistics Support may be aligned as a separate function directly under the Chief of Logistics.5. When authorized to support special systems.6. When required to support airborne missions per AIAI 11-402.Figure A13.2 Cat II Maintenance Complex Organizational Chart. CAT III MAINTENANCE COMPLEX ORGANIZATIONAL CHARTNOTES:1. Combines supporting tasks, such as Master PMI roster, Master ID Listing, PIPRs, etcetera, into one workcenter. Includes Administration functions.2. For FSMAs, the Chief of Logistics block includes the maintenance supervisor or the workcenter supervisor according to the size of the maintenance force required.3. Most Cat III units are authorized a Materiel Control function. A special supply account is authorized when needed to support special systems.Figure A13.3. Cat III Maintenance Complex Organizational Chart.CAT IV MAINTENANCE COMPLEX ORGANIZATIONAL CHART NOTES:1. If supported by a theater group, detachments should address issues through their group.2. The group should address all mission related issues to the center, with an info copy to the wing.3. The center is authorized a 24-hour Maintenance Control. Detachments report changes in equipment status to the center using applicable center guidance.Figure A13.4. Cat IV Maintenance Complex Organizational Chart. Attachment 14 (Added)RECOMMENDED FUNCTIONAL ADDRESS SYMBOLS FOR FIELD UNITS

LOGISTICS FUNCTION TITLE FAS

Chief of Logistics LG

Logistics Superintendent LG1STAFF ELEMENTS (NOTE 1)

Maintenance supervisor (only one used) LGM

Branch Chiefs (more than one maint supervisor) LGM1, LGM2, etcetera

Administration LGA

Logistics Support (P/O Chief of Logistics) LGL

Contract Liaison LGC

Standardization-Evaluation LGE

Maintenance Control (Cat I) LGH

Materiel Control (P/O LGH) LGHC

Maintenance Support (Cat I) LGQ

Maintenance Support (Cat II) LGG

Materiel Control (P/O LGG) LGGC

Administration (P/O LGG) LGGA

Special Supply Account (FB/FX) LGS

Materiel Control (aligned with FB/FX) LGSCMAINTENANCE WORKCENTERS (NOTE 2)

Radio/Ground Equipment LGMR

Antenna LGMW

AN/FLR-9 Maint LGMV

Satellite Systems LGMX

COMSEC/C3CM LGMY

CRITICOM LGMN

Data Systems/GPS/GCP LGMB

Conventional Systems LGMC

Airborne LGMJ

Computer LGMD

Flightline LGMF

ASARS Processing (APS) LGMA

Link/Communications Van LGML

Mission Control Maintenance LGMM

SENIOR YEAR (combined workcenters) LGMS

Imagery Exploitation (IES) Maintenance LGME

Production Support LGMO

TGIF/DGIF VAN LGMP

Zonal (ECU & Power Pro) LGMZ

Power Production LGMG

Environmental Control Units (ECU) LGMH

NOTES:

1. Functions may be organized as stand-alone FAS or as part of another FAS depending on workload involved and local management decisions. Examples are Logistics Support and Materiel Control.

2. Workcenters doing a similar job may be identified by numbers such as LGMR1, LGMR2.

Attachment 15 (Added)

FORMATS FOR MAINTENANCE STATUS REPORT (MSR)
AND AIRBORNE MAINTENANCE TECHNICIAN STATUS REPORT (AMT-SR)

A15.1. MSR Format. Use the following data and codes to document system use, status, and repair action.

A15.1.1. Address the MSR to the appropriate wing and depot responsible for system management and info other addressees as directed by higher headquarters.

A15.1.2. The message subject will include the program name (that is, COMBAT SENT, SENIOR YEAR, RIVET JOINT) and Maintenance Status Report.

Example: SUBJ: SENIOR YEAR MAINTENANCE STATUS REPORT

A15.1.3. In the first paragraph, provide the aircraft tail number, mission number, mission type, and success codes.

Example: 1. 12345/ABCDE/A/A.

Use the following mission type codes:

A - Operational and Exercise Mission.

B - Training Mission.

C - Busy RELAY.

Use the following mission success codes:

A - Complete mission

B - AIA-maintained system deviation, termination, abort.

C - ACC-maintained system deviation, termination, abort.

D - Other deviations (weather, sickness, etcetera).

A15.1.4. In the second paragraph, provide takeoff/landing times, scheduled/actual times, and scheduled/actual sensitive area (SA) times. Use Zulu times in DTG format.

Example: 2. TAKEOFF: 121212Z JAN 94; LAND: 122121Z JAN 94

SCHEDULED TIME: 4.0 HOURS; SCHEDULED SA TIME: 3.5 HOURS

ACTUAL TIME: 4.3 HOURS; ACTUAL SA TIME: 3.8 HOURS

A15.1.4. Document system status and titles in the next several paragraphs. This status must match the mission supervisor's assessment as documented on the PMFR. SENIOR YEAR MSRs will list each Standard Reporting Designator (SRD) assigned mission systems.

Use the following system status codes:

1 - System fully operational.

2 - Malfunction caused no mission impact.

3 - Malfunction caused reduced mission capability and outage.

4 - Malfunction caused mission termination or abort.

5 - System not used/required.

NOTE: Add an "F" to Codes 2 and 3 when malfunction was corrected during mission.

Example: CODE SYSTEM

3. 2F MIST

4. 1 TGIF

A15.1.5. A "REMARKS" section will follow the status paragraphs. Provide information on specific malfunction and repair actions for any system coded 2, 3, or 4.

A15.1.5.1. Include all PMFR REDCAP/outage (OD) times.

A15.1.5.2. Format:

First line: Paragraph Number, Status Code (Serial Number for SY sensors only): Discrepancy

Second line: C/A (Corrective Action): Repair action

Example: REMARKS:

3/2F: INTERMITTENT LINK.

C/A: RESEATED INTERFACE CONNECTOR.

A15.1.6. The final paragraph will be a "COMMENTS" section. Include information on any PMFR not covered in the MSR REMARKS section; comments on mission success codes B, C, or D; and comments on aircraft launch/recovery deviations.

Example: COMMENTS: LATE TAKEOFF DUE TO SNOW ON RUNWAY.

A15.2. AMT-SR Format (BIG SAFARI only).

A15.2.1. Submit the AMT-SR by message to 67 IW/LG with info copies to HQ AIA/LGMY, 26IG/LG, 692IG/LG, and all system-associated units.

A15.2.2. Paragraph 1 will contain name, rank, qualifications, date of separation or DEROS, and date next evaluation is due. NOTE: Under qualifications, enter the AMTs function if not in upgrade training (that is NCOIC, LG).

Example:

1. RANK NAME QUALIFICATIONS DOS/DEROS NEXT EVAL

(BL4 BL5 CS)

SSGT DOE III II IV APR 96 BL5/JUL 95

A15.2.3. In paragraph 2, comment on any situation possibly effecting flying/upgrade status for any AMT; that is, serious injury/illness, loss of clearance.

A15.2.4. List any assignment preferences for AMTs in paragraph 3.

A15.2.5. Paragraph 4 will list inbound and outbound AMTs.

Attachment 16 (Added)

REVIEW PROCEDURES FOR E-I PROJECTS DEVELOPED BY ISG TSS

A16.1. Introduction. Use this attachment to review E-I project packages developed by ISG TSS or when planning local or self-help projects. AFICR 100-14, AFIC Engineering Installation-Project Implementation, includes information for project reviews and preparation. Project reviews are systematic procedure to ensure the completeness and accuracy of project packages. Ensure all supporting workcenters review their portion of project packages. Publications required for performing a review or for preparing a self-help project:

AFR 700-4, Volume 1, Information Systems Program Management, and AFIC Sup 1 (AFI 33-104)

AFICR 56-16, Control of Compromising Emanations (TEMPEST)

ESCR 86-1, Standard Facility requirements for ESC Operations Buildings

AFICR 100-14, AFIC Engineering-Installation Project Implementation

AFIC Electronic Installation Standard 2-1

AFIC Electronic Installation Standard 2-2

NACSIM 5203, Guidelines for Facility Design and Red/Black Installation

TO 31-10-series, Standard Installation Practices

TO 31W2-10-12, Outside Plant Cable Placement

A16.2. General. TSS E-I project packages consist of various sections. Older project packages may differ in structure, but should still contain all the required information. Project packages normally consist of these sections:

General Information.

References.

Related Projects.

Support Requirements.

Installation Instructions.

Interposition Wiring Details.

Time Signal Distribution.

RF Distribution and Control System.

Materials.

Standard Drawings.

Facility Drawings.

A16.3. Review Procedures:

A16.3.1. Inventory the package. Use the drawing list to determine if the drawings or sketches provided with the package are the same as called for on the list. Check drawing numbers and revisions. If a project contains classified information, the classified portion of a project package may be mailed under separate cover.

A16.3.2. Read the package to become familiar with the projects requirements. Allow enough time to properly review the package. Remember there are many considerations to keep in mind during the review process. Try to identify and solve potential problems during this phase. Document review findings.

A16.3.3. Process recommended changes according to AFICR 100-14.

Chief of Logistics
NOTE 1Maintenance
ControlNOTE 3Logistics
SupportNOTE 2FB/FX Supply
AccountNOTE 4

Stan-Eval
NOTE 5Maintenance
Support
NOTE 2Maintenance
SupervisorsNOTE 6Production
Workcenters

Chief of Logistics
NOTE 1Logistics
SupportNOTE 4FB/FX Supply
AccountNOTE 5

Stan-Eval
NOTE 6Maintenance
SupportNOTESs 2, 3Production
WorkcentersChief of LogisticsNOTES 1, 2Maintenance Control
FB/FX SupplyAccountNOTE 3Production WorkcenterTheater Group
Logistics StaffNOTES 1, 2DetachmentCenter
Logistics StaffNOTE 3(Equipment Status Reporting)