This field shows the type of preventive maintenance that must be executed.
Select this check box to indicate that the notification involves a failure that has caused the object to stop working.
This field can be used, for example, when you have given a customer a guarantee that a machine will be functional 98% of the time. You can then use the Object standstill field to track when and how long the machine has not been functional due to a failure. By referring to the Object standstill, Notification date and time and Date concluded fields, you can calculate the uptime percentage of the object.
When you enter the object while entering a service notification, the correct service contract and contract version will be retrieved automatically. This retrieval function uses a fixed search path.
When you enter a service notification for a particular object, Isah will check a search path to find the contract and contract version applicable to this object. The software will first of all check whether the object itself is valid. If it is not, a warning will be displayed, but you can still continue if you want. The search path is checked as follows:
Based on the object, the notification date and the customer (if found), the service contract and the version are determined.
If a service contract and a version have been found, the program determines the latest date and time on which work should be started in order to resolve the failure.
This field shows the type of service contract. There are two possible contract types:
|
Service contracts of the 'Contract' type serve as an umbrella contract for contract versions in which you record object-specific contract conditions for a customer. |
|
Service contracts of the 'General terms and conditions' type are used to define general terms and conditions for an object group. You can define general service conditions regarding response time, availability of engineers, call-out charges, rates, etcetera. A contract of the 'General terms and conditions' type can have underlying service contract versions, but these contract versions do not allow you to register any specific objects to which the contract version applies. This means that you cannot register preventive maintenance or an invoicing schedule either. Service contracts with general terms and conditions can be linked to object groups on the Object groups form. |
The status identifies the stage of the service notification, for example 'Dealt with' for notifications that have been resolved. When creating service orders from service notifications, you can specify that orders should be created only from service notifications that have a particular status or higher.
This field automatically shows the last possible date on which the work required to resolve the failure must be started. The value in this field is calculated automatically based on the conditions found in the service contract version.
See also Calculation of latest start time in a service notification.
When you enter a service notification, the software will automatically calculate the time the work should be started at the latest. The program uses the values of the Response time and Availability fields (Service module, Service contracts, Versions button, Conditions tab). Factors in the calculation are:
Example of latest start time in a notification:
Situation 1
Response time: |
24 hours |
Availability: |
From 08:00 to 18:00 hrs |
|
Not at weekends |
|
Nights are counted, weekends are not |
Date and time of notification: |
Thursday 16:00 hrs |
Latest start date and time |
Friday 16:00 hrs |
Situation 2
Response time: |
24 hours |
Availability: |
From 08:00 to 18:00 hrs |
|
Not at weekends |
|
Nights and weekends are counted |
Date and time of notification: |
Friday 16:00 hrs |
Latest start date and time |
Monday 16:00 hrs |
Situation 3
Response time: |
24 hours |
Availability: |
From 08:00 to 18:00 hrs |
|
Not at weekends |
|
Nights and weekends are counted |
Date and time of notification: |
Friday 16:00 hrs |
Latest start date and time |
Monday 08:00 hrs |
As soon as you enter an object during a service notification registration, the customer will be looked up automatically. This customer is the customer specified in the object settings, or if no customer was specified there, in an object at a higher level of the as-built structure of the object.
You can also enter the customer yourself. The field is not required. You might be talking to someone who bought your product through a dealer. Manual entry will not register this person in your customer records, however.
If a service notification results in a service order, a customer must be entered.
If a notification relates to more than one customer, click the Related customers button to register these customers as well.
This is the person responsible for the management of the service notification.