Blog

I am going to discuss about the various views on the Field Service Schedule Board.

Lets get’s started.

View Configuration Options:

1) There is one default schedule board for the organisation.

2) Additional public and private schedule boards can be created and modified.

3) Views are tied to Dynamics 365 views that can be customized

Customizing the Schedule Board:

Items are populated on Schedule Board based on Dynamics 365 views

Views associated with the following entities:
> Resource Requirements
> Bookable Resources
> Organizational Units
> Booking Alerts

Default filters and view settings can be defined per view

Web resources can be created to define custom booking rules and can be added to board.

Once scheduled board is opened on the right hand side we can see the “Initial Public View” and “+” sign, if we need to create a schedule board for someone or specific people then click on the “+” sign and it will open new pop up window where we can configure accordingly.

The main use of the multiple Schedule boards is that if the Schedule manager looks after different regions then he can check the tabs to move into different views quite easily.

I hope this helps:

For Microsoft Dynamics 365 Consultancy/Training/Support/Licensing
Contact us: https://www.gmritsolutions.co.uk
Email: admin@gmritsolutions.co.uk

I am going to discuss what is included in the Field Services Schedule Board

Let’s gets started.

Schedule Board:

Drag and drop interface for scheduling and rescheduling.

Filter by Resource Type, Services etc..

Scheduler settings allow configuration of dispatcher time zone, grouping etc.

Booking Requirements:

Unscheduled items are displayed at the bottom of the schedule board in booking requirements.

Will display all unscheduled requirements for any entity that has been enabled for the universal scheduling.

Predefined view for unscheduled work orders is included as part of the Field Service Solution

Additional requirement views can be defined to provide a more customized scheduling environment.

Integrated Map:

Helps  determine best resource for job based on proximity.

Each resource is color coded for easy identification.

Routes are created and updated as resources are assigned jobs.

Today i am going to discuss about the connected field services, Communication and Integration with IoT Devices.

Connected Field Service
1. IOT Solution installed on top of Dynamics 365
2. Key benefits of Connected Field Service.

Reduce downtime with proactive alerts from connected devices
Address issues faster by remotely monitoring devices and keeping  customers in the loop.
Reduce maintenance costs by dispatching a technician with the right expertise, availability, and location to the job.

This feature was added in the December 2016 update for Microsoft Dynamics 365 and is only available for online.

Pre – Requisites:
1. Dynamics 365 for Field Service solution installed with appropriate licensing.
2. O365 Global Administrator or Dynamics 365 System Administrator credentials.
3. An active Azure subscription.

Connected Field Services Architecture:

Go to Market place and search for Connected Field Services and install the app and configure with your Azure subscriptions and with Power BI.

Once the Internet of Things(IoT) is installed on your Dynamics 365, there are connected devices:
IoT Alerts
Commands
Registered Devices
Device Categories
Registration History

How these are connected with Field Services is via Customer assets.

All the Registered Devices are present in the customer assets record.

When the new customer assets is created then in the record you need to fill in device Id  and save the record, Click on the Register device then from the Azure subscription the device id is fetched.

Thing to consider around Communication using Field Service

Most Implementations will require some type of communication
Examples of communications scenarios
1. Automated voice or SMS notifications to technicians when a they are scheduled
2. Customer notification based booking status changes
3.Travel status notifications

A variety of built in and external tools can be used to facilitate internal and external communication in Field Service.

Using third party utilities you can use like Microsoft Flow or Twilio for communication purposes.

Scenarios:
Workflow that send status updates via SMS
Workflow that would auto create resource requirement records for schedule board enabled entities.
Custom Action to define custom imput and output parameters that will be used to initiate plugin, workflows etc..
Auto creation of invoices when a Work Order is closed and posted.

Solution:
There is Twilio Solution that allows software developers with custom code makes and receive phone calls and send receive text messages using its web service APIs.

Twilio has a Dynamics 365 Solution that can be installed into an organisation (Requires a Twilio Account)

You can download from below link:
https://www.microsoft.com/en-gb/download/details.aspx?id=53586

Glympse Integration:

Provide a real-time notification to techs and customers
Notification sent through SMS or email
Uses GPS location in Field Service mobile application
Can be configured for voice messages
Available through App Source

Full example below  image illustration: