SAP Community - Internet of Things

IoT 3.0

2023-01-03T15:40:33+01:00

For many years I have been sending IoT data into central databases starting with Connect a Lego Mindstorms NXT to the HCP Internet of Things Services via a Raspberry Pi over Bluetooth, followed by Send your Raspberry Pi sensor data to SAP Vora via Apache Kafka managed by the SAP Data Hub, and Send your Raspberry Pi sensor data to SAP Vora via Eclipse Paho MQTT managed by the SAP Data Hub.

That had advantages in that I could leverage central application logic to Display your Lego Mindstorms sensor data on a Fiori Overview Page and deploy it to the HCP Portal Fiori Launchpad or Analyse your Raspberry Pi I2C sensor data with the HANA Cloud Platform, predictive services.

The architecture had been looking like this:

IoT data sent to a central instance and retrieved back from there.

With the emergence of Web 3.0 another option presented itself:

A decentralized distributed ledger holds the IoT data with the former central instance becoming an equal member.

For this blog I leverage Duino IoT that is a feature of Duino-Coin, a hybrid crypto currency.

This time, my device is an ESP32:

It mines Duino-Coin combining it with my IoT data:

Core 1 received a correct job with size of 87 bytes

Core 0 found a correct hash (2.62s)

Core 0 retrieved job feedback: GOOD, hashrate: 21.39kH/s, share #6062

Core 0 asking for a new job for user: architectSAP

AHT readings: 20.22*C, 47.76% rH

Core 0 received a correct job with size of 87 bytes

Core 1 found a correct hash (4.63s)

Core 1 retrieved job feedback: GOOD, hashrate: 21.13kH/s, share #6069

Core 1 asking for a new job for user: architectSAP

AHT readings: 20.22*C, 47.78% rH

Core 1 received a correct job with size of 87 bytes

Core 0 found a correct hash (5.54s)

As a result, my IoT data is stored with the blockchain and for example accessible through the Doino-Coin Web Wallet:

In my opinion, the potential for distributed ledgers for IoT is enormous especially also by reducing integration challenges and risks.

Building an End-To-End Machine Learning Solution for Product Inspection Centered On SAP Kyma

2023-01-31T16:44:03+01:00

Overview and Motivation

Over the last few months, Sanraj Mitra, Shetty Vriddhi and myself have been working on a product inspection solution combining SAP solutions with external technologies. Product inspection is a key part of quality assurance where goods are assessed for compliance with the company’s standards. Due to the wide range of checklists for each product, this often is a complex procedure. By automating the simpler tasks in this process and handing these responsibilities off to a computer, we would be able to lighten the workload of inspectors and speed up the duration of the inspection.In this use case, we will be simulating product inspection of beer cartons. Using a camera and a computer vision model, we will be able to count the number of beer bottles in a passing carton to ascertain whether the carton passes or fails inspection.

Scenario

Imagine a conveyor belt transporting beer cartons in a factory. By mounting a camera at a vantage point along the conveyor belt, we can record the cartons as they pass by. This live feed from the camera can be used as input to a machine learning model to count the number of beer bottles in each carton.

Application frontpage

Solution Architecture and Process

Solution Architecture

Although this is an end-to-end solution, the star of the show is of course the object detection. Let's have a closer look at its process flow.

Process Flow for Beer Bottle Detection

In addition to the above process flow, an SAC dashboard and SAP Build Apps mobile application are provided for end users to review the data collected for decision making.

In Detail

In this section we will go into more details about each component of the architecture.

ESP32-CAM

The first step was to find a suitable camera to record the beer cartons as they passed by. The requirements here was the camera needed to have Wi-Fi connectivity and be programmable. We were looking to create a WebSocket connection between the camera and the serving endpoint due to the quicker speed and low overhead per message, thus we needed to be able to program the camera to do so. The ESP32-CAM is a relatively affordable microcontroller with a camera mounted that fit the bill.

When powered, the ESP32-CAM will run a continuous loop to take a picture and send it through a WebSocket connection it establishes with the Flask app in SAP Kyma. We chose not to deploy the model on the ESP32-CAM but that is also a viable option for those who require machine learning on the edge, albeit with possible reduction in the model’s effectiveness.

YOLOv4 Bottle Detector Model

Next, we trained an object detection model to analyze the beer carton images from the microcontroller. To create our bottle detector model, we opted to train a YOLOv4 model on our bottle dataset. This is a process called transfer learning where we leverage the existing knowledge of a pre-built model to solve a new problem. We created a suitable dataset by using the ESP32-CAM to take images of the beer carton from the top. The areas within the image containing beer bottles are then labelled. This process is repeated with different number of bottles in the carton, with the carton at different positions.

Training Data Image Example

Training Data Labels Example

Once trained, the model’s weights are saved and are placed in the same Docker container as the Flask application. Using the trained model, we are able to detect how many bottles are in each picture frame, and where they are. In this way, we can label the original image with green bounding boxes wherever a bottle is detected, for easy reviewing of the model's performance.

Beer Carton Enters Camera View

Beer Carton Exits Camera View

Flask Web App

The web app allows us to provide an endpoint to receive the image from the ESP32-CAM. It also serves the YOLOv4 model and saves the inference results to our HANA Cloud database. In addition, the frontend provides users with the option to view a live feed of the incoming frames from the ESP32-CAM to ensure that the camera and model are operating as expected, in real-time.

The web app is containerized using Docker and pushed to Docker Hub. SAP Kyma / Kubernetes will then download the image from Docker Hub and use it to build a container to run the application. The Docker repository is linked to Kyma through the deployment yaml file.

Application Frontpage

SAP Cloud Application Programming Model (CAP) and SAP HANA Cloud

As mentioned, we also need a place to save our results. For this we used an SAP HANA Cloud HDI container. To make reading and writing to the database easier, we opted to deploy a CAP application in SAP Kyma to create a service layer. This way, we will be able to use HTTP requests and OData services to send and receive data from the database. The Flask application is able to write to the database through POST requests, while the SAP Build Apps application and SAC dashboard are able to retrieve the latest data through OData service.

Table Schema in HANA Cloud

SAP Analytics Cloud (SAC) and SAP Build Apps

Finally, we need to provide the end users with ways to view the data collected from the application. We demonstrated the utility in two products, SAC and SAP Build Apps in serving different purposes.

The SAC dashboard aims to provide users with a higher-level view across all production metrics. Here users can analyze historic trends and numbers.

SAC Dashboard

Meanwhile, the SAP Build Apps app is targeted towards staff working on the ground to gain quick access to inspection data. Here, users are able to view the batch information for specific dates, with an option to drill down further and double-check on the inspections' bottle counts.

On the Home page, the user can view basic statistics as well as select the batch date to be inspected.

Mobile App Home Page

After selecting the date, a list of all cartons that were manufactured on that date will be returned. The user can thus view which cartons passed or failed the inspection.

Mobile App Batch Inspection Page

Clicking onto any row will direct the user to that specific carton's information page. A labelled image of the carton will be displayed for the user to confirm that the machine learning model's bottle count is accurate. This can also be used to spot for consistent errors in the missing bottles. For example if the middle bottle on the top row is always missing, that could indicate an issue with the machine, rather than just random error.

Mobile App Product Page

Closing

To summarize, we have created an end-to-end product inspection solution revolving around SAP Kyma. While this proof of concept focused on an object counting use case, it can be easily extended to more complex inspection tasks.

Many thanks to Sanraj Mitra, vriddhishetty, lsm1401, gunteralbrecht, and jayadnure for their help and guidance throughout the development of this solution.

Industry 4.0 and the Standard ISA-95: The Pathway to Revolutionizing the Energy Industry

2023-04-05T23:11:38+02:00

The digital revolution of Industry 4.0, powered by big data and digital twins, has opened up new opportunities for the energy industry. By providing closer insight into production processes, digital technologies can enable more efficient, optimized, and automated operations to improve margins, reduce costs and reduce energy consumption. The Global Energy Industry is rapidly incorporating technologies such as the internet of Things (IoT), artificial intelligence (AI), 3D printing, cloud computing, and other cutting-edge innovations to support more efficient, competitive operations.

To ensure smooth and efficient operations, it is necessary that there is industry-wide interoperability and standardization. An excellent example is the Standard ISA-95 (also known as IEC 62264), developed by the International Society of Automation (ISA).

The Standard ISA-95 helps to streamline the collection, storage, and exchange of data to enable more meaningful insights and visibility. It provides the basis for digital data integration, describing the processes and equipment that support and manage digital communications within an enterprise. It differentiates between host sites (target systems such as electric meters and PLCs) and client sites (if available). It allows host sites to effectively collect and process data from other connected sites. It does this by using four levels – each of which have a distinct role in device control, level 0 being the field devices, level 1 being the field controllers (PLCs, PACs, PACs, etc.), level 2 being the supervisory systems, and level 3 being the enterprise system.

The Standard ISA-95 supports a range of communication networks, such as proprietary and open standards like OPC UA. It is already widely implemented, enabling deep data integration, messaging, and services. It makes it easy to connect equipment and subscribe to events to get updates and manage objects and addresses in the asset model. In addition, it allows users to develop enterprise control systems rather than individual control systems.

The traditional ISA-95 production stack is evolving into a digital manufacturing platform.

In short, the Standard ISA-95 is an intelligent, user-friendly platform that integrates different communication protocols, enabling more efficient, cost-effective, and better-informed operations. This gives the Global Energy Industry a cost-effective way to standardize its processes over a vast network and digitalize and secure its operations. This standardized system is essential for the energy industry to realize the promise of Industry 4.0 – enabling the energy industry to revolutionize its business.

SAP Industry 4.0 solutions and technology can bring data-driven processes and operational flexibility to the entire energy business.

https://www.sap.com/products/scm/industry-4-0.html

Streamlining Sensor Data Integration: Enhancing Telematics with AWS and SAP Digital Vehicle Hub

2023-05-30T16:21:15+02:00

Introduction:

In the rapidly evolving world of connected vehicles, leveraging telematic data is crucial for improving operations, enhancing driver safety, and optimizing vehicle performance. Integrating various systems and databases can be complex and time-consuming, but with the right tools and strategies, it becomes an achievable goal. In this blog post, we will explore how the combination of AWS services and SAP Digital Vehicle Hub can simplify the process of enabling telematic data persistence, integrating Otonomo with Amazon Kinesis, and displaying sensor data on SAP's user interface of SAP Digital Vehicle Hub.

Enabling Telematic Data Persistence into an AWS Timeseries Database:

One of the key steps in harnessing the power of telematic data is its persistent storage for analysis and future use. By leveraging Amazon Timeseries Database, you can store and manage vast amounts of sensor data efficiently. This eliminates the need for manual intervention, allowing a seamless and automated transfer of telematic data from vehicles to the database.

Benefits:

Reduced implementation efforts: By leveraging Amazon Timeseries Database, the process of bringing sensor data from vehicles is simplified, reducing implementation efforts significantly.

Streamlined data transfer: The automated integration enables a streamlined and efficient transfer of data from vehicles to the timeseries database.

Cost-effective storage: Amazon Timeseries database offers cost-effective storage solutions, allowing you to handle large volumes of sensor data without breaking the bank.

Continuing Integration of Otonomo with Amazon Kinesis:

Integrating Otonomo, a leading automotive data services platform, with Amazon Kinesis provides a powerful solution for processing and streaming real-time vehicle data. Amazon Kinesis allows you to receive and process massive volumes of sensor data at high speed, ensuring timely and accurate insights.

Benefits:

Enhanced data processing: By integrating Otonomo with Amazon Kinesis, you can efficiently process and analyze vast amounts of sensor data, unlocking valuable insights for your operations.

Real-time analytics: Amazon Kinesis enables real-time data streaming, empowering you to make informed decisions and respond promptly to critical events.

Cost-effective scalability: With Amazon Kinesis, you can scale your data processing capabilities based on demand, ensuring a cost-effective solution that grows with your needs.

Enabling Persistence of Telematic Data Using SAP Digital Vehicle Hub Naming Conventions:

SAP Digital Vehicle Hub is a comprehensive platform for managing vehicle-related data. By leveraging its naming conventions, you can ensure consistent and standardized storage of telematic data in the Timeseries database. This enables easy access and retrieval of sensor data when needed, enhancing the overall functionality of your system.

Benefits:

Standardized data organization: Utilizing SAP Digital Vehicle Hub's naming conventions ensures consistent and organized storage of sensor data, simplifying data retrieval and management.

Seamless integration: The integration of SAP Digital Vehicle Hub with the Timeseries database enables a seamless flow of telematic data, reducing complexity and maintenance efforts.

Improved data accessibility: With standardized naming conventions, sensor data can be easily accessed and displayed across various applications and user interfaces.

Displaying Sensor Data on SAP Digital Vehicle Hub's User Interface:

To fully leverage the power of telematic data, it is crucial to present it in a user-friendly and intuitive manner. By displaying the sensor data from the Amazon Timeseries database directly into the vehicle master of SAP Digital Vehicle Hub, you can provide a comprehensive view of vehicle performance and enable informed decision-making.

Benefits:

Enhanced data visualization: Displaying sensor data on SAP Digital Vehicle Hub's user interface enables intuitive visualization, making it easier for users to interpret and analyze the information.

Improved operational insights: By presenting sensor data within the context of SAP Digital Vehicle Hub, you gain valuable insights into vehicle performance.

Technical Integration details:

Prerequisite: Subscriptions to AWS and Otonomo accounts are available.

The following services are required in AWS for the integration: Kinesis Data Stream, Kinesis Data Analytics, Amazon Timestream

Follow the below steps to set up the integration

Configure the Streaming for fleet to send the data to AWS Kinesis from the Otonomo Dashboard

