Illustrative case study · methodology first

How a cultivation campus can be screened for a dedicated AI conversion

An anonymized, document-informed example of the questions, working assumptions, and independent checks behind a complete change of use. It is not a live opportunity or a conclusion about any property.

Anonymous illustrative caseNo live offering data

Document record

Independent checks

Conversion design

Decision

The process moves from an abstracted record through property-specific checks and a separately engineered design. It does not presume a favorable decision.
On this page

01 · Decision frame

What this case illustrates

Existing industrial infrastructure can create a reason to investigate; it does not establish transferable utility capacity, AI-ready cooling, network service, approvals, condition, schedule, economics, or transaction availability.

The question

Could a fully vacated cultivation campus be redesigned for a defined, sustained AI deployment?

The answer remains unestablished until utility, engineering, approvals, condition, network, cessation, and transaction diligence are complete.

The boundary

This is a complete change-of-use example.

Cultivation must cease, and the new use must be separately designed and approved. This is not a co-located cannabis-and-compute model.

02 · Provenance before persuasion

Reported conditions vs. what remains unproven

The confidential source record gives this example a starting point. It does not make the property AI-ready. The required checks are evidence gates, not a to-do list that the property is known to satisfy.

Document-derived · not independently verified

Large multi-building industrial cultivation envelope

Potential reason to investigate: It may provide a starting shell and staged-space concept.

Must be independently verified

Do not infer

A data-hall layout, structural capacity, white space, or usable cooling.

Required verification

Measured drawings, structural review, equipment layout, and code/life-safety review.

Document-derived · not independently verified

Existing electrical infrastructure

Potential reason to investigate: It may justify an early utility and electrical screen.

Must be independently verified

Do not infer

Available megawatts, voltage class, redundancy, tariff, timing, or a right to serve new load.

Required verification

Current written utility input, one-line review, protection study, field assessment, and a service agreement as appropriate.

Document-derived · not independently verified

Cultivation mechanical pathways and equipment areas

Potential reason to investigate: They may inform a new heat-rejection and routing study.

Must be independently verified

Do not infer

Reuse of equipment, AI-duty performance, water strategy, or PUE.

Required verification

Mechanical and thermal design, roof/slab assessment, controls review, weather/water strategy, and a maintainability plan.

Document-derived · not independently verified

Industrial access, perimeter security, and civil features

Potential reason to investigate: They may inform logistics and site-planning review.

Must be independently verified

Do not infer

Suitability for heavy equipment, generator/noise/air permits, drainage acceptance, or security compliance.

Required verification

Civil, environmental, logistics, fire, security, and applicable-authority review.

03 · Complete change of use

Illustrative conversion scope

The workstreams show how a team could organize a screen without prescribing a design for the anonymous campus. Each conceptual scope remains subject to its matching gate.

  1. Retire and clear the former use

    Planning assumption

    The illustration assumes cultivation fixtures, irrigation, CO₂ and odor controls, and unneeded branch circuits may be removed.

    Must be independently verified

    Cessation, asset ownership and disposition, hazardous-material/environmental review, and safe decommissioning must be assessed.

  2. Rebuild the electrical path for the defined deployment

    Planning assumption

    The illustration assumes utility coordination, service equipment, transformers, UPS, standby power, distribution, grounding, and controls may be needed.

    Must be independently verified

    No existing equipment is represented as suitable or reusable; service and equipment condition require written and field confirmation.

  3. Design heat rejection and compute support

    Planning assumption

    The working case uses a hybrid architecture to test dense liquid-ready compute alongside conventional support loads.

    Must be independently verified

    Capacity, redundancy, water strategy, structural loading, piping, controls, and maintenance must be engineered.

  4. Complete life safety, network, and operational commissioning

    Planning assumption

    The illustration assumes scope for fire/life safety, diverse network entry, access/security, commissioning, load testing, and operating procedures.

    Must be independently verified

    Approvals, carrier routes, commissioning criteria, and the operating model are not established.

Planning assumption

Planning scenario, not site capacity. The values below organize an educational conversion case. They do not represent delivered utility load, usable IT capacity, an engineering design, or a project commitment.

Illustrative planning envelope

Planning assumption

Illustrative IT-load envelope

2.0–3.5 MW IT

Planning assumption

Illustrative facility-input envelope

~2.8–5.0 MW

Planning assumption

Efficiency input used to relate the two

PUE 1.35–1.45

Planning assumption

Illustrative facility input = illustrative IT load × illustrative PUE

Actual limits can be set by utility service, service gear, electrical protection, cooling, white space, redundancy, equipment selection, permitting, and operating criteria. This page does not model any of those limits for the anonymous campus.

Open the capacity planner with your own documented inputs
Planning assumptionSee the illustrative sequence

The source scenario used an 18–22-month illustrative path from commitment to first energized deployment. This is a planning assumption, not a schedule commitment or an estimate for the anonymous property. The critical path can change materially when written utility scope, procurement, approvals, or field conditions change.

1. Define and investigate

Illustrative activity
Buyer deployment definition, cessation path, site/condition review, utility and network inquiries
Controlling dependency
Access to current records and written counterparty and utility responses

2. Design and procure

Illustrative activity
Coordinated electrical, mechanical, civil, fire/life-safety, and network design; long-lead procurement strategy
Controlling dependency
Defined scope, design maturity, vendor availability, and approvals

3. Build and commission

Illustrative activity
Decommission, construct, test, commission, and energize in phases
Controlling dependency
Equipment delivery, construction conditions, inspection, utility work, and integrated testing

4. Initial deployment

Illustrative activity
First energized deployment after completion criteria are met
Controlling dependency
Utility delivery, acceptance testing, operations readiness, and tenant/hardware plan

