Architecture of Product Information Exchange: Transformation and Adaptation of Knowledge within Supply Chain Context Hichem M. Geryville Lumière University

Architecture of Product Information Exchange:

Transformation and Adaptation of Knowledge within Supply Chain

Context

Hichem M. GeryvilleHichem M. Geryville

Lumière University of Lyon, FranceLumière University of Lyon, France

University of the Aegean, GreeceUniversity of the Aegean, Greece

[email protected] [email protected]

Lyon, February 2, 2006 Cerral/Prism@ Laboratory2

LOGOPlan

1. Introduction

2. Context & Problematic

3. PLM & SCM

4. The Product-Process-Collaboration-

Organisation Model

5. The Multiple Viewpoints Approach

6. The Architecture

7. Example

8. Conclusion


LOGOIntroduction

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.


LOGOContext & 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.


LOGOObjectives

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)


LOGOPLM: Product Lifecycle Management

Disposal

Ideation

Design Organization

Design

Detailed Design

Design Evaluation

Manufacturing

Product in Use


LOGOSCM: Supply Chain Management


LOGOThe 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.



Schema

Meta-data of product lifecycle data

Content-data of product lifecycle

–Specific vocabulary for product lifecycle data & supply chain data

–Meta-data for product lifecycle dataoMeta-data of Product, Process, Collaboration, and Organisation (PPCO)oMeta-data of interaction among PPCO

Product–ProcessProcess–CollaborationCollaboration–Organization

Ou

r vision

Characteristics

Organization

Collaboration

Process

Product

BOL MOL EOL Chronological Order

Changeability

Dynamic

Static


LOGOThe Product-Process-Collaboration-Organization ModelThe Product model


LOGOThe Product-Process-Collaboration-Organization ModelThe Product model



Our process model is based on SCOR model (Supply Chain) and IDEF3

The Process Model


LOGOThe Product-Process-Collaboration-Organization ModelThe Organization and Collaboration Models


LOGO

ODPODPSystemSystem

EnterpriseEnterprise

ComputationComputation

InformationInformation

TechnologyTechnology

EngineeringEngineering

The RM-ODP viewpoints

Hard- and software componentsThat implement the system

Mechanisms and services for distribution

transparencies

Information, changes,

constraints

Business aspects

who? why?

Configuration of objects

interacting at interfaces

The Viewpoints Approach


LOGO

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”.



LOGO

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.



LOGO

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.



LOGOThe Viewpoints ApproachThe proposed Viewpoint definition


LOGOThe Full Architecture


LOGOScenario 1: Supply Chain with externalization of DesignExample








LOGOScenario 1: Supply Chain with externalization of DesignExample (con.)

Number Quantity Part Number Product Description

1 1 MF1647B-FWE CP Vessel Body, 316L Stainless Steel

2 1 MF1647A-FWE CP Vessel Cover, 316L Stainless Steel with Lifting Eye

3 1 MF1645C-FWEGASKET, 1/8" [3mm] Thick Custom Cut for 10" [250mm]150# ANSI Flange, Gylon Blue 3504

6 C1091-55-0.077Cyclone, CP1, 316L SS Castings, Machined and Welded,0.188 [5mm] APEX ID, 0.077 SQ IN [50mm SQ] INLET,0.281" [7mm] Vortex Finder ID

4 8 C7090G-RV-D Gasket, 75 Durometer Viton

5 8 C7265-1-SS Washer, 316 Stainless Steel

6 2 C9411-SS Cyclone Blank, Machined from Billet, CP1, 316 SS

7 16 C7090G-RV-E Gasket, 75 Durometer Viton

8 8 C1762-1-5Z4 Bushing, Non Threaded, Machined 316L Stainless Steel

9 1 MF1647D-FWECP Vessel Capture Plate, 316L Stainless Steel, for 8 ModelCP1 CP Vessel

10 5 STD-0H13UC02ZGZStud, 1/2-13UNC x 2" Long, 316 Stainless Steel, A193-B8MMaterial

11 12 STD-0N09UC05ZGZStud, 7/8-9UNC x 5" Long, 316 Stainless Steel, A193-B8MMaterial

12 1 C4026-C8-0.375 Apex TIP, C8 96% Aluminia Ceramic, 0.375in [9.5mm] ID

13 1 C6019G-RN Gasket, 60 Durometer Viton

14 1 C1331-SSCentering Ring, 304 Stainless Steel, for CA026 APEXAssembly

15 1 C7715-SS Clamp, 316 Stainless Steel

16 24 NUT-0N09UOHH2HZNut, 7/8-9UNC x 5" Long, 316 Stainless Steel, A194-8M,with Bearing Surface

17 5 NUT-0H13UC02ZHZNut, 1/2-13UNC x 2" Long, 316 Stainless Steel, A194-8M,with bearing Surface

18 2 9F-PLUG-0.25-SS Pipe PLUG, 1/4" NPT, 316 SS

Bill of Material: C1091-SS-0.077

Number Quantity Part Number Product Description

19 1 C1075-SSCyclone Body, CPA Cyclone Body, S16L SS Casting,Machined for Welding

20 1 C1077-SS-0.188APEX, CP1 Cyclone Lower APES Section, 316L Casting,Machined for Welding, 0.188 [4mm] APEX Hold Diameter

21 1 C1071-SS-0.077Cyclone Head, CP1 Cyclone Head, 316L SS Casting,Machined for Welding, 0.077 SQ IN [50mm SQ] INLET,0.281" [7mm] ID Vortex Finder


LOGOScenario 1: Supply Chain with externalization of DesignExample (con.)

Viewpoints

a. Product architecture

c. Development supply-chain organization

b. Development process


LOGOConclusions

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.


LOGOReferences (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.


LOGOReferences (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


LOGOEnd of Presentation

Documents

Architecture of Product Information Exchange: Transformation and Adaptation of Knowledge within Supply Chain Context Hichem M. Geryville Lumière University