Glossary

The core Dime.Scheduler vocabulary in one place. These terms are used consistently across the documentation.

Action URI: A dynamic link, populated with fields from a task, job or appointment, that opens an external system in one click.
Admin center: The page that lists every administration and settings screen with a search box, plus a strip of things needing attention such as failed transactions and license usage.
Agenda: A read-only calendar page for consulting the planning of one or more resources without opening the planning board. It can be shared by URL or embedded in another page.
Allocation: The planned hours of a resource per period. The project team tab draws it as a heatmap to show who is over-allocated and who is on the team but not planned at all.
API key: A credential that authenticates calls to the Dime.Scheduler API. The preferred way to integrate over the deprecated JWT flow.
Appointment: A task scheduled to a resource for a specific period - the scheduled instance you see on the planning board.
Appointment template: A set of extra fields added to the appointment card, scoped to source types, so planners can capture data beyond the defaults.
Assembly order: A Business Central document that says what to build. The assembly order solution schedules the resources that build it and keeps the order’s dates in sync.
Assignment: The link between an appointment and a resource. An appointment can carry several assignments when more than one resource works on it.
Back office: The ERP or business system Dime.Scheduler plans for - most often Microsoft Dynamics 365 Business Central. It owns the master data and remains authoritative over what it receives.
Baseline: The original plan frozen in the Gantt chart. Shown underneath the current bars, it is how a project manager sees how far the plan has drifted from what was agreed.
Bidirectional synchronization: Two-way data flow between Dime.Scheduler and a back-office system: work comes in, scheduling decisions go back out.
Budget entry: A record of budget consumed by a task over a range of days, kept in an append-only ledger. A correction is a new entry that cancels an earlier one, so the history stays auditable.
Calendar: A definition of when work can happen, for the whole tenant or for specific resources: business hours, weekends and holidays. Calendars shade non-working time on the planning board and skip it in Gantt durations.
Capacity: The amount of working time a resource has available in a given period, used to spot over- and under-planning.
Caption: The label shown for a field or entity in the interface, translatable per language. A tenant that calls jobs "projects" changes the caption, not the data model.
Category: A visual indicator (a color) applied to appointments to classify or label them.
Claim: The act of turning finished work sessions into a time entry for one task and one day. A claim can also be made directly without a session; only work sessions count, travel and waiting do not.
Closed project: A finished project. Its appointments are locked, its tasks leave the open tasks list, no time can be registered on it and its pages are read-only. A project closes by hand or when its status reaches a done lane, and Reopen undoes it.
Connector: An integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out.
Container: A grouping mechanism that bundles related tasks or appointments so planners can move and manage them together.
Crew: A resource that stands for a group of other resources. Dropping work on a crew fans the booking out to every member, which suits people who always work together.
Data-driven security: Restricting which records a user can see based on the data itself - for example a region or business unit - rather than on their role.
Department: A grouping of resources used to sort and group rows on the planning board and in the grids. As a group behavior in the crews view, a department cannot be booked; it exists for structure and reporting.
Dimension: A Business Central dimension. The connector can read a resource’s default dimensions as the source of its type, department, team or pin, and use dimensions as the source of filter groups and filter values.
Dock panel: The container every component sits in. Dock panels can be moved, resized, stacked as tabs and retitled, and the result is saved as part of the profile.
DS Setup: The connector’s setup page in the back office (DS Setup in NAV, DS Connector Setup in Business Central). It holds the same settings as the FastTrack wizard, plus actions to send data manually.
FastTrack solution: One module of the Business Central or NAV connector that makes a kind of record plannable, such as service orders or production routing. Each has its own enable switch in the FastTrack wizard.
FastTrack wizard: The setup wizard inside Business Central or NAV that connects it to Dime.Scheduler and switches on the modules to plan from. It writes the source app and creates the source types for each enabled module.
Field template: A rule that composes an appointment subject and body from job and task fields, so the text reads the way planners want.
Filter group: A configurable set of fields used to filter resources and tasks on the planning board.
Filter value: A single value inside a filter group, used as a qualification on a resource or a requirement on a task.
Free field: One of the unmapped fields on jobs, tasks and appointments that a back office can fill with its own data, each with a localizable caption.
Gantt chart: A timeline view for long-term project planning, showing tasks, durations, dependencies and milestones.
Geocoding: Converting an address into map coordinates so a job or resource can be placed on the map and used for routing.
GPS tracking: Live location tracking of mobile resources, shown on the map so planners can dispatch the nearest available person.
Health rule: One condition that can make a project At risk or Off track, such as overdue tasks or hours used against the budget. Each rule warns and turns critical from thresholds an administrator sets for the whole organization; the most severe rule that applies decides the verdict.
Home address: The address where a resource starts and ends the day. The map plots resources on it when live locations are hidden, and a round trip uses it as the fixed start and end.
Import endpoint: The /import API endpoint that accepts a batch of stored procedure calls, each named like mboc_upsertJob with its parameter names and values. It is the batch way to push jobs, tasks, resources and appointments in.
Importance: A fixed scale driven by the back office, shown as an exclamation mark or arrow at the start of the appointment bar. What it stands for (priority, urgency) is decided when the application is set up.
Indicator: Collective term for the visual signals - categories, time markers, pins, and tags - that identify and label appointments.
Job: A high-level container, comparable to a project, that bundles related tasks together with common information such as customer, billing, and address.
Job planning line: The Business Central record that books a resource on a project (job) task. Planning a project task in Dime.Scheduler creates or updates one.
Job queue: Business Central’s scheduler for background work. The connector relies on job queue entries to process the outbound queue and to synchronize master data without blocking users.
Layout: A saved arrangement of the planning board - visible resources, columns, and settings - that can be reused.
Localization: The settings page that translates captions, maps localized country names to ISO codes for geocoding, and sets date and decimal formatting per language.
Locked appointment: An appointment that cannot be moved or edited. The lock is set in the back office, not in Dime.Scheduler, and locked appointments are drawn with shaded stripes.
Machine center: A machine under a Business Central work center. Like work centers, machine centers become resources when production routing planning is enabled.
MCP server: The Model Context Protocol endpoint that exposes scheduling operations as tools to AI assistants. It is authenticated with API keys and translates tool calls into Dime.Scheduler API calls.
Mobile app: The companion app for field workers to see their schedule, update appointments and share GPS location from the field.
My Work: The signed-in person’s own page in the web app: their schedule, tasks, projects and time, scoped to the resource linked to their account by e-mail address.
Notification: A message from the back office attached to a task, an appointment or the whole tenant. The notifications component lists them, and a colored vertical bar on the appointment signals their severity.
Open task: A task that has not been scheduled yet. It waits in the open task list to be placed on the planning board.
Outbound queue: The Business Central table where records headed for Dime.Scheduler wait when asynchronous processing is on. A job queue entry dispatches them a few minutes later and retries failures.
Pane layout: The configuration of the fields and groups shown in the details component, maintained on the Pane Layouts settings page.
Pin: An indicator that lives on a task rather than an appointment and colors its marker on the map, typically by skill, vehicle type or region. It has no equivalent on the planning board.
Planned task: An appointment together with the resources assigned to it - the full picture of what will be done, by whom, and when.
Planning board: The main graphical scheduling surface where dispatchers drag tasks onto resources across a timeline.
Planning digest: A recurring e-mail with a PDF of the schedule for a group of resources, sent daily, weekly or monthly to a shared inbox or to each resource. Recipients need no account or license.
Planning quantity: The amount of work an appointment represents, by default its duration in hours. A conversion factor can express it in another unit, and the capacity view compares it against resource load.
Planning view: The main screen of Dime.Scheduler, where a profile lays out the components a planner works with. A new tenant has none until a profile is created or applied from a template.
Pool: A group resource for work where you know how many people you need but not yet who. Assigning a pool holds one slot against the pool itself, to be resolved to a named resource later.
Portfolio: The projects page that shows every project in flight as an overview, a list, tiles, a timeline or a Kanban board, with the health measures that say which project to open next.
Preview feature: A feature that ships behind a flag while it is refined with early feedback. Pages for such features carry a Preview banner, and the flags live in Application Setup under Preview.
Production order: A Business Central manufacturing order with routing lines. The production routing solution puts those lines on the planning board against work and machine centers while BC’s own rules still hold.
Profile: A saved snapshot of a user’s planning board configuration, including the chosen layout and view options.
Project: A job seen as a whole in project planning: a body of work with a budget, a team, dependencies and a deadline. Its tasks are still planned as ordinary appointments on the board.
Project health: The verdict a project gets from the organization’s health rules - On track, At risk or Off track - shown per area as schedule, budget and resources. The rules are set once for every project in application setup, so a project reads the same in the portfolio and on its own page.
Project team: The explicit list of resources on a project, maintained in its Team view with their skills and weekly workload. Membership is declared, not inferred from who has appointments.
Quick start wizard: The wizard that gives a new tenant a working setup by applying a ready-made profile template or a setup package, then walking through application setup, connectors and users.
Recommendation: A ranked suggestion of resources for a job, matched on skills, location and availability. Available through the API and through the MCP server’s recommendation tool.
Recurring appointment: An appointment that repeats on a schedule - weekly, monthly - that you manage as one series instead of re-creating it each time.
Requested dates: Start and end dates carried by a task that, when the global setting is on, overrule where the planner drops the appointment. Requested times do the same for the time of day only.
Resource: An entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board.
Resource event delta: The change set the Exchange connector received from a resource’s mailbox for one sync window. The Deltas page lists them so you can see what Exchange actually sent.
Resource group (Business Central): Business Central’s own grouping of resources. The connector can use it as the source of a resource’s type, department or team, and sends capacity for a whole group in one action.
Resource number: The identifier a resource carries in the back office. Time entries and other records are keyed on it, so a resource created by hand without one cannot have time registered.
Resource type: A logical grouping of resources, such as "excavator" or "consultant", used to organize and filter them on the planning board.
Round trip: A route that starts and ends at the resource’s home address, with the waypoints in between as the variable. It is created from the map for a resource and a day and can be committed back to the planning board.
Route: The path between a set of stops drawn on the map, with travel time and distance per leg. The route sequence grid lists the same stops as rows.
Route sequence: An ordered list of a resource's appointments for a day, optimized by location so travel between jobs is minimized.
Sales order: A Business Central sales document. The sales planning solution lets you schedule resources against its lines and keeps the dates on both sides in sync.
Sandbox: The separate Dime.Scheduler environment where upcoming features arrive before the production release. It has its own API host, sandbox.api.dimescheduler.com, so API clients target it explicitly.
Sensitivity: The Outlook sensitivity level of an event: Normal, Personal, Private or Confidential. Together with show as, it filters which Outlook events reach the planning board.
Service item line: A line on a Business Central service order for one item to service. The connector can send each line as its own task, and its repair status can drive the task’s category or time marker.
Service order: A Business Central service management document. The service order solution plans it as one task or as one task per service item line, and writes the assignment back as a resource allocation.
Service zone: A Business Central service management field on service orders and resources. The connector can turn it into a filter group and use it to set the default category or time marker of a task.
Setup package: A portable JSON5 file describing a tenant’s configuration: profiles, layouts, users and settings. Also called a configuration package; it is composed, exported and applied from the Configuration packages page.
Show as: The Outlook free/busy status of a calendar event: Free, Tentative, Busy, Out of office and so on. The Exchange settings pick which statuses are allowed back into the planning.
Skill: A qualification a resource holds and a task can require, typically modeled as a filter group. Skills drive resource filtering, the project team view and the solver’s choice of who can do what.
Solver: The optimizer that assigns and sequences a set of tasks across a set of resources automatically, weighing skills, travel time and availability. It is a licensed module and produces a proposal, not a change.
Solver run: One execution of the solver, listed on the solver runs page with its scores, status and the before-and-after of every appointment it touched. A run reaches the board only when a planner applies it.
Source app: An identifier Dime.Scheduler attaches to data so it can route a change back to the correct back-office system.
Source type: An identifier that, together with the source app, tells Dime.Scheduler which back-office table a record belongs to.
Staging table: The Dime.Scheduler Appointments table in Business Central where incoming appointments land first. Business Central processes rows from there, so a row can be received and still fail processing.
Status mapping: The link between one back-office status and a work state, keyed on back office and record type. Records with that status show in the lane, and dropping a card in the lane writes that status back.
Tag: A reusable label with an icon and a color that can be applied to tasks and appointments. Unlike a category, a record can carry several tags at once.
Task: A unit of work that belongs to a job. It appears in the open task list until it is scheduled to a resource.
Team: A second grouping axis for resources, independent of department, used to sort and group them. In the crews view, "crew / team" is the behavior where a booking fans out to every member.
Time entry: A claim of a resource's time on one task for one calendar day. This is the record that is submitted to the back office, where it becomes a time sheet line.
Time marker: A visual indicator on an appointment, separate from its category, used to flag a status or condition at a point in time.
Time session: An observation that a resource was working, travelling or waiting on a task between two moments. Sessions support a time entry and never reach the back office on their own.
Time sheet (Business Central): The Business Central record that registers hours per employee. Dime.Scheduler can fill it from the plan (planned time) or from released time entries (time registration); running both for the same work registers the hours twice.
Timesheets page: The page where a team lead reviews logged time across every resource at once: what was logged, what was tracked but never claimed, and what failed on its way to the back office.
Transaction: The recorded call Dime.Scheduler makes to a connected system when the planning changes. It counts as successful on an HTTP 200, which means the endpoint received it, not that the back office processed it.
Transaction error code: A stable code such as DSBC003 that a connector attaches to a failed transaction. Codes never change once issued, so one can be looked up on the transaction errors reference page of its connector.
Travel time: The time needed to get from one appointment to the next, calculated from their locations. The planning board can show it in front of each appointment and fold it into the schedule.
User action: A single protected capability, such as 'edit appointment', that a role can grant. The building block of role-based access control.
User group: A container that coalesces users so security, profiles and layouts can be managed and shared for the whole group at once.
User role: A named bundle of user actions assigned to users and user groups. Permissions flow through roles, never directly to a user.
User-generated content: Profiles, layouts and filters that a user created and shared. The user-generated content page lets an administrator transfer their ownership before the user is removed.
Waypoint: One stop on a route. Selecting pins on the map adds waypoints, and reordering or removing them recalculates the route.
Webhook: The generic connector that POSTs every appointment change as JSON to a URL you choose. It delivers the message and leaves interpretation to the receiving system.
Work center: A Business Central manufacturing capacity unit. The production routing solution creates resources from work centers instead of the Resource table.
Work state: A lane on the task or project Kanban board, defined by an administrator. Statuses arriving from the back office are mapped onto work states so the board speaks your organization’s vocabulary.
Workspace: The arrangement of components a user sees in the planning view. A profile saves it, and dock panels are how it is shaped.