1 / 29

Hichem M. Geryville Lumière University of Lyon, France University of the Aegean, Greece

Architecture of Product Information Exchange: Transformation and Adaptation of Knowledge within Supply Chain Context. Hichem M. Geryville Lumière University of Lyon, France University of the Aegean, Greece Hichem.geryville@univ-lyon2.fr. Plan. Introduction Context & Problematic PLM & SCM

osanna
Download Presentation

Hichem M. Geryville Lumière University of Lyon, France University of the Aegean, Greece

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. Architecture of Product Information Exchange:Transformation and Adaptation of Knowledge within Supply Chain Context Hichem M. Geryville Lumière University of Lyon, France University of the Aegean, Greece Hichem.geryville@univ-lyon2.fr

  2. Plan • Introduction • Context & Problematic • PLM & SCM • The Product-Process-Collaboration-Organisation Model • The Multiple Viewpoints Approach • The Architecture • Example • Conclusion Cerral/Prism@ Laboratory

  3. Introduction • Within the actual competitive world, enterprises are ever more stressed and subjected to high markets requests. • Customers are becoming more and more pretentious in terms of products quality and delivery times. • The best product, at the lowest price, at the right time and into the right place is the only success-key for the modern enterprise. • The increasing complexity of the products’ definition pushes the companies to take care of their competencies and externalize complementary knowledge. Cerral/Prism@ Laboratory

  4. Context & Problematic • Enterprises have to focus on their core competences in order to improve the efficiencies and to reduce the inefficiencies → Multidisciplinary Collaboration (MC). • The MC between different actors depends on exchanging and sharing adequate information on the product, related processes and business throughout the product’s lifecycle. • The effective capture of information, and also its extraction, recording, exchange, sharing, and reuse become increasingly critical, especially when one considers the collaborators’ points of view. Cerral/Prism@ Laboratory

  5. Objectives • This work is focusing on integration of product, process, collaboration and supply chain organization modeling in a collaborative framework. • …To improve more and more the definition of the product development model. • …To increase the quality of the exchanged information by using “multiple viewpoints” approach, especially to capture the actors’ interest on the product information. • …To facilitate transformation/adaptation of knowledge/information from one actor to another, following his/her viewpoints on product (objective and focus) Cerral/Prism@ Laboratory

  6. PLM: Product Lifecycle Management Disposal Ideation Product in Use Design Organization Manufacturing Design Design Evaluation Detailed Design Cerral/Prism@ Laboratory

  7. SCM: Supply Chain Management Cerral/Prism@ Laboratory

  8. The Product-Process-Collaboration-Organization Model • In MC oriented PLM and/or SCM, we need to define a general core model which includes the information on the product (geometry design, manufacturing data, managing data, etc.), on the process, on the collaboration, and on the structure of the supply chain organization followed. • Our first objective on proposing the PPCO model is to provide a base-level information model which is open, non-proprietary, generic, extensible, independent of any product development process and a generic Supply Chain collaboration, able to capture the whole engineering and business context. • This model is composed of four main parts interconnected directly or indirectly (by using viewpoints approach) such, product, process, collaboration, and organization. Cerral/Prism@ Laboratory

  9. The Product-Process-Collaboration-Organization Model • Specific vocabulary for product lifecycle data & supply chain data Schema • Meta-data for product lifecycle data • Meta-data of Product, Process, Collaboration, and Organisation (PPCO) • Meta-data of interaction among PPCO • Product–Process • Process–Collaboration • Collaboration–Organization Meta-data of product lifecycle data Our vision Content-data of product lifecycle Changeability Dynamic Static Characteristics Organization Collaboration Process Product BOL MOL EOL Chronological Order Cerral/Prism@ Laboratory

  10. The Product-Process-Collaboration-Organization Model The Product model Cerral/Prism@ Laboratory

  11. The Product-Process-Collaboration-Organization Model The Product model Cerral/Prism@ Laboratory

  12. The Product-Process-Collaboration-Organization Model The Process Model Our process model is based on SCOR model (Supply Chain) and IDEF3 Cerral/Prism@ Laboratory

  13. The Product-Process-Collaboration-Organization Model The Organization and Collaboration Models Cerral/Prism@ Laboratory

  14. The Viewpoints Approach Enterprise Information Technology Computation Engineering The RM-ODP viewpoints ODP System Business aspects who? why? Information, changes, constraints Hard- and software components That implement the system Configuration of objects interacting at interfaces Mechanisms and services for distribution transparencies Cerral/Prism@ Laboratory

  15. The Viewpoints Approach • In ODP viewpoint model, we are interesting on the enterprise and information viewpoints, are respectively with organizational requirements and information modeling. • From these two kinds of viewpoints, we can say that the viewpoints framework provides an infrastructure for capturing and organizing product information extraction within multidisciplinary collaboration. • Our definition of a viewpoint is “an object encapsulating cross-cutting and partial knowledge about activity, process, and domain of discourse, from the perspective of a particular actor, or collaboration-team, on the processes of product development”. Cerral/Prism@ Laboratory

  16. The Viewpoints Approach • We define our own definition of viewpoint, and we take into account the way we use them. So we prefer the definition of GARLAN [Garlan 87] who says that “a viewpoint can be defined as a simplifying abstraction of a complex structure… suppressing information not relevant to the current focus”, or of Easterbrook [Easterbrook 93]: “viewpoint represents the context in which a role is performed”. • So our notion of viewpoint must permit: • Simple seek of information within product/process information, • Visualization of pieces of information relative to a given process/activity, • Comparison of information between viewpoints. Cerral/Prism@ Laboratory

  17. The Viewpoints Approach • Our definition of viewpoint can be defined as a subset of information concerning the description of a product. This viewpoint is characterized by a context, which allows locating the pieces of information that we can describe, and an actor, that let us know what degree of importance we can give to the information of the viewpoint. Cerral/Prism@ Laboratory

  18. The Viewpoints Approach The proposed Viewpoint definition Cerral/Prism@ Laboratory

  19. The Full Architecture Cerral/Prism@ Laboratory

  20. Example Scenario 1: Supply Chain with externalization of Design Cerral/Prism@ Laboratory

  21. Example Scenario 1: Supply Chain with externalization of Design Cerral/Prism@ Laboratory

  22. Example Scenario 1: Supply Chain with externalization of Design Cerral/Prism@ Laboratory

  23. Example Scenario 1: Supply Chain with externalization of Design Cerral/Prism@ Laboratory

  24. Example (con.) Scenario 1: Supply Chain with externalization of Design Cerral/Prism@ Laboratory

  25. Example (con.) Scenario 1: Supply Chain with externalization of Design a. Product architecture Viewpoints c. Development supply-chain organization b. Development process Cerral/Prism@ Laboratory

  26. Conclusions • The proposed framework is based on four layers and instead to capture, exchange, share and reuse information within supply chain context. • The viewpoints approach was integrated to capture the actors’ interest on their collaboration over the product lifecycle, and to optimize the exchange. • With the integration of the both proposition, the system particularly ensures: • The integration and consolidation of information coming various sources, and its filtering, transformation and adaptation to various viewpoints. • Optimization of time restitution. • Information traceability. Cerral/Prism@ Laboratory

  27. References (1/2) • Bowman, H.; Derrick, J.; Linington, PF.; Steen, MWA.: “Cross viewpoint consistency in Open Distributed Processing,” in A. Finkelstein and I. Sommerville (Eds.), IEE Software Engineering Journal, Special Issue on Viewpoints, Vol. 11, No. 1, pp. 44–57, 1996. • Bronsvoort, WF.; Noort, A.; Van Den Berg, E.; Hoek, GFM.: “Product development with multiple-view feature modeling”, Proc. of the IFIP Conference on Feature Modeling and Advanced Design-for-the-Lifecycle Systems, Valenciennes, France, June 2001. • Brown, J.: “The PLM program, an incremental approach to the strategic value of PLM”, http://www.technologyevaluation.com, 2003. • Bucciarelli, L.: “Between thought and object in engineering design”. Design Studies 23, 2002, pp 219-231. • Drews, Marino O. : “Raisonnement Classificatoire dans une représentation à objets multi-points de vue”, PhD Thesis, University of Joseph Fourier Grenoble 1, 4 October, 1993. • Easterbrook, S.: “Domain Modelling with Hierarchies of alternative viewpoints”, in Proceedings of IEEE International Symposium on Requirements Engineering, January 4-6, San Diego, California, 1993. • Finch, I.: “Viewpoints – Facilitating expert systems for multiple users”, In Proc. of the 4th International Conference on Database and Expert Systems Applications, DEXA’93, Springer-Verlad (Ed.), 1993. Cerral/Prism@ Laboratory

  28. References (2/2) • Garlan, D.: “Views for Tools in Integrated Environments”, Proceedings of TOOLS’87, pp. 313-343, 1987. • Geryville, Hichem; Ouzrout, Yacine, Bouras, Abdelaziz; Nikolaos, Sapidis: “A collaborative framework to exchange and sharing product information within a supply chain context”, in Proceeding of IEEE, International Conference on Machine Intelligence, 2005, pp. 195-202. • Gzara, Lilia; Rieu, D.; Tollenaere, M.: “Product information systems engineering: an approach for building product models by reuse of patterns”, Robotics and Computer Integrated Manufacturing, vol. 19, 2003, pp. 239-261. • Hoffman, CM.; Joan-Ariyo, R.: “Distributed maintenance of multiple product views”, Computer-Aided Design, vol. 32, 2000, pp. 421-431. • ISO/IEC: RM-ODP, Reference Model for Open Distributed Processing. International Standard ISO/IEC 10746-1 to 10746-4, ITU-T Recommendations X.901 to X.904. 1997. • Ribière, Myriam: “Using viewpoints and CG for the representation and management of a corporate memory in concurrent engineering”. ICCS’98, Springer-Velag, 1998, pp. 94-108. • Sudarsan, Rachuri; Fenves, SJ.; Sriram; RD.; Wang,F.: “A product information modelling framework for product lifecycle management”, Computer-Aided Design, 2005, in press Cerral/Prism@ Laboratory

  29. End of Presentation Questions ??? Cerral/Prism@ Laboratory

More Related