Best practices in IT Operations and process management is no longer an option. Thanks to Sarbanes-Oxley, Payment Card Industry Data Security Standards (PCI DSS), and other legislative, regulatory, and industry initiatives, it is a critical necessity. Despite the maxim "document what you do, do what you document" network and datacenter documentation is too often a siloed artifact created by one team and placed on a shelf or a SharePoint server that is never touched or updated by other teams. Designs are outdated by the time they are finished, if not before. This results in information loss, ineffective handovers, and duplication of effort. 

Living Documentation acts as a unified source of information about your network. At the heart of all aspects of the solution lifecycle, each group uses it to drive their daily interactions with the datacenter and network environment, ensuring that it is an accurate reflection of the current state of your environment and all the changes that have been made.

Our database approach means that your documentation sits at the heart of your network, not on any individual’s laptop or one group’s SharePoint. All team members see the latest information and can easily update those aspects they are responsible for in a fully audit-able manner. 


Living Documentation ensures that you are audit ready with a fully attributed history of the changes to your environment and can see planned changes before they happen. You can see the present, past, and future states of your network. Crash-projects for remediating compliance problems tend to distract an organization, and are hugely expensive in both time and money. LightMesh lets you devote your resources to operational needs rather than compliance.

By unifying your network documentation, design can be informed by your operational performance. Support requests, unplanned upgrades, and other operational challenges can be mapped against the original design, improving the quality and accuracy of your future planning.



LightMesh's unified approach to solution design starts with gathering requirements. A simple interface lets you capture requirements directly into the database, improving information flow and eliminating duplicative effort. Requirement IDs are generated automatically to track them through the design process, map assets against the requirements they fulfill, and ensure a complete solution.


The design phase uses the requirements document as a launching point for a highly detailed design. Specify services, applications, systems, devices, and interfaces to build a solution, either from existing assets or new physical or virtual assets. Customers and support resources can be identified, along with specific configuration details including zones, chassis, communication direction. As specific elements of a solution are added, they are tagged as satisfying particular requirements.


Once a design is completed and approved, LightMesh becomes a full featured build tool. For highly automated cloud services, LightMesh can orchestrate a deployment or integrate with available APIs. For existing datacenters, LightMesh can provide automated configuration scripts for major networking hardware providers. Alternatively, LightMesh can provide detailed build plans and switch configs for staff to follow in a virtual or physical environment.


With a live environment, LightMesh provides full details of every service and application provided to your users. Thanks to the search based interface users are able to quickly identify the hardware involved and the customers affected, regardless of the available information. LightMesh can integrate with existing enterprise ITSM systems, such as BMC Remedy, to surface information from frontline support workers and to provide advanced details that aren’t traditionally available.

Service Design Package

A key part of ITIL, the Service Design Package (SDP) provides a complete specification of a solution design along with verification that all requirements have been satisfied. 

LightMesh automates the creation of SDPs, providing a document that can integrate with your existing processes as well as a physical or logical backup of the designs. 

The Service Design Package can also be used as a building tool for physical data centers, giving full configuration specifications to the installation team.