Nexeed
    • Introduction
    • Operations manual
      • Overview
      • System Architecture and Interfaces
      • System Requirements
      • Migration from Previous Versions
      • Setup
        • Setup
        • Configuration
        • Nexeed Connectivity Configurator
      • Start and Shutdown
      • Regular Operations
      • Failure Handling
      • Backup and Restore
      • Logging and Monitoring
      • Known Limitations
    • Developer documentation
      • Getting started
    • Glossary
Direct Data Link
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Direct Data Link
  • Developer documentation

Developer documentation

OpCon XML is a standard for the exchange of data between production equipment and OpCon MES. The events specified in OpCon DirectDataLink are expressed as corresponding XML messages.

OpCon XML was developed in order to cover as broad a range of production equipment as possible. The elements defined here need not be supported to their fullest extent by all platforms. Simple clients (e.g. PLC) may only support the core of the specification, while other, more powerful clients (e.g. PC-based systems) implement the entire standard.

To be able to use OpCon XML in as broad a spectrum of applications as possible, the standard is divided into three parts:

  1. Core specification
    This part defines the portions which must absolutely be implemented by all clients. The definitions included in this part must always be observed.

  2. Extended elements
    This part includes the definitions which can be implemented by a client. The definitions here can be implemented depending on the capabilities of the client.
    If a client implements a definition, however, it must be implemented in its entirety. It is not permitted for a client to implement only parts of a definition.

  3. Area-specific elements
    Different production areas have different requirements for communications. The area-specific definitions can be stored in this part (e.g. specific definitions which are valued for the entire AE area).

This document contains Part 1 (core specification) and Part 2 (extended elements). Part 3 is described in one or more additional area-specific documents.

Examples

The examples in this documentation serve for the illustration of the respective definitions. They have no directly binding character. Particularly extended elements can be used in the examples to better work out different aspects of the definition. Therefore, it is possible that real-world applications can differ from the XML telegrams shown in the examples, provided that the applications do not violate any of the definitions described in this document.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses