Talk:BMC Software

Marimba Acquisition Price

The price for which Marimba was acquired by BMC Software is $187 million according to this article. The linked source states it to be $239 million.

This source says "The transaction reflects a purchase price of approximately $239 million. After adjusting for Marimba’s expected net cash balance, as of March 31, 2004, the net purchase price is approximately $187 million." That explains the discrepancy but I don't know how to properly update the article. HalJor (talk) 18:01, 25 June 2022 (UTC)

BMC company split

I have added information regarding the BMC Software split and posted this on their Wikipedia page. Please feel free to revert these changes if needed. This information should give more context about internal business unit nomenclature for readers as well as a better understanding of what changes have occurred since the Remedy acquisition and new platform name of Helix. Attached you can find a reputable article with this information. Mdoroshevich (talk) 17:02, 6 August 2025 (UTC)

Seeking consensus on article splitting

I am a connected contributor with declared COI. I would like to discuss whether the current article on BMC Software should be split into two separate pages — one for BMC Software and one for BMC Helix.

As of early 2025, BMC Software has formally divided into two independent companies with distinct business areas and leadership structures. I have a set of proposed edits and updated sources to reflect these developments, but before proceeding, I’d like to confirm whether there is consensus to create a separate BMC Helix article (with appropriate cross-links between the two).

Feedback on whether this split aligns with Wikipedia’s content guidelines for company articles would be greatly appreciated. Thank you! SBCornelius (talk) 16:16, 21 November 2025 (UTC)

I want to hear how other editors weigh in too, but I'd vote against this. I'm imagining how both pages would look, and that a huge chunk of both of them would be nearly identical. Keeping them together seems more encyclopedic, at least for now Likeanechointheforest (talk) 20:23, 22 November 2025 (UTC)

@Likeanechointheforest, thank you for the input. I'm looking forward to see what others think and await a consensus before I propose any specific edits. Thanks again. SBCornelius (talk) 18:20, 25 November 2025 (UTC)

Hi @45dogs and @isaidnoway! Since you've both contributed to this article in recent months, I wanted to ask if you would weigh in on the issue of splitting this article since the original subject of the article recently split into two distinct companies. Any feedback or thoughts on this issue would be helpful. Thank you! SBCornelius (talk) 19:58, 3 December 2025 (UTC)

SBCornelius, how notable is BMX Helix? If you can get at least 3 sources that follow the golden rule of sourcing, its likely a good candidate for a separate article. If not, keep it confined to this page, with a redirect to this page. 45dogs (they/them) (talk page) 20:44, 3 December 2025 (UTC)

@45dogs Thank you for the input. I'll look for sourcing and let that guide the approach. SBCornelius (talk) 17:15, 4 December 2025 (UTC)

My only contribution to this article was to fix a citation error. I have no comment as to whether the article would benefit from a split. Thanks.— Isaidnoway (talk) 21:44, 3 December 2025 (UTC)

Proposing an updated intro paragraph

Per the discussion above, I agree that the article may not be ready for splitting. I'm proposing an updated intro to make the article more accurate since the split into two companies. Any feedback is appreciated. Thank you!

−

'''BMC Software, Inc.''' is an American [[Multinational corporation|multinational]] [[information technology]] (IT) services and [[consulting]], and [[enterprise software]] company based in [[Houston]], [[Texas]].<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">[<i>[[Wikipedia:Citation needed|<span title="This claim needs references to reliable sources. (November 2024)">citation needed</span>]]</i>]</sup>

+

'''BMC Software, Inc.''' is a global [[Business-to-business]] [[Enterprise software|software]] provider focused on [[IT service management|mainframe]] [[IT service management|system management]], [[cloud management]], and [[IT operations|IT operations automation]] and workflow orchestration. In 2025, the company's Helix product was spun off into the independent IT service and operations-focused company BMC Helix. Both companies are owned by [[KKR & Co.|KKR]] and based in [[Houston]], [[Texas]].

SBCornelius (talk) 18:59, 17 December 2025 (UTC)

Tagging a few people from the discussion above, and I'd appreciate any feedback on this proposed edit. Thanks for your time. @45dogs@Likeanechointheforest SBCornelius (talk) 18:01, 6 January 2026 (UTC)

