OpenText Operations Bridge Reviews

The OVPA plugins for the various OS levels.

I'm not using it now, but when I was, it was the capability of auto fixing issues that could be customized per device, OS, or application. That seemed to make people the most excited.

It can be cumbersome to get up and running. And it's very expensive.

I used it for, probably, a total of 12 years.

Just some compatibilities with certain OS levels that I remember.

No issues, it was very stable.

No issues, in fact that's one of the features that I like about the tool.

Great.

It used to be great, but now it's off shore and is much more difficult.

No, but I've used Nagios after the fact at other places because it's cheaper, but it has much less flexible.

It wasn't complex, but, the DB behind it was the toughest part.

I implemented at the last place, alongside Pepperweed at Intrado. They were excellent.

No other options were looked at.

Be patient, and take things step by step to get it going. Once that takes place, it's pretty self-sufficient.

My primary use is the consolidation of monitoring tools and dashboards.

The most valuable feature is that everything can be consolidated into one dashboard.

The service takes a very long time to start and it requires a lot of resources. A huge amount of memory is required.

The setup process should be simplified and faster to complete.

I have been using Micro Focus Operations Manager for 15 years.

I have experienced no issues with stability.

I have not needed to scale this solution. We have fewer than 100 users and we do not plan on increasing our usage right now.

I have not needed to contact technical support within the past year.

My team has been in contact with the local Micro Focus partner and my understanding is that the local partner's skills could use some improvement.

We are using another similar tool in the company, but it is not in my department.

It took approximately one week to complete the installation and setup. I would say that the setup process is painful.

I implemented and deployed this solution myself.

I don't remember exactly how much it costs but I know that it's affordable.

I would rate this solution a seven out of ten.

It allows us to build dashboards for individual parts of the business. Our team members appreciate that they can just get a view of their part of the world without having to worry about anyone else's. This seems to be the most valuable feature for us right now.

We have a central screen that alerts us to problems from all parts of the business. This enables our operations team to have visibility of all issues and deal with them or call out as required.

I know that in the next version, X1005, they're moving to more graphical overviews, which should help our senior managers. We're looking forward to that upgrade.

I think it's been seven years since we first used it.

We've had no issues with deployment.

It's been stable though we've had issues in the past. I'm not sure whether they were hardware related or OS or the product, but it seems to be quite stable in the past few years.

I haven't bumped into any issues, so it's scaling well.

I would evaluate them as weak, unfortunately. They're barely bearable in the quality of the guys that support us. There are not always specialists in their support system. They seem to be learning as much as we are. So support is weak, I'd say.

The initial setup was straightforward. I had no problems with it.

Plan your implementation. Learn what's really important to your business that's not even from an IT perspective. That's only natural production or sale side or whatever it is and use that to map it onto your implementation. That's what I would say.

The most valuable feature of Operations Bridge is the centralization of all the alerts, events, and topology-based statistics that you can see in a centralized view for different customers internally. It could be your support groups, your management, or your governance. That's what we feel like it's giving us. It is the ability to look at it holistically, even though it's pure statistics from events and notifications. Your key performance indicators can be validated very easily and centrally.

From our monitoring perspective or from a visibility perspective, HPE UCMDB is a must have. It's an amazing piece of software. Regardless what other systems you have in your environment, you should have UCMDB in place because it performs a very good classification and discovery of your CIs. This tends to build up that service model that can be utilized between any piece of software. This is a great value we are getting out of UCMDB.

Operations Bridge, as is the OMI 10, is a great piece of software. It has a lot of potential that needs more exploration and we'll be doing that. We will be engaging my competent team, because we are working with HPE very closely, even for the developmental aspects. We are providing our inputs and we are bringing that change which is required for the tool. I must say that OMI 10 has great potential. This is where our core focus is, to improve on that potential aspect.

Reporting has to be tackled a bit more. Conceptually, it is there and conceptually it is amazing, but somehow the module itself is suffering. This is one of the issues with stability. The reporting module from HPE is not a very stable module, which is OBR to be very specific.

I'm going to have a round of meetings with the product development and the management to talk about that and to have more design plans and roadmap on this.

Not all the modules are very stable, but definitely we know from our practices and operations which ones are stable. Regarding the ones that are not stable, we are constantly having engagements with HPE support, as well as HPE development, to make it more stable. There are a few unstable modules, but most of them are very stable and long running. As our environment is changing, the requirements are changing and we are adapting based on our plans.

