Field Execution, Debrief and Mobile

Getting the right work and the right reference data onto the technician's device, and getting the results back. FSM 6 mobile synchronises a filtered subset of the database to each user according to mobile process rules, and the size of that subset decides whether the app is usable.

Building what the technician sees. FSM 6 ships a mobile designer with its own screens, fields, lookups and home items, versioned as design revisions and assigned to user populations as design sets.

Recording what was actually done and used. Debrief creates the part usage, non part usage and time records that become cost, revenue and installed base changes, so it is the point where field activity becomes financial fact.

Declaring the work finished and closing the chain behind it. Completion releases succession, stops the commitment clock, makes the work billable and, when the request closes, can close its remaining tasks automatically.

Recording what people spent, in hours and in money, outside of a single task debrief. FSM 6 ships time and expense trackers with personal, team and manager views, and the resulting non part usage is both a cost and a potential charge.

Holding the documents and images that prove what happened. FSM 6 attaches files to requests, tasks, products, places, contracts and more, and the mobile client is the usual capture point for photographs and customer signatures.

Clocking on and off, separately from booking time to jobs. FSM 6 ships time clocks with their own events and rules, giving an attendance record that can be reconciled against work booked.