Attachment, ADC 428 

Page 2

ADC 428A 

Support to Missile Defense Agency (MDA) as a FMS Implementing Agency 

(IA) and Assignment of New Service and Agency (S/A) Code “I”

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

 a. Service/Agency: Missile Defense Agency (MDA) 

 b. Originator: MDA, Attn: DI, commercial phone: 256-955-1142, DSN: 645-1142 

2. FUNCTIONAL AREAS: Supply (including requisitioning and Supply Discrepancy Report 

(SDR)/MAPAD) 

3. REFERENCES: 

 a. Defense Security Cooperation Agency (DSCA) memorandum dated March 14, 2011, 

Revised List of Implementing Agencies (lAs) in Chapter 5, Table C5.T2. of the Security 

Assistance Management Manual (SAMM), DSCA Policy 11-14, [SAMM E-Change 182]. This 

memorandum updates DoD 5105.38M, SAMM, to add MDA as an IA for Foreign Military Sales 

(FMS) (Enclosure 3). 

 b. DoD 4000.25-1-M, Military Standard Requisition and Issue Procedures (MILSTRIP) 

Manual. 

 c. DoD 4000.25-8-M, Military Assistance Program Address Directory (MAPAD). 

4. REQUESTED CHANGES: 

a. Description of Change: The MDA is soon to be established as an Implementing 

Agency (IA) for Foreign Military Sales related to a new weapon system and support parts. In 

order for standard logistics systems to recognize transactions associated with MDA FMS, a new 

Service and Agency (S/A) Code to identify “MDA - Security Assistance Only” will be 

established under this change proposal. The new S/A Code will allow tracking and independent 

processing for MDA, which is currently using Army systems for support. STAFFING NOTE 

FOR DOD COMPONENTS: This change initially impacts MDA and DLA Transaction 

Services. However, as the weapons system program matures, management of the weapon 

system itself and/or support parts may transition to the Army and Defense Logistics Agency 

(DLA). 

b. This addendum is provided to make administrative corrections to the approved change 

documentation and document additional requirements for new distribution code and fund codes 

to support MDA as an IA. Revisions are highlighted in green. 

 
Attachment, ADC 428 

Page 3

c. Background: 

(1) When a S/A Code is used to identify an FMS transaction, such as a requisition, it 

appears in the first position of the document number. From the value in the first position of the 

document number, it can be determined which Service or Agency is associated with the FMS 

case and which International Logistics Control Office (ILCO) is responsible for validating the 

requisition. Current S/A Code values indicating Security Assistance are "B, D, K, P, and T." 

These values are used to trigger numerous automated system processes. DLA Transaction 

Services routes all FMS requisitions to the ILCO if not received from the ILCO. Validated 

requisitions submitted by the ILCO are then routed to the designated DoD Supply Source. This 

ensures that all FMS requisitions are monitored and validated by the appropriate party before 

being transmitted to the supply source. 

(2) There has been a determination that MDA will be an IA for selected FMS weapon 

system cases. MDA will be using Army systems for support of FMS customers until the Security 

Cooperation Enterprise System (SCES) is fielded. The weapon system that MDA is supplying 

under FMS is owned by MDA, and MDA will be the source of supply for the equipment and 

parts through its weapon system contractor. At this time, no other DoD Components are 

involved as the DoD supply source. It is envisioned that common use parts may migrate to 

DLA for item management. The weapon system itself may transition to the Army as the supply 

source at a future time. 

(3) A new Routing Identifier Code (RIC) has been established to identify MDA. It will 

be used in requisitions to indicate that MDA is a supply source. The RIC value “HB1” was 

created using the H-series designation maintained by Washington Headquarters Service (WHS). 

The associated DoD Activity Address Code (DoDAAC) for the MDA is HQ0147. STAFFING 

NOTE: The S/A Code used in a DoDAAC or RIC does not correspond to the S/A Code used in 

the document number of Security Assistance transactions. The S/A Code used in the 

