Workbook Cell Mapping

Maps intake-doc question IDs (A1, B7, …) to the section and field label inside the official VCF 9.1 Planning and Preparation Workbook. We don’t pin to spreadsheet coordinates (P6 style) because Broadcom shifts rows between workbook revisions — field labels are stable, coordinates are not.

Workbook reference: reference/vcf-9.1-planning-and-preparation-workbook.xlsx v1.9.1.001 (revision shown in sheet VCF & VVF Planning, cell P5). When Broadcom ships a new revision, replace the file under reference/ and re-validate this mapping against the new sheet/field labels in the same commit.

How the downstream tooling reads the workbook (named ranges)

VCF.JSONGenerator (see README Related tools) turns a filled workbook into VCF deployment JSON by reading the workbook’s defined names (named ranges) — not cells or labels. Concretely it collects:

• every named range prefixed input* — the value fields (FQDN, IP, VLAN, CIDR, password, name, …). The pinned 9.1 workbook has ~2,338 of these.
• every named range suffixed *chosen — the dropdown selections (deployment model, sizes, include/exclude, …). ~465 in 9.1.

Names are structured by area — input_mgmt_*, input_wld_*, input_cluster_*, input_flt_*, input_xreg_*, etc. (biggest sets: WLD ~1188, mgmt ~428, cluster ~218, fleet ~190). Named ranges move with their cell, so they survive Broadcom’s row shifts — which is why they’re the stable reference if you script against the workbook: populate these input_* / *_chosen named ranges and VCF.JSONGenerator consumes them directly.

Intake → named range (management domain) — first cut

Maps each management-domain intake ID to the workbook named range(s) it populates. {a,b} = brace expansion of a name family; per-AZ names show az1 and gain an az2 twin (on Configure Management Domain) when A13 = stretched. First cut — validate before wiring a generator. Sources: the module’s input* / *chosen read logic + a full defined-names export of the pinned 9.1 workbook.

Validated. Resolved: C8 → input_parent_dns_zone; D1–D4 → the input_ca_* / input_certificate_authority_* block on Configure Management Domain. Confirmed absent (no named range): C3 DC FQDNs (only the Identity Broker Day-N input_flt_vidb_* fields exist), D5/D6 (cert SAN auto-derives from the FQDNs; validity not captured), F5 mgmt NSX Manager appliance passwords (only Edge input_mgmt_nsxt_en_*), B16 (route policy), B17 (DHCP scope), B22 (extra BGP neighbor). Day-2 (B21/E15) live on the Deploy Fleet Management Day-N sheet — the network fields there are input_xreg_* / input_flt_auto_*; the placement/method Select Option cells are not named ranges. Some passwords live on Value Reference Tables (sddc_mgr_*), not an input_* name.

Intake → named range (workload domain, section H) — first cut

The input_wld_* set is a single workload domain (not per-WLD-numbered) and mirrors the mgmt-domain layout (input_wld_az1_*, az2, cl01, nsxt, supvr, …). Fill it per WLD — repeat the block for each. Same conventions as above (az1/brace notation; az2 twins when stretched). First cut — validate before wiring a generator.

Not mapped (out of scope for a core WLD): optional-solution prefixes — input_srm_* / input_wld_vrms_* (Site Recovery / DR), input_ccm_* (Cross-Cloud Mobility), input_cbr_* (Cloud-Based Ransomware), input_k8s_* / input_vvs_* — populate only if those solutions are in use.

Sheet: VCF & VVF Planning

Sheet: Management Domain Sizing

Sheet: Deploy Management Domain

Sheet: Configure Management Domain

Sheet: Deploy Workload Domain

Sheet: Deploy Cluster

Repeat per additional cluster. New VLANs/subnets per cluster come from 01-network-dns-plan.md.

Sheet: Deploy Fleet Management Day-N

Fleet components deployed after bring-up (Day-2 / Day-N). Planned in 05-day2-deployments.md; the table below maps its decisions to this sheet. Also covers extra Ops / Automation nodes and federation driven by the platform roadmap (intake A15), captured in a follow-up session.