SwePub
Sök i SwePub databas

  Extended search

Träfflista för sökning "WFRF:(Poorkiany Morteza) "

Search: WFRF:(Poorkiany Morteza)

  • Result 1-19 of 19
Sort/group result
   
EnumerationReferenceCoverFind
1.
  • André, Samuel, 1986-, et al. (author)
  • Managing Fluctuating Requirements by Platforms Defined in the Interface Between Technology and Product Development
  • 2014
  • In: Advances in Transdisciplinary Engineering: Moving Integrated Product Development to Service Clouds in the Global Economy. - Amsterdam : IOS Press. - 9781614994404 - 9781614994398 ; , s. 424-433
  • Conference paper (peer-reviewed)abstract
    • Product platforms play an important role for the efficient customisation and variant forming of products in many companies. In this paper four different companies ranging from OEM to B2B suppliers have been interviewed on how they engage in technology and product development, create and maintain product platforms and how they respond to the changing requirements on the platforms and on the products and product families derived from them. The objective is to find how product platforms are used to meet the demands of efficient product customisation. The companies all have identifiable product platforms and established processes for product development. However, there are differences in how they define technology development, how the platforms are created, maintained, replaced and what the platforms contain. The introduction of new technology into the platforms and how the platforms are used from a Lean product development perspective has been of interest in the survey as reported in the paper.
  •  
2.
  • Elgh, Fredrik, 1971-, et al. (author)
  • Supporting Traceability of Design Rationale in an Automated Engineer-To-Order Business Model
  • 2012
  • In: DS 70: Proceedings of DESIGN 2012, the 12th International Design Conference, Dubrovnik, Croatia. - 9789537738174 ; , s. 1425-1434
  • Conference paper (peer-reviewed)abstract
    • The ability to efficiently and quickly design and manufacture highly customized product can provide a competitive advantage for companies acting on a market with shifting customer demands. A business model based on highly customized product requires advanced application systems for automating the work of generating product variants based on different customer specification. The establishment of a system for automated design and production preparation is a significant investment in time and money and is expected to give revenues over many years. To maintain a design automation system’s usefulness over time, frequent updating of design rules and execution control will normally become a necessity. Reuse of the system encapsulated generic product family descriptions when developing a new product family is also perceived to significantly increase the efficiency in system development. The scope and the purpose of this research originate from industrial problems and needs which have been identified within research projects carried out in near collaboration with industrial partners. New concepts, perceived as prescriptive models, are in this work introduced, evaluated, and refined which is in accordance with the design modelling approach [Duffy, Andreasen, 1995]. The focus of this paper is a case study carried out at a company with long experience of systems for automated variant design. The main objective is to provide a system foundation for modelling and management of product knowledge in design automation systems to support reuse, expansion and maintenance.
  •  
3.
  • Elgh, Fredrik, 1971-, et al. (author)
  • Traceability of decisions in product realization processes of custom engineered products
  • 2018
  • In: DS92: Proceedings of the DESIGN 2018 15th International Design Conference. - : The Design Society. - 9789537738594 ; , s. 249-260
  • Conference paper (peer-reviewed)abstract
    • Custom engineered products require an engineer-to-order approach in development, quotation preparation and order processing. This work reports the result of a three-and-a-half-year project were the objective was to develop means for implementation and management of computer support for engineering design and production engineering of customized products. Efficient re-use is essential for success and decision is identified as the core concept to trace tasks executed, knowledge used, design rationale and artefacts developed throughout the product realization process.
  •  
4.
  • Hjertberg, Tim, et al. (author)
  • Implementation and management of design systems for highly customized products – state of practice and future research
  • 2015
  • In: Transdisciplinary lifecycle analysis of systems. - : IOS Press. - 9781614995432 - 9781614995449 ; , s. 165-174
  • Conference paper (peer-reviewed)abstract
    • Individualized products, resource-smart design and production, and afocus on customer value have been pointed out as three opportunities for Swedishindustry to stay competitive on a globalized market. All these three opportunitiescan be gained by efficient design and manufacture of highly customized products.However, this requires the development and integration of the knowledge-basedenabling technologies of the future as pointed out by The European Factories ofthe Future Research Association (EFFRA). Highly custom engineered productsrequire an exercising of a very rich and diverse knowledge base about the products,their production and the required resources for design and manufacture. Thedevelopment and implementation of systems for automated design and productionpreparation of customized products is a significant investment in time and money.However, our experience from industry indicates that significant efforts arerequired to introduce and align these kinds of systems with existing operations,legacy systems and overall state of practice. In this paper, support for systemdevelopment in literature has been reviewed in combination with a survey on thestate of practice in four companies regarding implementation and management ofautomated systems for custom engineered products. A gap has been identified anda set of areas for further research are outlined.
  •  
