Model-based techniques and competence integration within development of complex mechatronic products.doc

graduate course: research planning2nd assignment of research planning course- given by hans hanssonmodel-based techniques and competence integration within development of complex mechatronic productsjianlin shikth, machine designbackgroundthe vehicle industry is experiencing a tendency that more and more functionalities are highly depended on electrical components and software apart from traditional mechanical components. thus it brings a crucial need for efficient integration of multidisciplinary as well as high degree of competence integration as complexity increases.purpose and aimaccording to above descriptions, the projects overall aim is to improve management of the complexity within the development of complex mechatronic system products. it is highly relevant to vehicle industry and other manufacture industries which use mechatronic technology, and devoted to develop knowledge, support methods and prototype tools for effective development of complex mechatronic system products. the status of problems can be attacked from two different but necessary and supplement approaches: how to manage technology integration within mechatronic development? how to manage the competence integration over disciplines boundaries within mechatronic development?the project is characterised of that research mixes both technique experienced factors and individual- and organization related factors.a long-term purpose of the project is that swedish companies that develop complex composite products shall be improved essentially. this expectation leads to higher growth in the manufacture industry and gives space for new business aspect to it-support and consults service. concrete aim for the project in terms of delivered and documented results is: inquiry, documentation and analysis of the current situation by development of one or more complicated system comprehensive functions/ products at vcc. requirement specification in respects of development methodology, development organization and tools support based on above analysis. model framework (abstraction, view, relations) for multi-domain development. methodology for mechatronic system development. methodologies for organizations development including identifying of possibilities and obstacles. prototype tools and description of how these are related to existed commercial tools. the prototype tools are based on the developed modelling framework. requirement specification in respects to product and model data and their management in coming pdm-system.all these aims and expected results were general and applicable in a large part of the swedish manufacture industry.definitionmodel-based development (mbd), defined as “systematic use of modelling throughout the life cycle to support product development and maintenance” by m. trngren, where modeller is compatible over domain boundaries and thus provides possibility to co-simulating and integrated system analysis, is the key approach to efficient development of better products. the model based approach also produces the prerequisite for necessary competence integration, which plays the key role in making better use of developments resources. according to ola larses and niklas adamsson 2004, there are three drivers for mbd: maturity, standardization and complexity of the product.recently, model-based development is also often referred as model driven engineering (mde). the object management group has promoted a new model based approach “model-driven architecture” (mda), which adopt number of technologies such as uml, mof, specific models, and uml profiles to provide high portability, interoperability and reusability through architectural separation of concerns omg, 2001.hypothesiscomplexity management and model integration are the central concepts in this project. the mechatronic product is complex and thus requires integration of technologies and competences. this, when combined with requirements on shorter process time and more cost effective development, assumes that elements of modelling and analysis are based on model instead of prototype building. hypothesis for the project are:model-based development, where model is compatible over domain boundaries and thus provides possibility to co-simulating and integrated system analysis, is the key to efficient development of better products. the model based approach also produces the prerequisite for the necessary competence integration, which is the key to make better use of developments resources.co-operation and communicationthe project is driven by the cooperation with project integrated products data management for complex products containing embedded system, which is seeking by mikael strm, ivf and prof johan malmqvist, chalmers.both project work with problems situation in filed of development of complex products containing embedded system.project integrated products data management for complex products containing embedded systems going to principally attack the problems situation in field of transference management of pdm, products data, information model and system engineering for embedded system. the project is going to attack problems in an overall plan and gradually on the way of requirement from individual functions.the planed cooperation between kth and ivf has been initiated partly through vinnovas application process with interest report and partly through earlier information exchange among itv- projects: itiv107 embedded system and itiv228 leading to innovation and durable development (emp/itv).because the project contains a case study of product development and empirical research on development process, it is expected that development methodology, tool and organizational further development could apply directly at vcc. the project results come to be an important part of swedish industry and companies have similar problem situations such as vcc, saab automobile, bombardier, volvo ab, etc.hot topicsas we discussed previous, the key conception in mbd of mechatronics is complexity and integration. therefore, there are two hot topics in this field as listed below: model integration information managementstate of the artthe research on mechatronic systems has traditionally focused on functionality, performance, and dependability. since the system increasingly more complex and widely used, complexity and flexibility becomes critical as well.related research projects in kth and partnerskth mechatronic has already operated 10 years research in model based development (rtp, 2003), in which including requirement on models (tngren and redell, 2000), model framework (chen and trngren, 2001), and development of tools prototypes and methodology (el khoury and trgren, 2001). kth mechatronic also participated in the vehicle project east-eaa (eureka) which aimed to develop description language for development of embedded system in vehicles. these researches are principally divided into model-based development of mechatronic systems and work methods in such development. codex: to develop a dependable and cost-effective x-by-wire system architecture for safety critical applications in heavy trucks. focused on architectural design, keyfigures, design parameters, information management, models and tools. (ola larses, martin trngren) save: model and component based development of automotive safety critical software specially a generic multiview system supporting dynamic integration. in cooperation with mdh, lith and uu (hans hansson). aida2: towards a modelling framework and methods for analysis of real-time behaviour in order to support the development of distributed, heterogeneous control systems. (redell ola, el-khoury jad and martin trngren) march: to develop a system architecture/framework suitable for embedded distributed computer control systems (di-jiu chen, martin trngren)other related research:because mechatronic products are distinguished by an increasing degree of connection between functions and components and also between components/subsystems in a product, there are huge requirements on harmony between products structure and developments organisational structure. as far as 2001, eppinger and salminen proposed an idea that three domains product, process, and organisation must be considered when studying complex product development. this connection between domains brings increased possibilities with co-construction, necessity of new competences, and of which potential problem within system integration. these problems have been identified, but not been analysed in detail for mechatronic products (epping eppinger et al. 2001, yan och sharpe 1994, gausemeier et al. 2001, wikander et al. 2001). today, model based development is regarded as a possible solution to theses problems with expensive test and verify, requirement on rapid development and necessity of product renewal. the research in this filed has often a perspective which is restricted to one or one pair disciplines. a summery over the research around model based development within embedded control system gives a roadmap which is taken out of eu-network artist (artist 2003). there are similar research efforts in usa (for example, darpa-project mobies 2003). however, many of these projects are restricted to those aspects which have already been considered (for instance. stress on time correct in mobies).fundamental research among modelling of complex embedded control system and methodology for this purpose are economical. interesting exception is the work done by leveson (2000), rechtin and maier (1997). performed work also around standardising and model format for transference of information between tools. now this work was developed also for that to including software, see sedres (2003) and step-based standard as ap233 (2003).to avoid sub-optimization within mechatronic development, the development of different subsystems (corresponding different disciplines) must be taken place simultaneously and integrated. in order to solve this problem, it requires new tools for modelling and simulating, see van amerongen et at (2000) and sinha et al (2002). parameter space will be very large, therefore methodology and tools for integrated synthesis are necessary (gausemeier et al (2000), rothfuss, r.et al. (2002).in eus sixth frame program, it planed an application- one integrated project included kth mechatronic- with strong relation to model based development and system integration (project is named sea: “seamless design space exploration for automotive electronics”). research which relates to those questions within the project addressing work methods (processes, organizations form) has mainly showed as technical experience. thats to say, there are many research projects which focused on technical support for cooperation between separated group (see coates m fl 2003 or tamin and dillman 2003). even research in “knowledge management” has focused technique with limited impact, one far too limited sight on knowledge concept. another relevant research handles rather than cooperation and efficient work form, and therefore can help with theory to support analysis for developing outline. there are more sources supporting necessity of integration between internal operators in a company. there is one strong relation between crossway function cooperation and a successful product development, as confirmed by griffin (1997), kahn (2001), and olson et al (2001). actual limitation in many of those studied sources are themselves context, for example, cooperate construction/production/market was touched but seldom cooperated among different disciplines.modelling tools:a large number of efforts have been made to improve mbd of automotive products, intending to raise the level of abstraction at which systems are specified and designed, and to provide tools that assist in transferring such designs to operating systems. this progress experienced a change from assembly languages to high-level programming languages and more recently graphical system representation such as matlab/simulink and unified modeling language (uml), which are two approaches widely used in mbd. as well, the object oriented concepts of uml are covered by other approaches. given that uml is given a new version (uml 2.0) as well as new tools, it thus is going to bring a new progress.some of other modelling approaches have been discussed from different views mainly differ in the type of approaches being targeted, the coverage and levels of details and the comparison framework. these modelling tools are briefly listed in following: acme, lustre, metah, rapid, sdl, unicon, vcc (chen dejiu, 2004, elkhoury jad and m. trngren, 2001, l. petersson, 2002.p.c. clements, 1996, r. wieringa, 1998, n. medvidovic, and r.n taylor, 2000).related networks and organizations: snart, artes, artist, ifac, incose, omg. see their homepages to find related conferences information. approachesto take this step in integrated products, embedded control system and programs are necessary, but theories, methods, and tools are lacking. the knowledge, especially respect to complex composite products is partly existed but further research efforts are demanded. the research approach includes five subprojects (dp 1-5) as shown in following:dp 1. case study that presents development of one or eventually more complicated system comprehensive functions/products at vcc, specially with efforts on models, model usage, use of competence, tools usage. the study will be completed with existed knowledge to decide what requirements should be put on the modelling framework, development methodology, development organization and tools support.dp 2. development of a modelling framework which comprise the most important subsystem and characteristics according to earlier experience (chen and trngren, 2001) and based on the case study mentioned above. modelling framework describes how subsystem, components and property can be structured in a number view (sub-model) which is directly connected to different design and analysis purpose, for example, optimization of function allocation and design of computer architecture with respect to physical properties, performance, security and cost. framework describes also how this view related to and affects each other, and also defines fundamental concepts and terminology. modelling frameworks thus constitute the foundation to be able to formalize description of mechatronic system and specify what models should be contained for possible analysis (for example, simulating) and synthesizer (algorithm development) over domain boundary. industrial case study will be performed to refine existed modelling frameworks. the relation to present research and standardisation activities will be examined (for example: respect to ap233, eastadl, aadl). then an updated framework will be developed to test in new case studies.dp 3. methodology for development of mechatronic system. this methodology is required to facilitate the project planning, decision making, assessment of competence requirement and information transference, to system integration planning, and also to support default searching. existed experiences around methodology for development of mechatronic products and knowledge about research front in this area will be used to refine a methodology for development of mechatronic products. this will be performed through testing, evaluating and improving present methods in concrete case study.dp 4. implementation of one case study of organization form and development processes respecting development of system or subsystem within vcc. the case study will include observation of in disciplines and cross-discipline work groups, and interview. the case study could be complemented with questionnaire over more companies which have similar complex problems. the study comes to describe the current position and embarrassed work method which gives effective improvement by competence integration.dp 5. one case study at vcc over the restricted subsystem from which two above components applied. in the case study, we will make use of existed tool prototypes (el khoury and trngren, 2001) which will be further developed in this project and collaborated with another research project. then results are going to be analysed and conclusions will be drawn.both dp 1 and dp 2 contain development of tool prototypes from the developed tool prototypes in the research group. computer based tool support is an assumption for a model based method and also requires management of model data and new type of products data. in general how the new attack method is going to affect the coming pdm system is surveyed and documented in the project. this will go in the cooperation with ivf as described in previous.reference:1. ap233, 2003: /ap233/ap233-overview.html2. (artist 2003). roadmaps for embedded software and systems, artist (advanced real-time systems information society technologies), ist-2001-34820, /roadmaps/ directlink.html.3. chen dejiu and trngren martin (2001). towards a framework for architecting mechatronic software systems. in proceedings of the 7th ieee int. conference on engineering of complex computer systems, skvde, sweden, june 11-15, 20014. chen dejiu (2004). systems modelling and modularity assessment for embedded computer control applications. doctoral thesis.5. coates, g., duffy, a.h.b., whitfield, r.i. & hills, w., (2003) a methodology for prospective operational design co-ordination, proceedings from the iced 03, international conference on engineering design, stockholm, august 19-21, 2003.6. east-eaa 2003: ref: /7. elkhoury jad, trngren martin. towards a toolset for architectural design of distr