*DLM 4000.25, Volume 2, December 27, 2022*

*Change 15*

**C30. CHAPTER 30**

**PROCEDURES FOR SERIALLY MANAGED MATERIEL REQUIRING OWNER VISIBILITY**

C30.1.  GENERAL.

	C30.1.1.  Purpose.  This chapter covers the additional procedures required for serially managed materiel requiring owner visibility.  See section C30.5. for the categories of serially managed materiel covered by this chapter.  

		C30.1.1.1.  For these procedures, the serial number is mandatory in the DLMS transaction, as is the unique item identifier (UII), when available--the intent is to capture both serial number and UII. Many legacy items have not been marked with an assigned UII; therefore, the UII cannot be considered a mandatory data element until transition to management by UII is complete across the Department of Defense.[footnoteRef:1]  That is the context in which the term “serial number/UII” is used in this chapter. [1:  The UII is an identifier used to uniquely identity an individual item used within the Department of Defense.  The UII may be a DoD Recognized IUID equivalent [e.g., Vehicle identification number (VIN)] or a composite structure defined by the Department of Defense [refer to UII Construct 1 and UII construct 2].  Refer to DoD policy and supporting documentation for specific IUID guidance at www.acq.osd.mil/dpap/pdi/uid/index.html.  Refer to the most current version of MIL-STD-130 for specific guidance marking of U.S. Military property.] 

***C30.1.1.2.  Serially managed items requiring owner visibility will follow DoD serial number guidance as stated in C30.4.4.  Any serially managed item coming to the DoD, regardless of the source, must comply.  DoD Components will add the necessary contractual clause to ensure vendor compliance in any new procurement contracts/acquisition actions.  This requirement will safeguard the integrity of the serial number in all of DoD systems.  Legacy items will only need remarking prior to inter-component shipments.  A legacy item with a non-compliance serial number will stop the receipt process and result in the materiel to be suspended awaiting disposition.***

***C30.1.1.3.  Under capital equipment and active UIT programs, the definition for line item includes the NSN + SCC + serial number + UII + owner.  However, for the physical storage of serially managed items, the intent is to allow DoD Components to store materiel by NSN, SCC, and owner and not by serial and UII.  This will allow storage activities to store multiple items of the same NSN, SCC, and owner in the same location.***

		C30.1.1.***4***. These procedures require record keeping by both the owner and storage activity and the constant transaction exchange at the item instance level (serial number/UII) to ensure that the records of both reflect the correct serial numbers/UIIs, by storage location, owner, and supply condition code (SCC).

	C30.1.2.  Transactions.  This chapter addresses the following DLMS transactions with their functions identified by their beginning segment and transaction type code.  Transactions identified support the business process, but may not actually be used to exchange serial number/UII.  The procedures in this chapter require that a system transact business interchanges using DLMS transactions,  The DLMS Implementation Conventions (IC)  are available on the Defense Enterprise Data Standards Office (DEDSO) Website on the DLMS IC Page. 

		C30.1.2.1.  Receipt Transaction is DLMS 527R with beginning segment (1/BR02/020) Transaction Type Code D4 – Receipt.    

		C30.1.2.2.  Standard Supply Discrepancy Report is DLMS 842A/W with beginning segment (1BNR06/0200) Transaction Type C1 – Claim Information.  

		C30.1.2.3.  Storage Quality Control Report (SQCR) is DLMS 842S/Q with beginning segment (1BNR06/0200) Transaction Type 03 – Report Message.  Use beginning segment (1/BNR01/0200) Transaction Set Purpose Code to distinguish the purpose.  

		C30.1.2.4.  Physical Inventory Request is DLMS 846P with beginning segment (1/BIA02/020) Report Type Code TC – Physical Inventory Request.  

		C30.1.2.5.  Response to Physical Inventory Request is DLMS 846P with beginning segment (1/BIA02/020) Report Type Code DD – Distributor Inventory Report.  This transaction is only used as a Response to Physical Inventory or follow-up when there is no record of stock number or no record of ownership (Management Code R), when physical inventory is in workload bank or in process (Management Code S), or when responding to follow-up when inventory is already complete (Management Code Y).  The usual response to a request for inventory is a 947I Inventory Adjustment in accordance with Chapter 6.

		C30.1.2.6.  Transaction History Request Transaction (from owner/manager to distribution) is DLMS 846P with beginning segment (1BIA02/020) Report Type Code  TF – Transaction History Request.  

		C30.1.2.7.  Response to Transaction History Request Transaction (when no history available) is DLMS 846P with beginning segment (1BIA02/020) Report Type Code AD – Agent/Distributor Inventory Report.  

		C30.1.2.8.  End of Day Transaction Count is DLMS 846P with beginning segment (1/BIA02/020) Report Type Code B1 – Batch Report.  

		C30.1.2.9.  Location Reconciliation Request is DLMS 846R with beginning segment (1BIA02/020) Report Type Code LC – Location Reconciliation Request.  

		C30.1.2.10.  Location Reconciliation Notification is DLMS 846R with beginning segment (1BIA02/020) Report Type Code X4 – Summary Report.  

		C30.1.2.11.  Location Reconciliation History Notification is DLMS 846R with beginning segment (1BIA02/020) Report Type Code ZZ – Mutually Defined.  

		C30.1.2.12.  Shipment Status is DLMS 856S with beginning segment (1/BSN06/0200) Transaction Type Code AS – Shipment Advice.  

		C30.1.2.13.  Shipment Status Materiel Returns is DLMS 856R with beginning segment (1/BSN06/0200) Transaction Type Code FT – Material Return.  For other types of materiel returns such as retrograde shipment for return of discrepant/deficient materiel or repair outside of the MILSTRIP Returns Program, use Transaction Type Code RD – Returns Detail.  Must use the ASC X12 Version 4030 as this version allows the UII to be carried in single data field

		C30.1.2.14.  Acceptance Report is DLMS 861 with beginning segment (1/BRA04/020) Receiving Advice or Acceptance Certificate Type Code 9 – Authorized Representative in Receipt of an Acceptance Alert.

		C30.1.2.15.  Materiel Release Confirmation is DLMS 945A with beginning segment (1/W0611/0200) Transaction Type Code NJ – Material Release Confirmation.  Must use the ASC X12 Version 4030 as this version allows the UII to be carried in single data field.

		C30.1.2.16.  Inventory Adjustment is DLMS 947I with beginning segment (1/W1505/0200) Transaction Type Code NU – Inventory Adjustment and use of 2/W1901/0200 Quantity or Status Adjustment Reason Code.  Must use ASC X12 Version 4030 as only this version includes the capability to carry UII.

