Panóptico · 2017—2018

Designing a system to understand and operate a connected city.

Panóptico was an urban monitoring platform designed to integrate cameras, devices, events, operators and territorial data into a single operational experience.

  • Product conceptualization
  • Product Design
  • UX/UI
  • Branding
  • Front-end
Placeholder temporal: panoptico-hero. Composición del ecosistema Panóptico.

The infrastructure already existed.What was missing was integrating it.

For years, municipalities and agencies adopted cameras, monitoring centers, vehicles, alert systems and other technologies. Much of that infrastructure still operated as separate pieces.

Panóptico emerged as a shared layer able to connect those resources and turn them into an integrated operation.

Scattered infrastructure converging into Panóptico, then opening toward observe, operate and analyze.

[MOCK — ecosystem-diagram]

  • Cameras
  • Alerts
  • People
  • Vehicles
  • Agencies
  • Monitoring centers
  • Data

Panóptico

  • Observe
  • Operate
  • Analyze

Designing for a system, not for a screen.

Panóptico combined video monitoring, territorial visualization, event logging and management, device administration, analytics, roles and permissions.

The challenge was to build coherence across products with different goals, information and contexts of use.

The problem was not solving a screen.

It was defining a logic that could sustain the entire suite.

  1. Territory

  2. Devices

  3. Monitoring

  4. Events

  5. Management

  6. Analytics

From a tool to a product family.

Together with the team I helped conceptualize Panóptico as a suite of specialized tools connected by a shared product model, identity and interaction language.

[MOCK — product-family]

Panóptico

Observation

  • SmartMap
  • Viewer

Operation

  • Regis
  • RegAdmin
  • Ediv

Intelligence

  • Command
  • GeoData

Administration

  • Users
  • Roles
  • Zones
  • Devices

A suite needed to behave like a suite.It also needed to look like one.

I designed the Panóptico identity and a visual language that let each product read as a specific tool without losing belonging to the system.

[MOCK — brand-system]

Panóptico

Panóptico

  1. SmartMap
  2. Regis
  3. RegAdmin
  4. Viewer
  5. Command
  6. GeoData

  • Family

    A master brand and tools that still read as part of the same system.

  • Function

    Each product is differentiated by its task, not by a separate visual language.

  • Recognition

    Shared iconography and treatments to keep belonging to the suite.

Designing every interface meant defining rules, not screens.

The tools had different tasks — exploring territory, watching video, logging events, administering devices or analyzing information — but they needed to share a recognizable structure.

Placeholder temporal: interface-smartmap. SmartMap.
Placeholder temporal: interface-viewer. Viewer.
Placeholder temporal: interface-regis. Regis.
Placeholder temporal: interface-regadmin. RegAdmin.
Placeholder temporal: interface-admin. Administración.
Placeholder temporal: interface-dashboard. Command / analítica.
  • Coherent navigation
  • Operational hierarchy
  • Territorial context
  • Contextual panels
  • Shared iconography
  • System states

Territory as interface.

SmartMap is a clear example of how system decisions materialized in a concrete tool.

v0.5

Placeholder temporal: smartmap-v05. SmartMap · v0.5.

v1.0

Placeholder temporal: smartmap-v10. SmartMap · v1.0.
Placeholder temporal: smartmap-navigation. SmartMap · navegación contextual.

  1. 01

    Contextual navigation

    Bring tools closer to the place where the operation happens.

  2. 02

    Hierarchy

    Reduce secondary elements so territory and devices can take the lead.

  3. 03

    Consistency

    Apply the suite language without losing SmartMap’s specific needs.

Observing was only the beginning.

The different tools existed because the operation did not end at the image: it had to detect, log, manage, analyze and decide.

[MOCK — operational-flow]

  1. Territory

  2. Detect

    camera / alert

  3. Observe

    Viewer / SmartMap

  4. Log

    Regis

  5. Manage

    RegAdmin

  6. Analyze

    Command / GeoData

  7. Decide

The model could grow beyond cameras.

Once a model based on territory, actors, devices, events and information was in place, new sources could be added without conceptually redesigning the whole product.

[MOCK — extensibility]

  • Partes Urgentes
  • Alerts

Panóptico

  • InfoCar
  • Sensors

These extensions show that the model could absorb new sources. They are not additional case studies.

Designing the product meant designing the system.

My work on Panóptico ranged from conceptualizing the suite and its product architecture to the visual identity and the design of its interfaces.

The most important challenge was not solving an individual screen, but finding a logic able to connect territory, devices, operators, events and data within a coherent experience.

Placeholder temporal: panoptico-closing. Composición de cierre.

Next project

KIU

Product Design for an airline ecosystem: reservations, check-in, operations and passenger services.

Continue