*DLM 4000.25, Volume 6, June 16, 2015*

*Change 4*

**C3. CHAPTER 3.**

**MILITARY ASSISTANCE PROGRAM ADDRESS DIRECTORY**

C3.1.  GENERAL

	C3.1.1.  Purpose.  This chapter establishes information requirements for the Military Assistance Program Address Directory (MAPAD).  This chapter prescribes the standards to establish, maintain, publish, and disseminate address data to requiring Military Service organizations, Federal agencies, foreign country representatives, freight forwarders, and commercial firms under DoD contracts who are engaged in supply and/or shipment of materiel applicable to the Security Assistance Program (SAP), including Foreign Military Sales (FMS) and Grant Aid programs.

	C3.1.2.  Assignment.  The Military Assistance Program Address Code (MAPAC) is a six position code that uniquely identifies a program or activity.  MAPACs are stored in the MAPAD database. Changes and additions to MAPAD are made by the Service International Logistics Control Office (ILCO) Central Service Points (CSPs).

	C3.1.3.  General Architecture.  The MAPAD architecture provides the capability to control, maintain, and provide access to the most accurate and current data related to MAPACs in near real-time.  This is accomplished by using a database of codes and address data maintained and available twenty-four hours per day, seven days per week at DAAS.

		C3.1.3.1.  Functional Architecture.  Defense Logistics Management Standards is the MAPAD System Administrator, and is responsible for ensuring that the MAPAD directory meets the requirements of authorized MAPAD users.  DAAS is the MAPAD Central Control Point, and is responsible for meeting the requirements of the MAPAD System Administrator and for maintaining the hardware, software, and help desk resources to ensure MAPAD users' operational requirements are met.  The ILCO CSPs are responsible for ensuring the accuracy and currency of the MAPAD data for their MAPACs.  The ILCO CSPs can, if they choose, establish MAPAD Monitors, delegating portions of their responsibilities (defined in Section C3.3 ACCESS) for review and approval of MAPAD maintenance actions; however, the ILCO CSPs are ultimately responsible for the accuracy and currency of the data pertaining to their MAPACs.

		C3.1.3.2.  Technical Architecture

			C3.1.3.2.1.  MAPAD Data Maintenance.  The ILCO CSPs or their designated ILCO CSP Monitors update the MAPAD via the MAPAD Web update application.  This applies only to the directory entries for which the ILCO CSP is responsible and authorized to update.  All ILCO CSPs shall use the DAAS MAPAD Web maintenance application to perform maintenance actions.  The MAPAD Web maintenance application ensures that data validation is consistent, and that completed maintenance actions update a single authoritative source database at DAAS in near real-time.  Access controls are built into the technical architecture to control who and what can be updated based on user identification (ID) and level of access.  Access Levels are defined in Section C3.3 ACCESS.

			C3.1.3.2.2.  Database Structure.  The MAPAD database structure easily supports the addition of new data types as requirements dictate.

			C3.1.3.2.3.  MAPAD Application System Access.  The MAPAD authoritative source database is available 24 hours per day, 7 days per week.  Application systems requiring access to MAPAD data to support their processing have three options. 

				C3.1.3.2.1.1.  Database Replication.  Database replication can be provided for the application, so that the application has near real-time access to a copy of the authoritative source.  Through the use of a replication process maintained by DAAS, the replicated copy is constantly synchronized with the authoritative source database.  

				C3.1.3.2.1.2.  Direct Connect Access.  Direct connect access to the authoritative source database can be established.  Both of the above access methods ensure that the application is always using the exact same data as that contained on the MAPAD authoritative source database.  Components who desire near real-time access can establish a replication link to the MAPAD by contacting DAAS.  

				C3.1.3.2.1.3.  Batch Processing.  The least preferred, option is batch processing; however, DAAS shall continue to support batch transaction processing for the foreseeable future.  The goal, however, is to encourage all users of the MAPAD to switch to real-time replication processing (if possible).

	C3.1.4.  Applicability and Scope.  This is applicable to the Army, Navy, Air Force, Marine Corps, General Services Administration (GSA), Defense Logistics Agency (DLA), Missile Defense Agency  and other activities that have agreed to participate in the system (hereinafter referred to as Components).  Also, this directory applies to DAAS, to commercial organizations that enter into materiel and service contracts with DoD, and activities of other Federal Agencies that maintain logistics support agreements with the Department of Defense.

C3.2.  POLICY.  DoDI 4140.01, “DoD Supply Chain Materiel Management Policy,” December 14, 2011 and DoD 4140.1-R, “DoD Supply Chain Materiel Management Regulation,” May 23, 2003 provide policies and governing procedures for this volume.

