Submitting Job Reports on Windows Mobile 6.5

During the era of Windows Mobile 6.5, field service technicians relied on rugged enterprise handhelds to log job details, capture customer signatures, and transmit reports back to central dispatch systems. This process relied on specialized mobile client applications built on the .NET Compact Framework, offline-capable relational databases, and wireless data connections via cellular networks, local Wi-Fi, or physical docking cradles.

Dedicated Field Service Software

Workers did not submit reports via standard web browsers or standard email. Instead, enterprises deployed purpose-built mobile applications developed specifically for the Windows Embedded Handheld and Windows Mobile platforms. These programs—often built using Microsoft Visual Studio and the .NET Compact Framework (C# or VB.NET)—provided structured digital forms tailored to field workflows.

Technicians used a resistive touchscreen and stylus to navigate forms, select diagnostic codes, input parts used, record labor hours, and capture customer signatures directly on the screen.

Local Data Storage (Store-and-Forward)

Because cellular coverage was inconsistent in industrial and remote locations, applications utilized a "store-and-forward" architecture:

  • Local Database: Applications saved completed reports to an embedded database running directly on the device, typically Microsoft SQL Server Compact Edition (SQL CE).
  • Queuing: When a worker tapped "Submit," the report was marked as pending in the local queue, ensuring no data was lost if the device was out of range.
  • Synchronization: As soon as an active data connection was detected, a background service initiated data transmission without requiring manual intervention from the technician.

Data Transmission Methods

Windows Mobile 6.5 handhelds supported three primary methods for transmitting completed job data back to corporate enterprise resource planning (ERP) or customer relationship management (CRM) systems:

  1. Cellular Networks (WWAN): Devices equipped with integrated SIM cards (utilizing GPRS, EDGE, or 3G HSPA) established packet-data connections. The mobile client packaged the report into lightweight XML or SOAP payloads and sent it securely over HTTP or HTTPS to an external-facing corporate web service.
  2. Wi-Fi Hotspots (WLAN): In facilities with wireless infrastructure, devices connected using 802.11b/g protocols to sync directly over the company’s local network or through a secure virtual private network (VPN).
  3. Cradle Synchronization (Batch Mode): For units without active data plans, technicians placed the handheld into an office docking cradle connected via USB or serial cables. The connection utilized Microsoft ActiveSync (on Windows XP) or Windows Mobile Device Center (on Windows Vista and 7) alongside database replication tools, such as Microsoft SQL Server Remote Data Access (RDA) or Merge Replication, to push the stored data to the central database.

Attachments and Peripherals

Submitting a report often required supplemental data captured by the device's hardware:

  • Barcode Scanning: Integrated 1D/2D laser scanners captured serial numbers of installed equipment and automatically inserted the text into report fields.
  • Digital Signatures: Touch-drawn customer signatures were rasterized into small monochrome or 8-bit image formats (such as BMP or PNG) and either serialized into the XML report payload or transmitted as separate binary attachments.
  • Photos: Handhelds equipped with low-resolution rear cameras allowed technicians to attach proof-of-work images, which were compressed on the device before transmission to minimize bandwidth usage over slow 2G and 3G networks.