Robotic Republic Certification

Note:

The certification process ensures that the customer experience is as good as possible. The following points are the foundation of the certification process. Certification adds value:

• Identify problems before the costumer does
• Offer testing possibilities to KUKA Creators
• KUKA and Creators work together to offer an improved customer journey
• During certification, KUKA creates marketing materials, such as photos and videos. These may be placed on the product page of the Marketplace, and/or used in general to promote the KUKA robot and the Creator product or extension together.

The certification process differentiates between hardware products and products that require software on the KUKA system, so-called toolboxes.

• Certification is mandatory for toolboxes written with the help of the KUKA SDK. A toolbox can only be used in developer mode on the controller without appropriate signing.
• Certification is optional for hardware products, where a minimal technical test is sufficient. However, certification is still recommended to take advantage of the above points.

The following describes the process for obtaining a certificate for a Creator product. The certificate is only valid for specific products and not for the Creator as a company or group. Accordingly, a certified product is displayed in the marketplace and is therefore visible to the end customer.

1. Requirement communication: In meetings between KUKA and Creators, the requirements and benefits of certification will be discussed.
2. Development: In the development stage the Creator can adjust their product, so it will fit to the desired KUKA Robots.
3. Pre-Stage: The pre-stage is for testing and evaluating what needs to be adjusted The Feedback Loop ensures that the Creator gets the necessary information to go through with the certification. The pre-stage can start also during the development to speed up the process.
4. Certification: The certification Phase makes sure no critical point along the customer journey is open. If this is the case a certificate can be granted.
5. Proof of certification: Proof of certification is handed to the Creator. The certification badge is also displayed in the Marketplace. Certification depends on the product and version. It must be renewed if critical changes are made to the product.

1. Requirement communication: In meetings between KUKA and Creators, the requirements and benefits of certification will be discussed.
2. Development: In the development stage Creators writes their Toolbox using the KUKA SDK.
3. Code verification: Code verification is necessary to make sure only valid libraries and interfaces are used.
4. System test: The system test verifies that the toolbox basic system tasks can be performed. These tasks include installation, drag and drop nodes, and using capabilities.
5. Function test: A functional test must be performed. Depending on the complexity of the product and toolbox, the function test may be performed either at a KUKA facility or through the Creator. If the Creator performs the final function test, a verification must be done.
6. Toolbox signing: When all tests are passed, the toolbox will be signed by KUKA. It will then by installable on all IIQKA.OS systems, depending on the version of the SDK used.
7. Proof of certification: Proof of certification is handed to Creators. The certification badge is also displayed in the Marketplace. Certification depends on the product and version. It must be renewed if critical changes are made to the product.