HCL Connections Reviews

• Business contacts network: You can define a business network like LinkedIn, but limited to your installation. You can also view the organizational chart inside the tool.
• Communities: One of the best functionality of the product. Complete functionalities.
• Automatic notifications: Users receive notification of all activities done on Connections. When files created, modified, ..., the platform advise users of some of the contents within the function of the role and the past activities. Users can also decide the way in which notifications are sent (they can filter the type of event and also the timing).

Marketing has created a community open to all internal employees where it has centralized all marketing content (brochures, presentations, communications).

Compared to the past, now we have a single point of interest where all content is available, and all employees receive a notification when new content is published. In addition, all employees can provide feedback and a personal impression about all shared content.

File management: File management is a little poor. For example, you don’t have the ability to create a folder or organize the contents of a folder. Some functionalities are available only if the customer also buys the IBM FileNet platform.

User management: Users are mainly on LDAP. There is no way to create a user “on the fly” and to add it to a community or business network. You must track all users on LDAP before interacting with them and this is very boring, especially if you have to interact with external users.

I have used it for two years.

I had some problems on earlier releases; in 4.5, I’ve only noticed some browser incompatibilities.

I have not encountered any scalability issues.

Technical support is 8/10.

I did not previously use a different solution.

Initial setup has been simple.

Pricing is not so “easy to access”; licencing is for a single user.

Before choosing this product, I did not evaluate other options.

It’s very important to understand what you want to do with “social” before implementing something on the platform.

The most valuable feature is definitely Files. We have totally transferred the way we work, or developed the way we work on information. The ability to upload files into the cloud, the sharing options, and, even better, the commenting options and the @ mentions on the file just eases the workflow dramatically compared to using email and sending attachments back and forth.

It saves a lot of time, includes more people that need to be included and it ensures better quality.

I’m happy with what I saw at a recent conference regarding Connections Pink and Orient Me.

We have had no downtime.

Scalability is okay-ish. We are more or less satisfied with the way it works. No major need for fixing it.

Technical support is great.

We knew we needed to invest in a new solution because we got advice from our business partner and from IBM that opened up our eyes to see the options out there.

Initial setup was complex. We suffered some setbacks on the migration from the on-prem solution to the cloud. We are currently in a hybrid solution and the migration didn't work exactly how it was supposed to; so we had some challenges on migrating.

We looked at Microsoft.

Quality and cost are the most important factors when selecting a vendor.

Just do it.

There are multiple applications available for the user.

• The blogs became the main source of information for the organisation and establishing dialogue.
• The forums are the best places to get and provide peer powered support.

Design and user experience.

Design: They present consistent shortcomings across their applications. For instance, when you are in a sub-community, it's difficult to figure out what other sub-communities are a part of the parent community. Whenever you land in a sub-community application, it's difficult to navigate to the parent one.

Another example is how the newsfeed tries to provide you with extra information with a blurb hovering to the right. However, it's actually the same information available on the newsfeed item.

User experience: The many ways in which you could use their different applications is, for most users, simply overwhelming.

IBM Connections can be a really good product for power users. However, for most of my users, the consistent feedback has been about how difficult it is to use and how the interface is poorly designed.

I used the solution for about two years, from 2013 to 2015.

The forums struggled to keep up when multiple users posted information.

I am not aware of any issues regarding scalability.

I would give technical support a rating of 9/10.

I am not aware of any previous solutions.

The setup was rather simple. IT handled most of the implementation. The functional owner designed a series of standard communities for everyone to join.

Using IBM Connections as a standalone product to replace the intranet is not enough. Further investment is required for a landing page, either from IBM solutions, or from any of their partners.

We evaluated Jive and Yammer.

You need a strong governance model and an effective adoption strategy. If possible, do not use the IBM Connections Files app as the main CMS of the organisation.

Connections is a full-featured enterprise social network solution. Below are some of the features most used by our employees:

