Task Creation, Assignment and Dispatch

Turning a request into the work that has to be done. FSM 6 selects a task template from request information through the delivered Task Selection rule, and the template supplies duration, skills, steps and parts.

Chaining work so that finishing one task creates or releases the next. FSM 6 ships four succession rules covering task to task, task to task set, task set to task and task set to task set.

Deciding who does the work. FSM 6 delivers a Work Assignment rule that proposes or sets the person on a task from skills, territory, availability and place relationships.

Controlling which task status can follow which, and what each transition means operationally. FSM 6 holds this as an explicit status flow, which makes it one of the few pieces of process in the product that is declarative rather than scripted.

Recording what happened to a task and telling the people who need to know. The pattern mirrors requests: an event generation rule writes task events, and a notification rule turns selected events into messages.

Raising something to a human when time or value thresholds are crossed. FSM 6 delivers sixteen escalation generation rules covering requests, tasks, purchase orders, projects, contracts, quotes, invoices and more, plus an approval limit framework for value based authorisation.

Making sure the parts are there before the technician is. A task generates part needs, which become demand on stock, and the task cannot sensibly be scheduled until those needs can be met.