Interoperability for operational systems

Valo connects live feeds, APIs, and data sources into a shared operational layer — enabling systems to work together without custom integrations.

Participants become immediate providers and consumers of fused intelligence.

We connected 13 different APIs and turned them into one operational system.

From fragmented APIs to a shared operational system

Before
Traffic API
Weather API
Events API
Isolated
Isolated
Isolated
After
Traffic
Weather
Events
Sensors
Valo (Shared model)
Unified observations / events
Dashboard / operators / agents

Connected data sources (live demo)

We connected 13 different APIs and turned them into one operational system.

Transport & mobility

  • HSL real-time (stream)
  • Traffic API
  • Routing

Environment

  • FMI weather
  • Geospatial data

City & services

  • Service Map
  • Open311
  • Events

Data layer

  • HRI catalog
  • Statistics

Normalized into a shared model

Traffic
Observation(type=traffic_density)
Weather
Observation(type=wind)
Open311
Event(type=issue_report)

Reusable across systems

Weather + Traffic
congestion risk
Events + Transport
crowd flow
Open311 + Location
incident mapping

What is happening right now

13
Data sources connected
2,341
Observations processed
18
Event types active
Active
Real-time stream
Primary Domain

Operational interoperability in real time

Modern defence environments combine drones, sensors, weather data, and communications systems. But these systems rarely interoperate.

Multi-source awareness

Combine live feeds into a shared operational view.

Rapid integration in exercises

Systems connect once and become immediately usable.

Cross-vendor interoperability

Structured and unstructured systems operate together.

Edge-compatible operation

Continue operating under degraded or disconnected conditions.

Real-time fusion
Drone feed Observation
Weather Observation
Sensor Event
Fused Result: Track / Incident
Secondary Domain

From fragmented APIs to reusable data

Government systems face a different but related problem: APIs exist across agencies, data is not discoverable, there is no shared structure, and reuse is limited.

API discovery layer

Identify what data exists and who provides it.

Transformation into shared model

Convert APIs into reusable structured outputs.

Cross-agency reuse

One integration becomes usable across multiple systems.

Reduced duplication

Eliminate repeated integration work.

Data reuse
Transport API Observation
Population data Resource
Permit system Event
Shared Layer: Reusable across agencies

Architecture principles

Built for real-world interoperability

Shared meaning before shared interfaces

Data is normalized into a common structure before it is exchanged.

Connect once, reuse everywhere

Each source integrates once and becomes reusable across systems.

Sensitive access stays under customer control

Protected systems are accessed through controlled connectors and delegated authority.

Centralize distribution, localize authority

High-bandwidth streams can be shared, while sensitive access remains local.

Built for federation, not silos

Systems act as both providers and consumers in a shared layer.

Policy travels with data

Access, classification, and provenance remain attached to data.

Useful alone, better together, safe when wrong

Each component works independently and improves when connected.

Valo is not another system

Not a sensor platform Not a data dashboard Not an API gateway

Valo is the interoperability layer that allows systems to work together in real time.

Building the foundation for interoperable systems

Valo focuses on enabling coordination between independent systems across operational and governmental environments.