C3.3.  MAPAD ACCESS

	C3.3.1.  User Access.  There are multiple levels of access governed by the roles of the user.  The MAPAD System Administrator (Defense Logistics Management Standards) shall set the policy governing access, and DAAS shall maintain the MAPAD System access controls.  All update access is Public Key Infrastructure (PKI) controlled.

	C3.3.2.  MAPAD System Access Requests.  DAAS provides a System Access Request (SAR) Web screen for potential users to request access. This screen requests information regarding the type of access required (drop down list), information about the requestor (fill in the blanks), need for access (drop down), and Component affiliation (drop down), and requests that they enter and verify their desired password (fill in blanks).  Access also requires a signed letter of appointment as a CSP, which may be forwarded via email to DAAS and the MAPAD System Administrator. Upon approval, DAAS shall send an email back to the requestor notifying the requestor of the approval or denial.  If access is granted, DAAS shall send two separate emails back to the requestor: one contains the user ID, and the other is for the password.  The user ID and password are only used to register a common access card (CAC) for PKI control.  Once the CAC is registered, all access shall be restricted to CAC/PKI access.

	C3.3.3.  Database Profiles.  The application server provides a database profile of all users with access by access level and maintains statistics on the number of accesses and types of access (update, query, download) by user.  The application server also maintains data on attempted unauthorized access. 

	C3.3.4.  Access Levels and Authorities.

		C3.3.4.1.  System Administration Level.  This highest level of access is provided only to the MAPAD System Administrator and DAAS.  They shall have access to all data and shall be able to download any information in the data base.  They shall also have access to all user profiles and usage data.

		C3.3.4.2.  Component International Logistics Control Office Central Service Point Level.  This level of access is granted to the individual(s) designated in writing by each DoD Component as its ILCO CSP(s).  The letter of designation shall be provided to DAAS, with a copy to the MAPAD System Administrator.  The MAPAD contains a field called “Sponsored Service” indicator, which restricts who can update a particular MAPAC.  If the Sponsored Service indicator is present, access is restricted to users in the same Component area as the Sponsored Service (e.g., the Army ILCO CSP shall not be able to update a MAPAC with the Sponsored Service indicator set to the Navy).  ILCO CSPs set the Sponsored Service indicator.  The ILCO CSP also has access to all data relating to the user profiles and usage data for the users affiliated with the DoD Component for which they are responsible.

		C3.3.4.3.  DoD Component Monitors.  Component level ILCO CSPs can delegate and or subdivide file maintenance responsibilities for their respective MAPACs.  A maximum of 20 delegations or Monitors per ILCO CSP are allowed.  Each ILCO CSP must identify to the MAPAD System Administrator and DAAS the individuals to whom sub delegations are being made and the MAPACs for which each is responsible in the MAPAD.  The user ID shall be structured such that, when an ILCO CSP or their designated Monitor logs into the system, the system recognizes the ILCO CSP or Monitor, the MAPACs, and related information for which that ILCO CSP or Monitor has responsibility.  The ILCO CSP or Monitor shall have the ability to access all information in the database and can update any information for the Component for which they have been assigned responsibility by their ILCO CSP.  ILCO CSPs or Monitors shall not be able to update information on other Component MAPACs, or MAPACs assigned to another ILCO CSP or Monitor within their Component.

		C3.3.4.4.  General Access Level.  This level provides user access to view any general information in the database via the Defense Automatic Addressing System Center Inquiry (DAASINQ) query program for a specific MAPAC.  Additional MAPAD information and file download capability is available by SAR/PKI access via DAAS enhanced DAASINQ (eDAASINQ).

C3.4.  RESPONSIBILITIES

	C3.4.1.  The DoD MAPAD System Administrator is responsible for chairing the MAPAD Process Review Committee (PRC) and administering the MAPAD system under the policy guidance of the Assistant Secretary of Defense, Logistics & Materiel Readiness (ASD(L&MR)) as outlined in Volume 1, Chapter 1 of DLM 4000.25, Defense Logistics Management Standards (DLMS) Manual”.

	C3.4.1.1 The DoD MAPAD System Administrator shall ensure that Continental U.S. (CONUS) addresses are authorized by the Defense Security Service (DSS) to receive/process materiel/documents classified SECRET/CONFIDENTIAL.  The procedures are as follows:

		C.3.4.1.1.1. The country representative shall submit a clearance request for any activity that has been selected to receive/process materiel/documents classified SECRET/CONFIDENTIAL for its FMS cases via electronic PDF to: MAPADHQ@DLA.MIL. U.S. Government facilities and foreign government property (e.g., embassies and missions) are exempt from actual security clearance inspection, but a request for MAPAD address input must be submitted.

				C.3.4.1.1.2. The clearance request shall be in writing and shall include the full name and address of the selected activity. The letter shall be scanned as a PDF file and addressed to:

Defense Logistics Management Standards, J627

ATTN MAPAD Administrator, ROOM 1650

8725 John J Kingman Road 

###### Fort Belvoir VA 22060-6217

C.3.4.1.1.3. The DoD MAPAD System Administrator shall submit the request to the Defense Security Service via email to OCC.Facilities@dss.mil with a copy to the ILCOs.  

C.3.4.1.1.4. Contact information for Defense Security Service (DSS) is: OCC.Facilities@dss.mil

Defense Security Service, ISFO

Facility Clearance Division (IOP)

27130 Telegraph Road

Quantico, VA 22134-2253

571-305-6642

C.3.4.1.1.5. The DSS shall conduct a security clearance survey in accordance with the requirements set forth in DoDM 5200.01, “DoD Information Security Program,” February 24, 2012, DoD 5200.2-R “Personnel Security Program,” February 23, 1996 and DoD 5200.8-R, “Physical Security Program,”  May 27, 2009.

C.3.4.1.1.6. When DSS determines that a freight forwarder (or other intended CONUS recipient) has the capability to receive and store materiel classified CONFIDENTIAL/SECRET, the country representative shall be notified directly by DSS of their findings with information copies to the DoD MAPAD System Administrator and the ILCOs.  The correspondence directing publication of the addresses shall cite the letter from the DSS as authority.  

C.3.4.1.1.7. When DSS determines that a freight forwarder (or other intended CONUS recipient) cannot be cleared or has been found incapable of safeguarding classified shipments; DSS shall notify the DoD MAPAD Administrator and all ILCOs via email. The requestor for clearance shall also receive a copy of the letter.

