Skip to main content

IOT and M/L driven analytics for manufacturing customers


This is a sample data architecture for a ERP centric landscape for a manufacturing customer . This fictional customer has IOT driven data analytics . 





1. IOT sensors capture and stream data which is captured by the data layer
2. This data layer filters, cleanses and aggregates the IOT data 
3. It takes out the pertinent data , for example the exceptional cases :
              a.Temperature (it takes the records and timestamps when the part overheats)
              b. Acceleration (for manufacturing company which makes automobiles , takes the values when the acceleration is not smooth ) 
             c. Electrical outages (Voltage spikes )
4. All this data is identified by unique Equipment ID . 
5. This can be co-related against ERP and other applications (On Premise / SaaS )      which stores all maintainance cases and service orders againts the Equipment ID 
6. The Data Store aggregates these data into the Historical Data store for future analysis and also derives KPIs 
7. The KPIs are sent to the Analytical Layer for visualization 
                              
Real Time Dashboards show performance for real time systems in discrete manufacturings . Predictive Analysis uses Machine Learning models to predict future behavior and co-relate failures . Azure / AWS / Google Cloud / IBM Watson all provide excellent ML functionalities 

Why do we send the data to Historical Data store ? Maybe we think of a new KPI or a need to look at the old data , for which we dont have analytics right now .

Example : A new equipment type B is releases which is similar to product line A 3. This has a lot of electrical issues after releasing the products . Thus we want to look at the data of product line A which is stored in the historical data store 


















Labels:

Comments

Post a Comment

Popular posts from this blog

Data Analytics for SAP - Part 1

 In this series of blogposts , I try to bring some of the new trends in Business Warehouse (BW) for SAP . With new predictive analytics and reporting capabilities being driven by Cloud platforms such as Azure/AWS/GCP, we now have a variety of options for creating business analytics on top of ECC 6.0 and S/4 HANA . These work very well on its own and also on top of SAP HANA 2.0 . The important thing to note is , it does not need the traditional SAP BW to work ! I want to present different options from the siloed data warehouse approach that has existed so far . Architecture This is a typical reference architecture of SAP ERP analytics that is an alternative to the traditional data loading models and paradigms  . Here we have three parts : Data Connector - Typically we can use Microsoft Azure Data Factory (ADF) , Theobald connector , Qlik connector or any 3rd party connector Data Layer - Here we need a Data Warehouse - either SAP BW or any other . We can also use (along with or in plac
Post a Comment
Read more

Managing SAP on Azure with ALM

Managing SAP on Azure with ALM SAP Customers are always looking for a lightweight, agile tool to manage their Multi-Product ERP landscape which may be a mixture of SAP , Integration Platforms, Custom Applications, SaaS vendors for different modules from billing to HR to logistics. They are always in the journey to perfect the process and one "toolset that rules them all"! Unfortunately, many customers , especially those with very large, diverse landscapes have come to a conclusion that there is no one platform that can do this and hence use a combination of tools for their Application Lifecycle Management(ALM) needs. Today I try to look at some possible use cases of a Cloudified SAP landscape and how to manage it. Typically, what does a typical SAP ERP landscape have - SAP ERP of course (ECC/S4HANA), BW, SAP Cloud Platform , GRC, Business Objects and then of course systems connected to it . So we will have : 1. Cloud SAP products (Ariba, C4C, Success Factors)  2
Post a Comment
Read more