About Revit Family (NAH) Project Family Management Annotation - - PowerPoint PPT Presentation

about revit family nah project family management
SMART_READER_LITE
LIVE PREVIEW

About Revit Family (NAH) Project Family Management Annotation - - PowerPoint PPT Presentation

About Revit Family (NAH) Project Family Management Annotation Family System Family Contractual & non-contractual Family Nested Family Family Data Family Graphic Family Controllability Family Library Annotation


slide-1
SLIDE 1

About Revit Family (NAH)

slide-2
SLIDE 2

Project Family Management

  • Annotation Family
  • System Family
  • Contractual & non-contractual Family
  • Nested Family

Family Data Family Graphic Family Controllability Family Library

slide-3
SLIDE 3

Annotation Family

  • Fit for designer’s favor.
  • Allow some freedom otherwise people use Text and Line.
  • When to use Text and Generic Annotation?
  • Use multi-category tag
  • Nested annotation in some cases
slide-4
SLIDE 4

Annotation Family

  • To visualize information
  • Mind the tags for linked objects, especially frequent file

exchange is needed

slide-5
SLIDE 5

System Family

  • Template/Library file for standard transferring
  • All people can damage the family types
slide-6
SLIDE 6

System Family

  • Fix rogue families/types asap, because

they will be spread

slide-7
SLIDE 7

Contractual & non-contractual Family

  • Identify them by shared parameter
  • Mind the LOD for contractual family
slide-8
SLIDE 8

Contractual & non-contractual Family

  • Need to count the families by rooms,

please mind the family location point

  • or linkup families and their rooms by

shared parameters

slide-9
SLIDE 9

Nested Family

  • Shared or not shared?
  • Which part of the component should be

nested?

  • Nested family in nested family? One more

layer of family to be taken care

slide-10
SLIDE 10

Family Data

  • Data only follow the last loaded family, please always update the library

right after modifying family in project file, and use only one centralized library.

For instance, someone change the lift data, but another colleague

  • verride it by loading from the outdated library.
  • Maintain data consistency, may do it externally
  • Data may be updated from time to time and changed massively
  • Better to maintain only one set of shared parameter, so that families can

be circulated among other projects

  • Change of parameters may bring data loss
slide-11
SLIDE 11
slide-12
SLIDE 12

New Families to be proceeded New Material Code Other data to be synchronized

“Data.ImportExcel”

slide-13
SLIDE 13

Family Graphic

  • To fit architect’s favor
  • Nature of family category (there are 35 or so reasons why

a building element will not show on your view) Generic Model vs Specialty Equipment

slide-14
SLIDE 14

Family Graphic

  • Use Subcategory
  • Use Detail level
  • Use Detail Item
slide-15
SLIDE 15

Family Graphic

  • Just the right among of things
slide-16
SLIDE 16

Family Controllability

  • Got enough thought, information & knowledge for new family
slide-17
SLIDE 17

Family Controllability

  • Got enough thought, information &

knowledge for new family

  • To provide many but not too many buttons,

think about what to be controlled first

slide-18
SLIDE 18

Family Controllability

  • Better not to use line based family, hard to

control in heavy file

  • Mind the data groups, parameters are first

come first served in project file

  • Define as invisible before creating new

parameter for visibility Control

slide-19
SLIDE 19

Family Library (make a wish)

  • Cloud based library with fast interaction
  • Easy operation on Revit working window

Like, Pop-up notification for updating library right after modifying a family; List of misaligned families compare to the library

  • Parameters on cloud

Batch add shared/non-shared parameters to chosen families before download