fbpx

UML Approach for Modeling and Specifying the Product Structure and Workflow


Call for Papers Engineering Journal, May 2019

Download Full-Text PDF Cite this Publication

Text Only Version

UML Approach for Modeling and Specifying the Product Structure and Workflow

Shanmugapriya S1

Department of Production Engineering PSG College of Technology Coimbatore, India

Arunprakash R2

Department of Production Engineering PSG College of Technology Coimbatore, India

Abstract- This project deals with modeling and specifying the product structure and workflow of pump assembly based on the UML Approach. It highlights the added value of using the object oriented approach for modeling, specifying and implementing the whole management of pump assembly about its entire lifecycle. It also provides the integration of the various dimensions of the submersible pump manufacturing system by specifying product, process and resource data.

Keywords Object oriented modelling; product structure; workflow

  1. INTRODUCTION

    The requirement of single and secured storage of product data of pump enables an early access or allows to share product data with its main contractors and suppliers. The main benefits of using Unified Modeling Language (UML) in an extended pump assembly approach are given below: 1. Reducing lead time and non-quality according to predefined processes, 2. Sharing the right data between the relevant users group regarding the pump development to minimize the iterations, and 3. Improving reactivity and customer supports with a high level of traceability and an efficient product configuration management.

  2. RESEARCH GOAL

    UML has been chosen for several reasons. First, it provides complete modelling notation for specifying the product breakdown structure (parts) with related product data (documents). Second, it provides an efficient language for modelling generic workflow with activities and transition criteria before their implementation in a workflow engine.

  3. PRODUCT DATA MANAGEMENT

    A PDM (product data management) system manages and stores product design, manufacturing and support data. Two important functionalities of such a system are:

    Product structure manager: It stores the whole product data. It manages the bills of material (BOM) and the product configurations. It helps in providing functionalities for linking the various parts and documents in the product structure.

    Workflow management: It routes documents to single or multiple users in-box. Users need to perform a predefined task on the routed document. Workflow can have complex network of task flow to implement a business rule. It can route any type of a document. It controls the flow of the package through the business rule network.

    1. About UML

      UML is given by

      Unified – Result of unifying the information systems and technology industrys best engineering practices.

      Modeling- A number of models are used to describe the system.

      Language-Not simply a notation for drawing diagrams, but a complete language for capturing semantics about a subject and expressing the same for purpose of communication.

    2. UML Diagrams

    A diagram represents a particular view into the model.

    • UML Diagrams comprises of model elements.

    • A single model is a complex entity and is difficult to present meaningfully within a single diagram.

    • UML defines a number of diagrams so that focus on different aspects of the system independently.

    Class diagrams: Shows a set of classes, interfaces and collaborations and their relationships.

    Object diagrams: Shows a set of objects and their relationships.

    Use-case diagrams: Serve to organize the use cases and actors that encompass a system's behavior.

    State-chart diagrams: Focuses on the changing state of a system driven by events.

    Activity diagrams: Focuses on the flow of control from activity to activity.

  4. PROBLEM DEFINITION

    Time to market, high security level, reduced design lead time and enhanced level of quality are becoming the most important business and strategic key elements for product development and manufacturing. Product data management system manages and stores product design, manufacturing and support data. For defining and modeling the product data clearly, the UML (Unified Modeling Language) is used. UML gives a clear understanding about the product structure and workflow and communicates well in heterogeneous environment. By this method, the modeling and integration of product structure and workflow is identified for the Pump Manufacturing. This helps in reducing the complexity of the assembly and making a better design.

    turning has to be matched for right welding. There are two product breakdown structure: they are joint product and mixed product breakdown structure.

    The joint product breakdown consists of separate viewpoint for design and manufacturing breakdown. Thus it is complicated to manage consistency between data throughout the lifecycle.

    The mixed product breakdown consists of single viewpoint for both the design and manufacturing breakdown. It avoids duplicating data: the shared data integrates into the common part of the product breakdown.

    GRIND : detail part

    I : impeller

    I : impeller

  5. PRODUCT STRUCTURE AND WORKFLOW MODELING

S : submersible pump

radial flow pump = 1

SH : shaft

TURN : detail part

WELD : detail part

WELD : detail part

CUT : detail part

  1. Use Case Diagram

    The tasks of each involved person have been identified in a use case diagram. This has been carried out based on

    M : module v6 pump = 1

    SU : suction housing

    BRAZE : detail part

    SOLDER : detail part

    ED : detail part

    several interviews of design team members: quality manager, process manager and design manager. It provide a

    M2 : module v7 pump = 1

    SC : stage casing

    TURN2 : detail part

    fairly good over view of the user needs and design project running based on data modelling. It gives a snapshot of one aspect of the system. A use case may be small or large. It captures a broad view of a primary functionality of the system in a manner that can be easily grasped by non- technical user. The use cases may be decomposed into other use cases.

    S2 : submersible pump2 mixed flow pump = 1

    NRV : NRV body

    D : DOL

    WELD2 : detail part

    TURN4 : detail part

    TURN3 : detail part

    TURN3 : detail part

    MILL : detail part

    TURN5 : detail part

    TURN5 : detail part

    LAP : detail part

    WELD3 : detail part

    GRIND2 : detail part

    TURN6 : detail part

    MILL2 : detail part

    System

    FIXING SHAFT

    <<include>>

    FIXING IMPELLER

    promote

    DESIGN MANAGER

    FIXING STAGE CASING Assembling te parts

    <<include>> demote

    QUALITY MANAG

    CREATE SUCTION HOUSING

    <<include>>

    FIX NRV BODY

    PLACING DOL

    <<include>>

    PROCESS MANAG

    CONNECTING DOL SLEEVE

    System

    FIXING SHAFT

    <<include>>

    FIXING IMPELLER

    promote

    DESIGN MANAGER

    FIXING STAGE CASING Assembling the parts

    <<include>> demote

    QUALITY MANAG

    CREATE SUCTION HOUSING

    <<include>>

    FIX NRV BODY

    PLACING DOL

    <<include>>

    PROCESS MANAG

    CONNECTING DOL SLEEVE

    Fig.2. Object breakdown for design breakdown.

    TURN : detail part

    TURN : detail part

    TURN2 : detail part

    Fig.1. Use case diagram.

    TURN3 : detail part TURN4 : detail part

    T : detail part

    T : detail part

    TURN5 : detail part

    TURN6 : detail part

  2. Product Breakdown Structure

    The product breakdown structure is based on a parts list (including: product, subassemblies and basic components). The product breakdown structure allows the bills of material management and product configurations. Two types of breakdown are as follows:

    S : submersible pump radial flow pump = 1

    M : module

    v6 pump = 1

    M : module

    v6 pump = 1

    G : detail part

    W : detail part

    W : detail part

    WELD2 : detail part

    GRIND2 : detail part

    GRIND2 : detail part

    WELD3 : detail part GRIND : detail part

    1. Design breakdown

    2. Manufacturing breakdown.

      The product breakdown is provided for clear understanding of the product structure. The shaft, impeller, stage casing, suction housing and NRV body are obtained by a same subassembly. In manufacturing breakdown, right objects must be mapped correctly. For example, right

      MILL : detail part MILL2 : detail part

      M : detail part

      M : detail part

      Fig.3. Object breakdown for manufacturing breakdown.

      GRIND : detail part

      TURN : detail part

      D. States of a Document

      The state diagram denotes the present state of the

      SH : shaft

      SH : shaft

      CUT : detail part

      I : impeller

      I : impeller

      WELD : detail part BRAZE : detail part

      D : DOL

      D : DOL

      SOLDER : detail part

      ED : detail part

      TURN6 : detail part

      TURN5 : detail part

      document. The owner of the data is in charge of the document. He promotes or demotes the maturity level. The Various States are:

      • In progress denotes that the data is modified by

        S : submersible pump

        M : module

        radial flow pump = 1

        v6 pump = 1

        T : detail part

        SL : sleeve

        S : submersible pump

        M : module

        radial flow pump = 1

        v6 pump = 1

        T : detail part

        SL : sleeve

        SC : stage casing

        NRV body : NRV body

        GRIND2 : detail part

        MILL2 : detail part MASK : detail part

        TURN2 : detail part WELD2 : detail part

        TURN4 : detail part

        TURN3 : detail part

        MILL : detail part

        WELD3 : detail part

        LAP : detail part

        an activity

        • Shared state denotes that the data is mature to be used by the process as input for other activity.

        • Released state denotes that data may not be modified further in this configuration.

        • Obsolete denotes that the data is unable to be used as input for an activity.

          Fig.4. Object breakdown for mixed product breakdown.

          in progress

          in progress

          submersible pump2

          +mixed flow pump

          +associate()

          +promote()

          +demote()

          submersible pump

          +radial flow pump

          +associate()

          +promote()

          +demote()

          Part

          +maturity

          +last modification

          +copy()

          +cut()

          +paste()

          +associate()

          +promote()

          +open()

          +demote()

          submersible pump2

          +mixed flow pump

          +associate()

          +promote()

          +demote()

          submersible pump

          +radial flow pump

          +associate()

          +promote()

          +demote()

          Part

          +maturity

          +last modification

          +copy()

          +cut()

          +paste()

          +associate()

          +promote()

          +open()

          +demote()

  3. Class Diagram Of Product And Process Structure

promote

promote

demote

demote

obsolete

obsolete

shared state

promote

shared state

promote

module

+v7 pump

+v6 pump

+associate()

+promote()

+demote()

module

+v7 pump

+v6 pump

+associate()

+promote()

+demote()

consist of

released state

released state

consist of

document

+psg pumps

+comment

+last modification date = today

+pump assembly

+editor

+browser

+status

+create()

+rename()

+copy()

+cut()

+paste()

+associate()

+promote()

+demote()

+open()

+check in()

+check out()

+update()

document

+psg pumps

+comment

+last modification date = today

+pump assembly

+editor

+browser

+status

+create()+rename()

+copy()

+cut()

+paste()

+associate()

+promote()

+demote()

+open()

+check in()

