Architecture

Dime.Scheduler is designed for integration. Its API and ability to post back planning data make it easy to plug in any system of interest. The following components are vital to the operation.

The workflow is the same as any of the standard connectors that Dime Software provides out of the box:

Obviously, the new aspect here is to extend your ERP, CRM, or LoB system so it can send data to Dime.Scheduler and be able to receive and process incoming planning data.

The simplified data model below visualizes the important components to get data in and out of Dime.Scheduler. Besides the transactional data, it is important to provide Source App and Source Type fields with all data that comes from your system.

If you want to write back the planning data generated in Dime.Scheduler, the system of choice must be able to receive incoming web service calls and have deployed code that can write back the planning data in the right tables.

Using the API, you can get all data in Dime.Scheduler. To get planning data produced in Dime.Scheduler back in your system, you could consider using the standard webhook connector. If this connector is deemed insufficient, get in touch with us to build a standard connector for the new system.