C.3.4.1.1.8. For a freight forwarder (or other intended recipient) to receive classified shipments for more than one country, a separate request must be submitted for each individual country.  These requests shall be submitted and processed as outlined above.

	C3.4.2.  DAAS is responsible for program execution.  Tasks include (but are not limited to):

		C3.4.2.1.  Hardware and software acquisition

		C3.4.2.2.  Technical design and database maintenance

		C3.4.2.3.  Testing and system interface connectivity

		C3.4.2.4.  Hardware and software maintenance and refresh

	C3.4.3.  Heads of participating DoD Components shall designate in writing a primary and an alternate ILCO CSP representative for the MAPAD.  The letter of designation shall be provided to DAAS, with a copy to the MAPAD System Administrator.

	C3.4.4.  The DoD ILCO CSPs shall:

		C3.4.4.1.  Ensure continuous liaison with the DoD MAPAD System Administrator and other DoD Components. 

		C3.4.4.2.  Assist country representatives in preparing letter requests for materiel and documents classified SECRET/CONFIDENTIAL by identifying their applicable MAPACs.. 

		C3.4.4.3.  The ILCO CSP shall enter the applicable MAPAC data via the MAPAD Web entry, except for data related to Type Address Code (TAC) A, B, C, or D which will be entered by DAAS.

		C3.4.4.4.  The ILCO CSPs are responsible for ensuring the accuracy and currency of the MAPAD data for their assigned MAPACs and for maintaining records to support the proper assignment, modification or deletion of each MAPAC.  ILCO CSPs shall validate MAPAD addresses on a continual basis.  Each Component shall establish internal MAPAD validation procedures.  Requests for changes to the MAPAD may be received from the following sources in addition to country representatives:

			C3.4.4.4.1.  Freight Forwarder.  A Freight Forwarder may submit requests to the ILCO CSP for a change of address to the existing addresses for receipt of materiel/documentation, except TAC A, B, C, or D addresses, which must have prior approval by the DSS and the country representative. 

			C3.4.4.4.2.  U.S. Government Representatives Located in the Continental United States/Overseas 

				C3.4.4.4.2.1.  Authorized U.S. Government representatives located overseas may submit a request for addition, revision, and/or deletion of any MAPAD address, provided they indicate that the request has been coordinated with the country representative.

				C3.4.4.4.2.2.  Authorized U.S. Government representatives may process a request for addition, revision, and/or deletion for Air/Army Post Office/Fleet Post Office/Diplomatic Post Office (APO/FPO/DPO) addresses and addresses to receive classified freight shipments without stating that the request has been coordinated with the country representative.

				C3.4.4.4.2.3.  ILCO CSPs may process a request for addition, revision, and/or deletion of special project addresses, (e.g., assembly/consolidated shipment point addresses) without coordination with the customer country or authorized U.S. Government representative.

				C3.4.4.4.2.4.  ILCO CSPs may process requests for deletion of MAPACs after the following procedures have been used to close all their cases associated with the MAPAC:

					C3.4.4.4.2.4.1.  Query the country to validate the MAPAC.  (Note:  The query must be approved by the Services' senior country desk officer.)

					C3.4.4.4.2.4.2.  After three months, if there is no response from the country, send a second follow up to the country, advising that no response shall mean an automatic deletion from the MAPAD.

		C3.4.4.5.  Additions, revisions, and deletions to the master MAPAD for Grant Aid addresses shall be made only by the responsible ILCO CSP following a request from an authorized U.S. Government representative or the DoD Component.  

C3.5.  SYSTEM MAINTENANCE

	C3.5.1.  Revisions to the MAPAD result from a release or change to DoD instructions/directives, from policy changes, and by recommendation of the DoD Components.

	C3.5.2.  Recommended changes to the administration and support of the MAPAD are handled through the documented DLMS change process found in Volume 1 of this manual.

C3.6.  USE OF MAPAC IN MILITARY STANDARD REQUISITIONING AND ISSUE PROCEDURES

	C3.6.1.  Activities that prepare FMS and Grant Aid requisitions must ensure that ship-to/mark-for addresses are published in the MAPAD before requisitions are entered into the supply system.  Conversely, addresses should be deleted only after all logistics transactions have been completed, or a cross-reference address (in the TAC 9) has been provided.  When shipping Activities are unable to select an address or when clarification and/or identification of specific ship-to/mark-for addresses is required, the appropriate freight forwarder/Component Security Assistance office shall provide assistance.

	C3.6.2.  Instructions for construction and use of MAPACs for FMS shipments are contained in Section C3.10.

	C3.6.3.  Instructions for construction and use of MAPACs for Grant Aid shipments are contained in Section C3.22.

C3.7.  COMPOSITION OF CLEAR TEXT ADDRESSES

	C3.7.1.  General applications are as follows:

		C3.7.1.1.  Clear text addresses for each assigned MAPAC shall be constructed to ensure timely and efficient delivery of materiel and documentation in accordance with the negotiated delivery conditions of the sales agreement for all FMS MAPACs and Grant Aid agreements.

		C3.7.1.2.  Each ship-to address shall be limited to a maximum of five lines and 35 or fewer positions per line.  This restriction is necessary to accommodate the space limitations on supply documents, transportation documents, labels, and for standardization in automated data processing (ADP) programs.  

		C3.7.1.3.  Addresses cannot contain a tilde (~).  Special characters such as ampersand (&) and parentheses are acceptable. Use of the tilde is restricted because it is used by DAAS as a delimiter in transactions.  

		C3.7.1.4.  Abbreviations shall be used only when they are essential to movement of materiel/documents and can be recognized by the involved Services/Agencies, contractors, or foreign government representatives. 

		C3.7.1.5.  Domestic mail addresses shall be constructed to include activity name, post office box number, street address, city, state, and ZIP + four code.  When the address requires additional information (e.g., exceptions), special instructions shall be included in the introduction to the appropriate country address listing.  However, other information (e.g., attention lines) may be included in any address line except the street address, city, state, or ZIP + four code line.  Post Office box numbers shall not be accepted for ship to addresses without Special Instruction Indicators (SIIs).

		C3.7.1.6.  Use of APO/FPO/DPO addresses must be specifically authorized by DoD Letter of Offer and Acceptance.  Additionally, their use requires the written approval of the addressee, stating that they shall accept full responsibility for receiving materiel/documentation.  APO/FPO/DPO addresses shall be constructed to include activity name, office symbol or code, post office box number, APO/FPO/DPO number and Zip + four code.  When the address requires additional information (e.g., exceptions), special instructions shall be included in the introduction to the appropriate country address listing.  Other information (e.g., attention lines) may be included in any address except the APO/FPO/DPO line. 

		C3.7.1.7.  International mail addresses are not to be used in shipping FMS or Grant Aid items unless specifically authorized by DoD Letter of Offer and Acceptance. 

		C3.7.1.8.  The Department of State Pouch Service is no longer allowed to be used for the movement of materiel, including small parcels.

		C3.7.1.9.  For deletion of a MAPAC, all logistics transactions containing the deleted MAPAC must have been completed or instructions for processing logistics transactions still in the system must be provided to the ILCO CSP.  Accordingly, one of the following must be accomplished: 

			C3.7.1.9.1.  When addresses for another MAPAC are to be used for processing requisitions, the deleted clear text addresses shall be replaced with an address reference that reads "Deleted.  Use MAPAC (insert appropriate code) addresses."  This shall be a TAC 9 and shall remain in the MAPAD for five years.  Also, the replacement MAPAC shall be entered in the cross reference field of the deleted MAPAC.

			C3.7.1.9.2.  When addresses of another MAPAC are not to be used for processing logistics transactions, special instructions indicator (SII) “S” shall be included in the directory and the clear text address field shall be blank.  Appropriate instructions for addressing outstanding transactions must be included in the special instruction portion of the address listing.

	C3.7.2.  Foreign Military Sales Address Composition

		C3.7.2.1.  Domestic freight addresses shall be constructed to include the name and address of the freight forwarder/country representative, street address, city, state, and ZIP + four code.  Other information, (e.g., attention lines) can be included on any address line other than the street address, or the city, state, and ZIP + four code lines.  Addresses containing telephone numbers shall be constructed at a request from the freight forwarder/country representative for notification by the carrier prior to delivery, subject to additional charges.  Therefore, all such entries should be closely coordinated with the country representative to determine whether prior notice and its subsequent charges are actually required.

		C3.7.2.2.  Mark-for addresses shall be constructed to provide for delivery to the ultimate consignee.

		C3.7.2.3.  When FMS shipments are to be delivered to an overseas port of debarkation or delivered to destination, the mark-for address shall be used with the Water Port of Debarkation (WPOD) or Aerial Port of Debarkation (APOD), as appropriate.  If the port of debarkation is located in a country other than the customer country, the customer must obtain approval authority from the transiting country and confirm this authority prior to MAPAD entry.  When the shipment is made to an APO/FPO/DPO address, the mark-for address should be placed on the parcel in such a way that it shall not be confused with the APO/FPO/DPO address. This will avoid the possibility of the parcel being inadvertently routed through international mail.

		C3.7.2.4.  Addresses for receipt/processing of classified mail or materiel must meet the requirement for classification of CONFIDENTIAL or SECRET as prescribed by DSS and discussed earlier. 

	C3.7.3.  Grant Aid Address

		C3.7.3.1.  When a small parcel shipment is not acceptable to the authorized U.S. Government representative located overseas, as indicated by the absence of a TAC 1 address, materiel shall be shipped to the freight address (TAC 2).

		C3.7.3.2.  An international mail address may be used when an APO/FPO/DPO does not operate but must be specifically authorized by United States Department of Defense Letter of Offer and Acceptance.

		C3.7.3.3.  The clear text address column shall normally be blank for a TAC 2 address.  The appropriate WPOD or APOD shall be used with the TAC M address for this MAPAC to consign materiel shipments.  The TAC 2 clear text address field shall contain the name and geographical location of the civil airport to be used for commercial air shipments if commercial air is authorized.  If commercial airlift is authorized, the name and location of the International Air Port is not shown in the TAC 1 or 2.  The TAC 1 and 2 shall have an “S” in the SII and the air port information shall be listed in the special instruction.  The APOD field shall contain the three-position air terminal identifier code for the airport to be used for delivery of materiel by U.S. Military aircraft.  To determine the APOD for a specific location, refer to the Scott Airlift Control Center Website (from "XOG Quick Links" select "Channel Sequence Listing".  The WPOD field shall contain the appropriate three-position water port designator code.  Valid APOD and WPOD codes are contained in the table Management Distribution System..  See “AERIAL-PORT” and “WATER-PORT” reference tables under the Master Model Compliant Reference Data section.

		C3.7.3.4.  The TAC M address shall be constructed to ensure efficient delivery of materiel after reaching the WPOD or APOD.

C3.8.  MILITARY ASSISTANCE PROGRAM ADDRESS DIRECTORY AUTOMATED FILES

	C3.8.1.  The automated MAPAD file enables automated and manually operated DoD Component Activities to be routinely informed of current changes to the master file.  To ensure that the most current information is made available to those Activities having a recurring operational requirement for the address data, all DoD Components should take full advantage of this feature.

	C3.8.2.  DoD Components requiring the automated address file for processing of documentation under the DLMS or for expeditious dissemination of data to activities with manual operations shall request the file from DAAS.  The preferred method to disseminate address data is through data replication.  DoD Components requiring the automated address file for internal use should coordinate with DAAS to replicate the MAPAD database. In the near term, batch transmissions shall be supported (see paragraphs C3.26.7 through C3.26.10. for details).  

	C3.8.3.  Transmission of batch transaction changes from DAAS to the designated DoD Component Activities shall be by electronic transmission using content indicator IHAF.  A separate transaction shall be made for each MAPAC and TAC that is to be added, revised, or deleted.  The document identifier code shall identify the action to be taken on the assigned effective/deletion date.  The transmission of batch transactions shall only be supported until replication can be established.

C3.9.  FREIGHT FORWARDER/COMPONENT SECURITY ASSISTANCE OFFICE  Problems in transportation during delivery of FMS materiel to a freight forwarder should be referred to the shipper if the materiel is moving under a prepaid Commercial Bill of Lading or Government Bill of Lading or via a prepaid small parcel carrier.  Problems with the carrier in transportation of materiel moving on a collect commercial bill of lading should be resolved between the carrier and freight forwarder.  Problems in documentation (e.g., misdirected shipments) shall be referred to the shipper.  If these problems cannot be resolved between the freight forwarder and shipper, contact the appropriate Component security assistance office in Table C3.T1.

C3.10.  FOREIGN MILITARY SALES SHIPMENT BACKGROUND AND GENERAL INSTRUCTIONS

	C3.10.1.  The FMS Program is defined as that portion of the Security Assistance Program (SA) under which the recipient provides reimbursement for defense articles and services. It is authorized by the Foreign Assistance Act of 1961, as amended and the Arms Export Control Act of 1976, as amended.  All FMS shipments are a result of a negotiated agreement between the U.S. Government and the government of the purchasing country.

	C3.10.2.  FMS requisitions are designed to be processed in the same manner as DoD logistics transactions; however, there are some instances where they will differ (e.g., construction of Military Standard Requisitioning and Issues Procedures (MILSTRIP)) requisition document numbers and the use of supplementary addresses. The following are general instructions used in shipping FMS materiel:

		C3.10.2.1.  There will be circumstances when deviations to the shipping instructions contained in the requisition are authorized.  An example of a deviation is when a shipment, originally scheduled for delivery to a freight forwarder, is redirected into the Defense Travel System (DTS) for direct delivery to an overseas location.

		C3.10.2.2.  To use the MAPAD to find in-the-clear, ship-to and mark-for addresses, both the document number and the supplementary address shall be used.  There are two very important factors to remember when constructing an MAPAC:

			C3.10.2.2.1.  The requisition numbers for FMS are not constructed the same way requisitions are constructed for the DoD Components.

			C3.10.2.2.2.  The first six positions of the document number cannot be considered to be the same as a MAPAC.

		C3.10.2.3.  Because Canada has no freight forwarders in the United States, the construction of their MAPACs is an exception to the rule.  Refer to Section C3.13. for construction of Canadian MAPACs.

		C3.10.2.4.  FMS items shall be shipped by a carrier that can provide evidence of shipment (for Supply Discrepancy Report purposes, evidence of shipment constitutes “constructive proof of delivery in compliance with DSCA 5105.38-M, “Security Assistance Management Manual (SAMM),” paragraph C6.4.10.6.

		C3.10.2.5.  Regulations, such as the Defense Federal Acquisition Regulation Supplement (DFARS) Volume III, Appendix F, Material Inspection and Receiving Report for procurement documents and independent Service requirements, mandate that the elements listed below be provided on shipping documents for use by the freight forwarder.  The freight forwarders use this information to obtain insurance, and identify the materiel for the export license.  Every effort should be made to ensure that the following information is provided on shipping documents:

			C3.10.2.5.1.  Requisition Document Number.

			C3.10.2.5.2.  FMS Case Identifier Number.

			C3.10.2.5.3.  Unit Price/Total Price.

			C3.10.2.5.4.  Quantity.

			C3.10.2.5.5.  NSN/Part Number and Description.

			C3.10.2.5.6.  Project Code (if applicable).

	C3.10.3.  Prior to selecting the appropriate address, the shipper must consider shipment size, destination, classification, type of materiel, deliver term code, and priority.

C3.11.  MILITARY ASSISTANCE PROGRAM ADDRESS DIRECTORY ADDRESS FORMAT FOR FOREIGN MILITARY SALES

	C3.11.1.  Data Elements Used To Construct MAPAD Codes For FMS.  Five data fields are required to construct a ship-to MAPAC and a mark-for MAPAC.  These data elements are taken from the requisition document number and supplementary address.  A MAPAC shall have six positions for the purpose of integrating the code into Component logistics systems.  This is accomplished by zero filling the non-significant record positions (rp).  The five data elements used to construct the FMS ship-to and mark-for MAPACs are listed below.

		C3.11.1.1.  Requisition Document Number

			C3.11.1.1.1.  The second and third position of the document number (MILSTRIP rp 31–32) shall contain the SA/FMS country/international organization codes assigned by the Defense Security Cooperation Agency. The authoritative source for these values is DSCA 5105.38-M, Chapter 4, Table C4.T2. 

			C3.11.1.1.2.  The fourth position of the document number (MILSTRIP rp 33) shall contain the mark-for code.  The alpha/numeric code indicates the final destination address of the materiel.  When the country does not identify a valid mark-for code, a numeric zero shall be shown in MILSTRIP rp 33.

		C3.11.1.2.  Supplementary Address

			C3.11.1.2.1.  The first position of the supplementary address (MILSTRIP rp 45) shall contain the code designating the customer country’s requisitioning Service. B=Army; P=Navy; D=Air Force; K=Marine Corps; T=other than Army, Navy, Air Force, or Marine Corps.  The first position of the requisition number (MILSTRIP rp 30) usually contains these same Service codes.  The difference is that rp 30 indicates the U.S. Military Service that manages or is responsible for the FMS case.  In constructing MAPACs for the ship-to and mark-for address, only the customer country’s Service Code (rp 45) shall be used.  The U.S. Service Code (rp 30) shall be used to show the appropriate freight forwarder/Service assistance office if any problems arise.  It is possible for rp’s 30 and 45 to have different Service Codes (e.g., if the requisition number begins with BATL4V and the supplementary address is DA2KBM, the shipper would use the D (customer country’s Air Force Code) from the supplementary address to construct the ship-to/mark-for MAPACs, but would contact the U.S. Army (B) for assistance, if required).

			C3.11.1.2.2.  The third position of the supplementary addresses (MILSTRIP rp 47) shall contain an alpha/numeric code to designate the customer country’s freight forwarder or designated recipient of materiel.

				C3.11.1.2.2.1.  If code X appears in the third position of the supplementary address (MILSTRIP rp 47), the shipment is to be made through the DTS to a designated address with no freight forwarder involvement.  This address can be identified by the use of rp 33 to construct the MAPAC.  Shipments moving through Air Mobility Command (AMC), Surface Deployment and Distribution Command (SDDC), and Military Sealift Command (MSC) must have an in-the-clear address or mark-for code (e.g., if movement is via AMC/SDDC/MSC and there is a numeric zero in rp 33, the in-the-clear address or customer code shall be obtained prior to shipment).  Contact your appropriate freight forwarder/Component Security Assistance Office for this information.

				C3.11.1.2.2.2.  If code W appears in the third position of the supplementary address (MILSTRIP rp 47), the shipment is to be made to an intermediate point (e.g., an item being shipped to a facility for calibration prior to final delivery to country) and the in-the-clear address shall be provided.  If the in-the-clear address is not provided, the shipper must call the freight forwarder/Service Security Assistance Office for the in-the-clear address. 

C3.12.  CONSTRUCTION OF MILITARY ASSISTANCE PROGRAM ADDRESS CODES FOR FOREIGN MILITARY SALES

	C3.12.1.  The ship-to MAPAC is constructed by taking the code in rp 45 (FMS country’s Military Service); rp 31 and rp 32 (two-digit code to identify the country/international organization (see country/activity code reference in DSCA 5105.38-M, Chapter 4, Table C4.T2); next, add two zeros (the non-significant record positions explained in C2.3.1 above) and then show rp 47 (the freight forwarder/designated representative code).

	C3.12.2.  The mark-for MAPAC is constructed by taking the code in rp 45 (FMS country's Military Service); rp 31 and rp 32 (two-digit code to identify the country/international organization; rp 33 (the code identifying the final destination of the materiel); and then adding two zeros (the non-significant record positions).

	C3.12.3.  Figure C3.F1. is an example of how the ship-to and mark-for MAPACs are constructed and the importance of the placement of the zeros for the non-significant record positions.  The MAPAC appears as a six-position code in the MAPAD.  It is constructed from selected codes located in various data fields of the requisition.  Specifically, requisition record positions 31, 32, 33, 45, 46, and 47 provide all the information necessary to construct a MAPAC when shipment is made through a freight forwarder.  A MAPAC does not exist as a discrete entity without a defining TAC.  The TAC further defines the clear-text address to be used.  Figure C3.F1. is an illustration of two FMS MAPACs constructed from applicable entries in a requisition.  This is necessary when a shipment is made through the FMS customer’s freight forwarder.  The freight forwarder’s address is represented by the ship-to MAPAC and the final destination address is represented by the mark-for MAPAC.  The numbers 30–50 in the figure indicate record positions in the MILSTRIP 80 rp transaction format.  The row of alphanumeric characters represents the applicable codes inserted in each record position by the originator of the requisition.

Figure C3.F1.  Example of Foreign MAPAC Ship-To/Mark-For

### C3.12.4.  Figure C3.F2. is a sample MAPAD address listing for Australia. Note that the clear text address is based on the use of specific TAC codes.

#### 

C3.13.  CONSTRUCTION OF CANADIAN MILITARY ASSISTANCE PROGRAM ADDRESS CODES FOR FOREIGN MILITARY SALES.  Since Canada has no CONUS freight forwarders, their ship-to and mark-for addresses are the same; therefore, shipments are made directly to the in country destination point.  Because of this, the Canadian requisition number and supplementary addresses are different to accommodate the unique construction of their MAPACs.  To construct a Canadian MAPAC, use the Service code from the first position of the supplementary address (MILSTRIP rp 45; next the second and third position of the document number (MILSTRIP rp 31 and rp 32 (two-digit Security Cooperation (SC) Customer Code); next rp 33 (zero filled); and finally, rp 46 and rp 47 from the supplementary address. (Figure C3.F3.)

C3.14.  TYPE OF ADDRESS CODES FOR FOREIGN MILITARY SALES

	C3.14.1.  The TACs used in this manual identifies the type of address to be used in the shipment/distribution of materiel/documentation.  There are 13 TACs; however, not all of the TACs shall be used in the MAPAD at the same time, but may be used in combination.  The ILCO CSP shall determine which combination of TACs is appropriate

	C3.14.2.  Table C3.T2. contains a brief description of nine of the 13 TACs.   Section C3.21. contains the four remaining TACs to be used in shipping classified materiel.

C3.15.  SPECIAL INSTRUCTION INDICATORS FOR FOREIGN MILITARY SALES

	C3.15.1.  SIIs are coded in the SII column to indicate instructions to be used in shipping materiel or sending documentation to a particular address.

	C3.15.2.  Only the SII S shall be shown in clear text.  This information is listed at the beginning of each country section.  The clear text SIIs are a means by which customer countries place their unique requirements in the MAPAD (e.g., political considerations, circumstances peculiar only to one country; a country that has negotiated their own freight rates with a carrier).  The shipper must adhere to these instructions.  The appropriate freight forwarder Service Assistance Office must be contacted if problems arise in executing the specific SII.

	C3.15.3.  SII S requires identification of applicable MAPACs and TACs with clear text special instructions, as shown in Figure C3.F4.

### 

### C3.16.  WATER AND AERIAL PORTS OF DEBARKATION CODES FOR FOREIGN MILITARY SALES.  These codes indicate the WPOD or APOD to which FMS shipments shall be sent under Delivery Term Code (DTCs) 6, 7, and 9.  The shipments shall be moved through the DTS to the in country ports.  In the case of DTCs 6 and 9, port personnel shall notify the ultimate consignee to pick up the materiel or make arrangements for delivery of the shipment to destination.  In the case of DTC 7, the U.S. Government is obligated to transport the materiel to the customer’s in country mark-for address.

### C3.17.  EFFECTIVE DATE AND DELETION DATE FOR FOREIGN MILITARY SALES.  This is a date when the MAPAC is effective and/or the date it is deleted.  The deleted record shall remain in the file for 5 years after it is deleted to allow the pipeline to be flushed.  Changes shall take effect when the current date matches the effective date.

### C3.18.  OFFER/RELEASE OPTION CODE FOR FOREIGN MILITARY SALES

### 	C3.18.1.  The MILSTRIP data elements outlined above were those elements required to construct MAPACs.  However, there are additional elements to be used in the movement of FMS materiel.  The second position of the supplementary address (MILSTRIP rp 46), is called the offer/release option code and identifies whether or not an NOA is needed prior to shipment. See section C3.21. for instructions on shipping classified materiel.

### 	C3.18.2.  If the Offer/Release Option Code is an alpha A, the shipment shall be released automatically to the freight forwarder or designated recipient of the materiel. Offer/Release Option Code A is not absolute. Offer/Release Option Code Z procedures must be followed if any unusual transportation factors apply. This includes oversize or overweight shipments, hazardous materiel shipments, classified shipments, sensitive shipments and ammunition, arms and explosives shipments, or any other factor that mandates coordinated release procedures (this does include Canada).

### 	C3.18.3.  When the Offer/Release Option Code is an alpha Y, the shipment must not be released until an NOA is forwarded to the TAC 3 address.  If a reply to the NOA is not received within 15 calendar days from the date of the notice, the shipment shall be released to the appropriate TAC 2 address with no further action by the shipper. Offer/Release Option Code Y is not absolute.  Offer/Release Option Code Z procedures must be followed if any unusual transportation factors apply. This includes oversize or overweight shipments, hazardous materiel shipments, classified shipments, sensitive shipments and ammunition, arms and explosives shipments, or any other factor that mandates coordinated release procedures (this does include Canada).

### 	C3.18.4.  When the Offer/Release Code Option is an alpha Z an NOA shall be forwarded to the TAC 3 address, or country representative if the shipment is classified.  However, the shipment must not be released until a response from the proper NOA addressee is received.  ***If an NOA response is not received within 15 calendar days of the NOA date, the shipping activity will send a follow-up to the designated NOA recipient using the same TCN.  The duplicate NOA will be annotated with the number 2 in the NOA Notice Number field to denote the second communication of the NOA and to indicate that release has been delayed due to non-response to the original NOA.  Two copies of the annotated DD Form 1348-5 (Notice of Availability/ Shipment), together with the applicable DD Form(s) 1348-1A, DD Form(s) 250, or DD Form(s) 1149 will be held as a record of the non-response to the original NOA.  If no response is received within 15 calendar days of the follow-up NOA, another follow-up will be sent with the number 3 in the NOA Notice Number field to indicate that release continues to be delayed due to non-response to the original and follow-up NOAs.  File copies will be updated to reflect the non-response and submission of a second follow-up.  Simultaneous with the second follow-up, the appropriate ILCO will be contacted (offline) for assistance and follow-up action to obtain the NOA response.  Upon receipt of the offline contact from the shipping activity, the ILCO must intervene, on behalf of the shipping activity, to obtain a response to the NOA so the open shipment action can be closed.  NOTE:  This follow-up procedure does not apply to Delivery Term Code (DTC) 8 releases.  DTC 8 releases involve materiel, usually Sensitive Arms, Ammunition and Explosives, which follow special export procedures that require more time to process than can be encompassed by the above follow-up procedure.***Note that Option Release Code Z procedures must be followed if any unusual transportation factors apply. This includes oversize or overweight shipments, hazardous materiel shipments, classified shipments, sensitive shipments and ammunition, arms and explosives shipments, or any other factor that mandates coordinated release procedures (this does include Canada).

### 	C3.18.5.  When the Offer/Release Option Code is an alpha X the United States is responsible for transportation and no NOA is required.

### C3.19.  DELIVERY TERM CODES FOR FOREIGN MILITARY SALES.  DTCs identify the Department of Defense and the purchasing country responsibility for transportation and handling costs.  A link to DTCs is contained in paragraph C3.26.3.

### C3.20.  PRIORITIES FOR FOREIGN MILITARY SALES.  FMS customer countries are assigned the same force/activity designator (F/AD) codes as the DoD Components.  The requisition priority designator shall be based upon the assigned F/AD–refer to MILSTRIP.  FMS materiel shall be transported in accordance with all the requirements and conditions of DoD 4140.1-R and DTR 4500.9-R).

### C3.21.  FOREIGN MILITARY SALES CLASSIFIED SHIPMENTS

### 	C3.21.1.  FMS classified shipments shall be moved utilizing a carrier that is authorized by SDDC to transport classified shipments.  These shipments shall be handled under all conditions and requirements governing the movement of US. Government classified materiel, DoDM 5200.01, DoD 5200.2-R, and DoD 5200.8-R. The following additional conditions apply:

		C3.21.1.1.  All DTC 4, 5, 8, C, E and H shipments of classified materiel require the full Offer Release Option Code Z process before they can be released; For example, a proper response from the NOA addressee must be received from the proper NOA addressee before shipment release.  The proper NOA addressee for shipments of classified materiel is the MAPAD listed country representative for the FMS Purchaser.

		C3.21.1.2.  Classified materiel requisitioned under DTCs 2, 3, 5, 6, 7, or 9 should be entered into the DTS for movement.

		C3.21.1.3.  There are many freight forwarders that have been identified by the DSS as authorized to receive classified materiel.  These freight forwarders are identified by the TACs A, B, C, and D.  If these TACs are not included in the freight forwarder's MAPAC, classified materiel shall not be released to that freight forwarder.

		C3.21.1.4.  Table C3.T3. shows a summary of the TACs to be used in moving classified materiel. 

		C3.21.1.5.  The shipper must send the NOA to the country representative as indicated in the appropriate country introduction page.  Shipments of classified materiel shall not be moved until the following conditions have been met:

			C3.21.1.5.1.  NOA response.

			C3.21.1.5.2.  Identification of a cleared facility.

			C3.21.1.5.3.  Identification of an authorized designated representative of that country.

### C3.22.  GRANT AID SHIPMENT BACKGROUND AND GENERAL INSTRUCTIONS

### 	C3.22.1.  The Grant Aid Program is defined as that portion of the SAP that provides defense articles and services to recipients on a non reimbursable or grant basis.  Grant Aid is authorized by the Foreign Assistance Act of 1961, as amended.

### 	C3.22.2.  The following general instructions are to be used to ship Grant Aid items:

		C3.22.2.1.  Generally, there are no freight forwarders involved in Grant Aid shipments.  DoD policy is to handle Grant Aid type shipments under DTC 9 procedures; however, DTC 7 procedures may apply depending on circumstances determined by the cognizant Combatant Commander.

		C3.22.2.2.  For Grant Aid shipments, data elements from the requisition document number and first position of the supplementary address shall be used for both the ship-to and mark-for MAPACs.

### C3.23.  DATA ELEMENTS TO CONSTRUCT MILITARY ASSISTANCE PROGRAM ADDRESS CODES FOR GRANT AID

	C3.23.1.  There are significant differences between constructing FMS and Grant Aid MAPACs.  For Grant Aid there are only three data elements in the requisition that are required to construct the MAPAC.  With Grant Aid requisitions, as with FMS, the MAPACs must contain six positions in order to be integrated into the DoD logistics systems.

	C3.23.2.  The data elements to be used to construct the ship-to/mark-for MAPACs are listed below:

		C3.23.2.1.  Requisition Document Number

			C3.23.2.1.1.  The second and third positions  of the document number (MILSTRIP rp 31–rp 32) shall contain the SC Customer Code.  

			C3.23.2.1.2.  The fourth position of the document number (MILSTRIP rp 34) shall contain the mark-for code.

		C3.23.2.2.  Supplementary Address.  Unlike FMS, the Grant Aid first position of the supplementary address shall always contain alpha code Y (MILSTRIP rp 45).  However, in locating the MAPACs in this directory, the Y code shall be converted to an X.  The first position of the requisition document number (MILSTRIP rp 30), shall still show the appropriate code to indicate the DoD Component managing the case.  These codes are:  B=Army; D=Air Force; I=Missile Defense Agency; P=Navy; K=Marine Corps; T=other than Army, Navy, Air Force, Missile Defense Agency or Marine Corps.

C3.24.  CONSTRUCTION OF MILITARY ASSISTANCE PROGRAM ADDRESS CODES FOR GRANT AID.  The ship-to/mark-for MAPAC is constructed by taking the Y code first position of the supplementary address to an X; the second and third position of the requisition document number (MILSTRIP rp 31–32) (two digit SC Customer Code); and the third position of the requisition document number (MILSTRIP rp 33) (final destination address); and then adding two zeros (non significant record positions).  Figure C3.F5. is an example of how the ship-to/mark-for MAPACs is constructed.

C3.25.  TYPE ADDRESS CODES FOR GRANT AID.  When making Grant Aid shipments, only five "type of address" codes shall be utilized as shown in Figure C3.F6.

### 

### C3.26.  SPECIAL INSTRUCTION INDICATORS FOR GRANT AID

	C3.26.1.  SIIs are coded in the SII column to indicate that instructions to be used in shipping materiel or sending documentation to a particular country. 

	C3.26.2.  Only the SII “S” shall be shown in clear text or narrative form.  This information is listed at the beginning of each country section.  The shipper must adhere to these instructions.  The appropriate freight forwarder/Service Assistance Office shall be contacted if problems arise in executing the specific SII.

### C3.27.  WATER AND AERIAL PORTS OF DEBARKATION CODES FOR GRANT AID.  Grant Aid shipments shall move through the DTS to Grant using in country ports of discharge.  DoD personnel at those ports shall notify the ultimate consignee to pick up the materiel or make arrangements for delivery of the shipment to its destination.

### C3.28.  EFFECTIVE DATE AND DELETION DATE FOR GRANT AID.  This is the date when the MAPAC is effective and/or the date it is to be deleted.  MAPACs shall remain on the MAPAD for 5 years beyond the delete date.

### C3.29.  DELIVERY TERM CODES FOR GRANT AID.  There are no DTCs that apply to Grant Aid shipments.  The U.S. Government is responsible from point of origin to delivery of materiel to port of discharge overseas.  RP 35 shall always contain a numeric zero.

### C3.30.  PRIORITIES FOR GRANT AID.  Grant Aid shipments shall be transported in accordance with the requirements and conditions of time-definite delivery (TDD) and DTR 4500.9-R.

### C3.31.  GRANT AID CLASSIFIED SHIPMENTS.  Grant Aid classified shipments shall be moved utilizing a carrier that is authorized by SDDC to transport classified shipments.  These shipments shall be handled in accordance with all conditions and requirements governing the movement of U.S. Government classified materiel in DoDM 5200.01.  Upon arrival at the overseas port the appropriate government to government transfer procedures shall be implemented.

C3.32.  CODES AND TRANSACTION FORMATS.  The MAPAD contains unique transaction formats, unique code lists, and common data element shared with MILSTRIP.  The following information is provided as supporting documentation to the MAPAD.

### 	C3.32.1.  Special Instruction Indicators.  SII “S” requires identification of applicable MAPACs and TACs with clear text special instructions, as shown in Figure C3.F4.”

### 	C3.32.2.  Type of Address Codes.  TACs designate the type of action being taken for a specific address (e.g., transmitting status, shipping information, Notice of Availability).  

### 	C3.32.3.  Delivery Term Codes.  DTCs designate DoD/purchasing country’s responsibility for transportation and handling cost.  The code designates the segments of the transportations pipeline for which the DoD is responsible during the transport of supply shipment units under FMS/Grant Aid programs. 

### 	C3.32.4.  Foreign Military Sales Military Standard Requisitioning and Issue Procedures Data Elements.  Appendix AP2.1 highlights MILSTRIP requisition document number and supplementary address data elements used to construct a valid MAPAC. 

### 	C3.32.5.  Address File.  Appendix AP2.6 Address File Identifier, identifies which MAPAD file shall be changed.

### 	C3.32.6.  Type of Address Codes.  Appendix AP2.4, Type of Address Codes, identifies transactions to logistics system(s) and specific operation to which they apply.  Appendix 3, also indicates the intended purpose and use of the transaction data (i.e., add, change or delete).

### 	C3.32.7.  Add/Change Foreign Military Sales Military Assistance Program Address Code.  Appendix AP2.7 contains the transaction formats (MA1, MA2) for Adding and Changing FMS MAPACs.

### 	C3.32.8.  Delete Foreign Military Sales Military Assistance Program Address Code.  Appendix AP2.8 contains the transaction format (MA3) for Deleting FMS MAPACs. 

### 	C3.32.9.  Add/Change Grant Aid Military Assistance Program Address Code.  Appendix AP2.9 contains the transaction formats (MA1, MA2) for Adding and Changing Grant Aid MAPACs.  

### 	C3.32.10.  Delete Grant Aid Military Assistance Program Address Code.  Appendix AP2.10 contains the transaction format (MA3) for Deleting Grant Aid MAPACs. 

### 	C3.32.11.  Security Assistance Program Service Designator.  The SAP Customer Service Designator is derived from the Service and Agency code list and is used in the first character of the MAPAC to classify the ownership of the MAPAC being defined.  Note:  The value for the SAP customer service designator also appears in the first position of the supplemental address field in the Security Assistance MILSTRIP requisition.****

C3-28

CHAPTER 3

# image1.png