No abstract

The design process has a significant impact on the performance and profitability of a housing project. Therefore, decisions made during the design process should take into consideration knowledge and experience from other processes in previously accomplished projects, specifically from the production phase. How to capture and use production experience in housing has not gained enough interest, possibly leading to suboptimal improvements during the construction process. This motivates research on how onsite production experience from similar previous projects can be captured and used to improve constructability without risking customer values. Based on the concept of constructability, 'design for manufacturing and assembly' and the theory of waste, the method 'design for construction' (DFC) has been developed. The four-step model complements the conventional construction process, and consists of the following steps: (1) specify customer values and similar previous projects; (2) identify onsite waste and cost drivers in previous projects; (3) develop criteria to evaluate constructability; and (4) evaluate constructability of the design. The DFC method is exemplified and tested through a case study, in which it was shown that the method facilitated identification of all problems that were considered in the investigated project. The method also highlighted other project obstacles that potentially could have been solved to improve constructability.

No abstract

No abstract

Traditional methodologies for working together, create useful results which no system design and development have proven part of the element can create separately" [1], c.f. insufficient when it comes to very large and [2] and [3]. Such a generic definitions of system distributed systems. As a consequence, should be valid for all degrees of system research on complex socio-technical systems complexity, from non-complex systems to i.e. System-of-Systems [SoS], has evolved, At extremely complex distributed systems, so called the same time, researchers of complexSoS. However, several of these general systems that are not SoS have started to pay definitions of system state or at least imply an attention to the tools and methods developed architect, a clear purpose, and apparent within the area of SoS. The purpose of this boundaries that separate the system from its paper is therefore twofold: (1) to improve the surrounding; all of which are not necessary true understanding of SoS and SoS methods from for complex systems. a non-SoS point of view, by presenting SoS definitions, properties and behavior of SoS, A first categorization regarding the complexity and (2) to analyze current non-SoS level of systems can be made into non-complex development methodologies to test their systems and complex systems. There is no clear applicability in a SoS environment. Finally a line between these categories, and the distinction metric for the well-being of a SoS is is decided dependent on the viewpoint, i.e. the introduced. observer decides whether a system's behavior is complex of not. However, a system with behavior 1-4244-1041-X/07/$25.00 ©)2007 IEEE

No abstract

No abstract

No abstract