5.
  • Johansson, Joel, 1978-, et al. (author)
  • Design Rationale Management – a Proposed Cloud Solution
  • 2014
  • In: Advances in Transdisciplinary Engineering: Moving Integrated Product Development to Service Clouds in the Global Economy. - Amsterdam : IOS Press. - 9781614994398 - 9781614994404 ; , s. 204-214
  • Conference paper (peer-reviewed)abstract
    • Due to increasing complexity of modern products it is many times impossible for single individual engineers to fully grasp the product they are a part of developing. Valuable time during the product development is therefore spent searching for knowledge about different aspect of the product. To enable engineers finding right knowledge in different situations, the knowledge must first of all exist. Secondly, it needs to be structured and thirdly, it needs to be accessible. In this paper all of these three aspects of design rationale (reasons for why the product is designed the way it is) are addressed with the main focus on the latter one, accessibility. An information model is presented that can be used to structure the design rationale. It also presents a schematic overview of how a cloud solution could be realized using the information model to make a complete system for instantly capturing, filtering and accessing design rationale in a contextual manner.To enable the instant and contextual capture, filtering and access of the design rationale, the design rationale management systems should be present to the engineers everywhere in the digital environment, ready for service. It should also include functions that make the design rationale shared to all privileged users making sure everyone has updated versions of the stored knowledge.In this work the main ideas of a method for instant and contextual capture, filtering and access of the design rationale are introduced and a pilot system described as a proof of concept. The pilot system can be used to capture, filter and access design rationale across and within text-documents, spread sheets and CAD-models.
  •  
6.
  • Johansson, Joel, 1978-, et al. (author)
  • Integrating knowledge objects and e-books to support six roles in the design automation life-cycle
  • 2019
  • In: Transdisciplinary engineering for complex socio-technical systems. - : IOS Press. - 9781643680200 - 9781643680217 ; , s. 571-580
  • Conference paper (peer-reviewed)abstract
    • Knowledge objects are used to automate engineering processes in a flexible and scalable way. The focus of knowledge objects has been the automation of engineering design. However, in this paper we present a way to integrate knowledge objects into e-books so that formalized engineering knowledge can be read by any stakeholder and still be automatically applied by the system from the same file. The paper shows how different stakeholders throughout the life-cycle of a design automation system benefit from the knowledge object and e-book integration, how the integration is done and an example where the integration was applied. The example is a real example from industry.
  •  
7.
  • Poorkiany, Morteza, 1980-, et al. (author)
  • A Case Study on Implementing Design Automation: Identified Issues and Solution for Documentation
  • 2013
  • In: 20th ISPE International Conference on Concurrent Engineering. - Amsterdam : IOS Press. - 9781614993018 - 9781614993025 ; , s. 324-332
  • Conference paper (peer-reviewed)abstract
    • Computer supported engineering design systems are used as support for designers by automating some tasks/activities of design process. From industrial aspect, implementation of a developed prototype system is a critical task. User acceptance is of high importance and strongly related to the access and understanding of the knowledge which requires a high level of system transparency. In addition, integration of the system in the environment or its compatibility with other systems/tools should be considered. Our experiences in industry show that two major issues are usually raised up during implementing a design automation system which are: documentation and organization. Documentation concerns the way of capturing, storing and distributing the information in systems, and organization concerns alignment of the system with other systems or tools as well as communication and collaboration among system participants and users. The focus of this paper is on documentation and the importance of reuse, design rationale and traceability is discussed. In order to align closely with industry practices, the thoughts are presented along with an on-going case study, where the development and analysis of roof racks for cars are being automated, and a number of challenges have been discussed. 
  •  
8.
  • Poorkiany, Morteza, 1980-, et al. (author)
  • An explorative study on management and maintenance of systems for design and manufacture of customized products
  • 2016
  • In: The 2016 IEEE International Conference on Industrial Engineering and Engineering Management. - : IEEE. - 9781509036646
  • Conference paper (peer-reviewed)abstract
    • This paper addresses the issues regarding retrieve, reuse and update of design information in context of customized products and adaptive design. Capturing and representing design rationale during the development process has been identified as an important factor to support design of product variants. The study explores the development process from identifying customer requirements to production preparation in a case company which has long tradition in automating generation of design variants.  
  •  
