The management of information is one of the key aspects within a successful andefficient product development process, particularly regarding complex products.Scania CV AB is at the moment developing a new IT-system, OAS, which aims tomanage the company’s product data. With this as a background, the purpose of thismaster thesis is to identify the cross-functional user needs within Scania’s organizationconcerning product data and the management around it. To fulfill the purpose, an empirical study consisting of 40 personal interviews with 50representatives from different functions within Scania’s organization was carriedthrough. The empirical data was then analyzed focusing on identifying thecross-functional needs and issues. The study points out that there is a big potential regarding improvement among themanagement of product data. For example, a lot of time is spent by the users to findthe requested information and to copy data manually from one IT-system to another.The most important findings, in terms of cross-functional user needs within Scania’sorganization, are the integration of Scania’s many IT-system and to make informationmore accessible. Further needs are regarding the ability to follow a product’s entirelifecycle, better support for the user’s understanding of the complex product, anenhanced management of Engineering Change Orders and a better supportconcerning the product structure.

none

The environmental assessment system Miljöbyggnad is a Swedish system initiated by Bygga-Bo-Dialogen to assess buildings with regards to three main areas; “Energy”, “Indoor climate” and “Materials”. A building can obtain three different classifications depending on how well it manages to meet the demands. GOLD is the highest classification and is followed by SILVER and BRONZE. The majority of the measures needed to comply with the demands are done during the design phase. During the production phase a considerable amount of work is required to make sure to document the built in products and make sure they do not contain any dangerous substances. The thesis is based on the experiences retrieved by working with Miljöbyggnad in Skanska’s project Sickla Udde skola which is aiming for the highest classification GOLD. Interviews have been conducted with employees of Skanska working with the system in order to take part of their experiences. The thesis identifies difficulties linked to working with the main area “Materials” during the production phase. It also describes the available product data bases used to simplify the work with the system. Furthermore the thesis gives suggestions on how to work with Miljöbyggnad during the production phase.

