Docstoc

Enterprise Modeling Methodology for Enterprise Integration

Document Sample
Enterprise Modeling Methodology for Enterprise Integration Powered By Docstoc
					Enterprise Modeling Methodology for
        Enterprise Integration




                2002.


         Cheol-Han Kim Ph.D
       Daejon University, KOREA
               Recent Publications
 Modeling Methodology
    Development of Integrated Methodology for Enterprise Engineering,
     International Journal of CIM, vol.14, No.5, pp.473-488, 2001
    Functional Modeling for Enterprise Integration, ICPR 2000, Bangkok,
     Proceedings CD, 2000.8
    An Integrated Use of IDEF0, IDEF3, and Petri-Net Methods in support of
     business process modeling, proceedings of institution of mechanical engineers
     part E- Journal of Process Mechanical Engineering, Vol.215, No.E4, 2001
    The Complementary use of IDEF and UML modeling approaches, submitted to
     International Journal of Computers in industry
 Requirement of EI Framework
    Requirements of a Framework for Enterprise Integration, ICPR 16, Praha,
     Proceedings CD, 2001.7
 Two-phase Modeling for VE
    A Two-Phase Modeling Method for Virtual Enterprise, to be presented at IJIE,
     Busan, KOREA, 2002.10
                                              Contents


This is probably just a powerpoint version issue,                                                    Functional
       Function Capability
       but my slide here contains nothing.                                    Business scenario         area
          Information Hub   Requirements                                                             Company
         Information       of EI framework     Analysis                       Information
        Infrastructre service
                                                                              Function
                                                                              Resource
  Enterprise                                                                  Organization
   Modeling       higher level    Two-phase         Topics   IMEE            Repository
   Simulation      lower level     modeling                                  Process
                                                                             Behaviour
                                                                                           Simulation
                                                                    Design   Database
                Development of
                                                                             Organization
                 modeling tools     Current works                                                 Function class
                           VERA                                              Object-oriented
                                                                                 model            Entity Class
                 Introduction
 Background
   Mass Customization on a Global Scale
    Is enabled by highly information intensive
     manufacturing engineering such as CIM, CALS, and
     EC
    Drives close cooperation between partnership
     enterprises
      Requires close interaction and cooperation between
        business partners despite their geographical
        distribution
  ICEMIT’97 working group developed Generalized
   Model for partnership enterprise
                                                Introduction
                       sub-process (or activity) nodes
                                                                 process stream
                          n1          n3           n6 n7 n8          n 11    n 13 n 1 4 n 15
                                                                                                     product
 Organization stream




                                                                                                   application 1
                                                                                                     product
                                                                                                   application 2

                                                                                                     product
                                                                                                   application 3

                                                                                                     product
                                                                                                   application 6




                                                                                                     product
                                                                                                   application m


                       company a      company b          company c   company d     company e
                                                                                               From ICEIMT 97 working group

 Describe only one way direction between participants
    Does not describe information flow and interactions between participants
  What is Enterprise Integration?
 Definition: the task of improving the performance of
  large complex processes by managing the interactions
  among the participants
   CPC: what is this? between development and
    manufacturing
   Supply Chain : between supplier and manufacture
   EI is normally pursed within the context of an emerging,
    network-centric environment.
       Aims at streamlining process, breaking barriers, sharing knowledge,
        and ? interacting information systems. – http://www.afei.org
     What is Enterprise Integration?
                                           Distribution

                                       Production Planning


Customer       Product Order              Part Order       Work Order          Product

                                                Purchase Order
           Product Design

               Part                      Assy’s Supplier
               Assy’s Spec.
                              Part Design Part Supplier

                                         Sub -Assy’s
