BMC Communities Banner

The BSM Ecosystem

4 Posts tagged with the ecosystem tag

- By Fred Johannessen, Technology Alliance Program and Market Zone

 

The music ecosystem and commonality with the software industry.

 

I'm not really a Ray Bradbury fan, I got this title from a Weather Report album, which was no doubt inspired by the Walt Whitman poem. Weather Report was instrumental in the transition from traditional jazz to jazz fusion.  Joe Zawinul (keyboards) and Wayne Shorter (sax) were on a couple of Miles Davis' fusion albums and then broke away, forming the new group called Weather Report.

 

My favorite album of theirs is "Heavy Weather", which included one of the best bassists of all time, Jaco Pastorius (RIP). A real work of genius on that album is "The Juggler", which has my very favorite song ending - a single forlorn bass note giving an ironic twist to a complex song. Jaco later connected with Pat Metheny and you can still hear Jaco's influence in Metheny's later albums with Mark Egan on bass.

 

It's fascinating to trace these influences and their branches into other genres of music. At each juncture, a musician influenced another musician by participating in the creation of new music, but their influence continued well after they moved on.

 

Before open source, the ISV world was Borg-like, “resistance is futile. We had no choice but to absorb, regurgitate and attempt influence through traditional marketing, creating countless standards committees, and raiding each other's staff. Software is now growing up. Adding open source to the ecosystem creates the opportunity for collaboration between developers regardless of corporate affiliation. The resulting innovations can then be incorporated and used in powerful, sometimes unanticipated ways. Each participant in the process is affected.

 

I believe it is mandatory that anyone who calls themselves a "professional" developer must be able to show examples of open source contributions - and the companies they work for should encourage this participation. These contributions become the incubator of innovations that will later find their ways into commercial applications that will help change the world.

 

I’m proud to say that BMC’s permissive licensing is a potent enabler of rapid development and innovation in the systems management space. Permissive licensing incents developers to build on the baseline code provided and build commercial innovation. And I believe that as such developments become visible to the community there will be natural pressure to encourage contributions back to the community. A good name is still important in the industry. In addition to this, market demand has created the opportunity for enthusiastic partnerships in the new ecosystem to help fill existing and future software needs. This can be in the area of platforms, specialized applications, and variations of current applications. Just look at all the custom applications developers have done on the Remedy Action Request System. It's important to have the infrastructure for the market to express their needs and to have those needs met with either commercial or open source software - and they are not mutually exclusive.

 

We have all this with developer.bmc.com. Take a look.  Participate.   Give feedback. Check out the new podcast with whurley and me talking more about BMC Developer Network.

 

 

The postings in this blog are my own and don't necessarily represent BMC's opinion or position.
| More
0 Comments Permalink

Welcome to the Show!

Posted by Alena Hitzemann Jul 27, 2007

- By Fred Johannessen, Technology Alliance Program and Market Zone

 

 

Announcing BMC Developer Network (BMCDN) and Open Source offerings.


Welcome back my friends to the show that never ends


We're so glad you could attend


Come inside! Come inside!


~From Karn Evil 9: First Impression on Emerson, Lake, & Palmer's Brain Salad Surgery Album

 

 

 

