Field Service Portal.

What does the ETHX Softcon Field Service Portal do for Oracle users?

The ETHX Softcon Field Service Portal is a work-order management solution that covers dispatch, technician routing, on-site mobility, and closure for field service teams, with invoices posting back to Oracle automatically. Customers can log service requests through a self-service portal with status tracking, and dispatchers work from a drag-and-drop board with route optimisation, SLA traffic lights, and live GPS technician location. Routing can be rule-based or AI-assisted using skill match, SLA, location, and technician utilisation.

Technicians use an offline-capable mobile app that caches work orders, parts, and instructions and syncs when connectivity returns. On site, they capture photos, parts used, labour time, and customer signature; closing the work order triggers an Oracle AR invoice for labour and parts. The portal integrates with Oracle Service Cloud, Fusion AR, inventory, and telephony. ETHX Softcon rolls it out through assessment, configuration, integration, a two-to-four-week pilot with one region or team, and region-by-region scaling.

What should you evaluate before adding a field service portal to Oracle ERP?

Begin by comparing your requirements with Oracle Fusion Field Service, because Oracle already offers scheduling, technician mobility with offline access, and a platform that connects customer service, supply chain and ERP. If your work orders, skills and service levels fit that model, configuring the standard product may cost less over time than maintaining a custom one. A custom portal is easier to justify when workflows are unusual, when service requests originate in a non-Oracle system, or when the back office runs on E-Business Suite.

Offline behaviour and devices deserve early, specific decisions. Technicians work in basements, plant rooms and rural sites, so define which records are cached on the device, for how long, how conflicting edits are resolved, and how photos and signatures queue until connectivity returns. Devices get lost, and they hold customer addresses and sometimes personal data, so apply mobile controls for local storage, authentication and network traffic, such as those in the OWASP Mobile Application Security Verification Standard, and manage devices centrally.

Integration determines whether the portal actually closes the loop to billing and inventory. Parts consumed on a job should reduce stock, and completed labour and materials should reach receivables with the right prices and contract entitlements. Use supported interfaces such as Oracle Integration's ERP adapter, which handles REST APIs and business events, so regular Oracle updates do not break custom connections, and decide which steps must be real time and which can run in batches. Adoption is judged in the field: technicians compare taps per job with the paper or spreadsheet they used before, so test with them early.