C30.2.  APPLICABILITY AND SCOPE.

	C30.2.1.  The provisions of this chapter apply to the Military Departments including Coast Guard and Defense Agencies (hereafter referred to as the DoD Components).

	C30.2.2.  This Chapter’s procedures supplement (are additive) the procedures in DLM 4000.25, Volume 2, Chapters 4, 5, 6, 7, ***10,***11, 13, 14, ***16,*** and 17.

	C30.2.3.  The procedures in this chapter can only be implemented by Automated Information Systems (AIS) that have implemented the DLMS ANSI ASC X12 ICs or the equivalent DLMS XML business partner interchange transactions.

C30.3.  EXCLUSIONS.

	C30.3.1.  Classified activities that determine the visibility of specific items may compromise operational security must request guidance from their DoD Components.

	C30.3.***2***.  ***The DoD excludes all i***tems that are ***not******cataloged***in the ***Federal Logistics Information System (FLIS) from the procedures in this chapter, with the exception of management control numbers (MCN) under the SA/LW Program.***

	C30.3.***3***.The procedures in this chapter do not directly address update of the IUID registry.  The procedures for updating the IUID registry are contained in the DoD Procurement Toolbox found on the “Unique Identification” link at https://dodprocurementtoolbox.com.  ***Procurement Integrated Enterprise Environment (PIEE)*** eBusiness Suite web based training video tutorials of different aspects of the IUID registry and baseline functionality are available at ***https://piee.eb.mil/***.

C30.4.  POLICY.

	C30.4.1.  DoD Instruction 8320.04, Item Unique Identification (IUID) Standards for Tangible Personal Property, dated September 3, 2015 states, “The unique item identifier (UII) will be used globally as the common data key in financial, property, acquisition, and logistics (including supply and maintenance) automated information systems to enable asset accountability, valuation, life-cycle management, and counterfeit materiel risk reduction.”

	C30.4.2.  DoD Components will follow the IUID procedures identified in DODM 4140.01, Volume 9, “Materiel Programs”, and Volume 11, “Inventory Accountability  and Special Management and Handing. 

	C30.4.3.  The DoD Integrated Requirements Set (IRS) for IUID in Supply Business Processes documents the ODASD(Logistics) vision for the integration of IUID at the transactional level. 

	C30.4.4.  DOD established overarching guidance for the serial number convention and only alpha numeric (A-Z, 0-9), dashes, and forward slashes are allowed with a maximum field length of 30 characters. Spaces are not allowed.  DOD Components must ensure future procurement actions require vendors to follow serial number convention guidance as applicable.  ODASD (Logistics) will update appropriate DOD policies to reflect these changes followed by the implementation of this change.  Consequently, DEDSO will develop a change to incorporate these changes in all applicable DLMS transactions and manuals. 

C30.5.  CATEGORIES OF SERIALLY MANAGED MATERIEL COVERED BY THIS CHAPTER

	C30.5.1.  DoD Unique Item Tracking Programs.  The procedures in this chapter apply to items within a DoD level (inter-DoD Component) unique item tracking (UIT) program[footnoteRef:2].   [2:  This chapter does not apply to the DoD Small Arms and Light Weapons Serialization Program (DoDSALWSP) pending implementation of weapon transaction reporting using standard supply logistic transactions.  The Defense Enterprise Data Standards Office will address DoDSALWSP use of standard logistics transactions by a proposed DLMS change.] 

		C30.5.1.1.  Unique Item Tracking Designator Codes. 

			C30.5.1.1.1.  The UIT designator code indicates that an item is part of an established UIT program.  In accordance with DODM 4140.01 policy, the DoD Components will not establish any new UIT programs.  The FLIS is the authoritative source for UIT designator codes.

			C30.5.1.1.2.  DoD Components apply the appropriate FLIS UIT designator codes to NSNs in existing UIT programs.  Table C30.T1. shows authorized UIT designator codes.  Ensure that the integrated materiel manager (IMM) applies the UIT designator code to every NSN comprising the DoD level program, for which a UIT designator code is not already assigned.  The IMM assigns UIT designator codes to a NSN based on direction by the DoD Component UIT central control point.  The UIT designator code, in conjunction with FLIS IUID Indicator Y, provides the DoD Components a systemic means to identify that an NSN is subject to these procedures.  For system to system updates of the UIT designator code, activities should subscribe to the UIT data through the FLIS Portfolio Data Warehouse which is Logistics Information Services Master Data Capability.  To negotiate this XML Data Exchange/Subscription, send an e-mail request to J62FPDWPMO@dla.mil

			C30.5.1.1.3.  Table C30.T1. shows the UIT Designator Codes

		C30.5.1.2.  DoD Small Arms and Light Weapons Serialization Program (DoDSALWSP).  ***The DoD SA/LW Serialization Program is subject to the IUID transactions requirements identified in this chapter.  In addition, section 30.13. provides specific instructions for scenarios pertaining to SA/LWs.***

***C30.5.1.2.1.  To maintain full accountability of all SA/LW within the DoD, Components will ensure all SA/LW are properly recorded and managed in their respective accountable system of record in accordance with DoDM 4140.01.  All SA/LW must be reconciled by line item as stated in the DLM 4000.25, Chapter 6 Physical Inventory Control. Components will follow the procedures in this chapter as well as those listed in paragraph C30.2.2. for intra and inter Component shipments pertaining SA/LW.***

***C30.5.1.2.2.  The accounting of SA/LW includes, but is not limited to:  Newly procured weapons; returns; Weapons procured from commercial sources to include offline ordering; Lost, abandoned, or unclaimed privately owned weapons turned over for disposal; Weapons purchased with non-appropriated funds turned over for disposal; Ceremonial/Training weapons; Lost, stolen, and/or recovered weapons; Captured, confiscated, or abandoned enemy weapons; Recovered weapons turned over to the DoD by law enforcement or foreign countries; Museum/historical weapons; and Loans.***

