Asset Maintenance Mobile

The problem this solves

Asset management in Dynamics 365 Finance & Operations holds everything a maintenance department needs: functional locations, assets, maintenance plans, maintenance requests, work orders, work order jobs, checklists, counters and maintenance schedules. What it does not hold is the technician. The technician is under a machine, in a plant room, on a roof, or in a vehicle — usually somewhere with no usable signal — and the F&O work order form is not usable on a phone in that situation.

So the day runs on paper. Work orders are printed in the morning, annotated by hand, and typed into F&O by a planner or an administrator in the afternoon or the following week. Three things break as a result. Completion times are guesses, entered from memory, so labour hours against the asset are wrong and any downtime analysis built on them is wrong. Meter readings arrive late or not at all, so counter-based maintenance plans trigger against stale readings and either over-service or miss the interval. And spare parts get taken from the store and consumed against the job without ever being posted, so inventory on hand drifts from reality and the maintenance cost on the asset is understated.

The warehouse mobile app solves this shape of problem for warehouse work. Nothing equivalent ships for maintenance.

What ECOSIRE builds

A technician mobile app over F&O work orders

A mobile application for phone and tablet that authenticates the technician against their F&O user, shows the work orders assigned to them from EntAssetWorkOrderTable and their jobs, and lets them execute the job end to end. The list is filtered by the technician's assignment, functional location and maintenance job type, so a technician sees their work and not the plant's.

Each work order opens onto the asset record: asset ID, functional location, manufacturer and model data, the counters registered against it, and the maintenance history. Attachments held against the asset — drawings, manuals, previous photos — are available on the device.

Genuine offline operation

This is the part that decides whether the app gets used. Work orders assigned to the technician, their assets, checklists and the relevant spare-part list are downloaded to the device on sync. From that point the technician works with no connection: completing checklist lines, recording readings, capturing photos, logging hours and consuming parts. Everything is queued locally.

On reconnection the queue posts to F&O through data entities, in order, with conflict handling for the case where a planner changed the work order in the meantime. Failed postings are visible to the technician and to a supervisor rather than silently dropped — nothing is ever discarded because sync failed.

Checklists, readings and evidence

Maintenance checklists defined on the maintenance job type are rendered as structured mobile forms: pass/fail, numeric entry with tolerance, text notes, and mandatory-photo lines. A line outside tolerance can be configured to automatically raise a maintenance request in F&O, so a technician spotting a second problem while doing a routine service does not have to remember to phone it in.

Counter readings post to the asset counters that drive counter-based maintenance plans, with plausibility checking against the previous reading so a mistyped digit is caught on the device rather than triggering a spurious maintenance schedule.

Photos and signatures are captured on the device and attached to the work order record in F&O through the document management framework.

Parts, hours and costing

Spare-part consumption is recorded against the work order job and posts as item consumption to F&O, relieving on-hand inventory in the correct warehouse and location and landing the cost on the asset. Where a part is not in the van stock or the store, the technician raises a request from the device rather than improvising.

Labour hours are recorded against the job and posted as hour consumption, so the true labour cost sits on the asset and on the maintenance job rather than being reconstructed later.

Supervisor and back-office surface

An F&O workspace for the maintenance supervisor showing device sync status per technician, queued and failed postings, work orders in progress, and readings received today. Batch jobs handle the scheduled sync of assignment data and any periodic housekeeping, registered through the SysOperation framework with standard batch group and recurrence behaviour.

Platform and integration

The mobile front end is built on Power Platform where that fits your licensing and device estate, or as a dedicated cross-platform app where offline requirements or device constraints call for it — we decide that with you during scoping rather than assuming. Either way the F&O side is X++ extensions and data entities in a dedicated model, with no overlayering, and Dual-write is used where a Dataverse-side record genuinely needs to exist rather than as a default.

Who this is for

Organisations running F&O asset management with technicians who work away from a desk: manufacturing plants with in-house maintenance teams, facilities and property operators, fleet and equipment operators, utilities and process sites. It is most valuable where meter-based maintenance plans matter, where spare-part consumption is currently posted late or not at all, and where connectivity on site is unreliable.

It assumes asset management is configured in F&O with assets, functional locations and maintenance job types in place. If you are not there yet, that configuration comes first and we will say so during scoping.

How delivery works

Scoping call. We review your asset management setup: functional location hierarchy, maintenance job types and checklists, counter usage, how spare parts are stocked and issued, how technicians are assigned, what devices they carry, and what connectivity is really like on site.

Fixed quote. A written scope covering the app platform chosen, the offline model, which postings are in scope, supervisor tooling, the F&O version targeted, device assumptions, explicit exclusions, and a fixed price. Nothing begins until you accept.

Build. Built in our F&O development environment against a copy of your configuration where available. Typical lead time is one working week from accepted quote.

Install in test. The deployable package goes into your sandbox via LCS and the app is installed on real technician devices. We configure job types, checklists and assignment rules with your maintenance team, and you run acceptance with real technicians on real work orders — including a deliberate offline test, because that is the requirement that matters most.

Production. Promotion to production through your normal release process after sandbox sign-off, with support through the first live week and full source handover.

Support. A defect-support window from go-live covering anything not behaving as specified. Additional device platforms, new checklist types beyond the scoped set, and enhancements are quoted separately.