When you manually schedule several bookings, it should still be possible to calculate the travel time. You should have a right-click option on the booking (in the schedule board) which calculates the travel time from the preceeding booking, or the Resource start location if this is the 1st booking for the day. The system should then ask whether the booking should be moved so there is no gap between the prior booking and start of travel for the current booking. Alternatively, the second action could also be a separate right-click option.
The option to re-calculate travel times for all bookings for that day for a specific resource in one operation should also be available, Similarly it should be possible to abut all bookings for the day for that resource. This could be achieved by right-click actions on the white space or anywhere on the board for that day and resource.
The above applies to the hours view.
Customer Assets may change over time. They may be upgraded and become a different product, other field may change, they could move accounts so their external id changes etc. Currently if you look at any Work Order/Incident, it shows you the current asset data. So if you look at an old call and the asset has changed since, you get an incorrect picture. If you re-print a service report it will also show incorrect asset information.
This ought to be changed so that the WO and Incident reflects the asset at the time the call is taken. Reports should also use this data instead of current data. This is a standard feature in other FS systems.
Ideally an Asset's change history, including account and agreement moves etc, should be stored separately and accessible from the Asset record.
Ability to have multiple visits/resource bookings for a single work order to be carried out consecutively, not at the same time. i.e. An Installation Work Order which requires 3 bookings: a. Initial Site Survey, b. The installation visit, c. a Quality control visit. The structure to define these can be achieved via a Requirement Group template - they need to have a requirement each. However they must not be booked for the same time as they happen consecutively. When you book each of them, you need to also see the other related requirements.