The Ecosystem review process serves as the pathway to getting your device approved and published on the marketplace and Industrial Edge Hub.
Our team conducts a thorough evaluation of your device, applying our Ecosystem framework, quality checks, and security assessments to ensure it meets our standards for proven quality.
Once your device successfully passes the review, it will enter the publicity state, granting approval for marketplace release and visibility to others.
We recognize the importance of this step for you as a device builder and strive to make the process transparent and efficient.
This document provides an overview of the quality test process, input conditions, and technical test cases involved in the Ecosystem review, empowering you to enhance your device's readiness to meet the needs of our Industrial Edge users.
Thank you for choosing to submit your device for the Ecosystem review process; we are excited to collaborate with you and support your success in the marketplace.
Siemens Ecosystem team is conducting a thorough review of the ecosystem to ensure that the device aligns with the framework.
In addition, the Ecosystem team is implementing quality assurance measures that include upfront test standards based on common pitfalls, which will help us reduce time to market.
Our focus on security involves conducting thorough security checks to minimize risks for our customers.
Scalability is also a crucial aspect as we strive to enhance trust in the device's quality, enabling us to sell it on a large scale.
Lastly, we aim to increase trustworthiness by implementing a standardized onboarding process, which will improve the reliability of the device.
By prioritizing these key areas, we can ensure that your device meets the needs of our customers, delivers high-quality user experiences, and can be confidently sold at scale.
In the initial phase all the groundwork for a successful test needs to be done.
In this phase all the information and files required for the actual execution of the later tests are collected.
In order to be published on the marketplace, it is necessary to provide all the information requested.
Get in contact with your Ecosystem Manager inbox to inform about the start of Ecosystem review process.
For the review to start please send the required files and documents to your Ecosystem manager.
To verify the successful integration the test results performed by the Device Builder must be sent to the Ecosystem team.
Exception Condition
If it is a initial release the device can be provided including the firmware (OS + EdgeIoTCore + services)
Failed condition
No test results available or test showing >=0 errors. No further testing is performed.
1.2 Device release candidate hardware is provided¶
Test Title
Device hardware is available
Test Category
Mandatory before testing for hardware-based devices
Description
In order for us to begin our review process, the Device Builder must provide one physical hardware device that has integrated IEDK and services running.
Exception Condition
For software-based devices this test case is not neccessary
Failed condition
No hardware available. No further testing is performed.
To enable the test team to perform the test any specific information can be sent in a documentation about the device. E.g. creadentials, IP configuration etc.
Exception Condition
-
Failed condition
No documentation available. Further testing is performed.
Usability test cover the way of how a Industrial Edge user would work with the Industrial Edge device and Industrial Edge Management features concerning devices.
Reset: The Device has applications installed and after a Reset, only the Application and it's volumes are gone. Hard Reset: The Device has applications installed and after the Hard Reset all Applications, it's volumes and the device configuration is gone. The Device is offboarded of the IEM. The Network settings can stay persistent.
Exception Condition
-
Failed condition
Reset / Hard reset not possible. No further testing is performed.
Network Segmentation
Prohibit general routing or bridging between connected networks by default.
It can be possible to adjust the routing via a configuration mechanism or installing specific apps if metrics on routes or individual routes mustbe set.
Hard Reset
Whenever the hard reset is triggered, it must be ensured that all security-relevant information e.g., passwords are securely deleted from the device.
Time Synchronization
It is necessary to provide an up-to-date time on the device.
NTP compatible protocols, like NTPsec.
Storage of Artificats
It must be ensured that all directories, which contain IE packages and the corresponding volumes to store app data are protected against read access and modification.
Secure Logging
Devices must emit logs via an API to be able to export them on IEM e.g., for auditing or operational purposes.
Trusted Deployment Of Updates
Devices must implement a trusted deployment of updates to ensure the integrity of update packages.
Authentication
If a user needs access to an Edge Device for administration or configuration purposes the access needs to be secured by a login mechanism with state-of-the-art credential policies.
Root Privileges / Runtime Protection
Based on the user roles, authentication must be enforced.
Root-privileges are prohibited on productive devices.
Only the Device Builder is allowed to have a root-access for debugging of the firmware.
Recovery option
It is required to ensure a method that the user can reset the device if e.g. the admin credentials have been lost.
If the tests failed in any of the test stages, the tester will inform the Ecosystem team to get in contact with the device builder.
EOM Manager will inform the Device Builder about the failure causes and comments from the test team.