Done though I kept the original first description as it was more neutral, less buzzy Likeanechointheforest (talk) 20:22, 9 January 2026 (UTC)

References

Proposing updates to the History section

Thank you, @Likeanechointheforestfor you update to the description. I also have some updates to suggest for the History subsections.

Acquisition and privatization by private equity firms

−

In May 2013, BMC announced that it was being acquired by a group of major private equity investment groups for $6.9 billion.

+

In May 2013, BMC announced that it was being acquired by a group of major private equity investment groups for $6.9 billion. The process was completed in September 2013 and the company is no longer publicly traded.

Creation of Two Independent Companies

−

In October 2024 BMC announced that it was splitting into two separate organizations. BMC Software remains the name of the company that includes the Intelligent Z Optimization and Transformation (IZOT) and Digital Business Automation (DBA) business units.

+

In October 2024 BMC announced that it was splitting into two separate organizations. BMC Software remains the name of the company that includes BMC's Automated Mainframe Intelligence (AMI) product and the data and application workflow orchestration platform, Control-M.A new company named BMC Helix will retain BMC's Helix product offering, encompassing the Digital Service and Operations Management (DSOM) business, and will be focused on the service and operations management business.

Thank you, and any feedback is appreciated. SBCornelius (talk) 19:46, 16 January 2026 (UTC)

References

Partly done: First suggestion has been implemented. Second suggestions is frankly confusing and doesn't seem to be too relevant to the a reader's understanding of the sale. Feel free to revise and resubmit. - Otherwise (Talk?) 21:05, 31 January 2026 (UTC)

@Mustbeotherwise thank you! I'll try to clarify this. It's an issue throughout the article, because everything discussed now resides in one of the two distinct companies. I'll take another run at simplifying it and resubmit. Thanks again! SBCornelius (talk) 21:17, 3 February 2026 (UTC)

I don't know the specifics but you can submit an article split request if you think that'd be appropriate. - Otherwise (Talk?) 21:19, 3 February 2026 (UTC)

@Mustbeotherwise I raised that issue here and sought a consensus about splitting before I suggested edits. The consensus was that it isn't ready for a split. Maybe others will be swayed as I try to clarify things further. SBCornelius (talk) 21:24, 3 February 2026 (UTC)

Looks like the main problem is that theirs no proof the other company is notable. Try and find 3 sources on the other company that follows the Wikipedia:Golden rule. - Otherwise (Talk?) 21:30, 3 February 2026 (UTC)

Hi @Otherwise! I've tried to make the language about the company split more accessible for the disinterested reader. Please let me know what you think of this version. Thank you!

−

In October 2024 BMC announced that it was splitting into two separate organizations. BMC Software remains the name of the company that includes the Intelligent Z Optimization and Transformation (IZOT) and Digital Business Automation (DBA) business units.

+

In October 2024 BMC announced that it was splitting into two separate companies. BMC Software will focus on mainframe systems and automation software used to run large-scale computing processes. A second company, BMC Helix, will focus on software for managing IT services and day-to-day digital operations and system monitoring.

SBCornelius (talk) 16:54, 11 February 2026 (UTC)

Hi @Mustbeotherwise, I hope all is well. Thank you for the time you put into this before. If you have a second, please let me know if this version addresses the issues you raised earlier. Thanks again! SBCornelius (talk) 20:09, 25 February 2026 (UTC)

Most of what you requested is already mentioned in the article's first paragraph. I don't see why we have to repeat what BMC Helix does for a second time. Accordingly, I am closing this edit request as partially done. Altamel (talk) 03:20, 24 April 2026 (UTC)

Suggesting rewrite of the Products & Services section

I am a connected contributor with a declared COI. Given the recent split of BMC Software into two distinct companies, and the fact that one retains the name BMC Software and one does not, the Products & Services section needs clarifying edits because it mentions things no longer belonging to the company "BMC Software", which is the title of this article. My suggested rewrite is below.

---

Products and services

−

