IFS FSM 6 (Field Service Management) · FSM4

Scheduling and Optimisation

6
Processes
214
Details worked out
42
Execution steps
6
Diagrams
FSM4.01

Manual Dispatch on the Schedule Board

A dispatcher placing work against people and time by hand. The FSM 6 schedule board is the control surface for unoptimised or exception work, and in many estates it is where most dispatch decisions are actually made.

IFS FSM 6 Service, Schedule Board
35 details
diagram
FSM4.02

Dynamic Scheduling Engine Integration

Handing scheduling decisions to the optimisation engine. FSM 6 connects to Dynamic Scheduling through configured service endpoints, sends rota and task data to it, and receives allocations back.

IFS FSM 6 Dynamic Scheduling
40 details
diagram
FSM4.03

Appointment Booking and Time Window Offer

Offering the customer a real, keepable time slot while they are still on the call. FSM 6 books appointments against either its own availability logic or the Dynamic Scheduling engine, within a configured window and lead time.

IFS FSM 6 Appointment Booking
39 details
diagram
FSM4.04

Roster, Shift and Availability Management

Recording who is working when. Rosters, shifts and shift exceptions are the capacity model that every scheduling decision in FSM 6 rests on, and they are also what is sent to the optimisation engine.

IFS FSM 6 Rosters
32 details
diagram
FSM4.05

Team, Skill and Territory Definition

Describing what each resource can do and where. Skills, teams and territory are the filters that both rule based assignment and the optimiser use to narrow the candidate set for a task.

IFS FSM 6 Core Entities, person skills and teams
33 details
diagram
FSM4.06

GPS Tracking, Geofencing and ETA

Knowing where resources are and using it. FSM 6 collects position from the mobile client, applies address geofences to infer arrival and departure, and generates the estimated arrival time that customer messaging depends on.

IFS FSM 6 GPS
35 details
diagram
What a license opens

Everything you can see here is real and current, the names, the structure and the counts come straight out of the ModelIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.

Sign in to open it