Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Use Case Details:





Attributes

Description

Informational

Type

New

New

Industry Sector

Industrial IoT


Business driver

Predictive Maintenance


Business use cases

Many devices give off hints that they will need to have maintenance earlier than their schedule maintenance.  Through Machine Learning (ML), we can create models that will allow us to know that a device will soon need maintenance.  For many machines, we can gain a great deal of information on the health of the device by looking at the temperature of the device.  This requires collecting the data and then sending it to a Historian or similar device.  These data points can be sent to the cloud to be modeled.

Other requirements

  • Need to take the current temperature of the device and react in near real time to rising temperature
    • Example: If over 150 C- send out a warning to a email list, show warning on a UI
      if over 180 C trigger light or horn
      if over 200 C trigger shutdown process

Other variations:

Monitoring restricted spaces

  • If a human enters in a space, 
    • first level of restriction- sound an alarm and turn on lights
    • second level- start shutdown process

Predictive maintenance: There are many different types of models.  For example, many models do not need to be done in real time.  Thus, the data can be sent to the Cloud and processed.  The data is not time critical, so if there is a delay in sending/receiving data, the data will need to be stored and then sent when the network is available. 


Yet, there are many scenarios, where real time or near real time is required.  An example of this would be a machine reaching a maximum temperature.  As it approaches this, we would want to send out a warning and then if it reached this critical temperature, the device needs to be shut down.


For this type of scenario, there needs to be a server or space on the IoT gateway that can process the data in real time. 


Business Cost - Initial Build Cost Target Objective



Business Cost – Target Operational Objective



Security need

Because of the remoteness of the devices, need the ability to control ports (turn on/off)


Regulations

TBD


Other restrictions



Additional details




Case Attributes

Description

Informational

Type

New


Blueprint Family - Proposed   Name

Integrated Edge Cloud (IEC)


Use Case

Industrial Predictive Maintenance


Blueprint proposed Name

IEC Type 6: IIoT for Integrated Edge Cloud (IEC) Blueprint Family


Initial POD Cost (capex)

Under $20k

FLIR Camera-

IoT Gateway-

ZEDEDA Cloud (or simular) 

FogLamp 


Scale & Type

1 server


Applications

FogLamp, Ubuntu


Power Restrictions

NA


Infrastructure orchestration

EVE

VM- Unbuntu


SDN

None


Workload Type

  • Containers (Tensoflow, Keras containers)
  • VMs


Additional Details

Submitter to provide additional use case details



Committer

Committer

Company

 Committer Contact Info

Committer Bio

Committer Picture

Self Nominate for PTL (Y/N)

@bill hunt

Dianomic

bill@dianomic.com




Shiv Ramamurthi

ArmShiv.Ramamurthi@arm.com


Cplus Shen

Advantech

Cplus.Shen@advantech.com.tw




Ashwin GopalakrishnanDianomicashwin@dianomic.com


Erik NordmarkZededaerik@zededa.com


Daniel LazaroOSIsoftdlazaro@osisoft.com


Aaron WilliamsLF Edgeaaron@lfedge.org



Contributors: 

Tina Tsou (Deactivated)




  • No labels