Ask Pipedot: small office collaboration/messaging

by
in ask on (#2V33)
Here's the situation: you've got a small office of 8-20 employees who work in a consulting business and whose main products/deliverables are reports, spreadsheets, occasional CAD drawings, Gantt charts, project plans, and the like. Not only do they produce those things, they receive reports for which they produce comments/observations. Much of what they produce is collaborative or iterative (ie, not necessarily 'live editing' of spreadsheets, but several people must all contribute to a doc over the space of a week or so). To do so, they need efficient means of communication, discussion, versioning, etc.

Needs: document repository, shared editing of many types of documents, a messaging system for internal office communication, "sharing" system that permits clients to upload or download large files, a managed-content "front page" web site, an internal intranet, shared calendars, contacts lists, some sort of system to produce and maintain office policies and procedures, and otherwise manage internal communications and office admin. Some considerations for discussion, so I'm intentionally not specifying: (1) ideally, systems are usable by different OSes. Obviously there are going to be problems ensuring total OS independence. (2) ideally, the system doesn't require full-time online presence. Should a consultant wind up in a basement office with no internet, he won't be totally lost (again, not perfect). Note: no obligation for Free/Open Source software, although they are preferred. The goal here is an office that communicates and collaborates efficiently.

Ten years ago, you'd be sitting in a cube farm, using Microsoft Office and a shared drive and emailing documents back and forth. Later they'd have added Sharepoint. These days, there's been a ton of innovation in these areas, and there's consensus that collaboration-by-email is not fun. And there are lots of new approaches to these age-old problems.

So, how would you do it?

Engage A Consultant (Score: 1, Informative)

by Anonymous Coward on 2014-11-17 15:46 (#2V3A)

These days, there's been a ton of innovation in these areas, and there's consensus that collaboration-by-email is not fun. And there are lots of new approaches to these age-old problems.

So, how would you do it?
I'd hire a consultant.

OK, seriously, what you are describing is nowadays referred to as a CMS - which can variously refer to call, contact, customer, configuration or content management system.

Some of the Wikipedia articles I'm about to cite identify some of the attributes that people care about, such as the ability to interact with the system via an electronic mail interface, or a web interface, or support for a specific operating system, or adherence to a specific license.

http://en.wikipedia.org/wiki/Call_management
http://en.wikipedia.org/wiki/Contact_management_system
http://en.wikipedia.org/wiki/Software_configuration_management
http://en.wikipedia.org/wiki/Content_management_system
http://en.wikipedia.org/wiki/Comparison_of_CRM_systems
http://en.wikipedia.org/wiki/Comparison_of_open_source_configuration_management_software
http://en.wikipedia.org/wiki/Comparison_of_revision_control_software

Each of those attributes translates into a choice of different software packages, which it is worth your while to negotiate if only to keep the results manageable, so that, after the dust settles down, you don't have three or four different, contending open source RDBMS installed.

And so we return to the original advice: engage a consultant.

My personal favorite is RedMine, but the last time I chedked they didn't support FreeBSD too well, and there was that horrible dependency upon Ruby.

Many people like Trac, but the last time I looked, it didn't have security.
Post Comment
Subject
Comment
Captcha
The list thumb, shirt and penguin contains how many body parts?