Initially, we started with the normal support. We had a lot of hiccups. Then we had a lot of discussion with the product teams, as well as the HPE account managers. Then we went for the FlexCare support, and that actually changed the way support works with us. We were able to receive Level-2 support directly instead of going to the log procedures and wasting time over the initial assessment of the cases. Then we were able to get guys directly involved in our support issues or the cases and incidents, which actually helped us a lot.

For us, the most valuable features are the ability to identify IT issues in your estates and to be able to rectify them hopefully before they cause outages to services.

It keeps our IT systems functioning, which for our company is absolutely essential.

I can’t think of anything that particularly needs to improve. I think their functionality is there now, so I don't think we need more functionality. I think we just need to get that more stable and get it quicker and maybe a bit more intuitive and easy to use. I think the functionality has just gone through the roof from what the previous products would do. So with all of these stands up and looking around, your level of automation in that has gone right up. I don't have a problem with functionality at all. It's almost too much to use all the functionality. They need to go in and start low, get what you need working and then build up.

If you're using the full functionality, it can be a bit naive to think, “I'm going to just deliver this all singing, all dancing gold plated Rolls Royce in the solution; all in one go." For a large organization it's quite a task, so we're starting off with minimal migration and not just put another in. We are migrating from old versions of HP Operations Manager. So we have that path of migrating our legacy systems and our old monitoring policies onto the new.

We were using an older version of Operations Bridge and have migrated to the new version. Originally, when it was first based on Java, it wasn't as stable as the newer version, which we like. So, it's getting better. But we appreciate that it was a completely new product with a total rewrite and re-architecture. So you expect that sort of thing, and you expect a few patches and stabilization issues. Nothing that we didn't expect, but on the whole good.

We're reasonably large, so we started large-scale, and we've stayed large-scale. So we haven't had to scale up and we just came in at the level we needed to come in at.

Technical support has occasionally helped fix problems. They're good.

Operations Bridge was on our road map; HPE Operations Manager and Operations Bridge. It’s the enterprise tool of choice, and that's what we're sticking with. Our guys know it, and we're used to it. We've invested in time and all our monitoring is around Ops Bridge. It's a big jump to migrate to Operations Bridge from Operations Manager, let alone migrate to a different product.

Initial setup was fairly straightforward. The documentation is good, so we didn't have a problem with that. There are lots of different ways you can set it up and lots of different architectures. So choosing the one that was right for us was challenging. The documentation was valuable in that it enabled us to choose what we needed to choose.

I would advise them to look at their infrastructure and think very carefully about what they need. Only buy what they need, and start small and build up. I've seen so many projects and programs fail because they tried to deliver too much too quickly. And even with the might of HPE and HPE's contractors and the whole of HPE, we still have problems with a huge implementation of trying to bite off too much too soon. So I would advise to find out what you need, try and build on it. Get that foundation and level of understanding and eye out the problems as you go. Rather than trying to put everything in all at once and then have a stack of problems.

I don't know about anybody else, but for me, as a technical consultant I want to make sure that the products enter my strength, that it scales up properly. It's all well and good having a part, and then when you try and scale it up it all falls to bits. The support structures need to be there, and when there's a fault the labs get on it and the patches are written and issued quickly. All those sort of boring, technical reasons for me. I'm the one that deals with the errors and issues. So for me, it's less about the finances, if somebody else pays for it.

Operations Bridge is a solution that will bring together a lot of various operation data sources from the network server's applications and help the customer to focus in one area, one place, so they can escalate and route the issue to the proper resource for particular incidents. I've applied that type of software for various customers.

It optimizes their operations efficiency, and makes people more focused on the issue at hand instead of trying to figure out what's going on. It gives them an up-to-date status. If there's an issue in the IT system - whether it's a server, network, application, or resource issue – the product emphasizes it and gives you tools to troubleshoot and resolve it.

I think they are moving toward the whole platform format. They need to move away from Java, Flash, and plug-ins to streamline the integration with third-party products. This will make it easier for customers to use and deploy; using wizards and those type of things. I believe these are in the lifecycle and will be in v12.

It's been a pretty stable product. In its earlier years, it had typical lifecycle and maturity issues, but now it's at version 10 or 11 and seems to be running fairly well.

It's been very scalable; as a platform, it handles various data sources, both from HP products and third-party products.

