That is a strange table format. What happens if there is a need for more than 3 technicians for a task?
Anyway, in this case I would probably load the table in three load statements (Since the table structure is the same, these three tables will automatically be concatenated into one table in your datamodel):
Task, Tech1 as Tech, Tech1Hours as Hours
Task, Tech2 as Tech, Tech2Hours as Hours
Task, Tech3 as Tech, Tech3Hours as Hours
Then it'll be easy to create charts and calculating the total time spent for each tech.
Sorry for the delay in my response, you gave me a good idea however I had to do some research.
To provide more insight in regards to the table format, I have to say that we are managing the process in MS SharePoint so I am exporting to the table to Access and then doing an ODBC with Qlikview. I really don't want to mess up with the SP process at this point so ... I had to found a way to work with that "particular" table.
Going back to the solution I used "Concatenate":
Task, 1st Tech-ID as Tech, 1st Tech-Hrs as Hours
Task. 2nd Tech-ID as Tech, 2nd Teck-Hrs as Hours
Task. 3rd Tech-ID as Tech, 3rd Teck-Hrs as Hours