Request

Response

    Sample integrations workflows

    With Fusion Operations API, it’s possible to integrate with other systems, such as Enterprise Resource Planning (ERP), Product Lifecycle Management (PLM), Accounting, Marketplaces, Machines, and Business Intelligence. In this section you can find some examples of possible integrations to have different entities synchronized between systems.

    Disclaimer: Note that the integrations and recommendations provided herein are suggestions based on common API use cases. Users are encouraged to validate their specific integration requirements and ensure compatibility with their systems. Thoroughly verify your integration to meet your needs and comply with all relevant standards and regulations. It is also recommended to approach the integration with a phased strategy, incorporating additional entities gradually over time to ensure a smooth integration, minimizing disruptions and optimizing functionality. Autodesk does not guarantee the suitability of the API for all possible integrations and use cases.

    ERP Integrations

    These integrations usually connect Production Orders, Production Records, Inventory and Products. They may also synchronize Sales and Purchase Orders.

    Production Orders

    When a Production Order is created on the ERP side, the Production Order data should be sent to Fusion Operations API using the Production Order creation endpoint. If the Production Order needs to be updated in Fusion Operations, the Production Order Edition endpoint must be used. When completing the Production Order in Fusion Operations that information can be sent back to the ERP by using the webhooks feature.

    Inventory

    When a product is received, shipped, consumed or produced in Fusion Operations, the new inventory quantity can be requested by the ERP by using the product’s inventory endpoint.

    Products

    When a new product or product version is created in the ERP, the Product data should be sent to Fusion Operations API using the Product creation endpoint. If the Product needs to be updated, the Product edition endpoint must be used. If only the Bill of Materials needs to be updated, the Update Product BoM endpoint must be used.

    Sales & Purchase Orders

    When a new Sales Order or Purchase Order is created in the ERP, the Sales Order or Purchase Order data should be sent to Fusion Operations API using the Sales Order creation endpoint or Purchase Order creation endpoint. If these need to be updated, the Sales Order edition endpoint or Purchase Order edition endpoint must be used. When closing the Sales Order or Purchase Order in Fusion Operations that information can be sent back to the ERP by using the webhooks feature.

    PLM Integrations

    These integrations usually synchronize Products, their Bill of Materials, and use Production Records data to trigger actions in the PLM.

    Products

    When a new product or product version is created in the PLM, the Product data should be sent to Fusion Operations API using the Product creation endpoint. If the Product is updated in the PLM, the Product edition endpoint may be used to update the data in Fusion Operations.

    Production Records creating Non-Conformity / Problem Reports

    When a production record containing waste is created in Fusion Operations, the webhooks feature may be used to trigger the non-conformity record in the PLM. The production records get by id endpoint can be used to get content of the production record. The answer contains waste will have the waste information. The waste code or its quantity may be used to decide what is triggered in the PLM (non-conformity or a problem report).

    Accounting Integrations

    These integrations usually connect Sales Orders, Shipping Inventory Movements, Purchase Orders, Receiving Inventory Movements, Inventory and Products.

    Sales Orders

    When a new Sales Order is created in the accounting system, the Sales Order data should be sent to Fusion Operations API using the Sales Order creation endpoint. If these need to be updated, the Sales Order edition endpoint must be used. When closing the Sales Order in Fusion Operations that information can be sent back to the accounting system by using the webhooks feature. This trigger may be used to create an invoice on the accounting system.

    Purchase Orders

    When a new Purchase Order is created in the ERP, the Purchase Order data should be sent to Fusion Operations API using the Purchase Order creation endpoint. If these need to be updated, the Purchase Order edition endpoint must be used. When closing the Purchase Order in Fusion Operations that information can be sent back to the accounting system by using the webhooks feature. This trigger may be used to create a bill on the accounting system.

    Receiving Inventory Movements

    Every time a product on a Purchase Order is received, that information can be sent back to the accounting system to update the receiving status and create a bill by using the receiving_inventory_movement_created.

    Products

    When a new Product is created in the accounting system, the Product data should be sent to Fusion Operations API using the Product creation endpoint. If the Product needs to be updated, the Product edition endpoint must be used.

    Marketplaces/E-commerce Integrations

    These integrations usually connect Sales Orders, Shipping Movements, Inventory and Products.

    Sales Orders

    When a new Sales Order is created in the marketplace, the Sales Order data should be sent to Fusion Operations API using the Sales Order creation endpoint. If these need to be updated, the Sales Order edition endpoint must be used. When closing the Sales Order in Fusion Operations that information can be sent back to the marketplace by using the webhooks feature.

    Shipping Inventory Movements

    When one of the products of a Sales Order is shipped, that information can be sent back to the marketplace to update the shipping status by using the shipping_inventory_movement_created. This trigger can also be used to create shipping labels in external systems.

    Products

    When a new Product is created in the accounting system, the Product data should be sent to Fusion Operations API using the Product creation endpoint. If the Product needs to be updated, the Product edition endpoint must be used.

    Machine Connectivity Integrations

    These integrations usually synchronize Machines and their status over time (stopped, producing, or available)

    Machine stopped/available

    When a machine is stopped, that information can be sent to Fusion Operations by using the Machines Update Downtime endpoint. This endpoint will create a downtime record associated to the machine. The same endpoint can be used to indicate the machine is available again (meaning that the downtime has ended), ending the downtime record associated to the machine.

    Machine producing/available

    When a machine starts production, that information can be sent to Fusion Operations by using the Production Records Creation endpoint. When the machine ends production, that information can be sent to Fusion Operations by using the Production Records Edition endpoint (the Production Record attribute “finished” must be set to “true”).

    Machine producing/stopped

    A machine can have both an open Production Record and Downtime Record at the same time. In that case the machine will be marked as stopped, since the machine stopped status overrides the machine producing status.

    Business Intelligence (BI)

    These integrations usually pull production records and production orders data from Fusion Operations. It’s possible to see a more detailed analysis on how to build an integration with Power BI Desktop in this. article.

    Production Records

    Production Records data can be pulled from Fusion Operations using the Production Records List endpoint.

    Production Orders

    Production Orders data can be pulled from Fusion Operations using the Production Orders List endpoint.