Content Management Systems – Principles and Concepts of Information Assurance

Content Management Systems – Principles and Concepts of Information Assurance

A major challenge in businesses is a misconception, that data is 100% secure concerning any part of its data processing within that business. This data processing concerns the content management lifecycle; from creation, to storage, to distribution, to workflow and eventually archive of that data. The misconception? “Security Breach? Its not going to happen to us” mentality. It is vital that there is an understanding of Information security and Information Assurance in content management security. As an information security professional (or Architect covering security), you should be prepared for any aspect of secure breach can happen that can affect the confidentiality, availability, and integrity of the data. Any service delivery disruption caused by a security breach is harmful to the profitability, and has far reach consequences which could include liability, status and much more.

(more…)

Office 365 Monitoring using System Centre Operations Manager

Office 365 Monitoring using System Centre Operations Manager

One of the most compelling challenges for Office 365 is centralised monitoring. Those working in the SharePoint arena will know only too well importance of monitoring and reporting across the platforms they manage. This is not simply from a technical but also from proof of service; the availability and evolution of those services.

(more…)

SharePoint Configuration Management

SharePoint Configuration Management

Platform Governance is there to help bridge the communications gap between the business and technological groups; ensure ROI, mitigate risks associated with IT Projects impacting SharePoint, and provide a key cog for SharePoint Service Delivery, capability of service.

When a SharePoint solution is delivered, you need to ensure the continued availability of that service to related customers. You will need to protect the integrity of that SharePoint solution. You will need to prove that the SharePoint solution is capable (that is, that things like Change, Risk and Issues concerning the SharePoint solution are managed and communicated and documented).

Take this scenario:

Fabrikam is a manufacturing organization and has a project management office. Their IT team gets SharePoint and installs a site for the project management office. The company culture isn’t strict in terms of website control, and the IT team do not create documentation concerning the design or installation. The small site expands as more projects are added, and more features are added. Again, no documentation concerning changes was made. Six months into the project management office site, and there is a request to add more functionality which will change the way in which the project management office runs. However, in order to do that information is needed about the features applied and the reasons behind why they have been applied. Chaos ensues as no-one has any idea on how the sites evolved; the IT team is squarely blamed for not having adequate documentation about the sites history

ARandom Person

SharePoint Programme Manager, FABRIKAM INC

Check out my book 'Implementing and Managing SharePoint Projects 2010'

This section comes from my book, Implementing and Managing SharePoint 2010 Projects, which is a great read covering lots of service delivery topics to aid SharePoint programme delivery.

This comes from my book

 

Clearly, not a scenario that you would ever like to find yourself in! Therefore, you should use Configuration Management techniques to control specifications, drawings, software assets and related documentation which define the functional and physical characteristics of a SharePoint solution, down to the lowest level required to assure standardization. Control of those elements also means you control the SharePoint solutions and its Platform, under a Change Control regime and to control release of SharePoint solutions into your SharePoint platform. This enforcement of change control is linked to Platform Governance. The Configuration Management (CM) process also provides a documented, traceable history of the development lifecycle of SharePoint in an organisation, including any modification, upgrades or variants, and should be used to hook into your Change Management processes with SharePoint.

SharePoint when implemented is defined by identifying configurable items based on its technical, administrative and maintainability criticality. The selection process is one of separating the elements of SharePoint on a hierarchical basis for the purpose of managing their baseline characteristics.

Any item associated with the SharePoint solution, including deployment and any associated asset is subject to Configuration Management.

The diagram below illustrates the degrees of control applied to a configurable item during its implementation lifecycle.

 

Configuration Image 1

 

Initially an item is uncontrolled whilst under development by the author. It becomes controlled once a unique identified has been allocated and the item is subject to review. Once the development of an identified configurable item is sufficiently stable to declare a baseline standard, it will be subject to configuration control processes. On small projects, configuration management techniques may be applied by the project staff using a simple SharePoint list to control baselines and record the version / issue status of the identified configurable items.

On larger projects, particularly where a large number of hardware drawings or modules of SharePoint features have been produced, Configuration Management may be delegated to specialist staff. The advantage of a central site CM facility, with its own specialized staff and archive, is the long term maintenance of project configuration records. However, the production of SharePoint add on features (e.g. Web Parts, Automation, Branding, Site Definitions etc.) is particularly well suited to the use of configuration management and tools, remaining under project control.

Check out my book 'Implementing and Managing SharePoint Projects 2010'

This section comes from my book, Implementing and Managing SharePoint 2010 Projects, which is a great read covering lots of service delivery topics to aid SharePoint programme delivery.

This comes from my book

How to apply Configuration Management in SharePoint

To apply Configuration Management in SharePoint you will need to state a policy for its use and its procedure. You will need to ensure that any deviation from this policy, together with designated configuration management authorities for the SharePoint delivery program is documented. Other configuration management details may be contained in a separate configuration management plan, depending on any contractual arrangements or the size and complexity of SharePoint being implemented.

As the SharePoint Delivery Planning initiates, so should Configuration Management. You must choose a set of methods, procedures and tools to satisfy the requirements below. If the client organization does not have any Configuration Management processes in place you will need to create those processes. A method of recording these is via a central SharePoint site for the purpose of storing CM documentation and history of changes to the solution. If you intend on doing this, and if the client does have a full configuration management process running, investigate and find out if either (a) there is connectivity between that and the SharePoint site and/or (b) that the configuration management process in place includes the requirements below:

  • Enable unique identification and description of the SharePoint solution and components
  • Enable the evolution of products and their components to be controlled and traced
  • Enable identification and control of the means by which products will evolve in order to satisfy their requirements
  • Record securely and maintain all the information required
  • Provide validated, identical copies of products

To satisfy these fundamental requirements, the configuration management system should provide the following:

  • Methods for unique identification and version control for all products and all components of a product
  • Methods for receiving and acting on observations concerning a product and for recording and controlling changes arising
  • Methods for keeping track of all items being produced or utilised by a project, including items inherited or sub-contracted
  • Methods for defining the means by which a product may be build or re-built and which must include any special requirements after delivery or after project completion
  • Methods for marking, storage and handling of all required media types
  • Procedures for controlling replication and distribution of products

 

Configuration Management Applies to SharePoint

Configuration Management is mandatory for all SharePoint Delivery programs. You cannot have a controlled SharePoint environment without records concerning is makeup and traceability concerning changes made. Even from the perspective of a handover of a SharePoint solution, as a Delivery Management you cannot simply handover a SharePoint solution by stating “I’ve finished implementing SharePoint for you, off you go”. CM provides a structured system handover meaning everything that the delivery program can be audited on, everything that the delivery program has an asset of (and that includes all documentation, technical specifications, software assets etc.)

Configuration Management is needed for any deliverable of hardware or software or where there is a change to either of those in a production arena. Configuration Management applies to configured items that are used in the development of a SharePoint product but are not a deliverable in their own right. Typical configuration items include:

  • SharePoint specification (design, topology, network connectivity)
  • Test Plans
  • Drawings (overall and detailed)
  • SharePoint Software Assets, and if any additional development applied to SharePoint, any code, program listings, associated documentation
  • Service or User ManualsOther items to which Configuration Management applies must be identified as part of any SharePoint solution delivery and subject to review.

 

