
Design Table for WBS

Hi One consultan, I have a Database with some tables, ones of them are correspond with the structure of the project WBS Work Breakdown Structure I have four level.
Level 1 Project, Level 2 Area, Level 3 Subarea, and Level 4 Subtistem in each box Level are asociated documents by disciplines.
Now I Link Each level to documents 1 to Many Level 1 to Documents, Level 2 to Documents etc.
I don't sure if is the best options I trie too related Level 1, to Level 2 to Level 3 and Level 4 but these option is complicated.
Some Alternative help
I send image example
-
It might be more helpful if you described a particular issue you are trying to solve that got you thinking about the relationships between your tables?
Rafael Sanchis said:
Now I Link Each level to documents 1 to Many Level 1 to Documents, Level 2 to Documents etc.
I don't sure if is the best options I trie too related Level 1, to Level 2 to Level 3 and Level 4 but these option is complicated.Maybe explain further here what you were trying to do.
-
That is my DB is one for Project.
Tablet Project 1 to Many to the 4 WBS
I have 4 tablets WBS relations 1 to Many to the table Documents (can have 2000 Docs easy) example one discipline can have Many document the Table Activities is Link Many to Many to Documents
Tablet Disciplines 1 to Many to Documents,
Tablet Activities Many to Many Documents
The other tablets are Client 1 to Many to Project
Responsibility 1 to Disciplines
Milestones and CutoffDate to Documents 1 to 1
The table Documents have a lot of info like Earned Hours for Planed, Real and same for each Disciplines.
-
My initial thoughts are that 3 of the 4 WBS tables are not needed as separate tables but as data points for each document. I guess maybe WBS Project could be a table. My feeling here is that Area, SubArea, and SubSystem are more fields for a record in Documents. One record in documents needs to hold data on which WBS Area, SubArea, and SubSystem they belong to.
To me the basic data set you have is a Project or WBS Project that has many documents. Can one record in documents belong to multiple WBS Project? WBS Area? WBS SubArea? WBS SubSystem?
What separates Project from WBS Project? Can 1 Project have multiple WBS Projects?
-
Here you can see the WBS Area have 6 diferent areas and in each area there are different Documents with different disciplines. The same for the Subarea and Subsystem.
The WBS Area, Subarea and subsystem working as Work packages each have your document hours, and progress.
It's not ease explain, my English is not good and the DB is complicated
Thanks again.
-
Fred
Hi FredI, I need cutoff every friday to know the earned hours, in the first graphic in the week 9 I earned 1.848 and in the week 10 I earned 924 hours but the problem is sum week 9 and 10 and need see the hours week by week.
Explain something.
I have a Datadate that I change every friday these days automatic copy in one field on all document and depend the Milestoneassociated to each the document and win the hours. Example if I have a document with 100 hours, and that win the second Milestone 45%, the document win 45 hours same for all document Now I have 4 Milestone for each documents(5% 45% 75% and 100%).
-
Just a thought:
Rafael Sanchis said:
I have a Datadate that I change every fridaySo the field 'Datadate' changes every friday and all the fields in the picture for week 9 - 15 use the same field. If that is true then my guess is that you would lose the ability to do week 9 when you change the date to week 10.
Going over your pictures, it looks like you just have 1 field that tracks hours and that is why you need to keep changing 'Datadate'. You need a way to track hours by date for each document so you can figure out how many hours are spent during each week or month or year.
Take a look at my sample DB, I have created the spentHours table. Since I am tracking a specific date to a specific hour I can now figure out what is done during any time period. So it would look something like:
sum((select documents).spentHours[week = 9].Hours)
I have attached an updated DB that has a dashboard that looks at week 10 and 11 (the weeks I have in my DB).