solliancenet / MCW-Predictive-Maintenance-for-Remote-Field-Devices

Creative Commons Attribution 4.0 International
2 stars 6 forks source link

SME Review - Workshop outline #1

Open DawnmarieDesJardins opened 5 years ago

DawnmarieDesJardins commented 5 years ago

Please place all feedback to the workshop outline in this issue by continuing the conversation below.

KalyanBondugula commented 5 years ago

Kalyan Bondugula: [Dawnmarie – Here is my high level feedback.

• Overall, the connected factory will resonate more in the “factory floor” setting – say in discrete manufacturing. Not sure if Oil field is a great example of that. You should check few connected factory case studies – Jabil/Sandvik etc. • The use case introduction does not talk about any data collection/devices related point. Focused only on the Machine Learning aspect. Looks more like intro for ML workshop than IoT. • We need to talk about “Edge” processing and “OPC UA” framework related points which are key for Manufacturing/Oil & Gas customers. • SaaS is one solution option, customers may also be interested in “Build” with “PaaS”. Should be considered as an option for solution]

mpeder commented 5 years ago

@DawnmarieDesJardins here is some high level feedback from me as well:

olivierbloch commented 5 years ago

I like the outline and only have a few suggestions:

krishna0815 commented 5 years ago

Few suggestions from my side.

  1. Remote field services esp in Oil and Gas / Offshore exploration typically merits edge analytics. Can we morph a part of this into edge story

  2. ASA offers built-in ML based functions for Anomaly Detection - both in cloud and edge based on now open sourced ML.net offering. Meaning, for simple A/D scenarios customers do not need to build and train their models. We should try and include this as a part of the crawl-walk-run approach within the ML spectrum.

  3. Geospatial capabilities - ASA has built in Geospatial functions, again on cloud and edge, to continuously detect distance between assets, generate alerts if an asset enters or leaves a geofence etc. For oil fields etc, based on real customer scenarios safety is critical. So customers like Petrofac (now in prod) want to generate alerts if a worker with inadequate training enters a high risk site. Essentially, they have a matrix of workers (single coordinates) and allowable sites (geofences) that ASA deploys in the cloud and edge.

  4. Talking of general analytics, i recommend introducing audience to simple concepts like time windows, native output in parquet for downstream batch processing and ML training with Spark, late arrival policies etc. These are very commonly used capabilities in many IoT scenarios.

Happy to help guide on the implementation of these features.

krishna0815 commented 5 years ago

Please accept these views as applicable to the 'Securing IoT end to end ' workshop as well.

krishna0815 commented 5 years ago

In effect.. -