Quick Take
Quick Take: Hitachi VSP One bake-offs fail when peers omit replication years or usable TiB honesty. Freeze one capacity brief, then dual-quote PowerStore and optional Dorado with equal DRR, host ports, and dated ATP at 100 TB usable, 32 Gb FC class, and 24 hours RFQ turnaround. Shanghai TaoHan Industrial Co., Ltd. supplies Hitachi, Dell, and Dorado packages.
When a Three-Column AFA Checklist Matters
Quick Answer: Use this when VSP One or VSP E Series is on the approved list, when PowerStore is the Dell default, or when Dorado is required as a third AFA column. Also use it when finance ranked raw flash stickers before usable TiB, replication years, and host-port maps were written into one RFQ.
- Brand hubs: Hitachi VSP hub · Dorado hub · SKU Lookup.
- Shortlist context: VSP One / E Series shortlist.
- Peer guides: Dorado vs PowerStore · Dorado usable TiB RFQ.
- Migration: VSP 5200/5600 EOS pricing when replacing aging Hitachi estates.
Architecture Fork — Platform vs Equal Brief
Quick Answer: Platform choice locks ops tooling and spare pools. Equal-brief design locks usable TiB, DRR, replication scope, and host protocol across every vendor column. Treat them as two tracks under one CapEx gate — a cheaper sticker with incomplete licenses is still a failed go-live risk.
| Track | What you freeze | Common miss |
|---|---|---|
| Platform | VSP One / E / PowerStore / Dorado | Nickname bake-off only |
| Usable TiB | Target + defended DRR | Raw flash marketing |
| Replication | Metro / async + license years | “Software TBD later” |
| Host I/O | FC / iSCSI / NVMe ports | Ports after cutover |
| ATP | Dated ship all columns | Array lands; licenses wait |
Naming traps
VSP One Block, VSP E Series (E590 / E790 / E1090), and high-end Hitachi paths are not one spare pool. Do not peer an E590 expansion to an enterprise PowerStore or Dorado 18000 brief without rewriting usable TiB, replication scope, and host-port counts on the RFQ.
Peer Mapping (Intent, Not Nicknames)
Quick Answer: Map by capacity and ops intent carefully. Midrange block often dual-quotes VSP E / VSP One against PowerStore; estates that need a third AFA column add Dorado on equal usable TiB. Confirm protocol and DRR before ranking vendors on raw flash stickers alone.
| Intent | Typical Hitachi path | Peer columns |
|---|---|---|
| Midrange AFA | VSP E / VSP One Block | PowerStore (+ Dorado) |
| Metro / DR | Matched dual site | Equal replication years |
| Dell-centric estate | Hitachi as challenger | PowerStore primary |
| Triple shortlist | VSP + PowerStore + Dorado | One capacity brief |
Equal-Assumption Matrix (Put Counts on the RFQ)
Quick Answer: Classify every capacity and license line before ranking CapEx. Usable TiB, DRR, replication, host ports, shelves, and support years belong on the brief. Wrong capacity math wastes negotiation time and fakes a cheaper array until the first growth cycle fails later.
| Line | Prefer | RFQ fields |
|---|---|---|
| Usable TiB | Same DRR on all columns | Target TiB, profile note |
| Replication / metro | If RPO needs it | Term years, site count |
| Host ports | FC / iSCSI / NVMe map | Speed, qty, optics |
| Shelves / support | Matched growth plan | SKU qty, support years |
Usable TiB is a written assumption
Do not accept raw marketing capacity. State the data profile and DRR you will defend — then quote VSP One, PowerStore, and Dorado on the same numbers. Pull Hitachi and Dorado part lines from SKU Lookup; start hubs at brand-hitachi and brand-dorado.
Sizing Truth — Equal Assumptions
Quick Answer: Force equal usable TiB, host protocol, DR scope, license years, and optics on every vendor column. If one quote includes replication and shelves and another is bare controllers, stop ranking platforms immediately — fix the storage brief first, then re-quote.
- Capacity: usable TiB beats raw flash when comparing CapEx.
- Protocol: FC vs NVMe changes HBA and switch spend on the same RFQ cycle.
- Licenses: replication and feature packs must year-match support terms across columns.
- Lead time: shelf and entitlement queues can exceed controller ATP — shared go-live gate.
RFQ Checklist — Three Columns, One Brief
Quick Answer: One storage brief → VSP One or E Series → equal usable TiB and DRR → PowerStore column → optional Dorado column → replication years → host ports and optics → dated ATP. Third columns are fine only when capacity and protocol assumptions stay fully equalized.
What to put on the RFQ
- Usable TiB target + defended DRR assumption (same on every column)
- Exact Hitachi path: VSP One Block vs VSP E Series class
- PowerStore model class matched to capacity intent
- Optional Dorado family (6000 / 8000 / 18000 class) on the same TiB
- Host protocol: FC / iSCSI / NVMe and port counts
- Replication / metro yes/no + entitlement years per vendor
- Optics/DAC for front-end ports + spare %
- Support term years matched to software years
- Dated ATP for controllers, shelves, and entitlements vs one go-live
- SKU Lookup BOM export or part list attachment
Start from brand-hitachi.html or SKU Lookup, then submit the equal brief on rfq.html.
Real-World Deployment Scenarios
Quick Answer: Map the three scenarios below to your workload, facility, and commercial constraints before freezing CapEx. Equal-BOM RFQs should cite which scenario drives the shortlist.
Scenario 1: Equal-BOM Rebid After Price Notice (Commercial Bound)
Workload Profile: Incumbent quote ages across a VSP One price update.
Architectural Fit: Re-open on equal usable TiB and software packs; force vendors to restate nets against the new list climate.
Scenario 2: Tri-Vendor Shortlist (Architecture Bound)
Workload Profile: VSP One vs PowerStore vs Dorado on one scorecard.
Architectural Fit: Lock resilience, replication, and license models before price—otherwise discounts hide scope gaps.
Scenario 3: Controller/Software Bundle Audit (BOM Bound)
Workload Profile: Quotes bury capacity licenses inside controller lines.
Architectural Fit: Explode feature codes; renegotiate only after the BOM is readable line-by-line.
Frequently Asked Questions
Quick Answer: Unequal DRR and missing replication years stall cutovers more often than controller gaps on the critical path. Write capacity assumptions and license years up front, itemize host ports, and demand dated ATP for array and entitlements on the same go-live before CapEx locks.
One column often includes replication licenses, optics, and multi-year support while another is bare controllers at raw flash marketing capacity. Equalize usable TiB, DRR, protocol, and ATP on one RFQ.
Usable TiB after a defended DRR assumption, host protocol and port counts, replication or metro scope and license years, shelves, support term, and dated ATP against one go-live.
Yes when policy requires three AFA columns. Keep one capacity and protocol brief; add Dorado only with matched usable TiB, HyperMetro or replication years, and host-port maps.
Submit one RFQ with identical usable TiB, protocol, and go-live.
Key Takeaway
Key Takeaway: Multi-vendor AFA CapEx is incomplete without equal usable TiB, DRR, and license years on a shared ATP gate. Win on assumptions — then rank VSP One, PowerStore, and Dorado. Shanghai TaoHan Industrial Co., Ltd. supplies all three packages with competitive pricing for global buyers.