MB-240 key terms

A schedulable record for anyone or anything that can be assigned work: a technician, crew, equipment, facility, or account. It stores work hours, capacity, territory membership, and characteristics, and it is what a booking actually reserves.

A skill, certification, or attribute such as 'Licensed Electrician' or 'Forklift Certified' that is attached to resources and to requirements. Scheduling only matches a requirement with resources whose ratings meet the required characteristic.

A geographic or organizational area used to group resources, work orders, and warehouses. Territories filter the schedule board, help route work to resources in the right region, and can restrict which records users see.

A record that models a physical place inside a site, such as a building, floor, or room. Functional locations form a hierarchy, and customer assets can be installed at one so technicians know exactly where equipment sits.

A record defining a state a booking can be in, such as Scheduled, Traveling, In Progress, Completed, or Canceled, along with its color on the schedule board. Booking statuses control which actions are available and whether time counts as work.

A reusable template of service tasks, products, and services describing a common job, such as replacing a compressor. Adding an incident type to a work order automatically creates the matching work order incidents, tasks, and line items.

A definition of a repeatable step of work with a name, estimated duration, and optional required resources or characteristics. When used on a work order it is copied into a work order service task that technicians complete in the mobile app.

A record grouping product and service prices for a context such as a region, customer, or agreement. Work orders and agreements reference a price list to calculate the amount charged for the products and services they contain.

A classification such as Inspection, Repair, or Installation that supplies defaults to new work orders, including incident types, priority, service territory, and price list, so dispatchers enter less data and reporting stays consistent.

The core record for a job performed at a customer location. It holds the account, customer asset, incident type, service tasks, products, services, time window, and status, moving from creation through scheduling and completion to billing review.

A line created on a work order when an incident type is added. It groups the service tasks, products, and services belonging to that specific job, letting technicians track and complete one part of a multi-part work order separately.

A checklist-style step on a work order, generated from a service task type or added manually. Technicians mark it complete in the mobile app, and it can carry instructions, estimated duration, and required resources or characteristics.

A record of equipment or property installed at a customer site, such as an HVAC unit, elevator, or medical device. Assets link to accounts and functional locations, carry warranty and service details, and accumulate history from completed work orders.

The accumulated record of work performed for an account or on a customer asset, generated when work orders are completed. It shows what was done, when, by whom, and which products were used, supporting troubleshooting and renewal conversations.

A record describing recurring service a customer has purchased, such as monthly preventive maintenance. Agreements generate work orders on a schedule, define covered customer assets, and supply a price list plus invoice and billing settings.

A line item on a work order for a part or material. Quantities are tracked as estimated, used, or returned, and recording usage in the mobile app consumes warehouse or truck inventory so stock figures stay accurate.

The dispatcher's primary workspace: a timeline of requirements, bookings, and resource availability. It supports drag-and-drop scheduling, map and list views, filters, and the scheduling assistant for finding and comparing candidate resources.

The shared scheduling engine used by Field Service, Project Operations, and other Dynamics 365 apps. It provides requirements, bookings, the schedule board, and optimization so that any table with schedulable records can be resourced.

A record describing what must be scheduled: duration, time window, required characteristics, territory, and preferences. Fulfilling it creates a booking, either manually on the schedule board or automatically through the scheduling assistant or optimization.

An add-in that automatically assigns requirements to the best resources using constraints, objectives, and weighted goals such as minimizing travel, cost, or overtime. It runs on a schedule or on demand and can re-optimize existing bookings.

The record that reserves a bookable resource's time for a requirement from a start to an end time. Bookings can be created manually, by the scheduling assistant, or by optimization, and each one carries a booking status.

A setting on a requirement that determines how scheduling assigns resources, such as a single booking, one booking per resource, or a crew, and whether follow-up work should go to the same resource.

A group of bookable resources scheduled together as one team, such as a two-person repair unit. Crews have their own capacity, characteristics, and work hours, and they can be booked directly to a requirement.

The model-driven Power Apps application technicians use on phones and tablets. It shows bookings, work orders, and assets; captures photos, signatures, and barcode scans; and keeps working offline when the device loses connectivity.

A configuration that defines which tables and records download to the Field Service mobile app for offline use, including sync filters and sync intervals. Without a suitable profile, technicians cannot work without connectivity.

A mobile feature that draws a virtual boundary around a work order's address and uses the device location to record arrival and departure automatically, producing more accurate travel and labor times.

An AI assistant in the Field Service mobile app that summarizes work orders, answers technician questions from organizational knowledge, and drafts updates, reducing time spent reading long notes or searching documentation.

A location that stores inventory, typically a depot, a service truck, or a technician's van. Warehouses are the source and destination for adjustments, transfers, and purchase order receipts, and they carry their own on-hand quantities.

The record of how much of a product is on hand in a specific warehouse. It is updated by receipts, transfers, adjustments, and consumption from work orders, and it drives what the mobile app shows as available stock.

A record that changes on-hand quantity in a warehouse outside of a purchase or transfer, for example correcting a count or writing off damaged stock. It requires a warehouse, product, unit, and positive or negative quantity.

A record that moves product quantity from one warehouse to another, generating matching outbound and inbound transactions. Transfers keep on-hand figures accurate when stock moves between a depot and a service truck.

A record ordering products from a vendor, with line items, quantities, and agreed prices. The order is received into a warehouse, which updates product inventory and lets the business track what was ordered against what arrived.

The step of recording products that physically arrived against a purchase order. Receiving updates warehouse on-hand quantities, records the quantity received per line, and can capture serial numbers and the receiving date.

A supplier record used on purchase orders. Vendors hold contact and address details and are linked to the products they supply, so buyers order from the right source and can report on purchasing spend.

The cloud data service that stores Field Service records such as work orders, bookings, and inventory. Tables, columns, relationships, and security roles defined in Dataverse are what Power Apps, Power Automate, and Dynamics 365 apps operate on.

Microsoft's low-code application platform. Field Service ships as a model-driven Power Apps app, and makers build canvas or model-driven apps that read and write Dataverse data to extend field operations.

Microsoft's workflow service for automating steps across apps and services. In Field Service it triggers on record events, such as a work order created or a booking changed, to send notifications, create records, or call external systems.

A container that packages customizations, including tables, apps, flows, and configurations, for transport between environments. Managed solutions are locked for deployment to test and production, while unmanaged solutions are edited in development.