Skip to content

Task types

Smart Maintenance Task Manager has five built-in task types. Each type defines a default set of form fields tailored to the work. Individual tasks can add or remove fields beyond the defaults.

The five types

Type Typical use Default fields
Lubrication Applying grease, oil, or other lubricants Product, quantity, point condition, photo
Mechanical Inspection, adjustment, cleaning Measurements, condition rating, notes, photo
Electrical Voltage, current, insulation and thermal checks Voltage, current, insulation reading, thermal photo
Production Output reading, run-hour capture Output, run hours, anomaly flag
Repair request Resolution of a reported fault Failure confirmation, parts used, time spent, before/after photo

Every task type supports safety procedure gating, threshold-bound numeric fields, and photo attachments.

Lubrication

When to use

  • Grease application at a specific grease point.
  • Oil top-up on a gearbox.
  • Replacing a sealed cartridge.
  • Periodic re-lube cycles driven by run hours or calendar time.

Use Mechanical instead when the lubricant is incidental to a broader inspection or adjustment.

Default fields

Field Type Notes
Product Dropdown From the master Products list. Filtered by compatibility when the component has a preferred product.
Quantity Numeric Unit attached from master data (ml, g, oz, l). Drives reorder reports.
Point condition Dropdown Good / Fair / Poor, or a custom enum.
Photo Photo One photo of the lubrication point post-application is typical.

Reports that consume this type

  • Completion Report — counts completed lubrication tasks vs scheduled.
  • Consumption Report — aggregates quantity per product, useful for reorder forecasting.

Mechanical

When to use

  • Periodic inspection routines.
  • Adjustments, cleaning, minor replacements.
  • Any routine work that isn't specifically lubrication, electrical, or production-metric capture.

Mechanical is the most commonly-used type and the most flexible — most custom fields you add during task design end up on Mechanical tasks.

Default fields

Field Type Notes
Condition Dropdown Good / Fair / Poor (or a custom enum).
Observations Free text Notes about what you found.
Action taken Free text What you did about it.
Photo Photo Optional, usually recommended.

Common custom additions:

  • Numeric measurements (belt tension, bearing temperature, clearance).
  • Yes / No checks (is the guard in place? Is the coolant level adequate?).
  • Multi-select checklists for multi-step inspections.

Reports that consume this type

  • Task Reporting — raw execution log.
  • Task History — historical drill-down.
  • Technician Comparison — maintenance throughput per technician.

Electrical

When to use

  • Voltage / current checks on motors, drives, switchgear.
  • Insulation-resistance measurements (megger tests).
  • Thermal imaging of panels, connections, bus bars.
  • Any measurement that requires electrical PPE and lock-out / tag-out procedures.

Safety

Electrical tasks should always have a safety procedure attached. Without explicit acknowledgement, a technician can power-on-test without lock-out and get hurt.

Default fields

Field Type Notes
Voltage Numeric (volts) Threshold-bound if configured.
Current Numeric (amps) Threshold-bound if configured.
Insulation reading Numeric (MΩ) Threshold-bound.
Thermal photo Photo Required for thermal imaging tasks.
Notes Free text Observations.

Reports that consume this type

  • Task Reporting.
  • OEE Report — electrical failures correlate with downtime.

Production

When to use

  • Capturing run-hour readings from equipment meters.
  • Logging output counters (units produced, kilograms processed, metres of fabric).
  • Periodic recording of production-relevant metrics that aren't maintenance per se but feed analytics.

Production tasks are less about fixing things and more about capturing numbers that drive OEE and scheduling decisions.

Default fields

Field Type Notes
Output reading Numeric Units attached from master data.
Run hours Numeric (hours) Hour-meter reading. Often drives schedule triggers for run-hour-based tasks.
Anomaly flag Yes / No Quick escalation flag.
Notes Free text Optional.

Reports that consume this type

  • OEE Report.
  • Asset Availability.
  • Yearly Report.

Repair request

When to use

  • Resolving a reported repair request.
  • Corrective work after a shutdown.
  • Follow-up on an anomaly flagged during another task.

Repair tasks usually have an originating repair request — the link between the original report and the resolution is tracked so you can follow incidents end to end.

Default fields

Field Type Notes
Failure confirmation Yes / No Did you confirm the reported failure?
Failure type Dropdown From master Repair request types.
Parts used Multi-select From Products / Tools master data.
Time spent Numeric (hours) Drives cost reports.
Before photo Photo State when you arrived.
After photo Photo State after repair.
Notes Free text What you did, what you'd recommend next.

Reports that consume this type

  • Repair Request Report — resolution time, cost, recurrence.
  • Task Reporting.

Task type common behaviours

Safety procedure gating

Any task type can have a safety procedure attached. When a safety procedure is present, the technician must acknowledge each safety measure before the form becomes available. See Safety procedures (web portal).

Threshold highlighting

Numeric fields bound to a threshold in master data highlight when the entered value is out of range:

  • Green background — within range.
  • Orange background — at edge of range.
  • Red background — out of range.

Highlighting is advisory — the form still submits. It's a visual cue for both the technician and the approving Supervisor. See Master data.

Photo attachments

All task types support photos. Default limit: 10 photos per task, 10 MB per photo, JPEG or PNG. See Photos and attachments.

Recurring schedules

Any task can be attached to a recurring schedule (daily / weekly / monthly / custom pattern). The schedule generates task instances automatically at the right time. See Scheduling.

Offline execution

All task types work offline. The mobile app caches the full form definition and renders it without a server round-trip. See Working offline.

Choosing a type

Rough decision tree:

Is it lubrication?
 ├── Yes → Lubrication
 └── No → Is it measuring voltage / current / insulation / thermal?
          ├── Yes → Electrical
          └── No → Is it recording production output or run hours?
                   ├── Yes → Production
                   └── No → Is it resolving a reported fault?
                            ├── Yes → Repair request
                            └── No → Mechanical

When in doubt, choose Mechanical — it's the most flexible and the least likely to mis-categorise.

Custom fields

Beyond the defaults, any task can add custom fields. Common additions:

  • Extra numeric measurements with or without thresholds.
  • Extra dropdowns (pick from a custom list).
  • Yes / No checks.
  • Multi-select checklists.
  • Additional photo fields (named, e.g. "Photo of seal before", "Photo of seal after").

Custom fields are defined once per task, not per task type.