1 / 37

OiCoN Workshop Exercise on Organisational Interoperability approaches for Collaborative Networks

OiCoN Workshop Exercise on Organisational Interoperability approaches for Collaborative Networks. Dr.-Ing. Marcus Seifert, Patrick Sitek, BIBA, Germany Richard Stevens, Insiel, Italy Faisal Waris, AIAG (on loan from Ford, USA) I-ESA 2007 Madeira, Portugal 26 March 2007. OiCoN - Agenda.

topaz
Download Presentation

OiCoN Workshop Exercise on Organisational Interoperability approaches for Collaborative Networks

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. OiCoN Workshop Exercise on Organisational Interoperability approaches for Collaborative Networks Dr.-Ing. Marcus Seifert, Patrick Sitek, BIBA, Germany Richard Stevens, Insiel, Italy Faisal Waris, AIAG (on loan from Ford, USA) I-ESA 2007 Madeira, Portugal 26 March 2007

  2. OiCoN - Agenda 14:00 – 14.15 Welcome, Goal of workshop 14:15 – 14:30 Introduction of participants 14:30 – 14:45 Web-based IT solution for collaborative business Project: Extended Enterprise management in Enlarged Europe – E4 14:45 – 15:00 Open Source Enterprise Resource Planning and Order Management System Project: Tool-East 15:00 – 15:15 Business Collaboration Specification Project: AIAG 15:15 – 15:30 Preparation of group discussions 15:30 – 16:30 Grouping and Working incl. coffee break 16:30 – 17:00 Presentation of results 17:00 – 17:30 Discussion 17:30 Closing

  3. Who we are? The Bremen Institute of Industrial Technology and Applied Work Science at the University of Bremen (BIBA) is a research institute for engineering science which consists of four different domains: • Applied Information and Communication Technology for Production • Metrology, Automation and Quality Science • Product Development, Process Planning and Computer Aided Engineering • Intelligent Production and Logistics Systems

  4. Our competencies BIBA provides a range of up-to-date information technologies… • Planning, developing and realizing methods and tools to support inter- organizational networks • Design of efficiently and effective collaboration production processes due to the application of innovative information- and communication technology • Focusing in on cooperative acting in distributed production processes covering the product life cycle • The solutions are developed for companies of all sizes The BIBA is closely connected to the faculty of Production Technology and other faculties at the University of Bremen. • Achieved research results are disseminated in trainings and courses of studies of industrial engineering, production engineering, technical production engineering and systems engineering

  5. BIBA’s network BIBA participates in lot of regional, national and European projects with other scientific organizations and practitioners. ~ 500 partners in over 100 projects on national and international level ~ 300 international partners ~ 90 national partners ~ 100 local partners

  6. Insiel RICHARD

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

  8. OiCoN - Overview Motivation: • Collaborative networking as answer to unstable and dynamic markets • Capability and ability to interact and exchange information • Right IT-solution are of very high relevance for industry • Identify challenges and solutions to improve organisational interoperability, especially for SMEs Goal: Interactive session on general possibilities for realising organisational interoperability in cooperative networks. • Integrated Web based IT solution for Collaborative Business • Open Source ERP solution • Business Collaboration Specification

  9. E4 - Idea • “Networks”: today way of doing business Competitors, global dynamic markets, customer orientation  Change, collaborate, adapt, achieve customer satisfaction, provide complex, individual, order oriented, “End to End” solutions, extended products, etc. • In enterprise networks several independent user are working together on the same product. Suppliers rely upon a great variety of not integrated tools. • Networks compete on cost, quality and response time, whereby transparency and reliability are key components of network process quality • VO Project Manager and/ or specific process/ activity owner should get all information: To plan development activities To monitor the progress of work To keep cost, time, quality, engineering critical issues under control To deploy the information internally To view all relevant data at different levels of VO details To learn from a network

  10. Objectives of E4 • The approach presented is basing on the work carried out by the European funded research project E4 (IST-FP6) • Model of an engineering module specially tailored to the needs of the suppliers (SMEs) operating in a product development network • Low cost, standardized, effective, easy to understand web-based QM- services without client application for distributed networks • Covering collaboration phases like, initiation, management, operational life and dissolution • Covering product life cycle phases like R&D, design, production, use&service, end-of-life

  11. E4 Web-based IT-platform for organizations in Eastern Europe • To support the integration of OEM and suppliers in network enterprises • To realize distributed access in terms of a collaborative use of one platform • To achieve higher quality and efficiency in distributed processes related to product design Ability to achieve standardization, common vocabulary and integration in distributes networks while allowing individual participants to maintain their independence and competitiveness.

  12. E4 - Architecture Product Process Indicators (PPI) - time, cost, functionality Key Performance Indicators (KPI) Acquire Build Fulfill Build Fulfill Aquire Acquire Build Fulfill QCM PSM Bill of material CPM Reference Model Process (VCOR) Creation of Process Chains QCM Creation of Performance Charts Creation of Gantt/ Pert Chart/ Capability Plan/ … CKM

  13. Tool-East RICHARD

  14. AIAG FAISAL

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

  16. 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)

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

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

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

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

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

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

  23. Sample: IV&I Kanban Collaboration

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

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

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

  27. Preparation of group discussion • Reference Architectures, Methodologies and Tools to support Organisational Interoperability in collaborative networks • Reference Models for Organisational Interoperability • Interoperability approaches, case studies, standards, etc. for - Collaborative Project Management - Collaborative Customer Relation Management - Collaborative Quality Performance Management - Collaborative Product Structure Management - Collaborative Knowledge Management • Open source based E-Business solutions (ERP/CRM/SCM/SRM tools) • Open and interoperable platforms supporting collaborative businesses • Case Studies and Tools for supporting cross-enterprise co-operative work • Collaboration and IPR, trust processes, security, etc.

  28. (1) Open Source based e-business RICHARD

  29. (1) Food for thoughts RICHARD

  30. (2) Interoperable platforms • features for planning collaborative development activities • methodologies, tools and consultancy services that encourage the • collaboration and communication between involved actors Collaborative Product Structure Management • Predictive Performance measurement for • evolution of virtual • organisations. • methodologies, tools • and consultancy services • to record network processes • graphical visualisation on • progress of planning and execution activities traced by the platform. Collaborative Quality Control Management Collaborative Program Management • project centred communication with suppliers and customers which encourage structured knowledge transfer within a • network. E4 Collaborative Knowledge Management Collaborative Customer Relation Management Collaborative Project Management • unique repository of knowledge gained through collaboration to be available at any time

  31. (2) Interoperable platforms Marketing research C A D Design Prototype C A M Suppliers E 4 Platform Technical documentation CAD / CAM / ERP E 4 Platform

  32. (2) Interoperable platforms Design and manufacture of the equipment CAD / CAM / ERP E 4 Platform Suppliers Raw materials delivering Supplier 1 Components Delivery E R P Supplier 2 E 4 Platform Supplier …

  33. (2) Interoperable platforms . Supplier 1 Product manufacture E R P E 4 Supplier 2 Product Delivery Supplier … E R P Customers Supplier 1 Service and Maintenance E 4 E R P Supplier 2 Supplier …

  34. (2) Food for thoughts • www.beta.contactoffice.com • www.gliffy.com • www.desktoptwo.com • www.youos.com • E4 - Web based IT solution for Collaborative Business • Facing interoperability  Web 2.0 • Internet availability (airplane,…?) • Access speed • No direct access to data server (geographically) • Security of data access • …

  35. (2) Food for thoughts • Do all modules makes sense? • Where to locate collaboration platform modules in respect of product life cycle (ERP, CAD, customers, …) • How ensure user data (resources, processes) exchange/ integration from individual ERP (manually/ automatically)? • How to manage IPR, security, trust in networks using collaboration platforms? • How to manage user access rights in respect of different level of hierarchical authority? • Does it make sense to provide all modules as IT based solution? • Are parts as client application thinkable? • What technologies are needed? What level of abstraction is most efficient and effective (web services, data access rights, …)

  36. Grouping & Working Working in groups Probably idea for common FP7 proposal Time: 60min (16.30h) Results Time: 30min (17:00h) Discussion Feedback, Conclusion, Outlook Identify activities and responsibilities for further steps Time: 30min (17:30h) Closing

  37. Contact Patrick Sitek University of Bremen BIBA - Bremen Institute of Industrial Technology and Applied Work Science IKAP - Division "Applied Information and Communication Technology for Production" Hochschulring 20 D-28359 Bremen Germany mobile: +49 (0)179-7306904 phone: +49 (0)421-218 5591 fax: +49 (0)421-218 5610 mailto: sit@biba.uni-bremen.de http://www.biba.uni-bremen.de/english/ http://www.biba.uni-bremen.de/divisions/plt/projects.php

More Related