IIoT at the Smart Device Edge (family)

-Add in a description of the family, what makes the species linked together

• Needs to focus on Industrial IoT use cases at the Smart Device Edge (eg IoT edge compute deployed outside of the data center), not mobile devices/client
  • There can be other families that cover other smart device edge use cases- 
  • refer a lot to the white paper
  • 256 MB single node to a small server cluster 
  • gateway, router, hub, server
    • not just about gateways, 
• This would be covered by the smart device edge under the User edge- Taxonomy Whitepaper page 3
• is there a min hardware? maybe as small as a RPi, but really focused on true industrial machines
  • need some type compute functionality at the edge
• agnostic to silicon (eg ARM and x86 cpu, tpu, gpu, etc)
• comprehend the unique needs of the Industrial IoT edge compute use cases
  
  • latency and safety critical applications 
  • priority for uptime and safety
  • prevention of sending control messages back to critical infrastructure from the cloud
  • comprehension of OT protocols 
  • a mix of on prem and cloud back end systems...
  • deployment of legacy VM and apps plus modern containers
• add in a couple more UCs for this
• add in alignment with Akraino blueprints
• describe a baseline infrastructure
• horizontal infrastructure- market-tecture need to scope this out; draw the picture
• support to workload themes
  • computer vision, eg stream video
    • high bandwidth is needed
    • the killer app is to process this at the edge
  • machine intelligence, eg structured telemetry
    • many different protocols, 
    • varying amounts of data volume (eg vibration data vs temperature data)
• enable workload consolidation

Need to update the text in the table to reflect the changes from the taxonomy

Use Case Details:

<add in the taxonomy image from the white paper>

add in text explaining the smart device edge 

Family- IoT Device Edge-

This is for the Family, Blueprint creators are welcome to join by adding their name. 

We are starting the election of a PTL 3 Sept, which will end in two weeks (17 Sept).  Anyone interested in becoming PTL just needs to self nominate themselves by putting Y in the correct column.  As per the Akraino Community process and directed by TSC, a blueprint which has only one nominee for Project Technical Lead (PTL) will be the elected lead once at least one committer seconds the nomination after the close of nominations.  If there are two or more, an election will take place.  

Contributors: 

Tina Tsou (Deactivated)