document number for Security Assistance transactions correlates to the implementing agency/ 

ILCO responsible for the FMS case.

d. Procedures: The following procedures are approved. 

(1) MDA: 

(a) MDA will establish an ILCO, which will be responsible for entering and 

maintaining MAPACs in the MAPAD, as required, for use with requisitions submitted with 

Service/Agency Code “I”-based document numbers. MDA will initiate a Performance Based 

Agreement (PBA) and System Authorization Access Request (SAAR) with DLA Transaction 

Services to establish required interface connections. MDA will forward a letter to the MAPAD 

Administrator designating the MAPAD Process Review Committee Representatives with 

authority to establish and maintain MDA MAPACs. MDA will assume all ILCO responsibilities 

as required under MILSTRIP/MILSTRAP, or as otherwise required. (Not all responsibilities are 

delineated in this proposal.) 
Attachment, ADC 428 

Page 4

(b) MDA Security Assistance customers will be instructed to use the “I” as the first 

position of the document number when requisitioning under MDA-administered FMS cases. 

Initially, these requisitions will also identify MDA as the supply source. 

(c) MDA will be responsible for input of its customer SDRs, manually via DoD 

WebSDR or using a DLMS-compliant interface. MDA will receive Government-prepared SDR 

replies (acting as intermediary for the FMS customer). If a DLMS-compliant interface is not 

available, SDR replies will be provided via encrypted email. MDA must provide an appropriate 

email address for SDR distribution. 

(d) MDA will be responsible for providing updates to the Fund Code Table to support 

interfund billing as applicable. Fund codes are used in association with the specified 

Service/Agency and, therefore, new values must be assigned when needed for use with document 

numbers beginning with Service/Agency Code "I". Military Standard Billing System 

(MILSBILLS) Fund Code Service Points must be designated for maintenance of the Fund Code 

Table hosted by DLA Transaction Services. Fund Codes will be published in MILSBILLS, 

AP1.2, Current Fund Code to Billed DoDAAC Conversion Table. 

(e) MDA will submit additional SAARs as needed, e.g. for Logistics Reports and 

WebVLIPS access.

(2) DLA Transaction Services: 

(a) DLA Transaction Services and supporting systems need to add the letter “I” to all 

transaction edits intended to recognize FMS that are currently based on "B, D, K, P, and T" in 

the first position of the document number. 

(b) DLA Transaction Services will route all FMS requisitions to the MDA ILCO, if 

not received from the MDA ILCO. Pending implementation of the Security Cooperation 

Enterprise Solution (SCES), all FMS requisitions with document numbers beginning with "I" 

will be processed through the Army ILCO system, Centralized Integrated System for 

International Logistics (CISIL). 

(c) DLA Transaction Services will revise MILSTRIP edits that are based upon the 

Security Assistance S/A Codes. Examples are:

1. Expedited Handling edits will exclude S/A Code “I” for Expedited 

Handling Signal “999”, which currently does not apply to FMS/Map Grant-Aid requisitions.

2. Requisition downgrade logic for the Force Activity Designator (F/AD) 

process will include S/A Code “I” for automatic downgrade of F/AD 1.

(d) DLA Transaction Services will route MRA follow-ups for security assistance 

requisitions identified by S/A “I” to the MDA ILCO supported by CISIL. 
Attachment, ADC 428 

Page 5

(e) DLA Transaction Services will update the Distribution Code table to add new 

Distribution Code B for MDA in association with Service/Agency Code “I.” Use of a 

distribution code in record position 54 of the MILSTRIP legacy requisition, or the first position 

of the distribution code data field in DLMS, indicates that the activity designated by the entry 

will be furnished 100 percent supply and shipment status. Status provided for Distribution Code 

B will be furnished to the MDA ILCO supported by Army CISIL. 

(f) DLA Transaction Services will revise internal logic for Supply Discrepancy 

Reports (SDRs) processing under DoD WebSDR to recognize S/A Code “I” as Security 

Assistance. 

(3) DoD Components 

