The most recent review (the latest one) can be found at the bottom of this page.
...
1/ 7:00 am – 7:30 am BP The AI Edge: Federated ML application at edge, PTL @Enzo Zhang (@haihui wang on behalf of PTL) Maturity Review Certification of Federated ML Application At Edge Blueprint request to Mature level
Summary: As the BP had fulfilled the requirements for Documentation submission for Akraino Rel. 5 ( R5 Federated ML application at edge Documentation), it is recommended to Akraino TSC to deem the maturity requirements for Documentation to "mature" level as fulfilled and accept the BP graduation request to "Mature" level.
2/4/2022 schedule
1/ 7:00 am – 7:30 am BP Robot basic architecture based on SSES, PTL Haruhisa Fukano Request to review architecture document.
| View file | ||||
|---|---|---|---|---|
|
Review Summary:
As the submited Fujitsu BP Architecture document on Robot-based SSES, explicitly refers to be a part and as such follows the Specifications and Framework from:
1: The SIP (Strategic Innovation Promotion) Program in Japan, that is a Cross-Ministerial National Program led by the Council for Science, Technology and Innovation (CSTI) of the Japanese Government with interdisciplinary Management to realize Scientific and Technological Innovation, also with the participation of the Japanese SDOs, namely, ARIB and TTC and
2. implements the Ritsumeikan University's SSES (Sensor-rich Soft End effector System, please see attached as a reference the paper:
Ritsumeikan University SSES Cyber Physical System Considering Physical Contacts in Robotic Manipulation for Improving Automation in Food Industry from Dec 2021).
| View file | ||||
|---|---|---|---|---|
|
It is recommended to Akraino TSC to deem the submitted Architecture document as "approved" and accept it.
Remarks:
It is recommended to the authors of the Architecture document to consider whether it might be useful to add in the Architecture document a ToC (Table of Contents) so that the recipient/reader of the Architecture Document may quickly have an overview of the Architecture Document contents, e.g. that the API's is n/a as indicated on p. 11, Section 6 and/or page 3, Section 2 about UCs and/or on page 9, Section 5 about the SW Platform Architecure....are couple of examples.
This remark shall be treated by the authors of the Architecture Document as "optional" and be subject to their discretion to accept or reject it.