Skip to main content
Products
Prototype AccessPrototypePausedPartially Implemented

GridOps

A governed software prototype for electrical telemetry, operational visibility, and monitoring workflows.

GridOps explores how compatible electrical measurements, equipment state, alerts, and history can be brought into one browser-based operational interface. Live remote breaker actuation is not implemented.

Prototype under active development. Live remote breaker actuation is not implemented. All website readings and operational states are synthetic and illustrative. No production deployment, hardware compatibility, safety validation, cybersecurity assessment, commissioning procedure, or commercial access is established.

Access is not active. Production readiness, hardware compatibility, safety validation, cybersecurity controls, deployment responsibility, support, licensing, and commercial availability remain pending.

Discuss This Prototype

Illustrative synthetic data — not a live deployment.

Product Fact Sheet

Summary facts

  • Product categoryDocumented
    Prototype Access
  • ApplicationDocumented
    Browser-based monitoring interface
  • Field integrationDocumented
    Existing compatible meters, breakers, I/O, and gateways
  • Protocols documentedDocumented
    Modbus and MQTT
  • Deployment statePending
    Pending
  • AccessDocumented
    Not active
  • Production readinessDocumented
    Not established
  • HardwareDocumented
    Not designed, manufactured, or sold by FCLX Studios
  • DeliveryProvisional
    Custom deployment model under review
  • LicensePending
    Pending
  • SupportPending
    Pending
  • CommerceDocumented
    Disabled

Overview

Bring electrical state, telemetry, alerts, and history into one monitoring view.

Electrical assets at remote or distributed sites can be difficult to observe and costly to operate manually.

GridOps is designed to collect measurements from compatible industrial equipment, organize that information in a browser-based dashboard, classify abnormal states, and record historical activity. Live remote breaker actuation is not implemented.

The platform is intended to work as a software and integration layer over compatible existing electrical and telemetry infrastructure.

Use and audience

Current use cases and intended users

Primary use cases

  • Collect electrical measurements from compatible existing equipment.
  • Present equipment state and device health in a browser-based operational dashboard.
  • Record historical telemetry, events, and command activity.
  • Classify abnormal conditions and communication faults.
  • Generate alert and notification events.
  • Review monitoring-oriented electrical state without presenting real-device remote breaker actuation as an implemented capability.
  • Provide site-specific and fleet-level operational visibility.

Intended users

  • Operators of high-density computing facilities.
  • Cryptocurrency-mining operations.
  • Operators of remote industrial sites.
  • Operators of distributed facilities.
  • Energy-intensive plants and workshops.
  • Multi-site operators.

Current scope

Documented capabilities

Monitoring

Documented
  • Three-phase voltage and current.
  • Frequency.
  • Apparent power.
  • Power factor.
  • Breaker or equipment state.
  • Device health.
  • Historical trends.
  • Event records.

Future remote-operation groundwork

Documented
  • M16 command/control framework is simulator only.
  • Live remote breaker actuation is not implemented.
  • M17 real-device remote OPEN is not started.
  • M18 real-device remote CLOSE is not started.

Multi-site structure

Documented
  • Site-specific dashboards.
  • Site-specific connected equipment.
  • Site-specific access rules.
  • Fleet-level visibility.
  • Site configuration and lifecycle management.

Alerts and notifications

Documented
  • Normal and abnormal-state classification.
  • Communication-fault detection.
  • Power-loss detection.
  • Email and messaging notification concepts.

History and analytics

Documented
  • Time-series data.
  • Minimum, average, and maximum trend buckets.
  • Event history.
  • CSV export.

Roles and audit

Documented
  • Named user accounts.
  • Role-based access.
  • View-only and control roles.
  • Two-factor authentication in the documented design.
  • Additional identity confirmation for sensitive actions.
  • Full command and event audit trail.

Reliability

Documented
  • Data-feed health monitoring.
  • Watchdog-based recovery logic described in the source material.
  • Communication-state visibility.

