ServiceNow CIS-FSM - Field Service Management Implementation - Work Orders Dispatch Scheduling Mobile Parts

FSM's billing data capture uses multiple mechanisms: (1) Time Tracking — technicians use the mobile app's timer (start/stop) for each work order task, recording precise billable labor hours by service type; (2) Parts consumption — when parts are recorded as used (from van stock or picked up from warehouse), pricing is pulled from the parts catalog for accurate material billing; (3) Travel — either GPS-based mileage calculation or per-trip flat rate configured by zone/territory. All this data flows to FSM cost records that can be exported to billing/ERP systems (SAP, Oracle, Salesforce Billing) via IntegrationHub. Option A (weekly timesheets) is inaccurate and delayed. Option C (scheduled duration estimate) doesn't reflect actual time and is not acceptable for T&M billing. Option D (manual reading of notes) is error-prone and requires significant manual effort.

FSM SLA Definitions work identically to other ServiceNow SLA frameworks: (1) Create an SLA Definition for Enterprise Work Orders with response target = 4 hours, warning at 3 hours (75%), breach at 4 hours; (2) Create another definition for Residential with 8-hour target; (3) Configure SLA Conditions using filter conditions that match account type = "Enterprise" or "Residential" — the correct definition is automatically applied when a work order is created. SLA pause/resume can be configured for business hours and exclusion windows. Escalation notifications at warning and breach stages alert the dispatcher and supervisor. Option A (priority note) has no system enforcement. Option B using two instances is operationally impractical and loses integrated reporting. Option D (priority levels) can feed into SLA conditions but Priority alone doesn't define time targets.

FSM Work Order Task checklists are enforced pre-conditions that must be completed before the technician can change task status. For hazardous work: the checklist for "Gas Line Repair" tasks includes mandatory items (PPE: hard hat ✓, gas detector ✓, safety boots ✓, hazard survey completed ✓, briefing acknowledged ✓). In the mobile app, the technician cannot set the task to "In Progress" or "Completed" without marking all checklist items — the button is grayed out until the checklist is done. This creates a per-job safety record embedded in the work order, providing regulatory compliance evidence. Option A (weekly email) doesn't ensure per-job compliance. Option C (supervisor calls) is unreliable and undocumented. Option D (work order description) is informational only — no enforcement mechanism.

ServiceNow's Location and Account records serve as aggregation points for all associated records. In FSM context, a store location record has related lists showing: all work orders (past and open), installed equipment CIs with their PM schedules, service contracts, open and historical Cases (if CSM is integrated), and SLA compliance history. This "Location 360°" view gives FSM dispatchers and service managers immediate context about a site without running separate queries. Option A (ad-hoc reports) provides the data but requires manual execution and doesn't provide a unified view. Option C (custom app) is unnecessary — the native Location record with related lists provides this. Option D (SharePoint) creates a data silo outside ServiceNow.

Route Optimization in FSM's DSE analyzes the complete set of a technician's assigned work orders for the day, their current GPS location, appointment time windows (customer availability constraints), estimated job duration, and road network to generate an optimized visit sequence that minimizes drive time and fuel costs. This is calculated automatically rather than relying on manual dispatcher review. The FSM mobile app then presents the optimized route to the technician with turn-by-turn navigation integration. Option A (manual daily review) is time-consuming and prone to suboptimal decisions at scale. Option C (zip code sorting) is a crude proxy for actual route optimization. Option D (map display) provides visibility but requires the technician to manually optimize — still human-dependent.