“För ett automatiserat återskapande av inbyggda systems funktionella arkitektur från källkod och produkt data” Den ökade komplexiteten i inbyggda system inom fordonsindustrin tillsammans med de striktare säkerhetsrestriktionerna som infördes av ISO26262 standarden, kräver bättre kunskap och kännedom om produktarkitekturen. Men, för befintliga produkter som inte var utvecklade enligt en väldefinierad arkitekturmodell, så måste en modell återhämtas. Syftet med detta examensarbete är att automatisera återhämtningen av funktionella arkitekturen för fordons inbyggda system, vilket är ett krav för många av ISO26262 aktiviteter. Detta examensarbete föreslår och beskriver två modeller för det inbyggda systemet i ett fordon, och visar dess användning för att bland annat generera användarvänliga vyer. Återhämtningen av modellerna sker genom att tolka den inbyggda C-koden och bearbeta fordonets data såsom inblandade styrenheter, deras adresser och CAN buss detaljerna. Två modeller har föreslagits för att fånga den återskapade informationen om inbyggda systemet i ett fordon: en produktmodell för inbyggda system och en mjukvaruarkitektur modell för den inbyggda mjukvaran. Produktmodellen är en enkel modell på det inbyggda systemet som bara inkluderar nödvändig hårdvaru- och mjukvaru-detaljer för att klara uppgiften att skapa denfunktionella arkitekturen. Den inbyggda mjukvaruarkitektur modellen härleds från produktmodellen. Den modellerar endast högnivå komponentbaserade mjukvarulagret i alla styrenheter tillsammans. Därmed så abstraheras all hårdvaruinformation inklusive mjukvaruallokering och CAN buss information. De föreslagna modellerna har framgångsrikt använts för att generera funktionella arkitekturen för ett par SCANIA lastbilar. Generering och återhämtningen av modellerna utfördes med hjälp av ett verktyg som utvecklades för detta ändamål. Vidare så har en standardiseringsmekanism från de föreslagna modellerna till AUTOSAR också tagits fram och presenterats. Standardiseringsmekanismen är rättfram när styrenhets kring utrustning inte beaktas i modellen. I framtiden bör sensorer och ställdon inkluderas i modellerna. En mer detaljerad studie av den inbyggda programvaruarkitektur modellen, beträffande databeroende, bör också genomföras för att ta itu med problemen rörande felaktiga data-flödesvägar vilka har träffats på i detta arbete. Dessa problem uppkommer vid steget för CAN buss abstraktion. / “Towards automated recovery of embedded system functional architecture from source code and product data” The increased embedded system complexity in the automotive industry together with stricter safety constraints introduced by the ISO26262 standard, require a better knowledge about the product architecture. However, for existing products which were not developed according to a well defined architecture model, the latter need to be recovered. The objective of this thesis work is to automate the recovery of the functional architecture in a vehicle, which is required for many of ISO26262 activities. The work of this thesis proposes and describes two embedded system models for the target system, and shows their usage to generate user friendly views. The recovery of the models is done by parsing embedded C-code and fetching vehicle's data such as involved ECUs, their addresses and CAN bus details. This work has proposed two models for capturing the recreated information about an automotive embedded system: a product model for the embedded system and an architecture model for the embedded software. The product model is a simple embedded system model that only includes needed hardware and software details for the task of generating the functional architecture. The embedded software architecture model is derived from the product model and abstracts all hardware information. The embedded software architecture model covers only the high-level component based software in all ECUs together abstracting away allocation and CAN bus information. The proposed models have been successfully used to generate functional architecture for a couple of SCANIA trucks. The generation and recovery of the models was performed by a software tool that has been developed for this purpose. In addition, a mapping from the embedded software model to AUTOSAR standard has been proposed as a way to standardise the representation. The mapping to AUTOSAR showed that it is quite straight forward when not taking in consideration any possible ECU peripherals. In the future, representation of sensors and actuators should be included in the models. A more detailed study of the architecture model for the embedded software, with regards to data-flow, should also be conducted to tackle issues related to wrong data-flow paths which have been found in this thesis. The issues arise in the step of CAN bus abstraction. / الموجز"نحو أتمتة استخلص  البنية الوظيفية للنظم المضمنة من مصدر وبيانات المنتَج"،ISO إن الزيادة في تعقيد النظام المضمن في السيارات بالضافة إلى شروط السلمة الكثثر صرامة والتي أدخلها معيار 26262تتطلب معرفة أفضل ببنية المنتَج. ولذلك، فبالنسبة للسيارات التي تم إنتاجها بدون تتبع نموذج معماري واضح المعففالم، ف ففإن هففذاالخير يجب أن يتم استخلصه ل حقا.كثان الهدف من هذه الطروحة إثبات إمكثانية أتمتة استعادة البنية الوظيفية للنظام المضمن في السيارة، وهو المر المطلوب للعديدهذه الطروحة تقترح وتصف نموذجين للنظام المضمن، وتُظظهر إمكثاني ففة اسففتخدامهما لخل ففق .ISO من أنشطة المعيار 26262وبيانات السيارة المختلف ففة م ففن C عروض حاسوبية سهلة الفهم والستعمال. يتم استخلص  النماذج عبر تحليل مصدر لغة البرمجة.(CAN) مثل أجهزة التحكثم الموجودة، عناوينها وتفاصيل شبكثة الكثانيقترح هذا العمل نموذجين جزئييْنن للنظم المضمنة في السيارات: نموذجَ المنتَج للنظام المضمن ونموذجففا لبرمجي ففات النظففامالمضمن فقط. نموذج المنتَج هو نموذج مبسط للنظام المضمن يحتوي فقط على الحد الدنى من التفاصيل اللزمففة عففن الجهففزةوالبرمجيات الذي يخوله للقيام بمهمة استخلص  البنية وظيفية. أما نموذج برمجيات النظام المضمن فيُستمد من نموذج المنتج. هففذاالنموذج يغطي فقط البرمجيات المتواجدة في الشرائح العليا من برامج أنظمة التحكثم كثلها في آن واحد. بهذا الشكثل، فإن هذا النموذج.(CAN) ل يحتوي أي معلومات عن الجهزة بما في ذلك معلومات تموقع البرامج في أجهزة التحكثم ومعلومات شبكثة الكثانوقد تم استخلص  ه ففذه النم ففاذج ،SCANIA تم استخدام النماذج المقترحة بنجاح لتوليد بنية وظيفية لبضع شاحنات تابعة لشركثةباستخدام برنامج حاسوبي تم تطويره لهذا الغرض. إضافة إلى ذلك، فقد تم تحديد طريقة ترجمة لنموذج برمجيات النظام المضففمنوالتي أظهرت أن الترجمة عملية سهلة ومباشِررة إذا لم يُؤخخذ في العتب ففار ،AUTOSAR المقترح حتي يصير متوافقا مع معيار الفأي أجهزة طرفية قد تكثون مربوطة بأجهزة التحكثم.مستقبل، ينبغي إضافة دعم لجهزة الستشعار والمشغلت الميكثانيكثية إلى النماذج المقترحة. كثما ينبغي إجففراء دراسففة أكثففثرتفصيل لنموذج برمجيات النظام المضمن فيما يتعلق بتدفق البيانات، وذلك لمعالجة بعض الشكثالت المتعلقة بمسارات تدفق خاطئ ففة.(CAN) للبيانات والتي تم العثور عليها في هذه الطروحة. هذه الخطاء تنشأ في خطوة تجريد معلومات شبكثة الكثان

