Message Requisitioning by DAAS

Ammunition MILSTRIP requisitions are prepared by fleet units in a specially coded standard format and transmitted by message directly to DAAS, Dayton, Ohio. DAAS redirects each requisition on the message to the activity indicated by the routing identifier. DAAS redirects the message by way of the automatic digital network (AUTODIN) system. The activity receiving the message takes the necessary action to fill or refer the requisition, as appropriate. Referrals and retransmittals are done by AUTODIN. The AUTODIN system provides the addresses with a punched card for each document in the originator's message. This process alleviates the need for message handling or keypunching by the addressee.

Table 17-6.-Advice Codes

Unclassified MILSTRIP requisitions without remarks are the only ammunition requisitions that qualify for DAAS transmission. As mentioned earlier, remarks can normally be avoided by careful coding of the requisition. When necessary, remarks can be transmitted in a separate (non-DAAS) message. The following types of requisitions are NOT submitted by DAAS:

1. Requisitions that require remarks

2. Requisitions for a CV loadout where the CV is loaded by an AE/AOE

3. Requisitions submitted to COMNAVAIRSYS-COM (for 8E COG material) or to COMNAVSEASYS-COM (for 8T or 8S COG material)

4. Requisitions with a classification of CONFIDENTIAL or higher

Requisitions that qualify for DAAS transmission are discussed in the following paragraphs.

FORMS.- NAVSUPForms 1353 and 1353-1, or a locally prepared MILSTRIP message transmittal work sheet, should be used to submit requisitions by DAAS. The sample worksheet shown in figure 17-10 is NAVSUP 1353.

FORMAT.- Refer to the format shown in figure 17-10. You should remember that this chapter deals specifically with units under the jurisdiction of CINCLANTFLT, and that some of the information is different for units under CINCPACFLT jurisdiction. However, the procedures for preparation of a NAVSUP 1353 are identical in both areas of jurisdiction

You should route the unclassified message for action to DAAS DAYTON OH, with information copies to CINCLANTFLT NORFOLK VA, the immediate operational commander, and the activity where the material is to be delivered (the supplementary address activity). The subject line should be AMMO MILSTRIP REQN. To be accepted for transmission by DAAS, each line can contain a maximum of 66 characters of data in the following sequence:

Figure 17-10.-MILSTRIP message transmittal worksheet (NAVSUP 1353).

Do NOT include paragraph numbers, slants between date elements, BLNK for blank data elements, remarks at the end of a line, or remarks at the bottom of a message.

MILSTRIP documents with different document identifiers, routing identifiers, or cognizance symbols may be included in the same message. DAAS will reroute each line item to the proper addressee.

REJECTED DOCUMENTS.- To preclude transmission of erroneous data, DAAS validates the following data fields in MILSTRIP documents:

1. Document Identifier code

2. Routing Identifier code

3. Quantity

4. Requisitioner

5. Supplementary address

6. Signal code

Omissions or invalid MILSTRIP codes in any of these fields cause DAAS to reject the document. DAAS sends a message back to the originator with a statement outlining the reason for rejection. Rejections are minimized by careful drafting and proofreading by personnel at the originating activity.

PROCESSING.- Requisitions coded in the above format and submitted to DAAS are automatically readdressed to the activity in the routing identifier. When the requisition cannot be filled by that activity, it is passed to the inventory manager for action to fill it. Supply status is provided to the requisitioner, the supplementary address, and to CINCLANTFLT according to the M&S code used. All status messages should come directly from the processing activity or from DAAS. These status messages should contain a subject line indicating that it concerns ammunition requisition status.