***C30.5.1.2.3.  DoD Components must establish active, inactive and historical records of all SA/LW to include those previously under custody/ ownership.   All SA/LW records must be retained in accordance with the National Archives and Records Administration (NARA).  The history of weapons must be readily available to respond to FOIA requests, law enforcement inquiries, or any other official request from an authorized organization.***

		C30.5.1.3.  Security Risk Category I Non-Nuclear missiles and Rockets. Items subject to Security Risk Category I Non-Nuclear missiles and Rockets UIT program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAB.

		C30.5.1.4.  Radiation Source Tracking System Program (RASTS)[footnoteRef:4] [4:  Radiation Testing and Tracking System (RATTS) was replaced by Radiation Source Tracking System (RASTS).  NRC licenses 12-00722-13 and 12-00722-14 covering Chemical Detection Equipment (CDE) and Tritium are obsolete terminated licenses and are replaced by NRC license 21-32838-01.] 

			C30.5.1.4.1.  Radiation Source Tracking System Program (RASTS) is a program established to provide regulatory and statutory compliance with Federal, state, and local regulations for the use of radioactive materiel in fielded chemical defense equipment and in industrial applications.  It is designed to provide strict control and identification of all radioactive sources to comply with relevant Nuclear Regulatory Commission (NRC) license requirements.  

			C30.5.1.4.2.  Identifying RASTS Items:  Items subject to the RASTS UIT program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAC.

		C30.5.1.5.  Navy Depot Level Reparable (NDLR) Program  

			C30.5.1.5.1.  The NDLR UIT program is the recognized inter-DoD Component program for select Navy-managed Depot Level Reparables (DLR). 

			C30.5.1.5.2.  Identifying NDLR UIT Program Items:  Items subject to the Navy DLR UIT program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAD.

 			C30.5.1.5.2.  Interim Process for NDLR UIT Program.  Navy and DLA Distribution previously activated the NDLR UIT program with a limited set of DLMS transactions.  Navy and DLA Distribution will continue that process as an interim process, until they implement Chapter 30 procedures.  DLMS will eliminate this interim procedure at that time.  Navy’s target implementation date to transition to the Chapter 30 procedures for the NDLR UIT program is unknown.

		C30.5.1.6.  Aviation Component Tracking Program

			C30.5.1.6.1.  The Aviation Component Tracking Program is designed to ensure unique identification for U.S. Army Aviation equipment flight safety parts and for life managed or special interest items.  It provides for control, improved accountability, and visibility of U.S. Army Aviation equipment. 

			C30.5.1.6.2.  Identifying Aviation Component Tracking Program UIT Items:  Items subject to the Aviation Component Tracking Program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAF.

		C30.5.1.7.  Tritium Unique Item Tracking Program  

			C30.5.1.7.1.  The Tritium UIT Program identifies all primary and secondary items comprised of tritium throughout the Army, Army Reserve, National Guard, and Marines.  This program is necessary to meet an Army requirement for location visibility of all tritium sources at all times.

			C30.5.1.7.2.  Identifying Tritium UIT Program Items:  Items subject to the Tritium UIT Program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAG. 

		C30.5.1.8.  Controlled Cryptographic Items (CCI)

			C30.5.1.8.1  Controlled Cryptographic Items UIT Program.  The CCI UIT program was established to meet National Security Agency requirements to maintain visibility of controlled cryptographic end items.  

			C30.5.1.8.2.  Identifying CCI Items:  Items subject to the CCI UIT program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAH.

		C30.5.1.9.  Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM)

			C30.5.1.9.1.  Air Force program for providing positive inventory control for NWRM.  

			C30.5.1.9.2.  Identifying PIC NWRM Items:  Items subject to the PIC NWRM UIT program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAJ.

			C30.5.1.9.3. Air Force Integrated Logistics Solution-Supply (ILS-S) (Retail Supply) and Supply Status.  Air Force will use Supply Status (DLMS 870S) in Air Force ILS-S (Retail Supply), on an intra-Air Force basis to provide the latest status to the intended receiving activity, including UII and/or serial number in support of the PIC NWRM UIT program.  For legacy items where the UII has not been marked in accordance with IUID policy, the serial number alone will be passed.  The Defense Automatic Addressing System (DAAS) will enable transmission of information copies of the ILS-S Supply Status to the NWRM PIC Fusion Module to ensure the PIC NWRM UIT program has near real time access to UIIs and the associated serial numbers of NWRM item movements. 

			C30.5.1.9.4.  Retail Supply and Transportation Interchange.  (See DLM 4000.25, “Defense Logistics Management Standards Manual,” Volume 3, Chapter 2.)  For designated supply trading partners (currently limited to the Standard Base Supply System (SBSS) – Cargo Movement Operations System (CMOS) interface):.

				C30.5.1.9.4.1.  Use the DLMS 940R Materiel Release Order (MRO) to support the PIC NWRM UIT program.  Pass UIIs and the associated serial number in the MRO for each item meeting the PIC NWRM UIT program criteria.  For legacy items where the UII has not been marked in accordance with IUID policy, the serial number alone will be passed.

				C30.5.1.9.4.2.  Use an information copy (image) of the DLMS 940R MRO and DLMS 945A Materiel Release Confirmation  in support of Air Force PIC Fusion program data requirements.  The routing of an additional information only copy of the DLMS standard transactions (940R and 945A) is authorized for forwarding PIC Fusion data needed for the Air Force UIT registry.  This is a specific authorized use with unique identifiers to flag the transaction as information only.

			C30.5.1.9.4.  Interim Process for PIC NWRM UIT Program.  Air Force and DLA Distribution previously activated the PIC NWRM UIT program with the limited set of DLMS transactions shown in Table C30.T4.  Air Force and DLA Distribution will continue that process as an interim process, until they implement Chapter 30.  DLMS will delete this interim procedure at that time. The Air Force target implementation date to transition to the Chapter 30 procedures for the PIC NWRM UIT program is unknown.

******C30.5.2.  Serially Managed Items under UIT Designator Code AAK.[footnoteRef:12] [12:  Refer to ASC 1317.] 

		C30.5.2.1.  UIT Designator Code AAK identifies assets requiring serial number tracking for Service Owned items, to include capital equipment, when no other UIT program applies.  UIT Designator Code AAK enables Components to address serially managed items that they store, beyond those items that require special handling under existing UIT designator codes.  The intent of this new program code is to account for serialized items stored at DLA Distribution Centers, however, UIT Designator Code AAK is available to all DoD storage activities.

	C30.5.2.2.  Following the initial implementation by DLA, the Services will be able to classify items as serialized under the UIT Designator Code AAK by submitting the change to FLIS.

C30.6.  OBJECTIVES.

	C30.6.1.  Establish visibility by serial number/UII, from point of entry into the DoD logistics systems through disposal, demilitarization, or shipment outside the control of the Department of Defense.

	C30.6.2.  Reestablish serial number/UII visibility over materiel previously shipped outside the DoD’s control when it is reintroduced to DoD control.

	C30.6.3.  Require the use of standard logistics transactions to interface serial number/UII reporting between/among owners, the DoD Components, and suppliers.  The objective is to populate accountability and owner records using standard DLMS logistics transactions.

C30.7.  ESTABLISHING INITIAL VISIBILITY BY SERIAL NUMBER/UII

	C30.7.1.  Establishing serial number/UII visibility may begin at any point in the supply chain.  Customarily, “cradle to grave” serial number/UII tracking begins at the time of Government acceptance from the supplier/manufacturer.

	C30.7.2.  Alternatively, serial number/UII visibility may begin after items are already in the DoD logistics system.  Examples are items that meet the criteria and are already in the inventory, or returns to inventory at any time after the item was originally accepted by the Government.

