Planning and advice before a request

← All Insights

1. The work that happens before the request exists

A case begins with a written request from the partner government. What produces that request is months of conversation, and the manual treats it as a job with owners.

The office in the embassy starts from the partner’s finances, working out how the procurement fits that government’s budgeting timeline (SAMM C5.1.4). The technical side sits elsewhere. "The IA Program Office will oversee the acquisition planning process to ensure all facets of acquisition, including technical, regulatory, and procedural aspects are managed appropriately" (SAMM C5.1.4).

Between them they keep the partner current on the United States program of record, from acquisition milestones and lot buys to obsolescence and production delays (SAMM C5.1.4). One warning is singled out. "SCOs and IAs should emphasize to the partner that sustainment of requested defense articles will likely require budgetary planning beyond the initial acquisition case" (SAMM C5.1.4).

2. Teams sent to work out what is needed

Where the requirement is unclear, people are sent. The embassy office can arrange a site survey team or an expeditionary requirements generation team. The stated purpose is practical. Such a team identifies capability gaps, holds the planning discussions that save time later, and checks that the proposed purchase matches both the operational requirement and the budget (SAMM C5.1.4.1).

The second kind of team is approved at the top. "Approval for ERGTs is made by the DSCA Director" (SAMM C5.1.4.1), and it is sent with a product in mind: "Deployment of an ERGT should result in submission of an actionable LOR" (SAMM C5.1.4.1). How such teams are requested and who they answer to is covered in the teams sent to a partner country.

Someone must pay for the visit before a case exists, and the manual uses a loan rather than a grant. "If an LOA does not yet exist, FMS Administrative funds may be used to perform the site survey up front, but the FMS Administrative account must be reimbursed if and when an LOA is developed from the site survey" (SAMM C5.1.4.1). The account that fronts the money is described in what goes into the price.

3. When the requirement is too complex to price

Some requirements cannot be answered with a quotation because nobody yet knows what is being bought. The manual lists the markers: significant acquisition costs, intricate integration of systems of systems, bespoke deviations from the United States program of record design, strategic acquisition and contracting, or other risk reduction activity (SAMM C5.1.4.2).

The answer is to sell the analysis first. The partner is directed to request a studies and analysis case, a planning case, or a technical assistance case to cover that work (SAMM C5.1.4.2). The definition work becomes a case of its own, which is worth knowing when a partner asks for a price on something still being designed.

4. What the embassy office may say

The manual publishes a short list of what the office in the embassy is expected to do before a request arrives. It opens with a caution rather than a task: "Avoid false impressions" (SAMM Figure C5.F2).

The rest runs through maintaining dialogue, assessing partner capabilities against United States strategy, and recommending equipment and training that fit the operational requirement. Where sensitive or classified capability looks likely, the office prepares a release assessment in advance (SAMM Figure C5.F2).

The last item carries the sharpest tension. "Promote U.S. industry solutions to foreign government counterparts while maintaining neutrality between U.S. competitors" (SAMM Figure C5.F2). The same balance is examined in what a security cooperation office may do for industry.

5. The advisory memorandum

Certain requests are reported upwards as soon as they arrive. An advisory memorandum notifies the under secretary of defense for acquisition and sustainment and the joint chiefs of staff that a request has come in for a listed item (SAMM C5.2.6.1).

One office writes it to a published format and sends it with the partner’s request attached, along with the country team assessment where required (SAMM C5.2.6.1.1). Timing is early by design, so the answer forming inside the government matches theater objectives and technology security policy.

The reply window is short. "The LOR recipients at the IA have 10 working days from the date of the LOR Advisory to provide comments to DSCA for consideration" (SAMM C5.2.6.1.1). Disagreement has a route out of the room: "In the event of non-concurrence, DSCA will refer disagreements to an appropriate level in OUSD(P) for resolution" (SAMM C5.2.6.1.1).

What the advisory does not do matters as much. "The LOR Advisory does not take the place of any Exception to National Disclosure Policy (ENDP) processes or releasability requirements that are worked by the MILDEPs" (SAMM C5.2.6.1.1). Completing it clears nothing on the release side, which runs separately and is described in technology transfer and release decisions.

6. The published list of triggers

Eighteen entries set out which items attract an advisory letter, a unique review, or both. "Table C5.T6. identifies defense articles requiring item-specific review and provides links either to forms for LOR Advisories or to explanations of unique review requirements" (SAMM C5.2.6.1).

Two entries get their own advisory format. Larger air to surface and indirect fire munitions with their delivery systems use one form, and ballistic missile defense capability uses another with the missile defense agency added as an addressee. Everything else needing an advisory uses the standard letter (SAMM Table C5.T6).

The rest of the list maps where sensitivity concentrates: intelligence and command systems, communications security, geospatial content, electronic warfare, night vision, shoulder fired air defense missiles, white phosphorus munitions, medical countermeasures and police training (SAMM Table C5.T6). Two structural entries sit alongside them: the first introduction of major defense equipment to a purchaser, and any sale expected to cross the notification threshold.

7. Two reviews, one with the wrong number attached

Two of the listed items also carry a short rule of their own. "The IA reviews requests for integration or certification services for installation of non-U.S. subsystems and coordinates with DSCA (IOPS/WPN) prior to development of P&A data or an LOA" (SAMM C5.2.6.2). The parallel rule for equipment that is not standard in inventory sends the coordination to a different office: "The IA reviews requests for SME not standard in DoD inventory and coordinates with DSCA (IOPS) prior to development of P&A data or an LOA" (SAMM C5.2.6.3).

Both bite before any pricing goes out, which ties them to the estimates in rough order of magnitude and price and availability. Anyone following the table to those rules will not find them: it cites two section numbers that do not exist, the real text sitting two numbers lower in each case.

8. What a supplier can take from this

The decisions that shape a case are largely made before the request is written. By then the capability has been discussed, the budget tested, and sometimes a team has visited and written the requirement down.

If the equipment appears on the published trigger list, the timeline lengthens before anything visible happens, because the advisory goes up as the request comes in. Non standard equipment and foreign subsystem integration are the two cases where a supplier is most likely to be asked for data early, since the coordination has to be complete before a price can be given at all.

Key terms

Acquisition planning	The pre-request work of fitting a purchase to a partner budget and to production reality.
Expeditionary requirements generation team	A team approved by the agency director, deployed to produce an actionable request.
Studies and analysis case	A case sold to fund the definition work where a requirement is too complex to price.
LOR advisory	A memorandum notifying two senior offices that a request for a listed item has arrived.

Every statement above links to the document behind it. The full source list for this piece is on the sources page.

This page describes public United States government programs for general information. It is not legal, regulatory or procurement advice, and it does not address the facts of any particular case.

How Sentfore supports this

Requirements written before a case exists are the ones that shape delivery years later. Sentfore works at the delivery end of defense programs in difficult environments, providing secure movement, protective security, facilities and life support. Requirements can be sent through the contact page.