Quote Checklist

FlashSystem Quote Checklist

A practical checklist for gathering the workload, capacity, protection, host, migration, and lifecycle details needed before requesting an IBM FlashSystem quote.

A useful FlashSystem quote request gives the reseller enough context to configure the array, not just price a model number. Use this checklist before comparing vendors.

What Do I Need to Gather Before Requesting a FlashSystem Quote?

Quote inputs

InputWhat to Gather
WorkloadsIBM i, AIX, Linux, VMware, database, file, backup, analytics, and any high-ingest workloads.
CapacityCurrent used capacity, growth rate, required usable capacity, snapshot retention, and data reduction expectation.
PerformanceLatency targets, IOPS, bandwidth, peak ingest windows, batch windows, and host count.
MediaWhether FCM is required, optional, or unknown; include any standard NVMe preference.
ConnectivityFibre Channel, Ethernet, switch ports, zoning, host adapters, VIOS, multipath, and virtualization requirements.
ProtectionSafeguarded Copy, Cyber Vault, immutable backup, synchronous or asynchronous replication, and DR testing needs.
MigrationCurrent array, firmware level, host OS mix, cutover window, outage tolerance, and fallback plan.
LifecycleSupport term, Storage Assurance interest, refresh window, capacity expansion expectations, and budget model.

Build a FlashSystem Quote Request

Start with the unknowns already marked, then replace only what you know. The generated request can be copied, emailed to yourself, or sent to BigTech Reseller for preferred partner routing.

Input 1Workloads

A reseller needs to know which platforms and applications will use the array. IBM i, VMware, AIX, Linux, database, backup, and analytics workloads can drive different sizing choices.

Best scenario: list each major workload, business owner, host platform, and any workload that has unusual ingest or latency needs.

Input 2Capacity

Capacity should include current used capacity, near-term growth, snapshot retention, and whether the buyer expects data reduction to change the usable number.

Best scenario: provide current used TB, target usable TB, annual growth, and snapshot or protected-copy retention.

Input 3Performance

Latency targets, IOPS, throughput, batch windows, and peak ingest periods help prevent a quote that is sized only by capacity.

Best scenario: include latency sensitivity, peak batch windows, host count, and any known IOPS or bandwidth targets.

Input 4Media

FCM and standard NVMe choices affect capacity, compression expectations, performance posture, and pricing. It is fine to start with unknown if the reseller should model both.

Best scenario: state whether FCM is required, preferred, optional, or something the reseller should compare against standard NVMe.

Input 5Connectivity

Host attachment can change the quote through Fibre Channel, Ethernet, switches, adapters, VIOS, multipath, zoning, and virtualization requirements.

Best scenario: list host platforms, port needs, switch capacity, adapters, and any VIOS or multipath constraints.

Input 6Protection

Protection choices can affect licensed features, capacity overhead, replication design, and recovery testing. Quote requests should separate backup, snapshots, Safeguarded Copy, Cyber Vault, and DR.

Best scenario: define protected-copy retention, replication needs, immutable backup use, Cyber Vault interest, and DR test expectations.

Input 7Migration

Migration planning depends on the current array, firmware, host mix, outage tolerance, cutover window, and fallback expectations.

Best scenario: name the current array, host OS versions, data movement method, cutover window, and rollback plan.

Input 8Lifecycle

Support term, Storage Assurance interest, future expansion, refresh timing, and budget model influence the configuration and commercial path.

Best scenario: state the preferred support term, expansion expectations, Storage Assurance interest, and refresh or budget timing.

Preferred partner routing