Skip to main content
STRIPED DONKEYWe do the heavy lifting.

Nairobi · Utilities & digital city

Energy.
Explore electricity connection records.

Explore connection status, tariff context and contracted load before reviewing the wider service and reliability scope.

Public sample available

Published domain facts

Complementary electricity perspectives
2
Active Connections
1,410,787
Municipal/public-facility energy context
Scoped
Structural + realism certification checks pass
18/18

Overview

Domain scope

Explore connection status, tariff context and contracted load before reviewing the wider service and reliability scope.

Read the published guide →

Known limits

Electricity context supports urban analytics, not power-system simulation. Nairobi lacks equivalent direct Business service links; another referenced capability remains incomplete. Deployed, certified behavior takes precedence over forward-looking specifications.

Review the source limits →
Full scope reference 2 documented sections
Published domain scope.

Published domain scope.

Inspect electricity access, tariffs, billing and outages. Household and commercial relationships follow each city’s published coverage.

  • Compare connection and tariff categories
  • Inspect connection dates and service status
  • Review load and household context
Complementary electricity perspectives
2
Active Connections
1,410,787
Municipal/public-facility energy context
Scoped
Structural + realism certification checks pass
18/18
Domain scope.

Domain scope.

Inspect the published scope and deployment boundaries.

Read the published detail

FCTE represents electricity through two complementary service perspectives : a grid-to-customer layer for household access, billing and outages, and a municipal/public-facility layer for infrastructure and service context. The public site shows their analytical relationship without exposing internal data design.

In the current Nairobi release, household electricity is represented directly while business-linked electricity is not asserted as an equivalent identity relationship. That boundary is disclosed without exposing internal source fields or internal paths.

Every public claim is grounded in release evidence, regulatory context or certification. Representative relationships are shown for evaluation; internal data structures and engine internals are not published.

Nairobi City Twin™

Samples & fields

Published sample records.

Public sample · rows and field definitions

Public sample

Consumer category codeTariff class codeConnection typeConnection dateConnection statusContracted power capacity (kVA)Household typeHousehold reference
RESIDENTIALDC2_ORDINARYResidential Three-Phase2025-04-19Active7.50Nuclear1437577
RESIDENTIALDC2_ORDINARYResidential Single-Phase1961-01-10Active7.50Nuclear1544622
RESIDENTIALDC2_ORDINARYResidential Three-Phase1962-02-26Active9.50Nuclear1235834

Showing 3 of 100 sample rows and 8 of 9 fields. “Not recorded” is a display label; downloads retain original values.

Published field definitions · 8 visible fields

Consumer category code

The published code identifying the consumer category. Codes are retained as supplied in the source.

Original field: ConsumerCategoryCode
Example: RESIDENTIAL

Tariff class code

The published code identifying the tariff class. Codes are retained as supplied in the source.

Original field: TariffClassCode
Example: DC2_ORDINARY

Connection type

The category or type assigned to the connection in the source record.

Original field: ConnectionType
Example: Residential Three-Phase

Connection date

The date recorded for the connection event.

Original field: ConnectionDate
Example: 2025-04-19

Connection status

The state recorded for the connection in this extract.

Original field: ConnectionStatus
Example: Active

Contracted power capacity (kVA)

The contracted electrical capacity recorded for the connection, in kilovolt-amperes.

Original field: ContractedLoadKVA
Example: 7.50

Household type

The recorded household structure, such as a single-person or extended household.

Original field: HouseholdType
Example: Nuclear

Household reference

The reference used to identify the household associated with this record.

Original field: HouseholdId
Example: 1437577

Complete published field dictionary · 9 fields
HouseholdIdHousehold reference
The reference used to identify the household associated with this record.Example: 1437577
WardIdWard reference
The reference used to identify the ward associated with this record.Example: 13
HouseholdTypeHousehold type
The recorded household structure, such as a single-person or extended household.Example: Nuclear
ConsumerCategoryCodeConsumer category code
The published code identifying the consumer category. Codes are retained as supplied in the source.Example: RESIDENTIAL
TariffClassCodeTariff class code
The published code identifying the tariff class. Codes are retained as supplied in the source.Example: DC2_ORDINARY
ConnectionTypeConnection type
The category or type assigned to the connection in the source record.Example: Residential Three-Phase
ConnectionDateConnection date
The date recorded for the connection event.Example: 2025-04-19
ConnectionStatusConnection status
The state recorded for the connection in this extract.Example: Active
ContractedLoadKVAContracted power capacity (kVA)
The contracted electrical capacity recorded for the connection, in kilovolt-amperes.Example: 7.50
Download complete field guide JSON ↓
Additional records and schema context 1 documented sections
Inspect the published utility surface.

Inspect the published utility surface.

Inspect the published definitions and release context.

Read the published detail

The public site documents the modeled utility entities, regulatory anchors and certification maturity. Internal generation workflows, sequence and orchestration are not published.

Connections

Known and possible relationships

Inspect the published definitions and release context.

Domain or contextRelationship and published scope
Grid / utility contextservice access
Service accessHousehold
ServiceArea / Ward
Direct business identity linkagenot asserted in the Nairobi release
Reliability eventsservice area
Full relationship reference 1 documented sections
Known and possible relationships.

Known and possible relationships.

Inspect the published definitions and release context.

Read the published detail

Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.

Domain or contextRelationship and published scope
Grid / utility contextservice access
Service accessHousehold
ServiceArea / Ward
Direct business identity linkagenot asserted in the Nairobi release
Reliability eventsservice area

Domain guide

Energy · archived guide edition

Striped Donkey V5.89 - 7 September 2026

Counts, prices and “live/today” certification statements reflect this dated edition. They are not a current rerun or offer. The current scope, known limits and accepted quote take priority.

Published scope and limits

Electricity context supports urban analytics, not power-system simulation. Nairobi lacks equivalent direct Business service links; another referenced capability remains incomplete. Deployed, certified behavior takes precedence over forward-looking specifications.

Read the source limits →
Accessible HTML reference 4 documented sections
Modelled entities.

Modelled entities.

Explore the entities and states represented by this domain.

Read the published detail

FCTE's Energy domain combines complementary analytical perspectives that were built for different questions. The public site presents the shared data model while keeping physical table layouts, field mappings and generation dependencies private.

Residential, commercial and service categories describe who receives electricity and under what service context.

Household service context is represented directly; equivalent business identity linkage is not asserted for this release.

Generation, transmission, distribution and alternative-supply context support city-scale energy analysis.

Longitudinal consumption and billing context supports affordability, demand and service analysis.

Grid and utility assets provide the physical context beneath electricity service. See Infrastructure → .

Outage, restoration and service-quality context allow access and reliability to be studied separately.

━━ Public semantic relationship · ┄┄ Disclosed boundary.

  • Customer service and metering context
  • Household linkage represented in the release
  • Area-level outage and demand context
  • Public-facility consumption and infrastructure context
  • Area-level reliability and maintenance context
  • Residential/commercial identity coverage is intentionally separate
Follow electricity service into one household.

Follow electricity service into one household.

Inspect the published definitions and release context.

Read the published detail

This public traversal shows the service lifecycle semantically. Exact assignment rules, generation order, starting configurations, workflows and internal orchestration are not published.

The Nairobi release represents electricity as a connected longitudinal service context. The public page shows the analytical chain and certification outcome; internal mechanics remain controlled.

Electricity access is useful only when service quality is visible too.

Electricity access is useful only when service quality is visible too.

Inspect the published definitions and release context.

Read the published detail

A ward-level electrification indicator provides an analytical view of service access. The public site exposes the indicator and regulatory context, while exact source joins, denominator construction and generation model targets remain controlled.

Metering and billing are represented in the release; full certification execution (18/18 checks) is complete for Nairobi and reported as such.

Access and reliability remain deliberately separate concepts: a household can have electricity service and still experience outage or restoration events. Exact event-generation distributions and calibration thresholds are not public.

Release-backed utility model and regulatory evidence.

Release-backed utility model and regulatory evidence.

Review the documented generation rules and assumptions.

Read the published detail
Public entity familyRepresentsDisclosure boundary
Energy service contextHousehold/business access and service-status contextExact access targets and assignment rules are controlled
Metering & billing contextConsumption and billing relationships through timePhysical meter/billing data structure and formulas are controlled
Network asset contextGeneration, transmission and distribution contextPhysical network topology is not published
Reliability & maintenanceOutage, maintenance and service-quality contextOperational simulation mechanics are controlled

Evidence & limits

Scope and known limits

Electricity context supports urban analytics, not power-system simulation. Nairobi lacks equivalent direct Business service links; another referenced capability remains incomplete. Deployed, certified behavior takes precedence over forward-looking specifications.

Evidence, findings and release history 2 documented sections
Known limits.

Known limits.

Electricity context supports urban analytics, not power-system simulation. Nairobi lacks equivalent direct Business service links; another referenced capability remains incomplete. Deployed, certified behavior takes precedence over forward-looking specifications.

Read the published detail

FCTE stores plausible grid, demand and service context for urban analytics; it is not a power-systems solver and does not claim voltage-drop, phase-balancing or grid-stability simulation.

The Nairobi release supports household electricity and municipal/public-facility energy, but does not claim an equivalent direct business-linked service relationship.

A related capability referenced by the model is not complete in this release. FCTE reports the resulting coverage boundary rather than presenting the planned capability as delivered functionality.

Where forward-looking specifications and the deployed release differ, the marketplace relies on the deployed, certified behavior and does not expose speculative internal fields as public functionality.

Back to Domain Directory →

Reported checks for the documented Nairobi release.

Reported checks for the documented Nairobi release.

Inspect the published definitions and release context.

Read the published detail

The documented Nairobi release reports 13 structural checks and 5 realism checks, with all 18 reported as passing.

Lagos's Energy certification has not yet been run against a populated release — this result covers Nairobi only.

Access & datasets

Scope your data request

Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.

Published access and recorded examples 1 documented sections
Recorded example.

Recorded example.

Published release reference · These recorded checks are not a current rerun.

Explore the supplied synthetic example and its source references.

Read the published detail

A real Connection row, connected 1947-06-10 — 1,410,787 published on Nairobi.

A real Outage row affecting 3,683 customers — one of 134,258 real, dated outage records on this domain.

Municipal energy provides a separate operations perspective.

A direct business identity relationship is not asserted for the current Nairobi release.

Electricity service is presented as a semantic city relationship; the internal dependency design remains private.

Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™