Mitarbeiter mit Tablet und Schutzhelm nutzt Microsoft Dynamics 365 zur Produktionssteuerung.

Case Study

Our Role: Project Management

Our client

Polifilm GmbH

04/2024 – 02/2025

The customer originally planned to replace a self-developed Excel-based maintenance solution with Microsoft Dynamics 365 Business Central. However, during the process analysis, it was recognized that MS Dynamics 365 Field Service already offers a specialized module for mapping maintenance – including mobile order processing, automatic scheduling, and technician control.

Following this, the project strategy was adapted: Business Central remained the leading ERP system (e.g., for warehousing, purchasing, invoicing), while operational maintenance and incident management were outsourced to D365 Field Service. A bidirectional interface was designed between the two systems to automatically exchange data such as spare parts consumption, working hours, and costs.

Initial Situation | Objectives

  • Previously, maintenance planning was done via manually maintained Excel spreadsheets.
  • No system-supported ticketing, no mobile processing, no evaluation
  • Planned replacement by Business Central failed due to functional limitations
  • Goal: Introduction of a professional, mobile-usable maintenance system
  • Integration with Business Central for Material Flow, Postings, and Cost Transfers

Duties | Responsibilities

  • Analysis of Excel-Based Maintenance Processes (Reactive/Preventive)
  • Creation of a target concept in Business Central and Fit/Gap analysis
  • Decision Paper and Architecture Design for Field Service + BC Integration
  • Implementing Dynamics 365 Field Service
  • Setup of Work Orders, Technician Planning, Escalation Logic
  • Design and Testing of the Bidirectional Interface to BC
  • Training of technical and IT users, change management
  • Project management and coordination of external service providers

Key areas:

  • Process recording of previous Excel maintenance
  • Creation of a Target Concept for Replacement Processes in BC
  • Identification of Limitations in BC and Selection of D365 Field Service as a Better Solution
  • Joint architecture planning for the integration of both systems
  • Introduction of Field Service including Work Orders, Mobile Apps & Resource Scheduling
  • Interface structure BC ↔ Field Service (e.g., spare parts, bookings, expenses)
  • Training & Change Management for Technical and IT Teams

Technologies & Methods

  • Dynamics 365 Field Service (Power Platform, Dataverse)
  • Dynamics 365 Business Central (ERP Features, Warehouse & Purchasing)
  • Power Automate, Azure Logic Apps for System Integration
  • Field Service Mobile App (incl. Offline Mode)
  • Project Methodology: Phased Rollout with Pilot Scheme at the Main Plant

Project Management

Results

Weidehoff Business Solutions

  • Complete replacement of the error-prone Excel solution
  • Mobile, system-supported maintenance with photo, scan, and signature functions
  • Complete data flow between Field Service and Business Central
  • Reducing unplanned equipment downtime through faster response times
  • Demonstrable improvement in technician scheduling efficiency (−25 % idle times)