Internal testing has been successfully completed. The test protocols are available to verify compatibility to gridX requirements in a repeatable way.

An Alpha feature is available for first on-site tests at the customer's site after individual communication and activation by gridX.

Alpha integrations are only available via individual deployment targeting individual gridBoxes.

Alpha integrations are not covered by the gridX Support Terms.

A first draft of documentation is available.

gridX reserves the right to discontinue Alpha integrations at any time if performance is deemed unsatisfactory.

The integration was validated on at least ten customer sites and has been running for four weeks without major issues. An issue is considered a major issue if it affects more than two sites and is not related to asset configuration or commissioning. It has been thoroughly tested in accordance with the test protocol and no major performance degradation is expected. The number of sites required for the stage may be decreased for assets outside of residential solutions.

Beta integrations are available via activation in XENON scan configuration, reaching whole fleets of gridBoxes, but subject to customer contractual terms and conditions.

Beta integrations are available for PoCs.

A commissioning document is available in the help center.

Incidents are maintained by the Integrations teams.

Beta integrations are not covered by the gridX Support Terms.

Quality of control behavior and measurements complies to our Asset compatibility requirements.

gridX reserves the right to discontinue Beta integrations at any time if performance is deemed unsatisfactory.

The module or feature is an established part of the gridX product portfolio. It has been used at at least 100 customer sites for twelve weeks without major issues. The number of sites required for the stage may be decreased for assets outside of residential solutions.

Stable integrations can be added to any customer contract.

Stable integrations are covered by the gridX Support Terms.

Stable integrations support over-the-air-updates from the OEM and/or customer side that allows the whole fleet to be running under the same firmware version.

Stable terms only apply to assets equipped with firmware versions approved by gridX.

Stable integrations are supported by a contractual relationship between gridX and OEM that allows dedicated support and troubleshooting in cases of issues and new features.

gridX may deprecate or reduce the maturity stage of a stable integration in face of insufficient performance with regards to the asset compatibility requirements, or lack of OEM support, with at least 90 days of prior notice.

All assets at this maturity state are classified as sensitivity ‘critical’.

The integration use is not encouraged anymore as it will not be updated with regards to bug fixes. New modules and features will not take deprecated integrations into account during development and testing.

Integrations may still be visible in external documentations. The product manager decides accessibility based on impact and consequences.

Deprecated integrations are not covered by the gridX Support Terms.

Any integrations (Alpha, Beta and Stable) may be deprecated, given the upfront notice periods mentioned in contracts and agreements involving them. gridX will only deprecate items for technical reasons after a careful consideration of impact on its partners.

Deprecated integrations formerly on Stable stage are subject to support and bug fixes for at least two years.

Deprecated integrations formerly on Alpha and Beta stages may not be given support and bug fixes.

The integration reached its end of life and is no longer supported by gridX, even for bug fixes.

The integration is not mentioned in the website or external documentation in a sense the state serves more of an internal purpose.

Assets that have reached the field already can be discontinued if appropriate action has been taken with the customer to eliminate the effects of the lack of support. Product Management, Customer Success and Solution Engineering shall work together in shutting down the feature.

Discontinued integrations are disabled in XENON and are not present at any system at all in the field.