Use case · Digital twins · 2 min read

The structured bed beneath a campus twin

A digital twin is only as live as the input it consumes. Djeed turns the filings, sensor logs, and incidents around a campus into typed records the twin can read — so the model stays current as the real thing changes.

Why twins drift

A campus twin is rendered once and starts drifting almost immediately. New permits land, equipment incidents are filed, occupancy and use change, and the inputs that would keep the model honest live in places the twin cannot read.

Djeed restructures the same inputs into typed records with stable schemas — the twin's contract for what it can consume. The feed is continuous; the structure is the same every time.

What the twin team gets back

A stable, typed feed of records the twin can read directly — permits, incidents, sensor events, occupancy and use changes. The twin team focuses on the model; Djeed keeps the underlying input current and structured.

  • · Typed records on a stable schema the twin can consume
  • · Permits, incidents, sensor events, and use changes in one feed
  • · Continuous refresh — the model stays current with the real thing
  • · Every record keeps its source, so updates are auditable

How it works

  1. 1

    Connect the inputs

    Connectors pull from the permit system, incident reports, sensor logs, and the open record around the campus.

  2. 2

    Djeed produces the typed feed

    Every input becomes a record on a stable schema. Records are deduplicated, time-stamped, and source-linked.

  3. 3

    The twin consumes it

    The twin team reads from the feed via the workspace API. The model stays current as the records arrive.

What you connect

  • · Permit and works records — filings touching the campus
  • · Incident reports — equipment, safety, and operations events
  • · Sensor and telemetry logs — continuous numeric input
  • · The open record — news and filings around the campus

Common questions

Does Djeed run the twin?

No. Djeed produces the typed feed underneath it. The twin model and renderer stay with the team that owns them; Djeed makes sure the input is current and structured.

Can the schema change over time?

Yes — the schema is versioned, and the team that owns the twin decides when to consume a new version. Older records remain readable through the prior schema until the model migrates.