{"id":1752,"date":"2025-12-29T15:59:35","date_gmt":"2025-12-29T10:29:35","guid":{"rendered":"https:\/\/blogs.infosys.com\/engineering-services\/?p=1752"},"modified":"2025-12-29T15:59:35","modified_gmt":"2025-12-29T10:29:35","slug":"building-efficient-shopfloor-connectivity-for-real-time-data-exchange-with-sap-digital-manufacturing","status":"publish","type":"post","link":"https:\/\/blogs.infosys.com\/engineering-services\/industrial-iot\/building-efficient-shopfloor-connectivity-for-real-time-data-exchange-with-sap-digital-manufacturing.html","title":{"rendered":"Building Efficient Shopfloor Connectivity for Real-Time Data Exchange with SAP Digital Manufacturing"},"content":{"rendered":"

SAP Digital Manufacturing (SAP DM)<\/strong>\u00a0is designed to enhance productivity by automating and streamlining your manufacturing processes. It ensures seamless integration of data and processes between your shop floor and business applications, enabling comprehensive workflows from planning to execution with physical devices.<\/p>\n

What\u2019s inside this blog:<\/strong><\/p>\n

\n
Setting Up Shop Floor Connectivity: Establish communication between tag-based OPC UA server and SAP DM.<\/li>\n
Using the Production Connector and Cloud Connector: Enable seamless data flow.<\/li>\n
Reading Tags from Devices: Configure a production process in SAP DM to read\/write tags from a device on your OPC UA server<\/li>\n<\/ol>\n
Introduction to Production Connectivity Model<\/strong><\/p>\n
\n
The Production Connectivity Model allows linking physical devices with various systems, including SAP systems, shop floor systems, and third-party systems.<\/li>\n
The Production Connector and the Cloud Connector work together to establish a secure, stable, and traceable data communication channel between shop floor systems and SAP DM using Transport Layer Security (TLS).<\/li>\n<\/ul>\n
$\"\"$ <\/p>\n
Production Connectivity<\/strong><\/p>\n
Physical devices\u2014such as machines, facilities, transportation, or other means that enable shop floor processes\u2014are represented as assets in SAP DM. These assets have static properties (attributes) and dynamic properties (indicators). This representation allows you to manage assets in SAP DM just as you would handle physical devices in the real world. With established shop floor connectivity, you can integrate and fully automate manufacturing operations using production processes.<\/p>\n
Prerequisites<\/strong><\/p>\n
Before connecting your shop floor to SAP DM, ensure the following:<\/p>\n
\n
Subaccount Membership: You must be a member of the subaccount where you have subscribed to SAP DM on the SAP Business Technology Platform (BTP).<\/li>\n
Service Key Creation: Create a service key for your SAP DM service instance. For more details, refer to Prepare for API Integration.<\/li>\n
Destination Creation: Set up a destination in the subaccount. For more details, refer to Create a Destination for System Communication and Integration.<\/li>\n
Production Connector Installation: To install the Production Connector, follow these steps. For detailed instructions, refer to Installation of the Production Connector.Prerequisites:
\nBefore installing Production Connector 2.2, ensure that the following two Microsoft .NET 8.0 runtimes are installed:<\/p>\n
.NET Desktop Runtime 8.0 (x86)
\nASP.NET Core Runtime 8.0 (x86)<\/p>\n
Note: The x86 versions are required because Production Connector applications run as 32-bit programs.<\/li>\n
Cloud Connector Installation: Install the Cloud Connector. For more details, refer to Installing the Cloud Connector.<\/li>\n
KEPServerEX Installation: Download and install KEPServerEX from the demo link. Do not run it yet to start the initial setup.<\/li>\n<\/ol>\n
Note:<\/strong> In this blog, we use KEPServerEX to set up an OPC UA server as an example. It is not recommended for production usage.<\/p>\n
$\"\"$ <\/p>\n
<\/p>\n
\n
Step 1 \u2013To start, configure the Production Connector, which serves as the central on-premise middleware enabling communication between the shop floor and SAP DM.<\/li>\n
Step 2 \u2013 To use the Production Connector with SAP DM, configure the Cloud Connector following the assisted Configuration of the Cloud Connector.<\/li>\n
Step 3 \u2013 Configure the OPC UA Server<\/li>\n
Step 4 \u2013 After configuring the Production Connector, Cloud Connector, and OPC UA server,\u00a0 onboard them in SAP DM to establish shop floor connectivity.<\/li>\n
Step 5 \u2013 Create and Connect an Asset. Now that OPC UA server is connected to SAP DM, create an asset in SAP DM representing the equipment you created in Step 3. The asset’s indicators will connect to the its tags.<\/li>\n
Step 6 \u2013 Read Asset Indicators Using a Production Process. The equipment on OPC UA server now has a digital twin on SAP DM. You can read its tags using the built-in Choose Quick Deploy > Deploy and Activate.<\/li>\n<\/ol>\n
$\"\"$ <\/p>\n
Demonstration of the setup by changing Tag Values and Running the Production Process:<\/strong><\/p>\n
1.Change Tag Values in the KEPServerEX Configuration app, choose Tools > Launch OPC Quick Client. In the OPC Quick Client dialog, select the equipment and tag and choose Tools > Item > Synchronous Write. In the Write Value field, enter the desired value and choose OK.<\/p>\n
$\"\"$ <\/p>\n
2. In production process in SAP DM, choose Run.<\/p>\n
$\"\"$ <\/p>\n
3. Open the Monitor Production Processes app and select the process instance just ran, to see its details.<\/p>\n
4. Select the step Read Indicators and choose Process Parameters View.<\/p>\n
5. The tag values are displayed under Output Parameters – Read Indicators.<\/p>\n
$\"\"$ <\/p>\n
The set up for Production Connector, Cloud Connector, and local OPC UA server is completed and onboarded them in SAP DM, enabling connection to devices on the shop floor using the asset model enabling efficient Shopfloor Connectivity for Real-Time Data Exchange.<\/p>\n","protected":false},"excerpt":{"rendered":"
SAP Digital Manufacturing (SAP DM)\u00a0is designed to enhance productivity by automating and streamlining your […]<\/p>\n","protected":false},"author":928,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[4,35],"tags":[52,149,150,151],"coauthors":[148],"class_list":["post-1752","post","type-post","status-publish","format-standard","hentry","category-industrial-iot","category-iot","tag-mes","tag-sapdigital","tag-sapdm","tag-sapmes"],"acf":[],"_links":{"self":[{"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/posts\/1752","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/users\/928"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/comments?post=1752"}],"version-history":[{"count":5,"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/posts\/1752\/revisions"}],"predecessor-version":[{"id":1852,"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/posts\/1752\/revisions\/1852"}],"wp:attachment":[{"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/media?parent=1752"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/categories?post=1752"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/tags?post=1752"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.infosys.com\/engineering-services\/wp-json\/wp\/v2\/coauthors?post=1752"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}