Enterprise Integration
                                                                 Engineering Process
                         Supply Chain
                                              Part
           Modeling Methodology
 Overview
  existing enterprise engineering methodologies:
        do not completely address collaboration and interaction.
        are less well suited to modelling certain dynamic aspects of
         partners interactions
   Integrated Methodology for Enterprise Engineering (IMEE),
    developed to meet key aspects of modelling multi-partner
    enterprises, incorporates two complementary kinds of
    modelling concept:
        process oriented modelling in support of enterprise requirements
         capture and analysis, centered on ‘function’, ‘activity’ and
         ‘dynamic systems’ modelling and simulation approaches
        object-oriented modelling in support of the conceptual design of
         multiple business systems, centered on ‘function’, ‘information’ and
         behaviour modelling.
                                       IMEE
  Overview - Three axes of enterprise modeling (why 4
       bullets below?) functionality to perform the business process
         Activity : unit of
                - Physical activity (PA): deals with the tangible
                - Logical activity (LA): deals with the intangible
        Resource: something required to business process
                - mfg. facility, human resource, computing resource
        Organization: personnel that perform business process
        Information : data, fact, or knowledge required to perform the business process


Type        main resource           output                            organization
                                   part,
P.A       mfg. Facility, human
                                   product
L.A     computing resource,        information,                               activity
        information                service
                                                                   Information
             Modeling Methodology
                                       (IMEE)

  Overview - Example
[Physical activity]
                                                Shop #1
                                                             Cutting the material
                     Machine tool

                                       process plan
                                   machine tool capability


[Logical activity]                            Purchase department
                        Internet                             Issue a purchase order

                                   Purchasing requirements
                                    supplier’s information
               Modeling Methodology
                                    (IMEE)

 Overview
                             Business Scenario

      Organization    Resource                 Function   Information
        Analysis      Analysis                 Analysis     Analysis

                              Matrix Analysis
Analysis

                                  Repository
      Organization                             Process     Common
                     Simulation
         Design                                Design     Data Model

                                                           Database
                     Behavioral                             Design
                     Description
Design
                                  Object-Oriented
                                  Approach(UML)
                                       IMEE
                                       -Analysis

 Analysis Phase                                   IA
                Information Analysis                     Entity vs. Function Matrix


                                          OA/RA          FA
    Business
    Scenario
                   Function Analysis
                                                   IA
                                                         Entity vs. Organization Matrix
 Organization Analysis
 Resource Analysis                                      FA

                    Analysis Matrix/    OA/RA
                      Repository
                                                   IA
                                                         Function vs. Organization matrix
                                                         Function vs. Resource matrix
                                                         Resource vs. Organization matrix
                                                        FA
                                       OA/RA
                                IMEE
                        - Analysis Phase

 Business Scenario
  Objective: Design a scenario for business goal under EI


           Procedure                            Output

   Design Business scenario           Business scenario
       Define major process               context diagram
   Select function area and            Functional area table
    organization for business           Company table
     scenario                           Function vs. organization
                                          matrix
                                 IMEE
                         - Analysis Phase

 Functional requirements analysis
  Objective: To define the functional unit and related object


           Procedure                              Output

   Define the function                  Function definition
   Deduce activity list using           Activity list
    map from the function                Functional diagram
   Decompose the function               Unit function definition
   to unit function level                Functional description
   Describe components of
   the function
                                                         Function name       Tracking of invoice
                                                         Description
                                                         Enterprise code     Final assembler (E1)
                                    Control Data
                               (source function code)    Function code       E1-F314
                                                         Input data          Invoice (I1), vendor (I2)
      Input Data
(source function code)                     Output Data   Output data         Invoice status (O1)
                         Function Name                   Control data        Delivery date
                         Function code
     Material                               Material     Resource
                                                         Organization        Purchase department
                                                         Organization code   E1-O32
                                                         Task1 (10 min)      Trace invoice
                  Resource      Organization
                                                         Task2 (5 min)       Calculate delivery time
                                                         Operational logic   O1 = I1 AND I2

                                Functional description
                             IMEE
                       - Analysis Phase

 Information Analysis
  Objective: To define the entities and relationships


           Procedure                           Output

   Collect information                Information requirements
    requirements                        table
   Define Subject area –              Subject area table
   - Product, Order, Production        Data dictionary
   Integrate views of the unit        E-R Diagram (Key level)
    function output                    Information requirement vs.
   Describe the entity                entity matrix
                                       Function vs. entity matrix
                              IMEE
                        - Analysis Phase

 Resource Analysis
  Objective: To define the resource involved


           Procedure                            Output

   Define the resource                Resource table
    (manufacturing, computing,         Resource vs. function
     and human)                         matrix
   Allocate resource
   Define resource capacity
   Analyze resource utilization
                               IMEE
                       - Analysis Phase

 Organization Analysis
  Objective: To define the organization involved


          Procedure                            Output

   Define organization                Organization table
    (Human resource)                   Organization vs. company
   Analyze the Organization           matrix
                                       Organization vs. function
                                        matrix
                                       Organization vs. entity
                                        matrix
                                 IMEE
                          - Analysis Phase

 Matrix Analysis
  Objective: To verify and valid the analysis result


           Procedure                              Output

   Analyze matrix                       Functional set tracing
   Trace information                      report
    requirements
     - Analyze the functional set
      for the required information
                                     IMEE
                                  - Design Phase

 Overview                                    DD    Object-oriented model
                                                    Object-state transition description
               Database Design

                                                        PD
                                        OD
 Repository
                 Process Design
                                              DD
                                                        Distribution & Centralization
