Operator interface
Mapping, video streaming and platform data provide a shared operating context. Laboratory interface demonstrations do not constitute completed field validation of the full system.
Mission map
Mapping connects the mission with platform information. Maps and operator screens are shown in demonstration materials; data sources are agreed during integration.
Video in context
Video streams help operators relate observations to mission progress. Formats, availability and channel presentation depend on the connected system.
Platform state
Telemetry and state displays support shared situational understanding. Parameters and interpretation rules are agreed with the platform manufacturer.
Clear operator workflows
The interface is developed around user workflows. Preparation, observation and control are intended to connect through clear transitions and confirmations.
Roles and access
The roadmap includes separating responsibilities across team members. Roles and access models are defined by the requirements of each deployment.
Planning and coordination
Development covers task, route and mission parameter preparation, together with coordination across platforms. The operator remains responsible for decisions.
Task preparation
Planning is being developed as a structured description of the task, platform and operating conditions. It is intended to reduce ambiguity between preparation and execution.
Routes and parameters
Development covers route and mission-parameter preparation in the operator environment. Available actions depend on implemented interfaces and platform capabilities.
Air and ground platforms
The target architecture provides a shared digital context for UAVs and UGVs. Compatibility and interaction scenarios are evaluated for each integration.
Supervised plan updates
The roadmap includes controlled updates to parameters and tasks. Operator confirmation and permitted changes are defined by the mission workflow.
Templates for recurring tasks
Reusing agreed scenarios is a direction for scaling the product. Templates are intended to help teams prepare recurring missions with consistent settings.
Telemetry and monitoring
Platform status, execution progress and mission events. Available data sources depend on the configuration and implemented integrations.
Unified telemetry context
Connected-system states are brought into the operator environment according to available data. This provides a basis for observation without constant switching between separate tools.
Execution progress
Development covers comparing mission plans with execution states. Detail depends on the messages and feedback provided by the platform.
Events and notifications
The roadmap includes structured presentation of events requiring user attention. Priorities and notification conditions are aligned with operator workflows.
Link availability
Data-link status is important operator context. Indicators and interface behavior when data is unavailable are defined during integration.
Logs for review
Recording agreed events and technical data is a direction for engineering review. Retention, access and use are defined by partner requirements.
Integration layer
Connecting the ground environment with onboard software and platform interfaces. UAV integration is in progress; compatibility is verified for each specific configuration.
Onboard software connection
The ground environment connects to onboard software through agreed interfaces. UAV integration is in progress and evaluated for each configuration.
Manufacturer-specific adapters
A modular approach aligns communication with partner systems. Messages, commands and feedback are specified in the technical scope.
Aligned data model
State semantics, measurement units and timestamps need to be understood across subsystems. Data-model alignment supports a consistent operator experience.
Connection with ORB Robotics
The target architecture connects the mission environment with the UGV autonomy software layer. Available functions depend on module readiness and integration results.
Scaling through validation
Integration-package development relies on documented configurations and acceptance criteria. This provides a basis for reusing validated components in future projects.