Who is this article for?

IT Personnel who want to learn to integrate Lucidity with Sharepoint.

No elevated permissions are required.

Many Lucidity clients use Sharepoint side by side with Lucidity. Sharepoint is best viewed as a platform, rather than a software application, and offers useful day to day tools and collaboration opportunities for an organisation as part of the broader Microsoft ecosystem. There are a couple of very simple and useful integration opportunities between Sharepoint and Lucidity.

1. Launching Lucidity from Sharepoint
2. Sharing Sharepoint documents within Lucidity
3. Other considerations when using Sharepoint
4. Further reading

1. Launching Lucidity from Sharepoint

In order to use Lucidity as your Risk, HSEQ and Digital Forms/Mobility solution, it is useful to insert a link into Sharepoint on an appropriate page to launch Lucidity. Whether the link is branded with any reference to Lucidity or not is a business decision. Your instance of Lucidity will be company branded, so there is complete freedom.

If Single Sign On (SSO) is enabled, then the user will not need to re-authenticate after following the link to open Lucidity. Note that SSO is available on the Lucidity App as well as the desktop (browser). Both Azure AD and ADFS are supported.

2. Sharing Sharepoint documents within Lucidity

Lucidity Intranet offers flexible document sharing for your Integrated Management System (IMS), regardless of storage location. Its process-oriented pages allow administrators to link documents from various sources, including Sharepoint repositories.
This flexibility preserves existing document management processes while providing stakeholders easy access to current versions through Lucidity. The system seamlessly integrates documents and electronic forms from multiple sources into a single, coherent interface, streamlining information access and management.

3. Other considerations when using Sharepoint

1. Platform, not solution
   • Requires a software developer for HSEQ functionality.
   • Needs a project sponsor for design and user acceptance.
2. Mobility challenges
   • No specific HSEQ mobile functionality out-of-the-box.
   • Requires developer skills for implementation and maintenance.
   • Offline functionality adds complexity.
3. Access issues
   • Remote access not guaranteed.
   • Contractor and customer access may be limited.
   • Licensing considerations for non-employees.
4. Limited training management
   • Ineffective for managing training and inductions.
   • Lacks automated workflows for Training Needs Analysis (TNA) and e-learning.
   • Difficult to achieve features of a modern Learning Management System (LMS).
5. Not an ecosystem
   • Customisations are client-specific.
   • Lack of shared features and improvements across users.
   • Risk of stagnation without ongoing development.
6. Long-term sustainability concerns
   • Dependence on initial developers and sponsors.
   • Potential loss of organisational knowledge over time.
   • Risk of needing to replace with a specific solution after a few years.

In summary, while Sharepoint offers document management and collaboration features, it requires significant customisation and ongoing maintenance to serve as an effective HSEQ solution. Organisations should carefully consider these limitations and the long-term implications before implementing Sharepoint for HSEQ purposes.