Friday, June 10, 2011

RTC USA & J... Ah, What's The Program Doc?

The following (quoted text) is an excerpt from one of the upcoming RTC USA classes I am presenting... More to follow... Follow the RTC, that is!!!

These images illustrate but 2 of the many kinds of Planning & Programmatic projects possible. Using Revit as the main production tool; we created a scenario where immediate program validation & design verification was possible and sometimes actually FUN!!!

 "...Before anything we must formulate a road-map to ensure predictable results, inclusive of most of our needs.

The common road-map for any project is: Assess / Devise / Generate / Validate.

Assess The type of project will dictate what approach is used and there are many possible approaches. Herein we will look at several project types: TI and Office, Urban Planning and Client specific projects; in your approach define the scope of the project, based on client program, practice needs, etc. Generate a topology to capture thoughts and ideas, as these will most likely fluctuate so having good process documentation is paramount to train & communicate to colleagues and others.

Devise (Plan) your needs, keeping the end result in mind; “Will this become an office standard, will it need 3D review or simply 2D and Informational” and on and on. Sketch out what the components and results want to look like –a sort of cartoon set of components and sheet design, etc. At the end of this document is included a simple but useful 2 page “Family Planning” document that I use to sketch out & help formulate and plan families, designs and so forth; this way when I get to the actual creation phase I have a good understanding of the items necessary and have a kind of blueprint for blueprints, as it were.

Generate or Create: Need I say more? Well, I will… This is the time to begin to create the families, key schedules, schedules, parameters (shared & or project), design options and any other components that were deemed necessary in the assessment and planning phases. The suggested workflow is to create prototypes for each individual object, outside of any ‘official’ template first, so validation can be accomplished without creating havoc in final template files.

Best Practice: PROTOTYPE FIRST; whenever creating any family, etc.

Validate. The QA & QC phase. Flex all families in both the family editor as well as in a proxy project, again before bringing them into any prospective project or template. Test all other components & schedules, etc. we only want completely functional and tested objects into Revit®..."

Hope to see you (t)here!!!

Images courtesy: Gensler

No comments:

Post a Comment