(a) DoD Components will be required to recognize S/A Code “I” in the first position 

of the document number as denoting “MDA - Security Assistance Only.” 

(b) There are many rules in Inventory Control Point (ICP) systems applicable to 

Security Assistance. For example, only materiel above the reorder point level is available for 

FMS issues. Modifiers are rejected if the Country FMS Offer/Release Option or Freight 

Forwarder Code is modified when the requisition is not FMS. Logistics transfers are done 

differently for modifiers that are FMS. Denial Management Code 8 is only valid on FMS. The 

MRA process contains many time frames based on whether or not the requisition is FMS. SDR 

time standards are different for FMS. STAFFING NOTE FOR DOD COMPONENTS: 

Components must determine specific applications/business processes that will be impacted. 

Where programming changes are required, Components need to provide the estimated time 

required to complete the changes. Under the phased implementation plan, future impact may 

be restricted to DLA and Army systems.

 

(4) DLA Distribution Depots. Subsequent to transition to the Army and/or DLA as 

supply sources, the Distribution Standard System will be required to recognize S/A Code “I” as 

“MDA - Security Assistance Only.” 

(5) Historical record retention rules within DoD Components and DLA Transactions 

Services will need to be modified to ensure applicability to MDA FMS. 

(6) Changes to MILSTRIP manual will be made as identified in Enclosure 1, with 

corresponding changes to the MAPAD manual. 

5. REASON FOR CHANGE: Currently, the MDA contractor is providing parts as needed, 

until the final development is completed. Therefore, the requested changes are needed to allow 

MDA to function as an IA and as a source of supply. In order to identify requisitions and 

delivery reporting issued by MDA and not Army, the requested changes are necessary. Without 

the distinction, the Letter of Authorization (LOA) and requisition numbers will appear as Army. 

Ultimately, other Components, particularly Army and DLA will have a requirement to satisfy 

requisitions using the new S/A Code “I” in the document number. 

6. ADVANTAGES AND DISADVANTGES 
Attachment, ADC 428 

Page 6

 a. Advantages: These changes will support the MDA to become an FMS IA. MDA will be 

able to supply equipment that is owned by MDA or under contract to MDA with a correct source 

of supply identified. The delivery reporting that must go to Defense Finance and Accounting 

Services (DFAS) for Defense Integrated Financial System (DIFS) processing will be identified 

as initiated by MDA and not Army and will be posted to the MDA LOA. The FMS customer 

will have visibility of requisitions and deliveries that are MDA and not Army. Army reports will 

only depict true Army work and not have MDA work included. 

 b. Disadvantage: 

 (1) There is concern for the human readable aspect with “I” as an S/A code, especially 

since special program document numbers could begin with a “1”. 

 (2) The exclusive use of S/A Code “I” for MDA may result in inappropriate transparency 

of support and transport of equipment/parts relevant weapon systems.

7. IMPACT: 

a. DLA Transaction Services and DoD Component Systems. S/A Code “I” will no 

longer be treated as an invalid value and will be designated as applicable to MDA for FMS 

customer use. Applicable transaction processing rules/edits and business processes must be 

revised accordingly. 

b. The MDA Transition to an Implementing Agency Action Plan outlines applicable 

system and procedural changes for trading partners, as well as training and requirements for 

overarching authorization to proceed. Implementation of this change is contingent upon 

successful accomplishment of these.

c. Implementation Schedule: Phased implementation beginning with DLA Transaction 

Services and MDA. Subsequently, applicability will be expanded to other DoD Components. 

Testing is anticipated to begin June-July 2011. No date is available at this time for submission of 

requisitions using the S/A Code “I" – the first FMS case is not anticipated before 1st or 2nd 

quarter FY 12. 

d. Publication: 

(1) DoD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP) Manual, Appendix 2.2 

(2) DoD 4000.25-8-M, Military Assistance Program Address Directory (MAPAD). 

(3) DoD 5105.38-M, Security Assistance Management Manual (SAMM) as revised 