The Delivery Manager Specifies the Configuration Management Policy

The Delivery Manager is responsible for creating a configuration policy and the techniques to be applied. If this policy deviates from that stated in the Configuration Management procedures, those deviations must be defined in the SharePoint 2010 Quality Plan.

Additional issues that also need to be recorded are:

  • The designated configuration management authorities for the project
  • The identity of the root document or source from which all configuration status records can be traced
  • The Delivery Manager should appoint a configuration authority who will control the CM activities (SharePoint Solution Architect).

Configuration Management Glossary of Terms

Configuration Item An item selected for configuration management. Configuration Items are established on a hierarchical basis with one item comprising the complete product (hardware / software). This is then broken down into its lower level constituent items or parts, each with its own reference number
Configuration Baseline A specification or product that has been reviewed and agreed on that therefore services as a basis for further development. A baseline can be modified only through formal change control processes.
Controlled Item An items that is not identified as a Configured Item but still requires controlling in a formal manner
Configuration Control The systematic evaluation, co-ordination, approval and dissemination of proposed changes and implementation of all approved changes in a Configured Item
Master Record Index The index(es) to the master set of drawings, specifications which define the configuration item. This term is used generally to refer to a set of indexes that provides a record of the Configuration Items.

 

Bring the SharePoint Item under Control as it Develops

The following diagram illustrates when a SharePoint item should be brought under change control (note – whilst it refers to SharePoint 2010, the process is agnostic of SharePoint version):

 

Check out my book 'Implementing and Managing SharePoint Projects 2010'

This section comes from my book, Implementing and Managing SharePoint 2010 Projects, which is a great read covering lots of service delivery topics to aid SharePoint programme delivery.

This comes from my book
ConfigManagement Pic 2

 

The diagram above shows the passage of a configurable item from its generation to the point where it comes under customer control through change control. Each of the vertical lines represents a formal stage in the development of the item. Once the internal review cycle is complete the item will be raised to version 1, or, if being updated, to the next appropriate version number and issued for external use. From that point on its status shall be recorded in the Configuration Baseline Index and any changes to the item must be introduced via formal configuration control procedures (see the below section Changes to Configured Item Must be Controlled). When the client takes delivery / control of the product, there will be a need for a formal Master Record Index to be generated for each Configuration Item.

Control the Item Prior to Configuration Management

Whilst a configuration item is being developed during the pre-configuration stage, the author is free to make whatever changes that may be necessary on a day to day basis. Understanding the development of the item is still important and significant changes should be recorded as part of the configuration item.

Historical information needs to be maintained for Configuration Management auditing purposes. In SharePoint, you could, as shown in the above diagram, construct a list with Version Control switched on utilizing Minor and Major Versions. Those allow you to enter comments as the item moves from draft to draft version until it becomes a configured item.

Bring the Configured Item under Configuration Management at the Right Time

As the development of the item stabilizes, the baseline standard can be declared and the item brought under configuration control. Each configuration item must be given a unique reference number. All configurable items must be regularly reviewed. The review record may initiate further changes to the item, causing the draft number to be raised. Maintaining all the comment copies of a technical document is not necessary, provided the record and / or minutes are maintained to provide the traceability of the review process

Establish a Configuration Baseline for Each Item

A configuration baseline index shall be formally maintained as a status and history record of the project’s configuration items. The index must include the hierarchy and inter relationships of the items.

At appropriate points in the project development and certainly when the product is ready for delivery, it is necessary to product an index of all the configuration Items. This index is often called the Master Record Index (MRI). For software products, a Build Definition which defines the software and computing content of the release must be prepared.

A Configuration Status Account Provides History

Configuration status accounting is a mechanism for providing records of the current status of all the projects configuration items. The configuration status records provide complete traceability of what has happened to the configuration to date. These records can be centralized into a SharePoint CM site. For example, you could have an item subject to version control and carrying metadata – a multi-choice column called Configuration Status, for example. This configuration status column could have values defining the configuration level of the item. This means that not only do you have traceable history but you can also identify when and who made alterations to the configuration status and if there were any comments made at the time they would also be available.

Changes to Configured Items must be Controlled

Once an item comes under configuration control, changes can only be introduced by means of a formal change control process. All items in a SharePoint production and SharePoint User Acceptance come under configuration management. The following example of a processing chain concerning SharePoint Delivery through Change Control is shown in the below diagram:

 

Check out my book 'Implementing and Managing SharePoint Projects 2010'

This section comes from my book, Implementing and Managing SharePoint 2010 Projects, which is a great read covering lots of service delivery topics to aid SharePoint programme delivery.

This comes from my book
ConfigManagement Pic 3

Summary

Every item concerning SharePoint running in a production environment is subject to configuration management; whose rules are bound by Platform Governance. You may wish to argue that Configuration Management is overkill; that there is far too much ‘process’ and it would hamper SharePoint delivery. My response is the following question:

How do you know who created what?

If you cannot answer what constitute SharePoint operations under change control you do not have an environment under control. You do not have an environment duly documented to show the purpose, premise and operation of your SharePoint environment.

Configuration Management manages and records and brings a logical change control process, so that anything that takes place to deliver a product has a history from the point it was designed to the point it was implemented. SharePoint configuration management defines processes that describe the following:

  • Makeup of Infrastructure
  • Software and Hardware Assets
  • Modification
  • Procurement and Delivery (for example, third party solutions).
  • Tracking and AuditUnderstand the ComponentsItem Identifications
  • The basic or lowest level of configuration items for SharePoint under which configuration management (CM) will apply is the software under which SharePoint operates. However, any feature that comes off that is an item under CM process. For example, the Initial design of a site if not under strict control does not need to come under formal configuration but you should use sound judgement and identify whether changes to the site in the future could impact on customer experience and satisfaction.
  • Ensure that you know what makes up your SharePoint platform. Even before providing a SharePoint solution (even if it is the platform itself), and even before someone mentions – “hey what kind of solution do you want?” You need to document what makes up the SharePoint solution. Assuming that you have done that and have defined the specification, you then need to ensure you that the level of documentation is sufficient not just for you, but for anyone whose services you consume, and for those who would need that information as part of the CM process.
SharePoint Configuration Management

Renewed into my SIXTH year as an MVP

Am pretty humbled and pleased as punch to be renewed today, July 1st 2016, as a SharePoint MVP for the SIXTH year running. A big thanks of course goes out to all I have managed to reach out to enabling me to share my expertise with others and help individuals maximize their use of SharePoint and Office products. Of course, this works the other way around in being part of a great MVP group, all of whom are committed to providing knowledge, aid and expertise back into a growing and evolving community – and I’ve learned so much from the MVP group, the MS Product team and so many more. Many thanks therefore go to their support and yours, in helping me share knowledge and helping me to keep focusing on providing continued blogging, getting to grips with tweeting, forum support, presenting, helping with user groups, writing, helping organize events and much more!

 

Content Management Systems – Principles and Concepts of Information Assurance

Cyber Security – a Service Delivery Context

