rsharp
2005-11-28, 07:54 PM
If someone asked you, how is the best way to implement Revit on a large project with a team of inexperienced people, what would you say?
I've been rattling this around in my head over the week-end and I thought this might be an interesting subject for this forum.
What I came up with was is something like this:
First, there are (3) major divisions in the project scope as pertains to Revit. We have to deal with the 3-d model. We have to document that model, and we have to assign BIM parameters to as many building elements as possible.
Let's say that our project is a 1,000,000 sq.ft. of combined use that are broken up into (2) major structures and several peripheral small buildings.
Is it that important that every team member is introduced to the (3) major divisions of the Revit system at the same time? For example, could some team members that are focusing on the BIM programing enter the Revit experience from that point of introduction? Couldn't we set up members of the team who are doing the documentation to to be introduced to the 2-d documentation portion of the tools first. And then comes the modeling. We introduce Revit at this level to those doing the Modeling and not focus so much on the other two divisions at first.
You notice I didn't include rendering. I am assuming that our firm outsources this function and we are going to export out 3-d dwg's or 2-d hidden line perspectives to our Renderer.
It's not that our Revit team should stay pigeon holed like this through the life of our project. Naturally crossing over these lines by team members would be necessary.Certain team members would emerge from their particular focus and naturally cross these lines.
The thing is, I'm not so sure that the way to introduce Revit to your support staff is to give them a little book and show them how to make a little building. Some autocad draftspersons are going to respond to the 2-d tools more readily if that is there point of introduction. I don't know if any of us are fully comprehending the depth of detail we need to go to achieve this BIM thing. Some members of the team might be quite inspired to be set out to see what we can do with Revit from the BIM perspective.
This is simply throwing out some ideas. I'm very interested in knowing what experience others have had on this subject.
I've been rattling this around in my head over the week-end and I thought this might be an interesting subject for this forum.
What I came up with was is something like this:
First, there are (3) major divisions in the project scope as pertains to Revit. We have to deal with the 3-d model. We have to document that model, and we have to assign BIM parameters to as many building elements as possible.
Let's say that our project is a 1,000,000 sq.ft. of combined use that are broken up into (2) major structures and several peripheral small buildings.
Is it that important that every team member is introduced to the (3) major divisions of the Revit system at the same time? For example, could some team members that are focusing on the BIM programing enter the Revit experience from that point of introduction? Couldn't we set up members of the team who are doing the documentation to to be introduced to the 2-d documentation portion of the tools first. And then comes the modeling. We introduce Revit at this level to those doing the Modeling and not focus so much on the other two divisions at first.
You notice I didn't include rendering. I am assuming that our firm outsources this function and we are going to export out 3-d dwg's or 2-d hidden line perspectives to our Renderer.
It's not that our Revit team should stay pigeon holed like this through the life of our project. Naturally crossing over these lines by team members would be necessary.Certain team members would emerge from their particular focus and naturally cross these lines.
The thing is, I'm not so sure that the way to introduce Revit to your support staff is to give them a little book and show them how to make a little building. Some autocad draftspersons are going to respond to the 2-d tools more readily if that is there point of introduction. I don't know if any of us are fully comprehending the depth of detail we need to go to achieve this BIM thing. Some members of the team might be quite inspired to be set out to see what we can do with Revit from the BIM perspective.
This is simply throwing out some ideas. I'm very interested in knowing what experience others have had on this subject.