// Methodology

How the data is sourced and scored.

Every fact in Cxdir traces back to something an operator, government agency, or trade outlet has already published. This page explains what that looks like in practice, how refresh scoring works, and how corrections happen.

// Sourcing

Publicly disclosed sources, all the way down.

Cxdir doesn't purchase leaked operational data, doesn't rely on private industry lists, and doesn't estimate figures the operator hasn't published. The rule is simple: if the source can't be pointed to publicly, the field stays empty.

Where a fact isn't public, we mark the field empty or annotate it explicitly. "Not yet researched" is a valid answer. Guessing isn't.

// Pre-operational pipeline

Tracking projects before they're built.

Cxdir tracks projects across four lifecycle stages: planned (announced or permits filed), permitted (permits approved, construction imminent), under construction, and operational. Pre-operational entries are the earliest signal in the pipeline — an announcement today is a commissioning conversation 18–30 months from now.

Sources for pre-operational tracking:

Where a project exists only as an announcement — no permit filings visible yet — the entry is marked planned. Once permits are on file and approved, it moves to permitted. This distinction matters: permitted projects are 12-18 months from construction; planned projects are 24+ months out and carry more uncertainty on the final scope.

// State-specific sourcing

Different states, different data structures.

Not every state consolidates pre-operational data-center data the way Georgia does. Cxdir tracks whichever authoritative source exists per market:

// Refresh scoring

Vintage-based scoring, refined by disclosure.

Every facility gets a refresh status derived from its opening year and typical equipment lifecycles: UPS batteries (5–8 years), UPS modules (10–15 years), generators (25–30 years with overhaul), switchgear (20–30 years), cooling systems (15–20 years).

When public disclosures surface a specific install year for a piece of equipment (from a vendor press release, permit filing, or expansion announcement), that individual asset gets scored separately in the intel layer and can override the facility-level default.

Fresh
Less than 50% through expected life. No refresh action needed.
Monitoring
50–70% through. Track for early planning signals.
Approaching
70–90% through. Refresh window opening in 2–5 years.
Due
Inside the refresh window now. RFP likely within 12–24 months.
Overdue
Past expected end of life. Refresh work is either underway, deferred, or already extended past design.
// Note

Refresh status is a signal, not a guarantee. Facilities routinely operate equipment past design life through maintenance regimes, partial upgrades, and asset-by-asset replacement. The score says when the conversation should be happening, not when equipment will fail.

// Why equipment specs stay private

The intel layer isn't public — deliberately.

Detailed equipment inventories, install years, GC of record, and Cx history are visible only in the private intel layer. Two reasons:

1. Operator relationships. Publishing a full equipment inventory publicly would make Cxdir hostile to the very operators whose cooperation we depend on for accurate data. Keeping the detailed layer private lets operators claim their listings without exposing operational information they'd rather not broadcast.

2. Signal integrity. The commercial value of the intelligence layer depends on its scarcity. Once refresh timing is public, it's already too late for the parties who paid to see it early.

// Corrections

How the data stays current.

Every facility page carries a Claim this listing action. Operators verify or correct their record; the update flows back into the dataset. Public disclosures — permit filings, press releases, M&A announcements — are monitored and folded in on a rolling basis.

Spot something wrong or want a facility added? hello@cxdir.com. Include the source. Corrections with sources move fast.

Questions on methodology, or want to discuss commercial access to the intel layer?
hello@cxdir.com