Introduction¶
Industrial Edge Ecosystem Framework¶
The Ecosystem Framework provides an orientation and guidelines for participants in the Ecosystem. Our Ecosystem brings together providers of a variety of offerings – including App Providers, Device Builders, and Solution Partners – with end users, for example, industrial producers and industrial machine producers, enabling them to interact, to develop new ideas, to foster the Ecosystem in its entirety. Now, in line with and focused on this objective, this Ecosystem Framework provides the Ecosystem Cornerstones, describes the expectations and requirements towards the participants and establishes the basis for an exchange between the participants. All participants need to commit to the Ecosystem Framework before they are eligible to access to and participate in the Ecosystem.
Version 25_04
Framework Specification¶
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
| Key Word | Alternative Terms | Definition |
|---|---|---|
| MUST | "REQUIRED", "SHALL" | This word means that the definition is an absolute requirement of the specification. |
| MUST NOT | "SHALL NOT" | This phrase means that the definition is an absolute prohibition of the specification. |
| SHOULD | "RECOMMENDED" | This word means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. |
| SHOULD NOT | "NOT RECOMMENDED" | This phrase means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. |
| MAY | "OPTIONAL" | This word means that an item is truly optional. One may choose to include the item because it is required or because it enhances the product while another may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein this also applies vice versa. |
Industrial Edge Ecosystem Cornerstones¶
1. Openness¶
- The Ecosystem is open to anyone who agrees to its comprehensive, explicit, and transparent rules and guidelines.
- We treat each other equally and fairly based on the Ecosystem Framework.
- All participants are invited to get involved in reviewing and developing the Ecosystem Framework.
- A well-defined platform architecture and governance (described in the Ecosystem Framework) serves to prevent and resolve conflicts.
2. Community Growth¶
- The Ecosystem embodies a give-and-take approach that strives for a balance between risk and reward for all participants.
- The opportunities to provide Industrial Edge-based offerings and to build on each other’s offerings generate benefits for everyone involved.
- We create win-win situations together by incentivizing complementary value creation.
3. Provider Focus¶
- Our mission is to foster a value exchange and to create sustainable and productive interactions between producers and end users.
- Direct and transparent feedback from end users to providers creates additional value.
- We enable providers to generate data-based insights that continuously improve their product and solution performance.
- Intellectual property rights are protected and respected, as described in the Ecosystem Framework.
4. End Users Focus¶
- A seamless and digital user journey allows our end users to access offerings with a few clicks.
- We deliver end users value by offering a broad and competitive portfolio of best-in-class solutions.
- All participants are committed to our principles of industrial quality, reliability, security, and safety.