Is your field operation still running on Excel and WhatsApp? The Field Management (FSM) module of the Intranet Portal links the alarm to a work order, the work order to a signed closure report, and that to the invoice. Drag-and-drop assignment from a live map, geofenced technician presence verification, SLA countdowns, barcode-driven material install/removal and a mobile offline app, all leaving your ERP as the single source of truth, on one monthly subscription.
An ERP keeps invoices, customer accounts and stock, but it never sees the field. "Is the technician on the alarm site right now, or have they already left?" is a question ERP architecture simply cannot answer; it has no concept for tying real-time geographic presence to a work order. Field-specific SLA timers (2-hour acceptance, due_at countdowns), drag-and-drop assignment from a map, geofenced presence verification, barcode-driven on-site install/removal and signed PDF closure reports all fall entirely outside ERP scope. Bolting these onto an expensive upper-tier suite such as SAP FSM, or building them from scratch, carries a prohibitive cost, which is why most companies run the field on Excel and WhatsApp. The Intranet Portal takes on this operational layer and writes back only the approved closure and billing result to the ERP.
Alarms arrive from four sources (manual entry, Turkcell webhook, Excel import, mail/OCR), and a work order is opened from any of them in a single click. A draft to assigned to accepted to started to completed to review to closed state machine writes every step to the audit trail. A closed work order, with its line-item costing, is ready to invoice directly.
A single screen shows 8 live counters, site and vehicle markers on Google Maps, and a technician chip grid. The dispatcher drags an alarm or work-order card and drops it onto a technician; the system automatically creates the work order, assigns it and starts the SLA timer. What used to take 5 or 6 clicks becomes a single move.
The mobile app sends a location ping every minute while a work order is active. Arrival is confirmed automatically against the site geofence (200m by default, adjustable from 50 to 2000m). If the technician leaves the site early, the supervisor receives an instant alert, protected against false positives by a 3-consecutive-ping hysteresis; if no ping arrives for more than 15 minutes, a 'location unknown' signal is raised.
A 2-hour acceptance SLA starts at assignment; if the job is not accepted in time, automatic escalation triggers an email, an SMS and a dispatcher notification. A separate due_at deadline runs a 4-stage colour-coded countdown (green, yellow, orange, red); as the deadline approaches and once it passes, the technician is notified, including a mandatory SMS.
Barcodes are scanned from the work-order screen using the camera (native BarcodeDetector, with manual entry on unsupported devices). An 'installed' action deducts stock, a 'removed' action restores it, and the list of materials used along with the closure-report line items are populated automatically. Where no supplier barcode exists, our own label (RFL-MAT-NNNNNN) is printed.
The warehouse to technician to site cycle is tracked via material_assignments: stock is untouched at hand-out, consumption on site is deducted FIFO from the oldest assignment, and any remainder is returned to the warehouse in the evening. A 'What I'm carrying' page shows what each technician holds; open custody older than 24 hours raises a warning.
An incorrectly entered install/removal is never deleted; it is undone with a reverse movement: the original is flagged, the stock and custody arithmetic is corrected automatically, and both lines remain in the audit trail. A technician can correct their own mistake within 30 minutes; a supervisor can reverse with no time limit.
Photo evidence categorised as before/after/material/meter (with part recognition and meter OCR via a Vision LLM). When a work order is completed, a draft closure report opens automatically; the helpdesk fills in the intervention reason, materials, hours and cost. A reproducible PDF is generated with the photo gallery and the technician and customer signatures.
An Expo iOS/Android app lets the technician run their entire day from the phone: accept/start/complete work orders, background location pings, a photo upload queue and material consumption. When the mobile signal is weak on site, an offline work-order queue ensures no record is lost and syncs once connectivity returns.
An alarm reaches the system via Turkcell webhook (HMAC plus replay protection), manual entry, bulk Excel import or mail/OCR. For a critical alarm, SMS, push and email are sent automatically to the dispatcher role; 5 or more repeats at the same site within 72 hours are flagged 'chronic', and an alarm correlated with a power outage is filtered out as 'no site visit needed'.
A work order is opened from the alarm in a single click (site, priority and title are filled in automatically). On the live board, the dispatcher drags the alarm card to the least-loaded technician; the work order is created, the assignment is made, and the 2-hour acceptance SLA timer plus any due_at countdown begin.
The technician accepts and starts from mobile; geofence telemetry kicks in. On site they install/remove materials by barcode (deducted FIFO from custody) and upload before/after and meter photos. If they leave the site early or the location drops out, a live alert is raised to the supervisor.
The technician completes the job; the work order enters the helpdesk review queue. Once approved, the closure report is filled in (intervention reason, materials, hours, cost) and a signed PDF is generated with the photo gallery and signatures. The line-item cost (closure_line_items) comes out ready to invoice.
The billable line items of the closed work order and the matched employee record are transferred through the Uyumsoft/ERP integration. The ERP holds the invoice and customer account as the single source of truth; the entire operational trail (SLA, photos, materials, signatures) stays in the portal.
Field Management is an operational layer that does not depend on the ERP; the field is run by the portal, not the ERP. The ERP remains the master data source and the financial ledger. The portal reads master data and writes back only the approved, closed result to the ERP on the billing side.
Technician, dispatcher and supervisor records are mirrored read-only from the HR module of the ERP (Uyumsoft/Logo/SAP/Mikro/Netsis). Assignment, custody and signature flows run on this master data; no second employee record is kept in the portal.
The line-item cost of a closed work order (closure_line_items: materials, labour hours, intervention) is combined with the subcontractor-operator contract rate to form an invoice draft and transferred to the Uyumsoft ERP. The invoice and customer account remain the single source of truth in the ERP; there is no double entry.
The GSM base-station inventory is matched per operator via an external ID (turkcell_site_id, etc.); material items are managed in the portal by barcode and reorder point, logged per movement so they stay reconciled with the ERP stock ledger.
Beyond the ERP, the Turkcell alarm webhook, Denge fleet GPS (15-60s), BEDAS/TREDAS outage lists, NetGSM SMS and Expo push connect directly to the portal. This operational feed is not the ERP's domain; the portal brings it all together on a single board.
Tell us your ERP and your process. We’ll show how this module works and scope it into your subscription — no man-day, licence or setup fee.
Book a Demo →