Collaborative Design & Data Exchange Leveraging SOA

Henri van den Bulk
PDE2009

© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.

Agenda
 Vision  Current

Environment

 Role

of SOA
Architecture

 Conceptual  Data

Exchange Framework

2
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.

How TIBCO Helps You Integrate Your Assets

Gives people the ability to observe and understand operations and opportunities.  Business Activity Monitoring  Complex Event Processing  Portal  Rich Client

Connects applications and assets across your extended enterprise.  Application Integration  B2B Integration  Data Integration  Mainframe Integration

Enables the coordinated and adaptable execution of activities and transactions.  Modeling  Execution  Analytics

Provides foundation for manageable service-oriented and event-driven architecture.

  

Standards-based
Common Environment Secure and Scalable

 Messaging  Monitoring and Management  Service Deployment Platform

3
© 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.

Vision Provide a consistent interface. for delivering acceptance data and interacting with program data that resides within the environment. All Rights Reserved. Confidential and Proprietary. based on industry accepted standards. 4 © 2008 TIBCO Software Inc. .

specifically ISO 10303 with STEP. Parts.  Based partner-conducted studies a general recommendation emerged for leveraging Industry standards for data delivery and integration. 5 © 2008 TIBCO Software Inc. . relying on partners and suppliers to provide significant portions of the product designs are required to provide data packages based on their contracts  Such as CAD. Requirements etc  Partners . Products. Confidential and Proprietary. All Rights Reserved.Background  Organizations are increasingly focused on the role of systems integrator.

All Rights Reserved. .Problem Statement  Delivery of data packages  Need for a system interface for delivery of data  Delivery of large data sets.g. e. CAD  Tracking of data deliveries  Verification of data delivery  Approval routing of acceptance data and partner notification  Dissemination of data  Collaboration / Interoperability  Ability to work in a geographically distributed environment with different stakeholders  Interoperability between systems  Provide access to program data 6 © 2008 TIBCO Software Inc. Confidential and Proprietary.

Current Environment  Design data resides within different sources inside and outside of the environment delivery of data occurs either as a file or upload manual into different systems standard external interfaces  Manual  No 7 © 2008 TIBCO Software Inc. . All Rights Reserved. Confidential and Proprietary.

accessing and controlling management information and product data defining all of the products. Confidential and Proprietary. integrating. . • Single source access to program data • Integrated systems that support the environment • Accessibility to all stakeholders 8 © 2008 TIBCO Software Inc. collaborating. academia and government for: sharing.Integrated Collaborative Environment Web-centric environment which is used by industry. All Rights Reserved.

