1 of 11 

ADC 216 

Attachment 

ATTACHMENT TO ADC 216 

Revise DLMS Supplement (DS) 527R Receipt in Support of Commercial Asset 

Visibility (CAV) and Administrative Change for Army Medical Materiel 

Agreement (AMMA) (Supply/Staffed by PDC 211) 

1. ORIGINATOR: 

a. Service/Agency: Sponsored by Defense Logistics Management Standards Office 

(DLMSO) in support of the Commercial Asset Visibility (CAV) program

b. Originator: Ms. Mary Jane Johnson, DLMSO, MILSTRAP Administrator, e-mail: 

Mary.Jane.Johnson@dla.mil

2. FUNCTIONAL AREA: Supply 

3. REFERENCES: 

 a. DLMSO memorandum, August 25, 2006, subject: Proposed DLMS Change (PDC) 211, 

Revise DLMS Supplement (DS) 527R Receipt in Support of Commercial Asset Visibility (CAV) 

and Administrative Change for Army Medical Materiel Agreement (AMMA) 

 b. DLMSO memorandum, July 6, 2006, subject: Proposed DLMS Change (PDC) 222, 

Communication of Unit Price and Total Price under DLMS. PDC 222 is available at: 

http://www.dla.mil/j-6/dlmso/eLibrary/changes/proposed.asp 

 c. DLMSO memorandum, June 22, 2006, subject: Approved DLMS Change (ADC) 201, 

Revisions to DS 867I to Support Requirements for the AMMA Issue Transactions. ADC 201 is 

available at: http://www.dla.mil/j-6/dlmso/eLibrary/changes/approved3.asp 

4. REQUESTED CHANGE: 

a. Title: Revise DLMS Supplement (DS) 527R Receipt in Support of Commercial Asset 

Visibility (CAV) and Administrative Change for Army Medical Materiel Agreement (AMMA). 

b. Comments to PDC 211. This change was staffed by referenced PDC 211. Comments to 

PDC 211 are as follows: 

Agency PDC 211 Comment Disposition 

Army 

Mr. Ken Deans 

SPRC representative 

Concur 

DoD CAV II Program 

Manager 

Mr. Booker Washington 

NAVSUP HQ 

My understanding, Navy CAV II DLMS changes will be 

incorporated in the Navy ERP Increment 1.1, 

scheduled for FEB 2009 

Noted in 527R 
2 of 11 

ADC 216 

Attachment 

Agency PDC 211 Comment Disposition 

For the CAV Receipt Type Code table, based on new 

CAV Release (V6.0), please add the following receipt: 

SRA RECEIPT (Sub-System Repair Assembly): 

 1. Receipt Type Description: SRA Receipt 

 2. DOC ID: D6A 

 3. Receipt Type Code : S 

 4. Receipt Condition Code: A 

 5. Purpose Code: A

Noted in 527R 

change table 

below at row 13 

Navy-NAVSISA 

Ms. Delores Leak 

Below is an explanation of the "award/order date" which 

NAVSISA received from Ms. Terry Donnelly (NAVICPM): 

"The Order Date is the date the Delivery Order (written 

against the BOA providing the authorization/funds for 

repair) is awarded. If the repair is being done against a 

different type of Contract that does not have a Delivery 

Order written against it, then the Award Date would 

reflect the date the Contract itself was awarded." 

[DLMSO note: NAVSISA provided this information in 

response to DLMSO request for explanation of use of 

term ‘award/order date’ in CAV II IDD.] 

Noted 

DCSA 

Mr. Kent Bell 

SPRC representative 

Concur with no comments 

DLMSO Comment on 

‘CAV Receipt Type Code’ 

DLMSO is acknowledging Navy CAV II use of a ‘Navy 

CAV Receipt Type Code’ in DS 527R as it is required 

by their existing Navy CAV II system, but no other 

systems should plan to use this code. 

In general, DLMS does not support codes which 

represents combinations of data such as CAV Receipt 

Type Code appears to do. Systems other than CAV 

should not use ‘CAV Receipt Type Code’, but should 

rely instead on the explicitly stated data such as supply 

condition code, purpose code, etc. 

DLMS discourages transactional use of codes with 

embedded data. DLMS strives to use data elements 

that are “atomic” in nature and represent a single fact 

with no other embedded meaning. Sometimes that is 

not possible as DLMS is faced with accommodating 

interface with legacy systems that are already invested 

in data schemas that are implemented in systems with 