Configure Streaming for a Fleet in Otonomo Dashboard

Create a data stream in AWS Kinesis

AWS Kinesis data stream overview section

Create a Database and table in Amazon Timestream

Amazon TImeseries tables section

Upload the JAR file provided by SAP Digital Vehicle Hub in S3. For JAR file please reach our us by creating a ticket using component LOD-DMO-DVH (this process could change in the future)

Upload the provided JAR file in S3 bucket

Create a AWS Kinesis Analytics Application with the provided JAR file

Provide the path of the upload JAR file in S3 in configuration of streaming application

Create Runtime properties for the application

Runtime Properties section for streaming application

Once, the application is created you should be able to open the Apache Flink Dashboard and see a running job called “Preprocess and save to Timestream”

Job in Apache Flink Dashboard

Create a technical user in AWS with permission "AmazonTimestreamReadOnlyAccess" using IAM

Create an access key for the technical user

Create a destination in your BTP subaccount: DVH_AWS_IOT.
See: Setting up destination for fetching telematics data from AWS for more information

Create a vehicle using create vehicle API with same vin present in Otonomo fleet and “telematicsDataSource” as “02” (AWS Kinesis Timestream).

Creating a Vehicle using Postman

Open View/Modify Vehicles App in IAM FLP. Search for the newly created vehicle and open it. Navigate to the “Indicator Chart” section, select the sensor for which you would like to view the data

Indicator Chart section in View/Modify Vehicles App

You should now be able to visualize the telematics data for vehicles present in your system. There also new features panned which should help you in visualize the complex data of the vehicle sensors in an easier way.

Please, share your feedback in the comments. If you have any questions, you can reach out to me or harshachaithanya.kethepalle

Also, make sure to follow the blog, we have exciting new features on the way, they will be shared in upcoming blogs.

Thanks!

How is Nordlaks Leveraging IoT Technology and Cloud Processing to Farm Salmon in a more Sustainable Way?

2023-06-20T16:25:51+02:00

When The Department of Fisheries challenged the industry in 2015 to find new solutions for farming fish in the open seas, Norway based Nordlaks Oppdrett stepped up and won the competition based upon an innovative and sustainable approach.

Reinventing Salmon Production in a Sustainable Way
Family owned Nordlaks Oppdrett AS has been a leader in aquaculture in Norway since the company’s founding in 1989, with comprehensive operations from breeding premium Atlantic salmon to sales and marketing. However, continuing its robust growth depends on adopting new and sustainable production methods, as space within fjords for traditional net-pen farming is limited.

Nordlaks realized that the answer lay in economies of scale and designed a unique sea vessel called Havfarm which is currently the largest floating structure in the world. To put it in perspective, it is almost the length of 4 football fields and is designed to have a lifetime of at least 25 years without the need to bring it into a dry dock for maintenance and repairs.

Mr. Bjarne Johnsen, Project Manager Havfarm at Nordlaks explained: “To keep up with growing global demand and support sustainable farming, we recognized the opportunity to turn to the open seas to expand production. We realized that the answer lay in economies of scale. If we built larger containers, we would no longer be restricted to the calm waters of the fjord and could afford to deploy more robust materials and sophisticated safety measures.”

Leveraging IoT Sensors and Cloud Processing to Empower Operations and Maintenance Processes
It is not only the sheer size of the Havfarm that is impressive, but also the technology that empowers it.

To take salmon aquaculture to a new level, Nordlaks looked to the latest technology to support operations and maintenance processes. They strategically placed IoT sensors on the vessel to monitor, analyze and broadcast motion data in real-time. This data is used to run the digital twin model of the vessel in SAP^® Enterprise Product Development (SAP EPD), a cloud-based application that enables improved and streamlined processes for monitoring of operations and maintenance.

This monitoring system enables Nordlaks to focus inspections and maintenance activities on critical areas of the vessel structure, identified through Digital Twin technology and virtual sensors. It measures the integrity of the structure under adverse conditions to ensure everything from the longevity of the materials to the grip of the mooring. Furthermore, heat maps are used to monitor feed output ensuring that there is no lasting impact on the environment.

The company now has access to historic and near real-time data and actionable insights leading to improved decision-making. They can monitor the balance of the vessel to improve ballast operations. And it has now processes in place to support efficient feed spill monitoring and simplified soil sampling underneath the vessel required to meet strict compliance regulations.

As Mr. Bjarne Johnsen states “Everything we do needs to be sustainable and that means when we leave an area, there should be no trace that we were ever there. He concluded, “SAP Enterprise Product Development helps us monitor the Havfarm vessel infrastructure and environmental impacts on the seabed, which is key to our strategy for sustainable growth”.

Request a free trial and watch an overview video to learn how to enable fast, collaborative product development and lifecycle management with SAP EPD. In addition, you can watch a Nordlaks video.

Events-2-Business Action Framework – Create Plant Maintenance Notification in SAP S/4 HANA

2023-08-03T02:18:50+02:00

Our approach

Our aim is to adopt event-driven architecture, by building an open-source framework on the SAP Business Technology Platform (SAP BTP) which can integrate events generated from non-SAP platforms and solutions into SAP business processes thereby extending the value of existing SAP applications and processes. The events may originate from various sources such as IoT platforms, mobile and web applications, enterprise systems, and industrial production, logistics platforms, and so on. Thus, this framework helps in making business intelligent and interconnected to improve overall process efficiency. The Event-to-Business Framework can run on your own BTP or as SaaS solution provided by NTTDATA Business Solutions.

Figure-1: “Events-to-Business Actions” Framework

Business Scenario

Challenges

Industrial processes in factories, plants, warehouses, and logistics generate critical events from disparate and discrete industrial systems and there is a need to trigger business processes as a response to these events.

The Case

Create a Plant Maintenance Notification for the inhouse service technicians to maintain or repair an equipment, triggered by sensors reacting on changing conditions.

IoT device reports regularly status of equipment, e.g. temperature monitoring of a manufacturing machine and report to MS Azure IoT platform

Rules for dedicated telemetry properties, e.g. abnormal temperature to trigger export of event data (temperature too high)

“Create Plant Maintenance Notification” in SAP S/4 HANA by streaming the event to Event-to-Business Framework, where the streaming event is interpreted and enriched by business rules to create final content for functional transaction.

This action payload triggers the API in the connected SAP business system, here S/4 HANA.

Figure-2: Process Steps

Process steps

Sensor/IoT devices determine conditions

IoT devices with sensors monitor the operation-critical figures of an equipment and transmit them to an IoT platform for further activities. We simulate the case with an IoS App, developed by NTTDATA Business Solutions.

Figure-3: Simulate abnormal temperature increase

Ingest the data in an IoT platform
(here Microsoft Azure IoT Central)

Figure-4: Data Export to SAP Event Mesh

The event data is ingested in a platform, such as an IoT platform. In our scenario we use Microsoft Azure IoT Central. But any other platform, which can export data managed by rules, can be used. We select the records which are relevant for the process with Data Export functionality. In this step we also enrich the data string with content we need in the next steps of the Event-to-Business Framework. The data string is published on to SAP Event Mesh.

Activities in Event-2-Business Framework

Figure-5: UI modeler

As shown in Figure-5, this framework provides an out-of-the-box UI modeler that is intuitive to configure different types of actions like workflow or process execution that can be taken in SAP backend systems as an outcome of the incoming events from external sources via SAP Event Mesh.

Actions

In this scenario with our preconfigured actions, we create a plant maintenance notification in a SAP S/4 HANA system. For flexible configuration we use main actions (for each transaction), which can be chained with pre-action and post-action activities.

Figure-6: Action Categories

Figure-7: Actions to create Plant Maintenance Notification

This framework leverages business rules capability within the SAP Build Process Automation, which lets you automatically choose a business action that should be executed for an incoming event based on the configured decision tables.

For the creation of a Plant Maintenance Notification you need the Main-Action to feed the API with all required fields to execute the transaction. The data to feed the API has its source in the IoT platform (see Enrichment) or is derived from business rules. A Pre-Action fetches the derived data from the business rules, e.g. maintenance plant, notification type. The Post-Action is used for actions after the successful execution of the Main-Action. In this case we use it to set the status and notification number in the device in MS Azure IoT. With that we avoid that the event is executed again after already creating a notification in SAP Plant Maintenance.

Business Rules

Figure-8: Business Rules

The Business Rule triggered by the action, for Plant Maintenance Notification the Pre-Action triggers the Business Rule to determine relevant parameters to feed the payload of the Main-Action.

Using If – Then Rules to determine Notification Type, Maintenance Plant, Asset Location etc. based on Device Location (information from MS Azure IoT Enrichments).

Logging

Figure-9: Error Log

Every transaction processed is recorded in the (error) log. From the log lauchpad you can control the details of the event with its payload. A restart function is on the SAP development roadmap.

Reference Architecture

The architecture is based on leveraging the services of SAP Business Technology Platform which includes event-based integration with SAP Event Mesh, the upcoming event bridging functionality of SAP Integration Suite (Beta), Advanced Event Mesh (to be updated), Business rules capability in SAP Build Process Automation coming from SAP Workflow Management, SAP Destination Service, SAP Private Link service, SAP Connectivity Service and Cloud Connector and a Node.js extension application on the SAP Cloud Foundry runtime.

Figure-10: High-level architecture with SAP S/4HANA on-premise and private cloud

The following steps depict the information flow across systems

(1) Event is triggered from Microsoft Azure and is published on to SAP Event Mesh.

In Event-to-Business-Action framework (extension app),

(2) processor module endpoint is subscribed to SAP Event Mesh to receive the event.

(3) processor module leverages the Business Rules capability of SAP Build Process Automation to derive business action (For example, Purchase Order Requisition creation in SAP S/4HANA system) based on certain characteristics of incoming event.

(4), (5), (6), (7) and (8) processor module triggers the defined action in the SAP S/4HANA system using the SAP Destination Service and SAP Private Link Service.

In case SAP S/4HANA is on-premise and private cloud (refer to Figure-6) – communication with SAP S/4HANA happens via SAP Connectivity Service and Cloud Connector.

(9) and (10) are on the SAP development roadmap. SAP S/4HANA publishes an event (e.g., Plant Maintenance Notification creation) to Microsoft Azure Event Grid via SAP Event Mesh Connectivity Bridge for further processing by Microsoft Azure applications.

Key Advantages of This Architecture

Developers implementing this framework architecture would benefit from the following design considerations.

A flexible and generic framework that can be easily extensible for any Line of Business (LoB) scenario /workflow/process and any source system events.

Event-driven integration architecture with SAP Event Mesh as a central hub, including a bi-directional flow of events (Microsoft Azure to SAP S/4HANA and vice versa). We are also evaluating on leveraging Advanced Event Mesh (to be updated soon).

Enriched with resilient and high availability architectural patterns.

Network security-focused design with SAP Private Link specifically for RISE with SAP customers between SAP BTP on Azure (any region) and SAP S/4HANA on Microsoft Azure

Scenario Setup and Deployment

To get the entire scenario working, there are prerequisites and initial configurations required in SAP Business Technology Platform, Microsoft Azure, and SAP S/4HANA.

Please refer to the published GitHub repository and Discovery Center mission of the initial set-up (see blog).

About Author

Simplifying the IoT Puzzle with SAP Asset Performance Management and Cumulocity IoT

2023-08-16T16:23:24+02:00

Following up from my previous blog on SAP Asset Performance Management (APM) and SAP IoT, I'd like to share some additional thoughts about IoT and APM, because we see such a diverse range of different customer situations. While some customers have started rationalising on a preferred ‘strategic’ IoT platform, others have a range of IoT tools, and many have inherited extensive applications and historians which will remain valuable data sources. In almost all customers we see a mix of these scenarios, and no ‘one platform’ nirvana. Therefore, I’d like to reiterate how important it is for APM to provide robust IoT capabilities as well as a flexible integration framework to simplify this IoT puzzle.

As we see our customers continue to rationalize their IT/OT platforms and shift to a more outcome based approach, our APM IoT strategy will continue to be agnostic and be able to ingest equipment/sensor data from any data source or end point: smart or IoT devices/edge gateways, data historians and data lakes, and other IoT/OT platforms or middleware. Furthermore, APM offers standard integrations with SAP S/4HANA and ECC Plant Maintenance and it can blend maintenance records and inspection data and measuring documents along with sensor timeseries data to provide a complete view of the asset health for condition-based maintenance (CBM) and predictive maintenance (PdM). Some of CBM/PdM connectivity use cases that we have seen in our customer’s project include:

Oil & gas customers with data historians and data lake via REST APIs

Utilities customers with SCADA systems via OPC UA

Transportation customer with connected assets via MQTT and edge

Industrial manufacturing customers with shopfloor systems via Plant Connectivity (PCo)

You might have seen this press release from Software AG announcing that they are with working us on integration with SAP Asset Performance Management. This relationship is a great example of our strategy at work – integration with their market-leading Cumulocity IoT will help our joint, existing and new, customers to simplify their IoT connectivity scenarios and focus on leveraging their IoT data to optimize their maintenance plans and activities.

We also see this relationship opening the door for more innovative use cases such as servitization. As our equipment manufacturing customers start to roll out as-a-service business models, Cumulocity IoT and SAP Asset Performance Management can help ensure the smart equipment/product is always working and optimize the maintenance schedules based on actual usage and health conditions.

Please watch this space and we will have more IoT-related news later this year. To learn more about SAP Asset Performance Management, please visit sap.com/apm and check out my latest APM Overview webinar here.

Events-2-Business Action Framework – Create Service Ticket in SAP CX

2023-08-25T16:28:28+02:00

Companies are driving the digitization of the factory, plants, warehouses, and business networks and creating an ecosystem by linking Information Technology (IT) with Operational Technology (OT). Bridging the gaps between different landscapes and processes with integrated frameworks is key for building a seamless, efficient, bi-directional collaborative ecosystem.

This scenario is built to trigger service tickets in SAP CX automatically for repair or maintenance based on critical events determined by IoT device.

The intention of the initial project was to set-up an event-driven framework based on SAP Business Technology Platform (SAP BTP) to respond to and integrate with events generated from industrial production processes in plants, warehouses, and logistics into enterprise business systems, triggering associated business processes to enhance enterprise operations and enable rapid decision-making. Target of this generic framework is to configure new scenarios rather than developing them individually. With the framework we reduce the implementation time significantly.

This scenario is fully built on the framework without individual development or modification.

See blog initial project shared by PVN PavanKumar (SAP Labs India):

https://blogs.sap.com/2023/01/27/part-1-events-to-business-actions-architecture-an-event-driven-framework-on-sap-btp-to-implement-industry-4.0-scenarios-with-microsoft-azure-services/

See my blog about Events-2-Business Action Framework –
Create Plant Maintenance Notification in SAP S/4 HANA

https://blogs.sap.com/2023/08/03/events-2-business-action-framework-create-plant-maintenance-notification-in-sap-s-4-hana/

Our approach

Our aim is to adopt event-driven architecture, by building an open-source framework on the SAP Business Technology Platform (SAP BTP) which can integrate events generated from non-SAP platforms and solutions into SAP business processes thereby extending the value of existing SAP applications and processes. The events may originate from various sources such as IoT platforms, mobile and web applications, enterprise systems, and industrial production, logistics platforms, and so on. Thus, this framework helps in making business intelligent and interconnected to improve overall process efficiency. The Event-to-Business Framework can run on your own BTP or as SaaS solution provided by NTTDATA Business Solutions.

Figure-1: “Events-to-Business Actions” Framework

Business Scenario

Challenges

The Case

Create Service Ticket for external service technician to repair or maintain equipment

IoT device reports regularly status of equipment, i.e. manufacturing machine to MS Azure IoT platform

Rules for dedicated telemetry property, i.e. oil consmption to trigger export of exception data (oil consumption too high)

Stream event and interpret content enriched by business rules to create functional transaction for
“Create SAP CX Service Ticket“

Trigger posting mechanism in SAP CX

Figure-2: Process Steps

Process steps

Sensor/IoT devices determine conditions

Figure-3: Simulate abnormal temperature increase

Ingest the data in an IoT platform
(here Microsoft Azure IoT Central)

Figure-4: Data Export to SAP Event Mesh

Activities in Event-2-Business Framework

Figure-5: UI modeler

Actions

In this scenario with our preconfigured actions, we create a service ticket SAP CX system. For flexible configuration we use main actions (for each transaction), which can be chained with pre-action and post-action activities.

Figure-6: Action Categories

Figure-7: Actions to create Service Ticket

This framework leverages business rules capability within the SAP Build Process Automation, which lets you automatically choose a business action that should be executed for an incoming event based on the configured decision tables.

For the creation of a Service Ticket you need the Main-Action to feed the API with all required fields to execute the transaction. The data to feed the API has its source in the IoT platform (see Enrichment) or is derived from business rules. A Pre-Action fetches the derived data from the business rules, e.g. service priority, service category. The Post-Action is used for actions after the successful execution of the Main-Action. In this case we use it to set the status and ticket number in the device in MS Azure IoT. With that we avoid that the event is executed again after already creating a service ticket in SAP CX.

Business Rules

Figure-8: Business Rules

The Business Rule triggered by the action, for Service Ticket the Pre-Action triggers the Business Rule to determine relevant parameters to feed the payload of the Main-Action.

Using If – Then Rules to determine Service Priority, Incident Category, Service Category, etc. from Pump Type of Device.

Logging

Figure-9: Error Log

Every transaction processed is recorded in the (error) log. From the log lauchpad you can control the details of the event with its payload. A restart function is on the SAP development roadmap.

Reference Architecture

Figure-10: High-level architecture with SAP CX

Key Advantages of This Architecture

Developers implementing this framework architecture would benefit from the following design considerations.

A flexible and generic framework that can be easily extensible for any Line of Business (LoB) scenario /workflow/process and any source system events.

Event-driven integration architecture with SAP Event Mesh as a central hub, including a bi-directional flow of events (Microsoft Azure to SAP S/4HANA and vice versa). We are also evaluating on leveraging Advanced Event Mesh (to be updated soon).

Enriched with resilient and high availability architectural patterns.

Network security-focused design with SAP Private Link specifically for RISE with SAP customers between SAP BTP on Azure (any region) and SAP S/4HANA on Microsoft Azure

Scenario Setup and Deployment

About Author

Events-2-Business Framework – Create Shopfloor Confirmation in SAP S/4 HANA

2023-08-29T16:32:25+02:00

Our approach

Figure-1: “Events-to-Business Actions” Framework

Business Scenario

Challenges

The Case

Create Shop Floor Confirmation (here with NTT DATA IoTConnect App)

Simulation of a packing process in shopfloor which needs a worker confirmation

We simulate the recording of
- Packed good parts
- Scrap
- Rework

This leads to a partial confirmation on a shopfloor order

App triggers data record for each case and report to MS Azure IoT platform

Stream each event and interpret content enriched by business rules to create functional transaction for “Shopfloor order confirmation“

Trigger posting mechanism in SAP S/4 HANA

Figure-2: Process Steps

Process steps

Sensor/IoT devices determine conditions

Figure-3: Simulate Shopfloor Confirmation

Ingest the data in an IoT platform
(here Microsoft Azure IoT Central)

Figure-4: Data Export to SAP Event Mesh

Activities in Event-2-Business Framework

Figure-5: UI modeler

Actions

In this scenario with our preconfigured actions, we create a shopfloor confirmations in a SAP S/4 HANA system. For flexible configuration we use main actions (for each transaction), which can be chained with pre-action and post-action activities.

Figure-6: Action Categories

Figure-7: Actions to create Shopfloor Confirmation

This framework leverages business rules capability within the SAP Build Process Automation, which lets you automatically choose a business action that should be executed for an incoming event based on the configured decision tables.

For the creation of a Shopfloor Confirmation you need the Main-Action to feed the API with all required fields to execute the transaction. The data to feed the API has its source in the IoT platform (see Enrichment) or is derived from business rules. A Pre-Action fetches the derived data from the business rules. The Post-Action is used for actions after the successful execution of the Main-Action. In this case we use it to update the production order and confirmation number in the device in MS Azure IoT.

Business Rules

Figure-8: Business Rules

Logging

Figure-9: Error Log

Every transaction processed is recorded in the (error) log. From the log lauchpad you can control the details of the event with its payload. A restart function is on the SAP development roadmap.

Reference Architecture

Figure-10: High-level architecture with SAP S/4HANA on-premise and private cloud

Key Advantages of This Architecture

Developers implementing this framework architecture would benefit from the following design considerations.

A flexible and generic framework that can be easily extensible for any Line of Business (LoB) scenario /workflow/process and any source system events.

Event-driven integration architecture with SAP Event Mesh as a central hub, including a bi-directional flow of events (Microsoft Azure to SAP S/4HANA and vice versa). We are also evaluating on leveraging Advanced Event Mesh (to be updated soon).

Enriched with resilient and high availability architectural patterns.

Network security-focused design with SAP Private Link specifically for RISE with SAP customers between SAP BTP on Azure (any region) and SAP S/4HANA on Microsoft Azure

Scenario Setup and Deployment

About Author

Be Ready: Future-Proofing Asset Management in Your Organization

2023-10-20T17:22:09+02:00

My basement flooded a few weeks ago, and my wife was on a mission to get to the bottom of the issue. And like any good husband, I got out of her way, and let here get to the root of the problem. As it happens, due to unprecedented rain fall over a very short space of time (who says there is no such thing as climate change) the sump pump, the device that protects us against flooding, had failed. Unfortunately, it was not smart enough to alert us to this situation and simply gave up.

And this is a metaphor for the challenges we are seeing from larger disruptions all over the world, from the impacts of environmental, geopolitical, and other types of risks.

Yet, if you work at all in asset management, you’ve probably felt the impact of disruption much more deeply than most. Asset management and field service management are among the operations most hurt by unexpected events as well as environmental, geopolitical, and other types of risk. In fact, when companies aren’t careful, many disruptions to business actually start with an asset failure (like my sump pump).

That’s why asset management is evolving. The future of modern asset management is always on, increasingly intelligent, and now – accessible wherever you are.

Supporting asset management’s role in strong supply chains

As we move to the future, asset management continues to grow in importance. That’s because asset management professionals are responsible for a rapidly growing network of, often very expensive, equipment, and much of this equipment is more complex – and intelligent – than ever before. Advanced technologies such as IOT and artificial intelligence (AI) are increasingly available and play a role in effectively executing business processes. In field service management, there are a greater number of field service operators, too, spread across a larger range of services and supporting more customers.

Whether you’re managing your own assets or providing asset management services to customers, these operations have never been more demanding of your time and attention. However, despite this growing complexity, many businesses continue to depend on the asset management and field service management software designed for the equipment and processes of 20 years ago. This software isn’t prepared to support the demands of modern equipment – or the disruptions of tomorrow.

The latest generation of asset management software connects business processes by closing the loop between asset strategy and maintenance execution, helps companies make better decisions by contextualizing their asset health and performance data through real-time insights, and supports improved collaboration with the ecosystem through network solutions.

Enabling asset management in the moment and on the go

As you look to the future, it’s time to ask yourself one all-important question: how can my assets be always-on, even if my asset management software and professionals aren’t?

Any asset management software will focus on keeping your assets up and running, but the right asset management software will do so by empowering your workers anytime, anywhere.

A brief look back in time

Early 2020 posed an extreme challenge for those businesses that didn’t have the tools or data integration to continue supporting everyday operations off site. You may now offer your workers some asset management tools on mobile, but do they provide all the features workers need to do their jobs and keep your assets running? Are they integrated and serving the data insights workers need to make fast, accurate decisions?

Modern asset management software is designed for a holistic approach to asset management that empowers you to connect, contextualize, and collaborate. Ultimately, it’s one part of a whole business that doesn’t work as intended when it’s siloed away from other operations.

For example, if you’re a manufacturer, your asset management team should be able to collaborate freely with operators and service providers. The impact of disruption is compounded by silos across the business. In field service management, you should be able to integrate front- and back-office processes for effective collaboration across teams – while keeping customers informed.

Expecting the unexpected with predictive analytics

The seasonally high rain fall in my area wasn’t a complete surprise. However, the failure of my asset (the sump-pump) was. I had no way of knowing that it was going to break down. Why? Because it didn’t tell me! I didn’t have the data. Why didn’t I have an app on my phone to alert me when the water level got to a certain point? Or when the part started to fail (which was probably several weeks ago)?

In that same way, the right data and predictive analytics can help your business prepare for what’s next in asset management.

For example, AI-based predictive maintenance is designed to help you determine a piece of equipment’s failure curve based on calculated probabilities. With these insights, you can clearly see the equipment’s remaining useful life and quickly make the best decision for your business. Predictive analytics can also reveal the likelihood of service needs for specific operations or customers by analyzing historical data from previous service requests.

AI enhances your understanding of asset operations and helps you make more-informed decisions, especially when these insights are available on mobile for your workers on the go. Embedding AI into asset management can help you get on the path to achieving your most important asset management goals, such as eliminating unplanned asset downtime and increasing resource utilization. Enterprise asset management (EAM) solutions from SAP include AI-powered capabilities such as these.

EAM solutions from SAP, including the SAP Field Service Management solution, can help you create a more-resilient supply chain, deliver service precision, and revolutionize equipment performance. To learn more about SAP solutions and how they help enable modern, mobile asset management, visit us online.

Also, download the ARC Advisory Group report to learn how asset-intensive companies are rethinking their asset management priorities.

Oh! My wife now has a smart pump, and an app on her mobile phone to tell her exactly how it is performing. What else would you get your wife of 30 years on her wedding anniversary.

AWS and SAP – Joint reference Architecture for IoT scenarios using Amazon Monitron

2023-11-14T14:30:24+01:00

When industrial machinery breaks down, it often results in significant operational downtime. Predictive maintenance can alleviate many issues related to equipment upkeep, but its implementation is not without challenges. The process usually requires the integration of sensors, data infrastructure, data analysis, and machine learning, a blend of software and hardware skills that often leads to lengthy setup periods and delayed return on investment. Therefore, it is vital to find a solution for managing equipment failure that seamlessly integrates with existing business procedures for asset management and plant maintenance.

Amazon Monitron enables the customers to implement a predictive maintenance program and reduce unplanned downtime. SAP customers use SAP Enterprise Asset Management to create maintenance notifications for industrial equipment.

In this blog post, we will walk you through a framework on SAP Business Technology Platform (SAP BTP) with which we can provide an integration framework between Amazon Monitron and SAP S/4HANA Asset Management and thereby automating the process of creating maintenance notifications.

In the upcoming sections of the blog post, we will describe the solution architecture, systems involved, PoC scenario and a quick demo followed by the instructions to deploy the solution from a GitHub repository.

Engagement

The outcome described in this article was facilitated by an engagement between SAP and Amazon Web Services which resulted in the creation and validation of a joint reference architecture use cases and PoC. Teams from PVN Pavan Kumar (SAP Labs India) and Soulat Khan (Amazon Web Services) have participated in this engagement.

Business Scenario

Predictive maintenance plays a crucial role in helping industries avoid downtime by using advanced analytics and machine learning algorithms to predict equipment failures before they occur. By analyzing historical data and real-time sensor readings, it can identify patterns and anomalies that indicate potential issues. This enables proactive maintenance thereby minimizing the impact on production.