by reference 3.a. 

 e. DLMS Data. This change adds a new value for Service and Agency Code in the DLMS 

dictionary (LOGDRMS). There are no new DLMS data elements associated with this change.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None provided.
Enclosure 1, ADC 428 

Enclosure 1

AP2.2. APPENDIX 2.2

SERVICE AND AGENCY1 CODES

MILSTRIP SERVICE CODES

NUMBER OF 

CHARACTERS: 

One or two. 

TYPE OF CODE: Alpha. 

EXPLANATION: S/A codes are designed to accommodate S/A identity in MILSTRIP 

documentation. For this purpose, these codes are used in conjunction with 

other codes to identify the parent S/A of requisitioners and other addressees. 

The S/A codes will be used in rp 4, 30, 31, 45, 46, 67, and 74 of the DD Form 

1348 series of documents. By exception, two-position combination codes using 

the authorized Service/Agency code and a specified second position are 

authorized to identify contractor DoDAACs.2

 FEDSTRIP provides for the use 

of the two position codes, defined as civil Agency codes, to be entered in rp 30-

31 and 45-46 of the GSA Form 1348 series of documents. The MILSTRIP 

Service codes3

 and the FEDSTRIP Agency codes4 are listed below: 

RECORD 

POSITION(S): 

4, 30, 31, 45, 46, 67, and/or 74.5

                                                           

1

Refer to the Treasury Financial Manual Supplement--FAST Book (Part II link to Independent Agencies) 

for listing of Federal Civil Agency codes http://www.fms.treas.gov/fastbook/ used as the first two positions 

of the AAC.

2 Combination codes authorized for USCG and DLA. Refer to ADC 319.

3

 Mandatory usage rules for Service and Agency Codes are established for the assignment of DOD 

Activity Address Codes (DODAACs) and Routing Identifiers (RICs). Further stratification for DODAAC 

assignment usage rules may be found at: Link to Service Codes

4

See Footnote 1.

5 MILSTRIP record position key: 

4 - First position of the Routing Identifier Code (RIC) 

30 - First position of the Document Number 

31 – Second position of the Document Number 

45 – First position of Supplementary Address 

46 – Second position of Supplementary Address 

67 – First position of RIC for U.S. supply source preparing the DD Form 1348-1A or DD Form 1348-2 

74 - First position of the RIC
Enclosure 1, ADC 428 

SERVICE CODES

CODE 4 5 30 31 45 46 67 68 74 75 S/A REMARKS

A A A A A A Army 

B B B B Army 

B B B Army Security Assistance Use Only6

C C C C Army 

C C C Army Contractor Use Only 

D D D D Air Force 

D D D Air Force Security Assistance Use Only7

E E E E Air Force 

E E E Air Force Contractor Use Only 

F F F F F F Air Force 

G G G G G G GSA 

H H H H Other DOD Activities Note: To designate other8

DoD Activity contractors, you 

must use Service Code H with 

G. When code HG is used, rp 

30-31 or 45-46 will contain 

the HG code, as appropriate9

. 

H H G H G Other DOD Activity 

Contractors 

H H H Not Assigned 

I I Not Assigned Missile 

Defense Agency 

Security Assistance Use Only 

J J Air Force On Base Use Only 

J J Air Force 

J J J J Not Assigned 

K K K K Not Assigned 

K K K Marine Corps Security Assistance Use 

Only10

L L L Not Assigned 

L L L L Marine Corps Contractor Use Only 

M M M M M M Marine Corps 

N N N N N N Navy 

                                                           

6

On Grant Aid requisitions, rp 45 will contain S/A Code Y.

7

See Footnote 4.

8

Procedures to control access to DoD material inventories by defense contractors last reported as not implemented by 

USA (Retail). Refer to AMCL 1A.

9

 See Footnote 2. 

10See Footnote 4.
Enclosure 1, ADC 428 

CODE 4 5 30 31 45 46 67 68 74 75 S/A REMARKS

