Key Links
The Case Description on the Basic LOA provides a brief overview of the Defense Articles and services being provided on the document. On AMDs and MODs, it identifies the major program involved, changes that were made, reason(s) for the change(s), and identification of previous unaccepted amendments, if any. In cases where the Case Description in intended to increase or decrease funds or Months of Service (MOS), the description must clearly state the reason for the increase or decrease. IAs are no longer required to reference each individual line within the Case Description.
RECOMMENDATION: In general, IAs should utilize Tables C6.T7. and C6.T8. as a guide of changes that should be listed within the Case Description field. Tables C6.T7. and C6.T8. do not provide an inclusive list of changes.
EXCEPTIONS: The following do NOT need to be called out in the Case Description, UNLESS they are the main or only reason for the document: Updates to Notes, description, payment schedule, Source Code, Type of Assistance Code, Offer Release Code, Line Manager Code and/or Operating Agency Code, and shipped complete status.
The phrase “This LOA” is hard-coded in DSAMS for all Basic documents and precedes the data entered in the Case Description.
| Example |
|---|
This LOA provides ammunition and applicable technical documentation, per Customer’s request. |
The phrase “This Amendment” / “This Modification” is hard-coded in DSAMS for all AMDs/MODs and precedes the data entered in the Case Description.
Example This Amendment provides for two additional C-130J aircraft and increases associated equipment, technical orders, technical assistance and AFMC Services, per Customer’s request.
This Modification decreases several lines to the highest financial requirement and corrects the FMS Administrative Surcharge on all applicable lines in support of SG-84C and SYV-5 technical assistance, per U.S. Government internal review.
This Modification extends the Months of Service on the F-15 contractor provided support equipment line due to contract slippage and delayed delivery, per U.S. Government internal review. There is no change in scope to this document.
Case Closure Document
Identifies LOA documents being prepared for case closure. Case Closure is the final phase of the FMS life cycle and is extremely important to the U.S. Government and the customer. It ensures the customer has received all deliverables outlined in the LOA document, and provides final billing and the return of any unused funds. When a document is processed for case closure, it will be identified in the first sentence of the Case Description using all capital letters for the term “CASE CLOSURE”.
Example This Modification is for CASE CLOSURE which decreases all remaining lines to the highest financial requirement, per U.S. Government internal review.
NOTE: This is intended for Supply Services’ Complete (SSC) case closure only, not line closure.
Restated Documents
Identifies that a previous document was offered to the customer, including offer date (found on Page 1 of the original offered document), but requires changes before the customer will accept the offer. When a restated document is processed, it is identified in the first sentence of the Case Description and is identified by all capital letters for the term “RESTATED”. The Case Description needs to identify all changes for the current document version).
Example This Amendment is a RESTATED document which supersedes the previous version offered on 16 July 2016. It provides for on-site maintenance support, repair and return services, and spares replenishment for an existing AH-64E Longbow Crew Trainer (LCT) and Tactical Engagement Simulation System (TESS), per Customer’s request.
EXCEPTION: If required changes are discovered before the document is sent to the customer, this situation is treated as a Rework and the “Restate” language is not referenced in the Case Description.
The IA will still need to enter the RESTATE milestone required in DSAMS to return the case to Development status.
The IA will add remarks in the LOA Checklist Comments section (page 2) and in the Case Remarks advising that the document was not sent to the customer.
Previous Unaccepted Document
Occasionally, an AMD or MOD is canceled which creates a gap in the numerical sequence of documents being sent to the customer. To explain the gap, the unaccepted document is referenced in the Case Description of the next document of that type. For instance, if MOD 2 is canceled, the next MOD that is generated must reference the canceled MOD. This is the last sentence in the Case Description.
Example The previous document, Amendment 2, was canceled on 10 March 2017.
The canceled document is identified in DSAMS: 1) View, Case Reports, Document History (RP079) and 2) the Document Number window.