Traceable context
Each proposed record keeps a source, collection time, last update time, location reference, and quality state alongside the operational view.
CITY OPERATIONS
Bring local facility signals into an accountable operating view.
A concept workspace for municipalities, facility operators, and SI teams to assess parking availability, environmental APIs, and facility sensors with their source, time, and quality visible.
Concept · Design stage
Planned operating view
See what happened, where it came from, and who acted on it.
The proposed view connects a map and time axis to provenance and quality checks, then records the operator case behind an operational decision.
- 01 · ReceiveParking, environment API, and facility sensor records
- 02 · VerifySource, timestamp, range, delay, and duplicate checks
- 03 · ObserveMap and time-axis context for reviewed signals
- 04 · ActThreshold event, assigned case, and action record
Designed for an operational conversation
The design focuses on a bounded local deployment, where an operator can distinguish a data issue from a facility condition before escalating work.
Map and time together
Operators could compare a facility on a map with changes over time, rather than infer a current condition from an isolated number.
Cases, not silent alerts
A threshold event would open an assignable case with a note, evidence links, and an outcome record for the responsible team.
Three steps for an MVP
These are proposed implementation steps, subject to customer data, operating rules, and security review.
- 01
Connect selected sources
Import a documented API or CSV feed for a defined district or facility scope.
- 02
Store and check records
Use PostgreSQL with PostGIS for spatial context and run deterministic freshness, range, and duplicate checks.
- 03
Review the operator case
Present the evidence, chosen threshold, assignee, and recorded action in one reviewable place.
Illustrative proposed event · fictional values
Facility: Example public parking lot A
Signal: available spaces reported as 0 for 45 minutes
Checks: last update delayed by 32 minutes; duplicate payload detected
Proposed case: confirm source connection before dispatching field actionSpecific, bounded AI assistance
AI would be considered only for selected, reviewable records. It would not control infrastructure or make an operational decision on its own.
Current: Codex-supported development
JinsongTech uses Codex to organize requirements, inspect edge cases, and review implementation work. The City Operations workspace itself is still in product design.
Planned: evidence-based case draft
With an operator-selected event, allowed source metadata, and deterministic check results, a planned Claude workflow could draft a case summary, cite supplied evidence, and list unanswered questions.
Planned: controlled release
Read-only tools, explicit permissions, audit records, cost limits, and human approval would be required before an output becomes a ticket, report, or change proposal.
Proposed technical boundary
A proposed React and FastAPI application would use PostgreSQL with PostGIS. An NGSI-LD adapter is a later option that needs validation against a customer’s data and governance requirements.
What is the initial deployment scope?
City Operations is in design around a defined district or facility portfolio. Its connection scope and operating model would be proposed with each customer.
Where could it run?
Deployment options would be scoped after confirming security, retention, and operational requirements with the customer.
Product conversation