Back to selected work

04 / Confidential system

Inseejam IoT Operations Platform

An IoT operations platform for monitoring distributed devices, tracking telemetry, automating schedules, and supporting remote control across multiple physical locations.

Confidential
Figure 01 — Representative project artifactNot a production screenshot
Representative blueprint-style visual for the Inseejam IoT Operations Platform

Representative visual artifact. No client-sensitive screens or proprietary data.

Status
Confidential
Domain
IoT · Telemetry · Operational Control
Project focus
Centralized IoT platform for distributed infrastructure and branch operations

01 / Brief

Problem and responsibility

The challenge

Organizations managing distributed branches need live visibility into devices, energy consumption, equipment status, automation schedules, and operational anomalies.

My role

Full-stack engineer contributing to frontend architecture, API-connected workflows, custom hooks, WebSocket-based telemetry behavior, and backend integration work.

02 / Contribution

What I worked on

The main areas I contributed to across the product and its supporting systems.

  1. 01

    Built dashboard modules for edge devices, scheduling controls, telemetry views, and branch-level operations.

  2. 02

    Developed modular React hooks such as device and scheduler abstractions to separate UI from data behavior.

  3. 03

    Contributed to Node.js backend services and real-time WebSocket workflows.

  4. 04

    Worked with Java and .NET integration layers connecting physical devices to ThingsBoard.

03 / System Context

How the work fits together

Representative system flowDirection of operation
  1. 01Sites / branches
  2. 02Edge devices
  3. 03ThingsBoard
  4. 04APIs / streams
  5. 05Operations UI

Generalized to communicate system context without exposing client-sensitive implementation details.

  • A1Device layer: meters, sensors, controllers, and edge devices.
  • A2IoT platform layer: ThingsBoard telemetry, attributes, and remote-control data.
  • A3Backend layer: APIs for devices, customers, schedulers, branches, and edge monitoring.
  • A4Frontend layer: React / Next.js dashboards for multi-branch operational visibility.

04 / Evidence

Outcome and engineering evidence

  • 01Live across 20+ SPL branches during the work period.
  • 02Improved operational visibility for distributed physical assets.
  • 03Shows ability to work with real-time systems, physical infrastructure, and Arabic/RTL enterprise interfaces.

Technical environment

Tools used across the project.

ReactNext.jsTypeScriptReduxNode.jsNestJSWebSocketsThingsBoardJava.NET