Sunday, September 15, 2013

Email Clients Versus Collaboration Tools

In this constantly evolving world we find ourselves in -- from getting up-to-the-minute news in the blink of an eye on our mobile devices to encountering increasingly integrated software apps -- it can be quite overwhelming for the average small town business owner when making decisions about which apps to use to run his/her business.  What if you pick an app that steals your contacts or puts malware on your applications?  What if you purchase an app that you don't understand how to use and manage because you got sold by fancy marketing PR that was thrown at you when you clicked on the website?

So, let me try and simplify the decision-making process a couple notches down for an area that most businesses require to run effectively - Communication.  If you are a business owner, how do you want to exchange information with your Customers, Employees and Vendors?  Does your business typically rely on on-line interactions the majority of the time versus verbally or in person?  Well, if it does, stay on this page because I will be discussing some Linux-based Email clients versus Collaboration tools.

So, you've made a plan to switch over to a Linux desktop with LibreOffice, what next?  You need an Outlook replacement, right?  Answer:  It depends.  The reason why I say "it depends" is that technology has evolved to the point that Collaboration tools include email and other additional communication functionality.  Do you really need an email client if a Collaboration tool has email and more?  Do you really need email if your work processes rely more on updates or exchanges that can be better handled within a Collaboration tool?

Let me give you some examples:

Example #1:  Your firm is a bakery.  You order your own ingredients and make your own baked goods within your small shop.  If you buy most of your ingredients by going to Costco, Sam's Club or a local grocery store, do you really need email to run your business?

Example #2:  Your firm is an Engineering firm that designs semi conductor components for the telecommunications industry.  Your customers interact with your Designers and Engineers through meetings and reviewing drawings.  If most of your work processes revolve around updating the status of the design process for a component until final approval by the customer, do you really need email to run your business?

For the first example, you would probably think email was not really necessary since you do most of the tasks yourself, supplying inventory, baking and interacting with customers in person.  For the second example, you might be tempted to say you really need the email so that your designers can attach drawings to emails they send to customers to review.

What if I were to tell you that there are feature rich tools within the Linux ecosystem that could handle enterprise-wide transactions and processes in a collaborative manner?  These tools consist of the following on a single platform:

  • Information sharing and CRM

  • Project, task and event management

  • Online file server and document management

  • Data exchange and synchronization

  • Incident tracking

  • Website content management

  • Email integrated with calendar management

  • Chatting


The above is what is displayed on Egroupware's site.

Just think.  If most of your processes revolved around approving drawings with internal and external resources, why not handle those processes within a Collaboration tool such as Egroupware or Group-Office?  You save the drawing one time into the tool's repository database.  Any comments, calendar events, resources or other updates would be associated with that drawing generating a history of the transactions related to that drawing.  Why there's even version control, tracking the changes to the design as it is approved by all parties throughout the design life-cycle.

Now wouldn't that be a better approach than exchanging emails with attachments back and forth, where the attachments could clog up the memory of the email server, requiring frequent system administration to free up memory resources for storage?  With exchanging emails, it's very easy to lose or find the right email when you are sending it to someone who gets 300 emails a day.  However, with one of the Collaboration tools above, the history of revisions and approvals for each drawing is kept intact in one place where all resources, whether employee or customer, can look up information related to that same drawing as long as they all have a login account to the tool.

If you decide that your business really does need email, there are two Linux email clients that come to mind:  Thunderbird and Evolution.

I'll go into those two in more detail in a later post but for now, just giving you some food for thought.

 

If you would like a Consultant to evaluate your organization for a potential migration to LibreOffice or other Linux products, please fill out the form provided in the Contact Us page.

Saturday, September 14, 2013

Evaluating LibreOffice For Your Business

So you happened to click on this site or another Linux site and were intrigued about the new world that opened up to you when you heard of the benefits of a Linux operating system: modularity, security, versatility, etc.  Then you chanced upon some articles related to using LibreOffice, the much touted drop-in replacement for Microsoft Office.  You figured to yourself, "Maybe I could garner operating expense cost-savings in the long run if I decide to replace all my Windows desktops loaded with MS Office with Ubuntu desktops pre-installed with LibreOffice..."

Here are things to consider before you make the migration:

1.  Interoperability - How important is the integration of documents or files within LibreOffice to other applications your business relies on?  Does your SAP, Oracle or other ERP system allow you to export data to LibreOffice Calc or Base?

2.  Collaboration - To what degree does your business share document or files internally and externally?  Is this critical to the execution of your business processes?  For example, do you share large documents which are heavily formatted with version tracking with customers, vendors or employees?  If so, can it be handled with LibreOffice Writer?

3.  Compatibility -  Think of all the file formats your business uses and whether LibreOffice can handle them.  For example, LibreOffice Calc was able to read an Excel Chart and data with an .XLS file but unable to read the Chart with an .XLSX file in my video below:

If this is the case, think of how you want to handle this situation.  Do you want to give users access to both LibreOffice and MS Office to account for situations like this?

4.  Process Execution - Can I execute this particular process and all its associated set of tasks using LibreOffice?  For example, can you take all your processes which rely on Microsoft Access/Excel VBA code and macros and recreate them in LibreOffice Base/Calc Basic and Python code?

5.  Support Resources - If you are considering migrating over to LibreOffice, do you have an experienced resource you can rely on when you run into issues using the new software?  For commercial support, LibreOffice provides a list of certified partners.

6.  Differentiation - What does Office have that LibreOffice doesn't have?  How often are those features or functionality being used by your users?  For example, if you are a small Design firm and your staff primarily use office to send Powerpoint presentations with associated Artwork to clients, it is probably overkill to have each member have a licensed copy of Office.  If the presentations can be viewed in Impress and occasionally there is a Word document with formatting that does not translate to Writer, then you only need one copy of Office stored on a Windows laptop or server for the staff to use when they need to view Office documents or files.

Here are things to do to make the migration successful:

1.  Create a detailed LibreOffice Migration plan.

2.  Encourage your employees to start using LibreOffice at home in preparation for the actual migration.  To download a free copy of LibreOffice, click here.

3.  Decide whether you want to standardize on LibreOffice or operate with a mixed environment.

4.  Create the business case for the LibreOffice migration and determine if there is a return on investment (ROI).

5.  Start a pilot project with departments where the migration change is going to be the least disruptive to evaluate the usefulness of the product and how it integrates with the department's normal workflow.

6.  Evaluate the pilot project after the evaluation period is over:  30 days, 3 months, etc.

7.  Conduct meetings with staff members from the departments which evaluated LibreOffice to determine whether there were any gaps in business processes that LibreOffice did not meet and whether they could be adequately addressed by using a substitute process or technology.

8.  Determine any additional benefits gained from using LibreOffice over MS Office.

9.  Compile the pros, cons, migration costs and operational savings gained to complete your business case.

10.  Make the decision to migrate based on the results of your pilot project and business case in Step 9.  Do the benefits and operational cost savings that will be gained from the migration outweigh the cons and migration costs?

11.  If you decide to migrate, ensure that you have appropriate Support resources and a plan to handle legacy documents created with Windows formats.  Perhaps, you want to keep an old Windows 7 laptop loaded with Office 2010 with each department or put a few licensed copies of Windows 7 loaded with Office 2010 on a citrix server that any employee can access via thin client.

There are numerous benefits to using LibreOffice:  no license costs, cross-platform compatibility (Linux, Windows, MAC) and a near drop-in replacement for MS Office.  However, before you take the plunge, you must evaluate whether LibreOffice can fill most of your office critical needs.  If you find that LibreOffice will fulfill most of your critical business needs, you must prepare your organization adequately to ensure that the LibreOffice migration will be successful.

If you would like a Consultant to evaluate your organization for a potential migration to LibreOffice or other Linux products, please fill out the form provided in the Contact Us page.

New Category Featuring Articles on Using Linux in Business

Dear Readers,

This site was primarily created to bring more public awareness to using Linux on the desktop as a viable alternative to Windows, MAC and other desktop operating systems.  Most of the articles up to this point have been geared toward personal and home use.  As Linux gains more acceptance in corporate enterprises the world over in the server, mobile and desktop arenas, I feel the time is ripe to introduce a new section on this site which features articles from the perspective of a business owner, whether large or small.  My own background encompasses working in Fortune 500 companies and small to mid-sized businesses in both technical and business roles.  Therefore, the articles here will serve as guides to aid business owners when making technology decisions about whether to add Linux products to their enterprise.

 

Sincerely,

Editor