Cyber security is about data loss prevention, detection and response. Service delivery includes ensuring the protection and managing the integrity of content through its lifecycle. This is cross platform, and cross industry, so in relation to whether you are using SharePoint on / off premise, or SharePoint is at the centre of an estate of multiple technologies, cyber security concerns all of these. These requirements directly relate to a technology current and future state – according to Gartner (and covered in my last keynote):

  • By 2016 Biometric sensors will be featured in 40% of smartphones shipped to end users.
  • By 2017 one-third of consumers in emerging markets will have never owned a windows device.
  • By 2018 more than 50% of users will use a tablet or smartphone first for all online activities.
  • By 2020 40% of enterprises will specify Wi-Fi as the default connection for non-mobile devices.

With the match of evolving technologies related to the above points, such as Internet of Things (IOT), Content Analytics, Hybrid Cloud Computing, Big Data, In Memory Database Management and more about to become widespread; how to provide integrity, protection, and governance to data becomes more important. We all work with data, utilising physical and digital technology in our daily lives. We use countless methods to create and use data, and assume that the accessed data has security maintained. In providing measures, providers of secure access to data provide measures to ensure legitimate access. Consequences resulting from unauthorised access to data could include:

  • Time, effort and monetary resources to correct.
  • Damage, deletion and compromise.
  • Damage to reputation.

From a global perspective there are security challenges in the ‘digital developed’ versus ‘digital developing’ world. For the developed world, users’ access information through a digital framework; internet services provisioned over high level Wi-Fi and 3G/4G networks. But, in the developing world, there some 950 million people still without the means to connect to these networks. Security provision is not a one-fits-all. Additional global challenges are ‘Freedom of Speech’, ‘Country A Trust Country B Trusts Country C’ and the ‘Political Will’.

From a company perspective, the primary objective is to ensure the management of security; enforcing breach policies and governance is vitally important to ensure their data integrity. The challenge is that the company workplace is changing, and so is the physical infrastructure. Whilst physical and digital technology has become increasingly sophisticated, like dongles, passwords, data encryption, the task is convincing staff – from senior manages to entry level employees that they need to become more security accountable, becomes harder due to their emotions about security and privacy.

From a personal perspective, security intertwines with privacy. Advances in technology threatens privacy, reducing the amount of control over data. Privacy affects technology use. The challenge is the space in which this takes place in the digital world, which is completely online through the use of the internet, which never corrects and never forgets.

In summary, humans adopt any cyber security imperative. Technology is neutral. This means work must be done in the governance, training, and management of data to protect integrity and at the same time provide detection and contingency against loss. Opportunities include:

  • Proactive security reporting
  • Automated content filtering
  • Protection of content via search engines
  • Child Protection, for example, Extremist content removal
  • Security Automation – for example, E-mail Scanning
Delivering a SharePoint ‘Data at Rest’ Encryption Service

Delivering a SharePoint ‘Data at Rest’ Encryption Service

Compliance Importance

Service delivery includes the protection and the integrity of content created. Like security, compliance is cross platform, cross industry. It does not matter whether you are simply using SharePoint, or using multiple platforms to service content into SharePoint.

Compliance concerns:

  • Monitoring, isolation, automated operations, secure network and encrypted data.
  • Security best practice, and the customer controls.
  • DPL, audit and retention, eDiscovery and Data spillage.
  • Standards such as ISO 27001, FISMA, HIPAA BAA, EU Model Clauses, and the CSA.

Note – this article is geared to looking at SharePoint on-premise. Office 365 is pretty much covered on encryption technologies. There is a wealth of information concerning this and more the Microsoft Office 365 article on this link: Data Encryption Technologies in Office 365. Also, there is also a huge amount of information available in its Trust Centre. There is a specific section concerning compliance on this link: Continuous Compliance in Office 365

Encryption is a solution against Data Breaches

Data Breaches are not simply relegated to external infringement of data by those who should not have access. This is an ongoing problem, and regulators are ramping up audits and confirming standards to ensure companies are taking heed. Some data breaches can occur for any of the following reasons:

  • Data copied and taken off premises
  • Downloading information then emailing the data unprotected to external parties
  • Saving content to a folder which is publicly available online
  • Provisioning of production data in test or development systems

Protecting against data breaches therefore must consider the data at the location where it is saved. Encryption of the data is without doubt the highest level of protection the data can get to prevent that data being subject to a data breach. However, the human culture of how they handle security matters is also extremely important.

SharePoint Data Security

When data ends up in SharePoint, the content is stored in SQL (at rest), except in the case of RBS (Remote Blob Storage). The data in SQL is ‘unstructured’, meaning, that it is not ‘easy’ to simply dive in and set security on specific bits of data. The data is also ‘unknown’, meaning that it is not also ‘easy’ to identify what data relates to what area and in what context – and even if you could, securing that would be a difficult in the extreme.

SharePoint, ‘Out-Of-The-Box’, provides access controls only to protect the data based on the role of the user. These access controls include:

  • Permissions access to the data
  • Auditing controls, stamping of data, lock down.

However, there are data encryption components provided ‘Out of the Box’ for SharePoint. Data could be read in a number of ways (described below). And again, confusion reigns from people trying to get to grips with the options. Some people even confuse authentication with encryption. I have even heard a client state that surely provisioning SSL will provide encryption. That client had to be informed that SSL only secures the network connection to the link where the data can be accessed (that is, Data in Transit, NOT Data at Rest). It does not protect the data from being ‘read’ at its source. Anyone unsure of this should check out this article Do you need SSL?

Compounded is the challenge humans the culture they apply to security – it is not simply a ‘one hat fits all’. From people I have spoken to and worked with on this topic, it is generally stated that users are simply not taking enough security measures to protect the data. Yes, one could very easily apply role permissions to ensure that individuals cannot read, write, or even upload. Provision of auditing tools to alert individuals of unwanted access is possible. Locking down of data so that the data cannot be modified or downloaded is possible. However, those solutions is not on the same plain as the protection (encryption) of the data where it is stored. For example, if a disk holding data was subject to attack / access from those who should not be able to read the data at source, then surely that is an out of compliance and classed as security risk. Indeed, taking a SQL SharePoint content database off a disk, and then applying that content database into another web application in another farm is relatively easy. Even if that operation takes place unless under strict and controlled circumstances (note that in some cases a challenge to implement, especially when working with multiple technical teams like a separated team for SQL, Windows, SharePoint, etc.) the mere fact that the data is in a read-able form when transmitted could be still construed as a data compliance issue.

The solution is looking at the data within SQL; that requires ‘security hardening’ and encryption solve these challenges.

Implementing encryption for Data at Rest starring SQL

As pointed out, SharePoint data resides in SQL. That is the point where encryption should be brought into play. Microsoft recognised this way back with the implementation of SQL 2008 and provided two technologies to protect ‘data at rest’ meeting various compliance standards. Thankfully, the architecture is in place to provide, since SQL provides the ability to have the data encrypted, using the following technologies:

  • EKM – Extensible Key Management
  • TDE – Transparent Data Encryption

Details of these technologies are available here:

Understanding Transparent Data Encryption (TDE)

