If you would rather have your information vertically underneath each material, instead of using note blocks to create a schedule, you can create a generic annotation family that looks like a mini schedule for each material. You can enter in the information here, or by selecting the generic annotations themselves and editing the type properties. For this particular method, each finish designation is a different type in the family, so that the symbol can be placed in actual views (typically interior elevations). Just remember that once you create the parameter, you can’t change its type (text, integer, number, area, etc.)Īll of these symbols are placed in a working drafting view so that they will appear in the schedule. These are mainly text parameters but can be whatever you desire. The generic annotation family has custom family parameters for all of the fields desired in the schedule. This symbol can be placed on drawings to show specific finishes if desired, but it is “dumb” in that it is not a tag that is pulling information from the finish but instead a dumb symbol. In this method, a generic annotation family is created with parameters for each of the columns that are required in a material schedule. Demo notes – when you don’t want to use keynotes for some reasonĮxample – Material Schedule – 2 ways Material Schedule – Small Symbol.Material schedule (because the industry is just not there yet with using a material takeoff schedule).You can have both working and printing versions of the schedule.With a key schedule, as you make parameters for your schedule, you are adding those to the actual family category you picked for your dummy schedule, which is typically a category that you wouldn’t use in your project, so they are completely unrelated. These parameters can be type or instance. Can create your own custom parameters that only exist inside the generic annotation object, and those parameters can appear in both the schedule AND the annotation itself.If you use a dummy key schedule, you are just adding/removing lines. If you remove/add one of those objects (generic annotations) this is automatically reflected in the schedule.Scheduling actual objects (generic annotations) in your model is a good double-check and provides a graphic representation of your scheduled element.It is better to create a generic annotation family and schedule that via a note block than create a “dummy” key schedule because of the following: You are scheduling actual objects and you can create an object just for that particular schedule. Note block schedules are a great way to create a “dummy” schedule because they are not actually dumb. Welcome to Part 4, where I will be explaining the wonderful world of Note Block schedules, and how you can use them to create “dummy” schedules in your projects in a way that’s much better than using a key schedule.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |