TM1 Task Logger
Posted: Fri Jan 06, 2012 5:49 am
Hi All
I have build a TM1 Task logger for our TM1 team which will capture every task raised by the TM1 user. The purpose of this model is to keep a track of every task/issue raised by the user. I have mentioned the overview and some additional add-ons of the model below
Wondering if anyone has done a similar model like this? If yes, then I would love to hear about their model architecture.
For this model I have 3 major cubes - Task Input, Task ReOpen and Task Report. Also I have got System Info and Validation cubes.
Regards,
Sameer Syed
Overview of TM1 Task Logger:
• TM1 Web front end
• When users add/create a task, then email notification goes to the user and the tm1 mail box - that a task has been created
• When the assigner (TM1 project manager) assign a task to one of his team member, then a mail goes out to the user and the tm1 mail box - that the task has been assigned to a tm1 member
• When the task is fixed then again a mail goes out to the user and the tm1 mail box – task is fixed
• When the user sign off then again a mail goes out to the user and the tm1 mail box – task is completed
• Users will be able attach any document from TM1 Web – e.g. screen shot of an issue
Additional Add-Ons:
• If a task is not assigned to a TM1 Developer then an automatic reminder mail comes out once in every 2 days (Mostly to the TM1 Project Manager)
• Every Morning a report comes out to show how many tasks were raised yesterday, how many were closed, which developer is completing or closing the maximum tasks on that day. And also high level numbers of how many tasks still opened
• If a task is not completed within 5 days from the date it was assigned (and not from the date it was raised), then a remainder mail goes to the USER and also to the developer
• Validation on the input templates – Task can’t be created by a user without filling out the mandatory fields
• If a Task is re-opened by the user (which means the developer has not fixed the task as expected by the user), then the model will capture the new date, time and description of the user. And once the developer fixes the task then again the new date, time and description of the developer is captured. So say if the task is re-opened 10 times, then the model will capture the date, time and description every time the task was re-opened (All the 10 lines).
• Drill functionality – If the cell says 5 tasks raised today – Right click and drill will give details of every task. And again if the re-opened measure says 5, then once again drill on that cell will give the information of re-opened details.
• Number of days a task took = Date Closed – Date Assigned
• Various reports – By Username, by Status, by Environment, by Severity, by Weekday, by Location, by Time, by Developer, by Date Raised, by Date Assigned, by Date Fixed and by Date Closed,
I have build a TM1 Task logger for our TM1 team which will capture every task raised by the TM1 user. The purpose of this model is to keep a track of every task/issue raised by the user. I have mentioned the overview and some additional add-ons of the model below
Wondering if anyone has done a similar model like this? If yes, then I would love to hear about their model architecture.
For this model I have 3 major cubes - Task Input, Task ReOpen and Task Report. Also I have got System Info and Validation cubes.
Regards,
Sameer Syed
Overview of TM1 Task Logger:
• TM1 Web front end
• When users add/create a task, then email notification goes to the user and the tm1 mail box - that a task has been created
• When the assigner (TM1 project manager) assign a task to one of his team member, then a mail goes out to the user and the tm1 mail box - that the task has been assigned to a tm1 member
• When the task is fixed then again a mail goes out to the user and the tm1 mail box – task is fixed
• When the user sign off then again a mail goes out to the user and the tm1 mail box – task is completed
• Users will be able attach any document from TM1 Web – e.g. screen shot of an issue
Additional Add-Ons:
• If a task is not assigned to a TM1 Developer then an automatic reminder mail comes out once in every 2 days (Mostly to the TM1 Project Manager)
• Every Morning a report comes out to show how many tasks were raised yesterday, how many were closed, which developer is completing or closing the maximum tasks on that day. And also high level numbers of how many tasks still opened
• If a task is not completed within 5 days from the date it was assigned (and not from the date it was raised), then a remainder mail goes to the USER and also to the developer
• Validation on the input templates – Task can’t be created by a user without filling out the mandatory fields
• If a Task is re-opened by the user (which means the developer has not fixed the task as expected by the user), then the model will capture the new date, time and description of the user. And once the developer fixes the task then again the new date, time and description of the developer is captured. So say if the task is re-opened 10 times, then the model will capture the date, time and description every time the task was re-opened (All the 10 lines).
• Drill functionality – If the cell says 5 tasks raised today – Right click and drill will give details of every task. And again if the re-opened measure says 5, then once again drill on that cell will give the information of re-opened details.
• Number of days a task took = Date Closed – Date Assigned
• Various reports – By Username, by Status, by Environment, by Severity, by Weekday, by Location, by Time, by Developer, by Date Raised, by Date Assigned, by Date Fixed and by Date Closed,