DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA 2206()..6221

Similar documents
DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA

DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA

DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA

DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA

DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA

2. FUNCTIONAL AREA: Primary: Supply/MILSTRIP/DLMS Receipt/DLMS MRA

DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA

1. ORIGINATOR: a. Service/Agency: Defense Logistics Management Standards Office (DLMSO). b. Sponsors:

a. DLMSO memorandum dated January 22, 2007, subject: ADC 225, DOD WebSDR Requirement for Information Copy

DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA

DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA

Approved DLMS Change 71B Administrative Correction for DLMS Mapping for MRO Exception Data Transaction

ADC 329 Use of Borrowed and Migration Codes in DLMS Supplements

ADC 452 Implementation of DOD WebSDR Automated SDR Rejection Capability

2. This transaction set is not used to reject a transmission due to ASC X12 syntax errors. Use a 997 transaction set for that purpose.

Approved DLMS Change 71 DLMS Mapping for DLA Materiel Release Order (MRO) Exception Data Transaction, Document Identifier (DI) Code CGU

DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA

ADC 256 WebSDR/Transaction Edits: Forwarding and Follow-up Timeframes

DLMS Implementation Convention (IC) 888W Weapons System Data Change ADC 111, 167, 167A and 1043C DLM

ATTACHMENT TO REQUEST FOR IMPLEMENTATION DATE FOR MILSTRAP AMCL 13 PARTIAL REVERSAL OF SELECT MILSTRAP TRANSACTIONS

ADC 298 DoDAAD Enhancements

ATTACHMENT TO ADC 348 Revise DLMS Supplement 527R and 527D in Support of Mapping Product Requirements (Supply)

ADC 1007 New DLMS 842P, PQDR Data Exchange and Enhanced Exhibit Tracking via Standard Logistics Transactions

a. CJSCI D, The Defense Message System and Associated Legacy Message Processing Systems.

ADC 406. DOD Activity Address Directory (DoDAAD) Removal of Unused Fields

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

888 Item Maintenance Functional Group=QG

ATTACHMENT TO ADC 212

ADC 385. DOD Activity Address Directory (DoDAAD) Enhanced Inquiry and Download for Multiple DoDAACs.

Nonconformance Report

ATTACHMENT TO ADC 1118 Project Code Management System (PCMS) Procedures

FedMall Frequently Asked Questions

FedMall Frequently Asked Questions

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

SUPPORT POINT Deficiency Report Program Manager (DRPM)

869 Order Status Inquiry

FedMall Frequently Asked Questions

Product Data Reporting and Evaluation Program (PDREP)

DLA RTD Web Guide 2017 V2

EDI Guide - Appendix W 527R - Receipt

Inventory Inquiry/Advice

WAWF Government Furnished Property (GFP) Module: GFP Attachment Training

EDI Guide - Appendix S 861 Receiving Advice/Acceptance Certificate (Inbound from DSS)

DCMA Quality Assurance Representative (QAR) Product Quality Deficiency Report (PQDR) Investigations in Product Data Reporting and Evaluation Program

Product Data Reporting and Evaluation Program (PDREP) Product Quality Deficiency Report (PQDR) Cloning PQDR

3. A single transaction set may contain a combination of requisitions for standard and nonstandard material.

ADC 311 SDR Attachment Interface

Navy Construction / Facilities Management Invoice

Screening Point Army Master Screener Product Quality Deficiency Report (PQDR) Processing In Product Data Reporting and Evaluation Program (PDREP)

Product Data Reporting and Evaluation Program (PDREP) Automated Information System (AIS) Prime Contractor Module

FedMall Frequently Asked Questions

Wide Area Workflow. IGT Performance Evidence Receiving Report

EDI Guide - Appendix J 821 Financial Information Reporting - (Inbound to irapt from GEX/SABRS/MISC PAY & Extract from irapt to GEX/SABRS/MISC PAY)

Product Data Reporting and Evaluation Program (PDREP) Contract Award and Delivery (CAD) Data Application

