Skip to main content

Blueprints

Blueprints define the data structures of features that can be installed to a company project, e.g. designs, interfaces, layers, workflows.

They're delivered in two ways: modules and packages. Every company project has the Core modules installed by default. Others are installed according to your organisation's requirements.

info

To discuss the modules and packages installed for your organisation, please contact Support.

Modules​

Modules provide optional extras, such as:

  • additional report types, e.g. Activity by Street, Job Ticket

  • additional functionality, e.g. Finance, Street Works

  • industry data structures, e.g. DEFRA Categories, NSG + NLPG

  • mesh endpoints for integrations, e.g. Enevo, Telensa

  • basic data structures for common service areas, e.g. Highways, Grounds

Packages​

Packages are more sophisticated and built to work together. A package might add data structures for scheduling and carrying out work, or build upon the foundations of an existing module to provide more advanced functionality.

A Solution package is ready-made for a specific service area. Installing one pulls in a whole chain of dependent packages and modules, alongside any data structures of its own. It gives your organisation everything it needs to get started immediately.

Unlike modules, packages are versioned. That makes it easier to update a package in place, without affecting any customisations your organisation builds on top.

Using this reference​

Select a module or package to list the features it installs. Select a feature to see its details.

The Dependencies diagram visualises everything the current module or package relies on. The table below it lists any modules or packages that rely on the current one. Select any of them to move up or down the dependency tree.

If you know the name or code of a module, package or feature, use the search box to go straight there.