In this scenario, abnormal conditions are detected and the events are generated and sent to the Events-to-Business Action Framework which maps it to an associated business action, which in this case, is to create a maintenance notification in SAP S/4HANA Asset Management. The business value of this integration helps industries to improve operational efficiency and ensure uninterrupted production.

Amazon Monitron is an end-to-end system that uses machine learning to detect abnormal conditions in industrial rotating equipment, enabling you to implement a predictive maintenance program and reduce unplanned downtime. It includes sensors to capture vibration and temperature data, a gateway to securely transfer data to AWS, a service that analyzes the data using machine learning (ML), and a companion mobile and desktop app to set up the devices and track the condition of your machinery. The Monitron service can export data to a kinesis stream and S3, making data available for downstream SAP integration. For more information, please check out Amazon Monitron.

Image courtesy : https://aws.amazon.com/pm/monitron

SAP Enterprise Asset Management (EAM) helps organizations to plan, optimize, execute, and track the necessary activities, priorities, skills, materials, tools, and information associated with an asset. Failure to manage and maintain enterprise assets can lead to unplanned downtime, suboptimal asset performance, and supply shortages. Customers also rely on EAM systems to demonstrate compliance with regulatory bodies to preclude liability if a failure occurs. To learn more about SAP EAM solution, refer SAP Enterprise Asset Management

Solution Architecture

The following steps depicts the information flow across systems:

(1) Event is triggered from Amazon Monitron Hardware and sent to Amazon Monitron Software.

(2) and (3) Amazon Kinesis streams the sensor data from Amazon Monitron and lands it into the Amazon S3 bucket.

(4) AWS Lambda is a serverless function, which will orchestrate the process of detecting a stream contains any alerts related to failure or warnings, and then the inference result is passed to SAP Advanced Event Mesh.

(5a) AWS secrets manager is used to store credentials; these are used by the lambda function to provide payload to SAP Advanced Event Mesh.

(5) Event-to-Business-Action framework (extension app) processor module's endpoint is subscribed to SAP Advanced Event Mesh, hence receives this event.

(6) Event-to-Business-Action framework processor module leverages the Decisions capability of SAP Build Process Automation to derive a business action (for example, in this scenario, Plant Maintenance Notification creation in SAP S/4HANA system) based on certain characteristics of incoming event.

(7), (8), (9) (10) and (11) Event-to-Business-Action framework processor module triggers the defined action in the SAP S/4HANA system by using the SAP Destination Service and SAP Private Link Service.

The integration architecture uses SAP “Events-to-Business Actions” architecture which is an event-driven framework on SAP Business Technology Platform (SAP BTP) to respond to and integrate with events generated from industrial production processes in plants, warehouses, and logistics into enterprise business systems, triggering associated business processes to enhance enterprise operations and enable rapid decision-making.

Scenario Setup and Deployment

To get the entire scenario working, there are prerequisites and initial configurations required in SAP Business Technology Platform, Amazon Web Services, and SAP S/4HANA.

Please refer to the published GitHub repository which contains code samples and instructions for implementing this scenario

GitHub Repo

Discovery Center Mission

We have created this reference architecture with accompanying sample code which can be configured and extended as per your requirements. However, it is up to the end user to utilize the code, make modifications and keep it maintained for productive use.

If you are using AWS IoT services for your own sensors, please follow the instructions here:

GitHub Repo

Benefits The business value and technical benefits of this integration are the following:

Detect machine issues before they occur with machine learning (ML) and take action to reduce operational costs.

Start monitoring equipment in minutes with easy installation and automatic, secure analysis through the Amazon Monitron end-to-end system.

Improve system accuracy continuously as Amazon Monitron learns from technician feedback entered in the mobile and web apps.

Network security-focused design with SAP Private Link specifically for RISE with SAP customers between SAP BTP on AWS (any region) and SAP S/4HANA on AWS

Event-driven integration architecture with SAP Advanced Event Mesh as a central hub.

Demo

The industrial equipment in Manufacturing plant is connected to Amazon Monitron that sends an event to SAP Advanced Event Mesh once abnormal condition is detected and the Event to Business Actions framework process the event and enriches it will relevant business context using decision tables from SAP Build Process Automation and creates a maintenance notification in SAP S/4HANA.

You can watch a demo here that showcases the PoC scenario

In Closing

We hope this blog has given you a brief idea on how to integrate events generated from industrial equipment to trigger different business actions/workflows/process in SAP backend systems.

On the SAP side, Many thanks to Uma Anbazhagan from SAP for driving this topic by collaborating with all the stakeholders involved in the engagement, Swati Maste and Ajit Kumar Panda for supporting the development of this solution, Madankumar Pichamuthu for enabling collaboration and finally Anirban Majumdar, PVN Pavan Kumar, Sivakumar N for leadership support for this project.

On the Amazon AWS side, Many thanks to Soulat Khan, Ganesh Suryanarayanan, Sunny Patwari, Renga Sridharan, Aiyappa Machanda, Abhik Ray, Suresh Pulivarthi, Krishnakumar Ramadoss and the SAP APN Partner Innovation team for their support in this project.

To learn more about SAP BTP, see the learning journey on SAP Learning called Discover SAP Business Technology Platform, a great introduction to BTP and the Intelligent Enterprise strategy to see what it’s all about for free.

As part of the global partnership between SAP and AWS, we have jointly developed an openSAP course titled “Build Resilient Applications on SAP BTP with Amazon Web Services

[Registration link] https://open.sap.com/courses/aws1

By joining this free openSAP course, you'll delve into multiple Joint Reference Architecture patterns, gain in-depth knowledge of the architectural patterns and also have the opportunity to enhance your skills through hands-on exercises.

To learn more about Amazon AWS, visit AWS training

For more information about this topic or to ask a question, please contact us at paa_india@sap.com

SAP Business Network Asset Collaboration and Classification Content by ECLASS: FAQs

2024-02-05T08:12:27.272000+01:00

This FAQ blog deals with questions related to the partnership of SAP Business Network Asset Collaboration and the classification content provider ECLASS. Main aspects are how the ECLASS classification is made available in SAP Business Network Asset Collaboration, how customers can get access to the ECLASS classification content in SAP Business Network Asset Collaboration, and what to do if you are missing ECLASS classification content either in SAP Business Network Asset Collaboration or in ECLASS.

General Questions

What is ECLASS?

ECLASS is a cross-industry product-data standard for the classification and unique description of products and services.