O Not Assigned 

P P P P Navy 

P P P Navy Security Assistance Use 

Only11

Q Q Q Q Navy 

Q Q Q Navy Contractor Use Only 

R R R R R R Navy 

S S S S S S DLA 

 S D S D DLA Contractor Use Only 

T T T T DLA 

T T DLA Security Assistance Use 

Only12

T T (See Footnote13 ) 

U U U U Not Assigned 

U U U DLA Contractor Use Only 

V V NASA 

V V V Navy 

V V V Not Assigned 

W W W W W W Army 

X Not Assigned Reserved (Used internally by DLA 

Transaction Services) 

Y Reserved (Nonsignificant) 

Z Z Z Z Z Z Z Coast Guard 

Z Z 0 Z 0 Coast Guard Contractor Use Only 

CODE 4 5 30 31 45 46 67 68 74 75 S/A REMARKS

FEDSTRIP CIVIL AGENCY CODES14

NUMBER OF CHARACTERS: Two. 

TYPE OF CODE: Numeric, Numeric.

EXPLANATION: Identifies civil agencies under FEDSTRIP 

RECORD POSITION(S): 30-31 and 45-46. 

                                                           

11See Footnote 4.

12See Footnote 4.

13S/A Code T entered in rp 45 may be used for any FMS country Defense organization which is not designated as an element of that 

country’s Army, Navy, Air Force, or Marine Corps.

14See Footnote 1.
Enclosure 1, ADC 428 

SPECIAL PROGRAM ACTIVITY CODES15

NUMBER OF CHARACTERS: Two. 

TYPE OF CODE: First-position Numeric, Second-position Alpha. 

EXPLANATION: Identifies special program activities that are neither DoD or 

Federal Agencies 

RECORD POSITION(S): 30-31 and 45-46. 

                                                           

15 Request for Implementation Date for Approved DLMS Change (ADC) 384, Special Programs for Non-DoD/Non-Federal 

Agency Requisitioners and Administrative Change for Contractor DoDAACs, January 18, 2011 
Enclosure 2, ADC 428 

Enclosure 2, Comment Resolution

 Originator Concurrence/Comment Response 

1. Army HQDA DCS G-44(s) Concurs with comment: 

While GCSS-Army will undoubtedly interface 

with Security Cooperation Enterprise System 

(SCES) some Supply Support Activities will be 

called upon to make FMS issues. As potential 

future users of GCSS-Army and the addition of 

a "new" RIC 'HB1', this data may have to be 

loaded within the Force Element (FE) structure 

as a recognized MRP/SLOC area. Army will 

be able to provide further impact after the 

GCSS-Army IOT&E. 

Noted. 

2. Army 

AMSACPO-LS-PM 

COMMENT #1: 

Re 4.c.(2)(a): Isn't the "first letter designation 

of MAPAC" rp45? To my thinking the 

MAPAD is unaffected by adding MDA as an 

I/A and making "I" a valid FMS service code 

in rp30. 

Re 4.c.(2)(b): I assume this paragraph refers to 

CISIL. Is there any reason it can't be stated 

explicitly? 

Lastly, there are several references to Army 

and DLA requisitions with MDA document 

numbers. That would be a tremendous impact 

on CISIL. My guess is that it's just a matter of 

time before the politics makes this a reality. 

COMMENT #2: 

I have attended several meetings/TELCONs 

with MDA/DSCA and have been told that ALL 

MDA managed material provided under a case 

will come from MDA procurement, including 

those items normally considered as WCF. Any 

Army/DLA material required to support any 

MDA cases (excluding AE-B-UAF) will be 

furnished on a companion Army case; 

consequently, I do not understand the last 

sentence of para 5, "Ultimately, other 

Components, particularly Army and DLA will 

have a requirement to satisfy requisitions using 

the new S/A code "I" in the document 

number." 

MILSTRIP Administrator: In response to 

the first two issues in comment 1: 

(1) Concur, there is problem with the 

current wording for this paragraph. The 