ELP is one of the original progressive rock bands with the original likely being King Crimson (Greg Lake's original band). Prog music is fun to trace because you can see influences inside and outside the genre even into pop music. The music industry is an interesting ecosystem that is always riding an edge between IP protection and creative license. When does a technique or a riff or lyric move from protected property to open source? And as most would agree, the music industry does not deal well with open source. :-) However, there are many examples of modern music openly using classical riffs from greats like Beethoven and Bach - so it does exist. And so it goes with the software industry - there are fits and starts with ISV's incorporating, developing, and contributing to open source but it is happening and becoming a larger and larger factor in ISV strategies. And thus it goes with BMC - we actually have, since Y2K, incorporated, developed, and made open source contributions - but generally not in a strategic context. Now we are.

 

In my last blog entry, I mentioned; "Such a strategy requires an infrastructure that narrows the distance between the platform provider and the developer community". This was an allusion to our BMC Developer Network which whurley announced at OSCON this week.

 

We've actually been semi-live with BMCDN for a couple of months, migrating the Remedy groups and also creating new forums aligned with our BSM strategy. We are also in the process of migrating the DevCon (a.k.a.: PATROL Developer Connection) to BMCDN. But, as you can tell, our release Open Source adapters at BMC is significant and, I believe, helps complete our ecosystem approach.

 

BMCDN is by no means perfect nor complete. We had a choice to attempt sterile perfection or to get the word out and truly commit to having the developer community drive the structure and content of the BMCDN. We chose the latter. So we have an initial structure and we have some content, but I'm hopeful that a year from now we'll have something completely different that has been tailored and built in conjunction with our development community.

 

I would like to acknowledge the hard work over the past year by people on my team including Ken Beck, David Fiel, Joe Vodvarka, Scott Powell, and Luis Laborda in getting this BMCDN ready. This not only included development of the infrastructure, but also included getting the open source adapters built, licensing schemes debated and agreed, and coordination with R&D and Marketing.

 

I'm excited about what we have and more excited about where our development community will take it. Come and join the show -- the BMC Developer Network developer.bmc.com!

 

 

The postings in this blog are my own and don't necessarily represent BMC's opinion or position.
| More
0 Comments Permalink

- By Fred Johannessen, Technology Alliance Program and Market Zone

 

I ran into Kash Noorani an Architect of our Dashboards and we got talking about ecosystem - since I describe my job as building the inbound ecosystem. We were discussing the importance of having developers build integrations and innovations on our platforms such as CMDB, AR, and, of course our dashboards. He pointed me to the funny yet scary "Developers,   developers, developers" rant by Steve Ballmer. It brings a realization that what makes a vibrant and lasting ecosystem for a software platform is the developer community. They are the source of innovation that extends the platform solution into new technology areas. An example of this is Aeroprise, and BMC development partner that extends our Remedy applications into mobile devices. They also can extend solutions into vertical markets such as TuringSMI and the Telco/eTOM solutions they provide. And, of course, these developers help grow the market, thus the pie for all of us while providing greater value to our mutual customers. The integrations and extensions aren't limited to commercial ISV software, but include "toolkit" source and binaries that help customers perform a specific task, and also open source software. There is no reason that a complete solution for a customer cannot or would not include all such components, in fact, a credible ecosystem strategy must include all of them.

 

Such a strategy requires an infrastructure that narrows the distance between the platform provider and the developer community to the point where there is near seamless interaction with all elements of the ecosystem - joining customers, developers, and the solution provider into one dynamic bazaar. I think this is where ISV's can learn a lot from the open source community...

 

 

The postings in this blog are my own and don't necessarily represent BMC's opinion or position.
| More
0 Comments Permalink

Virtual to Virtual

Posted by Alena Hitzemann Mar 20, 2007

- By Fred Johannessen, Technology Alliance Program and Market Zone


My role has changed from focusing on virtualization to helping build the ecosystem for BMC - the virtual platform.

 

It’s been awhile since I’ve blogged and since my last blog I’ve taken on a new role in BMC. I had been focused on (among many things) virtualization and BMC’s approach to managing virtual environments. You’ll notice in my last blog that I was talking a bit about ecosystem. Well, I got the opportunity to run our Technology Alliance and MarketZone organization – a major component for helping to build out the BMC ecosystem. My organization helps other companies gain access to software and consulting to help build out integrations to BMC technologies such as CMDB, Remedy ARS, Performance Manager, and others. We also help market and sell the products from those companies that fill gaps or enhance our solutions. No solution in IT is comprised of only a single vendor’s capabilities – the solutions are built of components from several companies – BSM solutions are the same. Just think of a car. You might buy a “Ford”, but the Ford is comprised of tires made from Goodyear, a Sirius satellite receiver, and on and on with components from other vendors/partners.

 

BSM solutions, while being comprised of major components built by BMC, still have partner componentry as part of the whole solution. For example, BMC has the leading Knowledge Management for Service Desk in the industry. Some customers may want to purchase off-the-shelf knowledge to get their knowledge-base started. We work with partners to provide the knowledge content that populates our Knowledge Management solution. Same goes for Network Configuration, Mobility, Notification, and other areas that complement our core solutions.

 

We are being very aggressive about building out the ecosystem across the solution set and have some pretty exciting and new programs coming out around developer enablement and communications and open source. I’ll expound more on these areas later…

 

The bottom line is that BMC has a complete BSM set of solutions and these solutions have a healthy ecosystem around them. BSM presents, if you will, a virtual platform for enabling a whole solution that includes best-in-class for every aspect of the infrastructure from hardware to network to application to business process. Thus I see my role as having changed from focusing on virtualization technology to helping to build the virtual business – the ecosystem around BMC’s solutions.

 

 

The postings in this blog are my own and don't necessarily represent BMC's opinion or position.
| More
0 Comments Permalink