Field Service Management (FSM) in ServiceNow is the platform module that plans, dispatches, and tracks on-site technician work through work orders. It delivers the best results when operating on two pillars: the CMDB, which indicates which asset will be serviced, and the ITOM, which indicates when and why service is needed. Without them, dispatch is fast, but relies on incomplete data.
Why Field Service Management depends on IT data
Field Service Management solves the execution of fieldwork: who goes, when, with which parts, and with which checklist. What it doesn't solve on its own is the quality of the information preceding the dispatch. An open work order for a poorly identified asset increases the risk of a wrong visit, wrong part, or a second visit.
The official ServiceNow documentation describes a work order as the record that stores data about the requested job, such as customer, address, work location, and... configuration items associates (Integrated work order entry documentation, Australia release, updated 12/03/2026The design of the FSM, therefore, already assumes that the CIs exist and are correct.
That's why implementing Field Service Management is also a decision about CMDB and ITOM. When field operations and IT work on separate bases, the gain from FSM is limited to scheduling, and the asset context continues to be reconstructed by phone or spreadsheet.
What CMDB delivers to Field Service Management
CMDB is the foundation for CIs and relationships on the platform. In Field Service Management, it appears in three documented locations:
- CI affected in work order. The Affected CI field identifies the main item requiring the work, and additional items are entered into a related list. The same CI can be applied to multiple tasks within the same work order.Work order creation documentation).
- Context-based inheritance. When creating a work order from an issue or change, the affected CI, priority, and descriptions are copied to the new record. From a CSM case, the work order inherits the account, contact, affected CI, location, and active information.work order management documentation).
- Linear assets. With the Enterprise Asset Management plugin enabled, FSM now supports linear assets, such as networks and ducts, common in utilities and telecom.Work order and task configuration documentation).
The table summarizes what each piece of data from the CMDB represents for those running the service.
| Data from CMDB | Use in Field Service Management | Risk when data is missing. |
|---|---|---|
| CI and asset class | Supports the selection of templates, tasks, and checklists. | Generic work order, without instructions properly related to the equipment. |
| Relationships between CIs | Shows which services the asset participates in. | Prioritization without a vision of business impact. |
| Location and responsible party | Supports territories, dispatch, and on-site contact. | Technician sent without a reliable address or contact information. |
| Work order history by CI | It gives the coach the asset's intervention history. | Diagnosis repeated at each visit. |
What ITOM delivers to Field Service Management
ITOM covers the visibility and operational health of the infrastructure, with Discovery, Service Mapping, and Event Management, among other capabilities. For field operations, three contributions are particularly important.
The first is the updating of the CIs. Discovery reduces the reliance on manual registration and keeps the CMDB closer to reality, which protects the reliability of the Affected CI field.
The second is the context of the alert. Event Management uses the information gathered by Discovery to map alerts to configuration items. An infrastructure alert, therefore, arrives already associated with the CI and, through its relationship, with the services that depend on it.
The third is response automation. Alert response subflows allow, among other actions, the creation of incidents and major incidents from alerts. Since an incident allows a work order to be opened with the affected CI, the alert, incident, and work order chain becomes traceable. The documented path goes through the incident: flows that link the alert directly to the work order require design and validation within each organization's environment.
The ServiceNow Work Order Management process guide (Zurich release) lists proactive monitoring among the work initiation sources, alongside customer service, projects, and planned maintenance. For preventive maintenance, the Field Service preventive maintenance documentation It describes plans that automatically generate work orders when a trigger limit is reached, with task templates by equipment type.
How the flow works from end to end.
With CMDB and ITOM connected to Field Service Management, the reactive service cycle follows this sequence:
- Discovery and integrations keep asset and service CIs up-to-date in the CMDB.
- A monitoring event generates an alert, mapped to the affected CI.
- A rule or subflow creates the incident, or major incident, already with the CI (incident code).
- The agent creates a work order from the incident, and the affected CI is copied to the new record.
- Field Service Management qualifies, schedules, and dispatches work based on skills, location, and availability.
- The technician executes and closes the work order, and the result is traceable in both the work order and the source record.
Field Service Management with and without CMDB and ITOM
The comparison below shows what changes in operation when FSM is deployed as a standalone module and when it is deployed on top of the IT database.
| Dimension | Isolated FSM | FSM with CMDB and ITOM |
|---|---|---|
| Asset identification | Free text or parallel registration | CI and CMDB relationships |
| Origin of the so-called | Request from the customer or the attendant. | Also, proactive alerts and monitoring. |
| Context for the coach | It depends on what was typed. | Affected CI, history and related services |
| Prioritization | Priority indicated in the call. | Priority combined with the impact on services |
| Preventive maintenance | Manually defined schedule | Plans with triggers based on configured limits. |
| Data governance | Duplicate information across areas | Single source for CIs and assets |
Where integration often fails
Field assets outside the CMDB are the first point of failure. Operational equipment, such as meters, stations, and networks, often never undergo an IT Discovery process. It is necessary to define which CI classes represent these assets and what the source of truth is for each one, whether it's ERP integration, controlled import, or Discovery, when applicable.
The second point is the confusion between asset and CI. The work order form has distinct fields for the asset, identified by label or serial number, and for the affected CI. The asset represents the lifecycle and cost record, and the CI represents the configurable item and its relationships. Without a clear linking rule between the two, the same equipment appears twice, and neither record is reliable.
The third point concerns incomplete relationships. Without them, the alert reaches the CI (Customer Interaction), but not the impacted business service, and prioritization of the field again depends on manual judgment. Modeling services with the CSDM This is what gives these relationships a stable pattern.
The fourth point is the absence of continuous governance. A CMDB (Corporate Governance and Development Committee) without accountability, without completeness indicators, and without a review routine loses credibility over time, and the field is the first to feel it. strategic value of CMDB in IT asset management It depends on that discipline.
How to begin: recommended order
In an operation without a structured CMDB, the deployment order reduces rework:
- Map the field asset classes and define the source of truth for each one.
- Model the services that depend on these assets using CSDM.
- Establish discovery and integrations, measuring the completeness of the CIs.
- Configure the alert, incident, and work order chain in a pilot scope.
- Enable Field Service Management scheduling and dispatching for this scope and expand by territory or asset type.
4MATT is a ServiceNow Elite Partner in Brazil, holder of the Technology Excellence Partner Award 2024-2025, and has more than 180 certified specialists working in FSM., ITAM, CMDB and ITOM. For an introductory overview of the module, see What is ServiceNow's FSM?, and for market recognition, coverage of ISG Buyers Guide 2025.
Frequently asked questions about Field Service Management, CMDB, and ITOM.
Does Field Service Management require a CMDB to function?
Technically, no: ServiceNow documentation indicates that it's possible to use Field Service Management only with work orders and tasks. In practice, without CMDB, the Affected CI field loses value and the technician receives less context. Therefore, CMDB should be treated as a prerequisite for the maturity of field operations, and not just as an additional module.
Does ITOM automatically create Field Service Management work orders?
The documented path goes through the incident: Event Management maps the alert to the CI, subflows can create the incident, and the work order is created from it with the affected CI copied. Flows that link the alert directly to the work order depend on configuration and validation in the environment, and should not be assumed as default behavior.
What is the difference between "asset" and "initial charge" in a work order?
An asset is a record of a piece of equipment's lifecycle, cost, and ownership, identified by a tag or serial number. A CI (Contract Item) is a configurable CMDB (Computer-to-Management Database) item, with class, attributes, and relationships. A work order has fields for both, and the organization needs to define the linking rule between them to avoid duplicate records.
Which ServiceNow modules integrate with Field Service Management?
The documentation lists the creation of work orders from incidents, changes, project tasks from Project Portfolio Management, and requests from ITSM. CSM also creates work orders from cases, and Order Management creates work orders for requests that require fieldwork. Each integration copies data from the source record to the work order.
Where do I start a Funds Management System (FSM) project without a structured Communications Management Board (CMDB)?
Start with a pilot scope: a field asset class, a territory, and a complete alert, incident, and work order chain. Defining the source of truth for CIs before configuring scheduling and dispatching avoids rework because scheduling inherits the quality of the data it receives.