Switching on encryption is not just a ‘fire and forget’ action. A number of tasks must be completed beforehand in order to deliver the service:

  1. The environment must be modelled first; for example, identifying the number of users, size of documents, underlying infrastructure, specific technical roles and skill set.
  2. Disaster Recovery environment and enabled technologies. Check the infrastructure applied to the SharePoint farm concerning DR. Check whether RBS is in use which will impact on how encryption is to be applied – note that TDE does not apply to content in a file stream because that content is not encrypted in SQL so additional encryption methods would have to be applied.
  3. Key management – who is responsible for managing the key – is it the SharePoint team? The SQL team? The Security team?
  4. Advise your corporate security team including any stakeholders of the impact of encryption. There is a technical as well as business impact. The technical side is a degradation of overall performance. From investigations I’ve been advised this could be up to 2% overall. On the business side is an impact on support, particularly from SQL and Security, since they have an extra accountability to the management of the encryption. Note also, that you should test this thoroughly in a isolated test environment and against DR and run DR tests.
  5. Apply Encryption at Rest for SQL, and for this, TDE must be implemented. Remember, TDE is used to prevent the restoration or attachment of databases into another SQL instance. This means that a master key needs setup, the database requires configuration, and the encryption password (stored in the certificate) must be backed up. Then, all must be tested (i.e. backup, restore – which should fail – then restore again along with the key – which should work).
  6. Ensure connections to SQL are encrypted. This means protection from those attempting to use tools to get at the data. This means forcing encryption settings to enabled for the SQL server and applying the certificate.
  7. Prevent other machines accessing the SQL instance (i.e. attempting to connect a different farm, or a machine outside of the ‘allowed server authentication list’ to a SQL instance being protected), you would setup isolation rules by configuring the firewall on the relevant servers themselves.

Note – doing this by yourself in a company with multiple teams looking after the infrastructure is unwise. You should seek aid from your SQL teams, as well as advice from Server teams.

To get detailed information on how to technically deliver encryption for SQL as well as isolation, step by step, check out the excellent article on this link:

Securing SharePoint: Harden SQL Server in SharePoint Environments

Conclusion

A key aspect of Data Compliance is the protection of data. Companies use data compliance to protect data, provide policies, processes and systems, and this stretches to governments and individuals. This is cross platform, and cross technology.

In Sharepoint, in order to meet data compliancy challenges and provide solutions through service delivery, there must be understanding that there is encryption tools available to data where that data resides. Encryption is the keyword here, since through this article I have explained how data can be securely stored and protected from unwarranted access.

SQL provides encryption and key management tools so that the data becomes unreadable to anyone except those who should have access to that data, using key management to automatically convert data back to its original, readable form. There are additional opportunities available to harden the SQL platform so that there is isolation and authenticated access.

The implementation of encryption though, whilst relatively easy from a technical viewpoint, provides many challenges to overcome in implementation. Security awareness, and identifying shortfalls in the surrounding infrastructure is vital, along with the marrying up of the roadmap of SharePoint. Implementing future technologies down the line will have an impact on encryption, so ensuring that you continually review encryption usage and change management is necessary.

SharePoint Security and helping users become more aware

SharePoint Security and helping users become more aware

A key aspect of implementing SharePoint in an organisation is relevant to security of content. The success of SharePoint in an organisation is due not only to how comfortable users are with using their current technology with SharePoint, it is also down to ensuring that the users are comfortable knowing the data they manage on their SharePoint sites are secure…

(more…)

Port, Pies and SharePoint Support

Port, Pies and SharePoint Support

Merry Christmas Everyone!

As the seasonal period quickly approaches, the discussions concerning what happens to supporting SharePoint over the holiday either approaches, or has been covered, or even assumed.  The Christmas period is of course where your SharePoint sponsors are more likely to show a little more concern than normal about how their SharePoint platforms are going to be monitored over the period.

So then, lets remind ourselves of the holiday period in question – basically, the days that will relate to anyone, is the week of Christmas starting from the 23rd through to the 28th. There are two days pretty much important to us guys in the UK over the seasonal period, especially in Scotland – Christmas Day and New Years day. Then there is Boxing day when it’s likely that you would be relaxing in front of the telly, or sledging, or skiing – using that day to wind down after the Christmas day madness. Then there’s the two days after boxing day, the 26th and the 27th, where relaxation, relief and playing with the various presents, and getting stuck in to food 🙂

So that means that over the period you are likely to do over those two days, probably a combination of one or more of the following not be in the Office, switch off the mobile, inform people you are not available?

So chances are, that on the days in question, you will be chilling out, and possibly even like me having a choice Mince pie, a Glass of port (or more – like Rum)…

But this is not about what you will be doing over those periods away from the office. It is about how you are going to support SharePoint, isn’t it?

