Orchestrate Overview

Owned by Megan Stanage
Aug 30, 2024
3 min read

Overview

Orchestrate strings together different segments of business logic into a coherent flow. 

The business logic currently includes:

The workflow below displays the segments in a specific sequence, but you can configure these features in any order necessary.

Similarly, the functions are independent; while they can work together, no piece is entirely reliant on another. This provides flexibility in implementation and design.

Orchestrate mimics the basic functionality of the D365 Order solution, but is built with an ERP-agnostic framework. 

Through our Swagger and API endpoints, users can submit requests from any ERP system. Additionally, if a client uses multiple ERP systems, each system can submit requests simultaneously.

The workflow below displays each function as its own object, as well as the outside data necessary to perform it.

Note

This is an example workflow. Segments can be reordered as necessary in the implementation.


Workflow


 Begin Execution

The workflow is initiated by the host system through either:

  • an API sending inventory to the On-Hand Inventory page
  • a JSON request for one of the many features


 Sourcing Engine

The Sourcing features within Orchestrate determine which warehouses to source an order from based on geography or other configured attributes.

Configuration Pages

Endpoints

  • Inventory API

  • Swagger


 Host Inventory Database

Inventory is maintained in SCC through the On-Hand Inventory page, but that endpoint must be updated through our API to remain as accurate as possible.

Host Inventory Database represents the ERP the client uses to track inventory real-time.

If multiple sources of inventory are present, they can be utilized, but will have separate API connections.

Configuration Pages

Endpoints

  • Inventory API


 Demand Priority Engine

Demand Priority allows clients to categorize and prioritize inventory allocation.

Users determine what characteristics or attributes define a segment of demand and the corresponding priority of that demand.

Additionally, allocation constraints, such as budgets and safety stock, are built into the endpoint to stabilize inventory where necessary.

Configuration Pages

Endpoints

  • Inventory API

  • Swagger


 Routing Consolidation Engine

Routing Consolidation allows you to consolidate demand lines according to a specific set of attributes.

These user-defined attributes are most often Customer, Purchase Order, and Mode of Delivery.

Configuration Pages

Endpoints

  • Swagger


 Suggested Carrier Engine

Suggested Carriers provides a suggested carrier based on the number of pallets or containers.

Configuration Pages

Endpoints

  • Swagger


 Estimated Palletization

Pallet Estimation offers a simple view of how many pallets can be generated for a set of demand lines.

Configuration Pages

Endpoints

  • Swagger


 Recommended Palletization

Coming Soon



FAQs

Q: Why is the Inventory endpoint API and not Swagger?

  • A: Inventory requires a separate API so that we can scale it according to a much higher expected volume relative to other endpoints.
  • A: The Inventory API runs on separate Azure infrastructure.

Q: Are any of the Orchestrate features extensible?

  • A: Orchestrate is not extensible. Any custom logic that cannot be handled within the configurations should be executed in the communication layer between Orchestrate and the host system.

Q: What are attributes and why are they part of every feature?

  • A: Attributes are user-defined characteristics that exist throughout Orchestrate and are primarily used to define demand.
  • A: Attributes are heavily utilized with most Orchestrate features as a method of matching desired demand to specific actions. For example, any demand with the attribute “Wholesale” is assigned to the wholesale demand channel and prioritized accordingly.


Feedback

Submit feedback.