Organization Design
                                                    PD

                                        OD
                       Object
                      Component               DD
                                                             Simulation
                                                   PD          - resource capability
                                                                 . Organization
                                        OD                       . Mfg. Facility
                                                               - bottleneck function
                              IMEE
                         - Design Phase

 Repository Design
   Objective: To design the meta-data for modeling component


           Procedure                               Output

   Define the meta-data                  Data dictionary for meta-
    for entity, function,                 data
    resource, organization                Matrix for
   Define the relationship                 - Entity vs. function
     between meta-data                      - Function vs. resource
                                            - Function vs. organization
                                            - Organization vs. resource
                                            - Entity vs. organization
                                           IMEE
                                        - Design Phase

     Repository Design
                                         MAJOR-PROCESS
        COMPANY         m                        n
             1                             has
                                n                m
             n
                                        FUNCTIONAL-AREA
      ORGANIZATION                                               n
                                                                         CONTROL-DATA
                                                 1
1
             1

             n                                   n   m
                            m       n                        1   1
    ORGANIZATION-DATA                    UNIT-FUNCTION                   OUTPUT DATA            ENTITY
                                                 n       m                                         n
                                                 m
n                       1           n                                n
       RESOURCE                          RESOURCE-DATA
                                                                          INPUT-DATA

                                                                                            1

                                                                                        SUBJECT-AREA
                              IMEE
                         - Design Phase

 Process Design
   Objective: To define business process with the business scenario


           Procedure                                 Output

   Define major process                    Functional diagram
     - Define sub-process                   Process model
     - Find the unit function to             - PFD
     meet start event and end
     event
     - Aggregate the functional
     set
     - Combine sub-process
   Convert unit function into
   UOB (Unit Of Behavior)
                          IMEE
                     - Design Phase

 Process Design
                                                 [Target Process Area]


    Start
    event
                                                          End
                                                          event
                                                                    direction


                           Repository

         Unit                              function vs. resource
       function                            organization vs. entity
                                           organization vs. resource
                                           organization vs. function
                             [Matrix]      entity vs. function
                                           entity vs. Information requirement
     E-R Model                             unit function vs. data matrix

                   [Concept of Process design]
                                           IMEE
                                    - Design Phase

 Process Design

       Suggest
      the spec.                                          C1            C2
      (A2-321)                                        inventory    Production
                                                       (B3-31)     plan(B3-42)
                                             Spec.
        required          propose          (A2-321)
                           order                                                     O1
          order                         I2
                         (A1-221)                                               proposed order
        (A3-111)                                         adjust order
                                           I1                                                                Booking
                                                           (B3-11)                                 Confirm
                                        order                                                       order    order
                                      (A1-221)                                            O2
                                                                                                   (B3-12)
                                                                                        adjusted
   Adjusted        Adjusted                                                              order
    Spec.           order
                                     SAND(I1, I2) -> X (O1,O2)



                                                                Object/order
                                                                                                     Confirm order
                   Propose
          X        the order
                                                                                                       3     A2-321
                   1      A1-221
                                       &                   adjust order                    X
      &
                                                            3           B3-11
                    Suggest
          X        the spec.
                   2      A2-321
                                IMEE
                         - Design Phase

 Common Data Model
   Objective: To define the entities and relationships


           Procedure                            Output

   Integrate views of each             Data dictionary
    entity                              E-R model (Attribute level)
   Redefine the entities and           Transaction analysis table
     their attributes                   IT platform
   Refine the E-R model
   Analyze the Transaction
   Design IT platform
                             IMEE
                        - Design Phase

 Behavioral description
   Objective: To define behavioral aspect of the UoB


           Procedure                          Output

   Analyze the behavior of the       Association table between
    process                            UoBs
   Analyze associations              Message table
    between the UoB                   Method table
   Define the message between
    UoB
                             IMEE
                        - Design Phase

 Simulation
   Objective: Find bottleneck functions and resources


           Procedure                                Output

   Allocate the resource                  Petri-Net model
   Convert to the Petri-Net               Bottleneck function list
    model from process model
                                      IMEE
                                 - Design Phase

 Simulation
    Function Model                 Process Model             Petri-Net Model

             Control                             Mechanism     resource
                       Output
Input Function name
          (FC)                                                   UoB
                                      UoB
            Mechanism                   FC




    IO relationship                    Link                        Arc
                                      Junction                  Transition
       Mechanism                      Referent                   Place

       Function                        UoB                        Place
                           [Analogy of modeling component]         FC: Function Code
                                 IMEE
                              - Design Phase

 Simulation
                          &

                          &

                          X

                          X

                     UOB



    p1               p3                             p6
          t1
                                  t3    p5     t4
     p2         p4
           t2
                               IMEE
                          - Design Phase

 Organization Design
   Objective: Define the organization that executes the business scenario
    (or are you assigning roles to things in the organization?)

           Procedure                                     Output

   Define organization and                    Organization table
   role                                        Information flow between
   Design the workflow                         organization
    between organization
                               IMEE
                          - Design Phase

 Database Design
   Objective: Implement the relational table of RDBMS


           Procedure                            Output

   Select target RDBMS                Relational table
   Translate data dictionary to
   relational table
                             IMEE
                         - Design Phase

 UML Model Generation
   Objective: Convert constructs into a UML model for easy
                  implementation

            Procedure                              Output

    Convert IDEF modeling                 Class Diagram
     component into UML                    Use Case diagram
     component                             Dynamic Diagram
    - define Function class &
      Entity Class
    - Design Class diagram
    - Convert IDEF0 & IDEF3
      into UML dynamic model
                                     IMEE
                                - Design Phase

 Object-Oriented Approach
                                 UML                                       IDEF
Main Focus of
 Modelling         Model                                          Model           Modelling
                                  Modelling Constructs
                  Context                                        Context          Constructs
 Define the                                                                 Context diagram,
                  Use case           Use case, actor,
  problem         diagram                system
                                                                 IDEF0      0-level functional
  context                                                                       diagram

Design static      Class                                                             Entity,
                                    Class, relationship           IDEF1x
  solution        diagram                                                         relationship

                                 Object, event, state              IDEF3      Object, state
                State diagram
                                 transition,                      (OSTN)       transition
                                  Activity, object transition,
                  Activity                                                   UoB, junction
   Design                            decision diamond,            IDEF3
                  diagram           Synchronisation bar                     and link, referent
  dynamic
  solution      Collaboration                                     IDEF0,      Link, referent,
                                  Object, link, message
                  diagram                                         IDEF3,      unit function,
                 Sequence                                         IDEF0,    input and output
                                  Object, link, message                     data, mechanism
                  diagram                                          IDEF3
  Requirements of EI Framework

 Functional Capability
   Requirements
      Business functions? (active components?) must co-operate with
       each other despite being distributed and owned by other enterprises
      Functions on EI process must communicate with each other to
       attain the global goal
           Functions and organizations which participate in the business
            process must be defined when designing business scenario
           Interaction between functions following a given scenario must
            be defined with collaboration rules.
           Resources of the business partners must be shared and
            controlled with business scenario
           A Function must respond to other function’s task or result
   Requirements of EI Framework
 Functional Capability
   Definition
       Possibility of Cooperating through different functions and
        organizations from each different company
       Ability to carry out certain types of activities, tasks or operations on a
        business process (why not “ability to produce a certain output”?)
   Elements of function capability
       Information needed for function execution
       Resource available for function execution
       Response time required for functional response
       Execution time for required time span
       Organizations that deal with a task ???
       Priority compared with a current task ???
      Requirements of EI Framework

 Function Capability
   Function A                                  Function A
                   s                                            A

                         Function B                                    Function B



        Synchronous interaction                   Asynchronous interaction
