Appendix G — Vendor catalogue, RFP, test scenarios, scoring and TCO
The procurement pack separates source provenance, capability evidence, legal/operational eligibility and commercial assumptions. Read Chapters 25–30 for the decisions behind the worksheets. No firm ranking, supplier benchmark or actual price quotation is claimed.
G.1 Open the right file
| Need | File / reading route | Population and evidence status |
|---|---|---|
| Source catalogue | Solution landscape workbook, research synthesis | Populated source inventory; grades describe provenance, not tested capability |
| Consulting comparison | Chapter 26 | Named first-party approach components, buyer implications and unknowns |
| Indian provider comparison | Chapter 27 | Product/service-level claims; nationality is not an evidence score |
| Platform / cloud mapping | Chapter 28 | Named module and integration boundaries, not a blanket compliance suite endorsement |
| Build/adopt decision | Chapter 29; adoption model | Hypothetical inputs and ownership economics; not a Presidio benchmark |
| Reusable scoring and RFP questions | RFP workbook | Blank reusable scorecard plus populated synthetic BID-001/BID-002, proposed PoV data and scoring; TCO inputs are embedded in each scorecard rather than supplied as a separate TCO sheet |
| Integrated decision | Dossier bidder workbook, inputs, workpapers | Same fictional bidders; formula evaluation does not turn “Tested” evidence-tier labels into real observations |
| Programme capacity and cost | Cost inputs, computed model, static workbook | Hypothetical staffing/meters; not additive to overlapping bidder TCO without reconciliation |
G.2 RFP issue checklist
Before sending a real RFP, state entity and processing scope, applicable control outcomes, mandatory gates, interfaces, environments and prohibited data movements. Ask each bidder for the same response: named product/edition, responsibility split, deployment dependencies, evidence export, rights/cessation/retention behavior, processor terms, failure recovery, operator capacity, pricing meters, upgrade responsibilities and exit plan. Record every exception and owner. A documented capability can earn a test request, not automatic acceptance.
Require an isolated PoV using synthetic data and predeclared expected outcomes. Include an accepted withdrawal followed by denied unauthorised processing, a scoped lawful-retention branch, stale replay, absent processor acknowledgement, failed replica, restore quarantine and evidence export. The workbook’s PoV scenarios are specifications for bidder evaluation. They are not executed vendor scripts. Executable local teaching checks are delivered in the dossier test pack and the reusable catalogue; production adapters must still be built and verified. This is the explicit boundary of the TOC’s executable-scenario promise.
G.3 Scoring cannot override a failed floor
The workbook supplies weights, score anchors, evidence discounts and mandatory gates. Blank inputs remain unassessed. A bidder with a higher weighted score can still fail the mandatory processor condition. Preserve the failed decision rather than redistributing weights until the preferred bidder wins. State whether a threshold is a buyer choice; do not present it as a statutory acceptance score.
The source inventory’s A/B/F grades and the scorecard’s evidence tiers are different scales. A legal source is not a bidder to be ranked against a vendor page. The “Tested” tier inside a synthetic bidder sheet is a stipulated input. Real procurement must replace it with the actual scoped workpaper and observed result.
G.4 Commercial reuse
Keep seats, requests, objects, storage, professional hours and support periods in their own meters. Price migration, connector maintenance, revalidation, exit and retained evidence. COST-001 funds a programme; bidder TCO prices a component proposal. Combining them without removing overlaps double-counts spend. The cost workbook is a static calculated view; the bidder workbook contains formulas. Neither has accepted native spreadsheet rendering in this handoff.
The procurement reproduction guide and recorded calculations retain actual local checks. Public first-party URLs, access metadata and hashes are in the source manifest. Recheck the real offer, licence, edition and live deployment before any commitment.