# FAQs — OSMUS

Canonical page: https://osmus.si/faq

Content reviewed: 2026-10-24

Scope, camera inputs, processing and operator responsibilities.

[Skip to content](https://osmus.si/#main)

[

![OSMUS](https://osmus.si/assets/osmus-icon.webp)

](https://osmus.si/index.html)[Powered by AIS  ↗](https://ais-slovenia.si/)

 Menu  +

[Camera System](https://osmus.si/camera-system.html)[Projects & Use Cases](https://osmus.si/projects.html)[Company](https://osmus.si/about.html)[Contact  ↗](https://osmus.si/contact.html)

[← OSMUS home](https://osmus.si/index.html)

FAQs

# Questions before you start.

Scope, camera inputs, processing and operator responsibilities.

### What does OSMUS build?

OSMUS focuses on camera-system workflows: connecting photographs or video with relevant context and human review. Camera hardware, processing and operator software are scoped around the application.

### Which camera hardware is supported?

There is no confirmed public camera-model or connection list in the available material. The intended device, mounting, connectivity and capture conditions need to be assessed for the project.

### Does every connected camera provide AI detection or tracking?

No. Capturing an image, processing it and interpreting it with AI are separate functions. Detection, tracking, recognition, reporting and performance need their own verified scope.

### What does an operator receive?

The proposed output depends on the application. It may be source imagery with review context or photographs associated with a vehicle record. Each application page describes its intended output and status.

### Are these applications deployed?

The application pages describe proposed scenarios. Defence reconnaissance remains a future application. The related AIS vehicle capture module is development-stage work; it does not establish an OSMUS deployment.

### Can the workflow connect to our existing software?

We first assess the access and connections supported by your existing tools. The interface, data mapping and responsibility for failed or incomplete transfers form part of the project scope.

### How are data and review responsibilities agreed?

Define who may view the imagery, where it is processed, how long it is retained and who approves the result. These requirements must be confirmed for the selected implementation.

### What should we bring to a first conversation?

Describe the task, the cameras and software involved, and the decision your team needs to make. Include a representative anonymised input where possible and name the person who can confirm a correct outcome.

[Discuss this workflow  ↗](https://osmus.si/contact.html)

[

![OSMUS](https://osmus.si/assets/osmus-icon.webp)

](https://osmus.si/index.html)

OSMUS — wholly owned by AIS

[Visit AIS ↗](https://ais-slovenia.si/)

[Camera system](https://osmus.si/camera-system.html)[Projects & use cases](https://osmus.si/projects.html)[Company](https://osmus.si/about.html)[Contact](https://osmus.si/contact.html)

[Process](https://osmus.si/process.html)[FAQs](https://osmus.si/faq.html)[Site information & privacy](https://osmus.si/site-information.html)[Site map](https://osmus.si/sitemap.html)

 © 2026 OSMUS Ljubljana, Slovenia[Visual credits](https://osmus.si/site-information.html#visuals)