MetaEnergy
MetaEnergy

MetaFlow - Monitoring & Dispatching Platform

Real-time platform for pipeline monitoring, dispatching, hydraulic analysis, and operational simulation

Energy, Monitoring, SCADA, Gas, Real-time, Hydraulic Simulation, Pipeline, Dispatching

Overview

MetaFlow is an operations platform for pipeline teams managing gas, liquid, and multi-fluid networks. It combines live telemetry, SCADA visualization, alarm workflows, hydraulic analysis, transient simulation, and role-based dispatching in one operator workspace. The platform supports multi-organization use, isolated demo environments, engineering-grade model analysis, and secure access control for dispatchers, engineers, and administrators.

Key Features

  • Real-time Telemetry & SCADA Visualization
  • Dispatcher Workspace
  • Hydraulic Solver Engine
  • Scenario & Report Management
  • Multi-organization Access Control

Challenge

Pipeline operators often work across separate monitoring screens, engineering tools, and reporting processes. That fragmentation slows alarm triage, makes it difficult to connect simulations with live network data, and creates inconsistent handover between shifts. → Monitor distributed infrastructure in real time → Run hydraulic analysis using operational data → Manage alarms, events, and dispatcher actions consistently → Produce traceable reports for engineering and operational review

Solution

MetaEnergy developed MetaFlow with a Java/Spring Boot backend, PostgreSQL/PostGIS data layer, React/TypeScript operator interface, and a hybrid C++/Java hydraulic solver exposed through gRPC. The platform streams telemetry through WebSocket services, supports steady-state and transient hydraulic models, and provides operator screens with alarm history, audit trails, concurrency controls, and role-based access.

Impact & Results

  • ✓ Unified operational visibility
  • Live telemetry, network status, and alarms in a single control-room view
  • ✓ Faster alarm investigation
  • Searchable history, clear event context, and configurable notification workflows
  • ✓ Repeatable hydraulic studies
  • Scenario comparison, run history, and PDF reports from the same network model
  • ✓ Safer concurrent dispatching
  • Role-based actions, auditability, and conflict-aware editing for multi-user teams

Tech Stack

  • Java
  • Spring Boot
  • PostgreSQL
  • PostGIS
  • React
  • TypeScript
  • Fabric.js
  • gRPC
  • C++
  • WebSocket/STOMP

System Architecture

End-to-end data pipeline from field sensors to real-time dashboards

  • metaenergy.ge · metaflow platform v2.0
  • Field Layer / Edge Devices
  • MetaFlow Desktop App (WebSocket)
  • Live mimic · Alarms · SCADA
  • Web Dashboard (React)
  • Vite · Tailwind · Bilingual EN/KA
  • Hydraulic Solver (C++)
  • Newton-Raphson · Nodal analysis
  • Dispatcher Engine (C++)
  • Parallel compute · Port 8096
  • MetaFlow Backend (Spring Boot)
  • Multi-module monorepo
  • Dispatcher · Hydraulic · OAuth2
  • Schema-per-session isolation
  • Windows Service (Data Listener)
  • TCP listener · Auto-reconnect
  • Communication Server
  • Protocol translation · Buffering
  • Raw telemetry buffer · Fallback
  • Ultrasonic / Turbine
  • MODBUS · Serial RS-485
  • GPRS/4G Modems (SIM)
  • Multi-operator failover
  • Cellular Network (Dedicated APN)
  • Private tunnel · Static IP

Real-Time Operations & Control

Live operational environments for dispatching, monitoring, alarms, and control-room workflows

We build operator-facing systems that bring telemetry, alarms, device state, reports, and actions into one workspace. These systems help dispatchers and supervisors move from fragmented screens and manual calls to live operational visibility.

What we deliver

  • Dispatcher workspaces
  • SCADA visualization layers
  • Live telemetry dashboards
  • Alarm routing and escalation workflows
  • Operator action logs
  • Shift handover and reporting views

Use this service when

  • Operators rely on disconnected SCADA screens, spreadsheets, or phone calls
  • Alarm history is difficult to reconstruct
  • Supervisors need a consistent view of live network state
  • Dispatching, reporting, and device records are not connected

Related posts