9.
  •  
10.
  • Poorkiany, Morteza, 1980-, et al. (author)
  • Capturing and Sharing Design Rationale for Customized Design Variants in an Integrated Design Environment
  • 2021
  • In: Proceedings of CAD’21, Barcelona, Spain, July 5-7, 2021. - El Paso, TX, USA : CAD Solutions. ; , s. 339-343
  • Conference paper (peer-reviewed)abstract
    • From the Introduction: Some companies represent their product family design as a space of design alternatives. The design space is a mathematical space that is governed by applying a set of design rules to design parameters. A key principle in establishing a design space instead of developing a single solution is to put minimum requirements for design optimization in the early stages of development. Developing a new design variant requires understanding the base design and adapting the design according to the new requirements. Use of design rationale can provide such understanding. With increasing the number of variants, access to design rationale becomes more important. Understanding why a design variant was accepted and if there have been any other alternatives in the beginning but were rejected (due to functionality or manufacturing limitations) can help the designers to avoid developing new design variants that have previously been proven wrong. Or it can support the designers to propose design variants that can be accepted under specific conditions for unique customers. The repetitive and time consuming design activities can be assigned to design automation systems in order to increase efficiency and shorten the lead time. The use of design automation system is more vital when the number of design variants drastically increase. Use of Domain Specific Language (DSL) can amplify the applicability of the design automation system by targeting specific domains. A DSL is a computer language that is developed focusing on a particular application domain [3] (some DSLs are widespread such as SQL which is used for database querying, but many are note widespread).In this paper, a method is presented for capturing and sharing design rationale for each design variant in an integrated design environment. An argumentation-based approach is used for capturing design rationale. An industrial partner which has a long tradition in automating its design process has been involved in the research, and the results of the research have been tested and evaluated in the company. In total, 11 workshops, 15 meetings and more than 20 semi-structured interviews with engineers from different departments in the company were conducted. A method and prototype system were developed to enable capture and share design rationale. The prototype system was demonstrated for a group of engineers on-site and a group of designers across the globe as part of the development. DSL is used initially by the company to develop the automation system. Our proposed design rationale system was developed as an extension to the automation system. 
  •  
11.
  • Poorkiany, Morteza, et al. (author)
  • Capturing, structuring, and accessing design rationale across product design and FEA
  • 2016
  • In: Product lifecycle management in the era of Internet of things. - Cham : Springer International Publishing. - 9783319331102 - 9783319331119 ; , s. 387-396
  • Conference paper (peer-reviewed)abstract
    • Implementing design automation systems to automate repetitive and time consuming design tasks enables engineer-to-order manufacturers to perform custom engineering in minimum time. To maintain a design automation system, regular updating of design information and knowledge is necessary. Consequently, there is a need of principles and methods to support capturing and structuring associated knowledge, specially, design rationale. In this paper a method for capturing, structuring, and accessing to design rationale in order to support maintenance of design automation systems is presented. The method is tested through a design automation system that develops FEA (finite element analysis) models automatically. The results are evaluated in a case company which is a supplier to the automotive industry serving many brands and car models which each more or less requires a unique solution.
  •  
12.
  • Poorkiany, Morteza, et al. (author)
  • Capturing, structuring and accessing design rationale in integrated product design and manufacturing processes
  • 2016
  • In: Advanced Engineering Informatics. - : Elsevier. - 1474-0346 .- 1873-5320. ; 30:3, s. 522-536
  • Journal article (peer-reviewed)abstract
    • Developing customized products is the business case for many manufacturing companies striving to fulfill the customers’ specific needs. When manufacturing customized products it is often necessary to also develop corresponding customized manufacturing tooling. There is a need to support concurrent development of new product variants along with their manufacturing toolsets. The communication between design engineers and manufacturing engineers is hence a key issue that if solved would enable design engineers to foresee how changes in product design affect tooling design and vice versa. To understand the correlation between the design of a product and its corresponding manufacturing tools, access to design rationale of the product and the developed tooling is required. Design rationale provides an explanation of why an artifact is designed in the way it is, including statements (textual, numerical or geometrical), argumentations, and decisions. Since design rationale is composed of information scattered all across the company's repositories in different formats (e.g. in type of a geometry, picture, table, and textual document), representing the design rationale is a challenge for many enterprises. In this paper a method is introduced that enables capture, structure and access to design rationale across product design and tooling design. The system enables representing design rationale in formats such as CAD models, spreadsheets, textual formats, and web pages. The method has been examined by developing a prototype system tested in a case company which develops and manufactures customized car accessories, such as roof racks and bike carriers, for different car models. The company develops and manufactures the products as well as the required tooling equipment. The prototype system includes different software commonly used by engineers during designing a product, for the purpose of making it applicable for other companies.
  •  