complex logic to unravel the facts that are contained in 

composite data elements. 

Noted in 527R 

Change Table 

below, at CAV 

Receipt Type 

Code (527R 

change table, 

row 13, 

2/LQ01/130/T03) 
3 of 11 

ADC 216 

Attachment 

c. Description of Change: 

 (1) This change updates and supports CAV requirements for the DS 527R receipt 

transaction. It provides clarification of specific DS 527R CAV receipt data; the addition of 

additional data required by CAV; and corrected CAV mapping for certain data. This change also 

incorporates DLMS expanded field length requirements for unit price identified by PDC 222, 

Communication of Unit Price and Total Price under DLMS (reference 3.a.). 

 (2) This change provides administrative updates to add a new DLMS introductory note for 

Authorized DLMS migration enhancement. The new note states: “Data associated with a DLMS 

enhancement authorized for implementation by modernized systems under DLMS migration. This 

data (including expanded field sizes) should be adopted during, or subsequent to, modernization 

when applicable to the Component’s business process. Prior coordination is not required. 

Components should ensure that inclusion of this data in a DLMS transaction does not cause 

inappropriate rejection of the transaction.” 

(3) This change provides an administrative update to Army Medical Material Agreement 

(AMMA) ‘acquisition unit price’ to reflect the R9.2 format documented for AMMA by ADC 201 

(reference 3.b.); and to reflect the new DLMS introductory note 5.g for Authorized DLMS 

Migration enhancements. For AMMA revisions, see rows 10 and 11 of the DS 527R change 

table at subparagraph 4.c below. 

 d. Procedures: Revise DS 527R as follows (Changes from PDC 211 are highlighted): 

Item

# 

Location Revision to 

DS 527R Receipt 

Reason Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes 

Add new DLMS introductory note 5.g: 

g. Data associated with a DLMS enhancement 

authorized for implementation by modernized 

systems under DLMS migration. This data 

(including expanded field sizes) should be adopted 

during, or subsequent to, modernization when 

applicable to the Component’s business process. 

Prior coordination is not required. Components 

should ensure that inclusion of this data in a DLMS 

transaction does not cause inappropriate rejection 

of the transaction.

To provide an enhancement note 

to acknowledge enhanced data 

authorized for implementation in 

DLMS 

No 

impact 

2. DLMS 

Introductory 

Notes 

Add ADC 216 to DLMS introductory note 7: 

-ADC 216, Revise DS 527R Receipt in Support of 

Commercial Asset Visibility (CAV) and 

Administrative Change for Army Medical Material 

Agreement (AMMA). 

To identify DLMS changes 

included in the DS 

No 

impact 
4 of 11 

ADC 216 

Attachment 

Item

# 

Location Revision to 

DS 527R Receipt 

Reason Federal 

IC 

Impact

3. 1/N101/70 

Qualifier 41 

Add a new DLMS note 2 to existing qualifier 41-

Submitter, to identify CAV use, and number 

existing note as note 1.

DLMS Note 2. Used in Commercial Asset 

Visibility (CAV) receipts to identify the repair 

contractor submitting the receipt. CAV expresses 

the repair contractor as a DODAAC (N103 code 10). 

To document CAV requirement No 

impact 

4. 1/N103/70 

Qualifier 10 

Add a new DLMS note 2 to existing qualifier 10-

DODAAC, and number existing note as note 1:

DLMS Note 2. CAV uses for receipts in 

conjunction with N101 code 41 to identify the 

DODAAC of the repair contractor submitting the 

receipt to CAV. 

To document CAV requirement No 

impact 

5. 2/G6201/50 

Qualifier 52 

Existing qualifier 52-Ordered:

DLMS Note: Use in Commercial Asset Visibility 

(CAV) receipts to indicate an Order Date. 

Documents CAV use of the 

Order Date in CAV receipts. 

Existing 527R qualifier and note 

unchanged. 

PDC 211 requested that Navy 

provide a functional explanation 

of what the “order date” was; 

specifically what does “order” 

represent in this context, and why 

it is called the “award/order” 

date in the NAVSUP/NAVSISA 

Interface Design Description 

(IDD) for CAV II 527RD4S/D6A (Version 5, Change 2, 

1 Aug 2005). 

Per the PDC 211 comments in 

paragraph 4.b., above, NAVY 

indicates the Order Date is the 

date the Delivery Order 

(written against the BOA 

providing the authorization/ 

funds for repair) is awarded. If 

the repair is being done against 

a different type of Contract 

that does not have a Delivery 

Order written against it, then 

the Award Date would reflect 

the date the Contract itself was 

awarded.

No 

impact 
5 of 11 

ADC 216 

Attachment 

Item

# 

Location Revision to 

DS 527R Receipt 

Reason Federal 

IC 

Impact

6. 2/N901/90 

Qualifier OR 

Add qualifier OR-Order/Paragraph Number

with DLMS note as follows:

OR Order/Paragraph Number 

DLMS Note 1: For use with CAV receipt, to 

identify the 4-position order number associated with 

a contract number. Authorized DLMS migration 

enhancement for CAV use. See DLMS 

introductory note 5.g.

To document CAV requirement 

for a 4-position order number 

used with a Contract Number 

Supports NAVSUP/NAVSISA

Interface Design Description 

(IDD) for CAV II 527RD4S/D6A (Version 5, Change 2, 

1 Aug 2005) (hereafter referred 

to in this PDC as CAV II IDD)

which indicates CAV maps order 

number to 527R 2/N901/90 

qualifier OR. 

No 

impact 

7. 2/N907/90 Add Federal Note: Use any code. 

Renumber existing DLMS note.

Add new DLMS Note: For DLMS use, only the 

following codes are authorized. 

For consistency with other DLMS 

supplements 

Revision 

required 

8. 2/N907/90 

Qualifier 1Y 

Revise current DLMS note and add a second 

DLMS note to existing qualifier ‘1Y-Repair 

Action Number’ to identify current CAV use: 

1Y Repair Action Number 

DLMS Note 1. Use in conjunction with N901 

code AH for receipts to identify the DMISA line 

number when applicable. , otherwise do not use.

2. For Commercial Asset Visibility (CAV) 

receipts, temporary use of qualifier ‘1Y’ to 

identify the CLIN/SUBCLIN is acknowledged for 

CAV systems which have already programmed for 

‘1Y’. New and future CAV implementations 

should use 2/N907/90 qualifier C7 to identify 

CLIN/SUBCLIN. Current CAV users of 1Y shall 

transition to qualifier C7 as soon as possible, and 

1Y shall no longer be used for CLIN/SUBCLIN. 

Navy anticipates CAV II DLMS changes will be 

incorporated in the Navy ERP Increment 1.1, 

scheduled for February 2009. 

DLMSO’s understanding is that 

some CAV systems have 

programmed qualifier ‘1Y-Repair 

Action Number’ to represent the 

CLIN/SUBCLIN, while others 

have programmed qualifier ‘C7-

CLIN’. 

DLMSO does not agree with 

continued use of 2 distinct 

qualifiers for the same purpose; 

however as a temporary measure, 

this PDC documents current CAV 

use of ‘1Y’ for CLIN/SUBCLIN 

by some CAV systems, while 

noting that 1Y shall be phased out 

in favor of qualifier ‘C7’. 

Accommodates current CAV 

requirements where both 

qualifiers are used, but identifies 

the inconsistency for CAV 

correction. 

No 

impact 
6 of 11 

ADC 216 

Attachment 

Item

# 

Location Revision to 

DS 527R Receipt 

Reason Federal 

IC 

Impact

9. 2/N907/90 

Qualifier C7 

Add qualifier C7-Contract Line Item Number 

with DLMS Note

C7 Contract Line Item Number 

DLMS Note: For use in Commercial Asset 

Visibility (CAV) receipts to identify the 

CLIN/SUBCLIN. Use in conjunction with N901 

code CT. Authorized DLMS migration enhancement 

for CAV use. See DLMS introductory note 5.g. 

To document CAV requirement No 

impact 

10. 2/AMT/100 Revise AMT segment DLMS note 1 and add note 2: 

DLMS Note 1: Use as needed for Army Medical 

Material Agreement (AMMA) and Commercial 

Asset Visibility (CAV) receipts. Use of this segment 

for AMMA and CAV is an authorized DLMS 

migration enhancement. See introductory DLMS 

note 5.g. 

2. Use by other than AMMA or CAV is a DLMS 

enhancement. See introductory DLMS note 5.a. 

Documents CAV requirement for 

a unit price in the receipt 

Background Note: The CAV II 

IDD shows unit price mapped to 

2/FA201/346 qualifier ZZ, 

however FA201/ZZ is 

supplemental accounting 

classification data, and is not 

designed nor intended for use as a 

unit price. Accordingly the AMT 

