Skip to main content

An Interview with Neebula Co-Founder - Part One

Pete Goldin
APMdigest

In Part One of BSMdigest’s exclusive interview, Ariel Gordon, Neebula VP of Products and Co-Founder, and BSM pioneer, talks about the concept, history and evolution of Business Service Management.

BSM: To set the stage for this interview, first tell me about your history with BMC.

AG: I joined BMC through the acquisition of New Dimension in 1999. I was the CTO of New Dimension at that time and so I became a member of BMC’s new CTO team. At the time BMC was unable to sell at the CIO level and we had funny ads in the papers: “We are BMC … We are the silent giant from Wall street, you don’t know us Mr. CIO but we run your IT”. To help resolve it, the new CTO team offered BSM as the strategy that would integrate our management solutions around this theme and enable BMC to sell at the CIO level.

I was given the task to work with Business Development to design the solution. We came back with the architecture and roadmap of the needed solution. The solution was centered on an “Object Store” which included a record of all the IT assets and a service model that mapped the infrastructure to the business services. The strategy also included the acquisition of an ITSM product suite and a BSM aware event management product. This “Object Store” was later renamed by us as “Atrium CMDB”.

After BMC completed the first phase of the project, the second phase was to make all the BMC products integrate to the CMDB and between themselves to create a BSM solution. By then I became BMC’s CTO, and in that role worked with key BMC architects and teams on the design, creation and development of the Atrium integration technology within BMC. I left BMC at the end of 2007 to return to Israel.

BSM: What was the initial driver behind the creation of Business Service Management?

AG: At the end of the 90s it became clear that the concept of Frameworks was beginning to fail. Services started to span across many servers (and applications) and silo management could not provide the availability and quality needed and it was clear that you needed to look at services as a whole and not only at the individual components.

As usual, customers and in particular leading edge banks and Telco’s, were in the frontline and created their own solutions. I remember visiting four such banks to see private solutions they had created. In addition, software companies started to note this and a number of startups were trying to fill the void, Sysstar, Proxima, Managed Objects, Interlinks, Appilog, to name a few. At this time it was called Service Management – the context of Business (BSM) was added later. At that time, BMC was looking for a way to become a leading vendor in the eye of the CIO and using this new trend looked like an opportunity that could not be missed.

BSM: I heard that BMC coined the term "BSM" – is this true?

AG: When we decided to adopt the term BSM inside BMC, we were looking for a catchy term for our strategy that we can turn into an industry trend that would replace and “wash away” the framework concept of our competitors. BMC decided not to register BSM as a trademark with the hope that many other organizations would adopt the same term. So even though I think BMC was the first to coin the term, I am afraid we will never know this for sure. One thing is clear: that BMC’s decision to make BSM its strategy, not to register it as a trademark, and push the concept with all its marketing dollars in order to make BSM a major industry term, drove BSM to the mainstream of IT. This really made BSM a significant trend that was adopted by almost all the players in the industry.

BSM: Is there a big difference between BMC's initial BSM strategy and the strategy today?

AG: A lot of the concepts of the original BSM strategy are still in place but even in 2007 BMC was more focused on the ITSM side of the solution than the availability management side. And today our market and industry are very different than the one we had in 2001. Back then, virtualization existed only on the IBM mainframe, and consolidation and cloud computing was not even a dream. BSM was designed in an era when data centers were static and was definitely not built to support these new dynamic environments. So BMC and other vendors like HP are adding new cloud management components to the strategy, and are trying to strengthen their current BSM solutions to cope with this paradigm shift, however this effort is huge and there is still a big gap between what they provide and what customers are in need of. To fill this void there are new startups like Neebula.

BSM: How have BSM tool capabilities evolved over the years?

AG: The BSM idea was how to loosely integrate all of the IT management tools in order to enable the management of IT from the perspective of the services that IT provides to the business. The integration was centered on a CMDB and a service configuration model that describes the services. This model is then used by all the BSM-enabled products.