C30.8.  REQUIREMENTS FOR  SERIALLY MANAGED MATERIEL REQUIRING OWNER VISBILITY 

	C30.8.1.  General Requirements. The DoD Components will:

		C30.8.1.1.  Maintain AIS(s) necessary to apply management in accordance with DODM 4140.01 IUID requirements.  Maintain visibility by serial number/UII, within owner, and DoD storage activity AISs to include the custodian’s system of record which is the official auditable quantity for an item of inventory.

		C30.8.1.2.  Use DLMS transactional interfaces among AISs to ensure that visibility exists in all AISs at the serial number/UII level.

		C30.8.1.3.  Apply the appropriate FLIS IUID indicator to NSNs for which they have PICA responsibility.  The IUID indicator provides the DoD Components a systemic means to identify whether an NSN requires tracking by serial number and the UII when available.  The FLIS IUID indicator currently has two values (Y) indicating that IUID marking is required and (N) indicating IUID marking is not required.  For system to system updates of this data, activities should subscribe to the IUID data through the FLIS Portfolio Data Warehouse which is DLA Logistics Information Services Master Data Capability.  To negotiate this XML Data Exchange/Subscription, send an e-mail request to J62FPDWPMO@dla.mil

		C30.8.1.4.  An item’s NSN, in conjunction with the serial number/UII will be the means for tracking an item in a logistics AIS.  Management is not possible if there is no NSN recorded in the FLIS.  Item visibility will be by NSN, owner, SCC, serial number/UII.  DLMS provides flexibility to accommodate tracking by NSN, serial number and UII.

		C30.8.1.5.  Owner visibility tracking by serial number/UII will cease when DLA Disposition Services acknowledges receipt of serially managed materiel.  DLA Disposition Services will validate serial number/UII for serially managed materiel during receipt processing and provide an SDR to the turn-in activity for any discrepancies.

		C30.8.1.6.  Retention of Source Documents and Transaction History. Activities may require audit capability for a period of time following the processing of documents and transactions for serially managed materiel.  Activities will maintain and dispose of documents and transaction history records in accordance with DoDI 5015.02, DoD Records Management Program.

	C30.8.2.  Specific Serial Number/UII Requirements.  DLMS Transactions will always be sent to the owner when the NSN, quantity, ownership code, SCC, or serial number/UII is affected.  Except as noted for receipt processing, DLMS transactions will always include the serial number.

		C30.8.2.1.  Requisitioning.  Requisitioning will be in accordance with the procedures contained in Chapter 4.  There is no documented requirement for requisitioning of items by serial number/UII.  Therefore, serial number/UII procedures are not applicable to the requisition, requisition modification, MRO, redistribution order, or disposal release order.  With the exception of the processes documented in paragraph C30.5.1.9. supporting the intra-Air Force use in the NWRM PIC Fusion Module UIT Registry, the MRO and supply status transactions will not include serial number/UII. 

		C30.8.2.2.  Due-In and Prepositioned Materiel Receipt (PMR), Activities will follow the procedures in Chapter 12 for establishing due-in records and processing PMRs.  Do not include serial number/UII in the PMR. 

		C30.8.2.3.  Shipping Activity Processes 

			C30.8.2.3.1.  Advance Shipment Notice (From Procurement Source).  When the procuring DoD Component orders UII items from a vendor, the procuring DoD Component must ensure that the applicable clause requiring the vendor to provide IUID information in accordance with Defense Federal Acquisition Regulations Supplement (DFARS), “Item Unique Identification” clause is included in the contract.[footnoteRef:13]  The contractor must submit IUID information to the ***PIEE***e-Business Suite in accordance with the ***Wide Area Workflow (WAWF)***Implementation Guides for the 856, Ship Notice/Manifest; 857 Shipment and Billing Notice; direct online input; or another comparable information exchange method supported by ***PIEE***.  ***WAWF*** will disseminate the vendor shipment information to the procuring activity to satisfy the shipment performance notice requirement for the vendor to provide notification of shipment to the procuring activity using DLMS 856, Advance Shipment Notice (ASN), including UII(s) and serial numbers, or comparable 856 transaction.  DLMS-compliant receiving activities must coordinate with ***WAWF*** for dissemination of the vendor shipment information to the receiving system using the DLMS 856 ASN, including UII(s) and serial numbers. [13:  See www.acq.osd.mil/dpap/pdi/uid for specific UID DFARS clause information to include in the contract.] 

			C30.8.2.3.2.  Shipment Status***/Shipment Status Materiel Returns***

				C30.8.2.3.2.1.  Chapter 5 contains procedures to prepare and report the shipment status.  ***Chapter 11 contains procedures to prepare and report the shipment status/materiel returns.***  The shipping activity will report shipment status/***materiel return*** with the serial numbers/UIIs selected for shipment, to the receiving DoD Component activity.  ***Shipping documentation may be available for validating serialization data; however, it does not substitute or supersede the requirement for the shipping activity to provide the shipment status transaction at time of shipment.  For inter-Component shipments, a serially managed item received without a corresponding shipment status will result in the materiel to be suspended.  Compliance with this requirement will ensure the receiving activity can establish a due-in, in advance and confirm the serialization data at time of receipt.  The receiving activity will prepare a due-in using the information available from the shipment status and/or the PMR transactions.  The document number is the data element that connects the shipment status transaction and the incoming shipment.  When the serialization data does not match or is missing, a systemic trigger is necessary to alert the user performing the receipt that a SDR is required.  The receiving activity will then follow the SDR process and suspend the materiel until resolution.***

***C30.8.2.3.2.2.  Pending DLMS implementation, Components under a legacy environment will provide the Document Identifier Code AS_ (Shipment Status) and will communicate the serial numbers via other means to ensure the necessary information is available at time of receipt.  Failing to provide serialization data will result in the materiel to be suspended.***

				C30.8.2.3.2.2.***3***.  DLA Disposition Services Shipment Status.  ***The requirement to provide a shipment status, documented in paragraph C30.8.2.3.2. applies to materiel shipped or received by DLA Disposition Services.***

***C30.8.2.3.2.2.4.  Reporting Materiel Ownership via Shipment Status/Materiel Return.  DoD Components will communicate the future owner of the materiel shipped when it is other than the receiving activity.  The owner data element is also required for: (1) inter component shipments for the purpose of maintenance or loans; (2) shipment to a DLA storage activity requiring serial number tracking.  The intent is to communicate the future owner, when known, for all commodities to include serially managed items and not to eliminate the requirement to provide the PMR.  Inventory control points (ICP)s are still required to provide a PMR in advance for all shipments.  The shipment status and the PMR transactions are not mutually exclusive—when both transactions are present, the receiving activity will use the PMR to determine the materiel owner and the shipment status/materiel return to confirm the serialization data.***

			C30.8.2.3.3.  Storage Activity Shipments

				C30.8.2.3.3.1 Materiel Release Confirmations.  Chapter 4 contains the procedures to prepare and report the materiel release confirmation.  The storage activities will confirm materiel release to the owner and report shipped serial numbers/UIIs.  Must use the 4030 version of the materiel release confirmation.  

				C30.8.2.3.3.2.  The AIS supporting the owner will use the materiel release confirmation to record which serial numbers/UIIs have been shipped and decrement those serial numbers/UIIs from its record as no longer available and in storage at that location.

		C30.8.2.4.  Receiving Storage Activity.  Receiving storage activities will maintain records of materiel received in its custodial system of record by NSN, owner, SCC, serial number/UII and its location.

			C30.8.2.4.1.  Acceptance Report (Procurement).  When acceptance at origin is applicable, the shipment status or comparable transactions, forwarded to the procuring and receiving activity, will contain accepted IUID information.  When acceptance at destination is applicable, the receiving system must report acceptance using the acceptance report, or use direct input to iRAPT.  The IUID information will be provided in the acceptance report only when partial acceptance occurs, and will include those items which were accepted.  Responsibility for Government acceptance may also be contractually assigned to an alternative organization which may use the acceptance report or direct input to iRAPT for acceptance reporting.  iRAPT will extract the IUID information for all Government accepted IUID items and use to establish the birth record in the IUID registry.  Additional information and guidance on the IUID registry can be found on the UID Website http://www.acq.osd.mil/dpap/pdi/uid.

			C30.8.2.4.2.  Receipt.  Chapter 13 contains procedures to prepare and report receipts.  Receiving activities will ***perform the***receipts  ***process by serial number/UII and transmit******the******materiel receipt acknowledgement (MRA) to*** report the ***serialization data*** that were actually ***receipted to the shipping activity***.  ***The receiving activity will use the information in the shipment notice and/or the PMR to establish a due-in in advance to the receipt.******Shipping documentation may be available for validating serialization data; however, it does not substitute or supersedes the requirement for the shipping activity to provide the shipment status transaction in advance.  A serially managed item received without a corresponding shipment status will result in the materiel to be suspended.******The receiving activity will validate the serialization data during the receipt process and follow the SDR process for missing serial number(s) or mismatches on serial number/UII.*** A missing serial number ***on the physical item(s)***at receipt will stop the item in the supply chain, and must follow the discrepancy reporting procedures below.  ***Storage activities will not suspend or report a discrepancy at receipt solely due to missing UII.***

***C30.8.2.4.2.1.  When the storage activity receives the physical shipment without a matching shipment status (due-in) transaction, the receiving activity will treat it as a potential misdirected shipment.  The receiving activity will receipt the shipment in a suspended condition and follow the SDR process.***

 				C30.8.2.4.2.***2***.  Receiving storage activities will maintain locator records within their supporting AIS of the location where each serial number/UII is stored at that activity.

				C30.8.2.4.2.***3***.  The storage activity will send the receipt transaction to the owner and include the serial numbers/UIIs.  The owner will record the serial numbers/UIIs on the owner record.

***C30.8.2.4.3.  Materiel Receipt Acknowledgement (MRA).  DLMS Volume 2, Chapter 10, Materiel Receipt Acknowledgement contains procedures to prepare and report MRAs.  In addition, receiving activities will use the MRA to report the receipt of a serially managed item by serial number/UII to the shipping activity.  This will ensure the materiel receipted matches the materiel shipped.  The receiving activity will match the shipment status/materiel return with the MRA/TRA to close the due-in status.  A successful match of the DLMS 856S Shipment Status, 856R Shipment Status Materiel Returns, and the MRA/TRA closes the in-transit balance and ensures the materiel shipped matches the materiel received.  The receiving activity will submit the SDR for discrepancies between the shipment status/materiel return and the MRA/TRA.***

***C30.8.2.4.3.1.  Disposition Services uses the TRA in lieu of the MRA.***

***C30.8.2.4.3.2.  Shipping activities will use the MRA follow-up process for outstanding shipments awaiting receipt acknowledgement as stated in DLMS Volume 2, Chapter 10.  The shipping activities may use the WEB Visual Logistics Information Processing System (WEBVLIPS) to research for missing MRAs before submitting a follow-up.***

***C30.8.2.4.3.3.  After 30 days, certain serially managed items, such as SA/LWs, without a matching receipt acknowledgement or offline confirmation of receipt will require an investigation as potential lost or stolen asset(s) in accordance with section C30.13.***

		C30.8.2.5.  Supply Discrepancy Reporting (SDR) Processes

			C30.8.2.5.1.  Serially managed items requiring owner visibility at the storage activity, that are received without a serial number will not only require an SDR, but will stop the item in the supply chain until a serial number is identified and the materiel is marked.  If the storage activity cannot determine the serial number using the associated shipment notice and marks/labels on the item or packaging, ***the storage activity*** will receipt the materiel without a serial number in a suspended condition and submit the SDR under Chapter 17 SDR procedures.  The materiel owner is responsible for determining the appropriate serial number and providing disposition for marking the item.  Upon positive resolution of the missing or mismatched serial number/UII scenario, separate dual inventory adjustment transactions are required to update the serial number/UII and update the SCC of the suspended item to the appropriate SCC.

			C30.8.2.5.2.  SDRs reporting discrepant receipt will contain the serial numbers/UIIs when reporting missing or mismatched serial number/UII data (including shortage, overage, mismatch with no quantity discrepancy, condition other than expected, and wrong item receipt) as well as when the materiel condition is misrepresented or otherwise deviates from the original condition shipped.  WebSDR will ensure that the owner/manager has visibility of SDRs sent to the shipper.  The receiving activity will submit an SDR in accordance with Chapter 17 procedures showing the appropriate discrepancy code, inclusive of the IUID discrepancy code when reporting missing or mismatched IUID data. 

			C30.8.2.5.3.  SDRs reporting non-compliant serial number will be reported using Discrepancy Code U14 (Serial number convention invalid).  This code is distinguished from other similar U-series discrepancy codes in that this code specifically informs the owner that a serially managed item was received with an invalid serial number convention.  The receiving activity must annotate the non-compliant serial number in the SDR comments field since the DLMS 842A/W SDR transaction will not allow for an invalid serial number convention to be transmitted in the transaction.

			C30.8.2.5.4.  Reporting and action activities must ensure SDRs follow the time standard requirements for submission and response in accordance with Chapter 17.  Chapter 17, Table C17.T1 provides a decision matrix identifying when an SDR is required for UIT program items, based on missing or mismatched IUID data during receipt processing.

		C30.8.2.6.  Physical Inventory Control Processes.  The procedures for processing and reporting transactions to maintain physical inventory control in Chapter 6 apply with the following additions:

			C30.8.2.6.1.  To increase auditability of physical inventory requests, serially managed items will include a unique document number.  The document number will help relate a physical inventory request with it appropriate response.  The owner will provide a document number in the Physical Inventory Request.  The storage activity will perform the necessary physical research as described in Chapter 6 Physical Inventory Control.  The physical inventory response will carry the same document number provided by the owner.  These procedures are required for UIT programs and recommended for all other commodities.

			C30.8.2.6.2.  The response to a transaction history request transaction (No History Available), and end of day transaction count transaction will not contain UIIs or serial numbers.  However, when the owner initiates a physical inventory request to assist in resolving discrepancies, where the only difference between the owner records and the storage activity records is on serial number and/or UII, the request will contain Type of Physical Inventory Code B.  Owners will initiate a physical inventory due to mismatched serial numbers or UIIs when the owner identifies a mismatched condition on serial number and/or UII between its records and transactions received.

			C30.8.2.6.3.  Owner/manager processing a materiel release confirmation from a storage activity where the owner does not have a matching record of the serial number and/or UII or the owner/manager records have that serial number and/or UII located at other than the storage activity reporting the release/issue of the item.  Either of these conditions may necessitate a complete inventory be taken at all storage locations for all owners and supply condition codes.

			C30.8.2.6.4.  Owner/manager processing receipts, issues, or inventory adjustments from storage activities where there is a mismatch on serial number/UII between the owner records and storage activity transactions reporting which serial number and/or UII may at a minimum necessitate an inventory and research to resolve the discrepancy.

			C30.8.2.6.5.  Inventory Adjustments.  The inventory adjustment function encompasses increases, decreases, or dual adjustments.  The C6.4 procedures for processing and reporting Inventory Adjustments (Physical Inventory) are applicable with the following additions:

				C30.8.2.6.5.1.  Inventory adjustment (gain, loss, or dual) transactions will include the serial number/UII when adding, removing, or correcting a serial number/UII.

				C30.8.2.6.5.2.  When a discrepancy exists solely on mismatched serial number and/or UII, the storage activity will transmit a DLMS 947I Inventory Adjustment, Inventory Transaction Type Code DU (Inventory Adjustment Dual), Quantity or Status Adjustment Reason Code AQ (Inventory Adjustment (UII and/or serial number mismatch)) to correct the serial number/UII in question.  The storage activity will collaborate with the materiel owner(s) to research inventory adjustments due to serial number/UII discrepancies resulting in a mismatch (Quantity or Status Adjustment Reason Code AQ) in accordance chapter 6.  When the item was previously suspended, two inventory adjustment transactions are required to correct the serial number/UII, and to update the SCC.

				C30.8.2.6.5.3.  Items where a discrepancy exists solely on missing serial number/UII requires a dual inventory adjustment transaction.  The storage activity will transmit a DLMS 947I Inventory Adjustment, Inventory Transaction Type Code DU (Inventory Adjustment Dual), Quantity or Status Adjustment Reason Code AM (Missing Unique Item Identifier (UII)/Serial Number) to add the serial number/UII in question to the existing records.  The storage activity may add multiple missing serial number/UII using a single transaction.  When the item was previously suspended, a dual inventory adjustment transaction will be required to cite the impacted serial number(s)/UII(s) to update the suspended item(s) from the suspended SCC to the appropriate SCC.

				C30.8.2.6.5.4.  In response to a Physical Inventory Request, the storage activity will transmit to the owner a DLMS 947I Inventory Adjustment with zero quantity, Quantity or Status Adjustment Reason Code AA (Physical Count) by line item indicating the completion of the inventory.  Inventory adjustment transactions with Quantity or Status Adjustment Reason Code AA and zero quantity must include all serial number/UII(s) associated to the NSN, Condition Code, and Owner from the initial request.  The storage activity will send all gain, loss, or dual adjustment transactions prior to sending the final inventory adjustment transaction (Reason Code AA, zero quantity) containing all serial numbers/UIIs.  The owner will process all inventory adjustments prior to processing the final inventory adjustment.

				C30.8.2.6.5.5.  Owner/managers processing location reconciliation history transactions resulting from End-of Day processing or an owner initiated location reconciliation request where there is a mismatch on serial number/UII between the owner records and the transactions received from the storage activity.  The history transactions will perpetuate the serial numbers/UIIs included in the original transactions.

***C30.8.2.6.5.6.  After 30 days (90 days for OCONUS) without a positive confirmation of receipt, certain serially managed assets such as SA/LW(s) requires an investigation for potential lost or stolen assets.  The DoD Component will follow the instructions documented in section C30.13. for reporting lost or stolen SA/LW.  The shipping activity will also perform the necessary inventory adjustments to account for the loss/gain of materiel pending an investigation and report to the corresponding APSR as necessary.***

***C30.8.2.6.5.6.1.  The shipping activity will initiate the investigation and perform an inventory adjustment using Quantity or Status Reason Code WS, Suspected Lost or Stolen, to record the loss of the missing asset pending an investigation.***

***C30.8.2.6.5.6.2.  When the materiel is found, the shipping activity will perform an inventory adjustment using Quantity or Status Reason Code WR, Found/Recovered, to report the gain of the asset(s) resulting from the investigation.***

		C30.8.2.7.  Location Survey

			C30.8.2.7.1.  Chapter 6 contains the procedures for location surveys.  Location survey requires a physical verification, other than actual count, between assets and recorded location data to ensure that all assets have their locations accurately recorded. 

			C30.8.2.7.2.  Serially managed items requiring owner visibility may be in individual storage locations within the storage activity.  The storage activity may, for items of this nature, include the serial number/UII verification as part of the location survey.  When the storage activity identifies a discrepancy during the location survey program (Type I or Type II error (see subparagraphs C6.8.1.2.1. and C6.8.1.2.2.)), the storage activity will conduct prompt research and assess the need for a special inventory Physical Inventory Request Transaction with Type of Physical Inventory/Transaction History Code K).  

		C30.8.2.8.  End-of-Day Reconciliation.  Storage activities and materiel owners will perform End-of-Day (EOD) reconciliation in accordance with Chapter 6 C6.2.6.  End of the Day Processing.  In addition storage activities and owners will reconcile all associated serial numbers/UII to ensure proper accountability of serially-managed items.  For mismatches between system records, the owner, in collaboration with the storage activity, will take the necessary steps to ensure proper research and resolution.  It is the responsibility of the owner to submit any necessary updates as applicable to the IUID Registry.

C30.9.  RETAIL SUPPLY AND TRANSPORTATION INTERCHANGE.  (See Volume 3, Chapter 2).  The transportation office will perpetuate the serial numbers/UIIs (when available with the associated transportation control number (TCN) in the materiel release confirmation (Distribution Code 111).  This data content will be used by the supply activity to perpetuate this information to the shipment status.

C30.10.  MATERIEL RETURNS, REDISTRIBUTION OF ASSETS, DIRECTED DISCREPANT/DEFICIENT MATERIEL RETURNS, AND RETROGRADE RETURNS

	C30.10.1.  Materiel return, redistribution of assets, directed discrepant/deficient materiel returns, and retrograde procedures are contained in Chapter 11.  The following paragraphs identify the additional requirements for total visibility items. 

	C30.10.2.  Activities shipping returns of any kind or responding to redistribution orders will include the serial number/UII in the shipment status materiel return transaction.

	C30.10.3.  Storage activities receiving returns or redistributed items will include the serial numbers/UIIs in the receipt transaction.  Missing serial number(s) and mismatches on serial number/UII will be considered discrepancies.  Refer to the SDR processing section in this chapter. 

C30.11.  REINTRODUCTION OF UNIQUE ITEM IDENTIFIER ITEM PREVIOUSLY SHIPPED OUTSIDE THE CONTROL OF THE DEPARTMENT OF DEFENSE.  When an item previously shipped outside DoD control is reintroduced to DoD control, the receiving activity will report the receipt, including serial number/UII, to the owner.  If the UII is available****on the receipt transaction, the owner will update the IUID registry using IUID registry procedures.

C30.12.  DOD STOCK READINESS PROGRAM.  

	C30.12.1.  Under the Stock Readiness program, the Department of Defense requires uniform care of supplies, including the inspection and reporting of materiel condition and serviceability, and the scheduling, controlling, and reporting of packaging and other cost reimbursable actions supporting care of supplies in storage (COSIS).  For serially managed materiel the storage activity will report storage quality issues requiring COSIS work to the materiel owner via the storage quality control report (SQCR), including the serial numbers/UIIs, for approval in accordance with DoD Component "Stock Readiness" Policy.

	C30.12.2.  Missing serial number.  Serially managed items requiring owner visibility that are located in storage without a serial number will stop the equipment in the supply chain until a serial number is identified and the materiel is marked.  If the remarking/relabeling exceeds the dollar threshold for pre-authorized corrective action or the storage activity cannot identify the serial number using inventory records and other available information, the storage activity will suspend the item in SCC J and prepare an SQCR.  Cite the applicable discrepancy code and provide clarifying remarks with descriptive information for the item.  The materiel owner is responsible for determining the appropriate serial number and providing disposition for marking the item 

***C30.12.3.  Duplicate human readable serial number.  A human readable serial number is a combination of alpha-numeric characters, forward slashes and dashes that in combination with the item NSN and manufacturer CAGE code, helps uniquely identify a serially managed item.  However, a human serial number alone is only unique to the manufacturer and not to the DoD.  A duplicate human serial number refers to two or more items where the NSN, serial number, UII (when available), and manufacturer CAGE code are the same.  Therefore, two identical items with the same human readable serial number may not necessarily be a duplicate.  DoD Components will report discrepancies at time of receipt using the SDR; storage quality control report (SQCR) for materiel in storage.***

***C30.12.3.1.  When a potential duplicate human readable serial number exists, the materiel owner is responsible for resolving any discrepancies pertaining the human readable serial number and/or missing data plates as well as providing the corresponding information to the storage activity for proper marking.  The DoD Component will suspend any movement of the materiel pending resolution.  Upon confirmation of the duplicate human serial number, the materiel owner may issue a modified human serial number using selected alpha suffix to maintain a historical cross-reference.  The Component will permanently inscribe the modified human serial number into the item as required.  Temporary tags are authorized for Items destined for disposal or maintenance.***

***C30.13.5.2.  Under new procurement, a duplicate human readable serial number will result in contractor non-compliance.  DoD Components are responsible for reporting the discrepancy via SDR and coordinate with the manufacturer for resolution of the duplicate human readable serial number(s).***

***C30.13.  Additional Instructions under the DoD Small Arms/Light Weapons (SA/LW) Program***

***C30.13.1.  Law Enforcement Inquiries.  Within 72 hours, the Army is responsible for providing the initial response to law enforcement.  The initial response will include the identification of the last known owner or custodial activity (to include contact information) for a given serialized weapon identified as DoD property.  The Army may also be contacted by other authorized entities inquiring about a particular small arm/light weapon.  In response, the Army will provide the last known owner to the inquirer. The last known owner will collaborate with law enforcement and other authorized entities to provide any additional information requested in a timely matter.  In compliance with NARA, the Army must maintain records of all inquiries.***

***C30.13.2.  Non-Compliant characters in the serial number***

***C30.13.2.1.  All serialized items to include SA/LW must follow DoD guidance for serial numbers.  DoD Components will ensure that any new procurement contracts/acquisitions follow the DoD guidance on human readable serial numbers.  DoD Component will need to remark legacy non-compliant serial numbers prior to any inter-component shipment.  DoD Components are not required to remark SA/LWs prior to turn-in materiel to DLA Disposition Service Field Office Anniston, Alabama for disposal.  The tracking of serially managed SA/LWs ends upon positive receipt of the turn-in.  When a Component acquires a SA/LW through the DLA Disposition Services Reutilization Program, the Component will resume the serialization tracking of the SA/LW and will ensure the serial number follows current DoD serial number guidance.***

***C30.13.2.2.  The DoD Components will assign a new serial number to foreign weapons containing unidentifiable characters in the original serial number (non-English alpha characters/non-Arabic numerals).  All new serial numbers must follow DoD guidance as stated in section C30.4.4.  Upon assignment, the DoD Component will permanently inscribe the newly assigned serial number on the weapon, except for those with historical artifact value or weapons turn-in to DLA Disposition Services for disposal.  When permanent inscription is not possible, the DoD Component will securely tag the SA/LW.  DoD Components will maintain records of the original serial number for a historical cross-reference of the weapon.***

***C30.13.3.  Assignment of Management Control Numbers (MCN)***

***C30.13.3.1.  The MCN is a control number assigned by the Army to enable the movement of SA/LW without a valid NSN.  The intent of the MCN is to be temporary, pending the assignment of a cataloged NSN.  Once a SA/LW qualifies for a cataloged NSN, DoD Components will transition from the MCN to NSN within 90 days.  The MCN will remain part of the SA/LW identification pending assignment of a valid NSN.  DoD Components will not use the MCN to circumvent or avoid the cataloging process.  All DoD Components are responsible for catalog qualifying items as described in DoDM 4100.39, Federal Logistics Information System, and Stock Numbering Criteria.  MCNs for heritage assets, as defined in DoDI 5000.64 “Accountability and Management of DoD Equipment and Other Accountable Property”, are exempt from the 90 days to transition to NSN.***

***C30.13.3.2.  DoD Components will request a new MCN from the Army when a cataloged NSN is not available.  The Army is the authoritative source for MCNs.  To ensure no duplicate MCNs, the Components must provide a detail description of the weapon to include, but not limited to, make, model, caliber, manufacturer, manufacturer commercial and government entity (CAGE) code, and/or nomenclature, unit price, and supporting documentation.  Examples of acceptable supporting documentation includes procurement documents, bills of sale, photograph of the weapon’s data plate, and technical drawings.  Army publication DA 708-1 provides additional guidance pertaining to the assignment of MCNs.***

***C30.13.4.  Reporting Potential Lost or Stolen SA/LW.  Each Component must establish proper procedures to ensure reporting of lost, stolen, unaccounted, and/or recovered SA/LW under the provisions of DoDM 5100.76, “Physical Security of Sensitive Conventional Arms, Ammunition, and Explosives”.  DoD Components are responsible for reporting lost, damaged, or destroyed SA/LW in accordance with DoD 7000.14-R Volume 12, Chapter 17 Financial Liability for Government Property Lost, Damaged, Destroyed, Or Stolen.***

***PROPERTY LOST, DAMAGED, DESTROYED, OR STOLEN.  The DoD Component will ensure the capture of all necessary details and the resolution of the investigation as evidential matter.***

***C30.13.5.  Duplicate Serialization Data.  A human readable serial number is a combination of alpha-numeric characters, forward slashes, and dashes that in combination with other data elements, helps uniquely identify a serially managed item.  However, a human serial number alone is only unique to the manufacturer and not to the DoD.  A duplicate serial number refers to two or more items where the NSN, serial number, UII (when available), and manufacturer CAGE code are the same.  Two identical items with the same serial number may not necessarily be a duplicate.  DoD Components will report discrepancies at time of receipt using the SDR; storage quality control report (SQCR) for materiel in storage.***

***C30.13.5.1.  When a potential duplicate serial number exists, the DoD Component will contact the Army for assistance in the validation of the duplicate.  The DoD Component will suspend any movement of the SA/LW pending resolution.  Upon confirmation of the duplicate serial number, the Army will direct the DoD Component to issue a modified serial number using selected alpha suffix to maintain a historical cross-reference.  The Component will permanently inscribe the modified serial number into the SA/LW.  For a SA/LW that cannot be permanently inscribed due to its historical value, the Component will securely tag the SA/LW with the modified serial number.***

***C30.13.5.2.  Under new procurement, a duplicate human readable serial number will result in contractor non-compliance.  DoD Components are responsible for coordinating with the manufacturer for resolution of the duplicate serial number(s).  SDR procedures apply for duplicate human readable serial numbers in a new procurement shipment.***

***C30.13.5.3.  A legacy SA/LW with a duplicate serial number may be suffix when the CAGE code is unknown.***

***C30.13.6.  Non-Standard Acquisitions.  When DoD Components purchase/acquire SA/LWs from sources other than new procurement, it is the responsibility of the DoD Component to account for the SA/LW(s) in accordance to DLM 4000.25, Volume 2, Chapter 13, Materiel Receipt.  Examples of non-standard acquisitions includes but it is not limited to offline purchases, commercial acquisition outside of the DoD acquisition process, and turn-ins for disposal by private entities (i.e., Morale, Welfare, and Recreation, or any procurement outside of the DoD supply chain).  SA/LW(s) acquired through non-standard acquisition methods will require serialization and permanent marking.***

***C30.13.7.  Nonappropriated Funds Purchases.  SA/LWs purchased with non-appropriated fund purchases or privately owned SA/LWs are exempt from serialization program requirements as these are under the control of civil authorities under the Gun Control Act of 1968.  However, DoD Components will account for SA/LWs purchased with non-appropriated funds and/or privately owned once the property is turned over to the DoD Component for disposal.  In the absence of NSN and/or serial number, the DoD Component will assign a new serial number and follow the procedures to request a MCN from the Army.***

***C30.13.8.  Shipments Outside the Control of the Department of Defense.***

***C30.13.8.1.  DoD Components shipping weapons to entities outside of the DoD will retain all evidential matter pertaining to the shipment and have it readily accessible to respond to inquiries from law enforcement when requested.  The shipping activity will need to obtain acknowledgement of receipt (electronic or offline) prior to closing in-transit status.***

***C30.13.8.2.  When shipping SA/LWs to FMS and Grant Aid customers, DoD Components will release property accountability at time of shipment.  The last DoD Component is responsible for retaining all evidential matter of the shipment and must be available to respond to inquiries pertaining the shipment.  If the weapon is returned to the DoD supply chain, the Component will re-establish property accountability via the receipt process and update their respective APSR.***

***C30.13.9.  Loan of SA/LW(s).  Loan of SA/LW may occur within the DoD or under the Law Enforcement Support Program.  For the purpose of loans, the loaner is the entity or organization that owns the SA/LW while the loanee is the organization receiving the loan.  The accountability of the SA/LW(s) remains with the DoD owning Component (Loaner) while the custodial accountability transfers to the authorized DoD organization or Law Enforcement Agency (loanee) until the SA/LW(s) returns to the loaner.***

***C30.13.9.1.  DoDM 4140.01 Volume 11 and DoDM 4160.21. provides additional instructions regarding the accountability of assets while in loan.***

***C30.13.9.2.  Loans of SA/LW are not authorized after property is officially declared excess and transferred to DLA Disposition Services as stated in DoD 4160.21.***

***C30.13.10.  Shipment of Partial Weapons to DLA Disposition Services Small Arms Anniston, Alabama.  DoD Components will follow procedures for the shipment of partial weapons as described under DLM 4000.25 Volume 2, Chapter 16 Disposition Services.***

***C30.13.11.  New/re-engineered weapons.  The JSALWCG chairperson will determine the reportability of new/re-engineered weapons when the SA/LW classification is unknown. The chairperson will then notify the results to the DoD Components.  If no determination can be reached, the chairperson will reach out to the JSA/LWCG for further consideration.***

***C30.13.12.  JSA/LWCG.  JSA/LWCG responsibilities are as set forth in DoDM 4140.01, “DoD Supply Chain Materiel Management Regulation”.***

9

C30-10	CHAPTER 30