Sector and market
Salt Lake City Data Center Owner-Side Review
Salt Lake City and the Wasatch Front include urban, suburban, and industrial properties set within a distinctive mountain valley context. Winter conditions, dry periods, local water considerations, and parcel-specific utility arrangements all merit project-level confirmation. An owner should avoid treating a metro-wide description as evidence of a site's service availability, approvals, or construction sequence.
Project Value Advisors reviews data center budgets, proposals, commercial scope, procurement, and owner decisions. PVA can make assumptions and responsibility boundaries easier to compare while the applicable provider, operator, local professionals, and licensed engineers confirm service, approvals, and technical performance. The work is owner-side advisory, not engineering or utility planning.
Establish parcel-specific infrastructure status
For power, water, access, drainage, and other site dependencies, record the source, confirmation status, conditions, responsible party, and next action. Confirm which provider and local process apply to the selected parcel. Keep a planning assumption separate from an executed commitment, and show which procurement or schedule milestone depends on each unresolved item.
PVA can connect that information to the project budget, civil scope, equipment packages, and construction plan. This gives the owner a view of dependencies that may otherwise be split among consultant narratives and provider correspondence.
Review cooling and resource assumptions carefully
A dry regional climate and local water considerations make it important for the owner and operator to state the resource and operating basis for cooling. The licensed design team confirms technical requirements and evaluates solutions. PVA can compare how contractor and equipment proposals address the approved brief, including controls, interfaces, commissioning, service, and owner responsibilities.
Distinguish an operational requirement from a bidder's assumption or an option that remains unapproved. Track the evidence supporting each position and identify the person who can resolve an open question. That approach prevents commercial comparison from implying engineering acceptance and helps the owner see where additional confirmation is needed before an award.
Account for seasonal delivery and reliability decisions
Cold winters and dry, warm periods can influence site access, construction planning, and the operator's project-specific criteria. The responsible team establishes how those conditions affect work and operation. PVA can review schedule qualifications, temporary conditions, equipment protection, delivery access, storage, and readiness as commercial responsibilities rather than making technical determinations.
For reliability and expansion, define the owner's present requirement separately from future capacity or enabling provisions. Compare what is installed, what is reserved, and what remains undecided. PVA can help connect these distinctions to procurement, budget assumptions, warranties, and contract language so that the owner does not commit to a vague future scope.
Make procurement choices traceable
Normalize equipment proposals for included scope, exclusions, allowances, owner-furnished items, delivery, installation, commissioning, testing, warranty, and service. Show the source of schedule dates and any prerequisites for release. Where a utility or site action is outside the package, make the dependency clear rather than allowing it to disappear between the vendor and general contractor.
PVA can prepare a bid comparison, responsibility matrix, and decision summary for ownership and its advisers. The owner retains commercial authority; operators and licensed engineers decide whether technical requirements are satisfied.
- Site and provider assumptions documented by status
- Operator-defined cooling and resource criteria
- Seasonal delivery, equipment scope, and owner decisions
Relevant team-led work before PVA
Mixed-use project example
An approved team-led mixed-use example from before PVA was formed involved review of consultant and contractor agreements on a large development. It was not in Utah and did not concern data centers. Its relevance is the need to check whether contract responsibilities and handoffs match the work an owner expects. Salt Lake City owners can use that commercial lens for infrastructure dependencies and equipment packages while leaving resource, operational, and engineering determinations to the responsible specialists.
See the approved project examplesCommon questions
Frequently asked questions
Can PVA confirm water or power service for a Salt Lake City site?
No. The applicable provider and project professionals must confirm service, availability, conditions, and timing. PVA can record the evidence and explain how unresolved assumptions relate to scope, procurement, and schedule.
Does PVA design or approve a cooling approach?
No. The operator and licensed engineers establish requirements and validate technical design. PVA can review commercial proposals against the owner-provided basis and identify scope, responsibility, and contract questions.
How can an owner compare future expansion provisions?
Define current operating needs separately from planned future capacity, then identify installed work, reserved interfaces, assumptions, and items deferred. Technical feasibility is confirmed by the licensed team; PVA can make commercial commitments and owner decisions visible.
Start with the decision