# IFS Cloud Integration Options: Projections, Connect, Events and a MES Example > Source: https://netray.co/erp-help/ifs-cloud-integration-options-projection-connect-mes-example > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer IFS Cloud offers four main integration routes. Projections expose data and actions as OData services for request and response, IFS Connect handles message-based and file-based exchange with transformation, business events push notifications out when data changes, and workflows orchestrate steps. For a MES, the common pattern is orders and BOMs out by projection or event, and confirmations and quantities back in through a projection or a message. ## Kind advanced ## System ifs ## Erp IFS Cloud ## Module Integration ## Query ifs cloud integration options ## Alternate Queries - ifs cloud integration process - ifs cloud for mes - ifs connect messages - ifs cloud odata integration ## Applies To IFS Cloud 21R1 and later, cloud or customer-hosted. Specific projection names and message formats must be checked in your release documentation. ## Steps ### How to choose and build an integration **Items:** - Define the data flows: what moves, which system owns it, how often and how fast it must arrive. - For request and response over HTTP, use a projection through OData with an IAM service client. - For asynchronous messages, files or partner formats, use IFS Connect with routing and transformation. - For near real-time outbound notifications, use a business event that triggers a message or call. - Plan error handling: retries, a dead-letter place, alerting and a way to replay failed messages. - Test with production-like volume in a non-production environment before cutover. ## Sections ### Choosing the route **Body:** Projections are the modern default for synchronous reads and writes, since the same layer feeds the web client and respects permission sets. IFS Connect is the better fit for queued, batch or legacy formats where you need transformation, routing and a message log. Use events to avoid polling, and use workflows when a step needs conditions or human input. Authentication for projection calls uses tokens from the IAM service. Our page on projection 401 errors covers the usual token problems. ### Worked example: MES integration **Body:** A typical manufacturing execution link works like this. When a shop order is released in IFS, an event or a scheduled projection read gives the MES the order, operations, routing and material list. The MES runs the job and reports back operation start and finish, good and scrap quantities and consumed material. Those confirmations go back through a projection call or a Connect message that posts them to the shop order. Keep IFS the owner of the order and cost, and the MES the owner of the execution. Decide up front how the MES handles an order changed in IFS after release, since that is where integrations usually break. **Code:** - GET https://IFS_HOST/main/ifsapplications/projection/v1/.svc/?$filter= Authorization: Bearer ### Operational concerns **Body:** Treat integrations as products: name an owner, monitor message queues, version the contracts and test after every service update. Idempotent writes matter, because a retry must not post a confirmation twice. Where data cannot leave your network, keep the integration layer and any AI or analytics beside IFS on the same private network and use read-only service clients for anything that only needs to look. ## Pitfalls - Polling a projection every few seconds when an event would do. - Using an administrator login instead of a dedicated service client. - Posting confirmations twice because retries are not idempotent. - Not defining what happens to released orders changed in IFS. - Skipping regression tests on integrations after service updates. ## Ai Angle For integrations, an on-prem assistant can read your message logs and projection responses to explain why a MES confirmation was rejected, or to compare the order in IFS with the order in the MES. Because it runs on your own hardware with a read-only service client, production data stays inside your network. It does not replace the integration layer; it helps people run it. ## Faq ### Should I use IFS Connect or projections? **Answer:** Use projections for synchronous request and response over HTTP. Use IFS Connect for message queues, files and formats that need transformation and logging. Many integrations use both. ### Can IFS Cloud push data out when something changes? **Answer:** Yes. Business events report changes and can trigger an action or message, which avoids constant polling by the external system. ### Which system should own the shop order in a MES integration? **Answer:** Normally the ERP owns the order, routing and cost, and the MES owns execution on the floor. Define clearly how changes and cancellations travel in each direction. ### Is the integration different on a customer-hosted installation? **Answer:** The mechanisms are the same, but network access, certificates, identity provider setup and who operates the middleware differ, so confirm each with whoever hosts your environment. ## Search terms ifs cloud integration, ifs cloud integration options, ifs connect, ifs cloud odata, ifs cloud mes integration, ifs cloud business events, ifs cloud projection, ifs cloud integration process --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json