segment is being opened for the 

unit price. 

DLMSO does not agree with use 

of FA201 ZZ for unit price, 

however as a temporary measure, 

a DLMS note at 2/AMT01/100, 

qualifier NT acknowledges the 

current CAV mapping of unit 

price to the FA201 qualifier 

intended for ‘supplemental 

accounting classification data’, 

while documenting the need for 

CAV update. 

No 

impact 
7 of 11 

ADC 216 

Attachment 

Item

# 

Location Revision to 

DS 527R Receipt 

Reason Federal 

IC 

Impact

11. 2/AMT01/100 

Qualifier JJ 

Revise qualifier JJ-Cost Basis’ DLMS notes 1 and 

2 as follows: 

JJ Cost Basis 

DLMS Note 1. Use only for AMMA receipts to 

identify the acquisition unit price of the material. This 

price will allow valuation of inventory for receipts not 

against a purchase order. Under DLMS the latest 

acquisition cost will be expressed as R9.2. R is the 

data element type indicating a decimal numeric data 

element. The decimal point is passed within the 

transaction; leading and trailing zeros are not 

transmitted. 

2. Authorized DLMS migration enhancement. See 

DLMS introductory note 5.g. 

Administrative update to: 

(1) Reflect ASC X12 R9.2 

format for Army Medical 

Material Agreement (AMMA)

acquisition unit price previously 

documented by June 22. 2006, 

ADC 201, Revisions to DS 867I 

to Support Requirements for the 

AMMA Issue Transactions 

(2) Reflect new DLMS 

introductory note 5.g for 

Authorized DLMS Migration 

enhancement.

No 

impact 

12. 2/AMT01/100

Qualifier NT 

Add AMT01 Amount Qualifier Code ‘NT-Unit Value’ 

with DLMS notes: 

NT Unit Value 

DLMS Note 1. Use when needed in CAV receipts to 

cite the standard unit price of the item received. 

2. DLMS transactions authorize an expanded unit 

price field size of 9 digits for dollars and 2 digits for 

cents. This is expressed as “R9.2” (R is the data 

element type indicating a decimal numeric data 

element). The decimal point is passed within the 

transaction; leading and trailing zeros are not 

transmitted. 

3. Use of unit price in CAV receipts and use of the 

expanded field size are authorized DLMS migration 

enhancements. See DLMS introductory note 5.g. 

4. Until the expanded field size is fully implemented, a 

field size exceeding 7 positions (5 digits dollars and 2 

digits cents) may not be received or understood by the 

recipient’s automated processing system. DAAS will 

truncate the price for MILS users. 

5. CAV temporarily uses 2/FA201/346 qualifier ZZ to 

identify the unit price, but this use conflicts with the 

intended DLMS purpose for qualifier ZZ. CAV shall 

transition to use of the AMT segment for unit price in 

lieu of 2/FA201/346/ ZZ. Navy anticipates CAV II 

DLMS changes will be incorporated in the Navy ERP 

Increment 1.1, scheduled for February 2009. 

Supports CAV requirement for a 

unit price in the receipt. 

Use of the AMT segment affects 

CAV mapping for unit price 

identified in the CAV II IDD. 

Background: The CAV II IDD 

shows use of 2/FA201/346 

qualifier ZZ for unit price. 

FA201/ZZ is supplemental 

accounting classification data and 

is not intended for use as a unit 

price. 

DLMSO does not agree with use of 

FA201/ZZ for unit price, however 

as a temporary measure, this PDC 

notes the current CAV mapping of 

unit price to the FA201 qualifier in 

a DLMS note at 2/AMT01/100/ 

qualifier NT, documenting the need 

for CAV update. 

STAFFING NOTE ON FIELD 

SIZE: PDC 222, Communication 

of Unit Price and Total Price Under 

DLMS, expands the field size for 

the unit price on the Issue Release/ 

Receipt Document (IRRD) (DD 

Form 1348-1A) and establishes a 

corresponding field size for the unit 

price in the DLMS transactions. 

ADC 216 perpetuates the PDC 222 

unit price expanded field size. 

No 

impact 
8 of 11 

ADC 216 

Attachment 

Item

# 

Location Revision to 

DS 527R Receipt 

Reason Federal 

IC 

Impact

13. 2/LQ01/130 

Qualifier T03 

Add qualifier ‘T03-Operation Type’

with DLMS Notes: 

T03 Operation Type 