. prototyping. All Rights Reserved. schedule. Visualization – web-centric capability providing 2D and 3D visual collaboration. 9 © 2008 TIBCO Software Inc.Major Components Product Life Cycle Management – enables access to all sources of authoritative program data resident in multiple data sources. Project Collaboration – Application for sharing and teaming among all ICE constituents that provides access control. review and study as part of the product development process. risk) as well as providing a single view into information allowing users to develop earned value metrics and risk mitigation plans. performance. Programmatic Management – Management of all programmatic data (cost. Confidential and Proprietary. discussion forums. resource management and project reporting. Process Automation (Workflow) – automated process management ensuring consistency across programs. mock-up.

Confidential and Proprietary. All Rights Reserved.Dx Objectives  Establish the data exchange standards to be used for data delivery and interaction with data Provide services to allow for delivery of data in automated processes that support large data file delivery Enable collaboration between partners Provide process management to support variations in acceptance processes Establish data dissemination framework Provide security across the capabilities      10 © 2008 TIBCO Software Inc. .

Confidential and Proprietary. All Rights Reserved.Role of SOA in this domain  Focus on wrap and re-use of existing capabilities in the infrastructure Business Process Management (BPM) across the Product Life Cycle access to PLM data of key Business Events  Enable  Uniform  Dissemination  Support business and process change. . create organizational agility 11 © 2008 TIBCO Software Inc.

All Rights Reserved.PLM Architecture Components for SOA 12 © 2008 TIBCO Software Inc. Confidential and Proprietary. .

capabilities and layers of design Complex Event Processing (CEP) – Provide the capability to correlate events from different sources and stages of PLM process. Requirement Management. etc. anomalies occurring in different areas of the process taken together might indicate a design flaw or defect   Data Integration and Master Data Management (MDM) – Manage Products. Confidential and Proprietary. Part and other PLM objects Application Integration – Provide connectivity to the underlying systems (PDM.Architecture Components  Business Process Management (BPM) – Management of processes across the lifecycle. . All Rights Reserved. For example.)  13 © 2008 TIBCO Software Inc.

. All Rights Reserved.Service Model and Properties Loose Coupling Virtualized Modular Consumer Standardized Service Provider Composable Abstracted 14 © 2008 TIBCO Software Inc. Confidential and Proprietary.

standardized services at the lower layers that are increasingly specialized at the higher layers. measured and minimized. Abstraction is the most powerful of tools in the agility toolbox. All Rights Reserved. 15 © 2008 TIBCO Software Inc. its data and application portfolio. Relative dependency and modularity should be determined in the business model and applied to the business processes. But as the portfolio is more widely based on service interfaces that make the underlying applications more transparent there will be many opportunities to componentize at all levels of the architecture with considerable benefits of increased agility and reduction in cost. providing the loose coupling has been properly implemented and there are no design or platform dependencies established by the service consumer or provider. Confidential and Proprietary. channel or geographic data and rules may be abstracted to allow a common capability to be used in a consistent manner across an enterprise or ecosystem. Standardization is a business matter and relates to how an enterprise manages its business processes.Principles of SOA      Standardization is something that is just not talked about by many people. A small amount of work to generalize a service specification can allow the service to support many different contexts. provides a high level of transparency of the underlying resources. services and components. Modularity is a concept that can be implemented at many levels in an SOA. In the early stages an architect should be looking to reduce dependency so that the horizon of change can be predicable. Forget reuse. . not because IT desires reuse. or to allow support for future business change within minimal or no effort. Standardization is required because the business demands consistency. with or without web services. Composability is again a hugely powerful technique that takes advantage of the fractal nature of SOA that allows hierarchies or assemblies to be constructed based on more common. for example product. The virtualization then provides opportunities for the provider and consumer to act independently and to have different life and upgrade cycles with consequent increased agility and response to change. Virtualization is an important part of the SOA. this is a programmers view of the world. The basic service concept.

SOA Challenge SOA application .NET/J2EE application Provision Customer Order FF Manufacture 16 © 2008 TIBCO Software Inc. . All Rights Reserved. Confidential and Proprietary.

All Rights Reserved. . Confidential and Proprietary.Leverage ESB Service Consumers Governance (Service Registry & Policy Management) Core Business Process Web 2.0 Composite and AJAX Rich Internet Applications Service Virtualization Enterprise Service Bus Developers/ Producers A O A O A Program / Project O A O A Ecosystem O EVM A Ecosystem O PDM Requirements Management Management Risk Management Partners 17 © 2008 TIBCO Software Inc.

ESB Capabilities       Ubiquitous Mediation Layer Separation between Business Logic and Transport / Technology Transport Bridging Eventing Content Based Routing Service Virtualization      Service Scaling Horizontal / Vertical Policy Management Ensure loosely coupling of services Messaging Based Orchestration and Choreography 18 © 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary. .

Architecture Views  SOA Architecture is based on industry best practices the OASIS Reference Model for SOA  Leverage  Model describes different architecture views:  Business view – high-level business requirements and utilization  Infrastructure view – concepts from a system infrastructure perspective  Metadata view – concept for metadata 19 © 2008 TIBCO Software Inc. Confidential and Proprietary. All Rights Reserved. .

All Rights Reserved.Business View B u s i n e s s O u t c o m e S u p p o r t s Business Function: A service executes (encompasses) a useful business function. which warrants some action from the business. Baseline of Requirements B u s i n e s s E v e n t P u b l i s h e s B u s i n e s s F u n c t i o n S e r v i c e SOA Reference Model 20 © 2008 TIBCO Software Inc. Confidential and Proprietary. Close Risk I s p a r to f B u s i n e s s P r o c e s s T a s k T r i g g e r s T r i g g e r s I n v o k e s Business Event: An incident occurring in the business environment. E x p o s e s .

Confidential and Proprietary. A d m i n i s t r a t o r M o n i t o r .Infrastructure View M e s s a g e B r o k e r I m p l e m e n t s S u p p o r t s Q u a l i t y o f S e r v i c e H a s M e s s a g e T r a n s p o r t C a r r i e s M e s s a g e M E P A s s o c i a t e s t w o o rm o r e S e n d s / R e c e i v e s B i n d s t o P r o v i d e s S e r v i c e I m p l e m e n t s C o n s u m e s S e r v i c e P r o v i d e r I s a S e r v i c e E n d p o i n t R u n s I s a S e r v i c e C o n s u m e r E x p o s e s A p p l i c a t i o n F u n c t i o n I m p l e m e n t s S e r v i c e C o n t a i n e r M a n a g e s M o n i t o r s A p p l i c a t i o n 21 © 2008 TIBCO Software Inc. All Rights Reserved.

All Rights Reserved. Confidential and Proprietary.Metadata View R e p r e s e n t O p e r a t i o n s I n c l u d e s U s e R e g i s t r y R e p o s i t o r y C o n t a i n s C o n t a i n s M e s s a g e s C o n s t r a i n D e s c r i p t i o n M e t a d a t a S c h e m a s P u b l i s h e s C o m p r i s e D e s c r i b e s C o m m o n D a t a M o d e l S u p p o r t s S e r v i c e S e m a n t i c s C o n f o r m s t o P o l i c y E x p r e s s e s E x p r e s s e s E x p r e s s e s S e c u r i t y 22 © 2008 TIBCO Software Inc. A u d i t Q u a l i t y o f S e r v i c e .

.Possible Data Exchange Mechanisms  Manual – Either provide a data package by file or upload this package into a tool manually. The format is then used for importing / exporting data. Confidential and Proprietary.  File  Service 23 © 2008 TIBCO Software Inc. All Rights Reserved. The tool can have structured or unstructured data. taking a package and putting this into the PDM System Transfer – Delivery of package in a tool specific format using standard file transfer mechanisms. For example. but is specific to that tool Oriented – Provide standardized interfaces that can accept and route information independent of format.

. All Rights Reserved. Management Program / Portfolio Management Others 24 © 2008 TIBCO Software Inc.Conceptual Architecture Data Delivery UI File Based Partner Data Validation and Verification Partner Systems Mass data exchange (asynchronous) Data Exchang e Services Drop Box Review Partner Systems / UI Service Based System Synchronous PLM / PLCS Services Data Distribution Connectivity & Interoperability (ESB/MFT) PDM Req. Confidential and Proprietary.

Confidential and Proprietary. . All Rights Reserved.Data Exchange Framework The framework provides distinct components of the exchange Partner Agreement Conversation Security Message Envelope Transport Protocol 25 © 2008 TIBCO Software Inc.

Depending on the business protocol. and encryption.Defines the policies that govern the previous mentioned areas of a data exchange. . Security . Depending on the business protocol. this may include MIME. and security attributes that partners choose for their communications. Each business protocol must provide a message envelope to carry the message body.   Message Envelope . S/MIME. Conversation . Confidential and Proprietary. this may also include technical details like the certificates file and the URL for HTTPS transport.Depending on the business protocol.Components of a Data Exchange  Data Exchange Agreement .This is a specific agreement between partners. as well as options like time-outs. or SMTP. HTTPS. this may include HTTP. All Rights Reserved. Depending on the business protocol. message structure. non-repudiation.This includes certain communication options. XML.   26 © 2008 TIBCO Software Inc. or OWL. access control. retries. It refers to the particular conversation. these may include transaction types like notify and synchronous or asynchronous request-response. This envelope and message are then wrapped in an envelope provided by the transport protocol. Transport Protocol . (S)FTP.Depending on the business protocol. and exception handling. this may include authentication. transport protocol.

Confidential and Proprietary. .Common Data Model (payload of envelope)  Data that’s being delivered and it’s meta data needs to be consistent such that validation and dissemination can be done is contained as payload in the envelope. All Rights Reserved. Each message contains meta-data that describes the delivery  Data  The CDM needs to be based on standards to ensure interoperability 27 © 2008 TIBCO Software Inc.

. function best when they fluently speak a common language (set of standards) data interchange and representation and management of information costs and increased efficiency Acceptance among partners  Facilitates  Lower  Higher 28 © 2008 TIBCO Software Inc. Confidential and Proprietary. All Rights Reserved.Why use Standards? Using Industry Standards provide the following benefits:  Reduce likelihood of mistakes  Easier to communicate and generate ideas – a large number of people working together.

.Which Standards Apply?     ISO STEP AP203 Configuration Controlled Design. ISO STEP AP239 Product Life Cycle Support (PLCS) OASIS PLCS Data Exchange Specifications (DEX) . ISO STEP AP233 Systems Engineering Data Exchange.Product Life Cycle Support (PLCS) standard (ISO 10303-239) Product Lifecycle Management (PLM) Services (OMG standard)  29 © 2008 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary.

. All Rights Reserved.Challenges with Standards  Focus  Can is generic result in loss of tool specific capabilities parts are left up for interpretation  Richness of tool specific functionality  Some  Flexibility can cause compatibility issues  Who drives the standards? do they apply to specific industries?  Keeping standards current with emerging technologies. OWL  How 30 © 2008 TIBCO Software Inc. Confidential and Proprietary.

All Rights Reserved. Confidential and Proprietary. .Challenges Ahead  Determine the delta between standards and business needs Master Data Management  Consistent  How do you perform approvals via PLM services for data changes? have been your finding around establishing exchanges using the standards?  What 31 © 2008 TIBCO Software Inc.

Sign up to vote on this title
UsefulNot useful