Product development companies are continually seeking methods to increase efficiency while maintaining quality. Distributed development is also more important than ever before as industries globalize. These forces have driven firms to adopt formal data management practices that allow groups and individuals to work from singular, centralized data source that are secure, reliable, and support collaboration. This thesis proposes a methodology to leverage globalized infrastructures for the efficient storage of product variations. The methodology is proved through a working prototype using the market leader in Product Lifecycle Management (PLM) systems, Teamcenter Engineering. First, paradigms are set forth for the storage of various types of engineering documents in PLM systems in parametric formats. Then the use of these paradigms is exemplified by various programs retrieving and storing document variations in the form of PLM metadata. Finally, the results show that this methodology produces drastic increases in system performance as well as the enabling of PLM-compatible automation and optimization. The impacts of these findings have significant implications for industry and has generated interest from several global engineering firms and academic journals.

No description available.

Le travail de recherche présenté dans ce mémoire s’intéresse aux problèmes d’interopérabilité dans le domaine du Product Lifecycle Management (PLM) et vise à proposer une méthodologie capable d’y remédier. Nous définissons l’objectif stratégique du PLM comme la maîtrise de la complexité qui caractérise le développement et le suivi des produits. Dans ce cadre, l’objectif de l’interopérabilité est le contrôle des interactions entre constituants de ce système complexe PLM. Nous montrons que cet objectif est atteint si on assure la continuité et la conservation du flux sémantique qui circule dans le système. Notre étude est restreinte aux seuls domaines de la conception et de la production, mais a l’ambition de pouvoir s’appliquer à d’autres domaines. La continuité du flux sémantique est assurée par une architecture que nous avons baptisée « médiation multi-échelle orientée services ». Le cœur de cette architecture, le médiateur, se charge d’orienter les flux sémantiques vers les systèmes concernés, et met en correspondance sémantique les informations échangées en s’appuyant sur un méta-modèle d’unification. Nous montrons que pour assurer la robustesse, la flexibilité et l’agilité du système ainsi constitué, il faut privilégier le choix d’un méta-modèle standard générique et extensible. A cet effet, nous proposons une cartographie du standard STEP permettant de choisir le méta-modèle pertinent. Nous illustrons le choix et la définition de ce méta-modèle dans le cas de deux problèmes d’interopérabilité des domaines de la conception et de la production : l’interopérabilité CAO/PDM et l’interopérabilité PDM/ERP. Nous expliquons notre démarche dans la mise en œuvre de la norme PLCS. Par ailleurs, nous introduisons un modèle d’annotations sémantiques du produit qui permet de reconstruire des vues multiples correspondant à différents besoins métiers. Un ensemble de démonstrateurs permet de valider nos propositions et nos résultats. / Research work presented in this manuscript deals with interoperability issues in the domain of Product Lifecycle Management (PLM) and aims at proposing a methodology able to remedy it. We define the objective of PLM as the control of the complexity that characterizes the development and monitoring of the product. In this context, the objective of the interoperability is to control the interactions between components of this PLM complex system. We demonstrate that this objective is reached if we ensure the continuity and the conservation of the semantic flow inside the system. Our study is restricted to design and production fields, but can be extended to other domains. The continuity of the semantic flow is guaranteed by an architecture that we entitled “service-oriented multi-layered mediation”. The main part of this architecture, the mediator, takes care to orientate the semantic flows towards the adequate systems, and semantically connect the exchanged information by relying on an unification meta-model. We demonstrate that, to ensure the robustness the flexibility and the agility of the so-constituted system, the choice of a generic and extensible standard meta-model should be favored. We thus proposed a mapping of STEP standard allowing to choose the adequate meta-model. We illustrate the choice and the definition of this meta-model in the case of two interoperability problems in the design and production domains: the interoperability CAD/PDM and the interoperability PDM/ERP. We illustrate our methodology in the implementation of the PLCS standard. Moreover, we introduce a model of product semantic tags that allows to rebuild the multiple product views corresponding to different actor needs. A set of demonstrators validate our propositions and our results.