Initially in 2001-2002 this was a very novel concept without any real technology behind it. Only in 2004-2005 with the release of BMC’s Atrium, HP’s BSM solution and other vendors’ solutions, did BSM really take form and have integrated solutions that customers could use.

Today, the BSM solutions out there are much more integrated and mature but the building and maintaining of the service configuration model is still an issue, as it is so costly. That is one of the major reasons for BSM implementation failures.

BSM: What is the biggest challenge with BSM today?

AG: The biggest issue is the changing paradigm of IT infrastructure e.g. the move to virtualization, private clouds, and public clouds with all its variants, IaaS, PaaS, SaaS. We are not yet seeing the effect of these changes on IT shops. This will take years as organizations morph themselves to benefit from the new capabilities. And these changes will be radical – internal IT infrastructure and the teams that manage them will be eliminated.

The BSM concepts were designed 10 years ago and the solution – because of the modeling issue – is hard and lengthy to implement, slow to react to change, and by nature not agile. That is exactly the opposite of what is needed today, and so these tools are now becoming one of the shackles that are blocking the move to the new IT infrastructure. I am afraid that unless a new breed of BSM tools is created, BSM as we know it today will disappear.

BSM: What do you consider “true BSM”?

AG: A true BSM solution is any solution that allows organizations to manage their IT infrastructure and their applications from the quality of the service that it provides to the business. At the heart of such a solution is a map or a model of each service that allows the organization to understand all the components that are needed in order to provide this service. A true BSM solution has a set of tools that use this mapping to provide comprehensive management of the business services, including their performance and quality of the service.

Click here to read Part Two of the BSMdigest interview with Ariel Gordon, VP of Products and Co-Founder of Neebula.

Hot Topic
The Latest
The Latest 10

The Latest

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

The gap is widening between what teams spend on observability tools and the value they receive amid surging data volumes and budget pressures, according to The Breaking Point for Observability Leaders, a report from Imply ...

An Interview with Neebula Co-Founder - Part One

Pete Goldin
APMdigest

In Part One of BSMdigest’s exclusive interview, Ariel Gordon, Neebula VP of Products and Co-Founder, and BSM pioneer, talks about the concept, history and evolution of Business Service Management.

BSM: To set the stage for this interview, first tell me about your history with BMC.

AG: I joined BMC through the acquisition of New Dimension in 1999. I was the CTO of New Dimension at that time and so I became a member of BMC’s new CTO team. At the time BMC was unable to sell at the CIO level and we had funny ads in the papers: “We are BMC … We are the silent giant from Wall street, you don’t know us Mr. CIO but we run your IT”. To help resolve it, the new CTO team offered BSM as the strategy that would integrate our management solutions around this theme and enable BMC to sell at the CIO level.

I was given the task to work with Business Development to design the solution. We came back with the architecture and roadmap of the needed solution. The solution was centered on an “Object Store” which included a record of all the IT assets and a service model that mapped the infrastructure to the business services. The strategy also included the acquisition of an ITSM product suite and a BSM aware event management product. This “Object Store” was later renamed by us as “Atrium CMDB”.

After BMC completed the first phase of the project, the second phase was to make all the BMC products integrate to the CMDB and between themselves to create a BSM solution. By then I became BMC’s CTO, and in that role worked with key BMC architects and teams on the design, creation and development of the Atrium integration technology within BMC. I left BMC at the end of 2007 to return to Israel.

BSM: What was the initial driver behind the creation of Business Service Management?

AG: At the end of the 90s it became clear that the concept of Frameworks was beginning to fail. Services started to span across many servers (and applications) and silo management could not provide the availability and quality needed and it was clear that you needed to look at services as a whole and not only at the individual components.

