Infrastructure Management Software Blog

OH, IL, WI, IN, MI Operations Center Technical Roadshow - April 20th to April 29th - Don't miss it!

Ever wish you could talk face-to-face with more technical people about Operations Center and Network Management Center products? Don’t really have the time or budget to travel very far to do so?  Well, here is a great opportunity to meet and talk with technical experts on products like Operations Manager and NNMi – right in your background.


Vivit will be hosting a series of six (6) one-day sessions, where there will be a nice mix between presentations and Q&A sessions around these products.  The sessions will be held in the following states on the following days:


- (Columbus) Ohio – April 20, 2010


- (Orrville) Ohio – April 21, 2010


- (Dearborn) Michigan – April 22, 2010


- Wisconsin – April 27, 2010


- (Chicago) Illinois – April 28, 2010


 - (Fishers) Indiana – April 29, 2010


Feel free to contact me if you have any further questions about this roadshow at asksonja@hp.com.

Labels: agent| agentless| agentless monitoring| agents| automating operations management| automation| BES| BlackBerry Enterprise Server| CMDB| consolidate events| consolidated event| Consolidated Event and Performance Management| consolidated event management| Consolidated Management| correlate events| DDM| Discovery and Dependency Mapping| event console| event consolidation| event correlation| event management| Hewlett Packard| HP Network Node Manager| HP OMi| HP OpenView| HP Operations Center| HP Operations Manager| infrastructure management| infrastructure monitoring| IT dashboard| IT infrastructure management| IT infrastructure monitoring| IT management| manager of managers| managing IT| managing IT infrastructure| managing IT operations| monitoring| Network Management| Network Node Manager| NNM| NNMi| Norm Follett| OM| OMi| OML| OMU| OMU 9.0| OMW| OpenView| OpenView Operations| Operations Center| Operations Manager| Operations Manager i| Operations Manager on Linux| Operations Manager on Unix| Operations Manager on Windows| performance| Performance Agent| performance management| Performance Manager| performance monitoring| SiteScope| Smart Plug-in| Sonja Hickey| SPI| TBEC| Topology Based Event Correlation| topology-based event correlation| virtual server| virtual servers| virtual systems management| virtualization management| Virtualization SPI| virtualization sprawl| virtualization strategy| virtualizationation| virtualized environment| virtualized environments| Virtualized Infrastructure| Vivit

Rip and Replace - Never (Operations Manager has 15 years of stability)

There has been some FUD thrown around by one of our competitors about HP’s commitment to our Operations management products. This nameless competitor is calling for HP customers to migrate to this competing suite of BSM products. They even have specific plays for HP OpenView Operations (now called Operations Center), SiteScope, and several other HP Software products.


Let me be very clear about one thing:
HP Operations Center has NEVER required a rip and replace upgrade!



HP understands the production nature of it IT infrastructure monitoring products and is very sensitive about forcing its customers to migrate. The same cannot be said about our unmentioned competitor. Their migrations are neither easy nor free.


A good example of our commitment to stability is OMi. It introduces significant new functionality such as Topology-Based Event Correlation (TBEC) as an overlay to our existing Operations Manager products that fits seamlessly into existing deployments. This allows customers to leverage their existing investment in management servers, agents, and Smart Plug-Ins - with no rip and replace.


If you have any questions about this or want to discuss our competitors false claims, please let me know.


For Operations Center, Peter Spielvogel

When is a NOC an Operations Bridge

I've been pondering about recognition of the term "Operations Bridge" for some time now and decided I'd air some thoughts and see what people think.
 
The term "NOC" (Network Operations Center) has been floating around for years, it seems to originate in the telco world but has been adopted by many organizations to refer to some sort of centralized operations function.


But then a lot of organizations still use the term NOC to refer to the Network (only) operations center - the silo which owns and operates the network.
 
So there's the problem that I have with the term NOC.. It's somewhat indistinct, means different things to different people.
 
ITIL V3 recognizes the term "Operations Bridge" as part of the "Service Operation" discipline:
"A physical location where IT Services and IT Infrastructure are monitored and managed."
 
My view is that this is a nice clear definition of the 'modern NOC '- the place where ALL IT infrastructure monitoring comes together and is related to the services which depend on the infrastructure. It avoids confusion about whether we're talking about a "network only" monitoring silo or a full consolidated event and performance management organization.
 
We're using the term Operations Bridge in our own outbound marketing materials. But here is the "rub"... We've done some surveys and the term "Operations Bridge" is not universally recognized - i.e. People do not instantly recognize it or are able to explain what it is.
 
This is not everyone of course but it is true of a large proportion of the people that we tested the term with. I have to add that recognition levels are higher in Europe than the US, maybe something to do with the broader adoption of ITIL . 
 
Interestingly as soon as you start to explain what an "Operations Bridge" is, people "get it" - you don't even need to finish the explanation. It just makes so much sense - and everyone understands the concept of a "Bridge" as a central point of monitoring and control, either because of some nautical knowledge or a passion for Star Trek.
 
So, I'm on a campaign to drive widespread adoption of the term "Operations Bridge" - and move away from the indistinct and sometime confusing term NOC. Make NOC exactly what it states - an NETWORK Operations Center, and use Operations Bridge to describe a 21st Century consolidate IT Infrastructure monitoring function.
 
What do you think? Please enter your response in the comment field below. You may respond anonymously, if you choose.


(A) Yes NOC should be network only, "Operations Bridge" is the centralized monitorng point
(B) No, NOC is the right term
(C) It does not matter, both terms can be used
(D) Other (please elaborate)


For Operations Center, Jon Haworth

Search
Showing results for 
Search instead for 
Do you mean 
Follow Us


HP Blog

HP Software Solutions Blog

Labels
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation