/
Product Release Roadmap

Product Release Roadmap

  • Ready for review

    • The GEISA project is working on several products that would enable grid edge interoperability that consists of:

    GEISA Product Definitions Table

    Product

    GEISA v0.9

    v1.0

    v1.1 / v1.X

    v2.0+

    Out of Scope

    Product

    GEISA v0.9

    v1.0

    v1.1 / v1.X

    v2.0+

    Out of Scope

    Narratives

    1. Operations (How to use GEISA)

    2. Application Certification (Introduction)

    1. Firmware Updates

    2. Application Updates

    1. DNS

    2. Application Certification Process

    3. Default Sane Secure Settings

     

     

    Privacy & Security

    EE Security: https://lf-energy.atlassian.net/wiki/x/OID3Aw

    1. App Signing

    1. Maintenance Requirements

    2. Permission Models

    3. https://lf-energy.atlassian.net/wiki/x/KAB4Bw / PII

    1. ADM Security

     

    ADM Pillar:

    1. Manifest Definitions

      1. https://lf-energy.atlassian.net/wiki/x/BQD-Cg

    2. App Management

      1. https://lf-energy.atlassian.net/wiki/x/QQD5Aw

      2. https://lf-energy.atlassian.net/wiki/x/RwD4Aw

    3. Application Monitoring

    4. Container Resource Management

    5. Device Monitoring (in Spec)

    6. Data Management (in Spec)

    1. Network Resource Management

    2. Basic Diagnostic Behavior (Local/Cloud Tools)

    1. Application Certification Process

    2. Diagnostic Behavior (Interactions / Capabilities)

    3. Interoperability / Multi-Vendor platform integration.

    4. On-Demand data paths/controls for large data collection/triage.

     

    1. Device Resource Management

    API Pillar:

    1. Device State

    2. Networking (Status)

    3. Upstream Networking (In Spec)

    4. Metrology / Metered Quantities (In Spec)

    5. Waveform (In Spec)

    6. External Time Synchronization (Can’t find)

    7. Sensors (In Spec)

    1. Non-Connected Edge (or extended network outage)

    1. Hardware Acceleration access (i.e. AI accelerators)

    2. HAN / Local Device access

    3. Device to Device communication

     

     

    EE Pillar:

    1. https://lf-energy.atlassian.net/wiki/x/C4D5Aw

    2. Operating System

    3. Base Libraries

    4. Core Services

    5. Resource Management & Security

      1. https://lf-energy.atlassian.net/wiki/x/OID3Aw

    6. Edge InterApp Communications

      1. Application Programming Interfaces (APIs)

      2. Message Bus Security Considerations

    7. ADM & External Systems :

      1. Network Communications

    8. Filesystem (in spec)

    9. Logging (in spec)

    1. Proposal: On-device App to App Communication

    2. System Calls - note on geisa does not mandata LXc for LEE.

    3. Network - Physical Layer - Awareness

    1. NPU / GPU Access

     

    1. Application Classification

    2. Message Bus - Physical Layer

    Quality of Life Improvements

     

    1. Proto Versioning

    2. Repo Rethink

    3. GitHub Rework

    4. Swagger for API Catalog / AutoGeneration

     

     

     

    GEISA 1.0

    • Keeping things up-to-date – lean into reducing risk.

      • Updating apps, not doing a meter firmware update.

    • Application Certification (Introduction)

    • Firmware Updates

    • Application Updates

      • App Manifest Updates w/out redeploy

    GEISA 1.X

    • Bandwidth Management based on Interface (RF Mesh / WiFi / Cellular)

    • API: Calls GPU/NPU accelerators for need to be specifically defined

    • API: For additional types of hardware support (i.e. accelerometer)

    • API: App-to-App (on device), permissions, manifests, policies.

    • Peer-to-Peer (app on one device to app on another device).

    • HAN & Local Device Interactions

      • How does the operator & authorize local networks? (Narrative is needed - Out of Scope)

      • Application level permissions & policies

    GEISA 2.0

    • Native Implementation as opposed to containerization

    • Move towards Build Once (VEE) vs. Write Once (1.0)

    • For consideration:

      • Enhanced Platform Provided Security & Encryption Services

      • More Granular API control – authorizing permissions for a limited period.

        • This could be managed through app manifest / policy updates.

      • More extensive/comprehensive “zero trust” approach.

      • Post-Quantum Cryptography support (where logical)

      • Extension of the platform via apps (Need concrete examples on this).

    • Commercial:

      • Need GEISA to be digestible/useful for the 100k end-point utility

      • “Light” version of the spec / product brief for end users to understand it.

      • Sane / secure defaults in the spec that allows minimal-touch deployments.

    Moved out of 1.0/why

    1. API Security - covered via combination of existing docs (local only), access controls, and manifests.

    2. Threading - unless someone comes up with a reason (e.g. VEE) and offers to expand on it, not mandatory for 1.0 spec release.

    Beyond GEISA 2.0

    Future iterations of GEISA would expand the definition to increase interoperability and capability across the edge environment

    GEISA Project Timeline

    As of 6/10/2025, we are targeting a 0.9 to 1.0 Release by July 2026.

    • GEISA Specification (Draft Target 6/30/2025) for:

      • ADM: Application & Device Management

      • API: Application Programming Interface

      • EE: Execution Environment

    • Sample Implementation (Target Q3 2025) for a GEISA API and Execution Environment

    • Conformance Tests (Target Q1 2026) for each of the above specification

    The specification should be sufficiently defined that a conformance test can be performed for each component of the specification. The above products define the minimal set of requirements to provide basic interoperability and a consistent environment for edge application developers.

    image-20250224-221745.png
    GEISA project Timeline