Automotive industry action group aiag
This presentation is the property of its rightful owner.
Sponsored Links
1 / 14

Automotive Industry Action Group (AIAG) PowerPoint PPT Presentation


  • 110 Views
  • Uploaded on
  • Presentation posted in: General

Automotive Industry Action Group (AIAG). Automotive Industry ‘Vertical’ for North American Supply Chain Founded by Ford, GM, DaimlerChrysler 1500 members Goal

Download Presentation

Automotive Industry Action Group (AIAG)

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Automotive industry action group aiag

Automotive Industry Action Group (AIAG)

  • Automotive Industry ‘Vertical’ for North American Supply Chain

    • Founded by Ford, GM, DaimlerChrysler

    • 1500 members

  • Goal

    • “…reduce cost and complexity within the automotive supply chain and to improve speed-to-market, product quality, employee health-and-safety and the environment”

  • Global Strategic Initiatives

    • ODETTE, VDA, JAMA, NIST, OAGI, OASIS, WS-I, …

  • Co-Chair of Inventory Visibility & Integration Project

    • Applied research into…

    • Optimizing business partner collaboration leveraging electronic messaging

    • Focus on Inventory Management processes

      • Kanban

      • Min Max


  • Automotive industry action group aiag

    AIAG

    FAISAL


    Aiag inventory visibility integration project iv i

    AIAG Inventory Visibility & IntegrationProject (IV&I)

    • Optimize Supply Chain through better Business Collaboration

    • Leverage

      • XML Messaging

      • Public Internet

  • Shared Semantics

    • OAGI XML Vocabulary

    • Joint Automotive Data Model (in progress; jointly with Odette, JAMA,…)

    • ATHENA (research)

  • Considered several competing protocols

    • Web Services

    • ebXML

    • AS2

  • Currently focused on Web Services


  • Why web services

    Why Web Services?

    • Ubiquitous (but still maturing)

    • Interoperability

      • Web Services Interoperability (WS-I) Profiles

      • Basic; Basic Security; & Reliable Secure

  • Service Oriented

    • SOA already used for internal integration

    • Extend Service Oriented Concepts to B2B integration

  • Provide a ‘process’ context

    • Not just ‘message slinging’

  • Reasonably complete ‘stack’

    • Semantics (XML Schema)

    • Security

    • Reliability

    • Orchestration

    • Transactions

    • Directory

    • Metadata driven (WSDL, Policy, BPEL)


  • Soa building blocks

    SOA Building Blocks

    SOA Protocol Services

    Business Services

    Stateless

    WS-Trust, SAML-SSO, WS-Federation, Liberty, BPEL, XKMS, etc.

    State-full

    SOA Protocol Stack

    SOAP, WS-Security, SAML, WS-ReliableMessaging, WS-Transaction, WS-SecureConversation etc.


    B2b with soa

    Logical Service Bus

    B2B with SOA

    SOA Protocol Services

    SOA Protocol Services

    SOA Protocol Services

    Business Services

    Business Services

    Business Services

    State-full

    State-full

    State-full

    Stateless

    Stateless

    Stateless

    SOA Protocol Stack

    SOA Protocol Stack

    SOA Protocol Stack

    Partner A

    Partner B

    Partner C


    But something is still missing

    But Something is Still Missing

    • Web Services based SOA Provides a Lot But…

      • No clear way of defining Business Collaboration

        • Across Multiple Partners

    • BPEL provides a single-node view only

    • How to link multiple, independent nodes

  • Business Collaboration Specification (BCS)

    • Attempts to fill this gap


  • Bcs soa uml modeling

    SOA Protocol Services

    SOA Protocol Services

    SOA Protocol Services

    Business Services

    Business Services

    Business Services

    Partner A

    Partner B

    Partner C

    State-full

    State-full

    State-full

    Stateless

    Stateless

    Stateless

    SOA Protocol Stack

    SOA Protocol Stack

    SOA Protocol Stack

    BCS: SOA + UML Modeling

    BCS: UML-based methodology for Modeling Collaborations


    Bcs concepts

    BCS Concepts

    A Business Collaboration is modeled as a UML Activity Diagram.

    Each ‘Swimlane’ represents a collaboration Partner

    Partner A

    Partner B

    Each ‘ActionState’ represents some activity that a partner is expected to do, e.g. send or receive a message.

    Control flows from one activity to another but cannot cross ‘Swimlanes’ (BCS rule)

    Only message flows can cross ‘Swimlanes’

    Each ‘ObjectFlowState’ represents a message


    Bcs sample parallel processing

    BCS Sample: Parallel Processing

    Models a collaboration where ‘A’ is required to send two messages to ‘B’ and ‘B’ is required to wait for both before proceeding. Messages may be sent or received in any order.


    Sample iv i kanban collaboration

    Sample: IV&I Kanban Collaboration


    Bcs architecture web services

    BCS ArchitectureWeb Services

    Meta Models, Validation & Transformation Rules

    Business Collaboration Diagram

    UML

    Business Collaboration Specification

    Modeling Time

    Generate

    Collaboration Contract

    Build Time

    WS-BPEL (abstract)

    WSDL

    WS-Policy

    XML Schema

    SpecifiesRuntimeBehavior

    WS-BusinessActivity

    WS-AtomicTransaction

    WS-Enumeration

    WS-Transfer

    SOAP

    XML / HTTP

    WS-ReliableMessaging

    WS-Security

    WS-Addressing

    Run Time


    Transformation to web services metadata

    Transformation toWeb Services Metadata

    Two UML Profiles

    BCS Semantics

    Web Services Transformation

    Swimlane Control Flows & Activities WS-BPEL

    Activities, Messages WSDL, WS-Policy

    Messages XML Schema


    Bcs summary

    BCS Summary

    • The set of Activities and Control Flows in a ‘Swimlane’ describe a Partner's collaboration ‘state machine’ (process)

    • A ‘Business Collaboration’ is a set of processes and their coordination via message flows – a ‘Meta Process’

    • Gives each partner visibility to the relevant portions of other partners’ processes

    • Each partner is free to extend it’s process for internal processing as long as the external view is not affected

    ‘Reference Implementation’ available for MagicDraw™ UML Tool


  • Login