Overview

How Licensing Works

Our licensing model distinguishes between (a) modelling analysts and (b) infrastructure owners/entities. Modelling analysts are individuals responsible for running Juno Cassandra models, analysing outputs, and preparing reports.

Infrastructure owners or entities are organisations such as town councils, toll agencies, or national government agencies tasked with managing infrastructure such as road networks.

A Juno Cassandra license is purchased and held by the agency/organisation responsible for managing the infrastructure.
Typically, the license is held by town councils, national governments, or toll agencies. Thus, the commercial relationship is between Lonrix and the agency managing the infrastructure.

A modelling analyst using Cassandra to perform work for an agency (e.g. a town council) needs permission from that agency to use its license.
The license holder must notify Lonrix which analyst(s) will be using their license. A computer-specific license is then issued for each nominated analyst.

Note

Note on Elements
Each license granted to an agency has a limit on the number of elements in the infrastructure network. The definition of elements depends on the type of infrastructure being modelled. For example:

  • In a road network, elements are road segments in the model input set
  • In a water network, elements are pipe elements
  • In a bridge network, elements may include trusses, piers, or other structural components

Pricing for licenses is based on the number of such elements to be used in analyses for the licensee’s network.

Modelling analysts may be staff of the license holder, or they may be working for a third-party organisation such as a consulting firm.
In all cases, the analysts must be formally nominated by the licensee.

A licensee may nominate more than one analyst to work under their license (e.g. both an internal staff member and a third-party consultant).

For Clients (Network Owner Agencies)

As a client representing an infrastructure network, you will deal commercially with Lonrix Ltd to set up your annual license.

If your agency already has a license/subscription to the Juno Asset Management System (JunoAMS, also known as ‘JunoViewer’), you do not need to purchase a separate license for Juno Cassandra. Simply inform Lonrix that you wish to use Juno Cassandra, and provide us with the contact details of the person responsible for running your analyses.

If you do not have a license/subscription to Juno AMS, your organisation will need to purchase a license for Juno Cassandra. Please contact Lonrix for a quotation.

For Modelling Analysts (Individuals Using Cassandra)

If you have been asked by an agency to perform modelling for its network using Cassandra, you will deal with Lonrix for technical aspects.

The first step is to ask the license-holding agency to contact Lonrix and confirm that you are authorised to use its license. We will then add you as a user on the system and request the unique identifier for your computer, which you can obtain by running a tool in Cassandra. Next, we will add the client agency name to the list of licenses you can use for your modelling work.

License Check Process

  1. When a modelling analyst logs into Juno Cassandra, a call is made to our API to validate the user’s credentials.

  2. Once we know who the user is, our API retrieves the unique computer identifier on file for that user and compares it to the identifier of the computer being used. This validates both the user and the machine-specific license.

  3. After validation, the system checks which client licenses the analyst has been granted access to. The analyst is presented with a dropdown of the client licenses available.

  4. Once the analyst selects a client, the system determines the number of network elements allowed for that license. This is then used to confirm that the model input set does not exceed the allowed number of elements.

License Use Auditing

Our licensing model is designed to be straightforward and easy to use.
However, from Lonrix’s perspective, there is a critical risk: a dishonest person could attempt to use one client’s license to perform analyses on behalf of other clients who do not have licenses.

To protect Lonrix and license holders against such misuse, our End-User License Agreement (EULA) allows Lonrix to collect usage information from users. This includes information about when users log in and which networks/licenses they are working on. By accepting the EULA, both agencies and modelling analysts agree to this data collection and audit process.

As per our EULA, Lonrix further reserves the right to audit license usage. These audits may be conducted at random or triggered by anomalies detected in user license usage. Audits may include contacting license-holding organisations to confirm that the analyst running Cassandra is legitimately working for them.

Lonrix also employs anomaly-detection methods to identify irregular license use—for example, when an analyst appears to use a single license continuously over a long period, or when the number of elements in input sets varies significantly under a specific license.

Lonrix will take all reasonable care to conduct such audits in a professional and discreet manner. The objective of the audit process is twofold:

  1. to protect license holders against cases where a modelling analyst uses their license for other clients’ networks; and

  2. to protect honest users from unfair competition by those who perform work for unlicensed clients, thereby encroaching on the market for compliant users.