For our fourth consecutive year at this IBM social business conference, AppFusions is pleased to be digging in deeper as a Silver Sponsor, further cementing our belief in connected systems and reduced silos given the social business/collaboration movement sweeping enterprises across the world.
9 of us from the AppFusions team will be attending the IBM ConnectED 2015 conference in Orlando, on January 25th-28th. We can’t wait to share our new and updated product releases with customers and IBMers alike.
This integration allows you to post your WordPress blogs directly to your IBM Connections community. Further, activity streams are logged, and IBM Connections business cards are displayed for the WordPress authors.
Immersive for Atlassian JIRA, in IBM Connections V5•Extended!
Immersive for Atlassian Confluence, in IBM Connections V5 • Extended!
Immersive for Atlassian Stash, in IBM Connections V5 • New!
Immersive for Atlassian Bamboo, in IBM Connections V5 • New!
These integrations bring your Atlassian systems into IBM Connections. All from within IBM Connections, you have powerful advanced search capabilities into all the different Atlassian applications, native IBM business cards in Atlassian applications, you can create a JIRA issue directly or share it, access and interact with Atlassian applications’ live activity streams, and more. AppFusions have been developing these integrations since 2013.
Atlassian Integrations with IBM Sametime
IBM Sametime V9 in Atlassian JIRA • Updated!
IBM Sametime V9 in Atlassian Confluence • Updated!
IBM Sametime V9 in Atlassian Stash • Updated!
IBM Sametime V9 in Atlassian Bamboo • Updated!
IBM Sametime V9 in Atlassian FishEye • Updated!
These integrations allow you to run rich IBM Sametime chat sessions, with context, from inside your Atlassian systems. These integrations have been supported since 2012.
AppFusions will have two demo pods, so we hope you will stop by to check these out and/or to discuss with us your use cases or other possibilities for IBM Connections integrations.
Note: All AppFusions’ integrations are for sale as packaged supported solutions. As you grow and evolve, as well as your systems, so also do your AppFusions’ integrations. We’re right there with you on your integrated social business/collaboration journey.
AppFusions senior integrations experts build supported use-case driven integrations between some of the most popular collaboration tools in the industry. Our integrations are not just web-links. AppFusions’ solutions bridge systems with enhanced user experiences so you can work faster and better.
With over 50 packaged integrations, and counting, AppFusions solutions quickly solve common yet tough pain point integration challenges by bridging together Atlassian Software, IBM Connections and Sametime, Jive software, Dropbox, Box, Google Drive, Egnyte, Alfresco, Microsoft OneDrive, Yammer and Parature, Lingotek (translations), single sign-on solutions (SAML2, Kerberos, OAuth2), UserVoice, and more.
IDC concludes that the “increasing sophistication of use cases demonstrates that the market for enterprise social software is maturing quickly. Organizations are looking to engage internal users and customers in an ongoing conversation, inside and outside the firewall. As usage increases in breadth and depth, activity streams, discussion forums, blogs, and wikis are becoming assumed functionality of enterprise social software to facilitate collaboration in real time and in context.” I would certainly agree with this assessment.
Application integration is increasingly becoming a success factor. IDC notes that “Customers are demanding broader and more specific collaboration scenarios that tie together internal and external constituents, deliver sophisticated insight into user behavior on the network, and extend seamlessly across mobile form factors.” These seamless extensions and the connection of internal and external constituents requires comprehensive integration that is designed to address business objectives.
Their key success criteria include: the ability to extend activity streams, blogs, and wikis to a broad range of stakeholders. The optimization of the mobile experience, comprehensive analytics that can “perform behavioral and predictive analysis on data generated by the network,” a scalable platform that can extend to customers, and partners, as well as handle different roles, company sizes and industries, and “prepackaged integrations with collaboration tools and major enterprise application vendors delivered via the cloud.”
IDC notes that such social tools as activity streams and blogs are becoming required functionality within the enterprise. As social tools mature beyond initial marketing applications, use cases have grown into such areas as customer experience, sales enablement, digital commerce, socialytics, innovation management, and enterprise social networks.
The latter use case provides a means to find relevant information and people through connecting people, data, and systems in an overarching system. Collaborative workspaces are the outcome and the foundation for the connected enterprise.
Enterprise adoption of the new enterprise social software is on the rise. There has been as 40% year-over-year market growth. In this current survey 67% of organizations have implemented a corporate-sponsored enterprise social software solutions. While there are standalone solutions, many vendors have moved to more open and connected offerings through the use of APIs. This allows social software to be embedded within work processes, a topic I have covered before (for example, see Putting Social Media to Work and Giving Social Media a Good Job)
IDC concludes that “enterprise social software will eventually become the backbone of the ESN for a number of reasons.” This is being fueled by the recognition that connecting employees, customers, and partners is key to success. As McKinsey found, “higher operating margins (again, self-reported) than competitors correlated with a different set of factors: the ability to make decisions lower in the corporate hierarchy and a willingness to allow the formation of working teams comprising both in-house employees and individuals outside the organization.” Collaborative technologies create more agile organizations and these companies achieve higher profits.
In 2012 IDC expects to see enterprise applications and other collaborative applications being upgraded to include social functionality or becoming integrated with enterprise social software solutions in a complementary fashion.
It is an exciting time and we are pleased to be part of it thorough application integrations.
As Chief Community Officer, Jeff leads the Alfresco community. This includes partners, employees, developers, customers, and anyone else with an interest in Alfresco. Indeed this is a large order, with over 200K downloads, and growing, of their content management server software to date – so that’s a large community.
Jeff focuses on the health of the community and makes sure it has the right tools, tutorials, forums, blog aggregation, wikis, and whatever else is useful to support collaboration and continue its growth. He also conducts outreach to other relevant communities to expand its awareness and participation.
The Alfresco open source offering is built on a repository for files of all types: documents, audio, video, images, and other types. Expanded access is made possible through its API using CMIS, an industry standard that is also used by other tools such as SharePoint and Documentum. CMIS uses “Web services and Web 2.0 interfaces to enable information sharing across content management repositories from different vendors.”
There are several applications that Alfresco has added on top of their repository. Share is a main one and it allows for users to share documents, calendars, links to support collaboration. In addition to collaboration and content management, use cases for Alfresco include records management and digital asset management.
Alfresco provides an on-premise Enterprise version of their software that is offered with support subscriptions. There is also a free community version available through the LGPLv3 open source license. This year they have added a multi-tenant SaaS offering. This relieves clients of any hosting responsibilities so they can focus on organizing and using their content, not supporting the backend. Both the on-premise and SaaS version (cloud) have the same software and user interface.
With the cloud version, users can share content within the same domain since it is a multi-tenant offering. The cloud version also has a few less features at the moment, as basic document management is the primary use case. So the calendar, blogs, and wikis are not enabled at the moment. There are plans to make them also available in the cloud version in the future.
Next we discussed the Alfresco’s integration strategy.
Alfresco’s goal is to make Alfresco as open and available as possible. They want any interested developer to be able to work in the tools they are comfortable with to connect to the repository and create integrations. To enable this availability they have built APIs for both the on-premise and cloud versions. While CMIS covers such functions as create, read, update, delete, Alfresco wanted a richer experience, so they added additional features to the API specific to Alfresco such as rating and comments.
The Confluence integration allows users to embed and access Alfresco file lists. Users can also preview, embed, print, download Alfresco files from Confluence.
Finally, when you edit an Alfresco document in Confluence, you are able to edit it in your favorite local Office application (MS Office, Apache Open Office, NeoOffice), and when done – the file is auto-magically saved back to Alfresco. Here’s a video.
Collectively, these integrations really bring powerful platforms and brands, together. Best of worlds!
Alfresco has also recently released support for iOS and Andriod to enable developers to build mobile app integrations. They are also expanding CMIS client-side libraries to better work with what Alfresco offers.
Alfresco has its third annual user conference, DevCon, coming up in November. This year the European version will be in Berlin, November 6 and 7. The US version will be in San Jose November 14-15.
The conferences will include technical workshops by Alfresco engineers and partners, case examples by users, and keynotes by the Alfresco leadership team. Both conferences will be preceded by a day of workshops for those new to Alfresco so they can more thoroughly engage with the event.
Jeff sees the use of the cloud continuing to expand and I would certainly agree. Alfresco will continue to offer more capabilities through the cloud. As CMIS becomes more widely used, they will make more CMIS-related tools available.
Alfresco is certainly moving in the right direction, hitting three of the main themes in the application marketplace with its expanding capabilities in social, mobile, and the cloud.
Before we describe the place of AppFusions in the new world of Enterprise 2.0, it is useful to go back to look at the Enterprise 1.0 world which is still current for many.
Enterprise 1.0 – “A Single System For All”
In the Enterprise 1.0 world, large ERP systems claiming to be a “single system for all” integrated many (if not all) departments and functions across a company into a single computer system. They attempted to serve all the different department needs, running the business, successfully in some places, and not so successfully in others. These systems bridged the needs of products, customers, employees, and suppliers. (Below image from this excellent slideshare by Samuel Driessen.)
For many years, this cross-functional single-uber-system was thought to be the ultimate glue to solve all problems: the silver bullet solution to propel corporations fast forward in their business success.
However, despite best intentions, these lofty goals were hard ones to meet in a single system, given many mixed audiences and purposes between departments.
Cross-functionally, departments wanted to control (customize) their workflow.
While ERP systems were configurable out of the box – to a point – in most cases, they required costly customization SLAs to develop or configure the workflow exactly how a department wanted it.
Data integrations to other systems were extremely expensive ($50K – $200K+), given the reliance on niche technical knowledge in closed systems.
All integrations were like “black magic”, requiring ongoing support and vendor reliance without a natural support path.
Integrations where time-consuming and costs could be as much five times the software fees.
Over time, specialty purpose-driven or “rogue” systems crept into organizations (large or small), as department heads rebelled against the rigid IT uber-system, and shopped for their own systems to meet their department needs.
For the companies that succeeded in their ERP deployments, they paid dearly in implementation costs, yet also they got bigger and faster with these large system infrastructures. For a while, they enjoyed a competitive edge in their locked-down systems.
no, you cannot change the process or system (without an enormous amount of additional churn, cost, pain – to which we have no more money to expend).
Employees were forced to adopt the new inflexible systems, a change that often felt like steps back even from their slower, yet functional desktop processes.
Compounded with normal human resistance to change, the new systems were not always warmly received. People had to conform to rigid systems, rather than having flexible systems built around how people worked best.
The enormous level of cross-functional process coordination upfront, as well as the long term support for these systems, was often more crippling than helping. The systems had the potential to control corporate data in a better/faster way than previous manual ways, but it held employees hostage in so many other ways, and caused new problems organizationally.
Politics and internal fights evolved to ever high levels as employees felt duped when the new systems didn’t really do everything that they thought it would, and no customizations were allowed. If a department absolutely required customizations, they’d have to take the heavy cost hit in their departmental budget (not ITs), let alone the time-hit to implement (e.g., another 6 months often, assuming it got done before some other organizational crisis hit).
Companies would endure the growth of excessive politics, mistrust, and infighting causing systematic morale issues and lower productivity. Employee dissatisfaction grew at a higher than normal rate, as well as distrust for management who forced the new monster system on them in the first place (even if it was justified at the time given where technology was at).
In short – it was a vicious and often ugly cycle, especially for large corporations enduring these growing pains.
Outside the Enterprise 1.0 World, the Beginnings of Enterprise 2.0 Technology Moved Forward
Meanwhile, the open source movement had gained “officialness” in 1998 thanks to Netscape (Mozilla), and during the 2000s, the open source trend and collaborative engineering mindset grew more popular with the growth of Linux, further proving the value of both iterative agile engineering, open APIs, rapid development methodologies, and at the communications level – transparent collaboration.
Concurrently, the Internet was taking off well beyond the Silicon Valley, thanks to Yahoo! (1995), Google (1998) going big/global (as well as Microsoft with Internet Explorer). For the Enterprise, early pioneers Jive Software, SocialText, and Atlassian Software were founded in 2001 and 2002, respectively – three corps that would become pioneers in the Enterprise collaboration tools space in the years to come.
Atlassian also would become a leader in many of the open source stirred trends, namely agile development, ALM, engineering tools, and issue tracking, while boldly treading on common industries lead by big heavyweights like IBM, HP, and Microsoft, among others.
Overall – the timing of these new Enterprise collaboration businesses couldn’t have been better, overlapping with early social sites like MySpace (2003), Delicious (2003), Facebook (2004), Digg (2005), Twitter (2006), FriendFeed (2007), and a strong new-way-to-business Millenials culture pushing into industry with all their might.
By late 2009, open collaboration and social networking was no longer an idle idea.
It was a fast moving trend and way of the future, that had proven the beginnings of enormous business value for getting things done faster in the Enterprise. Concrete data began to emerge on the quantified value of these new approaches (see The Business Value of Application Connectors).
However, to be successful in the new world, people-centered Enterprise 2.0 apps need to connect with the old world transactional-centered Enterprise 1.0 systems. They needed to connect to each other to avoid establishing even more silos within organizations.
While AppFusions does not really believe in the legacy gigantic one-size-fits-all system ideal, at the same time we know that in most cases, these systems are largely not going away.
The new social systems of engagement still need to connect to the old world transaction systems to get work done.
AppFusions Bridges the Gap with Enterprise 2.0 Content Management Integration Connectors
We believe that business information and process management should be handled by a collection of systems that make up a whole. To make this happen, connectivity is the key driver. It is the glue that makes real work happen. It brings the benefits of social systems to work processes.
Modular system architectures in the Enterprise – from the same vendor or many vendors – provide greater flexibility, while also allowing organizations to pick and choose the best-of-breed systems for their purposes.
There are reasons for purpose-built systems, and a collection of many we feel is stronger than a single rigid system, especially if you can connect the strengths (data and workflows) of the different systems with common use case connectors vs. getting on an endless customization path.
Our integration connectors (current and future) bring together workflows, data files, and information between Enterprise systems for your collective purpose-built Enterprise 2.0 corporate solution of many systems. They allow companies to quickly and cost-effectuvely create the needed connectivity without going through the old-world pain of massive, costly, and time consuming integration efforts.
These connectors provide the means to close the gap between old and new, enabling the promise and opportunity within the capabilities of the new people-centered, social systems.
This blog will become the vehicle to tell this story and provide use cases demonstrating the essential nature of connectors.