Specifying Test Equipment in a Federal Contract: Name the Method, Freeze the Revision, Agree What Pass Means

Defence procurement · 5 min read · 25 cited facts

The expensive argument at acceptance is rarely about hardware. It is about a statement of work that said 'tested to MIL-STD-704F' and believed it had specified a test. It had not. MIL-STD-704 defines the power at the equipment's terminals; the test methods live in MIL-HDBK-704-1 through -8, individually numbered by power type — the SAC, TAC, SVF, TVF and SXF series. A SOW that names the standard without naming the method numbers has told the supplier what environment to think about, and nothing about what will be run, witnessed or accepted. Source: MIL-STD-704 document record — Defense Logistics Agency, ASSIST QuickSearch. Retrieved 2026-08-24.

Revision discipline is the second half of the same sentence. MIL-STD-704F dates from 12 March 2004, with Change 1 of 5 December 2016; the DLA ASSIST record carries a Revision F Notice 4 validation dated 24 June 2026, with the next review due in June 2036. Revision F has not been superseded — there is no Revision G to design against — so 'the latest revision' currently means F — but write 'F', because a SOW that says 'latest' has delegated its own meaning to whatever the review cycle does mid-programme.

The cancelled-revision trap

This is not hypothetical. MIL-STD-1399-300B, the shipboard electric power interface standard of 24 April 2008, was cancelled by Notice 1 on 25 September 2018 and superseded by MIL-STD-1399-300-1, Low Voltage Electric Power, Alternating Current; medium-voltage systems moved to Part 2. Vendor pages and test-lab capability sheets still cite 300B routinely, and SOW authors copy from capability sheets. A statement of work drafted today that invokes 300B is invoking a revision cancelled in 2018. Whether that is a finding or a formality at acceptance depends on the contract language — and the time to resolve it is before the acceptance procedure is written, not after the rack is on the dock. Source: MIL-STD-1399 Section 300 document record and Notice 1 — Defense Logistics Agency, ASSIST QuickSearch. Retrieved 2026-08-24.

The check costs nothing. Every military standard's status — active, cancelled, superseded, validated — is public on DLA's ASSIST QuickSearch. If the SOW invokes a document, pull its ASSIST record before the SOW goes out. Ten minutes there is cheaper than a contract modification later.

What a runnable requirement looks like

Compare two sentences. 'The unit shall be tested to MIL-STD-704F' — unrunnable; it names an environment. 'Steady-state 400 Hz AC voltage shall be verified within 108.0–118.0 V RMS and frequency within 393–407 Hz, per Table I of MIL-STD-704F, using the applicable MIL-HDBK-704 method for the platform's power type' — runnable; a technician can execute it and a quality engineer can sign it. The difference is not length. It is that 'pass' became a number with a clause attached.

• The method: the handbook or test-procedure document and paragraph for each test, not just the parent standard.
• The limits: acceptance values as numbers with their clause — Table I, Figure 3 — so pass is arithmetic, not opinion.
• The revision: named and frozen at award, with a stated mechanism for documents revised or cancelled mid-programme.
• The witness: who attends, what constitutes the record, and whether first-article testing runs at the supplier's facility or the buyer's.
• The split: which requirements bind the unit under test and which bind the test equipment — a source that must produce a transient envelope and a unit that must survive it are two different specifications.

That last line decides the bench. A SOW that names the 704F methods has implicitly specified the source: it must hold the Table I steady-state band and drive the transient envelopes — the normal AC transient reaches a surge of 180 V for 10 ms and a sag to 80 V for 10 ms (Figure 3 of MIL-STD-704F). Name the method, and the equipment requirement falls out of the document. Leave it out, and the equipment becomes a negotiation conducted at acceptance — the most expensive room to hold it in.

Where the contract is already ambiguous, do not resolve it by assumption in either direction. Which revision a contract invokes, which method set applies and whether a cancelled document still binds are questions about your contract, and the contracting officer's written answer outranks any vendor's reading — including ours. Nothing here is legal advice; it is the pattern of where acceptance goes wrong.