Architecture

Dime.Scheduler is built to integrate. Its API and its ability to post planning data back to your system let you connect almost any ERP, CRM, or line-of-business application. This page walks through the components that make that integration work and the data flow between the two systems.

Your integration follows the same workflow as the standard connectors that Dime Software ships out of the box. Step through it below:

Your systemERP · CRM · LoB

connecting

Dime.SchedulerPlanning board

SetupStep 1 of 5

Connect the system

The back-office system links to a Dime.Scheduler instance through a connector - the integration layer that knows how to talk to both sides.

The work on your side is to extend your ERP, CRM, or LoB system so it can send data to Dime.Scheduler and receive and process the planning data that comes back.

The simplified data model below shows the components you need to get data in and out of Dime.Scheduler. Alongside the transactional data, always supply the Source App and Source Type fields with every record that originates in your system. Select an entity to see its key fields and how it connects to the rest of the model.

Click any box to highlight what it connects to and see its fields and API reference. The arrows show how data flows: a job groups tasks, a task is scheduled as an appointment, and an appointment is tied to a resource through an assignment.

For the full entity-relationship diagrams, including cardinality and every field, see the data model reference.

To write back the planning data that Dime.Scheduler generates, your system must be able to receive incoming web service calls and run code that writes the planning data into the correct tables.

The API gives you access to all data in Dime.Scheduler. To get planning data produced in Dime.Scheduler back into your system, consider the standard webhook connector. If that connector does not meet your needs, get in touch with us to build a standard connector for the new system.