Graphical Equipment builder
The Service object record can be created in different ways and one of them is the Graphical Object Builder (GOB). With the GOB new structures can be made manually based upon pre-defined setup from the Service Object Family. The GOB can also be used to make adjustments on existing Objects in a controlled and structured way.
Service Object Families
Default setup which will be available for all objects of a specific type can be determined on the Service object family record. On this record information like Active Service schedules and Active Service orders can be stored, but also defaults regarding estimate hours and spare parts when a service call is performed by an engineer.
Service Object Customer information
A service object can have multiple customer accounts associated which are used in different processes of Service Management. On the Service object a Contract Holder, End user, and Owner can be setup. It can also holdAlso default information about the primary contact person.
When equipment is sold to a customer, Warranty terms can be made active for this ore multiple object(s). It will be visible on the Service Object if warranty is still applicable. Service Management will automatically check the warranty on Call creation and the service activity will be free of charge if warranty is still applicable.
Service Order History
The full-service history is directly available from the Service object. Information about both closed and open work orders is shown here.
Financial Cockpit view
The Cockpit view on Service object level displays all financial transactions and Service Management enables monitoring and managing objects through all phases of the object life cycle. With the Cockpit view, businesses are better informed regarding purchases, repairs, and overhauls throughout the entire life cycle. They also are up to speed on the total cost of maintaining an object, as well as margins.
Service order resource requirements
Some Service Objects need special resource skills when maintenance is performed. These requirements can be stored and determined via the Resource requirements at Service Object level. When a service call is planned on an object with resource requirements the graphical planboard will take this into consideration automatically.
Service object address information
Address information can be stored on the Service object, this is, of course, important, because he Service calls will get this address automatically assigned and this is the location where the engineer is sent to. The address information can also be shown on a map view when Dynamics Software Service Management is used.
Service object attachments
Attachments can be stored on the service object, which could contain valuable input for the service process. Documents like: pictures, BOM`s, a spare parts list and much more can be associated with the object.
An Equipment list record can automatically be created if an item is sold via a Sales order. With this record, the link between the Sales order, the Serial number and the ship date will always be in place. The shipment date is particularly important because this is normally the Warranty start date for the Object