Text preview & study summary

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

A free sample of 5 questions from this quiz, shown in full with answer choices and explanations. No interactivity — everything is visible on this page for study and review.

Want to test your knowledge? Launch the Interactive Exam Simulator

Question 1

A company wants to charge customers for field service based on time and materials. The billing system needs data on: actual technician labor hours, parts used with list prices, and any travel charges. Which FSM feature captures this billing data?

Answer choices

  • A. Technicians submit manual timesheets at the end of each week

  • B. FSM Time Tracking captures actual labor hours per work order task (start/stop timers in mobile app); Parts consumption records parts used with catalog pricing from the parts catalog; Travel charges are calculated from GPS odometer data or configured distance rates; a billing integration or FSM Cost Tracking module aggregates these for invoicing or ERP handoff (Correct)

  • C. Estimate billing based on scheduled appointment duration

  • D. Create a manual bill after reading work order notes

Explanation

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.

Question 2

A telecommunications company's FSM implementation requires that work orders for high-value enterprise customers are always completed within a 4-hour response window, while residential customers have an 8-hour window. How should SLAs be configured in FSM?

Answer choices

  • A. Add a note to work orders for enterprise customers asking technicians to prioritize them

  • B. Define FSM-specific SLA Definitions with different response time targets: one definition for Enterprise account type (4-hour window, escalation at 3 hours) and one for Residential (8-hour window), applied via SLA Conditions based on the customer's account type field (Correct)

  • C. Create two separate FSM instances — one for enterprise and one for residential

  • D. Configure Priority levels (Critical, High) to differentiate enterprise from residential

Explanation

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.

Question 3

A utility company uses FSM and needs to comply with safety regulations requiring that before a technician begins hazardous work (gas line repair), they must acknowledge a safety briefing and confirm they have the required Personal Protective Equipment (PPE). How can FSM enforce this pre-work safety acknowledgment?

Answer choices

  • A. Email safety briefings to all technicians weekly

  • B. Configure Pre-Work Checklist on the Work Order Task for "Gas Line Repair" type — the checklist appears in the mobile app before the technician can change status to "In Progress"; checklist items include PPE confirmation, hazard identification, and safety acknowledgment; the task cannot progress without completing the checklist (Correct)

  • C. Train supervisors to call technicians before each gas line job

  • D. Add safety information to the work order description field

Explanation

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.

Question 4

An FSM implementation for a retail chain needs to track service history for each store location, including all past work orders, installed equipment, maintenance records, and pending open issues. Where in ServiceNow FSM is this information aggregated?

Answer choices

  • A. Run ad-hoc reports filtering work orders by store address each time

  • B. The Location record (or Account/Asset record) in ServiceNow serves as the hub: all work orders, CIs (installed equipment), maintenance history, open issues, and associated contracts are linked to the location record; FSM and CSM agents can view the Location 360° view showing this complete service history in a single widget (Correct)

  • C. Create a custom application to store location service history

  • D. Maintain a SharePoint site for each store with service records

Explanation

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.

Question 5

A field service manager notices that technicians are frequently traveling long distances between jobs, resulting in low productivity. The company wants to enable route optimization. What FSM feature addresses this?

Answer choices

  • A. Manually review each technician's schedule daily and rearrange tasks by location

  • B. Enable Route Optimization in the Dynamic Scheduling Engine, which considers multiple pending work orders, technician current locations (via GPS from mobile app), appointment time windows, and generates the optimal visit sequence minimizing total travel distance/time (Correct)

  • C. Create a Scheduled Job that sorts work orders by zip code and assigns them sequentially

  • D. Use Google Maps integration to show technicians their work orders on a map, and let them self-organize

Explanation

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.