Licenses

The Meridian Explorer licenses are:

• Explorer Server License (part number includes M--EXS). One is required for each Meridian Enterprise server that is synchronized with a Meridian Explorer repository (excluding the Meridian Enterprise Data Library).

• For named licensing, customers use the Explorer Base, Standard, and Plus client licenses (part numbers include MN-EXB, MN-EXC, MN-EXP). Each license type enables specific client functionality:

  • Explorer Base: All basic functionality such as:

    • Documents view

    • Collections view

    • General, Properties, Revisions, References, and Project Copies property pages

  • Explorer Standard: All functionality of Explorer Base plus:

    • Projects view

    • Feedback property page

    • Packages property page and package import/export

    • Dashboard page

  • Explorer Plus: All functionality of Explorer Standard plus:

    • Tags view

    • Tag search

    • Related Tags property page

• For concurrent licensing, one M--EXC license is required for every concurrent Meridian Explorer user and the license remains claimed for the duration of the browser session.

  • Meridian Explorer client licenses will be substituted automatically by a PowerUser client (M--PUR) license (if available) when a user opens the PowerUser client while one of the licenses are claimed. The licenses are not substituted in reverse. That is, when a user has claimed a PowerUser license and opens the Meridian Explorer client, no additional Meridian Explorer license is claimed. The PowerUser license entitles the user to work in Meridian Explorer and the PowerUser license remains claimed. License substitution does not occur between concurrent and named licenses.

  • PowerUser client (M--PUR, equivalent to M--EXP) licenses will be claimed by Meridian Explorer users if no Meridian Explorer user licenses are available.

  • Client licenses expire after 30 minutes of inactivity. This is not configurable.

The Publisher system link licenses are:

• Windows file system link (part number includes FS-PUS) for publishing to or from a Windows file system.

• SharePoint system link (part number includes M--PSP) for publishing to or from a SharePoint library.

• Project Portal (formerly Kronodoc) system link (part number includes K--PUS) for publishing to or from a Accruent Project Portal or Kronodoc workspace.

  All system link licenses include the use of:

  • Meridian Enterprise vault extensions

  • Client applications to support publishing from that system

The Publisher rendering module licenses are:

• Native Application rendering module (part number includes M--PNR) for rendering through AutoCAD, Autodesk Inventor, Microsoft Office, MicroStation, SolidWorks, or the Custom rendering module.

• eSignature module (part number includes M--PES) for applying watermarks, electronic signatures, and signature pages to renditions.

• PDF Merge rendering module (part number includes M--PMD) for merging renditions into a single Adobe PDF file.

When configured in a cluster, all Meridian Enterprise Server nodes (primary and secondary) require their own system link and rendering module licenses for the jobs that they process.

To obtain additional licenses, contact your Accruent Partner or Accruent. For more information about registering licenses in the Accruent License Server, see Register Licenses - Administrator.