The IBM Rational strategy for integrating with Product Lifecycle Management (PLM)

Transcription

1 The IBM Rational strategy for integrating with Product Lifecycle Management (PLM) Richard Crisp Director, Systems Engineering 27 May, 2014

2 Please Note: IBM s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. Information is confidential and must not be shared or redistributed without permission from IBM. Plans are based on best information available and may change in future. 2

3 Setting the stage Today s typical Product Lifecycle Management Next Generation Product & Systems Lifecycle Management System Engineering along the lifecycle(s) Electrical Engineering Mechanical Engineering Software Engineering Physical Assembly, Document & Bill of Materials (BoM) Centric Approach to drive the Supply Chain Integrated Electronic, Mechanical, and Software Engineering Modern systems and products now more software intensive, more complex delivery & management Relationship between engineering & software orgs is often loosely connected & dysfunctional Current solutions require all lifecycle data to be physically located in PLM/PDM tools Requires data to be replicated across multiple tools or data stores, complex to manage 3 Data is stored and maintained by the tool that is best suited for those data Other tools to gain access via linked data methods built on open standards for data sharing, not proprietary interfaces and databases Provides an open environment where engineers have access to all relevant information needed, regardless of source

4 The IBM Systems Engineering Platform can access engineering and enterprise data wherever it resides IBM Social Media Analytics and Warranty Analytics Rational Market Analytics Focal Point Insight Tivoli Customer Requirements DOORS System Requirements Rhapsody System Design RTC Process & Data Mgmt. System Verification and Validation System Test Deployment/ Release to Mfg. RQM Operations and Maintenance Implementation Partners enabled by OSLC Electrical/ Electronics Design Agile Software Engineering Mechanical Design Engineering context RELM, Infosphere Data Explorer, and Big Engineering Data Open standards Business Engineering Operational Enterprise information 4

5 Rational Engineering Lifecycle Manager Extending the Rational solution for systems and software engineering Uniting engineering teams through: Visibility across many engineering disciplines Organization of information in context Analysis to answer lifecycle engineering questions Allows product development teams to: Find the right information when it s needed Understand and react to change quickly Gain actionable insights from engineering data Co-ordinate strategic re-use With no disruption to current engineering environments RELM demonstrates the power of linked data and provides an enterprise a new way to integrate tools and project tasks in one interface. 5 Systems Engineer

6 Customer Prioritization Key ALM/PLM integration pain points Rational Engineering Lifecycle Manager Visualize Analyze Organize Cross domain views and navigation Query, reporting, and impact analysis Product, system and component definition Change Management Requirements Management Product Structure Co-ordinating a product change e.g. new market requirements, safety regulation change, defect fixes. Enabling requirements decomposition across multiple systems Allowing organization of lifecycle artifacts and traceability between different views of the product 6

7 Primary Resource Types and Relationships Change requests and requirements exist in both ALM and PLM systems Product/component/capability definitions exist in ALM System (RELM) Material and Part instances exist in PLM system Product/component/capability definitions in RELM and Material and Part instances in PLM share a common abstract representation (OSLC PD) 7

8 Scenarios, with some examples I want to link an ALM change request and a PLM change request Associate a PLM Change Request to update the Flight Director tactile interface with an ALM Change Request to implement the relevant software changes Parent/Child relationship Associate a PLM Change Request to move flap sensor locations with an ALM change request to retune the sensor fusion algorithms Blocking relationship I want to link an ALM change request and a PLM requirement Associate an ALM Change Request to increase the width of forward Terrain Avoidance Warning System (TAWS) sensing with the PLM Requirements for sensor mounting orientation I want to link an ALM change request and a PLM part/material in a BoM Associate an ALM Change Request for improved error detection for the Runway Overrun Protection System (ROPS) sensors through a change to the electrical signal characteristics and the inclusion of a different part number (sensor with new interface) in the PLM BOM 8

9 Scenarios, with some examples I want to link an ALM requirement and a PLM requirement Associate an ALM requirement for range of visibility for TAWS object detection with a PLM requirement for angle of sensor mounting I want to link an ALM requirement and a PLM change request Associate a PLM change request for hardware housing with ALM requirements for adding Onboard Airport Navigation System (OANS) 9

10 Scenarios, with some examples I want to link an ALM product definition and a PLM change request Associate a PLM Change Request to use an alternate Forward Looking Terrain Avoidance (FLTA) sensor (smaller, cheaper, better,?) with an ALM product definition for a different sensor software component I want to link an ALM product definition and a PLM part/material in a BoM Associate a PLM master product node for a TAWS sensor with an ALM product definition for the sensor 10

11 OSLC SPECIFICATIONS RELEVANT TO ALM/PLM INTEGRATION OSLC CM 2.0 Change Management FINALIZED FINALIZED DRAFT OSLC RM 2.0 Requirements Management OSLC PD 1.0 Product Structure Co-ordinating a product change e.g. new market requirements, safety regulation change, defect fixes. Enabling requirements decomposition across multiple systems Allowing organization of lifecycle artifacts and traceability between different views of the product All in the context of multiple versions and variants DRAFT 11

12 Solution Architecture 12 IBM Confidential

13 Customer Prioritization Key ALM/PLM integration pain points Rational Engineering Lifecycle Manager Visualize Analyze Organize Cross domain views and navigation Query, reporting, and impact analysis Product, system and component definition Change Management Requirements Management Product Structure Co-ordinating a product change e.g. new market requirements, safety regulation change, defect fixes. Enabling requirements decomposition across multiple systems Allowing organization of lifecycle artifacts and traceability between different views of the product 13

14 Integrating Rational Change Management with PTC Windchill PDMLink

15 Change Management scenarios used to design the adapter Scenario 1: Change to Product Software arising from a field problem report Used to create Scene 1 of the Smart Golf Pull Cart example Scenario 2: Change to Product Hardware arising from a change in requirements Another example using the same implementation not detailed here 15 IBM Confidential

16 Summary of the targeted Rational PLM integration solution (CM) Flexible Change Management approach: Product centric Federated discipline approach Linking approach provides progressive control: greatly increases cohesion in the cross-discipline and sub-team processes allows choices about where and when to use heavy/light process tailor for different disciplines needs e.g. level of granularity, use of approvals and controlled workflows Reduced effort and time to create and maintain change notices Reduced effort and time to check and correct out of sync Reduced effort and time to report status and align colleagues Reduced effort and time to pinpoint problems or opportunities Leading to greater engineering and innovative capacity Target timeframe for CM and RELM integrations: 2H

17 Working with clients on additional scenarios for ALM/PLM integration

18 Example Airbus Use Cases for Requirements Management & Product Structure UC1: Link requirement module to master product node Multiple level of design, shall be linked together with traces Selection of requirements sets from the requirements database and of corresponding documents PLM shall store a baseline UC2: Under master product change request, change impact analysis identifies the requirements to be changed After changing, the owning requirements module is re-baselined UC3: Prior to approval of completion of a master product change request, the requirement changes are reviewed and comments are resolved or concessions agreed Reviews on a baselined reference. Reviewers will consider documents connected or not Target timeframe for RM and product structure integrations: 1H

19 IBM Innovate conference activities for PLM integration Voice of the Customer Event (VoiCE) Sunday - One hour segment in the session, "Hot topics in systems and software engineering," focused primarily on what we're showcasing at the conference, namely CM integration between PTC Windchill and Rational Team Concert Tuesday afternoon - Special session, "Hands On Design of Scenarios to Address Integration Pain Points," large group of customers (90+) registering spanning across both Systems and IT interests, including brief introduction to IBM s PLM integration strategy Wednesday afternoon (TENTATIVE) PLM Customer Steering Committee, focus on evolution of the RM & product structure use cases Birds of a Feather (BoF) - Tuesday 12:30-1:15, "Interoperability with PLM tools using OSLC," designed for customers not participating in VoiCE Session CEE-2022: Wednesday 4:15-4:45, "Driving Product Development Across the Bridge to Product Lifecycle Management," focus on PLM integrations with PTC Windchill PDMLink IBM Rational Board of Advisors (BOA) meeting - Thursday 12:30-1:30 on PLM integrations, based largely on what we present at the VoiCE session targeted to a different levels of customers Exhibition floor - We'll have a pedestal in the Continuous Engineering zone for "PLM Integrations" where we'll be demonstrating a Technical Preview of the Windchill CM integration 19

20 Copyright IBM Corporation All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

21 Engineering Lifecycle Manager provides a new platform for lifecycle collaboration across enterprise artifacts Rational Engineering Lifecycle Manager provides the key product and structure for the engineering and ALM landscape and make these available for queries and views across the available all enterprise resources Product definition structure with Components, version identity and variant Dimensions e.g. Structure Product ABC123 Ver Vn Dims D1..Dn Component view with contributing artifacts Engineering Lifecycle Manager Composite Product view ABC123 Ver Vn Dims D1..Dn Component re-use find use Product ABC123 variant Ver Vn Dims D1..Dn Product view PLM part ref id Requirements view Alternate Components Options Implementation & other views Lifecycle Query 21 ERP Docs SCM PLM RM