The initial release draft of GEISA aka GEISA 1.0 will define a minimum set of specifications required to provide basic interoperability to provide a more consistent environment for edge applications developers.
Definition will be sufficient enough to write a conformance tests.
GEISA 1.0 Specification (Q2 2025 - Release for Comments)
Minimum Grid Edge Hardware Requirements
Optional Add Ons
Provides Management info of GEISA HW capabilities
Specification Section | Release 1.0 Needs | Status |
---|---|---|
Base hardware requirements for edge environments meters | | |
Agreement on mechanism Agreement on format Agreement on defined meta-data | ||
https://lf-energy.atlassian.net/wiki/spaces/GEISA/folder/215285852 | Agreement on enumeration approach Agreement on default / “mailbox” mechanism Agreement on low-level API access | |
Agreement on approach: requirements or selection | ||
Container format Agreement on shared base container Shared base container contents | ||
Agreement on mechanism Agreement on supported methods | ||
Agreement on mechanism Agreement on supported attributes | ||
Definition of core libraries to be included |
| |
Agreement on services to be included in base environment Agreement on services to be included in base container | ||
Decision on Mechanism Format for Device State Data Format for High Resolution RMS Data Format for Waveform Data Format for Register Data Format for Other Sensor Data Format for Actuator Requests | ||
Agreement on bootstrapping / registration mechanism Agreement on application protocol security mechanisms Hardening Guide |
Reference Implementation (Q3 2025)
Conformance Testing Specification (Q1 2026)
Bash Script or Python that this works or not.
Define Testable / Not Testable Components
Beyond GEISA 1.0
Future iterations of GEISA would expand the definition to increase interoperability and capability across the edge environment
GEISA 1.x
More specific definitions for areas under existing categories that require further detail.
GEISA 2.0
Native Implementation as opposed to containerization
Move towards Build Once vs. Write Once
More API’s for other types of hardware support
Road Map Timeline