EDI Guide - Appendix T 861 Receiving Advice/Acceptance Certificate (From Navy ERP/ILSMIS to irapt)

SPECIAL OPERATIONAL EQUIPMENT Tailored Logistic Support Program Customer Guidelines Document

Invoicing, Receipt, Acceptance and Property Transfer Commercial Item Financing

X Aimee Ivey irapt EDI Technical Manager Signed by: IVEY.AIMEE.B

Why UID? LeAntha Sumpter May 11, 2005

DLMS Implementation Convention (IC) 870L Special Program Requirements (SPR) Status or Notification ADC 287, 333, 400, 436 and 1043C DLM 4000.

DAAS DATA BASE AND DATA INFORMATION SERVICES

CH 5 DoD 41OO.38-M Mailing Address. The Letter of Registration will be addressed to:

FedMall Frequently Asked Questions

Case Study: idworx!... electronic WAWF and UID submittals reduces time and errors.

Planning Schedule with Release Capability

NGMMC RS-TOPS. User Handbook. Version 1.0 Prepared By KYLOC. 1 May 2005

Nonconformance Report

Product Data Reporting and Evaluation Program (PDREP) Automated Information System (AIS) Corrective Action Record (CAR)

FTP Guide - Appendix K Progress Pay Report (PPR)

IUID Registry Access Request Quick Guide

Department of the Navy Data Server and Data Center Waiver Scope Matrix and FAQ

How to Order EMSS Services and Equipment

567 Contract Completion Status

Product Registration. Functional Group= WA

Product Data Reporting and Evaluation Program (PDREP) Product Quality Deficiency Report (PQDR) Originator Processing and PQDR Submission

Login & Registration Quick Start Guide

812 Credit/Debit Adjustment

Requirements Page 2 of 39

Product Data Reporting and Evaluation Program (PDREP) Product Quality Deficiency Report (PQDR) Local Purchase Processing

FTP Guide - Main Document Secure File Transfer Protocol (SFTP) Instruction Guide

Product Data Reporting and Evaluation Program (PDREP) Product Quality Deficiency Report (PQDR) Cloning 1227s

DAASC Integrated Logistics (DIELOG) User s Guide

Pos Id Segment Name Req Max Use Repeat Notes Usage 0100 ST Transaction Set Header M 1 Must use 0200 BGN Beginning Segment M 1 Must use

Product Data Reporting and Evaluation Program (PDREP) Automated Information System (AIS) Supply Discrepancy Report (SDR) Application

DOD Lawyers Roundtable Defense Logistics Agency (DLA Energy)

ADC 360. Procedures and Content Requirements for Catalog Data Support under Navy and Marine Corps BRAC

Miscellaneous Payment

DETAIL SPECIFICATION SHEET

824 Application Advice

ITEM UNIQUE IDENTIFICATION (IUID) SYSTEM. Software User Manual (SUM) Version 5.1.5

Product Data Reporting and Evaluation Program (PDREP) Product Quality Deficiency Report (PQDR) Originator Processing and PQDR Submission User Guide

OFFICE OF THE UNDER SECRETARY OF DEFENSE 3000DEFENSEPENTAGON WASHINGTON, DC

Electronic Bid Sets. presented by Susan Sherrell Seattle District, Corps of Engineers. US Army Corps of Engineers Seattle District

Using Wide Area Workflow for Vendors Student Guide

PDREP-AIS Production Publish 27 January 2018 The following CSRs are included in release Version: E

Product Data Reporting and Evaluation Program (PDREP) Product Quality Deficiency Report (PQDR) Army Action Officer PQDR Processing

CHAPTER 4 ABSTRACTS OF CONTRACT MODIFICATIONS

ENCORE II REQUIREMENTS CHECKLIST AND CERTIFICATIONS

Invoicing Receipt Acceptance Property Transfer. Invoice as 2 in 1

Action taken Code (ATC). A 2-character, alphabetic/numeric code to identifj advice being provided in a Line Item Advice Card (LIAC).

Transcription:

DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA 2206()..6221 IN REPLY REFER TO November 05, 2013 MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS SUBJECT: Approved Addendum to Approved Defense Logistics Management Standards (DLMS) Change 1014A (Staffed as PDC 1014A), Revised Procedures for Inclusion of Government-Furnished Property(GFP)/Contractor-Acquired Property (CAP) Contract Data- Updated Mapping for Concurrent Identification of the Manufacturing Directive Number (MDN) and the Contract Line Item Number (CLIN) (Supply and Contract Administration) The attached change to DLM 4000.25, Defense Logistics Management System (DLMS) and DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP) is approved for phased/staggered implementation beginning January 1, 2014. The DLA Supply PRC members are required to actively monitor for implementation of this ADC and provide implementation dates when they become available. The updated DLMS Implementation Conventions will be posted to the DLA Logistics Management Standards Office Web at www.dla.mil/j-6/dlmso/elibrarv/transformats/140 997.asp within 10 days from the above date. Addressees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP Administrator, 703-767-0676 or DSN 427-0676, email: ellen.hilert@dla.mil, or Ms. Heidi Daverede, DOD MILSTRIP Alternate, 703-767-5111 ; DSN 427-5111, e-mail: heidi.daverede@dla.mil. Others must contact their Component designated representative. Attachment As stated cc: ODASD(SCI) ODASD DP AP (PDI) ds~~ DONALD C. PIPP Director DLA Logistics Management Standards Office Federal Recycling Program G Printed on Recycled Paper

Attachment to ADC 1014A Revised Procedures for Inclusion of Government-Furnished Property (GFP)/Contractor-Acquired Property (CAP) Contract Data in DLMS Transactions Updated Mapping for Concurrent Identification of the Manufacturing Directive Number (MDN) and the Contract Line Item Number (CLIN) 1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: a. Requestor: Defense Logistics Agency b. Sponsored by: DLA Logistics Management Standards Office, Ms. Ellen Hilert, Supply PRC Co-Chair, 703-767-0676; DSN 427-0676; or, e-mail: Ellen.Hilert@dla.mil 2. FUNCTIONAL AREA: a. Primary/Secondary Functional Area: Supply/Contract Administration b. Primary/Secondary Functional Process: GFP Accountability 3. REFERENCE: a. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP) b. DLM 4000.25, Defense Logistics Management System (DLMS) c. Approved DLMS Change (ADC) 1014, Revised Procedures for Inclusion of Contract Data in Transactions Associated with Government Furnished Property (GFP) and Management Control Activity (MCA) Validation of Contractor Furnished Materiel (CFM) Requisitions, dated August 17, 2012. This change perpetuates the contract number through the requisitioning and MCA validation processing and establishes a mandatory requirement for inclusion of the applicable GFP contract number in relevant requisitions, redistribution/materiel release orders, and shipment status, thereby providing capability to monitor GFP through enterprise visibility/accountability programs. 4. APPROVED CHANGE: a. Overview: This addendum supplements the procedures authorized in ADC 1014 (Reference 3.c.) to further enhance the visibility of Government Furnished Materiel (GFM) and CAP in associated logistics transactions. GFM is that portion of GFP that can be obtained under MILSTRIP procedures; CFM refers to that portion of CAP that can be obtained under MILSTRIP requisitioning procedures. Under ADC 1014, DLMS transactions are able to support the inclusion of the authorizing contract number, call or order number, and either the CLIN or MDN. This addendum provides an additional update to allow for simultaneous identification of the CLIN and the MDN when both are applicable and required by the authorizing Attachment, ADC 1014A Page 1

