Work Management
To obtain the benefits of the Work Management module:
- Create a process for each user and configure the required daily operation time. We recommend you to add a photo of the person for each process.
- Configure the time statuses in order to generate the work calendar. Please take into account that you should configure correctly the classes of the statuses:
- Labour periods will be the real time minus the times of statuses marked with classes weekends or holidays. However, the scheduler will consider, in the future, as labour time the real time minus the times of statuses marked with classes weekends, holidays, external dependencies and breaks.
- The system will consider as worked the total time of the statuses marked with the productive class. This is useful, for example, to consider the brunch inside of the labour day, by marking this status as class productive.
- The system reads weekends and holidays from the calendar (planned statuses) and not from the statuses window, therefore you should not allow users to insert or justify weekends and holidays. On the other side, the system reads vacations from the statuses window and therefore you should allow users to insert or justify their vacations.
Now, according to this flow diagram:
- Train and make the working team:
- Create the tasks from edit schedule (step 1 in diagram).
- Ask for them to be scheduled, from the change status button, so that the supervisors receive an automatic notification (step 2) to check the times, finish dates, and characteristics, after which the supervisors can schedule (step 3), with the same change status button, the task so the worker will receive a notification (step 4) and may begin working on them.
- Start (step 5) the tasks and insert the advancement of results (step 6) for them.
- Justify the not productive statuses (step 7) when the system requires it due to not having input a status, or failing to input sufficient results.
- Prefinalize the tasks (step 8) when they are finished, which will generate and send an automatic notification (step 9) to the supervisors so they may check the quality (step 10) of the results of the given task.
- Supervisors should report low quality results (step 11), when they have been detected in the tests before finalizing a task. An objective and easy way of doing this is by giving the maximum possible detail based on subtasks, gathering these subtasks in a document which is linked to the edinn task or order as an URL, and in the quality evaluation performed by the supervisor, he/she will insert the % of no quality based on the subtasks of the task or order that were not completed successfully.
- Supervisors must then finalize the tasks (step 13) after reviewing the quality of results, which will generate an automatic notification to the worker (step 14); or, return the tasks to the scheduled (step 12) state so their colleagues may continue working on them until reaching the desired results.
- Visualize or receive alerts:
- Projects or tasks that are going to be delayed or have already been delayed.
- Personnel which should:
- Report results.
- Justify their time spent working.
- Perform periodic tasks or procedures.
- Other.
- Obtain reports:
- Indicators of personnel performance, including an adapted OEE:
- Availability: percentage of completion of their designated work hours.
- Velocity: percentage of completion of tasks within their designated deadline.
- Quality: percentage of high quality results compared to all given results.
- Projects and pending tasks, to whom they are assigned, anticipated deadline and completion dates, the state of each one, percentage of advancement, etc.
- Total time dedicated per project and task:
- Clic on the records to see the detail in time in Status\Status.
- To know what was done in detail, clic on the records to see the detail in Status\Status and then switch to the Results\Results report, type the "To order" field with the same task code that is present in the "From order", mark show fields and then view report.
Note: in the previous reports, to have the detail of what was done in each task, you have 2 options:
- Each task performed should have a separated task into the system. Additionally, to be able to know the total hours of the project, all tasks belonging to the same project should belong to the same area.
- If you use a generic task to include different real tasks, this task should include a result with a field of description mandatory if empty.