Omniwire Intelligence
PIXA Fleet
Management

Fleet visibility, engineered for action.

PIXA is a real-time fleet management experience designed to help organizations monitor vehicles, understand operations and make faster decisions.

Explore PIXA See how it works
PositioningOne fleet. One operational view.
EnvironmentInteractive demo — simulated data
InterfaceEnglish · العربية · RTL
Demo environment
PIXA — Operational Map Live simulation
Conceptual fleet map A stylized, non-geographic map showing simulated vehicles moving between a depot, customer sites and a service area. All positions are simulated for demonstration. Al Olaya Al Murabba Al Nakheel Industrial 2 East Corridor Ring Road DEPOT CUSTOMER RESTRICTED
Warning
Speed threshold
PIXA-104
Rule evaluated · alert generated
Simulated
Geofence event
Entered Depot Zone
Dispatcher notified automatically
Act 1 — The problem

A fleet is never just a collection of vehicles.

People. Routes. Time. Fuel. Maintenance. Safety. Customers. Decisions.

PIXA brings the operation into one view.

Vehicle leaves depot PIXA sees it Event detected Manager alerted Operation responds Data becomes analytics
Enter the operations console Everything that follows is an interactive demonstration built on simulated data.
Act 2 The visibility

See the fleet.

A working operations console: live map, fleet list, vehicle telemetry, geofences, event rules, alerts and an activity timeline — running entirely in your browser on simulated data.

Demo data
Role
Device
Al Olaya Al Murabba Al Nakheel Industrial City 2 Airport Corridor Central Park Central Ring Road North Axis South Distribution Rd
Simulated geography
Layers
08:00 Sim clock
Trip replay PIXA-104
08:10
Operational timeline Live simulation
All vehicles, positions, drivers, events and metrics on this page are simulated for demonstration. PIXA is not connected to live hardware here.
Act 3 · 4 The event, and the response

An event is only useful if something happens next.

PIXA is built around an event pipeline: telemetry is evaluated against rules, rules produce decisions, and decisions produce actions — notification, escalation, logging and dashboard state.

Automation rule RULE-014 Automation
IFVehicle enters RESTRICTED_ZONE during an active trip
THENCreate alert · Notify dispatcher · Log event · Update dashboard
Simulated
Turn automation off and run the trigger again — the event is still recorded, but no downstream action is taken. That difference is the product.
Vehicle enters restricted zone
Geofence boundary crossed — simulated Event
Rule engine evaluates conditions
Zone type, trip state, vehicle class Process
Severity assigned: critical
Decision recorded with rule reference Decision
Dispatcher notified · alert opened
Web + mobile notification, awaiting acknowledgement Action
Event logged · dashboard updated
Audit trail entry and KPI recalculation Log
Drivers & safety

Every trip has a person behind it.

Driver assignment, live trip state and conceptual safety indicators — so an operation can see behaviour patterns, not just dots on a map.

Driver roster

Fictional personnel
12
Driver Vehicle Status Current trip Safety events Score

Driver profile

Demo indicators
Fleet health & maintenance

Availability is an operational number.

Health state, service intervals and maintenance alerts sit in the same system as the map — because a vehicle that cannot run is a route that cannot be served.

Fleet health

Demo data
16Units
Select a category to filter the fleet list and the live map above.

Maintenance schedule

Simulated
Vehicle State Next service Interval
Act 5 The data

Movement becomes measurement.

Every trip, stop, alert and service event is a record. Aggregated, those records describe how the operation actually behaves — not how it is assumed to behave.

Conceptual analytics — fictional data

Fleet utilization

% of fleet on active trips
—%
Average across the selected range—

Vehicle availability

Share of the demo fleet by operational state

Trips completed

per day
—
Total in range—

Moving vs idle time

hours
—%
Idle share of engine-on time—
Moving Idle

Distance by vehicle type

Conceptual distribution across the demo fleet

Alerts by severity

Event volume across the selected range
Critical Warning Info

Maintenance load

Services opened vs closed, conceptual
Opened Closed
Cost & efficiency

The levers an operation can actually pull.

PIXA can help organizations identify operational patterns that influence fleet cost and utilization. The model below is illustrative — it demonstrates how the product frames trade-offs, not a projection of results.

Fuel / energy
—
Consumption index derived from moving time, idle time and load profile.
Idle time
—
Engine-on time without movement, aggregated per vehicle and per site.
Utilization
—
Share of available vehicle-hours spent on productive trips.
Maintenance
—
Planned vs unplanned service ratio across the fleet.
Route efficiency
—
Planned distance against actual distance travelled per assignment.
Illustrative model No savings claim
Reduction in idle time0%
Improvement in route adherence0%
Shift from unplanned to planned maintenance0%
Utilization index
100
Energy index
100
Indices are relative and start at 100. They illustrate direction of movement in a model, not measured or projected outcomes for any organization.
Sector adaptation

One system. Different operational models.

Fleet software fails when it assumes one workflow. PIXA is structured so the same core — vehicles, events, routes, roles — expresses a different operating model per sector.

Workflow expression

