Run a city on one operating picture — across every department.
Permits, transport, public works, social services, 311 calls, police, fire, public health. Each department keeps its own systems. Djeed reads what each one records, resolves the cross-department picture, and turns scattered signals into operations city hall can act on. The same shape works at a governorate or district level, federated with a national deployment if your country has one.
The operating view
Every department in motion. One city, one picture.
Each department's live signals plot onto a single map of the city. The 311 spike in the north, the permit backlog in the northeast, the flood watch in the southwest — visible together, on one screen, the moment they start.
Inside a city
Many sub-entities report up. Each keeps its own data.
A city or governorate isn't a single organisation — it's a federation of district councils, public corporations, utility boards, school authorities, local agencies and regional offices. Each runs its own systems, keeps its own ontology, holds its own data. Each reports up — but the city manager and the council only see what each entity chose to share, in the format each entity chose to share it.
Djeed reads each sub-entity's record, resolves the entities across them — the same parcel, the same citizen, the same business — and turns scattered ledgers into one operational record. One dashboard. One audit trail. The same picture for the City Manager, the council, the auditor, the citizen.
- District & neighbourhood councils
- Public corporations (transit, water, energy)
- Utility & sanitation boards
- Local school & education authorities
- Cadastre & land-registry offices
- Regional health authorities
- Local security & civil defence
- Heritage, parks & cultural agencies
Each with its own ontology · its own data
Djeed reads each sub-entity's system and resolves the cross-entity picture. The same citizen, parcel and business across every ledger becomes one record — with each source kept and each ontology preserved as a view.
The City Manager sees
- Every department's live signal · in one place
- Every sub-entity's record · resolved + traceable
- Every cross-entity pattern · surfaced as it forms
- Every brief · sourced back to the records under it
One dashboard · all sub-entities · audit trail public
What it unlocks
Capabilities one department alone could never deliver.
Once the cross-department record resolves into one picture, the things city hall could only do on heroic effort become routine. None of these are possible when every department can only see itself.
Resilience early warning
Floods, heat waves, outages and disease clusters caught in the cross-department signal — before the call-centre spike, before the press call, before the emergency budget request.
Service-delivery oversight
Permit backlogs, 311 response times, ageing complaints, repeat callers — surfaced across every department on one screen. The City Manager sees the bottleneck the day it forms, not in the next council session.
Citizen-centric records
One citizen, one record, across every interaction — permits, services, complaints, tax, housing. The same person stops being treated as a stranger in every department.
Capital planning
School-age projections, housing demand, transport load, healthcare registrations — unified for capital decisions that match where the city is actually growing, not where it grew last decade.
Council and committee briefings
Mayor briefings, committee papers, public reports — assembled from records city staff already keep. Every figure links back to its source department.
Public transparency
An audit trail any citizen, ombudsman, council member or auditor can follow. The same lineage the City Manager reads is the lineage published in the open data portal.
Early warning · A real scenario
A flood event that's contained, not a surprise.
The same storm, surfaced across four departments' data over three days. On separate ledgers, each signal looks like routine business. On the canonical city record, the risk projection lands a full day before the rain — and city hall has time to position sandbags, issue alerts, and pre-stage the evacuation plan.
Heavy-rain watch issued for the basin
Meteorology · rainfall forecast
Signal · isolated
Drainage capacity flagged in southwest districts
Public Works · storm-drain register
Signal · isolated
District risk projection — sandbags, alerts, evacuation
Cross-department overlay
Pattern caught
Storm event · contained, not a surprise
Public Works · response log
Contained · not a surprise
On Day −1, the cross-department risk projection lands. Public Works pre-positions sandbags in the flagged districts; Civil Defence stages the evacuation plan; 311 gets a briefing for the inbound calls. When the storm arrives on Day 0, the city has already moved — and the response gets reported, not asked for.
Connected to
Every department keeps the systems it already runs.
Djeed reads what's already there — without any department being asked to migrate, switch vendors, or hand over the primary system of record. Each department's existing ontology is preserved as a view; the canonical city record sits on top, not in place of.
The list opposite is illustrative — actual sources are scoped per city during a discovery engagement, against the city's privacy and records- management posture.
The five solutions, at city scale
The same flow. Sized for a city.
The five Djeed solutions are the same here as anywhere else — only the scale, the data sensitivity, and the deployment shape change.
Data & Ontology Foundation
Reads what every department already records. Reconciles their ontologies — permit records, work orders, 311 cases, citizen files — into one canonical model the whole city hall can act on.
Graph & Spatial Intelligence
The canonical record, navigable across departments and across the city map. Every entity tied to a parcel, district, or neighbourhood, so any question resolves to a place — not a spreadsheet.
Predictive & Generative AI
Forecasts grounded in cross-department data — service demand × demographic change × seasonal load. Generative answers traceable to records, not models trained on the open web.
Operational Intelligence
Continuous monitoring across the whole city record. The 311 spike in District 4 surfaces the day it starts — not in the next quarterly review.
Decision Intelligence
Council briefings, mayoral briefs, committee papers assembled from records you can trace. The auditor and the ombudsman read the same lineage as the analyst.
For the technical reader — full per-solution detail at /solutions.
Where it runs
On your infrastructure. In your jurisdiction.
Djeed deploys on your city's data centre, on a sovereign cloud region inside your country, in a hybrid shape, or federated with your country's national knowledge foundation. The data never leaves a jurisdiction your council and your General Counsel are comfortable with.
On your city's own infrastructure.
Djeed runs in the city hall's data centre. The classic shape for governorates and large cities with established IT capacity. No external network egress required.
In-jurisdiction cloud region.
Hosted on a sovereign cloud region within your country. Faster to start than on-prem; same legal posture. The deployment most cities choose for their first programme.
Sensitive on-prem, intelligence in cloud.
Police records, social-services case files, tax records stay at the department that owns them. The cross-department picture runs in the cloud above. Sensitive data never moves.
Plug into the national knowledge foundation.
If your country has a National Knowledge Foundation deployment, the city joins as a node in that federation — sharing the canonical ontology, keeping local data custody.
Trust + transparency
The audit trail is the public trail.
Every record knows where it came from.
Source department, original case ID, capture timestamp — attached to every record. Not in a side log; in the record itself.
Every brief shows its work.
A council paper or mayoral briefing can be unfolded to the records under it. The auditor reads from the figure on the page to the row in the source department's database, without going through the analyst.
The same trail the public can follow.
Records released to the open data portal carry the same lineage internal users see — modulo the privacy redactions the law requires. The audit trail is the public trail.
How a deployment starts
A department pilot, or a city-wide programme.
Settle the shape, then expand.
Pick the department whose cross-cutting issues are most urgent — often Public Works, 311, or Permits — and run a focused engagement. One department connected, one cross-department brief live in production, the deployment shape and privacy posture proven before the wider rollout.
- One department connected, live in months
- Privacy + records-management posture proven before expansion
- Each next department compounds on the foundation already laid
Every department, phased.
For cities and governorates ready to commit to the operating picture from day one — a phased programme across every department, sequenced so the high-volume sources (311, Permits, Public Works) land first and the long tail joins as their data is ready.
How a city-wide programme is scoped →FAQ
Questions a City Manager asks first.
Does this require us to centralise our departmental data?
+
Does this require us to centralise our departmental data?
+No. Every department keeps its own primary system of record, its existing ontology, and its data custody. Djeed reads and reconciles a cross-department picture on top of what each department already runs — it doesn't take ownership of any department's data.
How does this work with our 311 / citizen-services system?
+
How does this work with our 311 / citizen-services system?
+Djeed reads from the 311 record alongside the other departments' records. The citizen-services team keeps their dashboards, their workflows, their reporting. Djeed adds the cross-department view: the 311 call that's actually a permit-process issue, the recurring complaint that maps to a public-works backlog, the patterns 311 alone couldn't see.
What if our departments have different IT vendors and old systems?
+
What if our departments have different IT vendors and old systems?
+Expected. Most cities have a mix of legacy and modern systems across departments — a 20-year-old permit system, a recent transport platform, a custom social-services case-management tool. Djeed reads what each one produces; the connector work is scoped per system during a discovery engagement.
Can the council, the auditor and the ombudsman use the same system?
+
Can the council, the auditor and the ombudsman use the same system?
+Yes — each as a role with appropriate scope. The council gets briefings + drill-down for oversight; the auditor gets the immutable audit trail; the ombudsman gets the citizen-record view (subject to privacy law). All read from the same canonical record, with role-based visibility.
Can we federate with our central government's deployment?
+
Can we federate with our central government's deployment?
+If your country has a National Knowledge Foundation in place, the city joins as a federation node — same canonical ontology, local data custody. If it doesn't, the city deployment can become a reference for future national rollout. Either direction works.
What's the deployment timeline?
+
What's the deployment timeline?
+Pilot one department live in months — typically Public Works, 311, or Permits, whichever has the most cross-cutting cases. First cross-department brief in production a quarter or so after. Full city integration is a programme measured in quarters, scoped against the city's existing capital plan.
Run your city on one operating picture.
Tell us about your city or governorate and the cross-department issue you'd resolve first. We'll show you what the canonical city record would look like — and the deployment shape your privacy posture allows.