DLMS Note 1: Navy CAV uses with 

receipts to identify the ‘CAV Receipt 

Type Code’. DLMS is acknowledging 

Navy CAV II use of a ‘CAV Receipt 

Type Code’ in DS 527R as it is 

required and used by their existing 

Navy CAV II system, but no other 

systems should plan to use this code in 

527R.. Systems other than Navy CAV 

should rely instead on explicitly stated 

data in the transaction, such as supply 

condition code, purpose code, etc. 

Navy CAV use is an authorized DLMS 

migration enhancement for Navy CAV 

use only. See introductory DLMS 

introductory note 5.g. 

2. Navy CAV temporarily uses 

2/LQ01/130 Qualifier A9 to identify 

the CAV Receipt Type Code, but this 

use conflicts with the intended DLMS 

purpose of qualifier A9. Navy CAV 

shall transition to use of qualifier T03 

for CAV Receipt Type Code, in lieu of 

qualifier A9. Navy anticipates CAV II 

DLMS changes will be incorporated 

in the Navy ERP Increment 1.1, 

scheduled for February 2009.

To provide qualifier for ‘CAV Receipt Type Code’ 

1. See DLMSO comment on CAV receipt type 

code in the PDC 211 comments on page 2 of this 

attachment. 

2. Use of 2/LQ01/130 affects CAV 527R mapping 

for the CAV Receipt Type Code. The CAV II IDD 

shows “CAV Receipt Type Code” mapped to 

2/LQ01/130 Qualifier ‘A9 -Supplemental Data’. 

This is a misuse of qualifier A9. A different LQ 

qualifier should be used. This ADC documents use 

of ‘T03-Operation Type’ for this purpose. 

DLMSO does not agree with use of 

2/LQ01/130/A9 for CAV Receipt Type Code, 

however as a temporary measure, this PDC notes 

the current CAV mapping in a DLMS note at 

qualifier T03, documenting the need for update. 

3. CAV identified the following as sources for the 

CAV Receipt Type Code, the CAV Interface 

Design Description (IDD), Software Design 

Description (SDD), and Software Requirements 

Specification (SRS). These documents are located 

at NAVSISA. They are prepared by NAVSISA 

and provided to the CAV II sponsors only. “For 

Official Use Only – Business/ Competition 

Sensitive” 

The CAV Receipt Type Codes documented in the 

CAV II IDD: 

VALID RECEIPT TYPE/CONDITION/ PURPOSE CODE 

COMBINATIONS: 

Receipt Type 

Description 

Doc 

ID 

Recei

pt 

Type 

Code 

Receipt 

Condition

Code 

Purpos

e Code 

Receipt On 

Contract 

D6A C F A 

Receipt Not 

On Contract 

D6A N J A 

Procurement D4S P A A 

Rotable Pool D6A R A V 

Loaned Asset D6A L A A 

'A' Condition D6A A A A 

Litigation D6A T L A 

SRA Receipt 

(Sub-System

Repair 

Assembly )

D6A S A A 

No 

impact 
9 of 11 

ADC 216 

Attachment 

Item

# 

Location Revision to 

DS 527R Receipt 

Reason Federal 

IC 

Impact

14. 2/LQ01/130 

Qualifier 

SMI = SMIC 

GQ = MMAC 

No revision to DS 527R, however NOTE to 

CAV: NAVSISA CAV II IDD shows the Air 

Force MMAC mapped to 2/LQ01/130 qualifier 

SMI (Special Materiel Identification Code). 

Qualifier ‘SMI’ is correct mapping for the Navy 

SMIC only. 

Qualifier ‘GQ’ is correct mapping for the Air 

Force Materiel Management Aggregation Code 

(MMAC). 

Navy anticipates CAV II DLMS changes will be 

incorporated in the Navy ERP Increment 1.1, 

scheduled for February 2009.

This affects CAV 527R mapping 

identified in the CAV II IDD for 

the MMAC. Mapping should be 

corrected to reflect LQ01 qualifier 

GQ-MMAC. 

NOTE: ASC X12 1270 qualifier 

GQ is the qualifier DLMS 

currently uses for the USAF 

MMAC, however 1270 qualifier 

‘MAC’ has been formally 

approved for the MMAC for ASC 

X12 version 5010. 

No 

impact 

15. 2/N101/210 

Qualifier CI 

Add new DLMS note 1 to qualifier CIConsignor, and combine existing notes into note 

2 as shown:

DLMS note 1: Use in Navy Commercial Asset 

Visibility (CAV) receipts to identify the 

organization shipping the materiel. Authorized 

DLMS migration enhancement. See introductory 

DLMS note 5.g. 

2. Use in “not from due” receipts only to identify 

the organization shipping the materiel. DLMS 

enhancement. See introductory DLMS note 5a. 

To document CAV requirement No 

impact 

16. 2/N101/210 

Qualifier SF 

Delete qualifier “SF” Ship From and its associated 

notes from the DLMS Supplement. This is a 

duplication of the CI Consignor qualifier and serves 

the same purpose.

To eliminate qualifier with 

duplicate purpose. 

The CAV II IDD indicates that 

the consignor who shipped the 

materiel is mapped to ‘CIConsignor’ vice ‘SF-Ship From’. 

Since SF was added to 527R for 

CAV use by ADC 140, but 

duplicates the purpose of CI, 

recommend deleting SF at this 

time in favor of CI. 

Based on ADC 216, DLMSO 

will withdraw ADC 140. 

No 

impact 
10 of 11 

ADC 216 

Attachment 

Item

# 

Location Revision to 

DS 527R Receipt 

Reason Federal 

IC 

Impact

17. 2/N101/210 

Qualifier ZD 

Add DLMS note 2 to qualifier ZD-Party to Receive 

Reports:

DLMS Note 2. Use in Navy Commercial Asset 

Visibility (CAV) receipts to identify the party to 

receive report. CAV expresses party to receive 

report as a DODAAC (N903 code 10). CAV use is 

an authorized DLMS migration enhancement. See 

DLMS introductory note 5.g. 

To document Navy CAV 

requirement 

No 

impac. 

18. 2/N103/210 

Qualifier 10 

Add a new DLMS note 2 to qualifier 10-DODAAC, 

and renumber existing note as note 1:

DLMS note 2. CAV uses for receipts in 

conjunction with N101 codes Z4 and ZD. 

To document Navy CAV 

requirement 

No 

impact 

19. 2/REF01/250 

Qualifier SE 

Add a new DLMS note 2 to qualifier SE-Serial 

number:

DLMS Note 2. Commercial Asset Visibility (CAV) 

uses in receipts to identify the serial number of the 

repair item. 

To document Navy CAV use of 

serial number 

NOTE TO CAV: The CAV II 

IDD provides for mapping a 

serial number greater than 30 

positions (First 30 positions in 

2/REF01/250 with overflow 

going in another segment.) 

DLMSO cannot support this 

requirement as the OSD Item 

Unique Identification (IUID) 

policy restricts the serial number 

to 30 positions. DLMS complies 

with the IUID 30 position serial 

number limitation.

STAFFING NOTE: The “DOD 

Guide To Uniquely Identifying 

Items”, Ver 1.6, 6/1/06, App C,

IUID Business Rules, Metadata 

Requirements, Para 19 states that 

“the serial number string of 

characters (including special 

characters) will not exceed 30 

characters, excluding the data 

qualifier”. 

The guide is available at: 

http://www.acq.osd.mil/dpap/UID

/guides.htm. 

No 

impact 
11 of 11 

ADC 216 

Attachment 

5. REASON FOR CHANGE: DLMSO’s review of the “NAVSUP/NAVSISA Interface Design 

Description for CAV II 527R-D4S/D6A (Version 5, Change 2, 1 Aug 2005)”, revealed the need for 

revision of DS 527R receipt transaction for: clarification of specific DS 527R receipt data for 

CAV; incorporation of additional data required by CAV; and corrected CAV mapping for certain 

data. This change documents those requirements/revisions. Some of these issues initially surfaced 

during Spring 2006 teleconferences between DLMSO and USAF CAV representatives to discuss a 

CAV developed Context Inspired Component Architecture (CICA) message for Receipt, resulting 

in a detailed DLMSO review of the 527R IDD. 

6. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Clarifies CAV data requirements in DS 527R receipt 

 b. Disadvantages: Requires CAV revisions to reflect revised mapping where applicable 

7. INTERFACE AND IMPACT: 

a. Publication(s): DOD 4000.25-M, DLMS and 527R DLMS Supplement. Revision to 527R 

Federal IC will be submitted to the EDISMC/Logistics Functional Work Group for 

coordination/approval. 

b. DAASC Mapping: Updates may be required to DAASC mapping. 

c. CAV: Requires system and documentation changes, to reflect the revised/corrected 

mapping.