Cloud Data Platform Selection

A charter and frozen scorecard, real workload evidence, a three-year cost model, a proof of concept on your own data and a tested exit plan, so the platform you sign for still fits in year three.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Cloud Data Platform Selection, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

📊 Data & Analytics

Cloud Data Platform Selection

Comparing and choosing warehouse, lakehouse and BI platforms on cost, performance, skills and lock-in before committing for years.

  1. Platform selection charter and decision owner
  2. Current data estate and tool inventory
  3. Workload profile from twelve months of query history
  4. Contract and renewal date map for data tools
  5. Weighted selection criteria agreed before demos
  6. Stakeholder requirement interviews across roles
  7. Security and compliance gate for candidate platforms
  8. Team skills inventory for platform fit
  9. Warehouse, lakehouse or hybrid pattern decision
  10. Weekly evaluation checkpoint during selection
  11. Vendor record and claims log
  12. Quarterly platform market watch
  13. Architecture decision records for platform choices
  14. Lock-in exposure register
  15. Quarterly vendor business review on your agenda
  16. Committed spend burn-down against the contract
  17. Renewal preparation cycle
  18. Annual platform fit review
  19. How cloud warehouse pricing models work
  20. Concurrency and workload isolation concepts
  21. Open table formats and what they protect
  22. Reading vendor benchmarks critically
  23. Hidden costs in data platform pricing
  24. BI platform licensing models
  25. Semantic layer placement and BI coupling
  26. Long list to shortlist of three platforms
  27. Request for proposal pack for platform vendors
  28. Three-year total cost of ownership model
  29. Hands-on proof of concept with real workloads
  30. Benchmark suite built from your own queries
  31. BI tool bake-off on three real dashboards
  32. Exit plan and data portability test
  33. Single cloud or multi-cloud stance
  34. Managed service versus self-hosted open source
  35. Final platform recommendation and decision record
  36. Scripted vendor demo day
  37. Customer reference calls for the finalists
  38. Steering committee decision meeting
  39. Contract negotiation and signature
  40. Selection to implementation handover
  41. First data platform for a small team
  42. Enterprise procurement and architecture board route
  43. Consolidating data platforms after a merger
  44. Business case for finance approval
  45. Responding to a large incumbent price rise
  46. Platform selection under data residency rules
  47. Multi-engine lakehouse with a shared catalogue
  48. Workload placement rules across engines
  49. Enterprise commitment structure negotiation
  50. Reusable platform evaluation playbook

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Platform selection charter and decision owner

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Platform choices drift for months when nobody has written down what is being chosen, who decides and by when.

First tasks

  • Write two sentences on why the current platform is being questioned now
  • Name the single person who will make the final platform call
  • Agree the budget envelope with finance before any vendor conversations
  • Circulate the one-page charter to the sponsor for approval

Current data estate and tool inventory

Every comparison needs a starting point: what you run today, what it holds and what depends on it. A complete inventory of sources, storage volumes, pipelines, BI tools and downstream consumers shows how much has to move, which integrations a new platform must support and where the undocumented dependencies sit.

First tasks

  • Export the list of connections and service accounts from the current warehouse
  • Ask each BI tool admin for active user counts over the last ninety days
  • Record storage volume and monthly growth for each major schema
  • Interview two engineers about integrations that are not documented anywhere
  • Refresh the inventory before the annual platform fit review @recurring(yearly)

Workload profile from twelve months of query history

Vendors size and price against a workload, and if you cannot describe yours they will describe it for you. Mining the current platform's query history for data scanned, concurrency at peak, the spread of query durations and the split between dashboards, scheduled transforms and ad hoc work gives every sizing, benchmark and cost estimate the same honest base.

First tasks

  • Check how many days of query history the current platform retains
  • Group last year's queries by user type and scheduling tool
  • Find the busiest hour of the busiest week and count concurrent queries
  • List the twenty slowest recurring queries with their run times
  • Re-run the workload profile queries to catch shifts in usage @recurring(quarterly)

Make it yours.

Install Cloud Data Platform Selection, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.