— 06 · Security

Infrastructure, assets and area monitoring

Large perimeters and distributed assets produce more signal than a control room can review. Convex works on visual perception of areas, interpretation of change in the environment and coordination of remote inspection missions.

Monitoring infrastructure is first of all a problem of recurring observation and reading change. Convex works on visual perception of areas and assets, interpretation of what changed in the environment, and coordination of remote inspection missions.

Talk to Convex Back to home

Infrastructure, assets and area monitoring

06 · Security

— Operational context

The operational problem

01
Extensive perimeters
The area to watch grows faster than the capacity to review every image.
02
Signal without reading
Many events captured, few carrying enough context to decide on.
03
Distributed assets
Remote facilities require travel for any kind of verification.
04
Environmental change mistaken for an event
Vegetation, weather and lighting alter the scene and must enter the interpretation.
05
Weakly auditable record
Without comparable history it is hard to show what was observed, and when.

— Convex architecture

From observation to action

The same architecture runs across every sector. What changes is which layer is critical and which proprietary systems take part.

Observe→

Interpret→

Decide→

Coordinate

Observe

Nexa Vision

Visual perception of areas, facilities and assets, clipped per region of interest.

Interpret

Nexa M1

Reading of change between observations and description of what differs from the area's pattern.

Decide

Atmos

Environmental context that helps separate natural change from a relevant event.

Coordinate

Synapse Control

Coordination of remote inspection missions and of alert routing.

— Data layers

What feeds the pipeline

Sources compatible with the systems deployed in this sector. No layer is assumed: every monitored area declares what is actually available.

Cameras

Visual streams over fixed points of interest.

Images

Captures bound to each observation of the area.

Geospatial data

Clipping of the monitored areas and assets.

Time series

Comparison of the same area across successive observations.

Environmental context

Local conditions during each observation period.

Mission state

Route, execution and result of remote inspections.

— Applications

Technical applications

Each application states the problem addressed, the data used, the Convex system involved and the operational output produced.

Monitoring of areas and assets

Remote facilities only verified by travelling to them.

Data: Images and geospatial clipping of the area.
System: Nexa Vision
Output: Recurring observation with a comparable visual record.

Reading change in the environment

Gradual alterations mistaken for noise.

Data: Area time series and environmental context.
System: Nexa M1 + Atmos
Output: A description of what changed since the previous observation.

Remote infrastructure inspection

Hard-to-reach points needing periodic verification.

Data: Planned route, mission state, visual captures.
System: Synapse Control + Nexa Vision
Output: Mission executed with visual material and result recorded.

Alert routing with context

Alerts without enough information to act on.

Data: Observation, area history and environmental context.
System: Nexa M1
Output: Alert accompanied by the reading of what was observed.

— Operational flow

One cycle, from sensor to record

01Capture
The area or asset is observed on the cycle defined by the operation.
02Processing
The capture is clipped per region of interest and normalised.
03Interpretation
Nexa M1 compares against history and describes what differs from the pattern.
04Alert
Relevant change is routed together with the context of the observation.
05Action
The team decides on a targeted inspection or a local response.
06Record
Observation and result are archived as an auditable record.

— Deliverables

What the system delivers

Alerts

Notification of relevant change, with context.

Maps

Clipping of monitored areas and assets.

Time series

Evolution of the same area across observations.

Reports

Periodic consolidation of the observations made.

Operational history

Auditable record of what was observed and when.

— Technology stage

Maturity by capability

We separate what is in operation from what is still under development. Research and prototypes are never presented as deployed product.

In operation
Visual monitoring of areas and assets
Recurring observation with geospatial clipping and history.
In operation
Change interpretation by Nexa M1
Comparative reading across observations of the same area.
In development
Remote inspection missions
Coordination of recurring routes over distributed infrastructure.
In development
Biometric or facial recognition
Out of product scope. We do not develop identification of people.

— Application contexts