ADC 428 MDA As Implementing Agency S A Code
DEFENSE LOGISTICS AGENCY HEADQUARTERS8725 JOHN J. KINGMAN ROAD.IN REPLYREFER TOFORT BELVOIR, VlRGINIA 2206().6221)627May 23, 201 IMEMORANDUM FOR SUPPLY PROCESS REVIEW COMM ITIEE MEMB ERSSUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 428,Support to Mi ssile Defense Agency (MDA) as a Foreign Military Sales (FMS)Implementing Agency (IA) and Assignment of New Service and Agency (S/A)Code " J" (Staffed as PDC 446)The anacbed cbange to DoD 4000.25-M, Defense Logist ics Management System (DLMS)and DoD 4000.25- J -M, Military Standard Requisitioning and Issue Procedures (M ILSTRJP) isappro ved for implementation. Use of the assigned Service/Agency Code ''1'' is contingen.t uponsigned MDA Foreign Military Sales case designating MDA as the implementing agency .Estimated implementation date is 1S( quarter FY 12.Addressees may direct questions to Ms. Ellen Hilert, Supply Process Review Committee Co Chair, 767-0676, DSN 427-06 76, or e-mai ]: ellen.hilert@dla.mil,orMr. Rohert Hammond,Military Assistance Program Address Directory (MAPAD) Process Review Committee Chair,703-767-2 ) 17, DSN 427-2) ) 7 or email: rohert.hammond@d)a.miL Others must contact theirComponent des ignated Finance or Suppl y Process Review Comro itlee representative.DirectorDLA Logistics Management StandardsAttachmentADC428cc:ODASD (SCI)
ADC 428Support 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-11422. FUNCTIONAL AREAS: Supply (including requisitioning and SDR)/MAPAD3. 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 SecurityAssistance Management Manual (SAMM), DSCA Policy 11-14, [SAMM E-Change 182]. Thismemorandum 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 ImplementingAgency (IA) for Foreign Military Sales related to a new weapon system and support parts. Inorder for standard logistics systems to recognize transactions associated with MDA FMS, a newService and Agency (S/A) Code to identify “MDA - Security Assistance Only” will beestablished under this change proposal. The new S/A Code will allow tracking and independentprocessing for MDA, which is currently using Army systems for support. STAFFING NOTEFOR DOD COMPONENTS: This change proposal initially impacts MDA and DLATransaction Services. However, as the weapons system program matures, management of theweapon system itself and/or support parts may transition to the Army and Defense LogisticsAgency (DLA).b. Background:(1) When a S/A Code is used to identify an FMS transaction, such as a requisition, itappears in the first position of the document number. From the value in the first position of thedocument number, it can be determined which Service or Agency is associated with the FMScase and which International Logistics Control Office (ILCO) is responsible for validating therequisition. Current S/A Code values indicating Security Assistance are "B, D, K, P, and T."Attachment, ADC 428Page 2
These values are used to trigger numerous automated system processes. DLA TransactionServices routes all FMS requisitions to the ILCO if not received from the ILCO. Validatedrequisitions submitted by the ILCO are then routed to the designated DoD Supply Source. Thisensures that all FMS requisitions are monitored and validated by the appropriate party beforebeing transmitted to the supply source.(2) There has been a determination that MDA will be an IA for selected FMS weaponsystem cases. MDA will be using Army systems for support of FMS customers until the SecurityCooperation Enterprise System (SCES) is fielded. The weapon system that MDA is supplyingunder FMS is owned by MDA, and MDA will be the source of supply for the equipment andparts through its weapon system contractor. At this time, no other DoD Components areinvolved as the DoD supply source. It is envisioned that common use parts may migrate toDLA for item management. The weapon system itself may transition to the Army as the supplysource at a future time.(3) A new Routing Identifier Code (RIC) has been established to identify MDA. It willbe used in requisitions to indicate that MDA is a supply source. The RIC value “HB1” wascreated using the H-series designation maintained by Washington Headquarters Service (WHS).The associated DoD Activity Address Code (DoDAAC) for the MDA is HQ0147. STAFFINGNOTE: The S/A Code used in a DoDAAC or RIC does not correspond to the S/A Code used inthe document number of Security Assistance transactions. The S/A Code used in thedocument number for Security Assistance transactions correlates to the implementing agency/ILCO responsible for the FMS case.c. Procedures: The following procedures are approved.(1) MDA:(a) MDA will establish an ILCO, which will be responsible for entering andmaintaining the “I” series MAPACs in the MAPAD. MDA will initiate a Performance BasedAgreement (PBA) and System Authorization Access Request (SAAR) with DLA TransactionServices to establish required interface connections. MDA will forward a letter to the MAPADAdministrator designating the MAPAD Process Review Committee Representatives withauthority to establish and maintain MDA MAPACs. MDA will assume all ILCO responsibilitiesas required under MILSTRIP/MILSTRAP, or as otherwise required. (Not all responsibilities aredelineated in this proposal.)(b) MDA Security Assistance customers will be instructed to use the “I” as the firstposition 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 DoDWebSDR or using a DLMS-compliant interface. MDA will receive Government-prepared SDRreplies (acting as intermediary for the FMS customer). If a DLMS-compliant interface is notavailable, SDR replies will be provided via encrypted email. MDA must provide an appropriateemail address for SDR distribution.Attachment, ADC 428Page 3
(d) MDA will submit additional SAARs as needed, e.g. for Logistics Reports andWebVLIPS access.(2) DLA Transaction Services:(a) DLA Transaction Services and supporting systems need to add the letter “I” to alltransaction edits intended to recognize FMS which are currently based on "B, D, K, P, and T" inthe first position of the document number.(b) DLA Transaction Services will route all FMS requisitions to the MDA ILCO, ifnot received from the MDA ILCO. Pending implementation of the Security CooperationEnterprise Solution (SCES), all FMS requisitions with document numbers beginning with "I"will be processed through the Army ILCO system, Centralized Integrated System forInternational Logistics (CISIL).(c) DLA Transaction Services will revise MILSTRIP edits that are based upon theSecurity Assistance S/A Codes. Examples are:1.Expedited Handling edits will exclude S/A Code “I” for ExpeditedHandling 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 assistancerequisitions identified by S/A “I” to the MDA ILCO.(e) DLA Transaction Services will revise internal logic for Supply DiscrepancyReports (SDRs) processing under DoD WebSDR to recognize S/A Code “I” as SecurityAssistance.(3) DoD Components(a) DoD Components will be required to recognize S/A Code “I” in the first positionof the document number as denoting “MDA - Security Assistance Only.”(b) There are many rules in Inventory Control Point (ICP) systems applicable toSecurity Assistance. For example, only materiel above the reorder point level is available forFMS issues. Modifiers are rejected if the Country FMS Offer/Release Option or FreightForwarder Code is modified when the requisition is not FMS. Logistics transfers are donedifferently for modifiers that are FMS. Denial Management Code 8 is only valid on FMS. TheMRA process contains many time frames based on whether or not the requisition is FMS. SDRtime 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 timeAttachment, ADC 428Page 4
required to complete the changes. Under the phased implementation plan, future impact maybe restricted to DLA and Army systems.(4) DLA Distribution Depots. Subsequent to transition to the Army and/or DLA assupply 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 TransactionsServices will need to be modified to ensure applicability to MDA FMS.(6) Changes to MILSTRIP manual will be made as identified in Enclosure 1, withcorresponding 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 allowMDA to function as an IA and as a source of supply. In order to identify requisitions anddelivery reporting issued by MDA and not Army, the requested changes are necessary. Withoutthe 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 satisfyrequisitions using the new S/A Code “I” in the document number.6. ADVANTAGES AND DISADVANTGESa. Advantages: These changes will support the MDA to become an FMS IA. MDA will beable to supply equipment that is owned by MDA or under contract to MDA with a correct sourceof supply identified. The delivery reporting that must go to Defense Finance and AccountingServices (DFAS) for Defense Integrated Financial System (DIFS) processing will be identifiedas initiated by MDA and not Army and will be posted to the MDA LOA. The FMS customerwill have visibility of requisitions and deliveries that are MDA and not Army. Army reports willonly 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, especiallysince special program document numbers could begin with a “1”.(2) The exclusive use of S/A Code “I” for MDA may result in inappropriate transparencyof support and transport of equipment/parts relevant weapon systems.7. IMPACT:a. DLA Transaction Services and DoD Component Systems. S/A Code “I” will nolonger be treated as an invalid value and will be designated as applicable to MDA for FMScustomer use. Applicable transaction processing rules/edits and business processes must berevised accordingly.b. The MDA Transition to an Implementing Agency Action Plan outlines applicablesystem and procedural changes for trading partners, as well as training and requirements forAttachment, ADC 428Page 5
overarching authorization to proceed. Implementation of this change is contingent uponsuccessful accomplishment of these.c. Implementation Schedule: Phased implementation beginning with DLA TransactionServices 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 ofrequisitions using the S/A Code “I" – the first FMS case is not anticipated before 1st or 2ndquarter 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 revisedby reference 3.a.e. DLMS Data. This change adds a new value for Service and Agency Code in the DLMSdictionary (LOGDRMS). There are no new DLMS data elements associated with this change.8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITHIMPLEMENTATION OF THIS CHANGE: None provided.Attachment, ADC 428Page 6
Enclosure 1AP2.2. APPENDIX 2.2SERVICE AND AGENCY1 CODESMILSTRIP SERVICE CODESNUMBER OFCHARACTERS:One or two.TYPE OF CODE:Alpha.EXPLANATION:S/A codes are designed to accommodate S/A identity in MILSTRIPdocumentation. For this purpose, these codes are used in conjunction withother 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 Form1348 series of documents. By exception, two-position combination codes usingthe authorized Service/Agency code and a specified second position areauthorized to identify contractor DoDAACs.2 FEDSTRIP provides for the useof the two position codes, defined as civil Agency codes, to be entered in rp 3031 and 45-46 of the GSA Form 1348 series of documents. The MILSTRIPService codes3 and the FEDSTRIP Agency codes4 are listed below:RECORDPOSITION(S):4, 30, 31, 45, 46, 67, and/or 74.51Refer 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 positionsof the AAC.2Combination codes authorized for USCG and DLA. Refer to ADC 319.3Mandatory usage rules for Service and Agency Codes are established for the assignment of DODActivity Address Codes (DODAACs) and Routing Identifiers (RICs). Further stratification for DODAACassignment usage rules may be found at: Link to Service Codes4See Footnote 1.5MILSTRIP record position key:4 - First position of the Routing Identifier Code (RIC)30 - First position of the Document Number31 – Second position of the Document Number45 – First position of Supplementary Address46 – Second position of Supplementary Address67 – First position of RIC for U.S. supply source preparing the DD Form 1348-1A or DD Form 1348-274 - First position of the RICEnclosure 1, ADC 428
SERVICE Air ForceFFFFFAir ForceGGGGGGGSAHHHHHGHHHIJJJJKOther DOD ActivityContractorsHIJOther DOD ActivitiesGKKSecurity Assistance Use Only7Not AssignedContractor Use OnlyNote: To designate other8DoD Activity contractors, youmust use Service Code H withG. When code HG is used, rp30-31 or 45-46 will containthe HG code, as appropriate9.Not Assigned MissileDefense AgencySecurity Assistance Use OnlyAir ForceOn Base Use OnlyAir ForceJKContractor Use OnlyAir ForceFHSecurity Assistance Use Only6Air ForceAir ForceEREMARKSArmyArmyDES/AACD75ABCEJJNot AssignedKKNot AssignedKL646CDE30BCD5Marine CorpsLLSecurity Assistance UseOnly10Not AssignedLLLLMarine CorpsMMMMMMMarine CorpsNNNNNNNavyContractor Use OnlyOn Grant Aid requisitions, rp 45 will contain S/A Code Y.7See Footnote 4.Procedures to control access to DoD material inventories by defense contractors last reported as not implemented byUSA (Retail). Refer to AMCL 1A.9See Footnote 2.10See Footnote 4.8Enclosure 1, ADC 428
RRNavySSSSSSDLASDTDLAContractor Use OnlySecurity Assistance UseOnly12(See Footnote13 )TUUUContractor Use OnlyDLATUUNot AssignedUDLAVContractor Use OnlyNASAVVVNavyVWDLATTVDTTUSSecurity Assistance UseOnly11NavyRTREMARKSNot AssignedPQS/AWWWVVNot AssignedWWArmyXNot Assigned Reserved(Used internally by DLATransaction 03031454667Z6874Coast Guard75Coast GuardContractor Use OnlyS/AREMARKSFEDSTRIP CIVIL AGENCY CODES1411NUMBER OF CHARACTERS:Two.TYPE OF CODE:Numeric, Numeric.EXPLANATION:Identifies civil agencies under FEDSTRIPRECORD POSITION(S):30-31 and 45-46.See Footnote 4.See 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 thatcountry’s Army, Navy, Air Force, or Marine Corps.14See Footnote 1.Enclosure 1, ADC 42812
SPECIAL PROGRAM ACTIVITY CODES1515NUMBER OF CHARACTERS:Two.TYPE OF CODE:First-position Numeric, Second-position Alpha.EXPLANATION:Identifies special program activities that are neither DoD orFederal AgenciesRECORD POSITION(S):30-31 and 45-46.Request for Implementation Date for Approved DLMS Change (ADC) 384, Special Programs for Non-DoD/Non-FederalAgency Requisitioners and Administrative Change for Contractor DoDAACs, January 18, 2011Enclosure 1, ADC 428
Enclosure 2, Comment ResolutionOriginator1. Army2. ArmyAMSACPO-LS-PMConcurrence/CommentHQDA DCS G-44(s) Concurs with comment:ResponseNoted.While GCSS-Army will undoubtedly interfacewith Security Cooperation Enterprise System(SCES) some Supply Support Activities will becalled upon to make FMS issues. As potentialfuture users of GCSS-Army and the addition ofa "new" RIC 'HB1', this data may have to beloaded within the Force Element (FE) structureas a recognized MRP/SLOC area. Army willbe able to provide further impact after theGCSS-Army IOT&E.MILSTRIP Administrator: In response toCOMMENT #1:the first two issues in comment 1:Re 4.c.(2)(a): Isn't the "first letter designation(1) Concur, there is problem with theof MAPAC" rp45? To my thinking thecurrent wording for this paragraph. TheMAPAD is unaffected by adding MDA as anI/A and making "I" a valid FMS service code"I" would only appear in the documentin rp30.number and not in the constructedMAPAC. Revised to read: DLARe 4.c.(2)(b): I assume this paragraph refers to Transaction Services and supportingCISIL. Is there any reason it can't be statedsystems need to add the letter “I” to alltransaction edits intended to recognizeexplicitly?FMS which are currently based on "B, D,Lastly, there are several references to ArmyK, P, and T" in the first position of thedocument number.and DLA requisitions with MDA documentnumbers. That would be a tremendous impact(2) More detail added. Revised to read:on CISIL. My guess is that it's just a matter ofDLA Transaction Services will route alltime before the politics makes this a reality.FMS requisitions to the MDA ILCO, ifCOMMENT #2:not received from the MDA ILCO.Pending implementation of the SecurityCooperation Enterprise Solution (SCES),I have attended several meetings/TELCONswith MDA/DSCA and have been told that ALL all FMS requisitions with documentMDA managed material provided under a case numbers beginning with "I" will bewill come from MDA procurement, includingprocessed through the Army ILCOthose items normally considered as WCF. Any system, Centralized Integrated System forInternational Logistics (CISIL).Army/DLA material required to support anyMDA cases (excluding AE-B-UAF) will befurnished on a companion Army case;consequently, I do not understand the lastMDA response to comment 2:Currently there are no spare parts or anysentence of para 5, "Ultimately, otherComponents, particularly Army and DLA will parts on an MDA case that will not behave a requirement to satisfy requisitions using coming from a vendor. The systems arenot currently fielded and all parts comethe new S/A code "I" in the documentfrom the vendor. Any Army items will benumber."Enclosure 2, ADC 428
Currently, none of the current systems, e.g.,DSAMS, CISIL, DIFS, PBAS nor1200 System can prepare/execute a case withmultiple IA codes.3. Navy4. Air Force5. Marine Corps6. DLA7. DLAInformationOperations –DistributionStandardSystem (DSS)8. DLATransactionServices WebSDR9. DLAManagementStandardsThe Navy concurs with PDC446 as written andsubmits no additional changes or
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
DAC DAC ADC ADC. X19532-062819. Figur e 2: RF-ADC Tile Structure. mX0_axis Data Path ADC VinX0 mX1_axis Data Path ADC VinX1 mX2_axisData Path ADC VinX2 mX3_axis Data Path ADCVinX3 mX3_axis mX1_axis ADC mX0_axis Data Path ADC Data Path ADC VinX_23 VinX_01 Data Path Data Path Dual RF-ADC Tile Quad RF-ADC Tile. X23275-100919. Chapter 2: Overview
· ADC-20 or ADC-24 High-Resolution Data Logger · Quick Start Guide For detailed technical information, please refer to the ADC-20 and ADC-24 Data Sheet. An optional PP310 ADC-20/ADC-24 Terminal Board is designed for use with both data loggers. For simple applications, you can connect sensor wires to the screw terminals on the terminal board,
2. ADC Clock: Clock synthesis circuit to provide required clock frequency to the ADC 3. ADC Supply & Reference: Power supply circuits to provide analog and reference supplies to the ADC Designing for best possible performance MPC57xx SAR ADC Implementation and Use, Rev 0, 06/2014 Freescale Semiconductor, Inc. 5
The ADC-20 and ADC-24 are designed to measure voltages in the range 2.5 volts, but are protected against overvoltages of 30 volts. Any voltages outside the overvoltage protection range may cause permanent damage to the unit. Mains (line) voltages. The ADC-20 and ADC-24 data loggers are not designed for use with mains (line) voltages. Safety .
An ADC refers to a system that converts an analog signal into a digital signal. ADC architectures, notably the Flash ADC, Successive Approximation Register (SAR) ADC and the Pipeline ADC have evolved over the years, each offering one advantage over the other. High speed of operation while resolving a high number of bits with
NOTE: Sybase 12.5.0.3 users should make sure their MDA tables are properly configured so they can see all available statistics. Please refer to the instructions for enabling MDA tables. Enabling MDA Tables In ASE 12.5.0.3, a new feature called "MDA tables" wa
Sep 09, 2021 · Dennis O. Steinacker Buddy Boy, Inc. t/a The Gardener of Bel Air PFA 0821 MDA-F 0266 Edward J. Chmelewski Buffalo Construction Company, Inc. PFA 0797 MDA-F 0543 David J. Kardos Burning Tree Club PFA 1027 MDA-F 0452 Thomas C. Warfield C & C Custom Lawn Care, Inc. PFA 1519 MDA-F 0602 Matthew
*Bargains, Jack Heifner *Barretts of Wimpole Street, Rudolph Besier (2) Basement, The, Harold Pinter *Basic Training of Pavlo Hummel, David Rabe *Bear, The, Anton Chekhov (3) *Bearclaw, Timothy Mason Beautiful People, The, William Saroyan *Beauty Part, The, S. J. Perelman *Beaux’ Strategem, The, George Farquhar *Beaver Coat, The, Gerhart Hauptmann Becket, Jean Anouilh *Beggar on Horseback .
