One incident. The whole operating context.
A security-operations concept connecting cameras, events, access and device recovery, with the same investigation carried from desktop to mobile.
Selected work by Omar Samad. Informed by on-site security-operations experience through Pavion. This independent concept is not a deployed Tellbyte platform or a Tellbyte contract with Chick-fil-A.
- Omar’s role
- Product design & design engineering
- Project status
- Independent product concept
An investigation should not start over with every tool.
Security teams need to understand an event, locate the relevant footage and decide what to do next. When cameras, access records and device health live in disconnected views, the operator has to reconstruct that context while the incident is still unfolding.
The design question was how to keep the selected camera, event, time and available actions together. The interface also needed to distinguish a delayed stream, a lost connection and restricted access, rather than presenting every interruption as the same failure.
Build the experience around the investigation.
On-site observation, incident walkthroughs and working reviews informed the product structure. The concept brings monitoring, investigation and recovery into a shared operating frame, with different levels of detail for operators, technicians and security leads.
Persistent camera context carries the investigation from an overview into a selected feed and its playback history. Device and permission states remain visible beside the work so that the next action follows the information actually available.
- Keep the source selected: A persistent camera rail preserves the current location and source as the operator moves into detail.
- Make time inspectable: Playback and event history help the operator return to the relevant moment without losing the investigation.
- Design the interrupted path: Connection loss, restricted access and recovery receive explicit states alongside the normal flow.
Evaluate the task, not just the screen.
The original portfolio reports a comparison between the legacy workflow and the redesigned concept for investigation, task completion and device recovery.
Reported in Omar’s original case study. Sample size, test dates and the underlying study records are not published alongside these figures. They describe a concept comparison, not Tellbyte customer results or a deployed-platform guarantee.
- 2m 52s → 54s: Investigation task time. The portfolio reports a 69% reduction for the compared task.
- 71% → 94%: Task completion. A reported increase of 23 percentage points.
- 4m 08s → 1m 41s: Recovery task time. The portfolio reports a 59% reduction for the compared recovery task.
Discuss the project scope, delivery requirements and the next useful step with Tellbyte.
Discuss your project