Will the name within the products be changing as well? (i.e. Rational Team Concert was listed as ‘Change and Configuration Management’ in the interface which always drew confusion from customers).

Why would you keep the names DOORS and Rhapsody when you’re changing everything else, especially since it goes completely against your stated reasoning above – “to make it easier to identify each product’s primary function by its name”

How are the reporting components being rebranded?

@Kenny: The name inside the products and in the documentation will change in the next release of the products. This is to allow customers and business partners time to adjust to the new naming. We have gotten some feedback that customers would like to see in the UI that the new product name “Workflow Management” align with the capability name “Change and Configuration Management” when displayed in the user interface. We are taking a closer look at that and will make a decision soon. We will not be breaking URLs or context roots or error code categories to avoid breaking applications or scripts.

@Davyd There is a lot of brand equity in DOORS and Rhapsody and those products are renamed but retain their linkage to their known brand names in the market. IBM Engineering Requirements Management DOORS and DOORS Next. In the case of DOORS this was also done to show the relationship between DOORS and DOORS Next.

@Jackie: The reporting components that are features built into the Jazz Platform products are not changing their names. So Jazz Report Builder or LQE for example will not change their names. Jazz names in general are not changing. Jazz Team Server, Jazz Source Control, Jazz Build will retain their feature names. IBM Rational Publishing Engine is a separate product and it does change it’s name as per the blog above.

@Rolf – thanks for the reply, but I would argue that there’s also a lot of brand equity in the other names too. Feedback from all my clients at the moment is that they are confused – every single one has asked where Team Concert has gone and why IBM has dropped source code and build management from the products (when clearly that hasn’t happened). They also asked why DOORS and Rhapsody were kept and not Team Concert, so it’s not just me that feels it’s a bit weird.

@Davyd Thank you for passing this on. It will take time to adjust to the new names. Requirements Management, Test Management and Workflow Management (RM, TM, WM) make up the core of our ELM solution. It will take time to get used to the new names, especially IBM Engineering Workflow Management. Other names were considered that would have highlighted change and configuration management in the name but really we do more than that as well. Workflow Management is intended to mean that we orchestrate, teams, process, plans, work items, code and builds for developers. The workflow of all those artifacts at the core of any ALM solution. It’s much more than just change management or change and configuration management. So not less, but more, the workflow and process of all artifacts involved in development.

… [Trackback]

[…] Read More here: jazz.net/blog/index.php/2019/04/23/renaming-the-ibm-continuous-engineering-portfolio/ […]

That was the perfect opportunity to resolve the confusion among users between DOORS and DOORS Next Generation. These tools are sufficiently different from each other to justify a new name for the newer tool.

In our company, we have established the terms DOORS Classic to refer to the old tool and DNG to refer to the new tool. Now that there will be the term DOORS Family, I feel this will only further confusion.

But I agree with the other name changes. Change and Configuration Management was especially misleading and I welcome the new name.

As manager of a CLM 6.0.6 installation, I welcome any and all attempts to catalog and clarify IBM’s engineering lifecycle capabilities. Would you be able brighten the lines (separation or collaboration) between “Rhapsody”, “Rhapsody Design Manager” and “Rhapsody Model Manager”?

@zak my apologies for the delayed reply, I’m just getting back from vacation. For general clarification of the relationship between Rhapsody/RDM/RMM, I believe this blog is helpful: https://jazz.net/blog/index.php/2017/10/30/mbse-across-the-lifecycle-introducing-rhapsody-model-manager/.

[…] renaming, including the new names for each of the ELM products, check out Steve DiCamillo’s blog entry on our jazz.net […]

I thought the whole point of these tools was to be light weight and simple (common interface, lighter weight work items), while enhancing communication and visibility. However, even the naming is complex… There were too many ways to refer to this tool suite before; “Jazz”, CLM, RTC, “Team Concert”, CCM…. etc. etc. etc. For admins, yes each one has a specific meaning. For the layperson who just has to use this, these names were already used interchangibly in the same meetings. Now you’ve added even more confusion. Also- won’t this hurt product/brand value for potential buyers?

@Jason thanks for your comments. We believe our Engineering Lifecycle Management solution enhances communication, collaboration, and productivity while providing ‘right-sized’ governance. Our ELM solution is designed to scale to meet the needs of the most demanding engineering organizations who are designing some of the most complex systems in the world. This is complex problem to solve, and any capable solution will have some inherent complexity.
As the blog describes, the renaming results in a simplification by eliminating some of the redundant legacy names, and changing the application names to directly indicate their purpose. This requires a transition for our existing customers, but we believe this transition will be quick and smooth, resulting in a simpler and better solution for years to come.

[…] Team Concert (RTC) is no longer the name but is now Engineering Workflow Management (EWM). See Renaming the IBM Continuous Engineering Portfolio for more […]

Is there any product renamed to IBM Engineering Workflow Software Architect Designer?

[…] [Note: this post assumes you are already familiar with ELM CM capabilities. If you need more background, start with this Knowledge Centre overview topic. For ELM application names and acronyms, see my blog post or Jazz.net.] […]

[…] of the applications have had their names changed, for better or for worse. I think some of these are going to have a hard time sticking. That said, […]

[…] also the product names themselves. It is therefore recommended that you take a look at the article Renaming the IBM Continuous Engineering Portfolio before you continue […]

[…] Engineering Workload Manager 7.0 (formerly IBM Rational Team Concert ) Eclipse client is available thru z/OS Explorer Aqua v3.1.x, and before you install it (default […]

Thanks

[…] Note: for a complete list of product names and acronyms, see my blog post or Jazz.net. […]