Blog

Today i am going to share some information on how the Microsoft Dynamics 365 for Field Service Work Order Life Cycle.

What is the process to follow to complete the Work Order.

So let’s gets started.

Work Orders:- Work Order is a task to be completed for a Billing Account on Field Service.
so the main points to be remembered as follow:

-Capture essence of what needs to be performed.
-Used to coordinate and schedule resources and activities
-Can be used for different types of work such as installations, repairs, or preventatives maintenance.

Information of issue or work to be performed
– Description of issue or work to be performed
-Customer/Service Account
– Location
– Product (parts) and services that may be needed
– Tasks  or steps to Follow
– Priority and estimated duration
– Skills needed.

Work Order Life Cycle: The below are the steps in the Work Order Processing:

Work Order Creation -> Schedule -> Dispatch -> Service -> Review/Approval
what happens:
– New Work Order created
-Assigned incidents, products, services, Etc.

Who Performs:
-Agreements: Auto generated, or recurring
-Case:
-Opportunity
-Manual

Work Order Status:
-Open – unscheduled

Booking Status:
N/A

SCHEDULE:

What Happens:
– Bookable resource booking created
-Resources assigned
-Date and time specified

Who Performs:
– Dispatch(manually)
– Field Agent (Manually or Mobile)
– Dispatcher with help of scheduling assistant

Work Order Status:
– Open -Scheduled

Booking Status:
– Scheduled.

DISPATCH:

What Happens: 
-Field Agent notified of Work Oder.

Who Performs:
– Notification sent by system to Field Agent, Customer, or Others

Work Order Status:
– Open – scheduled

Booking Status:
– Scheduled
– (Custom Status)

SERVICE

What Happens:
– Work Order carried out
Who Performs:
– Field Agent

Work Order Status:
– Open – In Progress > Open – Completed

Booking Status:
– Travelling
– In Progress Completed.

REVIEW/APPROVAL

What Happens:
– Work done and information is accurate

Who Performs:
– Supervisor/Manager
– Back office accounting

Work Order Status:
– Open – Completed > Closed – Posted

Booking Status:
– Completed

I hope this helps.

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

Let me share some information about the Universal Scheduling in Field Service.

Allows scheduling non Field Service & Project Service Automation entities using the schedule board.

Provide visibility to those entities through the schedule assistant, and with resource scheduling optimization functionality.

Example:
Enable the opportunity entity to schedule technicians as technical sales consultants for sales opportunities.
Enable a custom entity that is used for additional services, and consulting items.

Universal Scheduling:

Depending on installed solutions, work orders and projects will be enabled for universal scheduling.
Additional entities will need to be enabled for scheduling through resource scheduling.
– Relationships between the entity with the Resource Bookings and Recruitment Entities will need to be defined.(Can be auto-created)

– You will need to publish you customization’s before the functionality is enabled for that entity.
-Once published, you can map specific information from entities to specific fields for entities that are enabled for scheduling.

Let’s see this in action from Dynamics 365 Field Service.

Login to Dynamics 365 > Resource Scheduling > Administration > Enable Resource Scheduling for Entities.

Then new window will pop’s up and you need to select an  entity you want to enable in scheduled board.

By default the system have all the Field Service entities are enabled and for instance you want to enable “Opportunity” entity.

Let’s see in action

Click on the “Enable Resource Scheduling for Entities..

In the above image “Opportunity” entity has been selected and Booking Relationship & Requirement Relationship like OnetoMany is automatically created by the system once you select the “create new relationship” and click on the “Publish Customization”.

In order to utilise the Opportunity entity double click on the Opportunity entity from the above image – enabled entities.

As you can see from the above image in order to use the “Opportunity” entity on the Field Service Scheduled board you need to configure the “Booking Status Field Logical Name” = “msdn_fieldservicestatus”.

Also the settings and Attribute mapping area needs to configured as how the Booking status needs to shown on the system related to Opportunity.

The Attribute Mapping is where the date from and to should be mapped with each from Opportunity and Field Service entity, also there are other attribute mappings for example if you enable the latitude and longitude on Opportunity then that should be mapped on the “Attribute Mapping” area.

so go ahead and click on the save button.

Now go back to the Opportunity entity on the “Sales “area on the Dynamics 365 and create new “Opportunity” record.

Once the new opportunity record created and click on the associated records of the opportunity down arrow:

It will create quick create of resource requirement:

What it will does is, it will create a resource schedule on the schedule board.

Lets go back to the schedule board and see the opportunity on the unscheduled items.

Now you can simply drag the Opportunity from the unscheduled booking area to the scheduled board where required according to the time and date.

Also  instead of seeing all the unscheduled booking of opportunity on  “open requirements”, you can create a new view on the Opportunity and utilize here on the scheduled board as new tab near the “Unscheduled Work Orders”.

I hope this helps.

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

Hi Everyone

Let’s discuss about the Purchasing phase in Microsoft Dynamics 365 for Field Service.

As the resources are in the field and perform operation and then eventually you need to raise the Purchase Order, Probably we need some additional products delivery from additional vendors,

 so we can stock your warehouse and make sure we have appropriate stock available based upon may be current jobs that are executing or future jobs that will be coming through down the pipeline as we move forward.

 The purchase order process from a Field Service standpoint has kind of three step process that you are going to be working with the first situation is you have to really requisition what are the products that you want to work with by creating a PO record inside the application.

When you create PO record we can do several different things around defining the specifics on what work order that PO is going to be associated with, how we are going to ship or drop ship that information,

what warehouse that inventory may be received into but as we define the specifics around the purchase order itself, then we are able to go in and gain approval.

Used to request and receive products from vendors to stock warehouses.

Purchase order process
 > Request products from vendor by creating a PO.
 > Gain approval.
> Document receipt of products by creating PO receipt.

Let’s see this in action.

Go to Dynamics 365 > Field Service >

Click on  “Purchase Order” and create new Purchase Order record.
Fill the from which vendor the products coming, fill the purchase order date and work order.

By default the System status is in draft, Fill the Purchase Order Date.

Vendor details, in the general section the delivery date expected ship to, payment term, ship via, receive to warehouse.

Work Order section fill the work order details and booking.

Also the User information of who requested.

In the business process flow approval & submit purchase order status should be changed to “Approved” and “Submitted”.

Once the Purchase Order as been created then create the associated Receipt record
Name of the receipt, received by, ship via and save record

then lookup the associated receipt product:

Finally you can see the Purchase order receipt product below image.