13.
  • Poorkiany, Morteza, 1980-, et al. (author)
  • Integrating knowledge objects and design descriptions to support maintenance of design automation systems
  • 2019
  • In: Transdisciplinary engineering for complex socio-technical systems. - : IOS Press. - 9781643680200 - 9781643680217 ; , s. 561-570
  • Conference paper (peer-reviewed)abstract
    • Design automation systems are implemented by many manufacturing companies to automate the repetitive and time-consuming design tasks. By automating such tasks, the designers have more time to focus on creativity and offer more customized solutions to the customers.To automate a design task, first, the design knowledge should be captured from designers. This type of knowledge which is usually understandable by humans should be structured and formalized. Next, computer codes and scripts (that are mostly understandable by computers/expert persons) are created to execute the knowledge and provide the desired output.To support maintenance of computer codes and scripts in a design automation system, it is necessary to know what, how and why about that piece of code/script. In order to support maintenance of the systems, we represent the system’s knowledge in form of knowledge objects. Knowledge objects are executed in run time and consist of two parts: computer readable and human readable. The focus in this paper is on the human readable which we call it “design description”. A MOKA-based framework is provided to create design descriptions for the computer readable parts. The design descriptions help engineers to understand and if needed update the computer readable parts, which in a wider aspect support maintenance of the whole system. E-books were used as a way to represent the design descriptions and a case study is provided to explore the results of the research.
  •  
14.
  • Poorkiany, Morteza, 1980- (author)
  • Managing design rationale in the development of product families and related design automation systems
  • 2017
  • Doctoral thesis (other academic/artistic)abstract
    • As the markets’ needs change rapidly, developing a variety of products that meet customers’ diverse needs is a competitive factor for many manufacturing companies. Development of highly customized products requires following an engineer-to-order business process to allow the products to be modified or adapted to new customers’ specifications, which brings more value to the customer and profit to the company.The design of a new product variant involves a large amount of repetitive and time-consuming tasks but also information handling activities that are sometimes beyond human capabilities. Such work that does not rely so much on creativity can be carried out more efficiently by applying design automation systems. Design automation stands out as an effective means of cutting costs and lead time for a range of well-defined design activities and is mainly considered as a computer-based tool that processes and manipulates the design information.Variant design usually concern generating a new variant of a basic design, that has been developed and proved previously, according to new customer’s demands. To efficiently generate a new variant, a deep understanding of the intention and fundamentals of the design is essential and can be achieved through access to design rationale—the explanation of the reasons and justifications behind the design.The maintenance of product families and their corresponding design automation systems is essential to retaining their usefulness over time and adapting them to new circumstances. Examples of new circumstances can include the introduction of new variants of existing products, changes in design rules to meet new standards or legislations, or changes in technology. To maintain a design automation system, updating the design knowledge (e.g. design rules) is required. The use of design rationale will normally become a necessity for allowing a better understanding of the knowledge. Consequently, there is a need for principles and methods that enable the capture and structure of the design rationale and sharing them with the users.This study presents methods and tools for modeling design knowledge and managing design rationale in order to support the utilization and maintenance of design automation systems. Managing design rationale concerns enabling the capturing, structuring, and sharing of design rationale. The results have been evaluated through design automation systems in two case companies.
  •  