Service/Agency. In addition, this addendum documents optional validation of the CLIN. All other aspects of ADC 1014 are unchanged. b. Background: (1) Requisitions identifying a contractor as the ship-to location and either free issue or a Government activity as the bill-to party are processed under MILSTRIP/DLMS GFM controls via the MCA. MILSTRIP prescribes the application of GFM controls to Army CFM. Additionally, DLA s Enterprise Business System internally requires GFM controls for DLAprovided CFM. (2) Pending implementation of ADC 1014, the following information is included in GFM requisitions: MCA monitoring the contract DoDAAC of the contractor requesting and/or receiving the materiel Indication when issue is without reimbursement (including applicable signal code) Identification of the MDN or contract number Identification of the call or order number, when required by the Component contract. (3) Under ADC 1014, MILSTRIP procedures will no longer authorize the use of the MDN instead of the authorizing contract number in the GFM/CFM requisition and subsequent MCA validation. During staffing of the Proposed DLMS Change 1014, no Military Services identified a requirement for use of the MDN; however, it continues to be integrated within DLA procedures and is considered a required data element. (4) The MDN is constructed using the MILSTRIP Distribution Code to facilitate transaction routing by DLA Transaction Services. Under DLMS, the MDN is mapped with applicable contract data to the GF (Furnished Goods and Services) Segment in requisitioning and MCA validation transactions. c. Requested Change in Detail: (1) Changes are required to DLMS transactions to enhance the visibility of applicable contract information within specified logistics transactions supporting GFM or CFM by allowing for simultaneous inclusion of the MDN and the CLIN. To accomplish this, this addendum expands the available data fields in the DLMS 511R Requisition, 511M Requisition Modification, 517G GFM Validation, 869C Requisition Cancellation, and 869F Requisition Follow-up transactions. The CLIN and MDN are identified as optional for use when directed by the authorizing Service/Agency. (2) The MCA validation process is updated to include optional validation of the CLIN under DLMS processing (does not apply to legacy MILSTRIP GFM requisition validations). Attachment, ADC 1014A Page 2

(3) The MILSTRIP Supply Status Code DB explanation is updated to clarify its use during validation of contract data inclusive of the call or order number and CLIN. d. Revisions to DLM 4000.25 Manuals: (1) Update DLM 4000.25, DLMS, Volume 2, Chapter 4 as shown in Enclosure 1. (2) Revise DLM 4000.25-1, MILSTRIP Appendix 15, Advice Codes, as shown below. REQUISITION TRANSACTION ADVICE CODES 2U MCA validation process has revealed that no valid contract/call or order number is registered at the MCA or Service/Agency required manufacturing directive number (MDN) or contract line item number (CLIN) is missing or invalid. (3) Revise DLM 4000.25-1, MILSTRIP Appendix16, Status Codes, as shown below. REQUISITION TRANSACTION STATUS CODES CODE EXPLANATION DB (1) Rejected. No valid contract registered at MCA. (2) Rejected. One or more of the following Service/Agency required data elements is missing or invalid: (1) call or order number, (2) manufacturing directive number (MDN), (3) contract line item number (CLIN). (4) Revise DLMS implementation conventions as shown in Enclosure 2. e. Alternatives: (1) The mapping solution provided in this ADC was chosen to minimize impact on existing implementation by opening a separate data field for the CLIN when used in combination with an MDN. This allows both the CLIN and the MDN to retain their existing mapping when not used concurrently. (2) One alternative also considered was providing guidance to map the MDN to the Distribution Code field when the CLIN is identified in the GF Segment of the DLMS transaction. This would have been feasible, but might have proved confusing since the MDN has been separately identified by this name in the GF Segment since the implementation of DLMS. f. Proposed DLMS Change 1014A Staffing Response/Comment Resolution: Originator Response/Comment Disposition 1. DLA Concur without comment. Noted. 2. Army Concur without comment. Noted. Attachment, ADC 1014A Page 3

Originator Response/Comment Disposition 3. Air Force Concur without comment. Noted. 4. Marine Corps Concur as written. Noted. 5. Navy Pending. 6. USTRANSCOM Concur. USTRANSCOM requests a minimum 30 day window from release of final approved ADC to implementation date. This time will be required to implement required changes in USTRANSCOM systems. Noted. Implementation planned for after January 1, 2013. 5. REASON FOR CHANGE: This change is provided to accommodate inclusion of the MDN and the CLIN in the GF Segment when both are applicable and directed by the authorizing Service/Agency. This capability will be useful to DLA, which requires continued availability of the MDN, but is also developing systems changes to support ADC 1014 implementation and foresees a future requirement to carry all pertinent data in support of GFM and MCA validation. 6. ADVANTAGES AND DISADVANTAGES: a. Advantages: Adding the separate mapping for the CLIN and MDN provides flexibility. b. Disadvantages: None identified. 7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Staggered/phased implementation is authorized beginning January 1, 2014. Supply PRC members are required to actively monitor for implementation of ADC 1014 and this addendum, and provide implementation dates when they become available. 8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH IMPLEMENTATION OF THIS CHANGE: Improved management, oversight, and visibility of GFP are expected to generate savings or cost avoidance. However, no specific data is available to quantify any expected savings or cost avoidance. 9. IMPACT: a. New/Revised DLMS Data Elements: There are no new data elements identified. Revisions to the status code and advice code explanations are shown above. Attachment, ADC 1014A Page 4

b. Automated Information Systems: This change will impact DLA EBS and DLA contractor requisitioning systems. DOD EMALL requisitioning formats must be updated to accommodate this change. No Service impact is identified at this time. c. DLA Transaction Services: Mapping updates are required. d. Non-DLA Logistics Management Standards Publications: Update for consistency with DLMS guidance as required. Attachment, ADC 1014A Page 5

Enclosure 1, DLMS Manual Revisions Revisions are identified in red italics and strike thru. Revise DLM 4000.25, Volume 2, Chapter 4 as identified: C4.2.10.5. Management Control Activity Processing of Government Furnished Materiel Validation Requests. MCAs in receipt of a GFM validation request (DLMS 517G, GFM Validation Request) will validate the data contained therein. This validation process must be completed and a DLMS 517G GFM Validation Response transaction created and forwarded to the applicable source of supply within 15 days or receipt of the GFM validation request transaction. A GFM validation response (DLMS 517G) will be transmitted to the applicable source of supply as follows: C4.2.10.5.1. If the requisition has been previously validated, cite Advice Code 2M. C4.2.10.5.2. If the requisition has not been previously validated and the call order number/procurement instrument identification number (PIIN) (or MDN and/or CLIN, if required by the Component in addition to the call order number/piin) is not present, cite Advice Code 2U. DLM 4000.25, Volume 2, Chapter 4, Table C4.T2 as identified: CODE OR DATA ELEMENT Table C4.T2. MCA Validation Process for GFM Transactions VALIDATION OF ENTRY Transaction Type If DLMS 511R, Requisition, Referral, or Passing Order (DICs A01, A02, A04, A05, A0A, A0B, A0D, A0E, A3_, A4_,) DLMS 511M, Requisition Modification (DIC AM_) (for modification to RDD, project code, PD, or advice code), DLMS 869F, Requisition Follow-up (DIC AT_), continue the GFM validation. Stock Number Unit of Issue Quantity Verify item requisitioned against a valid contract to determine authority for issue to the contractor. If blank, incorrect, or not authorized, reject with Status Code DN. Validate the unit of issue in conjunction with the quantity to ensure that the requisitioned quantity does not exceed the authorized quantity. If quantity is excessive, see validation of quantity field. (Note: If a change of unit pack has occurred, appropriate adjustment should be made for authorized quantity.) If ordered item is authorized by contract, verify the quantity. If blank or invalid, reject with Status Code CD. If the requisitioned quantity exceeds the remaining authorized quantity, reject the quantity exceeding the authorized quantity with Status Code DJ. If authorized quantity has been exhausted by previous requisition(s), reject total requisitioned quantity with Status Code DQ. ADC 1014A, Enclosure 1, Page 1

