Couple of things happening here. Initial impression may be that these two need to be performance managed (they don't sound inspiring!), however it's worth checking whether the 'direction' from above actually matches the real business needs of the organisation - which means understanding the role they are filling and the nature of the work that they are handling. Even if you know that management wants them 'out' it's worth knowing what the impact on your work areas is going to be - and it's always worth 'going through the hoops' to do these things properly.
Sometimes (sometimes) folk who appear to be 'doing nothing much' are actually performing 'hidden' tasks that aren't in their 'job description' and are actually doing something that requires a good deal of sophisticated job knowledge and skill and which (and this is important) adds value to the company. Even within a team who all share the same 'job description' some individuals may have (informally) taken on 'special' responsibilities. The final 'kicker' here is that the individual may not realize they're 'doing this special function' and isn't necessarily going to look more eager, or intelligent than any of their colleagues. Now one of the ways to 'discover' these 'extra angles' is to move the folk out and see what stops working, but depending on the nature of your business it's sometimes good to know 'up front'.
So that's the conceptual groundwork, start with the job and don't assume you really understand what's going on in the job. Then move on to the man/woman. So then, when you do start talking to the individual your understanding of the job gives you solid metrics to measure and assess them against - and a reference point to start discussions about their strengths and weaknesses. Straight-forward stuff..
How best to understand what's going on in the job? Well the activity-timesheet is indicative but suffers from two big failings. Firstly: your people may not fill it out accurately for reasons of laziness, sabotage or overwork. Secondly: if you are collecting information about 'categories' of work, if you leave out a category (possibly one of those 'invisible' functions these guys perform), then you don't get to collect information on that category. Going to folk 'who used to work in that job' to get their views (and to 'endorse' the activity-timesheet design) might help. However they aren't necessarily going to know what job mix the current occupants are doing, and likely suffer from a prejudice common in (the lower ranks of) IT, that anyone below them 'in the ladder' is less 'clever' and less hard working (something which every real manager learns is not true).
Frankly, if you can afford the time, I'd recommend sitting in their chair for a shift, or ideally two. They might find it 'difficult' or resent it, but you simply paint it as 'the way' that you get to understand and appreciate the WORK they do (whatever that might be). From that perspective you might see that they are doing a lot of 'soft' work (such as customer 'soothing', or little research jobs for folks - or running a repair business on the side..).
So then you are in a better position to design the activity-sheet sheet (because sitting in on a shift or two wont give you a total understanding of the volume of workflows that MIGHT be important to you). At the same time, however, you are now able to 'speak the language' of the specific job, and talk to the two guys about their performance against metrics using very specific (and appropriate) terms and examples. You have ALSO been able to observe them 'close up' for a period of time, and you might discover they have 'hidden' talents that the organisation needs somewhere (and depending on how you feel about them at this stage you might discover they are 'needed' a very long way away from you indeed...).
There's a bonus (but not for the faint hearted). While you are 'playing' at being the helpdesk operator (or whatever) it's a chance to put your deputy in YOUR job and observe his/her performance from below. Normally when whoever does that job fills in for you while you are on vacation or off sick. You get to see the aftermath of their occupancy (and it might always 'look good'), but you NEVER get to see them 'in the job'. By having them in the job while you're still there means you get a chance to experience them 'being your boss' - admittedly for only a brief period, but it can be extra-ordinarily enlightening. Not only of course might you observe that your deputy does things that irritate, but you might observe things that they do very well (better than you in fact..). In which case you can (very quietly) 'adopt' some of their management style (if it works for you).
That's just a few quick thoughts. Just one more though - document every step. Even if things seem to be progressing smoothly towards a satisfactory outcome, if things get derailed it helps to be able to produce a documentary record of all of the steps along the way. Just to show that you were doing things 'by the book' (and kill any arguments about 'who did/said what').
Cheers, Tban/Rosearch.