Sharepoint information and a possible roadmap

by oneafrikan on September 8, 2005

I recently worked with my colleagues to put together a document for a (property sector) client explaining what MS Sharepoint is all about, and what it could be used for… If you’re interested in Sharepoint from a high level business perspective, then this might be something interesting for you.

What does Sharepoint do?

  1. Provides a platform for document management, information collaboration, and information access out of the box.
  2. Sharepoint functions well as both an intranet and an extranet, where it is possible to give external people access to shared data for particular projects. For example, the Single Sign-on that Sharepoint offers enables people to access the portal from anywhere using a web browser, enabling them to access everything that is relevant to them.
  3. Provides a platform for creating individual and “team sites” that could be project, business function, or property focused. For example, an individual in the property management team could customize their own “site” where information, tasks, events and data relevant to them is shown and made available. They would also be able to interact with others through specific “team sites” which they would be a member of. A property management “team site” may contain documents, meeting dates in a calendar, lists of contacts, discussion about issues and financial data for the property(s) in question.
  4. Enables integration with other applications and databases. Information is then displayed on the portal available to relevant (security restricted) personnel. You could for example integrate financial data, lease data, property data and employee data in a single “dashboard” screen.
  5. Specific default Sharepoint functionality includes calendars, tasks, lists, discussions, document sharing, email, content and data from a variety of plugins.

How could a business use Sharepoint?
As a portal solution, Sharepoint does literally “out of the box” what a lot of other portals do with a lot of consultation, development, customization and time. Sharepoint allows an organization to share information and collaborate at the individual, team or enterprise level, allowing people within the organization to collaborate by creating and delivering news, relevant content and events; the sharing of documents and images; creating and delegating tasks; sharing contacts; creating discussions on specific topics; and conducting surveys; but perhaps most importantly giving individuals access to all of this without the need for complex VPN setup and administration.

It also gives the enterprise the option to create a central place (as a part of the intranet or portal) to access data from different systems. For example, it is possible to integrate MRI data into an “MRI dashboard” that is accessed from within the Sharepoint portal. In this way, non-technical or accounting personnel can gain access to data relevant to them when they want it. Another easy win would be to integrate consolidated real time leasing or construction data from other back-end systems or even e-mails into a “Leasing” or “Construction” dashboard.

Strengths

  1. Is relatively easy to install and set up – a basic installation should take 2-5days.
  2. Integrates seamlessly and easily with a Windows and Active Directory network.
  3. Users can access data internally as well as externally, on secure connections which protect privacy.
  4. Access permissions are granular, so it is possible to grant / deny individuals access to particular data at the individual, team or enterprise level.
  5. Eliminates the need for user access to data through complex VPN / Firewall solutions on fileservers that have no document management capability.

Weaknesses

  1. Requires a user paradigm shift from the networked file server solution to an intranet solution.
  2. Would suggest that current files that need to be shared are added to the portal. This has a time and cost associated with it. A phased approach would probably work best here.

A recommended Phased Approach:
Phase 1, Stream 1 – Installation

  1. Ensure MS Active Directory is on a domain on the organization network.
  2. Install Sharepoint Services using:
    1. A single Windows 2003 web server
    2. And a single MS SQL database server to store the data.
  3. Time estimate: 2-5 days
  4. Costs:
    1. Implementation cost, factor of rate per day and time
    2. Windows 2003 license
    3. SQL server license
    4. Hardware cost – 2 mid to high end servers with on-site support agreements
  5. Customization: none

Phase 1, Stream 2 – User Introduction to Sharepoint

  1. The intention is to introduce Sharepoint and the benefits of using it to users across the organization:
  2. Give users an idea of what Sharepoint is capable of with a default installation, through an introductory “show and tell” workshop.
  3. Conduct another workshop after the users have had sufficient time to interact with Sharepoint (suggest 1-2 weeks), as a detailed “Q&A” session, intended for users to ask questions and get answers demonstrated interactively.

Phase 2, Stream 1 – User requirements
The intention is to understand from individual users what they require for the Sharepoint portal to be a long term success, using the following process:

  1. After further use of Sharepoint, seek to understand what users feel the portal should enable them to do by conducting a brief survey, asking users across the organization for their input and comments.
  2. Summarize the results of the survey to determine what is most important to implement first.
  3. Present the results of the survey in a format which suits the organization best.

Phase 2, Stream 2 – Data migration

  1. Assign individuals within teams, projects and business functions to allocate time to update and upload relevant data into “team sites”. Suggest allocating at least an hour per day until all data is migrated.

Phase 3 – Customisation
Make changes to the functionality and features of Sharepoint as per the results of the survey, implementing in order of need and priority. Suggested customizations could be:

  1. Remove features which are either not needed or are redundant.
  2. Customize the look and feel to match the corporate brand and identity.

There will no doubt be further phases, which may include the following:

Phase 4 – Integration with other systems
Integrate data from other systems into Sharepoint, using either web parts or custom development. For example, you could:

  1. Integrate MS Outlook data into Sharepoint for remote access
  2. Create pages that show employee HR information
  3. Create pages that show accounting data for accounting or non-accounting users
  4. Create pages that show property data for property projects
  5. Create pages that show real time sales / revenue information
  6. Create accumulation of above for senior management view of all operations.

Phase 5 – Install Sharepoint Portal server
Once there are more than a few “team sites” and the amount of data Sharepoint manages increases, it becomes difficult for everyone in the organization to know where everything is. A unified search feature which Sharepoint Portal Server offers enables users to search all Sharepoint data and information from one place (assuming that they have the security rights to view the information). We do not think that this would add much value for businesses in the near term and would therefore not recommend it at this stage.

2 comments

This is a great article! Thanks for the information.

by Brandon Roland on May 24, 2007 at 12:46 am. Reply #

I believe HyperOffice Intranet solutions are much better than Sharepoint. Then again, that’s just my opinion.

by Christiene on January 11, 2008 at 2:04 am. Reply #

Leave your comment

Required.

Required. Not published.

If you have one.

Protected with IP Blacklist CloudIP Blacklist Cloud