The Army Maintenance Management System (TAMMS) Users Manual

1a. FROM (Originator). In addition to your unit, location, and ZIP Code or APO number, enter your Department of Defense Activity
Address Code (DODAAC).
1b. NAME, TELEPHONE NO. AND SIGNATURE. Type or print your name and duty phone (include DSN and commercial numbers).
1c. DATE. Type or print current calendar date; for example, 20 Jan 97.
2a. TO (Screening point). Enter the command and address from table 10–1. Use the MATCAT or FSC for the equipment used with the
computer software.
2b. NAME, TELEPHONE NO. AND SIGNATURE. Leave blank.
2c. DATE. Leave blank.
3. REPORT CONTROL NO. Enter the DODAAC of your unit (6 places) followed by the calendar year (2 places). Then give the number
of SF 368s submitted during the calendar year (4 places). For example, the first SF 368 for 1997 sent in by a unit with DODAAC
WK4FFF would be WK4FFF970001.
4. DATE DEFICIENCY DISCOVERED. Enter the calendar date, for example 10 Oct 92.
5. NATIONAL STOCK NO. (NSN). Enter the NSN of the bad item if one is known.
6. NOMENCLATURE. Enter the name of the computer software if available; for example, PDB2 initialization software.
9. SERIAL/LOT/BATCH NO. Enter the building number of the software being used.
16. DEFICIENT ITEM WORKS ON/WITH.
a. END ITEM (Aircraft, mower, etc.). Show type of end item and the model/series of the hardware that the computer software is used on
(for example, PATRIOT missile system, ECS).
b. INSPECTED. Leave blank. (this should read next higher assembly—query author)
22. DETAILS. Enter the following information. If more space is needed, use a continuation sheet. Be sure to enter the Report Control
Number (block 3) on the continuation sheet.
Failure detected during. Show when the failure was found—that is, during scheduled maintenance, test, storage, normal operation,
inspection, or handling.
First indication of trouble. Tell about the conditions present when the first sign of trouble was noticed—that is, stopped working, did not
perform as needed, false targets, and so on.
Circumstances prior to difficulty. Enter all the details of what was happening before the trouble started. Include the hardware
configuration/set up. These details help the investigator. Be sure to tell about any modifications directly related to the problem. Any other
information that might help the investigator should also be given here. Attach hard copy printout or other information when possible.
Classified information may be kept by originators as exhibits. No classified information may be entered on the SF 368 or mailed with it.
Description of difficulty. Write a thorough description of the problem including the effects on the user, mission, or equipment.
Cause. Outline the most likely cause of the problem or need for improvement.
Action taken. Give a short summary of what was done to correct the problem. List exhibit information, that is, exhibit held, destroyed, or
turned into supply.
Recommendations. Give any suggestions to help prevent future problems, improve the equipment, or change instructions.
23. Location of deficient materiel. Enter the unit name, location, and ZIP Code or APO number where the deficient materiel is located.
24a-27b. To be completed by the USAMC screening point.
Figure 10–2. Sample SF 368 used to report computer software deficiencies
DA PAM 750–8 22 August 2005
193