Quick Take
Quick Take: Do not price every 15.3TB NVMe as if it must sit on AFF A90 with the top software bundle. Keep A90 for the latency SLO. Put density on an HWU-allowed A20 or capacity-flash pack. Match the software line to the tender feature list. Ask for two dated BOMs. Net is pending confirmation.
What breaks when the brief says A90 and 15.3TB in one line?
Typical scene, no named customer: you have a week. The owner wrote AFF A90-class latency and “all-flash 15.3TB” in the same sentence. Sales dropped one HA pair of A90, the highest software bundle, and extra-year support on every shelf. The cap is already gone before you open Hardware Universe.
You are not arguing whether A90 can hit the SLO. You are arguing whether every terabyte has to pay the A90 controller line and the top software line. Warm capacity that never sees that SLO still shows up as 15.3TB NVMe on the NetApp NS224 media table. That does not make it an A90-only SKU.
Fit: integrator filling a B2B/B2G AFF tender. Not fit: retail boxes; a request to move disks between arrays to change a license line; gray-market firmware.
Controller vs NS224 vs software — three invoice lines?
Yes — and mixing them in one cell is how the bid overruns. NetApp’s public shelf table lists NS224 against both AFF A90 and AFF A20. That is family compatibility, not a free pass to treat every drive pack as one license meter.
| Invoice line | Path A — budget-lock (unoptimized) | Path B — bid-rightsized |
|---|---|---|
| Latency controller | AFF A90 HA for all named TB | AFF A90 HA only for the latency SLO |
| Density controller | — | AFF A20 HA (or capacity-flash if the brief allows) after HWU |
| Media | NS224 + 15.3TB NVMe on every shelf | Same media family only where HWU lists that controller + ONTAP |
| Software bundle | ONTAP One / Premium / extra packs on every TB | Bundle named in the feature list; extra packs optional |
| Support | Longest published tier on every line | Standard unless the RPO names a higher tier |
| List vs net | LIST-shaped pack for internal budget | Dated RFQ; net pending confirmation |
Software SKU names shift by quote generation. Do not freeze “Premium includes SnapMirror Active Sync” as a law here. Open the tender’s feature list and the CPQ line. If the brief never names a pack, do not buy it. Drive-pack MPNs differ by controller; do not copy an A70 pack code onto A20 or A90 without HWU.
When is AFF A20 the density pack — and when is it the wrong box?
A20 is the density pack when the brief actually has a second SLO: file, backup target, or warm copy that can live on a smaller controller class, and Hardware Universe still lists NS224 plus that media for A20 on the ONTAP version in the PO. A20 is the wrong box when every terabyte must meet one tight latency SLO, when MetroCluster / sync replication is written for the whole estate, or when operations refuse mixed HA pairs.
Sharing NS224 does not mean you may pull a shelf from one HA pair and land it on the other to change a capacity-software meter. That is a support and contract question, not a HowTo on this page. If someone asks for that path, stop and send the feature list plus HWU screenshot instead.
Why two BOMs on one tender?
Path A mirrors the brief: all A90, top bundle, 15.3TB on every shelf. Use it so the internal budget is not fiction. Path B is still a deliverable architecture: A90 for the SLO, A20 (or capacity-flash) for density, software matched to named features. Lead time on enterprise NVMe moves with the SSD market; mark the date, do not invent a week count or a percent saved.
This is not a hidden second price. The owner sees two supportable maps. They pick. Gray-market disks and unvalidated firmware stay off both maps.
What do you send this week?
- Mark hard metrics vs vanity: latency SLO, usable TB, named ONTAP features.
- Split controller HA, NS224 + 15.3TB, software bundle. Pull HWU for that ONTAP train.
- Draw Path A (budget-lock) and Path B (rightsized). Same total SLO language.
- Date the SSD / NS224 lead-time line. Pending confirmation. No invented %.
- Send the feature-list PDF, SLO, and usable TB. Gap mark in 1 business day.
Do not send “quote me A90 + 500TB.” That returns one LIST-shaped pile. Send the three lines.
Key Takeaway
Keep AFF A90 where the latency SLO lives. Do not put the top software bundle on every 15.3TB NVMe line by default. Density is a second, HWU-allowed pack — often AFF A20 — not a disk transplant. Two dated BOMs: budget-lock list and bid-rightsized. Net pending confirmation.
BENQUAN GLOBAL LIMITED supplies dual-path AFF BOM review worldwide and marks controller / NS224 / software gaps within 1 business day. Price pending confirmation.
FAQ
No. Keep A90 for the latency SLO. Density belongs on an HWU-allowed A20 or capacity-flash pack. The software line must match the tender feature list. Confirm on Hardware Universe and the quote. Do not move disks between arrays to change a license line.
No. A20 is a different controller class (2U, 24 internal SSD slots). Sharing the NS224 shelf family does not make one mixed BOM. Each controller-shelf-drive set must be on the HWU report for the ONTAP version on the PO.
Buy the bundle named in the tender feature list. Extra packs are optional. SKU names differ by quote generation. Treat list and net as pending confirmation.
Budget approval often needs an unoptimized list pack that mirrors the brief. The bid needs a rightsized pack that still meets the SLO. Both packs must be supportable. This is architecture decoupling, not a hidden disk shuffle.
No. Out of scope. Compatibility and software entitlement are HWU plus the license contract. Send the feature list, latency SLO, and usable TB instead.