Getting started
This guide explains the information and decisions involved in starting a deployment discussion. A public guide does not replace an agreement, authorize work, or grant access.
Essential information
A useful first review starts from four facts. Approximate answers are fine if they are labeled as approximate.
- Workload: what the infrastructure will run, and any hardware profile already selected
- Location: required geographies, proximity needs, and any jurisdictions that are excluded
- Scale: initial capacity and ultimate capacity, each with its unit (racks, kW, or MW)
- Timing: when service is needed, and which dates are fixed versus preferred
Confirmed versus estimated inputs
Mark each input as confirmed, estimated, or not yet determined. A confirmed hardware order and a planning assumption lead to different next steps, and treating an estimate as fixed can narrow options too early.
Hypothetical request: confirmed workload—batch model evaluation; confirmed geography constraint—within an approved jurisdiction; estimated scale—an initial rack count with equipment still being selected; estimated timing—a preferred quarter, not a fixed delivery obligation. Record unknown electrical and cooling requirements explicitly. The next review identifies candidate service models, missing equipment evidence, and delivery dependencies rather than accepting the estimate as a capacity reservation.
What the fit review produces
- An initial view of which service models fit the requirement
- Known constraints and open questions for each candidate environment
- The information still needed before a proposal can be scoped
- A suggested next step: technical review, briefing, or scoped proposal
Next steps
Use the capacity request form to submit the requirement. If you are still comparing service models, read the service catalog guide first.