• Function B must execute its task with       • Function B execute its task with given
  given scenario, as soon as function B         scenario, when function B need to do it
  receive information that we called active   • Function capability of function B is not
• Thus, Function capability of function B       considered. We called this information
   must be considered when function B           passive
   receives active information.
   Requirements of EI Framework
 Information Hub
    Requirements
       Business information can be shared between business partners
           Data must be accessed through distributed environments
       Data defined in EI environment are distributed logically or geographically
        and user may require information that is located in other database system
           Data Schema and Semantic must be represented with common
            meaning??
       Product Information must be shared between participants for efficient
        collaboration among set-maker?, suppliers, and customers in order to
        controls product quality and cost
           Because Product information has many different views according to the business
            partner or business process such as SCM or Engineering process
                The semantic of product information must coincide with business partner
  Requirements of EI Framework

 Information Hub
   Definition
      Common gateway to support data retrieve from and store
      into local databases through global database.
        Global conceptual schema and local schema are defined
        Data allocation is defined
   Requirements of EI Framework

                                   Client
                                                   Application
                                                     Server
                                   Web
Access control                     Server
      list          2              1        5
Data dictionary             Information Hub
                             SQL      ORB
Data Directory             Gateway     IIOP
Global Database                3            4

    Local Server        Local Server            Local Server


   Local database       Local database          Local database
   Requirements of EI Framework
 Information Infrastructure Service
    Requirements
        Despite heterogeneity, information access must be possible (not
         sure I captured your thought here).
            Interoperability between computing components must be guaranteed
            Common business objects, such as suggested by BOMSIG of OMG will
             support interoperability ???
        Each system must be defined with common representation
         semantics ??? and syntax
            XML will satisfy this requirement
        EI environment is possible when the seamless integration of
         distributed components is guaranteed in spite of heterogeneities
         between computing resources of the participants
  Requirements of EI Framework
 Information Infrastructure Service
  Definition
      Infrastructure Service that supports borderless
       access and control of distributed systems
  IIS will be supported by                the following to
   provide inter-operability:
      Business object based on CORBA, DCOM
         with business object, Application systems do not need to
          revised or changed with system expanding, changing, or
          new construction
         Flexible deployment or distribution of application is
          possible without consideration of each other application
      Web service based on XML and SOAP
        Two-Phase Modeling
 Basic Concept of two-phase modeling



                              Final Assembling




                                                 Participant of VE
                                                 Local simulation
                                                 Functional area
                                                 Functional element
                                                 Interaction
           Two-Phase Modeling
 Basic Concept of two-phase modeling
                 Enterprise Modeling
   event
                Design Business Scenario

               Decompose functional area

                 Define Process stream

                           XML
                                           enactment
                       Simulation
                      Local simulation

                    Global simulation
                 NO                 YES
                          Current Work
 Developing an modeling tool
    Support ICEMIT’97 generalized model & IMEE
        Define Function/Organization Matrix
            In order to decide participants and their functional areas with business scenario
        Define Functional Map
            In order to extract sub functions or activity with map
        Describe Functional Diagram without arrow from Functional Map
        Define Information flow adding arrow between functional elements of
         functional diagram
        Describe functional constructs such as resource, organization, execution
         time, combination logic between input & output
        Design and Implement Repository for IMEE case tool
        Support process model (IDEF3 & Petri-Net)
        Analyze business process
             Find bottleneck process
             Trace information flow with a specific task
                  Current Work
 VERA (Virtual Enterprise Research and
  Applications) Forum
   Enterprise Modeling
      How to describe Business Scenario
      Process Modeling Methodology
   Information Infrastructure Service
      Web service
      Community & Communication method
      Representation Scheme – ebXML
   Virtual Organization
      Organize and Evaluate virtual team’s performance
            Q&A




Thanks for listening to my
    presentation !!!

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:4
posted:4/16/2012
language:
pages:47