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
-
Sucefull Excelent Fred appreciate a lot your help. -
Hi Rafael Sanchis
Are you trying to manage a project or the documents related to a project? Ninox has a Projects DB template that you many want to look at to see if it might be a good start.
-
I need manage a documents for each level of the WBS and control the Hour of each document associated a each box in the WBS.
Each lebel have documents and hour for documents for each box and the sum of all documents give me the total progress project
-
I the image the first 4 tablets are the WBS, the second is Area WBS and I have 6 脕reas each Area have the associate products by Disciplina.
The Subarea WBS have 4 diferent Subarea with diferents Documents assiciate a each subareas
-
Ninox Projects DB template is too simple
-
Sounds like your DB is doing what you want. What are you trying to do now that you need help with?
-
Fred Yes Fr茅d is doing what I want only the idea is there are something more to optimazed the relation between tablets.
Many thanks
-
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.
-
Rafael Sanchis I appreciate that your DB is complicated. It looks like you have spent a good deal of time and effort building it to a place where it is working for you. You asked for opinions so I have offered one. It does mean a redesign and a new way of approaching your data. My suggestions would be able to handle 6 Areas or 100 Area and any combination of SubAreas and SubSystem.
That is why I asked if there was something specific you wanted to achieve. So maybe we can help figure out something that works within your current structure.
-
Fred
My feeling here is that Area, SubArea, and SubSystem are more fields for a record in Documents.
Ok Fred, I'm going to take some time to review this alternative. What worries me is that of I create these fields in Documents I will be repeat a lot of same information in the fields for each area, subarea or subsystem.
If I understood correctly.
-
Rafael Sanchis I'm not sure what you mean by
Rafael Sanchis said:
repeat a lot of same information in the fields for each area, subarea or subsystem.How I envision it is that the document table has an Area, SubArea, and SubSystem field. Then a record in the document table would have a name then would select the appropriate number (1.1, 2.2, 3.4, etc) for each one. Unless one document can be associated with multiple Areas, SubAreas, SubSystems. Is that possible?
-
Fred Good morning.
That is my WBS I can have many Documents for each level
Example
Evaluaci贸n t茅cnica Ofertas de accesorios de tuber铆as soldados a tope. PR-AR-OM-10-xxx
PR Project
AR Area
OM Ocemi Macolla
10 Disciplina
XXX # Document
-
1) it looks like a document can only belong to 1 Gerencia or 1 Area or 1 Sub Area or 1 Subsytem never all at the same time. So you wouldn't even need to have 3 separate fields, or 4 if you include Gerencia. You could create a field called MainCategory where you would choose Gerencia, Area, Sub Area, Subsystem. Then another field called subCategory where you would choose one of the sub categories of the 4 main categories, i.e. PMT or Oleoducto. Then you can have a formula field that puts together the mainCategory, subCategory, then have Ninox add a number to the xx part and show a final document ID.
2) Can a document belong to multiple projects?
-
Fred
1) it looks like a document can only belong to 1 Gerencia or 1 Area or 1 Sub Area or 1 Subsytem never all at the same time.
Yes is correct
MainCategory where you would choose Gerencia, Area, Sub Area, Subsystem.
Excelent God idea I try implement that in other project
Can a document belong to multiple projects?
No I have one Project in one database
Thank a lot Fred, when implement your idea contact you again
Regards for now
-
Fred
You said something like that.
-
@Rafael Sanchis that is something that I had in mind.
here is a quick mock up of what it could look like. there is no project table since each DB is a project. I've added a spentHours table to track when you read a document and the hours spent reading it.
-
Fred Whommm excelent you help me a lot appreciate yor time thanks again
-
Rafael Sanchis Fred
Excelent Fred work excelent only need eliminate the Project Table
I need consult you about Formula that not working is Posible ?
-
-
What separates Project from WBS Project? Can 1 Project have multiple WBS Projects?
The project need multiples WBS yes
-
Of course. Ask away.
im not replying directly to your response as now our thread is so hard to follow. If I did.
-
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).