"I" would only appear in the document 

number and not in the constructed 

MAPAC. Revised to read: DLA 

Transaction Services and supporting 

systems need to add the letter “I” to all 

transaction edits intended to recognize 

FMS which are currently based on "B, D, 

K, P, and T" in the first position of the 

document number. 

(2) More detail added. Revised to read: 

DLA Transaction Services will route all 

FMS requisitions to the MDA ILCO, if 

not received from the MDA ILCO. 

Pending implementation of the Security 

Cooperation Enterprise Solution (SCES), 

all FMS requisitions with document 

numbers beginning with "I" will be 

processed through the Army ILCO 

system, Centralized Integrated System for 

International Logistics (CISIL). 

MDA response to comment 2: 

Currently there are no spare parts or any 

parts on an MDA case that will not be 

coming from a vendor. The systems are 

not currently fielded and all parts come 

from the vendor. Any Army items will be 
Enclosure 2, ADC 428 

Currently, none of the current systems, e.g., 

DSAMS, CISIL, DIFS, PBAS nor 

1200 System can prepare/execute a case with 

multiple IA codes. 

on an Army LOA. 

However, in the future there may be a 

potential for parts from DLA and/or 

Army. The system will potentially be 

fielded in the Army but discussions are 

still ongoing as to what organization will 

control the equipment. I don’t expect that 

this will occur before SCES is 

implemented but I cannot say it will 

definitely not happen. 

Army FMS: Based on the response from 

MDA and the correction/enhancement of 

the DLMS Change documentation, the 

Army now concurs on this PDC. 

3. Navy The Navy concurs with PDC446 as written and 

submits no additional changes or amendments. 

Noted. 

4. Air Force Concurs. Noted. 

5. Marine Corps Concurs. Noted. 

6. DLA DLA concurs, with one minor comment from 

the FMS team (see below). There will be 

system impacts that require an EBS SCR. 

In paragraph 4.C(3)(b), the sentence reads 

"Modifiers are rejected if the Country FMS 

Offer/Release Option or Freight Forwarder 

Code is modified when the requisition is not 

FMS." I agree with that because there 

shouldn't be a Country FMS Offer/Release 

Option or a FF code on a non-FMS order. But 

is the sentence in there to be a further example? 

It just seems out of place. 

Noted. 

This business rule was just provided as 

one example of the type of rules that 

require a distinction between FMS and 

non-FMS. We did not intent to delineate 

all the rules and provided blanket 

statement regarding recognition of the “I” 

in the first position of the document 

number as denoting FMS. 

7. DLA 

Information 

Operations – 

Distribution 

Standard 

System (DSS) 

DSS currently has the "I" listed in the "other" 

category not associated to a Service, and if we 

had to associate the "I" to MDA and 

"Other" it poses a problem and a SCR will be 

required. 

A systems change request (SCR) will be 

required as every single program that reacts on 

the service code of a MRO must be evaluated. 

This then applies to most of the functional 

areas. 

The “I” will only be used for FMS 

requisitions where the “I “will identify the 

implementing agency. 

There is no near-term impact on the DSS. 

Initially, all support for the MDA case(s) 

will be provided by vendors. 

8. DLA 

Transaction 

Services - 

WebSDR 

We will have some minor routing and/or 

metrics designator updates for the new 

Document Numbers starting with an "I" 

character. 

Noted. 

9. DLA 

Management 

Standards 

Potential risk identified in the proposal: "The 

exclusive use of S/A Code "I" for MDA may 

result in inappropriate transparency of support 

and transport of equipment/parts relevant 

MDA response: 

MDA does not consider this a valid 

concern. When an Letter of Request 

(LOR) is received, it will require a 
Enclosure 2, ADC 428 

weapon systems." congressional notification package (36(b)) 

be prepared. Once that is approved by 

congress, it is unclassified and published 

in the congressional record. It is available 

for the public to see. The requisitions will 

be in CISIL and are unclassified. It is 

understood that the transactions will flow 

