Dynamics 365 Field Service : Configure 3D asset models

Imagine a field technician arriving at a complex site—say a wind turbine or an industrial HVAC system. Wouldn’t it be more efficient if they could visualize the asset in 3D, see how parts are connected, identify components, and even simulate a repair before physically touching the asset?

That's exactly what 3D asset modeling in Dynamics 365 Field Service offers.

With this feature, organizations can enhance remote support, field technician productivity, training, and maintenance planning using interactive 3D models linked to real-world assets.

What Are 3D Asset Models?

In Dynamics 365 Field Service, a 3D asset model is a digital twin—a virtual, interactive representation of a physical asset. These models:

  • Provide contextual visualization of machines or infrastructure.
  • Allow technicians to click on parts, view maintenance logs, and trigger workflows directly from the model.
  • Enable remote assistance and guided work instructions.

Prerequisites

Before configuring 3D models, ensure:

  •  You have access to Dynamics 365 Field Service.
  •  Microsoft Dynamics 365 Remote Assist or Guides is optionally available.
  •  The Mixed Reality (MR) solution is installed from AppSource.
  •  Your 3D model is in GLB (GL Transmission Format Binary) format.

Step-by-Step: How to Configure 3D Asset Models

 Step 1: Install the Mixed Reality Solution

1. Go to Power Platform Admin Center.

2. Choose the environment.

3. Open Dynamics 365 Apps.

4. Install Dynamics 365 Remote Assist Integration or Dynamics 365 Guides.

This solution includes entities and features required for 3D visualization.

Step 2: Upload the 3D Model

1. Go to Make.PowerApps.com.

2. Navigate to Assets > 3D Models.

3. Select New.

4. Upload your .glb file.

5. Fill out metadata (Model Name, Description, Version).

⚠️ Note: Ensure your GLB model is optimized (under 50 MB for web performance).

Step 3: Link 3D Models to Customer Assets

After uploading the model:

1. Go to Customer Assets in Dynamics 365 Field Service.

2. Open or create an asset record (e.g., Generator, HVAC).

3. Set the 3D Model field to reference your uploaded model.

4. Optionally configure:

  • Model Anchors: Identify parts inside the model (e.g., "Fuel Pump").
  • Hotspots: Define clickable zones that trigger actions (open a form, show a checklist).

Step 4: Test and View the Model

1. Go to the Field Service mobile app or HoloLens.

2. Open a work order or asset tied to the model.

3. Click View 3D Model.

4. Interact:

  • Rotate/Zoom/Pan.
  • Click on components.
  • View component info or trigger inspections/workflows.

 Bonus: Automate with Power Automate

You can also trigger workflows from model interactions. For example:

 When a technician clicks on a “Replace Filter” hotspot:

  • Start a Power Automate flow to create a part order.
  • Update the service task status.

Best Practices

  •  Keep models lightweight and optimized for mobile.
  •  Use meaningful anchors and naming conventions.
  •  Test extensively on real devices (phones, tablets, HoloLens).
  •  Use security roles to control who can upload or modify 3D models.

Final Thoughts

By integrating 3D models with Dynamics 365 Field Service, companies can modernize how field service is delivered—reducing downtime, enhancing training, and improving first-time fix rates.

In the era of digital transformation, 3D asset modeling bridges the physical and digital worlds, empowering technicians to be smarter, faster, and more accurate in the field.

Comments

Post a Comment

Popular posts from this blog

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

Connecting the Dots: FetchXML and Web API Integration in Dataverse

Image
 In Dataverse, FetchXML and the Web API are two powerful mechanisms for retrieving data and interacting with entities. Here's a brief overview of each and how they can be integrated: 1.    FetchXML :      -   Definition:   FetchXML is a proprietary query language used in Microsoft Dynamics 365 and Dataverse for querying data from entities.    -   Usage:   FetchXML queries can be used to retrieve data based on complex criteria, perform aggregations, and filter records.    -   Features:   FetchXML supports various query expressions, including conditions, sorting, grouping, and aggregation functions.    -   Integration:   FetchXML queries can be executed programmatically using client-side scripting, server-side code, or through tools like the Dynamics 365 Web API. 2.    Web API :      -   Definition:  ...
Read more