BMC Software provides support for enterprise [[mainframe]]s with its Automated Mainframe Intelligence (AMI) product line (known internally as IZOT).<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">[<i>[[Wikipedia:Citation needed|<span title="This claim needs references to reliable sources. (January 2026)">citation needed</span>]]</i>]</sup> AMI use machine learning to attempt to improve efficiency.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">[<i>[[Wikipedia:Citation needed|<span title="This claim needs references to reliable sources. (March 2026)">citation needed</span>]]</i>]</sup>BMC's Control-M software (internally known as DBA) allows businesses to run high-volume [[batch processing]] to optimize complex business operations, such as [[supply chain management]]. Users can access these batch jobs through a graphical interface. In 2019, the firm made the program available in a [[Docker (software)|Docker]] container, simplifying deployment. In 2020, the firm launched an [[SaaS]]-based version of Control-M. Helix, formerly known as [[Remedy Corporation|Remedy]], is the company's service management business unit.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">[<i>[[Wikipedia:Citation needed|<span title="This claim needs references to reliable sources. (March 2026)">citation needed</span>]]</i>]</sup> TrueSight is the company's AI and [[machine learning]] product line.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">[<i>[[Wikipedia:Citation needed|<span title="This claim needs references to reliable sources. (March 2026)">citation needed</span>]]</i>]</sup>

+

BMC Software, Inc.BMC Software provides support for enterprise [[Mainframe|mainframes]] with its Automated Mainframe Intelligence (AMI) product line (known internally as IZOT). AMI use machine learning to attempt to improve efficiency.BMC's Control-M software (internally known as DBA) allows businesses to run high-volume [[batch processing]] to optimize complex business operations, such as [[supply chain management]]. Users can access these batch jobs through a graphical interface. In 2019, the firm made the program available in a [[Docker (software)|Docker]] container, simplifying deployment. In 2020, the firm launched an [[SaaS]]-based version of Control-M. BMC Helix[[Remedy Corporation|Remedy]] was rebranded as Helix and, in 2025, was spun off into the independent company BMC Helix. Helix provides enterprise IT service and operations management.

Hi @Otherwise! These edit requests have been in the queue for a bit, and I realize the backlog is currently extremely high. I thought that since you made some edits to this article recently, you might be willing to take a look and provide some feedback. Thank you, and best of luck working through the backlog. SBCornelius (talk) 19:45, 20 March 2026 (UTC)

Always add a Template:reflist-talk to the bottom of every section which includes 'ref' tagged citations. Do not create top-level sections for content, as these will make a mess of any future talk page archives. As a paid editor in a volunteer project, do not make other people clean up after you. Grayfell (talk) 21:47, 20 March 2026 (UTC)

@Grayfell, thank you. I will apply these practices moving forward. SBCornelius (talk) 19:36, 26 March 2026 (UTC)

Templates are for non-controversial changes. This is too broad, and this proposal includes too many promotional buzzwords. If you wish to continue discussing this, do so, but propose more neutral language and do not re-open this template until consensus has changed. Grayfell (talk) 21:49, 20 March 2026 (UTC)

Hi @Grayfell! Thank you for taking a look and for the feedback — I understand the concern about scope and tone.

I’ll work on revising the language to remove jargon and reduce any phrasing that may come across as promotional, with the goal of making the section clearer and more neutral for a general audience.

That said, I do want to flag the underlying issue I’m trying to address. Following the company’s announced split into two independent businesses, the current Products and Services section describes products that now belong to different companies without distinguishing between them. As written, this creates some factual ambiguity about which entity is responsible for which products.

Before proposing changes, I reached out to several editors about whether the article should be split, and the consensus was to keep a single article. Given that, I'd like to update the existing section's accuracy.

I’ll revise the proposal with more neutral language and a narrower scope so it’s easier to evaluate. Once I’ve done that, I’ll bring it back here for further discussion and include the editor who helped arrive at the consensus for not splitting the article. Thanks again for your time. SBCornelius (talk) 19:49, 26 March 2026 (UTC)

Hi @Grayfell, thanks again for the earlier feedback. I’ve taken another pass at this with a focus on simplifying the language and removing anything that could read as promotional. I have replaced the previous version in my original post to keep the reflist template accurate.

This revision is more limited in scope, but it does still separate BMC Software and BMC Helix within the Products and services section. The goal here is to address what appear to be factual issues following the company’s split.

Also tagging @Likeanechointheforest and @45dogs per the earlier consensus on not splitting. I understand the preference is to keep a single article rather than split, and given your role in that, I hope you can take a second and weigh in on my proposal for this section.