First, let’s consider the available types of support:

  • On Premise SharePoint Support / IT Support combined / Outsourced
  • Off-Premise Office 365 Microsoft provisioned Support
  • Third party product support
  1. Throwing caution to the wind

    My dad once said to me when I was a lot younger that in order for Santa Claus to know what present I would like, that I should write a letter, and throw it into the wind when it was blowing north, so that the letter would reach the north pole.

    Of course, by doing that I eventually realized that the letter would not get there, unless my dad without me seeing ran like the clappers to retrieve the letter once I threw it out of the window.

    Clearly, I was throwing caution to the wind, assuming things would happen – luckily for me, most of the times when I did throw that letter, things would work out – but only because there was a contingency – my dad, running like the clappers.

    This relates in a way to the lack of responsibility those charged with SharePoint management judge the level of the support needed to ensure the availability of SharePoint services over an important period, like Christmas! There is not enough preparation carried out preceding the Christmas period by some organizations, to ensure that there is adequate coverage of SharePoint support. In some organizations, instead, there is a laissez faire approach, by simply throwing caution to the wind. Or, worse still, their IT support departments will not think to include SharePoint as system that should be monitored, and instead not including those with basic knowledge of SharePoint on the support desk.

    Take this real scenario which happened a while back. Fictional company used though, however, if their now SharePoint support individuals are reading this article, they will definitely remember this event!

    Five days leading up to Christmas day. Fabrikam has an IT Support department, and a number of individuals who are tasked solely with looking after SharePoint, called ‘SharePoint Admins’.  These SharePoint Admins look after the platform solely, there are no monitoring systems in place except for the server monitoring systems (alarm bells ringing already – no pun intended). A member of IT Support asks what the SharePoint Administrators will be doing on Christmas day.

    “We won’t be around, that’s for sure…” … “SharePoint looks after itself” – pipped the SharePoint Administrators. “We will just take a peek at midday to make sure all is well”.

    IT Support reports this discussion to the IT Support Manager. The IT Support Manager waves his arm saying ‘that’s not a problem, we have IT Support people on the desk who know a little of SharePoint, nothing can really go wrong’.

    Over the next 4 days, no more is mentioned as the company ‘winds down’. On the 23rd of December, the CEO puts a Christmas message to the communication team who then puts the message in an announcement list on the Fabrikam SharePoint Extranet.

    Christmas Day. At 9.30am that day, the CEO of the company, with his family in the Seychelles, decides to show a friend the message that was put on the SharePoint Portal on the 23rd. When attempting to display the announcement, the web page displays an error. Concerned, he raises a call into IT Support. IT Support try to get hold of the SharePoint Administrator, who has switched off his mobile because he is at the top of the hill where he lives, sledging. The CEO asks whether there is anyone else who can help, but IT Support have no knowledge of anyone and neither do they have any other contact number for the SharePoint Administrator.

    The SharePoint Administrator calls in at midday to find chaos. The CEO is fuming because he has no idea whether anyone saw the announcement, and even if they tried saw the error which was embarrassing. IT Support have stated to the CEO that they do not know how to fix the problem, which is embarrassing. And, guess what, the SharePoint Administrator, who fixes the issue in minutes finds that the rest of his day is spent building confidence with the CEO and IT Support – he is embarrassed.

    That SharePoint Admin threw caution to the wind. And in doing so, assumed the following:

    1: No one will care whether SharePoint is available or not

    2: The SharePoint Admins does not care whether SharePoint is available or not

    3: The SharePoint Admins assumed that the problem will ‘fix itself’

    4: The SharePoint Admins assumed that they will eventually be told or will find out themselves that there is a problem, and that no one will moan when they do, or how long it takes to correct the problem.

    5: That if a problem occurs where SharePoint is not available that there is no financial impact or otherwise

  2. Preparing for Christmas

    You must prepare your SharePoint environment to be supported over the Christmas period. This is just like preparing for Christmas itself. Doing things like putting up a Christmas tree, carefully putting up decorations without falling off ladders, writing Christmas cards, posting them, wrapping presents (carefully) without getting the sellotape stuck on the wrong part of the wrapping paper and making a mess. You put effort into doing all of that because you want to make others comfortable and yourself prepared. Therefore, there is no difference when it comes to SharePoint support.

    There are a nine things you could put in place, so that you can ensure that SharePoint is supported over the Christmas period:

    1. Make it clear the days when there will be SharePoint cover over the period. When on holiday, for example, ensure that there are phone contacts and that is communicated to IT Support and your SharePoint sponsor.
    2. Ensure that the contact details have a backup. One number is not enough. Consider adding on the home phone number or the number of the place you will be staying / visiting on the key days. Reasons for this could be bad mobile coverage, or you could be travelling
    3. Ensure that there is a remote method of you accessing the SharePoint environment. Most organisations using on-premise SharePoint have a method whereby individuals can log in over the Internet using say a Citrix / VPN / Xen Desktop etc. connection.
    4. Ensure that a member of the IT Support team is aware of any resolutions that can be used for ‘possible issues’. For example, one issue could be that in order to quickly reset an application pool for a SharePoint site to go into IIS on a relevant server, etc.
    5. Ensure that there is a list of the infrastructure, and details of any specific login information.
    6. Based on point (3) above, try to log into the SharePoint environment at least once a day to quickly check the status of the environment.
    7. Ensure that relevant third party information concerning their levels of support is listed and the details made known to IT Support.
    8. Provision monitoring systems for IT support which includes the status of key services to the SharePoint platform (on-premise).
    9. Provision monitoring services which includes the status of services for Office 365 Tenants
  3. On-Premise and Off-Premise Support are that different

    At a very basic level, the provision of support for SharePoint over a Christmas could be divided two segments – the SharePoint ‘supporter’ – the associated services ‘supporter’.

    For on-premise SharePoint, the levels of support are:

    1: The SharePoint ‘supporter’. The person(s) responsible for managing the products provided in SharePoint services.

    2: The Associated services ‘supporter’. The person(s) responsible for providing support for the infrastructure and associated services.

    The interesting aspect of Off-Premise (e.g. Office 365) Support is that there is in effect, also two levels:

    1: The SharePoint ‘supporter’. The person(s) responsible for managing the products provided in the Office 365 tenant – e.g. SharePoint Team Sites and relevant products in those sites.

    2: The Associated services ‘supporter’. The person(s) responsible for providing support for the Office 365 tenant.

    Both of these, on-premise and Office 365 have monitoring tools. Both have the priorities and service delivery of support defined to SLAs, which is communicated to the person responsible for managing the products provided. This information is then cascaded in an understandable form to the client.

    There is a huge amount of monitoring tools available to on-premise SharePoint support (default and third party provisioned), which I will not go into (and there are a huge number of articles that describe them). SharePoint Online now has a good amount of services and tools for monitoring. The Office 365 Admin app for which allows those responsible for supporting Office 365 to connect to their organization’s Office 365 service status on the go. The app enables them to view service health information and maintenance status updates from their mobile device. You can also filter information by service subscriptions and configure app data refresh intervals.

    To get the app, go here:

    https://www.microsoft.com/en-us/store/apps/office-365-admin/9wzdncrdtbmj

    Office 365 also has the Office Message Centre. The Message Centre is located in the Microsoft Online Portal. The Message Centre is the central hub for communicating with you about Office 365. And in there you will find the topics including those in the Admin Task Newsletter, messages on new feature releases, and other important information. The Office Message Centre also links with the Office365 Admin app, so you can have messages concerning the state of services sent direct to your mobile device.

    More information about the Office Message Centre: http://blogs.office.com/b/office365tech/default.aspx

    There are also methods of logging transactional data through code. Microsoft is releasing the Office 365 Management Activity API which allows visibility of all user and admin transactions within Office365 covering activity logs. These logs would include information like tenant, service, action, object, user location, IP Address and more.

    More information about the Office 365 Management Activity API: https://blogs.office.com/2015/04/21/announcing-the-new-office-365-management-activity-api-for-security-and-compliance-monitoring/

    Additionally, for those who have access to Microsoft System Centre Operations Manager, there are of course services available to monitor SharePoint on-premise, and to monitor Office 365. For those who have not done this before, or need to get further information, I wrote a blog ‘Office 365 Monitoring using System Centre Operations Manager’ located here:

    http://blogs.msdn.com/b/mvpawardprogram/archive/2015/07/08/office365-monitoring-using-system-centre-operations-manager.aspx

  4. Conclusion

    I hope by reading this article you have understood the importance of providing adequate and understandable SharePoint support over the Christmas period. The ability for you as a SharePoint ‘supporter’ to be forewarned of issues so that at the very least clients can be informed is vital. For on-premise, the ability to be contacted, or the ability provided to IT support to be able to deal with common issues, provides a service which in the eyes of the SharePoint sponsor is ‘good’. So I do hope that you are able to take points from this article and apply them to your SharePoint support cover proposals….

    I’d like to finish up by wishing you and yours a wonderful holiday season!

Web Analytics is a Revolution – Deciding the tool and management process

Web Analytics is a Revolution – Deciding the tool and management process

Introduction.

Web analytics, is of course about, at its heart, about user journeys. Web Analytics is a subject of complete interpretation, and reminds me of the very famous quote by Mark Twain. To explain, Mark Twain popularized the saying in “Chapters from My Autobiography”, which was published in the North American Review in 1906. Mark Twain wrote “Figures often beguile me, particularly when I have the arranging of them myself, there are three kinds of lies: lies, damned lies, and statistics.'” This is quite poignant since when applying the quote to understanding data, there is a lesson in terms of the misuse and misinterpretation. Also, in treating ‘statistics as lies’ one could be ignoring the valuable aspects of information that we deal with.

For me, Web Analytics is useful weapon for managing site control, and is one of the cornerstones of service delivery in any SharePoint solution provided to users.  Web Analytics improves the usability of the SharePoint solution, drives collaboration, boosts ROI (Return On Investment); and thus enhances the overall productivity of SharePoint users. SharePoint workers could very easily describe Web Analytics as “the analysis of SharePoint content, in order to improve the customer experience for owners and visitors”.

Web Analytics is everywhere on websites. It is possible for owners to get information concerning a myriad of customer behaviour interactions. But that then creates a conundrum. There are many tools trying to fill the space. There are many online search engine service even offers analytics for free to ’embed’ into websites.  Therefore, the challenge is that whilst there are tools to do the job, the procedures and systems in gathering the information is little understood, and therefore, makes it harder for owners to make decisions.

So this article will detail some “insights” concerning Web Analytics, why Web Analytics is needed, what are some of the challenges organisations face in managing Web Analytics, and what process needs to be put in place to choose from the myriad of Web Analytical tools available.

Note. This article does not single out or argue the case for a particular Web Analytics tool, and neither will this article will not advise that you should use solution over another. However, I should point out, that in order to write this article that I have access to quite a few providers and other case studies. Should you require further information concerning providers, or wish a demo of a particular solution, then by all means please contact me using the Contacts link at the top of the page.

Ok, to the article. The article presented as is set in the following segments:

  • Why is Web Analytics so powerful and important?
  • What are the challenges faced by organisations managing Web Analytic data
  • Why is a method to provision a Web Analytics solution required?
  • Step 1 – Agree with the Business where the site requires Web Analytics
  • Step 2 – What is available from using SharePoint Built-In Features?
  • Step 3 – Work the Business Requirement
  • Step 4 – Wrap Service Delivery into the Web Analytics solution provision
  • Conclusion
  • Also, check out the presentation as this is directly associated with this article.

Why is Web Analytics so powerful and important?

Any organisation using SharePoint needs some method of identifying SharePoint usage. It is critical to measuring adoption of SharePoint solutions, identifying support needs current and future, auditing and controlling access to content, helping the formation, management and enforcement of business rules concerning content use, providing a yard-stick in terms of measuring that all important ROI. And because of those reasons, Web Analytics is powerful. Web Analytics defines a ‘make’ or ‘break’ of a SharePoint solution. Web Analytics defines the market possibility to provision a SharePoint solution and ascertain its success. Here are a few more reasons:

  1. You can measure and track results across time. Web Analytics can show you what pages on the sites are viewed and that will show why they are not accessing the relevant areas, identifying what content has value, and what content does not.
  2. You can understand site visitors and prospects. Web Analytics can show you the terms customers are using to find content.
  3. You can improve site experience. Web Analytics will help you to understand customers experience in terms of what they like and dis-like and how they interact with site components.
  4. Analytics is vital for those managing websites. An interesting aspect is this blog that indicates Google reports over 10 million websites are using google analytics. This is simply an aid to prove that analytics is not new. Notably though, Google Analytics is not a good fit for SharePoint Intranets or for any website where data privacy is a concern.
  5. Data Scientist is the Sexist job of the 21st century according to Harvard Business Review. There are many breakthroughs concerning Big Data, like Hadoop, Open Source tools, Data Visualization and Cloud Computing. However, there are challenges associated with this which is the demand on people resources, such as Data Scientists. Once organisations have data they will definitely need people who can find insights and extract value from that data. Check out this companion article which describes why Data Scientists are so important.

What are the challenges faced by organisations managing Web Analytic data?

For organisations utilising web analytics, there are a number of challenges. The following are those reported by a number of organisations using various tools and methods. There are a number of challenges concerning the process of providing Web Analytics – they are:

  • Owners do not know what kind of analytics they require to help make decisions. An owner is an individual responsible for site management. They typically come from the business and own the data on the site. Therefore, they have the knowledge of what data is important, and what is not. What data is structured, and what data is not. From that, they would typically be responsible for sending out data to sponsors and stakeholders concerning site usage, growth, etc. Of course, owners are hard workers. And because of the requirement for web analytics data, they will send out reports on a regular basis. However, not all owners actually understand the data or ask questions to those creating the data about the data importance as it is worked on in the site. This could be down to lack of knowledge, organisational culture, implementation issues, or the wrong person as the owner (someone from IT not from the business), or a combination. Whatever the reason, if the no-one understands or questions the data on the site, then there is no understanding concerning the data importance and therefore when the analytics is surfaced there is no impact – effectively the analytics becomes ‘ignored’ and therefore, misunderstood and untrusted.
  • Web Analytics seen as “not important” for User Adoption Success. The most practical method of measuring User Adoption of a SharePoint solution is to extract data concerning its usage, growth. Additionally, when a SharePoint solution is developed (in fact even before it is) the basic understanding of the solution premise is set. For example, someone wants a SharePoint Finance site, so through planning, design and implementation a site matching the requirements of a Finance site is created, and as such, the premise of that site is known. User Adoption means the definition of that site from a business perspective – not a site which is for ‘content storage’. That definition includes information on what content is important, what process that creates that content, the output and therefore the value of that content. Successful User Adoption means that there are questions and answers concerning, for example, why the site exists (its justification), the lifecycle of the key content stored there, what content makes it thrive, what parts of the site does analytics needs focus on. Web Analytics needs to be factored into the User Adoption process.
  • Needed Procedures and Systems to handle Web Analytics not understood. I have witnessed enterprises taking on sophisticated Web Analytic tools and complex processes, producing the most beautiful of dashboards, and yet, the very people there to manage the human process have very little to no understanding of how to manage the process. Automated tools, using a ‘fire and forget’ deployment mentality, with no method of training other than reading on-line help guides has no long-term value and will result in chaos. Enterprises faced with this situation understand unfortunately very late that there needs to be a process that ensures the right people get keep it up to date, the right people provision the reports using the relevant methods, and that there can be decisions make to affect the site related to those reports.
  • There are lots of tools, difficult for owners to make the right choices. Just because there are millions using a particular Web Analytics tool does not make it the best around. The decision concerning the Web Analytics tool must take into consideration the functionality within SharePoint, work out the value of that tool through weighing alternatives, and the process needs to come from the alignment of business (including the business and owning the solution) and IT.

Why is a method to provision a Web Analytics solution required?