+check out()

+update()

consist of

detail part

consist of

+associate()

+promote()

+demote()

+turning()

+milling()

+drilling()

+welding()

+cutting()

+grinding()

shaft

shaft

stage casing suction housing

DOL

stage casing suction housing

DOL

sleeve

sleeve

NRV body

Fig.7. State diagram of a document

consist of

feature

+name

+comment

+creator: manager

+owner

+last modification: date = today

+create()

+rename()

+copy()

+cut()

+paste()

+promote()

+demote()

+open()

+update()

feature

+name

+comment

+creator: manager

+owner

+last modification: date = today

+create()

+rename()

+copy()

+cut()

+paste()

+promote()

+demote()

+open()

+update()

create create

+grinding()

+turning()

+cutting()

+milling()

impeller

+welding()

+brazing()

+soldering()

+EDM()

impeller

+welding()

+brazing()

+soldering()

+EDM()

+turning()

+grinding()

+turning()

+masking()

+turning()

+welding()

+turning()

+turning()

+milling()

+lapping()

+welding()

performer

+name

+data group

+organisation

+process group

+query()

+realize an action()

+import()

+export()

Fig.5. Class diagram for pump product structure

It helps to understand complex links between metadata. The class diagram highlights how the product is structured in the system and how it is used. The product breakdown will be composed of Part class, its sub-classes, performer and Document class. The performer will be able to use classes for carrying out the activity. The process structure consists of action, activity, performer and software part class.

software part

+soft version

+associate()

+promote()

+demote()

+open()

+version with same part no()

+version with different part no()

  1. Activity diagram

    It highlights the flow of activities from the start of the design to completion of the pump assembly. It is represented by a single diagram for overall process.

    design of profile of pump

    mechanical assembly of pump

    YES

    testing the pump

    NO

    design of profile of pump

    mechanical assembly of pump

    YES

    testing the pump

    NO

    performer

    +name

    +data group

    +organisation

    +process group

    +query()

    +realize an action()

    +import()

    +export()

    performer

    +name

    +data group

    +organisation

    +process group

    +query()

    +realize an action()

    +import()

    +export()

    process

    +name

    +comment

    +iteration

    +owner

    +creator

    +instanciate()

    process

    +name

    +comment

    +iteration

    +owner

    +creator

    +instanciate()

    activity

    +name

    in charge of

    +creator

    +relevant data list

    +generic software name

    +duration

    +instanciate()

    Fig.8. Activity diagram of a pump

  2. Workflow Modeling

realizes instanciates

action

+name

+creator

+input relevant data list

+output relevant data list

+software name and version

+status

+start date

+end date

+promote()

+demote()

+add output data()

Fig.6. Object breakdown for pump process structure.

Workflow can have complex network of task flow to implement a business rule. It controls the flow of the package through the business rule network. The main goal is to build the generic process with controlled data for each new product development cycle. This web-based system is implemented by creating the front end of the system

interface using HTML. The part number gives the description of individual parts.

VII. CONCLUSION

The current study aims at highlighting the added value of a UML approach for modeling and specifying the product structure and the workflow. Thus, UML has been chosen for many reasons. First, it provides a complete modelling notation for specifying the product breakdown structure of pump assembly (parts) with related data (documents). Second, it gives generic workflow activities before their implementation in a workflow engine. Finally, UML enables to detail the overall class diagram of the pump system and collaborative design with suppliers in an extended enterprise.

ACKNOWLEDGMENT

The results presented in this paper have been obtained by visiting the PSG pumps. The authors are most grateful to PSG pumps for its support and technical contribution.

Fig.9. Workflow activity of a pump

Fig.10. Part number details

VI. DISCUSSION

From the object diagram, the product structure need not be required when searching for the specific document related to specific part. The workflow process retrieves correct data without any confusion. The class diagram which indicates all the complex links between the metadata. State diagram helps to identify at which state the document is present. Activity diagram relates the whole pump design in a single flowchart.

REFERENCES

  1. Benot Eynarda, Thomas Galleta.b, Pierre Nowaka and Lionel Roucoulesa, UML based Specifications Of Pdm Product Structure and Workflow, Laboratory of Mechanical Systems and Concurrent Engineering, Troyes University of Technology, Computers in Industry 55 (2004) 301316.

  2. D.T. Liu, X.W. Xu, A review of web-based product data management systems, Comput. Ind. 44 (3) (2001) 251262.

  3. C. Marshall, Enterprise Modeling with UML, Addison-Wesley, Reading, 2000.

  4. I. Choi, M. Song, C. Park, N. Park, An XML-based process definition language for integrated process management, Comput. Ind. 50 (1) (2003) 8510.

  5. L. Gzara, D. Rieu, M. Tollenaere, Product information systems engineering: an approach for building product models by Reuse of patterns, Robot. Comput. Integr. Manufact. 19 (3) (2003) 239261.

  6. D.R. Liu, M. Shen, Workflow modeling for virtual processes: an order-preserving process view-approach, Info. Syst. 28 (6) (2003) 27.

Leave a Reply

Your email address will not be published. Required fields are marked *