Buyer Assessment

Dynamics 365 Field Service for Machinery OEMs and Distributors

The Microsoft Dynamics 365 Field Service module is built for enterprise service organisations. We evaluate how well it fits the requirements machinery OEMs and distributors have for after sales and field service software, and what it costs a 50 person service team.

Book a Demo Contact Sales

Cost

Dynamics 365 Field Service Pricing for a 50 Person Service Team

Four dispatchers, 38 field technicians, and 8 service coordinators who answer customer requests. Microsoft list prices, billed annually. Makula Field Service is €55 per user per month for every role.

Annual cost for 50 users, at published list prices

Line

Dynamics 365 Field Service

Makula Field Service

4 dispatchers

$5,040

Field Service, $105 per user, month

€2,640

€55 flat

38 field technicians

$47,880

Field Service, $105 per user, month. Team Members at $8 does not cover work orders, agreements, scheduling or dispatch.

€25,080

€55 flat

8 service coordinators

$12,000

Field Service plus Customer Service attach, $105 and $20, for case management and SLAs

€5,280

€55 flat, no second app

Licences

$64,920

€33,000

Schedule optimisation

$15,120

Resource Scheduling Optimization, $30 per resource. Optional, the schedule board is included.

Included

Customer portal

Quote required

Power Pages, licensed separately

Quote required

priced for your customer count, not per seat

Metered

Copilot Credits, pay as you go or prepaid

€10 to €30 per user

Implementation

Quote required

partner configuration and data migration

Quote required

Capability comparison

What Dynamics 365 Field Service Does out of the Box for Machine Service

We looked at the capabilities that matter to a machinery OEM or distributor, from keeping track of every asset and its service history, through issuing a customer portal, to performing field service on site.

Capability

Dynamics 365 Field Service

Built for enterprise service orgs

Makula Field Service

Built for OEMs

Installed Base and Assets

Complete list of you installed base

Customer Assets with parent and child hierarchy, plus functional locations

Emails sent and received, listed per asset

Custom

Customer Assets with parent and child hierarchy, plus functional locations

Complete service history per asset

Past and present work orders list against each asset

Bill of materials per asset

Limited

Asset hierarchy models components; a true bill of materials sits in Supply Chain Management

Preventive maintenance events per asset

Agreements generate recurring work orders and invoices

Meter readings saved against each asset

Custom

IoT telemetry via Connected Field Service; manual readings are a build

QR codes for customers and your own technicians

Help Desk

Help desk on a connected service email address

Add On

Customer Service Enterprise, from $20 attach on top of Field Service

Tickets saved in the context of the customer and the asset, building service history automatically

cases carry a Field Service tab linking to the asset and functional location

Personal mailboxes connected, so every customer conversation is captured

Add On

Customer Service Enterprise

Escalate a ticket straight into a work order

Work orders generate from cases as standard

Add On

AI copilot for troubleshooting in machine context

Copilot is integrated; agent capacity is metered as Copilot Credits

Add On

Service knowledge captured from calls and visits

Limited

Customer Portal

Portal showing customers their own machines, documents and parts lists

Add On

Power Pages shows assets, agreements, work orders and invoices; parts lists are a build

Portal service requests land in the service queue as a ticket, linked to the customer and the asset

The self scheduling portal creates a work order against the chosen asset

AI in the portal answers customer questions from the machine documentation

Custom

Add On

Customers request spare parts against their machine

QR code access from the machine, no login hunt

Distributors and service partners get their own access

Custom

Power Pages web roles, scoped by you

Distributors can reissue portals to their own end customers

Distributors and OEMs collaborate on solving end customer problems

Custom

Field Service

Scheduling and dispatch with capacity and skill levels

Schedule board included; automated optimisation is a $30 per resource add on

Offline mobile app with digital service forms

Work orders for on site visits, visualised on a kanban board

Work orders with attached procedures and signature capture

Inspection checks and structured checklists

Schedule board included; automated optimisation is a $30 per resource add on

Time tracking on the work order

Reports and analytics on service operations

Add On

Customers and assets shown on a map view

Quoting, Invoicing & Service Contracts

Manage service contracts

Agreements, with entitlements applied to work order pricing

Create quotes and invoices

Agreements generate invoices on a schedule

SLA response times tracked on every ticket

Add On

Entitlements and SLAs come with Customer Service Enterprise

IT & Coexistence

ERP and business system integration

Dual write to Business Central and Supply Chain Management

Open REST API and bulk data import

Hosted in Germany, ISO 27001:2022 certified

Limited

Azure regions in Germany are available; the company is US based

Fit & Effort

Designed for

Enterprise field service organisations

Machinery OEMs and distributors

Cost of stretching it to cover all five requirements

Strong on service execution; the customer and distributor half needs building

Weeks, standard configuration

IT involvement

An IT project. Partner led configuration on Power Platform, then an administrator to maintain it.

No IT involvement. Set up by a key user from the service team.

Typical implementation cost

$25,000 to $100,000 commonly cited, rising with data migration and integrations

Under €5,000

Frequently Asked Questions

What does Dynamics 365 Field Service cost for a machinery OEM?

The full user licence is $105 per user per month at list, billed annually. Contractors are $50, and Team Members at $8 does not cover work orders, agreements, scheduling or dispatch, so it is not an option for technicians. Coordinators who handle inbound cases and SLAs need Customer Service Enterprise as well, which attaches at $20 once Field Service is the base licence. For a 50 person team that comes to roughly $64,920 a year before the portal, schedule optimisation and implementation.

Can Dynamics 365 Field Service manage an installed base of machines?

Yes, and better than most. Customer Assets are a first class record with parent and child hierarchies, so a machine, its sub assemblies and its serialised components can be modelled properly. Functional locations add a separate hierarchy for where each asset sits on a customer site. Service history lists past and present work orders against each asset as standard. This is the area where Dynamics is genuinely strong for a machine builder.

Does it handle recurring maintenance contracts?

Yes. Agreements are a native concept: you define a recurrence and the system generates work orders across the assets at a customer location, and can generate invoices on a schedule alongside them. Entitlements apply pricing rules to those work orders. For an OEM selling maintenance contracts, this is one of the strongest parts of the product.

Can our customers see their machines in a Dynamics portal?

Yes, with Power Pages, which is licensed separately. Microsoft supplies a Field Service website template, and with the partner solution installed customers can view assets, agreements, work orders and invoices connected to their account, once each record is flagged to be exposed to them. There is also a self scheduling portal where a customer picks one of their assets and an incident type and books an appointment, which creates the work order. What the template does not give you is a parts list per machine or ordering against it.

Where does it fall short for a machinery OEM?

The customer facing and distributor facing half. Spare parts ordering by customers does not exist, QR access at the machine does not exist, and letting a distributor reissue portal access to their own end customers is a build. Meter readings have no native home, so operating hours captured by a technician become a custom field, and the IoT route through Connected Field Service solves a different problem. Emails also sit on accounts and cases rather than on the asset.

Is the help desk included?

Not in Field Service alone. Cases exist and work orders generate from them, and a case carries a Field Service tab that links it to the asset and functional location. But a connected service mailbox, routing and SLA tracking come with Customer Service Enterprise, which attaches at $20 per user per month on top. For coordinators that is a second licence rather than a setting.

Can we keep Dynamics and add Makula Field Service?

If Dynamics is already running your field operation, replacing it is usually the wrong move and we would say so. The case for Makula Field Service is stronger when the decision is still open, or when the customer and distributor half is the actual problem and the alternative is a Power Pages project plus a parts commerce build on top of an existing Dynamics estate.

When is Dynamics 365 Field Service the better choice?

When you are already a Microsoft estate with internal Dynamics administrators or a partner on retainer, when scheduling is genuinely complex enough to justify the optimisation add on, and when in house asset maintenance matters as much as customer machines, since the Supply Chain Management integration covers that.