lais efstathiadis
Sab, 28/02/2015 - 17:29
The main idea for this work was to create a Brise-Soleil made of wood segments that, by changing the angle of each one, could creat a smooth movement that reminds of a curve.
First part: create the wood segment.
Open a new family GENERIC MODEL FACE BASED and draw an extrusion on the view ELEVATION FRONT.
Add 2 parameters: LUNGHEZZA and ANGOLO. The parameter ANGOLO is the key parameter to create the movement of the Brise.
After drawing the extrusion, create different types of segments that variates on the angle:
Second part: create the aluminium structure.
Open another family GENERIC MODEL FACE BASED to create the basis structure of each segment of the brise and draw an EXTRUSION on the view ELEVATION FRONT.
Creat the parameters LUNGHEZZA, SPESSORE e BRACCIO.
Its also necessary to make a void on the extrusion that is going to be the fit for the wood segment:
Part 3: open a new mother family on GENERIC MODEL FACE BASED to join the 2 segments of the brise. In this part i joined the different angle wood segments with the aluminium structures.
With this structure you can create different shapes and draws.
Alicia de la Torre
Sab, 28/02/2015 - 11:54
Dopo l'idea di partenza che, effettivamente era troppo modulare, ho cercato di tradurrla in chiave parametrica.
I pezzi elementari saranno assemblati (ancora devo pensare il meccanismo), una vicino all'altra seguendo una generatriz lineare o di rivoluzione.
Variazione nella longitudine dei pezzi triangolari superiori che lanciano ombra.
Variazione anche nei pezzi inferiori di supporto, in longitudine ed orientazione secondo la funzione ad albergare: supporto pubblicitario o seduta.
Nicola Moscheni
Ven, 27/02/2015 - 05:27
Buildings (=components) = Data
In parametric desing every single element it's a data collector. I don't draw, I model. I don't simulate reality, I see it in different view.
In this post I want to collect data from the OTEKA project. First of all I Load OTEKA family in a new project (with a floor, since it's a Metric model floor based, you see...reality, nothing flies). I have five OTEKA on the floor, with different dimensions (instance parameters of the family).
I need to make the order for the purchase of the furnitures and I want to do that with only one phone call to my supplier. I just need to provide him a list of components.
To prepare the list, or better the Schedule and I need Shared Parameters to do that.
In the family OTEKA I change the Family Parameters in Shared Parameters (Family Type> choose the parameter > Edit > change in Shared Parameter). I create a Shared Parameter File, a text file with all the information the project needs to share data. Inside it, there is a Parameter Group called "Dimensions" that contains "S_side1", "S_side2", "S_shelf_height" (S is for Shared). Remember to re-load the family in the project.
Now, it's time to share components' entity and properties.
First of all I need to check the nested families of OTEKA are "Shared". Inside the Family Category panel I flag the "Shared" cell. By this way, families and types become shared data. (check also the Family Category to make order in your project, I choose Furniture category).
Now, I want also some parameters of the families become Shared ones. Like before I have to change the parameters, but inside my previous sharing file I add a new Group "components". The group contains the wooden beam's length for example.
And now an example for Cost scheduling. Imagine you want to now the Total Cost of all the joints are present in the project. But joints, in this case are different types, so I need to generate a Type Parameter about cost. In the Family Types panel I add a shared (type) parameter "SjointCOST". The value changes according to every joint type. After that, I make the "Cost" parameter in "Identity Data" equal to "SjointCOST".
Notice: "Identity data" are type parameters so you can equal only type parameters!
Schedule creation
In "View" panel there is the Schedule tab. View, interesting. The schedule it's another way to SEE the project. Data are part of the components, sometimes an easier way to manage elements and informations that can really change the project. For example, if you modify a dimension in the schedule, it will change for "real" also in the project.
1- Choose the Category for the Schedule, the same choosen for the families.
2- Select the Fields. "Family and Type" shows all the components. "Count" calculates the the quantities. "Cost" insert the price of the elements, when available in the family/material properties. You can also Add Parameters (from the shared ones).
3- Insert a "Calculated Value". For example to know the Total Cost of elements. In Formula you can add a parameter.
4- Sort the field to order and group them. Flag "Gran Totals" to calculate total quantities. Unflag "Itemize every instance" to group equal components.
5- Format the fields to change names, to change scale units, to add symbols. For "Total Cost" flag "Calculate Totals".
The schedule is ready.
This is the easy list I can use for my phone order. If you want to do that for me, see the excel attachment exported from the schedule.
Ven, 27/02/2015 - 08:48
Nicola Moscheni
Ven, 27/02/2015 - 01:35
This is the modelling procee of OTEKA: a shelf sytem, with parametric dimensions, made of steel angular joints and wooden linear beam. This will be the mother family. Inside OTEKA family there will be two nested families: joint+beam.
NB: In this post I don't explain how to model. For basic tips about modelling you can see my previous post. Here you can find the difference between Type and Instance parameters, how to use Family Types, how to manage nested families, how to use formulas for parameters, how to organise YES/NO parameter with Visibility properties.
NM_wood milled beam.rfa
The linear components of my shelf system are wooden beams with two milled ends, inserts for the joint. Let's see the model.
"beam_section" is a Type parameter: the section of the element is decided "before", I buy this elements with defined sections, I choose one of them, the most appropriate for my project.
"length" is a Instance parameter (default): I can cut an element (with a defined section) with different lengths. Also, this parameter allows to modify the dimension whem I load this family elsewhere.
About the milling parameters, they referes to a Void Forms and they are Instances because I can adjust them to different joints.
IMPORTANT: Type and Instance are strongly different. The first one is about standard, defined data. Restricted informations. The second one is a variable condition. It's up to you decide how to go through this issue. Often, it's easy to figure out with this thinking about components' production/construction or their use in the project. You can find the element in defined conditions? Or you can customize it? You can adapt your component according to the situation? Or it has to adapt to other ones?
If you have to buy this component you have to consider the supplier has this wooden elements with a maximum length. So I modelled this component using a formula for the length parameter. "lenght_calc" is the instance parameter assigned to the global dimension of the element. The value is ruled by a conditional formula IF. "lengthmax" and "lengthmin" are the two reporting paramters I set up to be the limitation for "length", the "typing" parameter. The IF formula has a scheme =IF(<condition>, <true>, <false>). According to my model, if "length" value is smaller than "lengthmax", "lenght_calc" will take the same. If not, "lenght_calc" will take the "lengthmax" value.
So, the formula is =IF(length>lengthmax, lengthmax, length)
By this way the length of the element never exceed of maximum value I set up (and OTEKA's maximum dimensions will do the same).
NM_steeljoint.rfa
The dimensions are Instances because I can adjust the joint to different elements.
The steel joint is designed as a modular spatial connection with different configurations (the family types).
Using Family Type means to give different values to every Type Parameter depending on the different configuration and "save" them.
I decided to use a YES/NO parameter assigned to the Visibility property of the elements. First, add the type parameter in the family. Then, assign this parameter to "Visible" in the Properties panel of the selected element.
Using different type YES/NO parameters and assigning them to the different elements visibility properties I provide the different Joint Types. Respectively O, T, E, K, A joints.
The flagged parameter means YES, so visible. Unflagged means NO, so non-visible. For example, the K joint has one non-visible element (so the corresponding parameter is unflagged). The E joint has two non-visible elements (so the corresponding two parameters are unflagged).
Notice: when you this property in Family Template, you see every "non-visible" element with light grey edges, but when you Load the family elsewhere you will see only visible elements.
Done! Now it's time nesting time. Now place the two components in the mother family and model the global system.
NM_Oteka.rfa
In this case I used two different joints (E, K). To choose the joints, I can select the Family Types by clicking them in the Properties panel. And I can modify them whenever I want. The elements (the joints and the beams) are aligned with different Reference Plans.
The dimension Instance parameters (assigned to the plans' distances) rule the two sides of the shelf system and the distance of the different levels.
Sp, that's it. Now I have my brand new parametric shelf system. And you too! Check out the attachments below.
Ven, 27/02/2015 - 03:26
laura.vellucci
Mer, 25/02/2015 - 15:03
I thought to add 4 bedrooms in the ovest side of the tower. They share the Kitchen and two bathroom.In the east side there are two apartment that share the kitchen; they can become a unique appartment simply opening the doors.