For more information on the company and the standard, please refer to the official ECLASS Web pages (https://eclass.eu/).

How does SAP Business Network Asset Collaboration work with ECLASS?

SAP Business Network Asset Collaboration and ECLASS have a partnership, and ECLASS acts as a Content Provider in SAP Business Network Asset Collaboration. This means that ECLASS is a participant in the network and ECLASS classification objects get created by ECLASS in their account and will be shared by ECLASS with their licensees in the network.

Content-Related Questions

Which ECLASS version is available with SAP Business Network Asset Collaboration?

ECLASS versions 10.1 and 12.0 are currently available.

Which ECLASS objects will be available in SAP Business Network Asset Collaboration?

ECLASS classification objects will be loaded as SAP Business Network Asset Collaboration Template objects, i.e., classes, subclasses, attribute groups, nested structures, attributes, and code lists.
Note: In ECLASS version 10.1, you can still see ECLASS model templates. These were used as a temporary workaround to realize the loading of ECLASS aspects when SAP Business Network Asset Collaboration (then SAP Asset Intelligence Network) did not have the nested structures functionality yet.

With ECLASS version 12.0, ECLASS Blocks and Aspects are represented as nested structures in SAP Business Network Asset Collaboration.
The obsolete Model Templates (= representation of Aspects) are still visible in version 10.1 but should not be used anymore.

In the beginning the following ECLASS segments will be available in the productive landscape:

– Segment 19 (Information, communication and media technology)

– Segment 23 (Machine element, fixing, mounting)

– Segment 27 (Electric engineering, automation, process control engineering)

– Segment 36 (Machine, apparatus)

– Segment 37 (Industrial piping)

More segments will be made available in upcoming releases. The sequence/priority of additional segments will be decided based on customer requests (see below).

It looks like ECLASS is currently only available in English and German language? Will there be other languages available?

Yes, ECLASS classification is currently available in languages English and German. Further languages supported by ECLASS can be made available for version 12.0 upon request (see below).

What can I do if I need additional ECLASS segments or additional ECLASS languages in the SAP Business Network Asset Collaboration productive landscape?

Please create an incident under component SBN-AIN-ACF-CNT and request the segment or language you need. ECLASS will then upload the requested segment(s) as soon as possible.

Note: You should only create such a segment request for ECLASS if you already have an ECLASS license (see LICENSING section below).

What can I do if I need additional classification content in ECLASS?

Missing content can be requested from ECLASS. Please follow the general process of submitting Change Requests to the ECLASS standard (refer to https://eclass.eu/support/guides/change-request). For questions, please contact directly ECLASS Office: info@eclass.de.

Licensing Questions

Does ECLASS classification content come for free with SAP Business Network Asset Collaboration?

A subset of ECLASS structural elements will be made available for a free Trial in the Test and Demo system. The classification content (= ECLASS segments) which is available as free trial are:

– Segment 19 (Information, communication and media technology)

– Segment 27 (Electric engineering, automation, process control engineering)

– Segment 36 (Machine, apparatus)

– Segment 37 (Industrial piping)

To use this free trial content, please create a connection request with ECLASS e.V. in the Test and Demo system. ECLASS will then trigger the sharing of the free trial content for your account. For productive use – i.e., in SAP Business Network Asset Collaboration Production landscape – you require a dedicated license from ECLASS to be able to model business objects using ECLASS content.

Note: There will be no migration possible from the free trial version to the productive system.

How can I license ECLASS and what are the costs?

Licensing of ECLASS classification content is handled by ECLASS. You can view the available licensing models on the ECLASS Web site (https://eclass.eu/en/eclass-standard/licenses).
For direct inquiries regarding the exact licensing options for your company, please directly contact the ECLASS office (info@eclass.de).

My company already has an ECLASS license. Can I use this for SAP Business Network Asset Collaboration as well?

ECLASS will share their objects with their licensees based on their customer list. So, if you already have an ECLASS license this will also be valid for use of ECLASS in SAP Business Network Asset collaboration.
As an ECLASS licensee, please create a connection request with ECLASS e.V. in the Production system. ECLASS will then trigger the sharing of their content for your account. For any license-related questions (including ECLASS sharing via SAP Business Network Asset Collaboration) you can also contact ECLASS directly (e-mail: info@eclass.de).

I have a Premium account in SAP Business Network Asset Collaboration, and I want my Invitee accounts to create classification content based on ECLASS classification. Will my Invitees need an own ECLASS license for this?

If objects are to be modelled based on ECLASS classification objects a dedicated ECLASS license is required independent of the SAP Business Network Asset Collaboration account type. Therefore, Invitees who model objects in SAP Business Network Asset Collaboration based on ECLASS classification content need an own ECLASS license.

Jowat: Seamless Just-in-Time Operations with SAP Digital Manufacturing to Make Better Decisions

2024-02-23T15:58:30.269000+01:00

Jowat Group is one of the world’s top adhesive manufacturers for industrial use. Tradition and experience from 100 years of corporate development and experience allow it to act as leading company in technology and innovations, in numerous markets and application areas. Jowat SE’s annual production amounts to 100,000 tons of industrial adhesives. Their production is complex and requires high volumes of specialized chemicals and a tremendous amount of power. With raw materials and energy costs skyrocketing, premium manufacturer Jowat looked to get a tighter grip on its inventory management and production processes.

To ensure maximum efficiency, Jowat requires enough raw materials to fulfil orders, while minimizing waste and inventory costs. Moreover, the company needs smooth workflows as any delay in order placement, production, or the delivery of raw materials can have huge cost implications for the company.

As a result, Jowat works hard to ensure that its 24/7 manufacturing processes always run like clockwork.

With demand for industrial adhesives surging, the company was eager to ensure that its production processes could scale to meet increasing order numbers and still deliver optimum efficiency.

Targeting Seamless Digital Workflows

Originally established in 1919, Jowat is no stranger to innovation. Leaders at Jowat identified that the next stage of the company’s evolution would require a radical digital transformation of its production and inventory management processes.

“Our factory workers relied heavily on paper-based processes,” explained Dirk-Alexander Segger, Detmold Plant Manager at Jowat. “For instance, when employees had finished mixing and decanting adhesives, they handwrote notes to track the volume and type of raw materials that they used during the process. Shortly after decanting, workers would then input the information from their notes into our inventory management and manufacturing execution systems—adding to their workload and increasing the risk of errors.”

Tracking materials usage manually created both time-delay, and potential for human errors, as well as discrepancies between the stock amounts recorded in Jowat’s inventory system and the actual volume of raw materials available on the factory floor. Moreover, with information stored across multiple systems and in different formats, plant managers had no clarity to identify process bottlenecks or potential enhancements.

Annette Podleschny-Borchardt, Project Lead at Jowat, commented: “To enhance efficiency, improve transparency, and prepare for growth, we decided it was time to go entirely paperless. Building digital processes would give us a more detailed, up-to-date picture of our stock position, which would help to drive smarter raw materials purchasing decisions as well as production improvements.”

“We aimed to take a more proactive approach to our manufacturing processes. Developing robust, reliable, end-to-end digital workflows was the perfect way to achieve this goal,” explained Christine Künne, Head of IT and Business Process Services at Jowat SE.

Embracing Digital Transformation

To find the best solution to support its digital transformation initiative, Jowat invited multiple technology vendors to outline the strengths of their solutions. To keep customization low, Jowat targeted a solution that it could easily adapt to meet the highly specialized nature of just-in-time chemicals manufacturing.

After reviewing 15 different solutions, Jowat selected SAP Digital Manufacturing (SAP DM). As well as providing a solid foundation for digitalization, SAP Digital Manufacturing also integrates seamlessly with Jowat’s existing SAP solutions, including SAP S/4HANA, SAP Extended Warehouse Management, and SAP Business Technology Platform.

“We were immediately interested in SAP Digital Manufacturing because it is a cloud-native solution,” commented Dirk-Alexander Segger. “Previously, we used on-premise solutions that required us to carry out extensive and disruptive updates. With SAP Digital Manufacturing, we get instant access to the latest features thanks to the quarterly release schedule.”

Jowat also valued SAP’s proactive engagement with the chemicals manufacturing industry. “We really appreciate that SAP is eager to co-innovate with industry leaders like Jowat to develop next-generation manufacturing solutions,” said Annette Podleschny-Borchardt. “Through the SAP Customer Engagement Initiative, we can help expert developers at SAP build smart factory solutions that meet the needs of our sector down to the finest detail.”

Sticking with the Experts

To ensure a smooth implementation of SAP Digital Manufacturing, Jowat relied on support from SAP Services and Support.

“Whenever we hit a stumbling block, the experts helped us work through the issues. For instance, we wanted to develop a dedicated production operation dashboard, which would give plant managers fast access to key production metrics. As this was uncharted territory, it naturally took a lot of time and energy to work through and SAP was behind us every step of the way,” said Dirk-Alexander Segger.

Currently, Jowat is completing the first phase of the SAP Digital Manufacturing implementation at its Detmold factory before expanding the solution across all plants. Christine Künne explained: “With a phased implementation we can ensure that the processes we build at our Detmold plant are tried-and-tested to deliver maximum efficiency. This will give us the best chance of success when we roll out these processes across all our facilities.”

“Consultants from SAP Services and Support brought not only their expertise to the project, but also the willingness to listen to the needs and the challenges of our industry. Because of this, we were able to collaborate extremely effectively,” added Annette Podleschny-Borchardt.

Driving Efficient Manufacturing with High-quality Data

With SAP Digital Manufacturing, Jowat left error-prone, manual processes behind and benefits now from seamless digital workflows with end-to-end transparency. This increases quality and eases work for shop floor operators. The activity confirmation is automatically done in the SAP system enabling real-time inventory insight.

Consequently, Jowat gained the following benefits:

100% digitalized manufacturing process
One source of truth for detailed production information
Time savings of 3 person days per week through automated raw material consumption updates allowing employees focus on higher value activities
100% accurate inventory

Dirk-Alexander Segger said: “Today workers feed consumption information at the point of production. Previously, it would take one full-time employee three days a week to track raw materials consumption. With SAP Digital Manufacturing, we have a real-time, accurate picture of our raw materials usage and needs. This is helping us optimize usage and reduce costs.”

Annette Podleschny-Borchardt added: “Production processes are so much faster now that we have built streamlined digital processes. Before, our paper-based ways of working could add up to five days to production timelines. With SAP Digital Manufacturing, we’ve shaved off this time, allowing us to produce and distribute products to our customers much faster—boosting satisfaction.”

Planning ahead for an AI-driven Future

With reliable, up-to-date information in SAP Digital Manufacturing, plant managers and leaders at Jowat have full visibility across the entire manufacturing cycle. Christine Künne said: “SAP Digital Manufacturing has helped improve the traceability of our products and given us a much more detailed understanding of our manufacturing operations. Ultimately, that helps to enhance planning and provides new insights into potential process improvements.”

Jowat’s plans for SAP Digital Manufacturing go far beyond a global rollout. The company is already exploring the potential to scale and streamline manufacturing processes further with artificial intelligence (AI) and Internet of Things (IoT) technologies.

“AI holds tremendous potential for us,” reflected Annette Podleschny-Borchardt. “We’re excited to explore how it can help us to ensure consistently excellent quality across heavily customized product lines, and how we can enhance production uptime with IoT-driven predictive maintenance. Having an AI-ready solution like SAP Digital Manufacturing at the heart of our operations makes taking these next steps in our innovation journey much easier.”

Summarizing the overall benefits, Christine Künne concluded “With the implementation of SAP Digital Manufacturing through SAP Services and Support, we see ourselves on the way to becoming a transparent factory with a reduction in risks, errors, and process costs thanks to optimized processes.”

Click here to see what benefits other companies have gained including improving quality with AI-assisted visual inspection. Be sure to listen to a webinar how a renowned manufacturer revolutionizes manufacturing with Industry 4.0. Also, read a report from Oxford Economics enabling you to make your supply chain more resilient and sustainable.

Oliver Schreiber

2024-02-29T14:55:22.990000+01:00

About Oliver Schreiber

Bielefeld, Germany

SAP Mentor since 2015

Oliver is a business and solution architect with strong focus on platform-based services leveraging SAP Business Technology Platform. Active startup entrepreneur with B2B SaaS services and the FinTech solution LiquidityHub on SAP Store! Long term history as SAP partner in many roles and a strong network in the SAP Ecosystem.

Topics of interest: SAP BTP, SaaS, PaaS, cloud architecture, platform-based business models, partner business models, SAP strategic advisory for SAP ERP transition program guidance, cloud operation

Oliver, what inspired you to become an SAP Mentor?

When I founded my company in early 2015 to leverage the upcoming platform-based business on SAP platform technology, I was asked to join the SAP Mentor team to bring in my skills of working with SAP for more than 20 years in different partner roles internationally. I was very excited and honored to become part of such an unbelievably nice, experienced, international team of experts that works so well together, stays honest and always has a lot of fun. I was very impressed with the overall experience and that our input and feedback was taken seriously by the SAP board and management which then led to real improvements in several areas.

What advice would like to share with other SAP community members?

We never had better circumstances and easy access to enabling technologies to design and establish new software solutions and businesses to start something new. Building a new business as a startup or a new solution based on SAP platform technologies is possible with limited investment for skilled people today. Always do that with a real customer as a pilot and properly analyse that there is a real market for it and how to reach it. Whether you are a developer or architect, or even a sales representative, it doesn’t matter, as long as your role fits your personal strengths and desire and you build the right team around it. And the community might be the right forum to find them and get early feedback.

Eduardo Chagas

2024-03-29T18:49:39.614000+01:00

About Eduardo

Rio de Janeiro, Brazil
SAP Mentor since 2013

Professional with over several years of experience in the field of Information Technology, with a great passion for IT and continuous improvement. I enjoy being part of a dynamic and fast-growing environment where I can apply all my knowledge and skills to new challenges every day. Excellent interpersonal relationships and a strong commitment to achieving goals.

Topics of interest: S/4HANA, Supply Chain, Logistics, Transportation Management, Warehouse Management, Logistics Business Network, Yard Management, Transportation Resource Management, IoT, AI & Machine Learning

Eduardo, what inspired you to become an SAP Mentor?

I was inspired by other professionals such as Henrique Pinto, Marlo Simon and Tobias Hofmann who were already SAP Mentors and who, in addition to their technical knowledge, did a lot to build and develop the SAP community in Brazil.

What advice would like to share with other SAP community members?

Hard work! If you want results in your business, whether personally or professionally, you need to dedicate yourself and go further! Having discipline and consistency is essential to get results. Another important point in my opinion is... you should ask yourself at all times "How can I add value to my client? To the process?". We cannot simply deliver a solution but rather ensure that it returns value to the customer.

IoT - Ultimate Data Cyber Security - with Enterprise Blockchain and SAP BTP 🚀

2024-04-22T11:07:39.454000+02:00

It wasn't that long ago that Cyber Security and Resilience translated to High Availability and Disaster Recovery. Driven by the Sensitivity, Confidentiality, and Availability requirements of the Data, Systems and Applications were built to have the highest possible availability. That requirement came from the times when an entire end to end Business Process ran in a single standalone Application.

Fast forward to today, end to end Business Processes can begin in one Application on one side of the world and pass through Applications somewhere else in the world and finish in Applications in an altogether different location in the world. The beginning of the Business Process can be Sensors and Things at the Edge, producing Data, Events, something has happened and triggered the Business Process.

This creates several problems:

Protect the Originality & Integrity of the Data - When the Thing, the IoT Sensor, let's say critical infrastructure, something like a Base Station in a Telco Network, or a piece of the Electrical Grid for a Utility Company, when the Thing, the IoT Sensor creates the piece of Data, a Record of something that just happened we need to make sure that piece of Data cannot be modified or destroyed and therefore protect the originality and integrity of the Data

Moving the Data from the Edge to the SAP Application in the Cloud or DataCenter and at the same time Protect the Originality & Integrity of the Data - we need to get the Data from the Thing, the IoT Sensor, to the SAP Application in the Cloud or DataCenter and we need to be sure, to have surety that the Data which arrives in the SAP Cloud or DataCenter is exactly the same Data that was created at the Edge at the Thing, the IoT Sensor. If this Data gets changed in any way, we won't be able to trust the Business Processes and Insights which are depending on that Data. And so, in the activity of moving the Data we need to make sure that that piece of Data cannot be modified or destroyed and therefore protect the originality and integrity of the Data

And so, here we are, the biggest threat to Enterprise SAP Applications is no longer the High Availability, the Server crashing, that's all under control and possible to take care of,

The biggest threat to IoT & Enterprise SAP Applications is Cyber Security and Cyber Attacks

A common thought is that a hacker, or cyber attacker wants to modify Data for their own financial benefit, for example change the destination bank account number for invoice payments, yes those threats are still there, but biggest threat is that a hacker or cyber attacker deletes or modifies Master and Transaction Data resulting that the Master and Transactional Data does not have integrity and cannot be used, and if the attacker succeeded to modify the Backup as well, then the Enterprise could be out of business for a long time trying to pick up the pieces and get up and running again.

The biggest threat to IoT & Enterprise SAP Applications is Cyber Attacks rendering the Master and Transaction Data un-trustworthy

And that's where the Enterprise Blockchain comes in, and this blog is going to explain why.

Ok let's go🚀

Welcome to the eighth blog in this series on Enterprise Blockchain and SAP. If you have been following the previous blogs then you'll be familiar with the blog template. We'll begin by talking about and framing the problem, in this case Data Cyber Security for IoT and SAP and then go in to identifying the enabling technology which will have the best capabilities and be the most appropriate to solving the problem all the way through to the reference solution architecture to be able to implement the solution.

The blog is going to break the subject down in to three sections:

Section 1.0: The What is it of IoT & SAP, and Enterprise Blockchain

Section 2.0: The Why is it, of IoT & SAP, and Enterprise Blockchain

Section 3.0: The How is it, of IoT & SAP, and Enterprise Blockchain

tl:dr

If you want to protect the originality and integrity and confidentiality of IoT data, from the Edge to Insights and SAP Business Processes, then the answer is an Enterprise Blockchain Database, where the Enterprise Blockchain Tenants are running on Edge Hosts/Servers and in the SAP BTP Business Technology Platform, enabling Enterprise Blockchain Database to protect the Data from the Edge Hosts/Servers to the SAP BTP.

IoT Internet of Things Edge Data Cyber Security and SAP Asset Performance Management BTP Protected by Enterprise Blockchain - atkrypto.io

[the finer technical details of getting the data from the Enterprise Blockchain to SAP Asset Management and S/4HANA will be clearer possibly after Sapphire Orlando in June. In the mean time there are a number of ways to get the Data in and out of the Enterprise Blockchain running on the SAP BTP Kyma Service]

Enterprise Blockchain is both:

. a Secure Store

. a Secure Communication Channel

Enterprise Blockchain is the Cyber Security for Enterprise IoT Data from the Edge to Insights 🚀

and now.... the long answer...

Section 1.0: The What is it of IoT & SAP, and Enterprise Blockchain

What is IoT Internet of Things ?

History of IoT

In 2021, there were over 10 billion IoT devices in the world, and by 2025, the IDC expects global data generation to exceed 73 zettabytes – which is equal to 73 trillion gigabytes. Although we can’t really quantify digital data in physical terms, we can say that if all that data were converted into 1990s floppy disks – and they were laid out end to end – they could go to the moon and back over 5,000 times.

[Source: What is IoT? The Future of Business | SAP]

What are some IoT applications?

Looking at IoT applications, which are sometimes described as use cases, can help ground the discussion about what IoT is. Broadly, IoT applications occur in one of nine settings.

Human health. Devices can be attached to or inserted inside the human body, including wearable or ingestible devices that monitor or maintain health and wellness, assist in managing diseases such as diabetes, and more.
Home. Homeowners can install devices such as home voice assistants, automated vacuums, or security systems.
Retail environments. Devices can be installed in stores, banks, restaurants, and arenas to facilitate self-checkout, extend in-store offers, or help optimize inventory.
Offices. IoT applications in offices could entail energy management or security for buildings.
Standardized production environments. In such settings, including manufacturing plants, hospitals, or farms, IoT applications often aim to gain operating efficiencies or optimize equipment use and inventory.
Custom production environments. In customized settings like those in mining, construction, or oil and gas exploration and production, IoT applications might be used in predictive maintenance or health and safety efforts.
Vehicles. IoT can help with condition-based maintenance, usage-based design, or presales analytics for cars and trucks, ships, airplanes, and trains.
Cities. IoT applications can be used for adaptive traffic control, smart meters, environmental monitoring, or managing resources.
Outside. In urban environments or other outdoor settings, such as railroad tracks, autonomous vehicles, or flight navigation, IoT applications could involve real-time routing, connected navigation, or shipment tracking.

Other real-world examples abound. IoT solutions are being used in myriad settings: in refrigerators, to help restaurants optimize their food-compliance processes; in fields, to track livestock; in offices, to track how many and how often meeting rooms are used; and beyond.

What is the economic impact of IoT?

The potential value of IoT is large and growing. By 2030, we estimate it could amount to up to $12.5 trillion globally. That includes the value captured by consumers and customers of IoT products and services.

The potential economic value of IoT differs based on settings and usages, with factory settings and human health applications representing outsize shares of this total. Factory settings could generate $1.4 trillion to $3.3 trillion by 2030, or just over a quarter of the total value potential. IoT economic impact in human health settings could reach around 14 percent of the total estimated value.

Another way of looking at IoT’s value is to explore use-case clusters (similar uses adapted to different settings). Some of the most common use cases account for a sizable share of IoT’s potential economic value:

operations optimization, which is basically making the various day-to-day management of assets and people more efficient (41 percent)
health (15 percent)
human productivity (15 percent)
condition-based maintenance (12 percent)

Other clusters include sales enablement, energy management, autonomous vehicles (the fastest-growing cluster), and safety and security.

[Source: What is IoT: The Internet of Things explained | McKinsey]

Like everything else we do in Enterprise IT,

IoT Internet of Things is about Data

What is Enterprise Blockchain ?

Enterprise Blockchain is both:

. a Secure Store

. a Secure Communication Channel

McKinsey & Company, in their December 2023 Featured Insights Publication, gave a beautiful description of what is unique and special about Blockchain, "Blockchain is a secure database shared across a network of participants, where up-to-date information is available to all participants at the same time". If we just pause for a moment and let that sink in, and think about what that means, to Business Processes, to Collaboration, to System Resilience, we start to see what is so special about Blockchain Databases and Distributed Ledger Technology.

In these previous blogs, I made a deep dive in to what Enterprise Blockchain is and why we should be positioning it in our Enterprise Architecture:

Why I love SAP and Blockchain Databases and why you should too🚀

SAP Enterprise Architecture: Positioning Blockchain Database as an Enterprise Technology Standard🚀

SAP Enterprise Architecture: Let the Use Case find the Blockchain 🚀

IoT Internet of Things and SAP - Enterprise Blockchain is the next generation Data Cyber Security Protection - atkrypto.io

and in a nutshell, Enterprise Blockchain is:

. The Digital Transformation of Information Security into Cyber Security

. The Next Generation Data Integrity, Originality, Confidentiality Protection

. Re-imagining Information Security

. Natively, out of the box, due to its special characteristics the strongest, hardest, most resilient Enterprise Database product

To wrap up this section:

. Iot Internet of Things is about Data

. Enterprise Blockchain is about Cyber Security of Data

Section 2.0: The Why is it, of IoT & SAP, and Enterprise Blockchain

So, why does IoT, Internet of Things, in the Enterprise IT, when implemented in conjunction with SAP Applications need Enterprise Blockchain ?

IoT is about Data, and the Data in most cases originates from the Edge and outlying parts of the Network.

The problem is the Cyber Security of getting the Data from the Edge and outlying parts of the Network to the safe zones of the SAP Cloud and yours or SAP's DataCenters.

IoT's biggest risk is that the Data coming from the IoT Devices is not trustworthy. In the same way as asking the wrong person for directions can leave you going all around the houses, if the Data coming from the IoT Devices, has been changed/contaminated/modified/poluted/made unreliable, whether purposefully through malicious acts or cyber attack, or accidentally, the result will be IoT's Data insights which cannot be trusted, and the result of that could be catastrophic. Just imagine not being able to trust the temperature of refrigeration during pharmaceutical and food production !

If we cannot protect and the originality and integrity of IoT Data, secure it, then how can we trust IoT Data ?

As Mckinsey & Company say:

IoT is about the Data

So, if we are going to do IoT and include IoT Data in our Business Processes and Insights, then we need to care for and protect the Data that is coming from IoT Devices.

Imagine, as described in the previous blog, when we let the Use Case find the Enterprise Blockchain, we have a Business Requirement, a Business Demand, to make IoT Data trustable.

When we look in our Enterprise Technology Standards, and we look for the Technology Standard in our Enterprise Portfolio which is positioned to bring the strongest protection to Data, we find the Enterprise Blockchain.

Comparison Enterprise Blockchain Database and Traditional Legacy Database - atkrypto.io

In the previous blogs, we have discussed in detail about the special characteristics of Enterprise Blockchain and just why it natively out of the box protects the integrity of data to a level that legacy database products cannot do, in a nutshell....

IoT is about Data

IoT is about the Data that goes in to the SAP Applications in the Cloud and Data Centers

This means IoT Device Data depends on a Database or a Datastore

What kind of Database do IoT Devices produces ? What capabilities does the Database for the IoT Devices Data need to have ?

1. It must not be possible to modify the Data in the Database which comes from the IoT Devices - the Database needs to be immutable

2. The Data in the Database, the integrity and originality of that Data must be protected to the highest level that is technically possible

3. The Data must be available with the highest availability, the Database must be resilient to attack

When we look in our Enterprise Technology Standards we find 1 Technology Standard in the Enterprise which has those capabilities, and that is..... Enterprise Blockchain

Enterprise Blockchain ticks those three boxes...

Immutable - tick that box

Integrity must be protected to the highest level - tick that box, thanks to the Enterprise Blockchain Hash Mechanism and the Enterprise Blockchain Consensus Mechanism

Highest level of resilience and availability - tick that box thanks to the Distributed and Decentralised nature of the Enterprise Blockchain

This is why, Enterprise Blockchain is the enabler of trustable outcomes from Enterprise IoT Devices' Data.

atkrypto.io what is a blockchain

But there's more than that, IoT Devices can produce a lot of data, and the volumes of data can be big.

And this is why, in this blog we take the Enterprise Blockchain Technology story one level further and we introduce the:

Enterprise Blockchain Wallet

Off-Chain Data Storage

In the Enterprise Blockchain Platforms, the Enterprise Blockchain Wallet is used for Off-Chain storage of big data and in the following paragraphs we will explain why.

What is the Enterprise Blockchain Wallet, and what is Off-Chain Data Storage and why would we use them and why do we need them ?

As we have explained in a previous blog, the Enterprise Blockchain Database, the Distributed Ledger, can be looked at simply as a Database Table (which is replicated and synchronised across multiple Servers) and in principle it stores the Data like this:

Blockchain is a very simple form of database atkrypto.io

This is fine, and suited to what we call Structured Data, and as AWS nicely describe, Structured Data is information like words and numbers. This kind of data is perfectly suited to being stored in an Enterprise Blockchain Database and also a legacy Database. Examples of the data would Names, Addresses, Phone Numbers, Product Information etc.

But, IoT Devices can produce a lot of Data, for example, there could be photographs proving that general waste was tipped at the correct certified location, photographs and in large volumes would be too big to be stored on the Enterprise Blockchain Database itself.

And that's ok, Enterprise Blockchain Platforms are ready for that, and have been designed to store both Structured Data and Data which is in files which are so big that they cannot be stored in the Enterprise Blockchain Database itself, for example the photographs from a Waste Truck's onboard camera proving that waste was responsibly tipped in the correct location and taken at the same time as recording GPS location coordinates proving the location of the Waste Truck.

So, if we can't store the large photographs files in large quantities to the Enterprise Blockchain Database, then how, in an Enterprise Blockchain Platform do we store large files of Data ?

Voila.... bring in the Enterprise Blockchain Platform Wallet. The best Enterprise Blockchain Platform products include what is called the Enterprise Blockchain Platform Wallet, or to make it shorter, the Enterprise Blockchain Wallet.

The Enterprise Blockchain Wallet enables us to store large Data, like large Files safely and securely off the chain, or 'Off-Chain'.

But if we store the large Data files Off-Chain in the Enterprise Blockchain Wallet, then how do we also have them some how on the Enterprise Blockchain Database ?

The way this works is elegant, in any decent Enterprise Blockchain Platform, the Enterprise Blockchain Wallet location is completely configurable, and could be anywhere from SAP HANA Cloud (Data Lake), or for example multiple hyperscaler object stores, such as Amazon S3, OSS (Alicloud Object Storage
Service), SAP HANA Cloud, Data Lake, and Azure Blob Storage.

The configurable Enterprise Blockchain Wallet of the Enterprise Blockchain Platform looks like this:

Enterprise Blockchain Platform - Enterprise Blockchain Wallets - Configurable Enterprise Wallets - atkrypto.io

Ok, so we've got the IoT Data stored in the (configurable) Enterprise Blockchain Wallet, but what about securing the IoT Data ? Obviously the Enterprise Blockchain Wallet storage location has built in security, for example the SAP HANA Cloud, the AWS S3 Buckets, but we need more than the out of the box security of these products, the reason we are using the Enterprise Blockchain Database is because of the amazing security strengths that it natively out of the box has, and so, what about the Enterprise Blockchain Wallet, doesn't the Enterprise Blockchain Platform have some cool super hard way of protecting the data in the Enterprise Blockchain Wallet ?

Well yes it does, this is the magic of Enterprise Blockchain Database 'Off-Chain' storage in the Enterprise Blockchain Wallet. This is so unique to Blockchain Technologies.

What happens is this, when store data in the Enterprise Blockchain Wallet, the Enterprise Blockchain Platform software runs a hash algorithm over the data that we have stored and the data, and the large file gets hashed:

The data or the file in the Enterprise Blockchain Wallet gets hashed, and then, that hash is stored in the Enterprise Blockchain Database.

This means we now have a unique hash of that data or file, and if anybody or anything makes even the tiniest teeniest change to that data or file, next time we run a hash over that data or file the result will be different that the original hash which is safely stored in the Enterprise Blockchain Database and this is how we will know that the data has been changed and we cannot trust the Data and therefore we cannot use it for our Enterprise IoT Data processing and Insights..

On the other hand, if just before we load the data in to the SAP Enterprise Applications, eg SAP Asset Performance Management and SAP S/4HANA, from the Enterprise Blockchain Wallet, if we run a hash over the data and the hash result is the same as we have in the Enterprise Blockchain Database, then we will know we can trust the Data and we can use it in our SAP Applications and we will have trustable IoT Data.

Enterprise Blockchain Wallet Data Hashes Stored in the Enterprise Blockchain Database - atkrypto.io

And this is why, for all of these reasons,

Trustable Enterprise IoT Data depends on Data being stored in the Enterprise Blockchain

But that's not the end of the Why IoT Data needs Enterprise Blockchain.

As we showed at the beginning of the blog in this picture:

IoT Internet of Things Edge Data Cyber Security and SAP Asset Performance Management BTP Protected by Enterprise Blockchain - atkrypto.io

As the picture shows, we have an Enterprise Blockchain Database Tenant installed on a Server Host at the Edge of the Network AND we have an Enterprise Blockchain Data Tenant installed on the SAP BTP Kyma Runtime.

The consequence of this is that we have a distributed Enterprise Blockchain Database table which stretches from the Edge of the Network where the IoT Devices are all the way across the Network to the SAP BTP and DataCenter.

This means we have Enterprise Blockchain Data Protection from the source where the IoT Devices are to the Insights and Business Processes where the SAP Applications are.

We have taken the Enterprise Blockchain to the Data at the source at the IoT Devices instead of taking the IoT Device's Data across all of the Networks to the safety of the SAP BTP and DataCenter. This is because we need to store the Data in the Enterprise Blockchain as close as possible to the source of the Data. The closer the Enterprise Blockchain Tenant is to the source of the Data, the safer the Data will be, it's as simple as that. Enterprise Blockchain is the next generation Cyber Security for IoT Data, and we need to minimise the amount of exposure IoT Data has to previous generation security technologies and approaches.

And this is why we say, Enterprise Blockchain is a Secure Communication Channel, because instead of integrating Applications sending and replicating Data across Networks, we are sharing the Data across the Enterprise Blockchain and the Enterprise Blockchain is the Secure Communication Channel.

IoT Internet of Things and SAP - Enterprise Blockchain is the next generation Data Cyber Security Protection - atkrypto.io

To conclude this section, the Why to, of IoT and Enterprise Blockchain, IoT Data needs to Trustable.

Enterprise Blockchain, due to its native super strong security strength when used as a store of Data enables IoT Data to be Trustable, and the Enterprise Blockchain Software needs be installed as close as possible to the source of the IoT Data, as close as possible to the IoT Devices.

Section 3.0: The How is it, of IoT & SAP, and Enterprise Blockchain

Now that we know why trustable Enterprise IoT needs the Enterprise Blockchain Database to protect the integrity and originality of the Data, how do we implement it today ?

Well that's easy, here are the ingredients and the recipe...

Ingredients, you're going to need:

Data Source(s) eg

IoT Devices which are either REST or MQTT (this could be other protocols and transfer mechanisms depending upon the required Adapters)

SAP and IoT IoT Devices sending Data to MQTT Broker in the Edge Host Instance of the Enterprise Blockchain Platform Database Tenant - atkrypto.io

SAP and IoT IoT Devices sending Data to REST Endpoint in the Edge Host Instance of the Enterprise Blockchain Platform Database Tenant - atkrypto.io

Large Storage for Large Data and the Enterprise Blockchain Wallet

SAP HANA Cloud (Data Lake)

Enterprise Blockchain Platform and specifically one which is capable of running Tenants as close to the Source of the IoT Data as possible at the Edge. We do NOT want to send the IoT Data across the Internet to a Blockchain somewhere in the Cloud, that would defeat the object of the exercise.

These are the basic ingredients, the data from the IoT Devices will be stored either Off-Chain in the SAP HANA Cloud (Data Lake) which will also be the Enterprise Blockchain Platform (configurable) Wallet, or On-Chain in the Enterprise Blockchain Platform Database Ledgers, this Enterprise Blockchain Database Ledger will be running from the Edge to the SAP BTP and DataCenters and then SAP Applications like SAP Asset Performance Management and SAP S/4HANA will be able use the Data in Business Processes and Insights.

And your Technical Reference Architecture will look something like this:

IoT Internet of Things Edge Data Cyber Security and SAP Asset Performance Management BTP Protected by Enterprise Blockchain - atkrypto.io

And that's how you do it.

Wrapping up, conclusions:

. Trustable Enterprise IoT depends on Data being stored in the Enterprise Blockchain at the Edge and in the SAP BTP

Enterprise Blockchain is:

. The Digital Transformation of Information Security to Cyber Security

. The Next Generation Data Integrity, Originality, Confidentiality Protection

. Re-imagining Information Security

. Natively, out of the box, due to its special characteristics the strongest, hardest, most resilient Enterprise Database product

Enterprise Blockchain is both:

. a Secure Store

. a Secure Communication Channel

The configurable Enterprise Blockchain Wallet enables you to store Big Data 'Off-Chain' and the hashes of the IoT Data are stored safely and securely on the Enterprise Blockchain Database.

The good news is, as we discussed in the previous blog, this is no longer hype, we can do all of this today, and now, within the SAP Partner Edge Open EcoSystem there are enabling technology Blockchain Products designed and built by SAP Experts specifically for the needs of SAP Customers to make doing Blockchain and SAP easy, and so you can do SAP and Blockchain, today it's real and there's nothing stopping you.

So what are we waiting for ? Oh yeah, more use cases, ok, that will be the next blog.

What do you think, are the words IoT, Blockchain, Web3, Distributed Ledger Technology, starting to appear in your Company's visions and technology visions ? What use cases are you looking at ? Let's chat about it in the comments.

For now, over and out.

Andy Silvey.

Independent SAP Technical Architect and CEO of atkrypto.io

Author Bio:

Andy Silvey is a 25 years SAP Technology veteran [15 years SAP Basis and 10 years SAP Tech Arch including Tech, Integration, Security, Data from 3.1H to S/4HANA PCE on RISE and the BTP and everything in between, and former SCN Moderator and Mentor alumni].

Andy is also co-Founder of atkrypto inc, an startup whose ambition is to make Blockchain easy for Enterprise.

atkrypto.io's flagship product is the atkrypto Enterprise Blockchain Platform for SAP, and atkrypto.io is a SAP Partner Edge Open EcoSystem Partner.

The atkrypto Enterprise Blockchain Platform for SAP has been designed by SAP Independent Experts for the needs of SAP Customers and to be deployed on the SAP BTP Kyma Runtime Service and leverage native integration to SAP Products.

atkrypto Enterprise Blockchain Platform for SAP has a number of unique qualities, including being the only Blockchain software in the world which has a DataCenter version and a light mobile version which can run on Edge/IoT/Mobile devices and enables data to be written to the Blockchain at the Edge where that same Blockchain is running on a Server in the DataCenter, protecting the integrity and originality of data from the Edge to Insights. Taking Blockchain to the Data at the Edge instead of taking the Data to the Blockchain.

All of this makes atkrypto,io the DePIN Decentralised Physical Infrastructure Network solution for Enterprise.

atkrypto is one of the Next20 startups being featured at TM Forum's DTW Ignite in Copenhagen in June

If you will be at DTW24 come and talk to us about Cyber Security of SAP Data with Enterprise Blockchain.

Uncorking the Supply Chains: How AI-Embedded Cloud ERP Makes Your Wine Taste Better

2024-08-06T13:25:51.290000+02:00

From frost challenges in merging vineyards in Essex, UK, to the looming threats of atmospheric rivers in California, environmental unpredictability is reshaping the wine production landscape, forcing winemakers to not only be masters of fermentation but also adaptation.

As a result, forward-thinking vintners are embracing a high-tech revolution, integrating AI to cloud ERP systems into their operations. These advanced technologies can now influence acidity, sugar levels, and bitterness and perhaps reduce the likelihood of a headache.

Let’s uncork more insight around how AI and cloud ERP are more than just buzzwords as they represent the wine industry's resilience and fusion of tradition with cutting-edge technology.

Harnessing AI to Enhance Efficiency and Adaptability

The wine industry is facing significant challenges due to climate change, with production levels fluctuating dramatically. Last year, global wine production decreased by 9.6% compared to the year before due to adverse climatic events, including early frost, heavy rainfall, drought, and widespread fungal diseases:

Italy experienced a 23.2% decrease in production
Spain saw a 20.8% decline
Australia's production fell by 26.2%
South Africa's production decreased by 10%
Greece faced a significant 34.4% reduction due to heavy spring rainfall causing downy mildew, followed by elevated temperatures and drought

Weather conditions significantly impact the quality and flavor profile of wine worldwide. Warmer temperatures are leading to earlier bud bursts, making vines more susceptible to spring frosts. Changes in ripening patterns are affecting the balance of sugar, acid, and secondary compounds in grapes, leading to wines with higher alcohol content and lower acidity, resulting in wines that taste flabby or lack freshness.

All facets of wine production must be carefully controlled to create quality wine. Such variables as temperature, weather changes, timing, fermentation, sugar, and acidity levels have a tremendous impact on the finished wine.

Exploring the Impact of Supply Chain Innovations on Sustainability

AI-embedded cloud ERP systems empower various industries to not just survive but thrive in the face of unexpected challenges. According to the recent IDC Infographic, 50% of organizations run their operations digitally, underpinned by an AI-powered cloud ERP system that supports digitally transformed operations and supply chains. Having end-to-end visibility is helping wineries and distributors navigate the complex journey from vineyard to glass with unprecedented precision and adaptability.

Predictive analytics and machine learning (ML) algorithms for climate adaptation enable winemakers to anticipate future trends and take proactive measures to mitigate the impacts of climate change, such as adjusting planting schedules or implementing protective measures against extreme weather events.

Real-time monitoring and automating responses to protect crops based on real-time data on critical factors like soil moisture, temperature, and wine health. For example, during unexpected frost events, these systems can automatically trigger protective measures like wind machines or heaters, preserving grape quality and preventing crop loss.

Optimizing harvest timing based on historical data and grape maturity enables winemakers to determine the optimal harvest time, ensuring grapes are picked at their peak for maximum flavor and balance.

Monitoring fermentation conditions and automatically adjusting parameters like temperature ensures a consistent and controlled process in real time.

Quality control with real-time tracking of grape parameters during harvest alerts winemakers to any deviations from desired quality metrics; which enables them to quick decisions on sorting and processing based on the grape quality. They also blend across vintages to achieve consistency in flavor profiles, balance out variations between years, or create unique and complex wines.

Traceability enables tracking of which vineyard blocks are harvested and when. So they can link harvested grapes to specific batches of wine for quality control and compliance purposes.

These systems also help create efficient harvest schedules, coordinate transportation, and manage grape flow into the winery. By leveraging these capabilities and technology-driven approaches, winemakers can achieve more precise decision-making, potentially improving wine quality and resource efficiency during critical periods.

Discovering the sustainable revolution in every drop with AI Embedded ERP

Having end-to-end visibility into the entire supply chain enables producers to track their environmental impact at every stage. With the usage of green ledger, wineries can track their carbon emissions throughout the supply chain. This helps them to identify areas for improvement and implement greener practices, from reducing water usage in vineyards or procurement processes to optimizing transportation routes for lower emissions.

By implementing AI-embedded cloud ERP solutions, organizations can achieve a 23% improvement in sustainability practices.

Inventory management also takes on a green hue with AI-embedded cloud ERP. It helps producers to minimize waste by accurately predicting the demand and optimizing stock levels. This not only reduces the carbon footprint associated with overproduction but also ensures resources are used efficiently.

In the face of climate challenges and disruptions that can occur at any time, you cannot have a supply chAIn without AI. Leveraging AI-embedded cloud ERP within supply chains, industries are not just producing great products, but they are cultivating a sustainable future.

Discover how cutting-edge technologies like AI-embedded cloud ERP can supercharge your business. Download the infographic: “Powering Operations with AI-Embedded Cloud ERP”

Utilization of SAP Integration suite to incorporate satellite IOT data into SAP Systems.

2025-06-24T10:04:36.856000+02:00

Hi All,

We can be able to integrate SAP Integration suite with the satellite IoT Data Providers which is an innovative as well as an emerging concept that has vast applications in logistics, defense and agriculture. It involves capturing of the data from satellites which includes geolocation, weather and asset movement while integrating it into the SAP systems like S/4 Hana, EWM and TM via SAP Integration Suite.

USECASE:

Imagining a logistics company with the fleets operating in some remote areas where GSM/4G signals are not available. Now, satellite IoT devices are often installed on the devices that could send telemetry data like location, temperature via satellite to a cloud provider or ground station. SAP Integration suite can then
ingest, process and roue this data into the SAP backend systems.

Architecture Overview:

Technical Flow:

i-Flow Design Steps in SAP Integration Suite:

Sender: HTTP Receiver from cloud IoT platform with the JSON payload.
Content Modifier: Extracting GPS, temperature as well as timestamp
Router: For applying the conditional logic.
Mapping: Conversion of the data type formats which can include JSON-> XML or it can be JSON-> SAP OData Format.
Receiver: Pushes data into SAP backend using HTTP or OData destination.

TESTING:

We can simulate IoT platform using tools like Postman.

Conclusion:

This integration would open doors to the smarter asset tracking as well as real-time decision making areas where GSM (Global System for Mobile Communication) is not available. Hence, SAP Integration Suite makes it possible to diminish the gap between remote IoT data as well as the enterprise systems.

Gagan Mohan Singh

2025-07-15T13:45:02.432000+02:00

Gagan

New Delhi, India

SAP Mentor since 2025
Follow Gagan on LinkedIn

Gagan is a seasoned SAP ERP Cloud architect, business relationship manager, presales strategist and an SAP storyteller with 18+ years of hands-on delivery and quota-carrying sales experience.

Gagan started his career at IBM where he cut his SAP teeth inside the Global Business Services unit, rolling out ECC for CPG and pharma clients across India. He also rolled out several Continuous Improvement and Key Control Initiatives for PepsiCo, modernised omnichannel retail at Page Industries (Jockey & Speedo), bootstrapped an online FMCG retail start-up, worked on Presales and Program Management at NEC Corporation India and is now responsible for SAP S/4HANA (RISE and GROW)sales and Program Management at Deloitte India. He loves talking about RISE/GROW programmes in SAP and translates deep technical detail into vivid business narratives for his 65,000+ SAP related LinkedIn followers.

Topics of interest: S/4HANA │ RISE with SAP │ GROW WITH SAP │ SAP BTP Extension & Integration │ SAP Signavio │Omnichannel Retail & CPG │ Presales Craft & Storytelling │ IOT │ AI

Gagan, what inspired you to become an SAP Mentor?

I’ve always loved sharing what I learn, and giving constructive feedback, so the SAP Mentor program felt like the perfect way to scale that habit. It offers a direct, two-way channel with SAP product managers and leadership—meaning the lessons I pick up in real projects can tangibly shape future releases—and it surrounds me with a community that’s just as passionate about raising the bar.

As someone who geeks out over the whole SAP portfolio—especially S/4HANA, RISE with SAP, and Signavio—I’m thrilled by the prospect of getting an early window into the new products and changes SAP is bringing to market. That behind-the-scenes insight, coupled with the chance to funnel field feedback right back to the engineers, is the part I love most.

What advice would like to share with other SAP community members?

Give back—consistently and generously. Whether it's by participating in events, answering questions, or sharing your own learnings, every contribution strengthens the SAP ecosystem. It’s not just a way to show appreciation for what the community has given you—it’s a way to multiply value for everyone.

Make contribution a habit. Whether you're posting on SAP Blogs, writing on LinkedIn, or speaking at an Inside Track, regular engagement helps you enjoy your own work more, navigate challenges better, and build meaningful connections across the globe.

And always remember:

Amplify others. Celebrate their wins, share their work—it grows your network and theirs. Ultimately we win together.
Share the full story. Don’t just post highlights; detail it out, your lessons from failures are often what help others most.
Stay curious. Make time to explore new SAP tools and innovations—this industry rewards those who keep learning.

Consuming the Free Open-Meteo Weather API Using ABAP – A Practical, Reusable OOP Approach

2025-11-22T06:44:27.499000+01:00

In many SAP teams, external API integration is still considered complex or “something middleware should handle”. But in reality, modern ABAP makes this easier than ever — especially when we take a clean OOP approach.

To demonstrate this, I built a simple, real-world example using the Open-Meteo weather API.
It’s absolutely free, requires no authentication, and returns clean JSON.

Example call:

Free Open-Meteo Weather API

This makes it a perfect learning API for ABAP developers who want to practice:

HTTP calls
JSON parsing
OOP design patterns
Storing data into SAP tables
Clean, reusable architecture

In this article, I walk through the exact steps to build a production-friendly ABAP solution that reads weather data and stores it in a Z-table — using patterns that you can apply for ANY external REST API.

1. Business Use Case

You want to collect weather snapshots for specific locations, such as:

Seaport / airport operations
Logistics planning
Production environment monitoring
Shift planning during heavy rain conditions
Agricultural or outdoor operations

The Open-Meteo API provides:

Temperature
Windspeed
Wind direction
Weather code
Day/Night indicator
Timestamp

Our goal:

✔ Call Open-Meteo
✔ Parse JSON
✔ Map data into an ABAP structure
✔ Save a snapshot in a Z-table
✔ Use clean OOP architecture

2. Create Z-Table to Store Weather Data

Table: ZWEATHER_SNAP

Suggested fields:

Field Description

LOCATION_ID	Logical location name
OBS_DATE	Date from API
OBS_TIME	Time from API
LATITUDE / LONGITUDE	Coordinates
TEMP_C	Temperature
WINDSPEED	km/h
WINDDIR	wind direction (degrees)
WEATHERCODE	API weather code
IS_DAY	X / blank
CREATED_ON / CREATED_AT / CREATED_BY	Technical audit

Sample DDL:

@EndUserText.label: 'Weather snapshot from Open-Meteo'
define table zweather_snap {
  key mandt        : abap.clnt;
  key location_id  : abap.char(20);
  key obs_date     : abap.dats;
  key obs_time     : abap.tims;

  latitude         : abap.dec(8,5);
  longitude        : abap.dec(8,5);
  timezone         : abap.char(40);
  temp_c           : abap.dec(5,2);
  windspeed        : abap.dec(5,2);
  winddir          : abap.dec(5,1);
  weathercode      : abap.int4;
  is_day           : abap.char(1);

  created_on       : abap.dats;
  created_at       : abap.tims;
  created_by       : abap.uname;
}

3. Define ABAP Types for JSON Mapping

TYPES: BEGIN OF ty_current_weather,
         temperature   TYPE decfloat16,
         windspeed     TYPE decfloat16,
         winddirection TYPE decfloat16,
         weathercode   TYPE i,
         is_day        TYPE abap_bool,
         time          TYPE string,
       END OF ty_current_weather.

TYPES: BEGIN OF ty_api_response,
         latitude               TYPE decfloat16,
         longitude              TYPE decfloat16,
         timezone               TYPE string,
         current_weather        TYPE ty_current_weather,
       END OF ty_api_response.

TYPES: BEGIN OF ty_weather_snapshot,
         location_id TYPE zweather_snap-location_id,
         obs_date    TYPE dats,
         obs_time    TYPE tims,
         latitude    TYPE zweather_snap-latitude,
         longitude   TYPE zweather_snap-longitude,
         timezone    TYPE zweather_snap-timezone,
         temp_c      TYPE zweather_snap-temp_c,
         windspeed   TYPE zweather_snap-windspeed,
         winddir     TYPE zweather_snap-winddir,
         weathercode TYPE zweather_snap-weathercode,
         is_day      TYPE zweather_snap-is_day,
       END OF ty_weather_snapshot.

4. Provider Interface (Strategy Pattern)

INTERFACE zif_weather_provider PUBLIC.
  METHODS get_current_weather
    IMPORTING
      iv_latitude  TYPE decfloat16
      iv_longitude TYPE decfloat16
      iv_location  TYPE zweather_snap-location_id
    RETURNING VALUE(rs_weather) TYPE ty_weather_snapshot
    RAISING cx_root.
ENDINTERFACE.

This makes the design future-proof:
Tomorrow you can add other weather providers or internal REST services.

5. HTTP Authentication Helper (For Future APIs)

Open-Meteo does not require auth — but real APIs usually do.
This helper makes your next extension very easy.

CLASS zcl_http_auth_helper DEFINITION PUBLIC FINAL CREATE PRIVATE.
  PUBLIC SECTION.
    CLASS-METHODS set_basic_auth
      IMPORTING io_http_client TYPE REF TO if_http_client
                iv_username TYPE string
                iv_password TYPE string.

    CLASS-METHODS set_bearer_auth
      IMPORTING io_http_client TYPE REF TO if_http_client
                iv_token TYPE string.
ENDCLASS.

6. Provider Class — Calling Open-Meteo

CLASS zcl_weather_open_meteo DEFINITION
  PUBLIC FINAL CREATE PUBLIC.

  PUBLIC SECTION.
    INTERFACES zif_weather_provider.

  PRIVATE SECTION.
    CONSTANTS gc_base TYPE string VALUE
      'https://api.open-meteo.com/v1/forecast'.

    METHODS build_url
      IMPORTING iv_latitude  TYPE decfloat16
                iv_longitude TYPE decfloat16
      RETURNING VALUE(rv_url) TYPE string.

    METHODS map_api_to_snapshot
      IMPORTING is_api TYPE ty_api_response
                iv_location TYPE zweather_snap-location_id
      RETURNING VALUE(rs_snap) TYPE ty_weather_snapshot.
ENDCLASS.

Provider Implementation

CLASS zcl_weather_open_meteo IMPLEMENTATION.

  METHOD zif_weather_provider~get_current_weather.
    DATA lo_http TYPE REF TO if_http_client.
    DATA lv_url TYPE string.
    DATA lv_json TYPE string.
    DATA ls_api TYPE ty_api_response.

    lv_url = build_url( iv_latitude = iv_latitude
                        iv_longitude = iv_longitude ).

    cl_http_client=>create_by_url(
      EXPORTING url = lv_url
      IMPORTING client = lo_http ).

    lo_http->request->set_method( 'GET' ).

    lo_http->send( ).
    lo_http->receive( ).

    lv_json = lo_http->response->get_cdata( ).

    /ui2/cl_json=>deserialize(
      EXPORTING json = lv_json
      CHANGING  data = ls_api ).

    rs_weather = map_api_to_snapshot(
                    is_api = ls_api
                    iv_location = iv_location ).
  ENDMETHOD.


  METHOD build_url.
    rv_url = |{ gc_base }?latitude={ iv_latitude }| &&
             |&longitude={ iv_longitude }| &&
             |&current_weather=true|.
  ENDMETHOD.


  METHOD map_api_to_snapshot.
    DATA lv_date TYPE string.
    DATA lv_time TYPE string.

    SPLIT is_api-current_weather-time AT 'T'
      INTO lv_date lv_time.

    REPLACE ALL OCCURRENCES OF '-' IN lv_date WITH ''.
    REPLACE ALL OCCURRENCES OF ':' IN lv_time WITH ''.
    CONCATENATE lv_time '00' INTO lv_time.

    rs_snap-location_id = iv_location.
    rs_snap-latitude    = is_api-latitude.
    rs_snap-longitude   = is_api-longitude.
    rs_snap-timezone    = is_api-timezone.
    rs_snap-temp_c      = is_api-current_weather-temperature.
    rs_snap-windspeed   = is_api-current_weather-windspeed.
    rs_snap-winddir     = is_api-current_weather-winddirection.
    rs_snap-weathercode = is_api-current_weather-weathercode.
    rs_snap-is_day      = COND #( WHEN is_api-current_weather-is_day = abap_true THEN 'X' ELSE space ).

    rs_snap-obs_date = lv_date.
    rs_snap-obs_time = lv_time.
  ENDMETHOD.

ENDCLASS.

7. Repository Class — Save to DB

CLASS zcl_weather_repository DEFINITION
  PUBLIC FINAL CREATE PUBLIC.
  PUBLIC SECTION.
    METHODS save_snapshot
      IMPORTING is_snapshot TYPE ty_weather_snapshot.
ENDCLASS.

Implementation:

CLASS zcl_weather_repository IMPLEMENTATION.

  METHOD save_snapshot.
    DATA ls TYPE zweather_snap.
    MOVE-CORRESPONDING is_snapshot TO ls.

    ls-mandt      = sy-mandt.
    ls-created_on = sy-datum.
    ls-created_at = sy-uzeit.
    ls-created_by = sy-uname.

    INSERT zweather_snap FROM ls.
    IF sy-subrc <> 0.
      MODIFY zweather_snap FROM ls.
    ENDIF.
  ENDMETHOD.

ENDCLASS.

8. Application Service — Business Orchestration

CLASS zcl_weather_app_service DEFINITION
  PUBLIC FINAL CREATE PUBLIC.

  PUBLIC SECTION.
    METHODS constructor
      IMPORTING io_provider TYPE REF TO zif_weather_provider
                io_repo     TYPE REF TO zcl_weather_repository.

    METHODS collect_and_save
      IMPORTING iv_latitude TYPE decfloat16
                iv_longitude TYPE decfloat16
                iv_location TYPE zweather_snap-location_id.
ENDCLASS.

Implementation:

CLASS zcl_weather_app_service IMPLEMENTATION.

  METHOD constructor.
    me->io_provider = io_provider.
    me->io_repo = io_repo.
  ENDMETHOD.

  METHOD collect_and_save.
    DATA ls TYPE ty_weather_snapshot.

    ls = io_provider->get_current_weather(
      iv_latitude  = iv_latitude
      iv_longitude = iv_longitude
      iv_location  = iv_location ).

    io_repo->save_snapshot( ls ).
  ENDMETHOD.

ENDCLASS.

9. Executable Report

REPORT zweather_collector.

PARAMETERS:
  p_lat TYPE decfloat16 DEFAULT '6.9271' OBLIGATORY,
  p_lon TYPE decfloat16 DEFAULT '79.8612' OBLIGATORY,
  p_loc TYPE zweather_snap-location_id DEFAULT 'COLOMBO' OBLIGATORY.

DATA lo_service TYPE REF TO zcl_weather_app_service.

START-OF-SELECTION.

  lo_service = NEW zcl_weather_app_service(
                 io_provider = NEW zcl_weather_open_meteo( )
                 io_repo     = NEW zcl_weather_repository( ) ).

  TRY.
      lo_service->collect_and_save(
        iv_latitude  = p_lat
        iv_longitude = p_lon
        iv_location  = p_loc ).
      WRITE: / 'Weather snapshot saved for', p_loc.
    CATCH cx_root INTO DATA(lx).
      WRITE lx->get_text( ).
  ENDTRY.

10. Why This Pattern Is Better Than a One-Report Solution

✔ Clean separation of concerns

Provider → HTTP & JSON
Service → Business logic
Repository → DB operations

✔ Highly reusable

You can connect ANY API by creating a new provider.

✔ Future-proof for SAP BTP / ABAP Cloud

This layered design aligns with RAP & clean architecture.

✔ Easy to maintain

Each class is small and focuses on one task.

✔ Ready for automated jobs

You can run this via SM36 as a weather-collector batch job.

✔ Perfect teaching material

Developers learn clean OOP practices with a simple, real API.

11. Where You Can Extend This

Build a Fiori List Report to display weather history
Publish weather snapshots via an OData V4 service
Add multiple locations
Add token authentication for your next article
Add job scheduling every 30 minutes
Add charts using CDS Analytical Queries

12. Final Thoughts

This small Open-Meteo exercise demonstrates how modern ABAP can easily consume external REST APIs using clean OOP architecture.

More importantly, this pattern applies to any scenario:

IoT sensor readings
Machine temperature & vibration
Traffic or route optimization APIs
Currency exchange APIs
Cloud microservices
Internal REST systems

Once you build this pattern once, you can reuse it across your entire SAP landscape.

SAP Community - Internet of Things

IoT 3.0

Building an End-To-End Machine Learning Solution for Product Inspection Centered On SAP Kyma

Overview and Motivation

Scenario

Solution Architecture and Process

In Detail

ESP32-CAM

YOLOv4 Bottle Detector Model

Flask Web App

SAP Cloud Application Programming Model (CAP) and SAP HANA Cloud

SAP Analytics Cloud (SAC) and SAP Build Apps

Closing

Industry 4.0 and the Standard ISA-95: The Pathway to Revolutionizing the Energy Industry

Streamlining Sensor Data Integration: Enhancing Telematics with AWS and SAP Digital Vehicle Hub

Introduction:

Enabling Telematic Data Persistence into an AWS Timeseries Database:

Benefits:

Continuing Integration of Otonomo with Amazon Kinesis:

Benefits:

Enabling Persistence of Telematic Data Using SAP Digital Vehicle Hub Naming Conventions:

Benefits:

Displaying Sensor Data on SAP Digital Vehicle Hub's User Interface:

Benefits:

Technical Integration details:

How is Nordlaks Leveraging IoT Technology and Cloud Processing to Farm Salmon in a more Sustainable Way?

Events-2-Business Action Framework – Create Plant Maintenance Notification in SAP S/4 HANA

Our approach

Business Scenario

Challenges

The Case

Process steps

Sensor/IoT devices determine conditions

Ingest the data in an IoT platform (here Microsoft Azure IoT Central)

Activities in Event-2-Business Framework

Actions

Business Rules

Logging

Reference Architecture

Key Advantages of This Architecture

Scenario Setup and Deployment

About Author

Simplifying the IoT Puzzle with SAP Asset Performance Management and Cumulocity IoT

Events-2-Business Action Framework – Create Service Ticket in SAP CX

Business Scenario

Challenges

The Case

Process steps

Sensor/IoT devices determine conditions

Ingest the data in an IoT platform (here Microsoft Azure IoT Central)

Activities in Event-2-Business Framework

Actions

Business Rules

Logging

Reference Architecture

Key Advantages of This Architecture

Scenario Setup and Deployment

About Author

Events-2-Business Framework – Create Shopfloor Confirmation in SAP S/4 HANA

Our approach

Business Scenario

Challenges

The Case

Process steps

Sensor/IoT devices determine conditions

Ingest the data in an IoT platform (here Microsoft Azure IoT Central)

Activities in Event-2-Business Framework

Actions

Business Rules

Logging

Reference Architecture

Key Advantages of This Architecture

Scenario Setup and Deployment

About Author

Be Ready: Future-Proofing Asset Management in Your Organization

Supporting asset management’s role in strong supply chains

Enabling asset management in the moment and on the go

A brief look back in time

Expecting the unexpected with predictive analytics

AWS and SAP – Joint reference Architecture for IoT scenarios using Amazon Monitron

Ingest the data in an IoT platform
(here Microsoft Azure IoT Central)

Ingest the data in an IoT platform
(here Microsoft Azure IoT Central)

Ingest the data in an IoT platform
(here Microsoft Azure IoT Central)