Conceptual

    Domain objects

    Same core, different labels
    PIXA core objectExpressed as
    Sectors shown as capability examples. Omniwire Intelligence makes no claim of existing contracts or deployments in these sectors.

    Don't just track vehicles. Understand the operation.

    A position is a fact. An operation is a system of people, time, assets and decisions. PIXA is designed for the second one.

    System architecture

    What has to exist for a map to be trustworthy.

    A conceptual view of how a system like PIXA is structured end to end. Select any stage to read what it is responsible for.

    Architecture concept No vendor or protocol claims
    Real-time engine

    Event → process → decision → action. The same loop drives the console, the alerts and the mobile notification.

    Event
    Vehicle enters geofence
    Position update crosses a defined boundary.
    Process
    System detects the event
    Stream processing classifies and enriches it.
    Decision
    Rule evaluates the event
    Severity, routing and escalation are resolved.
    Action
    Alert generated · manager notified
    Delivered to console, mobile and audit log.
    Simulated
    Performance & scale

    Designed to grow along the same axis the fleet does.

    More vehicles means more position updates, more events, more rules to evaluate and more people watching. The architecture separates ingestion, processing and presentation so each can scale independently.

    Stateless ingestion Queue-backed processing Time-series storage Push-based UI updates Horizontal workers

    Architecture concept. No throughput, latency or uptime figures are claimed on this page.

    API & integrations

    A fleet system that cannot talk to your other systems is a silo.

    PIXA is designed around an API layer so fleet data can move into the systems an organization already runs. The endpoints and payload below are illustrative examples of the interface shape.

    GET/api/v1/vehiclesIllustrative
    
        
    
      
    

      
    
        
    
          
    Integration surface
    Conceptual
    
          
    
            
    
              
    ERPAssets, cost centres, work orders
    
              
    CRMCustomer sites and service windows
    
              
    HRDriver records, shifts, licences
    
              
    MapsBasemaps, geocoding, routing services
    
              
    NotificationsEmail, SMS and push channels
    
              
    Fuel systemsTransactions reconciled to trips
    
              
    MaintenanceWorkshops, parts and service history
    
              
    AnalyticsWarehouse export and BI tooling
    
            
    
            
    
              
              Integration categories are shown to describe the intended interface surface. No existing integration, partnership or certification is claimed.
            
    
          
    
        
    

        
    
          
    Security layer
    Design intent
    
          
    
            
    
              
    Authentication
    Session and token-based sign-in with per-organization tenancy.
    
              
    Role-based access
    Manager, dispatcher, operations, driver and admin scopes.
    
              
    Secure APIs
    Scoped keys, request signing and rate limiting by design.
    
              
    Audit logs
    Who saw what, who acknowledged what, and when.
    
              
    Permissions
    Object-level rules for vehicles, zones, sites and reports.
    
              
    Data protection
    Encryption in transit, retention windows and data residency planning.
    
            
    
            
    
              
              These describe engineering intent for a production build. No certification, audit or compliance status is claimed.
            
    
          
    
        
    
      
    
    
    
  
    

    



    
  
    
    
    
      Mobile experience
      
    The operation does not stay at a desk.
    
      
    A manager needs the alert on the way to a meeting. A driver needs the next stop, not a dashboard. PIXA mobile is designed as a focused surface on the same real-time system.
    
    
    

    
    
      
    
        
    
          
    Built for two very different users
    
          
    
            
    M
    Manager / dispatcher
    Fleet state, alerts, acknowledgement and vehicle lookup.
    
            
    D
    Driver
    Current trip, next stop, tasks and vehicle checks.
    
            
    
              
              Demo data
            
    
          
    
        
    
        
    
          
    Interface parity
    
          
    
            
      
              
    • 01Same event model — an alert acknowledged on mobile updates the console immediately.
      • 
              
    • 02Same role model — a driver never sees the whole fleet.
      • 
              
    • 03Full Arabic and RTL layout, including navigation and notifications.
      • 
            
    
          
    
        
    
      
    

      
    
    
  
    

    



    
  
    
    Act 6 — The outcome
    
    From movement to insight.
    
    
    
      
    Track
    
      
    Monitor
    
      
    Respond
    
      
    Analyze
    
      
    Optimize
    
    
    
    
    Better operational visibility is not a feeling. It is a shorter distance between something happening and someone deciding what to do about it.
    
  
    

    



    
  
    
    
    
      Engineering surface
      
    What sits behind PIXA?
    
      
    PIXA is a demonstration of engineering capability across the full stack of a real-time operational product. These are the disciplines the build exercises.
    
    
    
    
    
      
    01
    Real-time data
    Position and telemetry streams, state reconciliation, live UI updates.
    
      
    02
    Map interface
    Vector rendering, camera control, layers, geofence geometry and hit testing.
    
      
    03
    Backend
    Ingestion, rule evaluation, job scheduling and service boundaries.
    
      
    04
    Database
    Operational store plus time-series history for trips and events.
    
      
    05
    API
    Versioned REST surface and a streaming channel for live clients.
    
      
    06
    Automation
    Rule chains that turn detected events into routed, logged actions.
    
      
    07
    Analytics
    Aggregation pipelines and operational reporting views.
    
      
    08
    Mobile
    Focused role-based application surfaces with push notification design.
    
      
    09
    Security
    Authentication, role scopes, permissions and audit trails.
    
    
    
  
    

    



    
  
    
    
    
      Omniwire Intelligence
      
    Your fleet is moving.
    Your data should be moving with it.
    
      
    Let's design and engineer the fleet-management system around your operation.
    
      
    
        Email Omniwire 
        
          omniwireintelligence@gmail.com
          
        
      
    
      
    This page is a product demonstration. Every vehicle, driver, location, event, metric and chart shown here is simulated for the purpose of demonstrating system design and engineering capability.