Operations and facility management Case study

Fieldo: field work orders and communication app

Fieldo, a cloud service with iOS and Android apps and a web portal where managers plan projects, workers log time, expenses and materials, and customers follow status and costs.

The fieldo.se home page: Digitalize your work orders, a mobile planning and journal service for contractors and service companies
Fieldo: field work orders and communication app: app screen
Client
Fieldo
Service
Web apps, Mobile apps, Integrations
Years
2013–2016 (3 years)
Stack
iOS, Android, MySQL, PHP and 12 more
Platforms
iOS, Android, Web

Overview

Fieldo is a mobile planning and journal service for contractors and service companies whose staff work in the field. Managers create and assign projects in a web portal; workers use the iOS and Android apps to follow the work plan and log time, expenses and materials; customers see the status and cost of their own projects; and economists get overviews of projects, spending and logs. The service runs in English, Norwegian and Swedish and connects to accounting and subscription systems. We built the web application, the web services behind the apps, and the iOS and Android apps between 2013 and 2016, and fieldo.se is still online.

The challenge

The office, the people in the field and the customer all need the same picture of a job: what was agreed, who is doing what, and what time and material it has used. Keeping that in sync by phone and paper is slow, so the product had to put it in one place on web and mobile.

What we built

  1. A web portal for managers with project creation and cloning, project templates, task lists, worker assignment and a calendar with leave
  2. Worker apps for iOS and Android: work plan, floor plans, time, expense and material logging, and messages inside the work plan
  3. A customer view with project details, invoices and ratings, so customers can follow status and costs
  4. Overviews for economists across projects, expenses and logs, with reports on time, travel and material expenses exported to Excel and PDF
  5. Web services and APIs between the apps and the web back end, including notifications and location services
  6. Google Calendar and mapping integrations for events and location plotting
  7. Integrations with AppDirect for subscriptions, Fortnox for accounting and Visma for business management
  8. English, Norwegian and Swedish language support and built-in user guides
  9. EDI features for Android and SFTP folder connectivity, and New Relic performance monitoring
  10. Testing and bug fixing across web, iOS and Android, including translation and browser compatibility

How a system like this fits together

Reference architecture: field work-order and communication platform

Simplified reference architecture, not a client schematic.

Reference architecture: field work-order and communication platformZones from left to right: clients (the manager web portal and the worker and customer apps), the application (one PHP application with web portals and a mobile API), data (MySQL) and background jobs (scheduled jobs), and third-party services (push services, Fortnox and Visma, and AppDirect). Full description in the numbered list below the diagram.ClientsApplicationDataBackground jobs (async)Third-party servicesweb pagesJSON / XMLread / writerunpushaccountingsubscription eventsManager portaljQuery, Bootstrap,DataTablesMobile appsWorker, customer:iOS and AndroidPHP applicationWeb portals, mobile API,reports and exportsMySQLProjects, workers, logs,customers, expensesScheduled jobsPHP cron, PHPMailere-mailPush servicesApple and GooglenotificationsFortnox, VismaAccounting and invoicingintegrationsAppDirectMarketplace subscriptionsReference architecture: field work-order and communication platformZones from left to right: clients (the manager web portal and the worker and customer apps), the application (one PHP application with web portals and a mobile API), data (MySQL) and background jobs (scheduled jobs), and third-party services (push services, Fortnox and Visma, and AppDirect). Full description in the numbered list below the diagram.ClientsApplicationDataBackground jobs (async)Third-party servicesweb pages, JSONread / writerunpushaccountingsubscription eventsManager portaljQuery, Bootstrap,DataTablesMobile appsWorker, customer:iOS and AndroidPHP applicationWeb portals, mobile API,reports and exportsMySQLProjects, workers, logs,customers, expensesScheduled jobsPHP cron, PHPMailere-mailPush servicesApple and GooglenotificationsFortnox, VismaAccounting and invoicingAppDirectMarketplace subscriptions
A PHP application serves the manager web portal and the mobile API for the iOS and Android apps, stores everything in MySQL, sends push notifications, and connects to Fortnox, Visma eAccounting and AppDirect.
  1. A manager plans the work in the web portal: customers, projects, templates, task lists and worker assignments, all served by the PHP application.
  2. Workers and customers use the iOS and Android apps, which call the mobile API in the same PHP application for projects, calendar, time, material and travel logs, notes and ratings (JSON and XML).
  3. Projects, workers, customers and every time and expense log are stored in MySQL; scheduled PHP jobs and PHPMailer e-mail run alongside.
  4. The application sends push notifications to the apps through the Apple and Google push services.
  5. Customer and invoice data goes to the accounting systems (Fortnox and Visma eAccounting), and AppDirect sends subscription events back to the application.

Technology used

Technology named in the project records, by layer
LayerChoicePurpose
MobileiOS and Android appsworker and customer apps
DataMySQLprojects, workers, customers and logs
WebPHP, jQuery, Bootstrap, DataTablesmanager, company, customer and admin portals
APIPHP endpoints returning JSON and XMLmobile app back end
Notifications and emailPush notifications, PHPMailerpush to the apps and e-mail
IntegrationsFortnox, Visma eAccounting, AppDirect, Google Maps, Google Calendaraccounting, subscriptions, locations and events
ReportingFPDF, Excel exportPDF and Excel reports
MonitoringNew Relicperformance monitoring

What happened next

  • Delivered

    The work described above was delivered to the client.

  • Operational facts
    • Our work on this project spanned 2013–2016.
    • It was maintained and extended over 3 years.

Screens

Fieldo: field work orders and communication app: app screen
Fieldo: field work orders and communication app: app screen

Could this be your project?

Request similar work

Questions about this project

How long did this project take?

Our work on it ran from 2013 to 2016.

What technology was used?

iOS, Android, MySQL, PHP, PHPMailer, Google Maps, DataTables, FPDF, Push notifications, Google Calendar, Fortnox, Visma eAccounting, AppDirect, New Relic, Bootstrap, jQuery.

Was it maintained and extended over time?

Yes. Our work on this project was maintained and extended over 3 years, from 2013 to 2016.

Similar work

My Taxi Ride: taxi dispatch and booking platform screenshot

Also iOS and Android, same industry

My Taxi Ride: taxi dispatch and booking platform

  • Logistics and transport
  • Operations and facility management
  • Mobile apps
  • Web apps
  • Integrations

2013–2016

Passenger and driver apps for iOS and Android, a dispatch admin panel with reporting, APIs, SIP calling and the public website for the My Taxi Ride dispatch system, built over four years.

GoAquatix: aquatic workforce management platform screenshot

Also iOS and Android, same industry

GoAquatix: aquatic workforce management platform

  • Operations and facility management
  • Business software and compliance
  • Web apps
  • Mobile apps

2019–2025

A MEAN-stack web app and iOS/Android apps for field-staff scheduling, duty and incident reports, water-safety testing, repair requests, training and hiring across aquatic facilities, built and maintained for six years.

SchoolWiki app designs: the home menu, events and newsletters

Also iOS and Android, also a web app

SchoolWiki: school communication app for parents and staff

  • Education
  • Web apps
  • Mobile apps
  • Integrations

2015–2018

SchoolWiki, a school communication platform: web API, parent site and iOS/Android apps for events, notices, messages, newsletters and absence reports, with a setup wizard.

Building something similar?

Tell us what you need and your industry. We will tell you what is realistic, what it would take, and show you the closest work we have done.

Are you ready to partner with us?

Our good-natured team is waiting to hear your business requirements.

Book a free project call