Table C4.T2. MCA Validation Process for GFM Transactions CODE OR DATA ELEMENT Requisitioner Document Number Supplementary Address Signal and Fund Manufacturer s Directive Number Contract Call or Order Number Contract Line Item Number (CLIN) Procurement Instrument Identification Number VALIDATION OF ENTRY If blank or incorrect, discard. If not authorized, reject with Status Code DN. If blank or incorrect, reject with Status Code CD. If contractor DoDAAC, and affected by signal code, and incorrect or not authorized, reject with Status Code DN. If signal and fund codes indicate issues without contractor reimbursement, process as GFM; otherwise, consider as CFM. CFM requisitions, except for Army, are not subject to MCA review. All Army contractor requisitions and associated transactions will be processed under GFM controls. DAAS will respond to requests for MCA review for Army CFM under special processing rules authorized by the Army. If the MDN option is required by the Component and the MDN equates to a valid contract number, validate; otherwise, reject with Status Code DB. If specified by S/A contract, and entry is blank or incorrect, reject with Status Code DB. If specified by S/A contract, and entry is blank or incorrect, reject with Status Code DB. If blank, or contract is not on MCA file, or contract has expired, reject with Status Code DB. (If requisition originated in the legacy MILSTRIP format, then only the last eight positions of the PIIN are mandatory.) ADC 1014A, Enclosure 1, Page 2

Enclosure 2, DLMS Implementation Convention Revisions a. Revise DLMS 511R as follows: Item # Location 511R, Requisition Revision 1. DLMS Introductory Notes Add ADC 1014A to DLMS Introductory notes: - ADC 1014A, Revised Procedures for Inclusion of Contract Data in DLMS Transactions Updated Mapping for Concurrent Identification of the Manufacturing Directive Number (MDN) and the Contract Line Item Number (CLIN) 2. 2/GF01/70 Revise DLMS Note to C7 and Add DLMS Note to W3: 1. Use to associate a Contract Line Item Number (CLIN) with the Contract Number. 2. Use in CAV transactions or as directed by the authorizing Service/Agency. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. Reason Identifies DLMS Changes included in the transaction. Clarifies that the CLIN may be provided at an alternative location when using the GF01 to identify the MDN. W3 Manufacturing Directive Number 1. Use to identify the MDN, in addition to the contract number. 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. 3. 2/GF08/70 Open GF08 and add Code C7 with applicable 1. Use to associate a Contract Line Item Number with the Contract Number when also identifying an MDN (at GF01). 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014A. Supports enhanced functionality to identify the CLIN when also identifying the MDN. 4. 2/GF09/70 Open GF09 for identification of the CLIN. Supports enhanced functionality. ADC 1014A, Enclosure 2, Page 1

b. Revise DLMS 511M as follows: Item # Location 511M, Requisition Modification Revision 1. DLMS Introductory Notes Add ADC 1014A to DLMS Introductory notes: - ADC 1014A, Revised Procedures for Inclusion of GFP/CFM Contract Data in DLMS Transactions Updated Mapping for Concurrent Identification of the Manufacturing Directive Number (MDN) and the Contract Line Item Number (CLIN) 2. 2/GF01/70 Revise DLMS Note to C7 and Add DLMS Note to W3: 1. Use to associate a Contract Line Item Number (CLIN) with the Contract Number. 2. Use in CAV transactions or as directed by the authorizing Service/Agency. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. Reason Identifies DLMS Changes included in the transaction. Clarifies that the CLIN may be provided at an alternative location when using the GF01 to identify the MDN. W3 Manufacturing Directive Number 1. Use to identify the MDN, in addition to the contract number. 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. 3. 2/GF08/70 Open GF08 and add Code C7 with applicable 1. Use to associate a Contract Line Item Number with the Contract Number when also identifying an MDN (at GF01). 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014A. Supports enhanced functionality to identify the CLIN when also identifying the MDN. 4. 2/GF09/70 Open GF09 for identification of the CLIN. Supports enhanced functionality. ADC 1014A, Enclosure 2, Page 2

