Release Notes Version History

Audience Five App Versions

Overview What is Ericsson Sensing Demo?

• Command and Control center — multi-client collaboration setup for coordinating operators in real time
• 2D / 3D map panel — switchable between Leaflet (OpenStreetMap or Google Maps) and custom WebGL 3D view with optional Google 3D tiles
• Zone drawing tools — draw perimeters, no-go zones, and ignore zones directly on the map
• Real-time detections feed — timestamped detections for perimeter breach, swarm pattern, loitering, and rapid approach events
• System connections panel — live link-status for all connected external systems

Overview What is Ericsson Sensing Demo? (cont.)

C2 Demo Five Stories for the C2 View

The C2 view supports a story-driven demonstration designed for security analyst audiences. Pre-loaded scenarios allow a presenter to walk through all five stories without a live sensor feed. All state is synchronized across connected clients in real time.

Story 1 Object Detection

Security monitors a pre-defined area. When an object is detected, it appears on the map and triggers a notification. The analyst decides whether to track or ignore it.

Demo checklist

1. Load a scenario from the Live view dropdown (or use live MQTT)
2. Point out unclassified objects on the map — they show a pulsating white ring
3. Show the Detections panel (right side) — new objects appear with color-coded urgency dots
4. Click an object on the map — a Track / Ignore popup appears
5. Click Track to promote the object, or click the Track link in the Detections list
6. Show that tracked objects move from Detections to the Tracked Objects table
7. Click Ignore on a non-threatening object — it is dismissed with an audit log entry

Story 2 Tracking & Classification

Security teams turn raw detections into a prioritized threat picture by classifying each object's type and intent.

Demo checklist

1. Select a tracked object — the ID card (Selected Object panel) shows speed, altitude, location, heading
2. Point out the Suggested classification hint below the dropdowns — the system proposes a type based on speed and altitude
3. Click Accept to apply the suggestion, or manually choose a type from the Classification dropdown (Drone, Helicopter, Plane, Car, Bus, Tram)
4. Set the Intent dropdown (Friendly, Suspicious, Hostile) — the map marker and table row color update immediately
5. Show the map icons — classified objects display an EDS icon (drone, car, plane, etc.) on a semi-transparent enlarged marker
6. Use the filter tabs (All / Friendly / Threats) in the Tracked Objects table to show how the threat picture is prioritized
7. Point out the color scheme — green = friendly, amber = suspicious, red = hostile, grey = unclassified

Story 3 Recording, Validating & Alerting

Security teams record and validate tracked objects, enrich them with notes, and take action on prioritized threats.

Demo checklist

1. Select a tracked object and show the Tracking accuracy percentage and Validated by field (system or analyst)
2. Type a note in the Note textarea — explain that notes are synced across all connected C2 clients
3. Click Alert — a commander notification is logged and the button briefly shows "Alert sent!"
4. Click Disable SIM — show the planned-capability placeholder dialog (future integration)
5. Click Center on map — the map pans and zooms to the selected object
6. Click View action log — the log dialog opens, filtered to show only events for this specific object
7. Show the Latest Actions panel (bottom left) — all operator actions appear as a timestamped audit trail

Story 4 Geofencing

Security teams define protected zones and receive real-time alerts when objects with matching intents violate them, or mark areas to ignore to reduce noise.

Demo checklist

1. Click Draw new perimeter on the map — click to place vertices, then click Done
2. In the dialog, choose a preset (No-go zone, Area of interest, Flight corridor, or Ignore zone)
3. Set the alert level (Red / Orange / Yellow / Blue / Green) and give the zone a name
4. Configure Alert rules — check which intents trigger alerts (Unclassified, Suspicious, Hostile, Friendly)
5. Optionally set altitude constraints (min / max) for a No-fly zone
6. Show the perimeter rendered in both the 2D and 3D map views
7. Demonstrate a breach — when a matching object enters the zone, a detection is automatically created
8. Show that an Ignore zone (green / alertLevel 0) suppresses all detections within it

Story 5 Data Export & Integration

Security teams stream detections, classifications, and incidents to external systems for a unified operational picture.

Demo checklist

1. Show the System Connections panel (bottom left) with on/off toggles for 7 external systems
2. Toggle a system on or off — point out the audit trail entry in Latest Actions
3. Click the three-dots menu (⋮) on the System Connections panel heading
4. Select Show information — walk through the system info presentation deck (SKYKEEPER, SIGMA, etc.)
5. Select Data shared — show which data categories are shared with connected systems
6. Select Connection status — show per-system connection state and timestamps
7. Select Export data — download the full C2 state as a JSON file
8. Mention that API-based streaming to external C2 platforms is a planned capability

Overview What is Ericsson Sensing GUI/Viewer/dev?

Quality Assurance Test Coverage

Jest unit tests · Async integration tests included · Playwright e2e (chromium, firefox, webkit)

Tab 1 Maps

Tab 2 Archive

• Historical playback — load compressed MQTT log files (.zip / .mqttlog) and replay at configurable speed
• JSZip decompression — client-side, no server round-trip required
• Syntax-highlighted inspection — JSON messages rendered with truncation for large payloads (>20 KB)
• Timeline integration — scrub through archive sessions directly on the timeline bar
• Memory-safe — tab content cleared on navigation to prevent layout reflow overhead

Tab 3 Status

More Tabs Docs & Settings

Launch Testing Strategy