Someone from your department where you have a SharePoint site says “Hey I think we should have some web usage statistics”. To fulfil any requirement like that, including creating a consistent approach, you need to consider the following four points:

  1. Sophisticated data harvesting will require good data collection capabilities. The interaction of the customer does not simply begin at visiting the site; there is a myriad of interactions which may needs to be analysed. So it goes without saying that the system employed must be capable of capturing those interactions, whilst not being overly unobtrusive or effecting platform performance. A good example of this failing is one customer who was using a sophisticated analytics product, but found that it took over 30 seconds to access the site because the product was gathering interactions of that user. Clearly, whilst being sophisticated this impacted on the user ability to actually use the solution, resulting in a problem for user adoption and more issues to deal with at the support end.
  2. Ensure there is a human method in place to collect and distribute the reports. Whatever system is in place to collect the analytics and then to distribute them via an automated process, the requirement to have a human process wrapped around that is important. For example, the process of producing the reports may require schedules (once a day / week / month) to be sent to sponsors, and to highlight insights for the sponsors to view and decide upon. There will be requirements to have those reports produced in various methods, and distributed using various methods. Those methods must be not only easy to follow, but needs to be mapped into part of the site management process. For example, there may be a requirement once every two weeks to review site activity, or to check on the usage of the site following a campaign. Irrespective of the audience, you must ensure that the methods in place are easy to set in place and follow.
  3. Reporting features and capabilities is not as important as usability. The tool providing analytics needs to be easy to operate. That may include the creation of reports, distribution. That also includes modification, configuration. Usability also includes supportability. Whether there is self-help available, and the levels of support available.
  4. The business needs to help determine what metrics are required. I visited a customer using SharePoint who pointed out that they do not have any SharePoint site business owners – instead, their ‘information’ department was responsible for owning the data. I cautioned that customer indicating that as well as a mass of other problems that decision creates, that there is absolutely no way that any individual from SharePoint support would immediately be able to advise what content they should be getting analytics on, as they are not responsible for defining the value of the content. You must engage with the business to determining the nuggets of site interaction, the important focus areas, and the important content.

So, now that you are aware of why steps are needed to provision analytics, the challenges that you will face, and the reasons why analytics is vital to user adoption, here are the four steps needed to provision web analytics.

Step 1 – Agree with the Business where the site requires Web Analytics

First, you will need to query the site owner and business stakeholders of the site, and the output is the purpose of providing Web Analytics associated with the premise of the site. The following questions must be put:

  • Why does site exist?
  • What is the sites focus?
  • What level of usage of the site indicates success or failure?
  • What areas of the site, when analysed will deliver juicy business insights?
  • What parts of the site should you focus web analytics on first?
  • Is there going to be any site marketing strategies?

Ensure you check out this article as it will give you further information concerning the kind of questions you should ask: Business Requirements Gathering in SharePoint.

Step 2 – What is available from using SharePoint Built-In Features?

You will need to know what Web Analytic features are in SharePoint 2013. This is so you can judge whether the requirements obtained from step 1 can be met quickly. Also, you can use this step to further advise the customer on the features available from SharePoint as part of the tool selection process, and the process required to gather and provision the reports. SharePoint has site web analytics measure a visitor’s behaviour once on the site. SharePoint 2013 has includes two types of built- in features covering Analytics and Auditing reports. These are titled Popularity and Search Reports, and Audit Log Reports. The Popularity and Search Reports contain these report types:

  • Usage
  • Number of Queries
  • Top Queries by Day and Month
  • Abandoned Queries by Day and Month
  • No Result Queries by Day and Month
  • Query Rule Usage by Day and Month

TechNet provides further information concerning Popularity and Search Reports here: http://technet.microsoft.com/en-us/library/jj219554.aspx.

As for Audit Log Reports, this is the ability provided in SharePoint 2013 to report on who has been accessing, opening, modifying content in a site. SharePoint provides Audit Log Reports which allows Activity Tracking. The audit log reports can be used by SharePoint owners to determine whether business rules concerning that the usage of relevant content are being met. Audit Reports cover Content Management, Information Management Policy, and Security and Site Settings. You can use Audit Reports to track the following Activities: tracked are and resulted into Audit Reports are as follows:

•    List Access

•    Library Access

•    Opening of Documents

•    Editing Items

•    Check In and Check Out

•    Copying, Moving, and Deleting items

•    Searching

•    Editing Permissions

Because of these options, there are a number of reports available as follows:

Report Description
Content viewing This report shows all events where a user viewed content in this site.
Content modifications This report shows all events that modified content in this site.
Deletion This report shows all events that caused content in this site to be deleted or restored from the Recycle Bin.
Content type and list modifications This report shows all events that modified content types and lists in this site.
Policy modifications This report shows all events related to the creation and use of information management policies on content in this site.
Expiration and Disposition This report shows all events related to the expiration and disposition of content in this site.
Auditing settings This report shows all events that change the auditing settings of Microsoft SharePoint Foundation.
Security settings This report shows all events that change the security configuration of Microsoft SharePoint Foundation.
Custom Reports Run a custom report

More information concerning Audit Log Reports is located on TechNet here:

http://office.microsoft.com/en-us/sharepoint-help/view-audit-log-reports-HA102772739.aspx.

Data Visualization Options. Whilst the data output by these reports are, in the majority, in EXCEL format, there are Microsoft Excel add-ins to help. The usage reports output by SharePoint allows you to then set them out in a dashboard very quickly using a Microsoft tool called POWER BI (provided free of charge for 1GB total usage – at the time of writing this article), or on a charged basis per user. More information is provided at https://powerbi.microsoft.com/en-us/

Office365 Reporting Dashboard. At the time of writing, Microsoft are still finalising the release of the Office365 Dashboard tool. This could be useful in providing statistics across the entirety of an Office 365 provision, however, this is not directly web analytics as statistics concerning all the other components of Office 365 would be displayed, and is too generalistic for this article. Screen shots are available in the presentation. The Office 365 dashboard view would be available only in the Office 365 Admin Center. The dashboard will show trend and aggregate views of the Office 365 services. It will have the capability to drill down into the individual, detailed activity reports.

Step 3 – Work the Business Requirement

Now you will need to factor the actual business requirement and then determine whether features of SharePoint 2013 can be applied, whether a third party product can be applied, or other alternatives. This part is not wholly technical, it is understanding that attention must be paid to ensuring that the requirement can be met, and that once it is met, that the same process can be applied (i.e. repeated) for any other request without having to carry out a significant amount of rework.

First you will require a design statement. A design statement is a number of lines which states who requires the analytics, the focus that needs to be applied, the key requirements of the analytics, including any other key items of information concerning distribution, etc.

Note. Remember to use the Business Gathering article to help you formulate a design statement.

I have given an example of a design statement below concerning a Human Resources site in an organization called Fabrikam Manufacturing.

Scenario: Human Resources department in Fabrikam Manufacturing have a SharePoint site. On that site, they provide forms for holiday, sickness, leave, job applications. As a company rule, all sickness forms must be filled and then uploaded into a document library in the Human Resources site. Human Resources needs a monthly report showing all interaction with the procedure documents on the site, so they can measure and the usage of the documents. They need to see this in chart format along and the report needs to contain those who have accessed the procedure documents.

Let’s work the Human Resources requirement. First, we start by having Human Resources answer these questions.

  • Are the users who need to view the report site owners?
  • Are Human Resources expected to have input to the report?
  • Do Human Resources team members have Excel skills?
  • Does the report have to be generated on a particular date?
  • Does the report have to include rolling statistics?
  • Is it possible that Human Resources will require more charts covering other aspects of the site?
  • Is it possible that Human Resources will require more information about the form usage?
  • Does the report need to be presented as a dashboard on the Human Resources site?