As usual, customers and in particular leading edge banks and Telco’s, were in the frontline and created their own solutions. I remember visiting four such banks to see private solutions they had created. In addition, software companies started to note this and a number of startups were trying to fill the void, Sysstar, Proxima, Managed Objects, Interlinks, Appilog, to name a few. At this time it was called Service Management – the context of Business (BSM) was added later. At that time, BMC was looking for a way to become a leading vendor in the eye of the CIO and using this new trend looked like an opportunity that could not be missed.

BSM: I heard that BMC coined the term "BSM" – is this true?

AG: When we decided to adopt the term BSM inside BMC, we were looking for a catchy term for our strategy that we can turn into an industry trend that would replace and “wash away” the framework concept of our competitors. BMC decided not to register BSM as a trademark with the hope that many other organizations would adopt the same term. So even though I think BMC was the first to coin the term, I am afraid we will never know this for sure. One thing is clear: that BMC’s decision to make BSM its strategy, not to register it as a trademark, and push the concept with all its marketing dollars in order to make BSM a major industry term, drove BSM to the mainstream of IT. This really made BSM a significant trend that was adopted by almost all the players in the industry.

BSM: Is there a big difference between BMC's initial BSM strategy and the strategy today?

AG: A lot of the concepts of the original BSM strategy are still in place but even in 2007 BMC was more focused on the ITSM side of the solution than the availability management side. And today our market and industry are very different than the one we had in 2001. Back then, virtualization existed only on the IBM mainframe, and consolidation and cloud computing was not even a dream. BSM was designed in an era when data centers were static and was definitely not built to support these new dynamic environments. So BMC and other vendors like HP are adding new cloud management components to the strategy, and are trying to strengthen their current BSM solutions to cope with this paradigm shift, however this effort is huge and there is still a big gap between what they provide and what customers are in need of. To fill this void there are new startups like Neebula.

BSM: How have BSM tool capabilities evolved over the years?

AG: The BSM idea was how to loosely integrate all of the IT management tools in order to enable the management of IT from the perspective of the services that IT provides to the business. The integration was centered on a CMDB and a service configuration model that describes the services. This model is then used by all the BSM-enabled products.

Initially in 2001-2002 this was a very novel concept without any real technology behind it. Only in 2004-2005 with the release of BMC’s Atrium, HP’s BSM solution and other vendors’ solutions, did BSM really take form and have integrated solutions that customers could use.

Today, the BSM solutions out there are much more integrated and mature but the building and maintaining of the service configuration model is still an issue, as it is so costly. That is one of the major reasons for BSM implementation failures.

BSM: What is the biggest challenge with BSM today?

AG: The biggest issue is the changing paradigm of IT infrastructure e.g. the move to virtualization, private clouds, and public clouds with all its variants, IaaS, PaaS, SaaS. We are not yet seeing the effect of these changes on IT shops. This will take years as organizations morph themselves to benefit from the new capabilities. And these changes will be radical – internal IT infrastructure and the teams that manage them will be eliminated.

The BSM concepts were designed 10 years ago and the solution – because of the modeling issue – is hard and lengthy to implement, slow to react to change, and by nature not agile. That is exactly the opposite of what is needed today, and so these tools are now becoming one of the shackles that are blocking the move to the new IT infrastructure. I am afraid that unless a new breed of BSM tools is created, BSM as we know it today will disappear.

BSM: What do you consider “true BSM”?

AG: A true BSM solution is any solution that allows organizations to manage their IT infrastructure and their applications from the quality of the service that it provides to the business. At the heart of such a solution is a map or a model of each service that allows the organization to understand all the components that are needed in order to provide this service. A true BSM solution has a set of tools that use this mapping to provide comprehensive management of the business services, including their performance and quality of the service.

Click here to read Part Two of the BSMdigest interview with Ariel Gordon, VP of Products and Co-Founder of Neebula.

Hot Topic
The Latest
The Latest 10

The Latest

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

The gap is widening between what teams spend on observability tools and the value they receive amid surging data volumes and budget pressures, according to The Breaking Point for Observability Leaders, a report from Imply ...