====== Welcome to parametric design! ====== ===== People ===== * [[user:Helena Johnsson]] * Examiner * Lecturer in Timber Structures, LTU * [[user:Marcus Sandberg]] * Tutor * Researcher at Timber Structures and Functional Product Development, LTU * [[user:Thomas Wingate]] * Tutor * Currently visiting scholar at Stanford ====== Course overview ===== ===== Background and goal ===== * Background * Effective construction design is characterized by standardization and reuse. * ‘Operative landscape‘ * Creating product models that can be used to build variable products and increase reuse. * Try what-if-scenarios and thus increases the number of possible design iterations. * Downstream process (e.g. design preparation, production, assembly) effects of design changes. * Several ways by e.g. connecting a geometric dimension to another, by using a programming language, etc. * Important to understand * the structure of the product parts, * how these parts are related to each other, * avoid building 'spaghetti'-relationships * understand how the company processes related to the product parts and * Use UML (Unified modeling language) as a method to model and visualize good object-oriented and modular product structures and processes. * Goal * Understand how to construct effective parametric design by building useful, transparent and reusable product models. ===== The Stanford trip ===== * Sponsored by VINNOVA * Monday: David Gerber Lecture + Joint modeling work with Stanford students * David Gerber (DDes Harvard GSD, SCI Arc. Faculty - http://www.djgerber.com/) gives a presentation on parametric tooling + Class work on parametric modeling. Joint work with Stanford students * Tuesday: Wiki workshop * Wiki workshop together with Stanford students - get everyone up to speed on how to use it + coach people with describing their projects. We may throw some UML in here as well. The wiki we will be using is: http://www.dokuwiki.org/dokuwiki * Wednesday: Laura Bachelder Lecture + Joint modeling work with Stanford students * Laura Bachelder (Associate Architect, Frank O Gehry and partners) Laura may give a lecture related to "Associative Parametric Design in Architecture" and/or "Parametric Practices" focusing on the use and impact of Building Information Modeling (BIM) + Class work on parametric modeling. Joint work with the Stanford students. * Thursday: PhD level round table * PhD level presentations and discussions w CIFE (cife.stanford.edu) & LTU people: John Haymaker, Victor Gane, Forest Flager,  et al. quick pesha-kusha presentations (20 slides, 20s/slide) of CIFE and LTU work in progress followed by general discussions with a focus on systems modeling and parametric design * Friday: Possible visit to ConXtech * (www.conxtech.com) in Hayward. * Questions to think about before the trip * What characterizes * good parametric design? * a robust parametric model? * What should one not parametrize? ===== Workshop UML ===== * Nov 25, Luleå University of Technology * 10:15 Introduction to UML and SysML * 11:45 Lunch * 13:00 Exercises * 14:30 Fika * 14:45-16:15 Exercises continued * Course contents is preliminary and may be updated slightly. Start time (10.15) will not change. ===== Workshop CAD ===== * Nov 26, Luleå University of Technology * 08:30 Introduction to NX * 10:00 Fika * 10:15 Maintaining design intent * 11:45 Lunch * 13:00 Maintaining design intent cont. * 14:30 Fika * 14:45-16:15 Scripting * 18:30 Course dinner * Course contents is preliminary and may be updated slightly. * Nov 27, Luleå University of Technology * 08:30 Knowledge based engineering * 10:00 Fika * 10:15 KBE exercise * 11:45 Lunch * 13:00 KBE exercise cont. * 14:15-14:30 Fika and wrap up ===== Project assignment ===== * Preferable to cooperate * Some favor design and CAD before processes and UML and vice versa * Find a challenge within your research projects * Suggestion for assignment handed in at Oct 27 * Group members * Background, goal and plan to reach the goal * Use the Wiki during the work * Describe work, like a diary * Discuss issues ===== Examination ===== * Report * Handed in in Dec 12 at the latest * Describe work (both what and why), discuss pros and cons, conclude the most important results * Oral presentation * Dec 9, in Stockholm, venue TBD * Prepare for 20 minutes per group, allow for 10 minutes of questions * Wiki * Activity on the Wiki is checked * To see contributions * Make sure that all group members log in in turns ===== Wiki ===== * An internet site where information can be communicated of the course * An organic source of information, a live document, where everyone can add and edit the information * News * Project work * Discussions * http://php.twofourfour.org/dokuwiki/start * Accessible for course participants shortly ===== Software ===== * Wiki * Dokuwiki * www.dokuwiki.org/ * UML * yED * www.yworks.com/products/yed/ * CAD tool * Siemens PLM NX * http://www.plm.automation.siemens.com/en_us/products/nx/index.shtml ====== Parametric design ====== * Making construction design effective (doing the right things) and efficient (doing things right) * Making product models that are robust (stable) and can be reused multiple times during product design. * Incorporating multiple types of information in the product model * Standardization and reuse * Automation * One change can affect many other changes * External data can affect the model * Building in rules * Maintaining the design intent at a change ===== Example of parametrization ===== ==== Dimensional relationships ==== * Geometry is controlled by relationships * Scaling and still keeping proportions * Maintaining the design intent at a change * Example of relationships * Two lines are parallel * Width = Height/2 * Parts that should be scaled by discreet values (standard parts e.g.) can be handled by scripts or KBE * Think before you create relationships – //Beware of creating too many relationships!// {{:ltu:material:ex_param_dim.png|}}{{:ltu:material:ex_param_transform.png?300|}} ==== Scripts ==== | Scripts consist of programmed algorithms to solve the parameter values of the geometry. They can create more sophisticated relationships than for example Width = Height/2. The building on the right (30th Street Mary Axe or ‘The Gherkin’) has parametrized triangular windows of which all have individual shapes. | {{:ltu:material:ex_param_gherkin.jpg|}} | ==== Knowledge-based engineering ==== * Often CAD-based * Radical geometry changes can be automated * Geometry can be analysed for, e.g. * Performance * Production * Cost * Maintenance * Object oriented * Rules * Ensure that standards are followed * Suitable for repetitive tasks and mature products {{:ltu:material:ex_param_kbe.jpg|}}{{:ltu:material:ex_param_kbe_pm.png?500|}} * Downstream knowledge made available in early stages * Capture of information, experience, knowledge * Formalization {{:ltu:material:kbe_pd_process.png?600|}} ===== Connection to UML and processes ===== ==== UML (Unified modeling language) – a short introduction ==== * Universal visual modeling language * Syntax and semantics * De facto standard for modeling software applications * Bridges the gap between idea and application implementation * Models the world as systems of interacting objects * Attempts in being unified across different domains * Based on Object Oriented Programming * Diagrams show views of the model * Class diagrams * Activity diagrams === Class diagram === * Describes the static structure of the model * Contains classes and relationships * Attributes * Class details (color of house, number of windows etc) * Operations * Invokes a behavior (e.g. create geometry object) * Method - implementation of an operation {{:ltu:material:uml_class_def.png?200|}}{{:ltu:material:uml_class_diagr_ex.png?600|}} === Activity diagram === * Shows a procedural flow for a process * Useful for work flow modeling * Company processes * Activity * Contains a number of actions {{:ltu:material:uml_activity_def.png?400|}}{{:ltu:material:uml_activity_diagr_ex.png?400|}} ==== SysML - Systems modeling language ==== * Graphical modeling language for systems engineering * UML Profile that represents a subset of UML 2.0 with extensions * Supports the specification, analysis, design, verification and validation of systems that include hardware, software, data, personnel, procedures, and facilities {{:ltu:material:uml_sysml_circles.png?300|}} **Diagram taxonomy**\\ {{:ltu:material:uml_sysml_taxonomy.png|}} **Parametric example**\\ {{:ltu:material:uml_sysml_param_ex.png?800|}}