> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/guides/system-connectivity/mes-erp-business-systems.md).

# MES, ERP & Business Systems

Integration guides for MES, ERP, and business platforms such as SAP, Microsoft Dynamics 365, and Ignition.

These guides describe how to exchange shop floor data with manufacturing execution systems (MES), enterprise resource planning (ERP) systems, and other business platforms. The following guides are available:

| Guide                                                                                                                              | Connector                                                                                                                          | Description                                                          |
| ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| [SAP Digital Manufacturing](/2-6-1/guides/system-connectivity/mes-erp-business-systems/sap-digital-manufacturing-integration.md)   | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md)                                                                  | Start production processes and log data collection values.           |
| [SAP S/4HANA](/2-6-1/guides/system-connectivity/mes-erp-business-systems/sap-s4hana-integration.md)                                | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md)                                                                  | Poll production orders and post confirmations over OData.            |
| [SAP MII](/2-6-1/guides/system-connectivity/mes-erp-business-systems/sap-mii-integration.md)                                       | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md)                                                                  | Run MII transactions and poll query templates.                       |
| [Microsoft Dynamics 365](/2-6-1/guides/system-connectivity/mes-erp-business-systems/microsoft-dynamics-365-integration.md)         | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md)                                                                  | Create and query Dataverse rows from shop floor data.                |
| [Oracle Fusion Cloud SCM](/2-6-1/guides/system-connectivity/mes-erp-business-systems/oracle-fusion-cloud-scm-integration.md)       | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md)                                                                  | Report operation and material transactions and poll work orders.     |
| [Odoo](/2-6-1/guides/system-connectivity/mes-erp-business-systems/odoo-integration.md)                                             | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md)                                                                  | Read manufacturing orders and log production events over JSON-RPC.   |
| [Tulip](/2-6-1/guides/system-connectivity/mes-erp-business-systems/tulip-integration.md)                                           | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md)                                                                  | Stream machine attributes and work with Tulip Tables.                |
| [Critical Manufacturing MES](/2-6-1/guides/system-connectivity/mes-erp-business-systems/critical-manufacturing-mes-integration.md) | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md)                                                                  | Post data collection results and poll MES business objects.          |
| [Ignition](/2-6-1/guides/system-connectivity/mes-erp-business-systems/ignition-integration.md)                                     | [MQTT](/2-6-1/connectors/enterprise-connectors/mqtt.md), [OPC UA](/2-6-1/connectors/shop-floor-connectors/opc-ua/opc-ua-client.md) | Publish Ignition tags via MQTT Transmission or read them via OPC UA. |
| [AVEVA PI System](/2-6-1/guides/system-connectivity/mes-erp-business-systems/aveva-pi-system-integration.md)                       | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md)                                                                  | Write and read PI Point values through the PI Web API.               |
| [Heisenware](/2-6-1/guides/system-connectivity/mes-erp-business-systems/heisenware-integration.md)                                 | [MQTT broker](/2-6-1/broker/cybusmq.md)                                                                                            | Feed low-code dashboards from Unified Namespace topics.              |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/guides/system-connectivity/mes-erp-business-systems.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.