• Files and document management, including file sharing and libraries
• Employee profiles
• Communities
• External communities
• Blogs
• Status posts
• Activities

Connections, with its file sharing and lightweight document management capabilities, has helped us reduce the volume of email and network file usage.

Ideally, the product will increment advances from consumer social networks and file sharing tools sooner, as users expectations are formed by the software they use at home and on their devices.

We have used IBM Connections since early 2013, beginning with version 4.0. In 2015, we upgraded to version 5.0. Throughout, we have used the on-premises solution.

In 2016, we extended the platform to external users via external communities.

We have not had any stability problems.

We have not had any scalability problems.

We used a variety of business partner support models and have been pleased with the support.

Prior to Connections, we did not have an enterprise social network solution.

Like any major software implementation, the initial project required planning, resource allocation, vendor management, and communications.

Learn and understand the different product offerings and pricing models and note the difference between cloud, hybrid, and on-premises solutions.

We evaluated Jive and SharePoint.

Do your research and look for the solution that best fits your organization. Ultimately, enterprise social network adoption will be about culture and fit, and not the technology.

It is the single quickest way for us to start consolidating all of our files together when we are going to many countries.

Communication is a benefit. The challenge with it is whether or not it's a monetary benefit.

There's nothing pressing for us about Connections itself at the moment that we are desperate for that we don't already see in version 6. The biggest benefit for us will be nested folders. Until we get nested folder support, folders within folders, we can't move away from the historical file stores on Windows.

We have it on premise, so we control the stability. We have had issues with tuning and configuration. The best practice isn't always clear about how to configure it and make it work when it scales. We control the tin, but I'd say that probably there's a gap at the moment in best practice recommendations.

When we went from 1,000 users to 2,000 users, we hit some problems and then it required a lot of retuning and reconfiguration.

When you get to the right person in technical support, they are very good. The challenge is finding the people who understand it. There are probably about 50 people around the IBM world that can deal with the level of detail we sometimes go into but getting hold of them is quite challenging.

I was not involved in the initial setup.

The product itself is good, probably best in its class still, but the solution brings it down. They don't approach it as delivering a solution to a customer. They look at it as a product that then you work with. And they're making a big mistake there.

Get a good partner that understands how to implement it and don't expect that IBM can respond quickly enough. Make sure that if you buy the product and you use the product, that you've got a partner that can fully manage it for you. Don't expect there to be rapid releases. If there are gaps in functionality, be very clear that you probably won't get them within 18 months.

When selecting a vendor, trust is the most important criteria.

I use it mainly for my files. I've got pretty much all my personal files and shared files in there. I use it on a day-to-day basis - the Activities part - for managing my work and the work of our teams, the scrum teams and the agile teams. We are able to see where we are in the process for everything that we have to deploy. I also use it for finding people or connecting with people and communicating.

For me, the benefit is that I have it on my mobile device, because I work a lot on mobile. I've got a lot of different devices and I work in a lot of different locations and most of the times in meetings. For me, it's easy to always be able to reach my files. Everything is on hand all the time.

For once, I would like to see better support for files. I mean, file storage is very good. It's not a concept of traditional file storage, but I figure if you want to make a transition from a traditional way of working into a new way of working, the gap between the old way and the new way, should be a little bit smaller.

I think it's very stable.

Scalability is also very good.

Technical support is good.

We had a lot of solutions and what we wanted to do was not invent a new solution or bring a new one in. We wanted to combine the solutions we already had and integrate them into a real social enterprise collaboration platform. That's why we use Connections as kind of an umbrella over all the solutions.

Initial setup was complex. It is a large-scale WebSphere deployment, and we have a twin data center, so you have to do a lot to deploy it at a very big enterprise.

We looked at everybody in the enterprise social space. We looked at Microsoft, but Microsoft wasn't that big; Jive; we looked at pretty much everyone. We did a full analysis.

When selecting a vendor, the integration between current solutions and the new solutions is important, as is the integration between different vendors. Pricing is also important, of course. Also, the social features and the completeness.