Product details

Qualifications and operating context

Architecture overview

Documented

Compatible field equipment provides measurements and equipment state through interfaces such as Modbus.

An industrial site gateway bridges field protocols and publishes telemetry through MQTT.

The documented server architecture includes telemetry ingestion, storage, alerting, analytics, application services, and separated control groundwork that does not provide real-device breaker actuation.

A browser-based interface presents operational state, history, alerts, and user controls; real-device remote breaker actuation is not implemented.

Software integration - not FCLX-manufactured hardware.

Documented

GridOps is an FCLX Studios software and systems-integration platform.

GridOps currently monitors compatible existing telemetry and device-state sources; any future control-signal integration remains planned and real-device actuation is not implemented.

FCLX Studios does not design, manufacture, or sell the underlying electrical panels, breakers, sensors, controllers, embedded devices, gateways, or networking equipment.

Remote electrical operation is safety-critical.

Documented

GridOps software cannot make an electrical installation safe by itself.

Any remote-control deployment requires qualified electrical and controls engineering, compatible equipment, physical interlocks, local or remote selectors, site-specific hazard analysis, cybersecurity review, commissioning, operating procedures, access control, emergency procedures, and compliance with applicable technical and legal requirements.

No Product copy may claim that accidental operation is impossible.

Target environments - not proof of deployment.

Documented

Potential environments include high-density computing facilities, cryptocurrency-mining operations, remote industrial sites, distributed facilities, energy-intensive plants and workshops, and multi-site operators.

These environments describe intended users and use cases. They are not evidence of existing GridOps deployments.

Product and deployment model pending

Pending

The current source material permits both a reusable FCLX software-platform model and a custom platform delivered for an individual client or site owner.

The boundary must be resolved before commercial positioning.

Hosted versus self-hosted deployment, infrastructure ownership, maintenance responsibility, cybersecurity responsibility, commissioning responsibility, hardware compatibility, support, service levels, pilot structure, pricing, and licensing remain pending.

Technical context

Requirements, compatibility, and data behavior

Requirements

  • Compatible field equipmentDocumented

    Site-specific compatibility assessment required

  • Industrial gatewayDocumented

    Required by the documented architecture

  • Electrical and controls engineeringDocumented

    Required for any remote-control deployment

  • CommissioningPending

    Required and currently not supplied as a finalized procedure

  • Cybersecurity reviewPending

    Required and currently not supplied as a finalized assessment

Compatibility

  • Field equipmentDocumented

    Compatible existing meters, breakers, switchgear I/O, sensors, and control interfaces

  • ModbusDocumented

    Documented field protocol

  • MQTTDocumented

    Documented gateway-to-server messaging protocol

  • Supported-device listPending

    Not supplied

  • Hardware validationPending

    Site-specific and not established

  • Production deploymentPending

    Not established

Data behavior

  • Electrical measurementsDocumented

    The documented platform scope includes collection and storage of electrical telemetry.

  • Event and command historyDocumented

    The documented platform scope includes event and command audit records.

  • Website prototype dataDocumented

    All monitoring values shown in initial website prototype visuals must be synthetic and clearly presented as illustrative.

  • Real deployment dataDocumented

    No real client, site, device, credential, or sensitive operational data is authorized for the initial website implementation.

Not current capability

Roadmap

These items remain roadmap items and are separate from documented current scope.

  • Energy and cost analytics.
  • Load profiling and efficiency reporting.
  • Predictive maintenance.
  • Anomaly detection.
  • Automated load-shedding policies.
  • Scheduled actuation.
  • Demand-response participation.
  • Renewable-energy and microgrid coordination.
  • Mobile companion application.
  • Expanded device and protocol support.
  • Advanced reporting.
  • Compliance-oriented exports.
  • White-label operation.
  • Multi-tenant operation.

Scope boundary

