Skip to main content
Version: 2.4

Mobile Execution and Material Management

WFM execution is mobile-first for technicians, with dedicated views optimized for daily field operations.

1. Mobile Solution Model

tSM mobile approach combines:

  • responsive web application,
  • Progressive Web App (PWA) packaging,
  • native Android/iOS packaging via Capacitor for device-specific capabilities.

This supports both browser-based access and enhanced native functions where required (for example selected device integrations and policy-constrained capabilities).

2. Technician Daily Work Surface

ScreenOperational Purpose
Task listWhat to do today and in which order
MapRoute and location-aware execution
Task detailWork instructions and contextual data
Start/finish formsExecution evidence and status transitions
Material sectionConsumption/write-off and equipment handling

3. Task List

Technician sees scheduled tasks for selected day with preview information.

Mobile task list

4. Map View

Map view supports location-driven execution and navigation.

Typical layers:

  • technician daily route,
  • colleague route overlays,
  • unscheduled tasks,
  • planned outages.

Mobile map and route view

5. Task Detail and Execution Steps

5.1 Task Overview

This overview shows example of core task information and type-specific details.

Detailed view of task information in the mobile app:

Task detail

Additional task details displayed on mobile:

Task detail

Available actions for the task in mobile interface:

Task detail - actions

Photo attachments section for task evidence:

Task detail - photos

Services or additional features related to the task:

Task detail - services

5.2 Task Start

Task start captures start context and execution initialization.

Task start example

Task comments section for initial notes or notes during task realization:

Task comments

5.3 Task Finish

Task finish captures:

  • customer signature for completion protocol,
  • result and completion notes,
  • issue/solution comments,
  • multimedia evidence,
  • optional collaboration mentions.

Task completion protocol with signature capture:

Task finish example - protocol

Final task note and completion summary:

Task finish example - final note

5.4 Material During Task

Technician records material usage related to the task.

Material entry for task consumption and stock write-off:

Task material entry example

Additional material entry details for task execution:

Task material entry example

5.5 Additional mobile execution examples

Work logs and execution history in mobile view:

Mobile execution example C

Mobile navigation and task overview interface:

Mobile execution example D

5.6 Task collaboration

Collaborators assigned to the task:

WFM mobile task colaboration

The dispatcher can assign collaborators to tasks as needed: WFM dispatcher task collaboration settings

6. Additional Mobile Actions

Configurable additional actions include:

  • collaboration request to another technician,
  • availability updates,
  • immediate follow-up task creation,
  • execution of selected external-system functions.

These actions reduce dispatcher load and shorten time-to-resolution in field conditions.

7. Material Management Domain

Material management in WFM coordinates task-level consumption with stock/ERP systems.

7.1 Material Catalog and Stock

  • material catalogs (master records) can be synchronized from ERP,
  • hierarchical categories are supported,
  • stocks may include central, local, project, consignment, and personal stock types,
  • materials can be serialized or non-serialized.

Material catalog and stock overview for WFM operations:

Poroduct

7.2 Supported Movements

OperationMeaning
Remove for taskConsume stock material during execution
Stock transferMove material between stocks
Material orderRequest replenishment

Created movements/orders are synchronized back to ERP.

8. Operational Notes

  • keep mobile forms focused on field context and minimum required input,
  • enforce evidence capture policy by task type,
  • align material write-off rules with ERP governance,
  • monitor offline/online behavior for critical process steps.