The support team has had its struggles; it is getting better. I think the split of HP into two companies has helped, but that on-going process has created some issues. However, they seem to be working through it and getting better. I think it could be improved with regard to response time, and getting the proper resources.

I'm a senior consultant, so I've extensive experience with the products, so my issues probably should be escalated to a higher-level person from first-level support, rather than have them going through the routine scripts, because I've already done that. No reason to repeat it.

For various customers, I deployed it and helped them run it. It has its complexities because IT has its complexities. When you're monitoring IT, you're going to inherit those complexities, but HPE did make pretty good strides to pull in the data sources and make out-of-the-box integrations, both for their products and for third-party products. Making it the most seamless product possible.

We do work with other solutions. I would say HP is probably one of our largest partners but we do work with other software vendors. We do some integrations with IBM's NetCool, and with legacy products. HPE make their products modular, even at the data cluster level. We can integrate into another Ops Bridge, but we have also done some other conversions of customers’ ideas and IBM's, and converted them over to HP's products. Sometimes it's a toss-up. Sometimes it is politics in the customer's technology.

You have to have an IT operations background, be familiar with the processes of IT operations, have that type of mind-set. A lot of technologies are based on previous HPE technologies, so some history with HP's legacy products helps. Even though this is a new product, that's always helpful.

I think it's ability to bring in obviously the HP products into one place, gives you a meaningful lens, meaningful correlations, and the ability to process and to take on third-party data, event streams, and metrics. Bringing it all together and it being not as complex as building your own integrations from scratch - they give you a nice, good jump start to bring the third-party data in - is where I give it strengths.

I recommend it and obviously I do make a living deploying it, but I also like to see whether it has value at a customer's site. Can I solve some of their problems, some of their use cases? Because even if they deploy it initially, if they can't use it and get value out of it, it won't last very long. You have to make it fit in their environment and solve some of their use cases and scenarios, and then they'll continue to use it and grow with it.

It helped us move from a company that looks at its network from a resource perspective to a service perspective.

It helps me on a day-to-day basis. We used to have our services monitored by two isolated islands. One island was from the IT perspective, with servers and operating systems. The other island looked at the service from a resource perspective, with routers, switches, and an aggregation layer.

HPE helped us aggregate, and we now have all these layers in one layer. We're now looking at the service from the core of it, not from a resource perspective or from an IT, servers-based perspective.

I see room for improvement in the licensing scheme area. It's getting more complex day by day. Every day there is a new rule, so it's hard for me to plan every year and determine what I need to buy. I have to find out what I need to merge together because the license scheme changes constantly.

My company is very large. Most of the implementations in our area involve 250 or 300 nodes. We have tens of thousands of nodes serving over 2 million users. We are a large enterprise in the telecom area.

It's pretty stable right now. Every batch increases it more and more.

Scalability is great. We are an example of HPE worldwide. We are one the few sites that has 45,000 devices managed by HPE. Scalability is very huge.

The HPE setup is very straightforward. However, once you go into scalability and grow larger, that requires expertise and needs some hard work.

Through a partner

I looked at IBM, CA, and BMC. I chose HPE because it gave me all that I needed in one suite. With others, I have to integrate multiple solutions and vendors to get what I need. With HPE, I have one vendor and one source where I can get almost 96% of what I need.

What's most valuable for us is the ability to see all events that occur on our network.

It gives us the ability to monitor the entire infrastructure proactively and reactively. We can build incident event management and problem management processes in case of a problem so that an event is registered. We can then change the event to an incident and resolve it in the least amount of time as possible. If we can't resolve it, it enters our problem process where we can determine the source, possible fixes, and prevent the same problem from occurring in the future.

There are a couple of areas of improvement:

• Performance needs to increase; and
• Better correlation from the box rules.

We've used it for four years.

We haven't had any issues with deployment.

Stability is pretty OK. We previously had issues with a large amount of correlation rules, but OM has mostly eliminated these problems. We've thrown 1000 different correlation rules at it and it's working just fine.

Scalability is not relevant because it's a standard solution that's built for a particular purpose, which it accomplishes.

3-4/5

We performed the initial setup, which I'd rate as 3/5.

We did evaluate other options, but the suite of HP solutions -- Operations Manager, SiteMinder, Essentials, Service Manager -- is better than anything else out there.

Plan and then integrate. Planning requires a good assessment of your needs. Be prepared also make some in-production investments because you'll likely need to make changes on-the-go as you determine how to correct mistakes.