Happy to refine further if there’s a simpler way to present this, but wanted to share an updated version that focuses on clarity and correctness.

Thanks for taking another look. SBCornelius (talk) 17:35, 31 March 2026 (UTC)

This proposal is unacceptable. Neither 'ktsl.com' nor 'softwarereviews.com' appear to be a reliable source. "AiThority" is PR churnalism, and should not be cited either. Further, a source from 2019 cannot support a 2025 rebranding. The 2016 source doesn't mention anything at all about machine learning or AI. While "insights" is an industry term, it's also both jargon and a buzzword, so it should not be used. Cite and summarize reliable, independent sources. Do not misrepresent sources. Again, this proposal is unacceptable.

If and when you address all of these issues, consider using Template:Text diff so that other people can tell what, exactly, is being replaced. Grayfell (talk) 22:08, 31 March 2026 (UTC)

Hi @Altamel! Thanks for reviewing my edit suggestion. Can you provide a few details about what you think needs to change to make this acceptable? The problem is that this article is now about two different companies and is in error unless some sort of distinction is made in this section. Any feedback will be helpful. Thank you! SBCornelius (talk) 17:25, 6 May 2026 (UTC)

References

"Tideway Systems" listed at Redirects for discussion

The redirect Tideway Systems has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 May 17 § Tideway Systems until a consensus is reached. Steel1943 (talk) 21:30, 17 May 2026 (UTC)

"Marimba, Inc." listed at Redirects for discussion

The redirect Marimba, Inc. has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 May 17 § Marimba, Inc. until a consensus is reached. Steel1943 (talk) 21:33, 17 May 2026 (UTC)

"Track-It!" listed at Redirects for discussion

The redirect Track-It! has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 May 17 § Track-It! until a consensus is reached. Steel1943 (talk) 21:34, 17 May 2026 (UTC)

"BladeLogic" listed at Redirects for discussion

The redirect BladeLogic has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2026 May 17 § BladeLogic until a consensus is reached. Zackmann (^{Talk to me}/_{What I been doing}) 22:57, 17 May 2026 (UTC)

Proposing clarifying subheadings for Products & Services section

Thank you to everyone who reviewed my previous request about the Products & Services section. Your feedback is noted and accepted. I do have one last minor request that I think would clarify the fact that the article is now about two separate companies. I want to propose adding two subheadings to this section. The first two paragraphs should be under the heading BMC Software, and the last two sentences under BMC Helix. Thank you for your time and consideration. SBCornelius (talk) 14:19, 18 May 2026 (UTC)

Hi @Grayfell! Thank you for all of the feedback you've previously provided about this article. I was wondering of you have an opinion about my suggestion above concerning adding headers to the existing product section to clarify that the products mentioned are referencing two distinct companies? Please let me know if you think this would be a good solution. Thank you. SBCornelius (talk) 16:23, 15 June 2026 (UTC)

Please propose reliable sources for this change. Grayfell (talk) 18:03, 15 June 2026 (UTC)

Just to recap here SBCornelius, you submitted a request back in March which was ultimately found to be inadequately referenced. My colleague Grayfell informed you of this inadequacy on March 31. You then responded to Altamel, asking for their input. Then on May 18, you pivoted to begin asking about having two seperate subheadings. One month after that, you posted a followup asking once again to split subheadings because its referencing two distinct companies. Then just yesterday, Grayfell responded by asking for reliable sources to support the change (perhaps harking back to their March 31st direction to provide reliable sources, which you did not appear to have answered at the time). So, setting aside the question of two subheadings, I'd like to go back to the information which you were attempting to modify way back in March. It seems that was never given adequate references. It's my guess that is why you're having difficulty placing this information in what you feel is its correct positioning in this particular section—because of the possibility of it being inadequately referenced. So let's make sure that the text we are wanting to alter is properly referenced, and then we can talk about placing that text into two separate subheadings. Regards,  Spintendo  12:14, 16 June 2026 (UTC)

Hi @Spintendo! Thanks for the reset! I'll dive back in with a reference-first approach and come back once I know what can be supported. Thanks again. SBCornelius (talk) 19:50, 29 June 2026 (UTC)