c. Revise DLMS 517G as follows: Item # Location 517G, Government Furnished Materiel (GFM) Validation Revision 1. DLMS Introductory Notes Add ADC 1014A to DLMS Introductory notes: - ADC 1014A, Revised Procedures for Inclusion of GFP/CFM Contract Data in DLMS Transactions Updated Mapping for Concurrent Identification of the Manufacturing Directive Number (MDN) and the Contract Line Item Number (CLIN) 2. 2/GF01/70 Revise DLMS Note to C7 and Add DLMS Note to W3: 1. Use to associate a Contract Line Item Number (CLIN) with the Contract Number. 2. Use in CAV transactions or as directed by the authorizing Service/Agency. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. Reason Identifies DLMS Changes included in the transaction. Clarifies that the CLIN may be provided at an alternative location when using the GF01 to identify the MDN. W3 Manufacturing Directive Number 1. Use to identify the MDN, in addition to the contract number. 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. 3. 2/GF08/70 Open GF08 and add Code C7 with applicable 1. Use to associate a Contract Line Item Number with the Contract Number when also identifying an MDN (at GF01). 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014A. Supports enhanced functionality to identify the CLIN when also identifying the MDN. 4. 2/GF09/70 Open GF09 for identification of the CLIN. Supports enhanced functionality. ADC 1014A, Enclosure 2, Page 3

d. Revise DLMS 869C as follows: Item # Location 869C Requisition Cancellation Revision 1 DLMS Introductory Notes Add ADC 1014A to DLMS Introductory notes: - ADC 1014A, Revised Procedures for Inclusion of GFP/CFM Contract Data in DLMS Transactions Updated Mapping for Concurrent Identification of the Manufacturing Directive Number (MDN) and the Contract Line Item Number (CLIN) 2. 2/GF01/100 Add Code C7 and associated DLMS notes and add new Note 3 to existing Code W3: 1. Use to associate a Contract Line Item Number (CLIN) with the Contract Number. 2. Use as directed by the authorizing Service/Agency. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. W3 Manufacturing Directive Number 1. Use to identify the MDN, in addition to the contract number. 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. 3. 2/GF08/100 Open GF08 and add Code C7 with applicable 1. Use to associate a Contract Line Item Number with the Contract Number when also identifying an MDN (at GF01). 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014A. Reason Identifies DLMS Changes included in the transaction. Updates data content for consistency across requisition related transactions. Clarifies that the CLIN may be provided at an alternative location when using the GF01 to identify the MDN. Supports enhanced functionality to identify the CLIN when also identifying the MDN. 4. 2/GF09/100 Open GF09 for identification of the CLIN. Supports enhanced functionality. ADC 1014A, Enclosure 2, Page 4

e. Revise DLMS 869F as follows: Item # Location 869F Requisition Follow-up Revision 1. DLMS Introductory Notes Add ADC 1014A to DLMS Introductory notes: - ADC 1014A, Revised Procedures for Inclusion of GFP/CFM Contract Data in DLMS Transactions Updated Mapping for Concurrent Identification of the Manufacturing Directive Number (MDN) and the Contract Line Item Number (CLIN) 2. 2/GF01/100 Revise DLMS Note to C7 and Add DLMS Note to W3: 1. Use to associate a Contract Line Item Number (CLIN) with the Contract Number. 2. Use as directed by the authorizing Service/Agency. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. W3 Manufacturing Directive Number 1. Use to identify the MDN, in addition to the contract number. 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014. 3. When both the CLIN and the MDN are applicable, identify the CLIN in GF09. Refer to ADC 1014A. 3. 2/GF08/100 Open GF08 and add Code C7 with applicable 1. Use to associate a Contract Line Item Number with the Contract Number when also identifying an MDN (at GF01). 2. Use as directed by the authorizing Service/Agency. Refer to ADC 1014A. Reason Identifies DLMS Changes included in the transaction. Updates data content for consistency across requisition related transactions. Clarifies that the CLIN may be provided at an alternative location when using the GF01 to identify the MDN. Supports enhanced functionality to identify the CLIN when also identifying the MDN. 4. 2/GF09/100 Open GF09 for identification of the CLIN. Supports enhanced functionality. ADC 1014A, Enclosure 2, Page 5