Sole-Source Justification for Dell: When and How to Write a J&A

There are moments in federal IT acquisition when the honest answer to "can another vendor meet this requirement?" is no. A new node has to join an existing Dell PowerEdge cluster managed by OpenManage. A classified enclave is built around PowerMax replication and a competitor's array would break the established data path. When that is genuinely the case, the lawful route is not to quietly steer the buy — it is to document a sole-source justification and, above the simplified acquisition threshold, a formal Justification and Approval (J&A). Done right, it survives protest and audit. Done lazily, it becomes the single most challenged document in the file. This guide explains when a Dell sole-source is defensible and how to write one that holds.

Sole Source vs. Brand Name: Know Which You're Writing

These two are related but distinct, and conflating them is the most common drafting error.

• Sole source (FAR 6.302-1, "only one responsible source") means only one vendor can satisfy the need at all. For Dell, this is rare and usually tied to proprietary integration — for example, expanding a PowerScale scale-out NAS cluster where the new nodes must be the same architecture to join the existing namespace.
• Brand-name justification means the brand is specified but multiple resellers can compete to supply it. Under FAR 6.302-1(c) and FAR 11.105, you may require a Dell brand name, then compete the award among authorized partners. This is the more common — and more defensible — posture for commodity hardware like OptiPlex, Latitude, or Precision fleets.

Decide which you are actually doing. If three resellers can quote the same Dell SKU, you have a brand-name requirement competed among sources, not a true sole source. Writing it as the latter when the former is true invites a sustained protest.

The FAR Authorities You'll Cite

For full-and-open exceptions, the operative citations are FAR Part 6.302. The two that fit Dell scenarios most often:

• FAR 6.302-1 — Only one responsible source or only one will satisfy agency requirements. This covers proprietary architecture, established interoperability, and follow-on integration.
• FAR 6.302-2 — Unusual and compelling urgency, where delay would cause serious harm. Use sparingly and only when genuinely true; urgency justifications draw scrutiny.

For simplified acquisitions below the threshold, you document a limited-source justification under FAR 13.106-1(b) instead of a full J&A — shorter, but the logic must still be sound. On a pre-competed Schedule order, the governing language is the fair-opportunity / limited-source framework (FAR 8.405-6 for Schedules), not Part 6 — cite the right one for your acquisition.

What Makes a Dell Justification Defensible

A reviewing official or a protest at GAO tests one thing: is the restriction tied to a genuine requirement, or to preference and convenience? Convenience is not a lawful basis. Anchor every justification in technical fact:

• Established interoperability. "The existing fabric is built on Dell PowerMax with SRDF replication to the COOP site; introducing a different array would require re-architecting the replication topology and revalidating the disaster-recovery posture." That is a requirement, not a preference.
• Management-plane standardization. A fleet managed through iDRAC and OpenManage Enterprise with established automation, firmware baselines, and security policies is a legitimate integration constraint — but state what breaks, not merely that staff like the tool.
• Compliance and accreditation lineage. If the enclave's ATO, FIPS 140-3 validated modules, or DoDIN APL listing were granted against specific Dell configurations, re-accreditation cost and risk are real, citable facts.
• Follow-on to a prior competed buy. If the original PowerEdge R760 cluster was competitively awarded and this is an in-scope expansion, say so — it strengthens the file considerably.

Avoid the language that gets justifications rejected: "Dell is the industry leader," "our team is familiar with Dell," or "it's what we always buy." None of those is a requirement.

Writing the J&A: Required Elements

A FAR 6.303 J&A has mandatory content. At minimum, include:

• Agency and contracting activity identification.
• Nature/description of the action and the supplies or services (e.g., "expansion of an existing PowerStore 5200 array, 12 additional NVMe drives plus one expansion enclosure").
• The statutory authority cited and a demonstration that the action falls within it.
• The reason competition is not available — the technical narrative above.
• A market-research description. This is non-optional and frequently thin. Show you actually checked: were there alternatives that could meet the requirement (not just the function)? Document why they don't.
• Actions to remove barriers to future competition — for instance, planning the next full refresh as a full-and-open competition so the agency isn't permanently locked in.
• Certifications by the technical and contracting personnel that the justification is accurate and complete.

Match the approval level to the dollar value per FAR 6.304: the CO can approve smaller actions, while higher thresholds escalate to the competition advocate, the head of the contracting activity, or the senior procurement executive. Route it to the right signature the first time.

Practical Takeaway

A strong Dell sole-source or brand-name justification is short on adjectives and long on architecture. Cite the correct authority for your contract type (FAR 6.302 for open-market, 8.405-6 for Schedules, 13.106-1 for simplified buys), prove the restriction flows from a real interoperability, accreditation, or follow-on requirement, document genuine market research, and route to the proper approval level. If you can swap "we prefer Dell" for "the existing accredited PowerMax/iDRAC environment requires it," you have a file that survives review.

The fastest way to firm up the technical narrative is to nail the exact configuration and its compatibility lineage. As an authorized Dell Technologies partner serving federal, DoD, SLED, and healthcare buyers, Uniqcli can confirm TAA-compliant SKUs, pull country-of-origin and certification documentation, and validate that a proposed expansion truly matches your installed base. Request a quote or talk to a specialist and we'll help you build the supporting record before it reaches your reviewing official.