Skip to main content

GxF Platform Evaluation

Overview

GxF is an opensource platform (set of capabilities; metering, public lighting) for distribution of power on a grid. It is currently being used by and was donated to the open source community by a Dutch utility company called Alliander. 

Here's some useful links from my discovery work on GxF

Next Steps 

  • Continue deployment to digital ocean VM

    • Start by reviewing all these packages and understanding which ones you want to deploy or explore whether it makes more sense to rebuild the latest release and deploy packages from that. 

      • To run the GXF (Grid eXchange Fabric) platform, you generally need only a subset of the packages published in the OSGP GitHub organization—specifically, those that are direct dependencies for the platform's core services and adapters.

      • GXF is a modular system, and the required packages depend on your deployment goals. Commonly, the following package types are used:

        • 1.  

      • Core Platform Packages – These include the main server components, messaging infrastructure, shared libraries, and authentication modules.
        2.
        • Protocol Adapters – Depending on your use case, you’ll need the adapters that communicate with your field devices (e.g., OSLP, DLMS, IEC61850).
          3.
        • Domain and WS Adapters – These provide domain-specific logic and web service endpoints (e.g., smart metering, microgrids, public lighting).
          4.
        • Shared Utilities – Supporting packages shared between multiple modules.

       Steps to Determine Required Packages

      1.

      • Review the GXF Deployment Documentation: The official [GXF deployment guide](https://github.com/OSGP/open-smart-grid-platformdocumentation) lists the core components and adapters you need to deploy for a standard platform.
        2.
      • Match Packages to Components: Identify which packages correspond to those components (e.g., "osgp-adapter-domain-smart-metering", "osgp-adapter-ws-publiclighting", etc.).
        3.
        • Check
      Your

      Focus on Smart metering Use Case: OnlyOne includeof adaptersthe maintainers tells the application’s current design allows you to deploy only the smart metering components, along with some core GxF components. You’ll need the following components for protocolssmart and domains your project requires (e.g., if you don’t use microgrids, you can skip related adapters).metering:

        Common
      • core CoreGxF Packagescomponents: (Typical
          Minimum)

             osgp-core
             osgp-shared
             osgp-domain-core
             

        • osgp-adapter-domain-\
          admin
        • osgp-adapter-domain-core
        • osgp-adapter-ws-\
          admin
        • osgp-adapter-ws-core
        • osgp-protocol-adapter-\
          core
        • osgp-logging
          • osgp-platform-auth

        • Example: If you want
      • Smart Meteringmetering andspecific Publiccomponents Lighting

          You'd likely need:

             osgp-core
             osgp-shared
             osgp-domain-core
             

        • osgp-adapter-domain-smart-metering
          smartmetering
          •  
        • osgp-adapter-ws-smart-metering
          smartmetering
          •  osgp-adapter-domain-publiclighting
             osgp-adapter-ws-publiclighting
             
        • osgp-protocol-adapter-dlms
          • (for
        • osgp-throttling-service
          • smart
        • osgp-secret-management
          • metering)
      • Smart metering simulator
        • osgp-protocol-adapter-oslpsimulator-dlms-triggered
          • (for public lighting)
             osgp-platform-auth

           

        • dlms-device-simulator-starter

      These components do not contain any user interface but provide a SOAP interface for communication with the GxF platform. The user interface is currently not part of the open-source implementation.

      - We could set up RESTful APIs and build a GUI we can use and contribute back to the community or we can also try to build a UI from the SOAP API available. Open to either, I don't know how much we can do with API only if we don't have a GUI. 

Back to top