Connections from HCL Technologies (formerly from IBM, acquired by HCL in 2018) is a collaboration tool and employee digital workspace with key features like social analytics, blogs, document management, and a social network.
N/A
Webex App
Score 8.1 out of 10
N/A
The Webex App brings together Webex Calling, Meetings, and Messaging into a single application, fostering collaboration and unlocking more productive ways to work.
IBM Connections is well suited for larger organizations that need an internal social networking tool and are willing to deal with IBM and the complexity of the software. It is less appropriate for smaller organizations and those who don't want to deal with the complexity, or IBM's awful customer service and prices.
The biggest use case I have for Webex is the public and private Spaces feature. It is so handy to have a single place where I can collaborate with team members on a single project. We can chat about new ideas and share files just on that specific project. That way I am not having to search email, or a Sharepoint site or a network drives for files. And I don't have to search through a separate chat log for ideas for this project. Add to that that I can use the Webex app on my PC, Mac, iphone and Android tablet and that makes it the killer app.
The plugin for MS Office/Explorer has made saving and sharing working documents extremely convenient for me and my close colleagues
The newsfeed feature conveniently aggregates updates from the communities/people you follow. It's nice not to have to jump from community to community to see what's going on in the organization
The various apps can be used for several purposes. A little creativity goes a long way when establishing what type of information the apps can be useful for communicating
The lack of a note-taking tool became a bigger and bigger issue as time went on. Our pilot users felt Connections was a natural place to take and share meeting notes – including photos, drawings, recorded audio, etc. – and were always frustrated that there was no easy, organized way to do that. We tried using a Blog, Wiki, etc. but nothing really resonated as a good solution for this.
The Wiki tool is weak, providing rigid structure but with few options. A Community can only have a single Wiki, for instance. Wikis are weak in the mobile app as well; they’re not even easy to navigate. Users ended up ignoring Wikis completely despite our efforts to get them to convert documents like guidelines, policies, procedures, handbooks, etc. into Wiki form.
The Windows Explorer plug-in was useful but required a lot of manual intervention to setup. For instance, once a user joins a Community in Connections, the Community also has to be manually added to the Explorer plug-in so the user can find, open and edit files with it. We felt this process should be much more automated.
Tagging is only relevant in the web UI and, to a lesser extent, in the mobile app. However, in the Windows Explorer plug-in, Tags are not usable at all making it difficult to find things that were easy to find in the web UI.
IBM Docs was not included in the on-premises deployment; it was an additional license so we did not test it. Documents, mainly Microsoft Office files, are still the single most common way our user community creates, shares, edits and presents information. That proved to be a major gap for our users, and slowed user adoption considerably. We considered testing it, but IBM Docs would only work for about half of our users so we found ourselves wondering if we really wanted to support two document editing platforms. IBM Docs also offers no way to work offline as far as we could tell. This also meant we would need to keep licensing Microsoft Office which is not cheap.
Consulting costs are high because the back-end environment is complex. Installing, administrating and even patching Connections is a fairly complex process. We needed to hire consultants to install our test environment and any major upgrades would’ve required additional consulting fees. Any 3rd party add-ons we looked at were highly technical in nature meaning…you guessed it, more consulting costs.
Administrating IBM Connections requires editing XML files in a specific, secure way that is typically done in a console. I love consoles as much as the next admin, but when you only use a console once every 2 months it means looking up all the documentation and re-educating yourself. A single change could take me 2 hours to implement. 3rd party admin dashboards do exist, at an additional cost, but IBM really should provide a much easier way to manage the environment.
The lack of in-person or online training courses, materials, videos, etc. really discouraged a lot of users. The only decent training we could find (marketing videos aside) was a single video series on Lynda.com which, of course, was an additional cost. In the end that video didn’t really help our users much beyond introductory concepts.
IBM includes reporting, but it’s a massive Cognos system requiring some serious hardware and Cognos expertise. We had neither, and would have ultimately opted for a 3rd party add-on for reporting and statistics.
An often overlooked concern is eDiscovery. Our contracted eDiscovery service extensively works with various ECMs, but had no idea how they would handle Connections data. The cloud version of Connections offers an add-on for eDiscovery, but as far as we could tell IBM offered nothing for on-premises deployments.
Connections has continued to more than meet our needs from a collaboration point of view and we are currently working on integration with our IBM Websphere portal platform to provide an integrated collaboration solution. This scenario will provide our users the best both products have to offer in a single interface.
I don’t have access to video features.) In an age when our smartphones do everything but call our friends, family, or clients, it’s refreshing to have a desktop app that can make calls in the smartphone’s place. It seems appropriate in a time when we’re all worried about the robots rising and taking over the world. Why not transfer the functionality of a telephone to the same computer where we program those world-dominating robots? It’s practical. Cisco Jabber takes the classic idea of making calls with a phone and puts it in the same place where we spend most of our worktime. This frees up desk space, as well as keeps the smartphone available for what it was invented to do: take Instagram photos. Not to mention, because it has its own number, it makes it easier to contact clients without having to give them your personal phone number. Need to make a call, but you don’t want to share your home phone? Cisco Jabber makes that easy. And best of all, because you call through your computer, all you need is a microphone to speak and speakers to listen, and you never have to pick up the phone at all. If you hate having sweaty ears, then Cisco Jabber is your app of choice. Note: Because I have access to phone features only, and Cisco Jabber has more available that I can’t use, I can see where it may also be a pro for business owners that Cisco apparently allows custom features availability for users, depending on roles.
Connections combines all the most useful abilities from various social networks. This makes it useful of course, but it also reduces user adoption time initially by allowing users to get comfortable with basic features. Once they are comfortable, it's easy for users to start exploring. They find new people in the organization to contact, new sources of information, etc. Before you know it, about half of the users are contributing back in some form -- and all with little or no training needed by IT.
Webex is quite usable, and it is, in fact very easy to use as well. You don't need a lot of documentation to learn how to use the app as it's mostly self-explanatory. The user interface is easy on the eyes, and people can see buttons without issues. Overall, WebEx's front-end design is great and I don't have much issue with it.
Once Connections was installed, patched, etc. it was ALWAYS up. We only had to bring it down for OS updates to the servers. That seems to be typical of anything that runs on WebSphere; it's bulletproof and could probably run for months and years if the underlying OS didn't require constant patching.
I would say every time I open it, it is there, there are times that our users have to sign out and back in to get it to work or even do a full exit as the app will disconnect from the controlling the desk phone, but some easy steps to sign-out or fully exit the app gets the user back up and running quickly.
IBM Connections web UI, mobile app (data sync to / from the device), and file transfer speeds were almost always very fast. It was rare for a slow-down of any kind, even when doing searches.
Software loads and runs well. I like the ability to run the full app version, or, just run through a browser using a lightweight webex experience. In a pinch, this ability has saved my bacon when I had to connect in an emergency on a borrowed phone or computer
IBM Support has ALWAYS been quick to respond, regardless of the product. Even first level techs seldom provide "canned" responses and they really try to help. If they can't help, they don't wallow around but engage the right person immediately. It's very rare that the first level tech needs to escalate, and even more rare when they do escalate and the next person engaged cannot solve it. We have been more than satisfied with IBM support's quick and professional responses to our issues.
The support team is quick in reverting to the issues faced, and it has multiple language support, which would be very helpful for some instances. Their expertise in resolving queries is instantaneous. Most of the common lags/issues in the application are identified and fixed with regular updates.
I am very satisfied with my experience with Webex App in online training. The creation of the event is very easy with the possibility of scheduling it in advance. The management of participants, organizers, and animators is complete. The invitations are automated and by simply using emails we can create all the schedules of the training session
Very easy to create. All operations are done without any problems with our business growth. All people like the experience including me as an instructor. The tools that WebEx App offers us are very complete for working in a virtual classroom, whether it is sharing the screen, the different display modes, the whiteboard, or even the scoring tools on the screen, it allows me to do my job as an instructor as if I was face to face with the participants.
Try to understand you will never find a product which suites all your end user for 100%. IBM Connections is the best of all breeds but if you go look on each functionality on its own there are better example out there. But as IBM COnnections delivers it all in just one platform makes it the best example about integration of different functionality into one platform.
There was quite a bit of back and forth with TAC and Cisco Reps to get it fully up and running but we did get there. Some of which had to do with documentation was not fully understandable. But with Cisco TAC we were able to get fully up and running.
From the few times that I have used MS SharePoint, I can say that it doesn't seem to hold a candle to the robust features of IBM Connections. The out-of-the-box capabilities of IBM Connections are amazing and are more easy to access and use than what I've seen with MS SharePoint.
A lot of drops from calls/meetings frustrated me and my customers in some cases, but with Webex App, I see very less (or even null) drops, even when I am streaming HD content through my camera, even when I connected with the support team for other products for an explanation, they blame it on ISP even though my ISP gives around 200 Mbps speed, Webex App is miraculously never "affected" by ISP speed.
Scaling UP is never an issue with IBM's core technologies like WebSphere, DB2, etc. as long as you have or can find the technical resources to implement it. Where IBM seems to fail is scaling DOWN for smaller organizations. Connections 5.0 on-premises would have required us to create 7 servers -- yes, they would be virtualized, but still that's 7 OS licenses, 40 virtual CPU cores, 80GB RAM, and a few TB of hard disk space. All to replace Quick which runs on 1 server with 1 OS license, 4 cores, 8GB RAM and 600GB of disk. Granted, there are major differences in capabilities between the two, but how do you get a CFO understand why features like a mobile app, file sync, and social sharing require 10x the back-end resources?
Once everything is in place on the back end getting Webex on a user's PC is now very easy and with single sign-on, users are able to sign in without having to remember another password. Just make sure you have all the user settings in CUCM, CUC set right, and that they have the needed licenses in Webex Control Hub.
Cisco Jabber helped us develop a Business Continuity Plan in case of emergencies.
It allowed our employees to answer their office-phones remotely.
It saved us a 10.000$ investment every 4 years on the desk phones for only the Turkey office, possibly much higher figures on the global scale of Hilti.
