|
|
||
|
|
FAQ
1. In FEDLOG there are many U.S. NSNs which have NCAGE codes that are not applicable to the U.S. Some NSNs have only such NCAGEs. Why is this?Many years ago, we did assign some U.S. NSNs to items manufactured in other NATO countries. However, we no longer do this. For all items manufactured in other NATO and Tier 2 countries, we request NSN assignments from the appropriate NCB. However, we still assign NSNs to items manufactured in other countries, as long as no other NATO and Tier 2 country has already assigned an NSN to the item. 2. If an item is canceled, and later the NSN is again needed, should we reinstate the NSN?Generally it is better to reinstate an NSN. However, there are circumstances where it is better to catalog the item with a new NSN; for example, if the country who has design control is now a Tier 2 country, then they should catalog the item. 3. How does assigning NCAGE codes to non-manufacturers work?NCAGEs may be assigned to manufacturers or non-manufacturers. Each NCAGE is assigned a Type Code (DRN 4238) that indicates the type of organization. See ACodP-1, Chapter V, Table 129, for a list of Type Codes and their definitions. Type "A" NCAGEs are manufacturers and Type "F" NCAGEs are non-manufacturers. The goal of the NATO Codification System (NCS) is to identify the true manufacturer or design control authority of each item. Thus, the standard is to assign Type "A" NCAGEs and their associated part numbers as the prime reference (RNCC/RNVC 3/2) on all NSNs. However, in some rare cases where the codifier cannot identify the true manufacturer or design authority, a Type "F" NCAGE is listed as a prime reference. It is always allowable to assign Type "F" NCAGEs and their associated part numbers to references as secondary references (RNCC/RNVC 5/2). FED LOG, and the NATO MCRL contain all types of NCAGEs. 4. How are the prices in FED LOG determined?Price data are included in FED LOG, which draws its data from U.S. FLIS data base. These prices generally represent the price that U.S. users in the field pay for items. The data is provided to FLIS by the U.S. item manager. These prices are not FMS prices nor are they the prices charged by manufacturers. Military prices, like prices in the civilian world, are frequently subject to change based on many factors. In addition to normal prices fluctuations, the U.S. updates all prices once per year as part of the "surcharge" program. For more information on DoD's annual price update and price stabilization program, see DoD 4100.39M, Volume 6, Chapter 9 (available on the Internet at http://www.dlis.dla.mil/flis_procedures.asp. 5. We need a lot of information to utilize the FEDLOG and other US codification products for our own use, where can we turn for help?There already is a FED LOG FAQ, at http://www.fedlog.com/main.php. Also, in the "help" application built into the FED LOG product, you will find plenty of information about the product, including a user manual and tutorial. Additional information about fed log may also be obtained from the fed log customer support office, details as follows:
6. What is the purpose and usage of your (U.S. NCB) internal Item Name Code (INC)?DLIS does not use internal Item Name Codes (INCs). We only use the INCs that are published in the H6/ACodP-3. However, please note that INCs in the system support file that begin with alpha characters refer to colloquial names. 7. We would like to know the purpose and criteria for assigning the Department of Defense Ammunition Code (DODAC)?DODAC are contained in the H3 product and are define as follows: Department of Defense Ammunition Codes (DODACs) are used by the U.S. military services for the following purposes.
8. Are two NSNs allowed to contain the same part number?Normally, two NSNs cannot be assigned to the same part number, unless the part number is considered obsolete on one of the NSNs or there is some other special reason. For a list of the reasons, see the reference Number justification code (RNJC) definitions found in ACod-1, Chapter V, Table 06. Systems edits normally prevent the same part Number from being assigned to two NSNs, except for the reasons just Mentioned and one other: the same part number can be on to or more NSNs if the part number is non definitive, as indicated by the reference number variation code (in particular, RNVC 1). 9. Can anyone just use the online FIIGS available at the DLIS website?Anyone who wishes may download FIIGs from Internet and utilize them as they wish free of charge. They are available at: http:www/dlis.dla.mil/fiigs/default.asp 10. How does one match Master Requirement Codes (MRCs) with the FIIG edit guide?DLIS does not have a tool that links MRCs between either the Internet or CD-ROM FIIGs and the FIIG Edit Guides. The Master Requirement Directory (MRD) works in concert with the Edit Guides to provide the logical and edit relationships, which are pictured in either the paper or electronic FIIG publications. 11. Why is the RNCC 1 limited to only certain types of item identifications?Reference numbers that are coded RNCC 1 are "source control," which means that a design control authority must test and certify all parts that are associated with that item of supply. Normally, source control drawings have two or more items of production listed on them. Therefore, it would be incorrect to code a source control item with Type of Item Identification 1A or 4A. The reason for this is that Types 1A and 4A require that "the item of supply is limited to a single item of production and cannot be identified on the basis of the descriptive characteristics alone." Source control items cannot be identified on the basis of descriptive characteristics alone because they require testing and certification by the source control authority. See the U.S. FLIS Volume 4, Chapter 4 (at http://www.dlis.dla.mil/flis_procedures.asp on Internet) for more detail on this issue. 12. Do "bar codes" replace NSNs?No, bar codes are simply manufacturer's part numbers and can be recorded in the NCS within NSNs. History has taught us that manufacturer's part numbers are not sufficient information with which to manage the flow of supplies, thus the need for NSNs. |
|
|
© 2000-2009 PACS - All rights reserved.
PACS - Is an Initiative of PASOLS |
||