04 · Bounded cost method

Illustrative retrofit-cost methodology

One category-based range is shown to make the planning arithmetic inspectable. It is not a cost estimate, a cost comparison, or a property-specific conclusion.

Planning assumption

Illustrative retrofit budget

$10.5M–$18.4M

Illustrative 2.5 MW IT scenario; approximately 3.5 MW facility input at PUE 1.4.

A category-based 2026 planning illustration. It is not a bid, appraisal, valuation, investment recommendation, or prediction of actual project cost.

Planning assumptionSee methodology, arithmetic, and exclusions
Planning assumption

Electrical and power

$5.5M–$8.0M

Allowance for potential utility/interface work, service equipment, transformers, standby power, UPS, and internal distribution. It does not establish utility scope or existing-equipment reuse.

Planning assumption

Cooling systems

$1.5M–$3.5M

Allowance for a conventional-to-hybrid cooling pathway. Final architecture, heat density, water strategy, redundancy, and equipment selection are unestablished.

Planning assumption

Structure and envelope

$1.0M–$2.0M

Localized assessment or possible reinforcement, interior change work, and security hardening. This is not a structural conclusion.

Planning assumption

Site and civil

$0.5M–$1.2M

Allowance for potential equipment-yard work, pads, grading, and drainage modifications, subject to civil, environmental, and authority review.

Planning assumption

Fire and life safety

$0.4M–$0.8M

Allowance for new data-hall and support-space life-safety scope. The appropriate design and code path have not been established.

Planning assumption

Network and connectivity

$0.15M–$0.5M

Allowance for potential lateral, diverse-entry, and meet-me-room scope. Direct service and routes are not represented.

Planning assumption

Soft costs

$1.2M–$2.0M

Planning allowance for appropriate design, studies, commissioning, permitting support, and management. It does not identify providers or a complete professional-services scope.

Planning assumption

Decommissioning and abatement

$0.2M–$0.4M

Planning allowance for removing former-use equipment and evaluating potential cleanup. Environmental conditions are unknown.

Planning assumption

Illustrative total

$10.5M–$18.4M

Rounded sum of the individual category ranges: low end $10.45M; high end $18.4M.

Planning assumption

How this range was formed. The illustration adds broad category allowances for a 2.5 MW IT planning case, then rounds the low-end sum from $10.45M to $10.5M. It is intentionally a wide preliminary range because the underlying utility scope, existing-equipment condition, design criteria, procurement strategy, local requirements, schedule, and field conditions are not known publicly.

Test a generic grow footprint against the same bounded planning logic. The calculator does not inherit any facts from this anonymous case.

Open scenario planner

05 · Stop/go evidence

Five verification gates

These are unresolved decision gates, not completion indicators. No readiness score, probability, or pass/fail outcome is implied.

Must be independently verified1. Utility and electrical service

What would close this gate?

  • Written utility response covering the proposed use, load, delivery point, timing, rate class (as applicable), and upgrade scope.
  • A current single-line diagram and a field review of service, protection, equipment condition, and maintainability.
Must be independently verified2. Complete cessation, control, and handoff

What would close this gate?

  • Lawful cultivation cessation and an asset-removal plan.
  • Property-control and consent diligence with a clear operating boundary.
Must be independently verified3. Building, thermal, environmental, and life safety

What would close this gate?

  • Structural, mechanical, environmental, fire/life-safety, code, and site/civil reviews tied to the actual equipment plan.
Must be independently verified4. Network, operations, and resilience

What would close this gate?

  • Carrier and path survey, network design, security and operations model, maintenance plan, commissioning criteria, and continuity design.
Must be independently verified5. Approvals and transaction viability

What would close this gate?

  • Applicable-authority review, contractual path, insurance and lender requirements, procurement plan, and definitive agreements.

A gate may uncover a reason to stop. That is a valid screening outcome—not a failure of the process.

Build a local draft that tracks evidence status; nothing is uploaded, and no counterparty is contacted.

Start a buyer site screen

06 · Accountability

Sources, methodology, and limitations

The source boundary is part of the method. Confidential material is neither linked nor exposed, and no unreviewed public source is presented as evidence about the anonymous campus.

Document-derived · not independently verified

Study basis

Broad, redacted conditions were abstracted from a confidential development record. UNICANN has not represented this record as independently verified, current, complete, or suitable for a new use.

Planning assumption

Scenario method

The capacity, PUE, sequencing, scope, and cost figures form an illustrative 2026 planning case assembled from category allowances. They are not site measurements, market offers, engineering calculations, or transaction terms.

External benchmark · context only

External context

Public industry material can explain common adaptive-reuse workstreams. It cannot determine the anonymous campus’s price, power, schedule, approval path, or suitability.

Must be independently verified

Reliance limit

A decision requires current property-specific evidence and appropriately qualified review.

External benchmark · context onlyView public context sources and source-use notes

No external source links are published on this reviewed page. A source will be listed only after editorial and legal review has verified its direct public URL, publisher or author, publication date, review date, and narrow conceptual use. Any future entry must state: “Not used to establish facts about the anonymous campus.”

The confidential development record, internal files, source-page images, and any material that could reveal a location or participant will not be linked, previewed, or made available through this page.

Role handoffs

Continue with your own evidence—not this case’s assumptions.

A viable outcome is not presumed. The right result may be a redesigned deployment path, a longer diligence process, or a decision not to convert. The purpose of the screen is to discover that early, with evidence.

For infrastructure buyers

Start with a buyer-defined deployment.

Build an evidence checklist without carrying over any values from the case study.

Evaluate a powered site
Continue to protected intake only after completing a role-specific screen. Do not send confidential source records unless the intake channel expressly confirms that it is active and that sending them is appropriate.