Why are there two separate columns for WBS and ID in project task list?
- What is the purpose of having ID when there is WBS and vice versa?
- I updated few tasks as 100% completed but they are still showing in my ERP home page. Why are they still there?
- Do I have to upload documents inside task page or in project?
WBS and ID are no way replacement of each other. Both have their separate relevance and importance. WBS or Work Breakdown Structure number in associated with the schedule of the individual project. It follows a hierarchy numbering like xx.xx.xx up to n levels, though between two and three levels are considered sufficient for small to large project. WBS can keep changing until the last stage of the project as per revision in the task arrangement. Even in a project same task can have different WBS number in different baselines. In Tuhund you have drag and drop option too to restructure WBS. Moreover, if you are entering schedule in bulk using excel upload, system will preserve WBS structure and numbering, unless a some task is missing. On the other hand, ID is fixed. When you add a task, whatever way that is, system will assign task ID and that will stay the ID of the task unless you delete the task. ID is unique across the projects and is the ultimate unique identifier. This is even more critical for an elaborate system like Tuhund and each task has relations with accounts, resources, material and so on. Assume, you have attributed some expense on a task and assume we had taken WBS as unique identifier together with project ID. Assume there was a revision in the schedule and WBS number changed. That would have an effect on financial transaction. Visualize a manager gets a notification to approve an expense on WBS #2.3.15 and by the time he logs in to take an action, WBS has changed and some other task is 2.3.15. Of course, if he drills down, he will reach the correct task, but there are good chances he might skip that take a wrong decision. All this cannot happen when we refer tasks with an ID outside project.
Issue # 2: You have updated your task as 100% completed, but it is still showing in your task list. It will keep showing till project manager or an authorized user (for whom the default title in Tuhund is Project Engineer) verifies task completion. They can verify one task at a time, they can verify number of tasks in one go, or they can verify a summary task to verify all subtasks in hierarchy.
Issue #3: A document uploaded at a task level is automatically a project document. Therefore, if the document is relevant to only the specific task, then please upload it in the task. Otherwise, please upload it at project level. If a document is relevant to a few specific tasks but would not be ideal to show at project level since it is irrelevant for all other tasks, there is a trick to upload once and keep one copy with links in multiple tasks. Upload such a document to your shoebox and import wherever it is relevant. Finally you can delete it from shoebox. It will stay where you have imported and go away only from shoebox. This is applicable everywhere in Tuhund, not just in Project Management Module. Another advantage using shoebox is that it is much simpler and faster. For instance, your you mobile phone you can just share the document with Tuhund Mobile App. You do not have to select anything. Document, pictures or any other files will automatically upload to your shoebox.
Thank you. That clarifies a lot.
How many baselines can we save?
In Tuhund, by default you can save up to 3 + 1 = 4 baselines. In can be extended up to 20. For a large project it is normal to have 3 to 4 baselines. If more than that is needed, then there is a likelihood you are either not doing something right or you are over doing.