15.
  • Poorkiany, Morteza, 1980- (author)
  • Support Maintenance of Design Automation Systems - A Framework to Capture, Structure and Access Design Rationale
  • 2015
  • Licentiate thesis (other academic/artistic)abstract
    • The ability to innovate and launch customized products that are well matched to customer demands is a competitive factor for many manufacturing companies. Development of highly customized products requires following an engineer-to-order business process to allow the products to be modified or adapted to new customers’ specifications, which brings more value to the customer and profit to the company.Design of a new product variant involves a large amount of repetitive and time consuming tasks but also information handling activities that are sometimes beyond human capabilities. Such work that does not rely so much on creativity can be carried out more efficiently by applying design automation systems. Design automation stands out as an effective means of cutting costs and lead time for a range of well-defined design activities and is mainly considered as a computer-based tool that processes and manipulates the design information.Adaptation and variant design usually concern generating a new variant of a basic design, which has been developed and proved previously, according to new customer’s demands. In order to efficiently generate a new variant, a deep understanding of the previous design is essential. Such understanding can be achieved by access to the design rationale explaining the reasons and justifications behind the design.Maintenance of design automation systems is essential to retain their usefulness over time and adapt them to new circumstances. New circumstances are, for example, introduction of new variants of existing products, changes in design rules in order to meet new standards or legislations, or changes in technology. To maintain a design automation system, updating the design knowledge (e.g. design rules) is required. Use of design rationale will normally become a necessity to allow a better understanding of the knowledge. Consequently, there is a need of principles and methods to enable capture, structure, and access design rationale.In this study, a framework for modeling design knowledge and managing design rationale in order to support maintenance of design automation systems is presented. Managing of design rationale concerns enabling capture, structure, and access to design rationale. In order to evaluate the applicability of the framework, the findings are tested through design automation systems in two case companies.
  •  
16.
  • Poorkiany, Morteza, 1980-, et al. (author)
  • Support management of product families and the corresponding automation systems – A method to capture and share design rationale
  • 2017
  • In: Proceedings of the 21st International Conference on Engineering Design. - : The Design Society. - 9781904670940 ; , s. 267-276
  • Conference paper (peer-reviewed)abstract
    • The ability to innovate and launch customized products that are well matched to customer demands is a competitive factor for many manufacturing companies. Development of highly customized products requires following an engineer-to-order business process to tailor the products according to customers’ specifications, which brings more value to the customer and profit to the company. Using design automation systems to automate repetitive and time consuming design tasks enables the manufacturers to perform custom engineering in minimum time. To manage and maintain a product family and the corresponding automation systems, updating the design knowledge is required. Use of design rationale will normally become a necessity to allow a better understanding of the knowledge. Consequently, there is a need of principles and methods to enable capture and effectively share the design rationale. In this paper a method for capturing and sharing design rationale is presented. The results are evaluated in a case company which is a supplier of tooling for manufacturing industry.
  •  
17.
  • Poorkiany, Morteza, 1980-, et al. (author)
  • Support reuse and maintenance of design information in a development process of custom engineered product
  • 2019
  • Conference paper (peer-reviewed)abstract
    • In this paper a method is introduced that supports reuse and maintenance of design information. The method allows sharing design information in different levels of details tailored for the stakeholders according to their needs. In addition, it is possible to share the information in multiple formats to suite different purposes. The results are demonstrated in an industrial partner which is a supplier of tooling for manufacturing industry.
  •  
18.
  • Poorkiany, Morteza, 1980-, et al. (author)
  • Supporting Tooling Design of Customized Products by Instant Access to Design Rationale
  • 2014
  • In: The 6<sup>th</sup> International Swedish Production Symposium 2014. - 9789198097412
  • Conference paper (peer-reviewed)abstract
    • In an integrated product and production development environment, where changes in tooling design affect the product design and vice versa, access to design rationale of tooling would support concurrent development of new product variants and required tooling. This paper presents an information model that enables easy capture and access to the design rationale of toolings, moreover, supports tracing relevant information within different design software applications. A solution based on integrating SolidWorks, Microsoft Excel, and Microsoft Word has been developed and an industrial case study, where the system is introduced and evaluated is presented.
  •  
19.
  • Stolt, Roland, et al. (author)
  • Managing Risk in the Introduction of New Technology in Products
  • 2015
  • In: Journal of Aerospace Operations. - : IOS Press. - 2211-002X. ; 3:3-4, s. 167-184
  • Journal article (peer-reviewed)abstract
    • In this paper interviews with staff involved in product development from four different companies is presented. The objective is to find out how the companies manage the technical risk of introducing new technology in products and how they prepare for meeting changing requirements from customers. The companies originates from aerospace, automotive and production engineering. Based on the results of the first study, a case study was carried out at the aerospace company. The studies shows that, the introduction of new technology varies with the risk of failure in the validation of the products. Companies that easily can revert back to the former technology is more risk taking. The types of products and the companies’ place in the supply chain has an impact on technology introduction and requirements handling. The companies have strategies for developing requirement specifications prior to the start of the project. This is most elaborate at the aerospace company where a thorough concept evaluation clarify possible variations in requirements.
  •  
Skapa referenser, mejla, bekava och länka
  • Result 1-19 of 19

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Close

Copy and save the link in order to return to this view