Out of scope

  • GridOps does not make an electrical installation safe by itself.
  • FCLX Studios does not design or manufacture the underlying electrical hardware.
  • FCLX Studios does not sell electrical panels, breakers, sensors, controllers, embedded devices, gateways, or networking equipment as GridOps products.
  • Production deployment is not established.
  • Access to a working GridOps environment is not active.
  • Hardware compatibility is not universal and requires site-specific assessment.
  • Roadmap functions are not current demonstrated capabilities.
  • No existing client deployment, scale, uptime, reliability, or performance result is claimed.
  • Energy and cost analytics.
  • Load profiling and efficiency reporting.
  • Predictive maintenance.
  • Anomaly detection.
  • Automated load-shedding policies.
  • Scheduled actuation.
  • Demand-response participation.
  • Renewable-energy and microgrid coordination.
  • Mobile companion application.
  • Expanded device and protocol support.
  • Advanced reporting.
  • Compliance-oriented exports.
  • White-label operation.
  • Multi-tenant operation.

Current boundaries

Current limitations

  • Production readiness is not established.
  • Access is not active.
  • No verified deployment is presented.
  • No supported-device compatibility list is supplied.
  • No certified safety case is supplied.
  • No cybersecurity assessment is supplied.
  • No hazard analysis is supplied.
  • No commissioning procedure is supplied.
  • No formal support or maintenance model is supplied.
  • Alerting destinations and providers are not finalized.
  • Platform ownership and deployment model remain pending.
  • Scale, availability, performance, and reliability claims are not verified.
  • Enterprise-grade claims are prohibited without evidence.
  • Self-healing language must be translated into specific watchdog behavior.
  • Equipment compatibility requires assessment.

Prototype limitations

  • No verified deployment is presented.
  • Production readiness is not established.
  • Access is not active.
  • Hardware compatibility requires site-specific assessment.
  • Safety validation is site-specific and not established.
  • No certified safety case, hazard analysis, cybersecurity assessment, or commissioning procedure is supplied.
  • Deployment responsibility, support, licensing, pricing, and commercial structure remain pending.
  • Prototype visuals and synthetic data are not proof of implemented or field-validated capability.

Operational state

Availability and maturity

GridOps has a substantial documented intended architecture and capability scope, but no production-ready deployment, supported-device list, certified safety case, cybersecurity assessment, commissioning procedure, or active delivery model is currently established.

  • DeliveryProvisional
    Pending / custom deployment model under review
  • LicensePending
    Pending
  • SupportPending
    Pending
  • AccessDocumented
    Not active
  • Production readinessDocumented
    Not established
  • CommerceDocumented
    Disabled

Governed notices

Important qualifications

Reserved visual evidence

Illustrative Product views

These governed positions are illustrative placeholders. They are not evidence of deployment, availability, compatibility, or production readiness.

  • Monitoring dashboard

    Pending

    Reserved position for a clearly labeled prototype monitoring dashboard using synthetic electrical data.

    Illustrative synthetic data

  • Equipment-state view

    Pending

    Reserved position for a clearly labeled prototype equipment-state view using synthetic identifiers and states.

    Illustrative synthetic data

  • Alert history

    Pending

    Reserved position for a clearly labeled prototype alert-history view using synthetic events.

    Illustrative synthetic data

  • Trend view

    Pending

    Reserved position for a clearly labeled prototype trend view using synthetic measurements.

    Illustrative synthetic data

  • User-role and audit view

    Pending

    Reserved position for a clearly labeled prototype role and audit view using synthetic users and events.

    Illustrative synthetic data

  • Control-confirmation workflow

    Pending

    Reserved position for an M16 simulator-only command/control workflow. Live remote breaker actuation is not implemented.

    Illustrative synthetic data

  • Architecture diagram

    Pending

    Reserved position for an accurate diagram of compatible field equipment, gateway, server services, isolated control service, and browser application.

  • Prototype screens

    Pending

    Reserved positions for additional screens explicitly labeled Prototype View or Illustrative Workflow.

    Illustrative synthetic data