Once these requirements are gathered, we need to be able to map those objectives and prioritise as necessary. This is done so we can then derive what the best solution is to meet the objectives. Again, this is not wholly a technical exercise – it is needed to choose what alternatives should be addressed to determine which is the most suitable in terms of cost, support, usability – in short, most of the factors noted in the questions just covered.

Identify Alternatives

Using value management techniques, you could identify whether SharePoint 2013 meets all the relevant questions (plus some others). Once done, you will be able to see things from a technical and business perspective, giving you an idea on how the solution would operate, using the identified alternatives (e.g. do nothing, adopt SharePoint built in feature, adopt Third Party, get a Developer).

You should visit this page which describes how to apply value management in determining what technology can be used to address business requirements.

Using value management techniques you can then create primary and secondary objectives which will inform you what features are required from the Web Analytics tool. This is further depicted in Figure 1.0 below.

Figure 1.0. Value Management to prioritise and add weighting to each key objective and sub-objectives.

Using the map defined from the question and answer session with the business as the example in Figure 1.0, a matrix showing a number of products, and a test to see if the above requirements can be met by those products. This is shown in Table 1.0 below. Try to see which one you should go for. If you chose Product A well done!

Table 1.0: Value Engineering to identify the best product to meet the requirements.

Note that for each of the alternatives in Table 1.0 it is not simply a case of writing down numbers and hoping for the best. A significant amount of work must take place to ensure that you appraise each of the products. For example, I am going to take a look at one of the alternatives from the table, SharePoint).

Use SharePoint built Web Analytics. From a technical perspective, you could get this data by using, for example, the events obtained from the audit log reports on the site. Specifically those which relate to opening, downloading documents, or other events like checking out etc. This information would have to be exported to Excel 2013, and then from there, could be forwarded to Human Resources, or be pushed back into the Human Resources site and then consumed using Excel services onto a specific page in the Human Resources site. In SharePoint 2013, in the document library where the form is located, the user could highlight the form, and from the ribbon click Popularity. Note that no information concerning list of users is available.

Use SharePoint built in feature. From a business perspective, Human Resources would have to be mindful that there is a human element involved, which is the creation of the chart in Microsoft Excel, the manual provision of the document to a SharePoint site. Of course, this means that the resource would have to be provided to do this work. If they did not create the chart based on the report, then someone would have to get the report to expose the relevant chart. It is also possible therefore, that there will be times when the report could not be produced on time, or is subject to human error in the creation of the chart. Additionally, there is a support overhead, and a skills overhead to consider.

The only real advantage of the SharePoint built in feature from Table 1.0 in the value management exercise is ‘Can be provisioned using built in features’. The disadvantages (which is possibly why Web Analytics is ‘glossed over’) are that people are required, specific skill sets are required, management of the report is required, and the output will need to be ‘tweaked’ to show the data required. In short, it’s all about the actual processes required to get the report to give meaningful data – and that requires resources. Some companies faced with this, even employ analytics personnel to come in, harvest the data and then present back to them the information needed in the form of charts using a mass of business intelligence. And because of all of this, the cost to provision is not cheap. The time taken for the report to be created by possibly more than one person, and the cost of even bringing in consultants may outweigh the value of providing the report. And the key disadvantage is that the requirement is not fulfilled since Human Resources need the list of users who have accessed the procedural document. That is not available unless a separate output is done using the audit reports, and again, that needs to be cleaned up in Excel.

The two links below will provide you with detailed instructions on how to apply Value Management techniques which will help you model out a method of choosing from a list of alternatives.

p

Value Management Part 1 of 3

Understand how Value Management can be used to test business requirements

p

Value Engineering Part 2 of 2

Understand how to determine best alternatives from the Value Management exercise

Step 4 – Wrap Service Delivery into the Web Analytics solution provision

Provision of a web analytics solution is effectively an enterprise SharePoint solution directly linked to proving the premise and sustainability of multiple sites and content. Therefore, the solution needs to be usable, repeatable, supportable and extensible. That means making sure that the solution provided covers most business boundaries and without increasing the relevant work to manage the solution. I wrote an article concerning Usability which will help you understand aspects of the Design, Development, Commonality, Consistency, Tools, Cross Platform, Environmental aspects. Check out this article for more information. There are other concerns. Ensure that the solution is repeatable. That the process for the deployment of the web analytics system can be followed on a platform to platform basis agnostic of version. That the upgrades for the platform can be provisioned and automated. Ensure that the solution is supportable. That there is a knowledge bank available to all relevant audiences (technical and business). That the details of the solution has proper version control applied. That there is a portal that can be visited to launch tickets, get more information, contact the product team. That there is the provision of SLA (Service Level Agreements) that can provide a level of comfort to the customer. That there is adequate provision for the solution to be audited for performance, health checks, sustainment. Finally ensure the solution is extensible. That the solution can be augmented without having to completely redeploy the solution. That the solution is compatible with the version of SharePoint that is in use, and that it is forward and backward compatible. For example, if the solution has been provisioned on a SharePoint 2010 farm that it is compatible with SharePoint 2013, and there are provisions for the same tool to connect backward to SharePoint 2007.

Conclusion

Web Analytics is not new. We are starting to see a major revolution in trying to retain existing customers and research for new customers, and that means using Web Analytics. Company thrive on a cycle of innovation to cash flow. So that means needing to know more about the activity surrounding processes, particularly online. That means needing to know more about online customer interaction. Therefore, there is a big buzz about Web Analytics. 2014 is definitely the year for that revolution, as companies move further into cloud provided services. This article has provided an approach which empowers us with a sustainable and repeatable process of not only determining the kind of Web analytics that will aid user adoption, but also the actual tools needed to produce web analytics going forward.

Data collection and reporting are fundamental and must be accomplished effectively. But these steps in the process should also be efficient. Find ways to minimize the time being spent on these efforts, or delegate to junior staff. Automate as much as possible through using great tools.

The majority of your focus should be on analysing the data, articulating the implications for business and coaching your colleagues through the implementation. What the data means and what your team is supposed to do with it are the priorities. The tighter your analysis and the more you focus on performance indicators that tie to the bottom line, the more successful you’re going to be.

Data for data’s sake isn’t a good investment. Data must drive actions that generate conversions and revenue. Tie your data collection and analysis efforts specifically to your bottom line.

Providing analytics aids service delivery which in turn improves adoption of the solution. This article has given you four steps that will help you provision Web Analytics, irrespective of the technology. You have learned:

  • Step 1: To identify why the site requires analytics, and where
  • Step 2: To understand what is currently available in SharePoint 2013
  • Step 3: To work through the business requirement, prioritise as required and identify alternatives
  • Step 4: To ensure service delivery is wrapped around whatever solution is in place.

Key reference: Microsoft SharePoint 2013: Planning for Adoption and Governance for more information concerning User Adoption importance in Web Analytics and Value Management techniques to identify the best alternatives when choosing a SharePoint solution to meet specific objectives.

Note – click the big arrow to start the presentation, and then click FULLSCREEN in the bottom right to get full benefit. Press ESCAPE to come out of FULLSCREEN at the end.