• Home
  • Download PDF
  • Order CD-ROM
  • Order in Print
Project Codes - 14024_473
MILSTRIP message transmittal worksheet (NAVSUP 1353) - 14024_475

Aviation Ordinanceman 1 - Aviation theories and other practices
Page Navigation
  452    453    454    455    456  457  458    459    460    461    462  
used, they should be left blank. The optional Advice codes are listed in table 17-6. DATA BLOCKS L THROUGH V (REMARKS). Normally, requisitions should not contain remarks. Enter remarks only when absolutely necessary to identify acceptable substitutes, clarify delivery, or to indicate the planned firing month of training missiles. Avoid including superfluous data that can be coded within the MILSTRIP format. For example, by placing the UIC of the activity where the material is to be delivered in the supplementary address, by using Signal code J, and by providing an RDD, the requisitioner can encode where and when delivery should be made and eliminate any remarks. If remarks are used, you should ensure that a document identifier of AOE or A05 is used. 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: COLUMN ENTRY 1-3 Document Identifier: Enter A0A or A01 when requisitioning with an NSN. Enter A0D or A04 when requisitioning with a DODAC or an NALC. 4-6 Routing Identifier: Enter the routing identifier of the activity that is to receive the requisition for action. Routing identifiers are contained in the 17-12







Western Governors University

Privacy Statement
Press Release
Contact

© Copyright Integrated Publishing, Inc.. All Rights Reserved. Design by Strategico.