via DAAS and that all shipping 

documentation will contain the document 

numbers. The FMS cases are for radars 

and launchers, in addition to missiles. 

Also spare part packages from the 

contractors and technical manuals will be 

requisitioned. Anything that falls into the 

category of arms, ammunition, and 

explosives (AA&E) or sensitive 

equipment will be shipped via Defense 

Transportation System (DTS) or approved 

cleared country freight forwarders. All of 

these issues were considered prior to 

requesting approval to sell to foreign 

countries. Therefore, inappropriate 

transparency is not a valid concern. 

10 IUID/ 

WAWF 

The DPAP IUID/WAWF Team does not have 

any comments. 

Noted. 

11 USTRANSCOM Abstains. Noted. 

Comments subsequent to ADC 428 publication: 

12 DLA 

Transaction 

Services 

(1) Para 4.b.(2) states MDA will be the source 

of supply for the equipment and parts. Will 

they generate any kind of billing as would 

normally occur? Where would these bills go? 

Will there be a new entry in MILSBILLS 

AP1.2 for Service Code "I" that will relate a 

Fund Code entry to HQ0147? 

(2) Para 4.b.(3) states there will be a RIC and 

DoDAAC established for MDA but does not 

mention Distribution Code. Don't know that 

this is a necessity but all other ILCOs use 

Distribution Code in transactions I assume to 

ensure they receive all related status. 

Para 4.c(1) says MDA will be entering "I" 

series MAPACS in the MAPAD. That isn't 

correct is it ? "I" is for use in RP 30 only, US 

Service, not RP 45 which would be the incountry Service. The MAPACs are 

constructed using the in-country Service code, 

not the US Service code so there would not be 

(1) The ADC Addendum has been updated 

to reflect that new Fund Codes will be 

required if interfund billing is to be 

employed. Further details are not 

available at this time. 

(2) This was not previously discussed, but 

it is correct that a new Distribution Code 

must be assigned so that CISIL will 

receive copies of supply and shipment 

status. The ADC addendum has been 

updated to include a requirement for DLA 

Transaction Services to update the 

Distribution Code Table for MDA 

Distribution Code B. 

(3) When correcting the wording from the 

PDC, this same issue was corrected 

elsewhere, but this paragraph was missed. 

It is correct that there are no “I” series 

MAPACs, only Service/Agency Code “I” 

document numbers. 
Enclosure 2, ADC 428 

any "I" MAPACs ? 

Para4.c.(2)(b) states that "Pending 

implementation of the Security Cooperation 

Enterprise Solution (SCES), all FMS 

requisitions with document numbers beginning 

with "I" will be processed through the Army 

ILCO system, Centralized Integrated System 

for International Logistics (CISIL)." Assume 

this means there will never actually be any 

unique MDA ILCO transaction interface but 

there will be a transaction interface to receive 

and actually fill the requisitions and generate 

status, bills (?). 

(4) Correct, there is no unique ILCO 

interface. The Army CISIL will be the 

ILCO system until SCES is deployed. 

Requisitions processed from CISIL will be 

passed to MDA. 
DEFENSE SECURITY COOPERATION AGENCY 

201 12TH STREET SOUTH, STE 203 

ARLINGTON, VA 22202-5408 MAR i A ?!111 

MEMORANDUM FOR THE DEPUTY UNDER SECRETARY OF THE AIR FORCE 

FOR INTERNATIONAL AFFAIRS 

DEPUTY ASSISTANT SECRETARY OF THE ARMY 

FOR DEFENSE EXPORTS AND COOPERATION 

DEPUTY ASSISTANT SECRETARY OF THE NAVY 

FOR INTERNATIONAL PROGRAMS 

DIRECTOR, DEFENSE CONTRACT MANAGEMENT 

AGENCY 

DIRECTOR FOR SECURITY ASSISTANCE, DEFENSE 

FINANCE AND ACCOUNTING SERVICE 

INDIANAPOLIS OPERATIONS 

