An AI command centre for Pattaya City. It reads the city's records, residents' photos and Thai official letters, computes with tools and drafts the next step for a named official to approve. This is the working demo, on synthetic city data.
Anything not yet confirmed is marked “To be confirmed”.
The city
One city government, a bay, an island and two populations to serve.
Pattaya runs its own hospital, roads, drainage, waste collection, beaches and back office. Each service keeps its own records. The AI opportunity is to read across them, so officials see one picture and act earlier.
Special administrative city
Self-governing under the Pattaya City Administration Act B.E. 2542 (1999). Bangkok is the only other city in Thailand with this status.
Bay, beaches and an island
City limits run from Naklua through Pattaya Bay to Jomtien, and include Koh Larn offshore.
Residents and visitors
Hospital beds, bins and roads are planned for residents but also used by large numbers of visitors, and demand shifts with the season.
Rainy-season pressure
Heavy rain from roughly May to October brings flash flooding on low-lying roads and extra load on drainage crews.
General public information. Figures and baselines will come from Pattaya City departments during discovery.
01 · The issue
Five focus areas, one shared problem: data that doesn't reach the decision.
The issues listed under each area are working hypotheses to test with the departments that own them, not findings.
Stray dog management
✓ In this demo
Reports arrive by phone, social media and walk-in, with no shared register.
Hard to know which dogs are sterilised or vaccinated, or where bite risk is rising.
Catch, neuter, vaccinate and return (CNVR) teams plan their routes by hand.
AI opportunity. Photo reports matched to a dog registry, hotspot maps and planned CNVR rounds.
Internal operations
✓ In this demo
Official letters and memos are drafted, routed and tracked by hand.
Citizen requests land in many channels, and nobody sees which ones are about to go overdue.
Monthly and annual reports are compiled by hand from many spreadsheets.
AI opportunity. A Thai-language document assistant, request triage and routing, and reports that draft themselves.
City digital twin
✓ In this demo
Roads, drainage, assets, events and permits sit in separate departments and formats.
Flash flooding after heavy rain is handled when it happens rather than before.
Big events bring traffic congestion and crowd-safety risks, with little way to test "what if" in advance.
AI opportunity. One live map of the city with what-if scenarios for flooding, traffic congestion and crowd safety.
This demo has the rain what-if only, as an illustrative model. Traffic and crowds: to be confirmed.
Municipal hospital
○ Not in this demo: next version, to be confirmed
Patient demand swings with the tourist season and big events, so staffing is planned after the rush starts.
Patients speak many languages; intake and history-taking slow down at triage.
Discharge notes, referrals and insurance paperwork take clinician time.
AI opportunity. Arrival forecasts, multilingual intake and drafted discharge and referral documents.
Go Green
○ Not in this demo: next version, to be confirmed
Waste volumes jump with visitor numbers while collection routes stay fixed.
Island logistics on Koh Larn add cost and complexity to every service.
Water quality, energy and carbon figures are checked periodically and reported by hand.
AI opportunity. Waste forecasts with re-planned routes, water-quality alerts and an AI-drafted monthly sustainability report.
Use cases still open
Possible further use cases. Scope, owner and data are not confirmed yet.
Traffic and public safety TBC
Budget and procurement monitoring TBC
Hospital scope detail TBC
02 · The AI
AI-driven workflows that end with an official's decision.
Each workflow starts from something that already happens in the city: a report, a forecast, a letter. Models do the numbers, an AI agent joins the pieces and drafts the action, and a named official approves it.
1 The morning city briefing
The console opens on what changed overnight, what is at risk and what to decide today, across requests, stray dogs and rain.
DataCity records
Requests, dog reports, bite incidents and the real rain forecast for Pattaya are read when the console opens.
ModelSignals computed
Database counts, dog-report clustering, a deadline-risk model and the drainage model each raise a signal with its facts and its reason.
AI agentExplained and drafted
The agent writes the briefing from the tool output and drafts an action for each signal that needs a decision.
OfficialApprove, edit or reject
The duty officer decides on each draft; executives see the same picture.
OutcomeOn the record
Each decision is logged with who made it. Nothing is sent anywhere without approval.
Today
Each division keeps its own list. The overnight picture is pieced together from phone calls and chat groups.
With AI
One ranked picture at the start of the day, with the numbers, the reason and a draft ready to approve.
In the demo right now Synthetic data
9 signals now, 3 need a decision
224 open requests, 92 overdue
Tools the AI agent calls:morning_briefingcity_overviewquery_requestsdraft_action
A scanned Thai official letter is read, routed to the right division and answered in the official format.
DataA letter arrives
An officer uploads a scanned memo or external letter, or a PDF.
ModelRead the Thai text
The model reads the number, date, sender, subject, place, request type and urgency. Officers can correct any field.
AI agentRoute and draft
The request type sets the division and the deadline, the place is found on the road map, similar past requests are shown, and the AI writes only the body inside a fixed letterhead.
OfficialApprove and sign
The division head checks the routing and signs. Signing registers the request with its deadline.
OutcomeTracked to the deadline
The deadline board shows which requests are likely to miss their deadline this week, from a model over past requests.
Today
Staff read, sort and retype each request. Deadlines are tracked in spreadsheets.
With AI
Staff check and sign instead of retyping, and every request has an owner and a deadline.
In the demo right now Synthetic data
72 of 89 requests due in 7 days are likely to miss the deadline
Checked on 2 past dates: ranks requests that missed above those that didn't 71% of the time.
Reading and routing the synthetic sample letters (the set it was tuned on): division 20/20, place 20/20, run 13 Oct 2026.
Tools the AI agent calls:letters_inboxrequests_at_riskquery_requestsdraft_action
The use cases share one data layer and one set of AI services, so the second use case costs far less than the first. Data flows up; approvals and audit wrap every step.
What people useEach role sees its own view
In this demo Command centre, division head signing, a field team page and a resident chat.
IntelligenceModels compute, the agent reasons and drafts
In this demo Clustering, a deadline-risk model, a drainage model and round planning compute the numbers; the AI agent reads, explains and drafts in Thai and English.
Data layerClean, joined, protected
In this demo One PostGIS database: geo index, Thai text, role-based access and an append-only audit log.
City data sourcesExisting systems, connected not replaced
In this demo Real: OpenStreetMap roads and schools, the Open-Meteo rain forecast, Copernicus elevation. Synthetic: requests, dogs, letters and residents.
03 · The screens
Each role sees its own view.
The opening screen is a briefing, not an empty dashboard: what changed overnight, what is at risk and what to do next. Ask a question in Thai or English, and the answer comes back as tables, maps and drafted actions.
Duty officerCommand centre · /
City Hall control room, on shift. Morning briefing, map and assistant; approves drafted actions.
ExecutiveCommand centre · /
Mayor and senior management. Reads the briefing and asks the assistant; duty officers approve actions.
Division headCommand centre · /
Director of a city department, e.g. Public Works. Signs replies to official letters.
Field officerField page · /field
Stray-dog team B on the street (CNVR: catch, neuter, vaccinate, return). Visits stops in order, records each visit.
ResidentResident chat · /report
Member of the public. Reports stray dogs with a photo, as on the city's LINE account.
Hospital team: next version, to be confirmed. Decision support. Officials approve every action.
Show the idea working on synthetic data, so officials can react to something concrete.
Four workflows with a live AI assistant, in Thai and English
Synthetic records on real roads, terrain and rain forecast
Presentation walkthrough for the city
The demo runs on a Groovy Web server, not on city or Thai cloud infrastructure.
Pilot Scope TBC
One or two use cases on real data with one or two departments, running alongside today's process.
Data access and PDPA review
Connect to existing systems
Success measures agreed before start
Staff training and feedback loop
Duration, budget and team: to be confirmed.
Production Later
A city platform: more use cases on one shared data and AI layer, hosted in Thailand.
Command centre for executives
Digital twin with live feeds
On-premise or Thai cloud hosting
Support, monitoring and model updates
Procurement path: to be confirmed.
Which use case to pilot first? An initial view
Use case
Data readiness (assumed)
Delivery risk
Visible to residents
Suggestion
Stray dog management
Medium
Low
High
Pilot candidate
Internal operations
TBC
Low
Medium
Pilot candidate
Go Green, waste routes
Medium
Low
Medium
Second wave
Municipal hospital
Needs system access
Higher, clinical
High
Second wave
City digital twin
Needs GIS and drainage
Medium
Medium
Production phase
A first read, for discussion with Pattaya City. It will change once real data is available.
Measures to agree for the pilotRequest resolution time Baseline TBCOverdue requests per month Baseline TBCDogs sterilised and vaccinated Baseline TBCER wait to triage Baseline TBCOverflowing-bin complaints Baseline TBC
Built for a city government
Trust, data and what we still need to learn.
A public body will ask who decided, on what evidence and where the data lives. The design answers that from day one, and the list below is what we need from Pattaya City before a pilot.
The AI drafts, officials decide
Dispatching crews, spending money or messaging the public always waits for a named official's approval.
0 decisions by named demo roles so far, each in the log.
Every answer shows its sources
Numbers link back to the record or document they came from, with the inputs and the rule behind each signal one click away.
Full audit trail
Who asked what, which data was used, what the AI suggested and who approved it, all kept on record.
✓ 48 AI and human actions logged; hash chain checked just now: intact.
PDPA by design
Personal data is minimised and access is role-based, in line with Thailand's Personal Data Protection Act B.E. 2562. The demo holds no real personal data.
Thai first
Reads and drafts Thai official documents. The demo works in Thai and English; a pilot can add the languages visitors use.
Hosted in Thailand, from the pilot on
This demo runs on a Groovy Web server. A pilot runs on city servers or a Thai cloud, and the AI model sits behind one adapter, so it can be swapped for an in-country model.
To confirm with Pattaya City
Nothing below is assumed. Each item is a question for discovery.
Data
ER arrivals, bed census and staff roster TBC
Citizen request channels and current tracking tool TBC
Dog registry, CNVR records and bite reports TBC
Road, drainage and asset GIS layers TBC
Waste routes, truck logs and tonnage TBC
ThaiWater, GISTDA and data.go.th access terms TBC
Decisions
Which department sponsors the pilot TBC
Traffic, public safety and budget monitoring in scope TBC
Systems we must integrate with TBC
Hosting and security requirements TBC
Procurement path and timeline TBC
Data and licences
Requests, dogs, reports, bites, letters and residents: synthetic, made up for the demo.