1 / 61

TDT4252 Modelling of Information Systems Advanced Course

TDT4252 Modelling of Information Systems Advanced Course. Sobah Abbas Petersen Adjunct Associate Professor sap@idi.ntnu.no. Overview of lecture today. Product Modelling Interoperability Based on the following articles:

silvio
Download Presentation

TDT4252 Modelling of Information Systems Advanced Course

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. TDT4252Modelling of Information SystemsAdvanced Course Sobah Abbas Petersen Adjunct Associate Professor sap@idi.ntnu.no Lecture 8: Product Modelling

  2. Overview of lecture today • Product Modelling • Interoperability Based on the following articles: A08: Krause et al. 1993, Product Modelling, Annals of the CIRP, Vol. 42(2). A09: Jørgensen, H. D., Karlsen, D. Lillehagen, F. Product-based Interoperability – Approaches and Requirements. Lecture 8: Product Modelling

  3. From lecture on perspectives to conceptual modelling • Structural • Functional • Behavioral • Rule-oriented • Object-oriented • Social communication • Actor/role-oriented Perspectives of an enterprise Lecture 8: Product Modelling

  4. Challenge Develop new products that have the shortest lead-time, highest quality and lowest cost, with optimal lifecycle considerations. • New product development strategies. Lecture 8: Product Modelling

  5. New Product Development Strategy “Why change when flying high?” • Boeing’s action plan (1993): • Cut costs by 25% to 30% by year 2000. • Speed up manufacturing time for the 737 from 13 months to 6 months and gain similar cycle time improvements on other models. • Cut inventory, moving toward a just-in-time system. • Train the entire work force in "competitiveness". Over 15,000 managers have completed a four-day course. • Bring customers and suppliers into the once-secret process of designing new airplanes. Lecture 8: Product Modelling

  6. IT’s importance to industry • Key in reducing time to market • Support dealing with the complexity of the task and engineering • Operations management • Manage inventory (>132,000 parts, 3,000,000 rivets, screws, etc.) Lecture 8: Product Modelling

  7. Redefine entire Business Process • Redefine the design and production process of the aircraft: • Computerised from concept to prototype • Use CAD/CAM – to design as three-dimensional, solid images and simulates how all these parts fit and work together. • Creation of design teams, the sharing of the information with suppliers and to some extent with customers. • extensive use of cross-functional design-build teams and concurrent engineering. • IT played a significant role in all these! Lecture 8: Product Modelling

  8. Product Modelling in the Evolution of Product Development Individualcraftsmanship industrialproduction Lecture 8: Product Modelling

  9. Product Modelling in the Evolution of Product Development For mal design methods: general design processes, has value in teaching design Lecture 8: Product Modelling

  10. Product Modelling in the Evolution of Product Development Knowledgeprocessing, computer-basedsimulartons Demand for integrated instead of isolated product development practice  product models and process chains. Computer-aided Design (CAD): 2D-> 3D, Lecture 8: Product Modelling

  11. A fundamental requirement • The need for advanced information technologies to integrate and coordinate various life-cycle considerations during the product development activities. • Central issue: product modelling, which generates an information reservoir of complete product data to support various activities at various product development phases. Lecture 8: Product Modelling

  12. Terminology and Concepts • Product: • Materialised, artificially generated object or groups of objects which • Model (in the context of CAD/CAM): • Contains relevant information including data, structures and algorithms. • Product Model: • The logical accumulation of all relevant information concerning a given product during the product lifecycle. • Product Modelling: • Generates an information reservoir of complete product data to support various activities at different product development phases. • Key factor in to support product development strategies. • Must deal with other manufacturing related models such as factory models, equipment models, resource models. Lecture 8: Product Modelling

  13. Terminology and Concepts • Product Life-cycle • All phases in the life of a product – from raw materials to recycling. • Product Development Activity: • Refers to those stages from an initial concept to a proven prototype of the product. Lecture 8: Product Modelling

  14. Complete Product Lifecycle concerns Lecture 8: Product Modelling

  15. Product Modelling • Product modelling, in its complete sense, consists of two inter-related aspects: • Product models • Process chains: commonly referred to as product development workflows or product modelling processes. • Represents the product modelling processes consisting of a set of technical and management functions required to transfer initial ideas to final products. • Should represent all tasks to be performed in a product lifecycle: product development workflows, production workflows, maintenance tasks and recycling considerations. Lecture 8: Product Modelling

  16. Product Models • Results (intermediate and final) through a process chain are recorded (using IT support) as product model data. • Product models can contain different types of data. • Product models can contain sub-models or partial models. e.g. • Functional model: supports the functional phase of the process chain. • Product structure information. Lecture 8: Product Modelling

  17. Contents of Product Models and Sub-models Lecture 8: Product Modelling

  18. Visualization of the ProductConcurrent Engineering using multidisciplinary models (source: Airbus ACE) By courtesy of Nicolas Figay, EADS Lecture 8: Product Modelling

  19. Requirements of Product Modelling Technology • Present Actual Data: • It is necessary that all activities performed during different phases of a process chain have the same and identical data available to them about a particular subject. • Facilitate product documentation: • Historical perspective. • To keep the rationale of the design in order to reconstruct the decision process at a later stage. • An important part of the corporate memory. • Offer decision alternatives: • Minimise unnecessary iterations through the process chain. • Should support the representation and exploration of process and product alternatives in order to reduce costly iterations and increase product flexibility: “tolerances” of product models at the conceptual level. Lecture 8: Product Modelling

  20. Example of a Product Modelling System Architecture Lecture 8: Product Modelling

  21. Technological Challenges in Product Modelling (1) • Consistency (syntactic and semantic) • Syntactic: information representations checked against a predefined form. • Semantic: more challenging. Some rules can be used to check if the values of some parameters are within predefined allowances. • Redundancy: • Traditionally, this is not desirable (information modelling). • In product modelling, this could be a way to represent decision alternatives. • Controlled redundancy is a term used for this. • Reliability: • Necessary for consistency and redundancy. • Need to achieve user acceptance. Lecture 8: Product Modelling

  22. Technological Challenges in Product Modelling (2) • Efficiency: • Dependent on a variety of factors: hardware tools, existing software systems, implementation strategies. • Security: • Security of information has to be assured: • Some of the data in product models may contain company strategy related information. • A data protection strategy is necessray. Lecture 8: Product Modelling

  23. Types and Example of Product Models • For complex products (e.g. a ship or an airplane), there is a need to store different types of engineering related information about a product. Hence, there is a need for different types of product models: • Structure-oriented • Geometry-oriented • Feature-oriented • Knowledge-based • Integrated Lecture 8: Product Modelling

  24. Structure-oriented Product Models • Product structure – a description of a product’s breakdown. • References to the data that represents the product structure are stored. • Classification, variants Lecture 8: Product Modelling

  25. Geometry-oriented Product Models • Primary purpose is to represent the shape of a specific product. • Typically supported by Computer-aided Design (CAD) systems. • Need additional support to store non-geometric information such as organisational or technical attributes or other product-related information. Lecture 8: Product Modelling

  26. Feature-oriented Product Models • An extension of geometry-oriented product models. • Provides the ability to represent often used shape patterns as coherent geometric items, called form features. • Form features represent shape patterns which have a specific semantic meaning concerning the design or manufacturing process. Lecture 8: Product Modelling

  27. Knowledge-based Product Models • Uses AI techniques, O-O, rule-based reasoning, etc. to support storage of human expertise explicitly and experiences concerning products, proceses and factory environments. • Provides the ability to build taxonomies of products or processes as objects that can be stored in a knowledge-base. • Knowledge about earlier design alternatives and processes can be stored. • Enhances the capabilities of information support during the product modelling process. Lecture 8: Product Modelling

  28. Integrated Product Models • Covers the abilities of structure, feature, geometry-oriented and knowledge-based product models. • All types of product information are stored. • Semantic integration: basic functionality offered by computer applications for design, planning and production are extended with the semantics needed to support real enterprise integration. Lecture 8: Product Modelling

  29. Standardization • Integrated product models require standardization: • Neutral data formats for representation and exchange of product data. • One such standard is ISO 10303: STEP (Standard for the Exchange of Product Model Data). • Goal of STEP: • Complete and system independent representation of all product-related data during a product lifecycle. Lecture 8: Product Modelling

  30. Types and Examples of Process Chains:Process Chains without Product Models Media incompatibilities, Manual actions and manual process control Interface between tasks realised by direct communication links, there may be redundancy Lecture 8: Product Modelling

  31. Process Chains with process Models Additional data describing the progress and actual status of the product development activities integrated into the product model Actual data for all tasks: changes will be notified to all tasks, redundancy control, consistency, data available for documentation Lecture 8: Product Modelling

  32. Parallel Process Chains with Integrated Product Models • Product Model based process chain controlled by parallel project management system. • Supports parallel processes to happen within product modelling. • Concurrent engineering • Teams can work in parallel. • An example: Boeing 777: 3.5 Tera Bytes of data. This data is accessed in parallel by several teams of users. Lecture 8: Product Modelling

  33. Product Modelling to Support Digital Pre-assembly Lecture 8: Product Modelling

  34. Virtual Aircraft for Early Involvement of Downstream Activities Lecture 8: Product Modelling

  35. Ideally, we would like to move towards a complete digital representation of all product and process related information to support product modelling activities. Lecture 8: Product Modelling

  36. Research and Education Demands • Segmented Total Product Model: logically related smaller components for easier management and higher efficiency. Interior Model: Represents the information of a specific product, its variants, costs, etc. Exterior Model: The generic portion of the product model. Lecture 8: Product Modelling

  37. Workbench: SWIFT • SWIFT (System Workbench for Integrating and Facilitating Teams) • System: a large complex task • Workbench: an intelligent, virtual and “active” worktable” existing on a networked computing environment that can aid group problem-solving tasks and facilitate the usage of different specific computer tools by engineering teams. Lecture 8: Product Modelling

  38. Industrial Demands • Shortest lead-time, highest quality and lowest cost, with optimal lifecycle considerations. • Introduce the concept of product Modelling into industrial practice. • Involve end-users as early as possible. • Compatibility with existing hardware and software. • Usage of existing product data has to be ensured. • Easy maintenance and extendibility. • High degree of hardware independence. Lecture 8: Product Modelling

  39. Product Modelling: Summary • We have looked at the domain of product modelling. • Different types of product Models • Product Models and Process Chains • Requirements for IT • Challenges Lecture 8: Product Modelling

  40. Discussion • How can IT support product modelling? • What are the main challenges for IT systems to support product modelling? • Can you draw parallels to IT systems development? Lecture 8: Product Modelling

  41. Interoperability (1) • Definition: • Interoperability is a property of a product or system, whose interfaces are completely understood, to work with other products or systems, present or future, without any restricted access or implementation. • The ability of two or more systems or components to exchange information and to use the information that has been exchanged (IEEE). • Initially defined for IT systems, considering exchange of information. But this is not enough. Lecture 8: Product Modelling

  42. Interoperability (2) • Syntactic Interoperability: • If two or more systems are capable of communicating and exchanging data, they are exhibiting syntactic interoperability. Specified data formats, communication protocols and the like are fundamental. XML or SQL standards are among the tools of syntactic interoperability. • Semantic Interoperability: • The ability to automatically interpret the information exchanged meaningfully and accurately in order to produce useful results as defined by the end users of both systems. To achieve semantic interoperability, both sides must refer to a common information exchange reference model. • Business Interoperability: • The ability for diverse business processes to work together. Lecture 8: Product Modelling

  43. Product Based Interoperability • Based on the article: • A09: Jørgensen, H. D., Karlsen, D. Lillehagen, F. Product-based Interoperability – Approaches and Requirements. Lecture 8: Product Modelling

  44. Product Based Interoperability It is about removing barriers to • Interdisciplinary knowledgesharing and cooperative problem solving. • Information logistics and quality management. • Dataexchange between companies and targeted applications for different disciplines. Lecture 8: Product Modelling

  45. Product Design Challenges Voices of Customers Voices of Business Product Design Voices of Technology Concept by courtesy of the Winquist Laboratory, Gothenburg. Lecture 8: Product Modelling

  46. Product Properties (Eder&Hubka)‏ http://www.cden2006.utoronto.ca/data/10021.pdf Lecture 8: Product Modelling

  47. Design Dimensions Lecture 8: Product Modelling

  48. Product Based Interoperability Profiles • Product Document Exchange and Management • Product Data Exchange through mapping (EAI) • Reference models and Semantic Mediation • Shared Product Information Repository (PDM) • Federated Knowledge Repository (Pragmatic web) Lecture 8: Product Modelling

  49. Product Document Management • Manual data processing • Email exchange or document management • Documents include text, spreadsheets, engineering drawings, etc. Lecture 8: Product Modelling

  50. Product Data Mapping • Local applications for automated data processing • Data to data mapping, APIs and web services • Enterprise Application Integration (EAI) Lecture 8: Product Modelling

More Related