The research work detailed in this dissertation relates to the computer representation of information which concerns product families and product platforms. Common to competitive companies today, is the quest of designing products and processes to meet a large variety of customer needs, in short time, and based on few resources. One way to succeed with this endeavor is to plan for the variety and design a modular, or adaptive, product family based on a common platform of resources. To further increase the efficiency in delivering customized products in time, a computer processible model of the family is created, which is used to realize a customer specific product variant during the order phase. The objective of this research is to define a generally applicable model of product family information for the purpose of supporting various applications, and for achieving an efficient utilization of information. The approach is to define a model of the product family according to the theory of Axiomatic Design, which reflects the trace from various requirements to functions and different properties and components of the product. By representing information from design in a generally applicable format, this information can be reused when building the configuration models of the order phase. By adapting the model to an existing standard, information exchange between systems is supported, and access is provided to information concerning detailed physical parts as well as constructs addressing various use and version management. Contributions include a description of a model architecture with reusable functional solutions, interfaces, structures and interrelations between platform solutions and product family. Further, it is described how to extend and model the domains and interrelations of axiomatic design in an information model, which is adapted to the product modeling standard of ISO10303-214. / QC 20100812

In recent years, due to severe global market competition, increase of manpower costs and decrease in foreign trade, plus low-price labor costs from China and southeastern Asia countries (eg. Vietnam), all these factors enforce Taiwan manufacturing, such as motorcycle industry, moving their production factories to those countries. This phenomenon has been brought to Taiwan government¡¦s attention, and this crisis has encouraged our industrial circles to develop higher-level R&D and design center. Furthermore, the official department (eg. Industrial Development Bureau) also supplies enterprises with expenses support to conduct R&D and design. Within New Product Development (NPD) is one of the major subsidiary entries. Take Taiwan motorcycle industry as an example. To develop NPD is an essential competitive strategy for enterprise. On the one hand, this strategy has helped Taiwan motorcycle industry to be independent of technical domination from Japan; on the other hand, it has created differentiation in motorcycle industry and consolidated the foundation marching into international market. This is also what internal manufacture enterprises strive for. NPD process involves several stages. For example, in 1994 Cooper brought up product composition, initial evaluation, concept design, product development, product test, engineering trial production and limited quantity to market, these 7 stages, and NPD participant units or departments are quite a lot. For example, in motorcycle development process, participant units include merchandise plan, sales, R&D, manufacture, mold design, and quality control departments, and even parts supplier or motorcycle agent. This kind of collaborative development method has the advantages of putting heads together so as to get better results and cooperation. However, it remains existing problems with wasting time and efforts on inter-department interaction and manual data communication, and data accuracy (eg. version of design chart). To cope with the above problems, most enterprises are solving via existing IT system, such as simplex e-mail, more complex ERP (enterprise resources planning, ERP) or PDM (product data management, PDM). These systems have their own functions. E-mail focuses on communication; ERP integrates information of manufacture, human resources, finance, and marketing; PDM puts emphasis on engineering data management. In the viewpoint of NPD, these systems can only provides partial functions, but are incapable of support the requirements of entire collaborative process. For example, e-mail cannot supplies simultaneous communication; ERP lacks of design mold required by R&D department; PDM only has engineering data. If other departments need related data, they must develop other software to obtain. Because of swift progress in IT plus the cooperation demands in business operation among enterprises, departments and individuals, all these arouse attention on collaborative commerce, and it can also recover the disadvantages of e-mail, ERP or PDM while operating in NPD process. Collaborative commerce contains collaborative scheme, collaborative marketing, collaborative product commerce (or development) and collaborative service, these system classifications. Within them, collaborative product development binds NPD most. In current, the main manufacturers are PTC, HP and IBM. The merits of the system lie in effective controlling NPD process, constructing NPD operation standard, and accumulating experiences in new product design and manufacture. For example, in1995 Airbus in France had used PTC Windchill to conduct collaborative aircraft design. In 1999, there was Taiwan manufacturer under government¡¦s subsidy applying this system on new motorcycle model design. The main objective to introduce collaborative product development software is applying IT to support NPD process. IT introduction process is an important period for enterprises to identify whether it is successful or not, and the adaptation during the process is the key accordance to determine success or failure of IT. Therefore, some scholars discuss IT introduction process from adaptation point of view. For example, Leonard ¡V Barton¡]LB¡^¡]1988¡^addresses mutual adaptation mode between technology and organization to resolve misalignment during introduction process in technology (original IT specification), delivery system (training courses), performance criteria (impact upon activity). Susman et al.¡]2003¡^addresses that while using collaborative technology, the misalignments between technology and work, team and organization should be solved. DeSantics and Poole¡]1994¡^ bring up adaptive structuration theory¡]AST¡^. The theory emphasizes on appropiration in technology, work, organizational environment and group. The higher the appropiration is, the higher the decision performance will be. Tyre and Orlikowski¡]1994¡^deem the technology adaptation is not gradual and continuous, but highly discontiunous. They indicate that in adaptation discrepancy events will discontinuously occur. This event provides enterprise an opportunity to review the suitability of existing process or a method to modify present process. Although above researches have provided vital results, research result from Majchrzak et al.¡]2000¡^about new technology introduction process still cannot clearly describe all phenomena. Hence, they have discussed adaptation in project process via rocket design project and used collaborative technology (such as e-mail, data sharing or electric board) Majchrzak et al. has connected collaborative technology and NPD, but the research has discussed small and simple collaborative technology only (such as e-mail), but lacked of result of large and complex collaborative product development software. Meanwhile, although the result is the application of NPD, it does not provide the adaptation of each NPD stage (such as engineering trial manufacture). Furthermore, the mature experiences from western countries, such as Airbus in France, in introduction of collaborative product development software in NPD is worthy of consultation, but the specific situations in different countries should be taken into consideration. In Taiwan, cases which application of collaborative product development software supports NPD are still rare, but these introduction experiences are worthy of making thorough inquiry for other enterprises¡¦ reference. Therefore, the article has selected a case closed study of Taiwan manufacturing that introduced collaborative product development software and accompanied with related adaptation theory (such as LB mode, AST, discrepancy event, etc.) to thoroughly investigate adaptation conditions and result analysis before, in the middle of, and after introduction.

No description available.