Video Screencast Help

Engineer Roaster in SD 7.5

Created: 11 Jul 2013 • Updated: 26 Aug 2013 | 6 comments
This issue has been solved. See solution.

Hi All

Can we make Engineer Weekly or Monthly roaster in Service Desk 7.5

Operating Systems:

Comments 6 CommentsJump to latest comment

Lark's picture

Hi there - can you give more explanation about what you are trying to do?

vikas1101's picture

Hi Lark

We are looking below requirement to be fullfill in Service Desk 7.5

1) Timesheet or roaster management feature to track engineers attendance 

2) In timesheet, supervisor should be able to allocate shifts to engineers

3) Sign in and sign out option should be available for the engineers to mark their attendance

4) Engineer attendance report

jbrown's picture

Sound do able, but it would take multiple custom projects to monitor the database, create integration that stores the information, a management web form and report.

Lark's picture

ServiceDesk is primarily for Incident Management, Change Management and Problem Management.  So its primarily a tool that your engineers would use while on shifts - not to manage the shifts themselves.

jbrown is quite right that it would certainly be possible to create a series of workflow projects that could provide shift roster management but I'm not sure this would be worth the effort.  You'd be better to find an "off the shelf" piece of software to do this.

Having said all that, if you don't have the budget and don't have the time to learn/build with workflow then you could partially achieve your requirements using the Change Module.  Having a supervisor schedule each engineers shift as a change would:

  1. Give each engineer an implementation task at the start of their shift to let them record attendance, make notes and close at the end of their shift.  Making a comment when they start and closing when they finish would give a record they were present.
  2. Show the shifts (as changes) in the calendar (even use multiple schdules or colours to show different engineers)
  3. Allow delegation or re-assignment of implementation tasks to other engineers if they were swapping shifts or away sick
  4. Report on completed changes (shifts), upcoming changes (shifts) etc
  5. If engineers were also responsible for implementing changes then you could potentially see who was on-shift at the time of the change to plan accordingly.

I think there would be too much manual effort to maintain this so its definitely NOT my recommendation - I just like thinking about how you could possibly use existing tools to do something new.

vikas1101's picture

Hi Lark

Thanks for your valuable response.

Lark's picture

Hi CBZ9104 you are most welcome.  If I answered your question could you please mark my answer as the solution?