DIRECTOR, DEFENSE INFORMATION SYSTEMS 

AGENCY 

DIRECTOR, DEFENSE LOGISTICS AGENCY 

DIRECTOR, DEFENSE LOGISTICS INFORMATION 

SERVICE 

DIRECTOR, DEFENSE REUTILIZA TION AND 

MARKETING SERVICE 

DIRECTOR, DEFENSE THREAT REDUCTION 

AGENCY 

DIRECTOR, NATIONAL GEOSPATIALINTELLIGENCE AGENCY 

DEPUTY DIRECTOR FOR INFORMATION 

ASSURANCE, NATIONAL SECURITY AGENCY 

SUBJECT: 	 Revised List ofImplementing Agencies (lAs) in Chapter 5, Table C5.T2. ofthe 

Security Assistance Management Manual (SAMM), DSCA Policy 11-14, [SAMM 

E-Change 182] 

This memorandum updates Chapter 5, Table C5.T2., ofthe SAMM by adding an IA code for 

the Missile Defense Agency (MDA) to the Foreign Military Sales (FMS) Terminal High Altitude 

Area Defense (THAAD) program. MDA will be designated as the IA for the FMS THAAD 

program once all requirements identified in the tripartite Memorandum of Understanding among 

the Army, MDA, and DSCA, dated June 23, 2010, have been satisfied. 

Effective immediately, Chapter 5 ofthe SAMM is updated as attached. This change will be 

included in the automated version ofthe SAMM found on the DSCA Web page, 
www.dsca.mil. as SAMM E-Change 182. If you have any questions concerning the attached 

guidance, please contact Mr. Kent Bell, DSCA-STRJPOL, kent.bell@dsca.mil, (703) 604-6612. 

Attachment: 

As stated 

cc: 

STA TEIPM-RSAT 

AFRICOM 

CENTCOM 

EUCOM 

JFCOM 

NORTHCOM 

PACOM 

SOCOM 

SOUTHCOM 

TRANSCOM 

USASAC 

SATFA 

TRADOC 

NAVICP 

NETSAFA 

AFSAC 

AFSAT 

DISAM 

~~ Scott R. Schless 


Principal Director 


For Strategy 

SECURITY ASSISTANCE MANAGEMENT MANUAL (SAMM), E-CHANGE 182

REVISED LIST OF IMPLEMENTING AGENCIES IN CHAPTER 5, TABLE C5.T2.

Revise Table C5.T2. of the SAMM by adding the following information.

Table C5.T2. Implementing Agencies Authorized to Receive Letters of Request (LORs)

Implementing Agency Purpose Address

Name Code

Missile 

Defense 

Agency

I

Action address for all applicable LORs 

related to the FMS THAAD Program, or 

the AN/TPY-2 Radar System

Missile Defense Agency

ATTN: LOR In-Box

7100 Defense Pentagon

Washington, DC 20301-7100

The following additional codes are provided for reference. These new codes will be used 

to support cases developed and managed by MDA. All pertinent databases should be updated 

with the following codes prior to the development of any LOAs for the FMS THAAD Program 

or AN/TPY-2 Radar System.

Description Code

A. Routing Identifier Code (RIC): HB1

B. Delivery Reporting Code: 9

C. Accounting Classification Code: 97-11X8242.00ON

D. MDA Case Manager Code: I

E. MDA Line Manager Code: I

F. Department of Defense Activity Address Code (DODAAC): HQ0147

G. Defense Finance Integrated System (DIFS) Manager/Command Code: 11

H. DIFS Monitor Code: 9

I. Operator Agency Code: BM

J. Defense Security Assistance Management System (DSAMS) Activity Identifier: MDA

K. Change Originator Code: I
Enclosure 3, ADC 428 

Enclosure 3, Revised List of Implementing Agencies (lAs) in Chapter 5, Table C5.T2. of the Security 

Assistance Management Manual (SAMM), DSCA Policy 11-14, [SAMM E-Change 182] 

(see PDF file)