Do a comparison of the different solutions, and really look into what your use cases are and how you want to use them. Especially, look a bit forward, for example, whether you want to be dependent on one vendor or to have multiple vendors and integrate them. I think Connections is a pretty good choice but it depends on where you're coming from and what your current installed base is.

The most important feature of IBM Connections is that it is a Social Collaboration suite covering nearly all aspects of modern enterprise communication and collaboration. As a comprehensive set of Enterprise 2.0 tools, Connections can serve many purposes in an enterprise and so be useful for many people inside. It is therefore superior to any single-purpose tools that sometimes might be better in specific functions, but are only useful for a small group. The reduction of information silos is one of the most important challenges enterprises are facing today and it can only succeed if everybody in the enterprise is using the same platform for open communication and collaboration.

The whole organization benefits from one of the most important key features of Connections: It provides context to everything either by organizing related information, data and files in communities or by simply adding tags to persons and all kinds of data. Context also means that conversations and discussions happen exactly where they belong and not somewhere else (e-mail, phone, ...).

The wiki is the weakest part of Connections, compared to standalone wiki solutions. It does not offer customizable templates for pages, a feature users often ask for. I would love to see improvements in this area.

I have used it since 2007.

I have not really encountered any deployment, stability or scalability issues. Stability and scalability are excellent due to the underlying platform, IBM WebSphere. Deployment on premises takes between 3-5 days and requires good, skilled and experienced technicians. Deployment in the IBM cloud is easy. Major upgrades on premises are sometimes challenging and should only be done by experienced technicians.

Technical support is good, but could be better, as always.

Previously, we mainly used email, which for collaboration purposes has a lot of disadvantages: It has no structure (personal email folders are not a collaboration tool), it is highly redundant, you neither know the status or the context of a message and finally, it is another silo. Sharing is way more efficient than distributing.

Initial setup is complex because you have to deal with installation and integration of several systems: WebSphere Application Server, HTTP server, relational database, LDAP, Tivoli Directory Integrator for syncing user data between LDAP and Connections, IBM Cognos for BI, e-mail integration.

We provide implementation of Connections as a service and did it ourselves.

Some IBM business partners offer very attractive prices if you combine Connections licenses with one of their add-on solutions.

IBM Connections is a software product but deploying Connections is not mainly an IT project. You should know WHY you are deploying it and which GOALS you want to achieve with it. Otherwise, it will fail even if the infrastructure is running perfectly.

IBM Connections is a great product, with new functionality each year. It can be integrated with other products easily and you can personalize this product to match with your organization.

For joint ventures, for example, it's easy to merge employees into the same entity group assignment, hierarchy and organization, with mixed rules and the right community and distinct special areas.

I actually work with profiles and identity, and also all the information around entities (not only geographic, but all properties assign to a employee).

My dream: Create a workflow to manage and simplify the lifecycle of a employee across the company...

My entity should be the same if I change companies; only some properties are different, but my links are the same (Twitter, Facebook, etc.).

I have used this solution for seven years, providing assistance and support, deploying social solutions or upgrading versions.

I am certified to deploy complex solutions.

I would rate customer service as follows:

• IBM 6
• JALIOS 6

I would rate technical support as follows:

• IBM 4
• JALIOS 6

We used to deploy Backbase Portal and IBM. I advised the selection of this solution.

It depends on the chosen architecture but initial setup can often be complex for a new user.

I implemented and deployed the solution. You need a good requirements evaluation for design and a good architecture.

Check IBM licensing.

• Search for a good partner who has installed a lot of solutions and multiple integrations with other products. This may not be easy and more skills may necessary.
• Most Connections functionality must be customized and personalized but it is more expensive to customize this product, and the product does necessarily provide the widespread coverage that a customer may seek.
• I developed a personal project to help integrate and interoperate where I can define like a ERP, and My ERP is based on a identity Management and access management much more.