FSM Fundamentals Flashcards
Explain the initiator role
Initiator (wm_initiator)
As an initiator, you can create a new work order or you can create a work order from other record types, such as problem, incident, change, or project task.
Explain the qualifier role
Qualifier (wm_qualifier)
Field Service Qualifiers are crucial in verifying work orders and related tasks, ensuring all details are accurate before dispatching field agents. Members of qualification groups can qualify work orders in the ‘awaiting qualification’ state. The qualification process includes:
- Reviewing and updating details of work orders and tasks.
- Optionally creating additional work order tasks.
- Defining task-specific requirements, such as parts and skills (optional).
- Establishing dependencies between work order tasks (optional).
- Assigning a dispatch group to each task.
- Officially qualifying each work order task.
These steps are vital in maintaining the integrity and efficiency of the field service process.
Explain the Field Service Administrator
[wm_admin}
Configures Field Service Application:
- Manual or Automatic Qualification
*
Explain the dispatcher role
Field Service Management Dispatcher
[wm_dispatcher]
Schedules tasks, adds parts, and assigns tasks to work agents. Dispatchers also can:
Create tasks.
Add part requirements.
Source parts.
Edit all work order task fields and manage tasks
from Draft to Assigned status.
Edit the Assigned to field until work starts.
Create tasks using the Clone Task feature.
Set actual travel time and work start and end times if needed.
Add work notes to any field service record.
Create, edit, and delete incidentals.
View expense lines.
View certain fields in non-subscription-based contracts.
What are phases of field service management process
Initiation
Qualification
Scheduling & Dispatch
Delivery & Confirmation
Analyze & Improve
Explain the field service agent role
Agent (wm_agent)
What are the workflow states? What primary role s interact with state?
Draft (wm_initiator)
Awaiting Qaulification (wm_qualifier)
Qualified (wm_qualifier)
Assigned (wm_dispatcher)
Work in Progress (wm_agent)
Closed Complete (wm_agent)
Define the hybrid roles and responsibilities
Field Service Initiator
Field Service Initiator Qualifier
Field Service Initiator Qualifier Dispatcher
Initiator
Qualifier
Dispatcher
What happens in the in the Initiation phase
Initiation phase is when the work order is created:
- Associate Assets
- Apply template (optional)
- Assign qualification group
- Approval (optional)
What happens in the qualification phase
Activities in qualification
- Create Tasks/Apply Template
- Define dependencies, parts, skills
- Assign dispatch group
- Qualify tasks
What happens in the Scheduling & Dispatch phase?
Activities during Scheduling & Dispatch:
- Requests for additional information
- Sourcing parts (optional)
- Dispatch Tasks
What happens during the “Execute Work Order Tasks”?
- Work Order tasks are accepted or rejected
- Source Parts and/or Pick up assets
- Tasks are performed
- Create Additional tasks (optional)
What happens during the ‘Close Work order’ phase?
- Record time worked
- Record Asset Usage
- Close Task(s)
- Sign & Confirm (optional)
What are ways to create a work order?
- Portal
- CSM/FSM Configurable Workspace
- ServiceNow Connect Operations
- Schedule Maintenance Plan
Integrated Applications:
1. From a Case
2. From ITSM records
3. From a project task
4. From Work orders
Work order templates can include:
- Descriptions
- Work Order Tasks
- Part Requirements
- Skills
- Task Dependencies
- Installation Guides or Maintenance Procedures
- Checklists
What happens when no work order tasks are are added?
If no task exists, at least one is automatically generated, inheriting the short description, detailed description, and location from the parent work order request.
However, this task still requires manual assignment to a dispatch group. Users holding the [wm_initiator_qualifier] or [wm_admin] roles are authorized to allocate these tasks to the appropriate dispatch groups.
What are work order task states?
- Draft
- Pending Dispatch
- Assigned
- Accepted
- Work in Progress
- Complete
Explain task-driven vs. request-driven process
The work order process lifecycle can follow either a task-driven or request-driven approach. By default, the field service business process favors the task-driven method, recognized as best practice. In this model, each work order must have one or more subtasks, with their statuses directly influencing the work order’s overall status. Conversely, the request-driven model operates without specific tasks. The choice between task-driven and request-driven lifecycles depends on the organization’s needs and is configured by a system administrator.
The work order lifecycle is controlled by the work order task states (task-driven). Explain in detail
- Once all associated work order tasks are in the Pending Dispatch state, the parent work order request moves to the Qualified state.
- The parent Work order state changes to Work in Progress if no other associated tasks are in Draft State
- If all work order tasks reaches ‘Closed Complete’ then the work order will be marked ‘Closed Complete’
- If any of the work order tasks are marked as ‘Closed Incomplete’ then the work order is marked ‘Closed Incomplete’
What happens when work orders are created from templates?
Using Work Order Templates significantly streamlines the qualification process. Regardless of whether qualification is manual or automatic, tasks stemming from templates automatically shift to the ‘Pending Dispatch’ state if set to manual task assignment method (the default setting). This efficiency lets qualifiers concentrate on exceptional cases needing extra scrutiny and planning, optimizing their workload.
In manual qualification process, the qualifier will:
- Examine work order and task details.
- Add parts or skill requirements as needed.
- Create additional work order tasks if required.
- Establish task dependencies if applicable.
- Assign or confirm a dispatch group.
- Officially qualify the work order.