For Modelling Analysts

Using Juno Cassandra Under a Client’s Licence

Juno Cassandra licences are held by infrastructure-owning organisations — councils, toll agencies, or national government agencies.

If you are asked to perform modelling for one of them, you must be formally nominated by that organisation before we can give you access to its project.

Getting Set Up

  1. Client approval — The licence-holding organisation contacts Lonrix to confirm that you are authorised, and says whether you need modeller or stakeholder access.
  2. Registration — Lonrix creates your account and grants it access to that client’s project.
  3. First sign-in — You set up two-factor authentication and accept the End-User Licence Agreement.
  4. Work — You sign in, choose the client project you are working on, and start.

That is the whole process. There is nothing to install, no licence key to enter, and no computer identifier to send us.

Note

If you used the earlier desktop version: your access is no longer tied to a registered computer. You can work from your office machine, a laptop or a client’s meeting room without telling us in advance.

Working for More Than One Client

You have one account, and it can hold access to as many client projects as have authorised you. When you sign in you choose which client you are working in, and everything you then do — files, runs, outputs — belongs to that client alone.

Each of those clients must have authorised you separately. Access to one client’s project never implies access to another’s, and you may not use one client’s licence to do work for somebody else.

Your Access Level

Your account carries one of two levels for each project:

  • Modeller — upload and change inputs, tune the setup, run models, publish results
  • Stakeholder — read-only access to the project and its results

The client decides which one you get. If you need modeller access and have stakeholder access, ask the client to confirm the change with Lonrix.

Licence Limits

Each client licence has a limit on the number of elements in the network model. For example:

  • Road segments (road networks)
  • Pipe elements (water networks)
  • Structural components such as trusses or piers (bridge networks)

Your analyses must stay within the limit of the client licence you are working under. The check happens when a run starts; a run over the limit does not proceed.

Building or Maintaining a Domain Model

If your client’s licence is in place, you may also build, debug, publish and maintain the domain model itself — the engineering logic behind the forecasts. There is no extra licence for this, and the Domain Model Assistant that supports the work is free and public.

What you supply yourself is a subscription to an AI coding assistant that runs inside Visual Studio Code. That is a subscription you hold directly with the provider; Lonrix neither procures nor pays for it. See Training for the module that covers this work.

Compliance and Auditing

By using Juno Cassandra you accept the End-User Licence Agreement, which allows Lonrix to:

  • Record when you sign in, which client licence you work under, and what you run
  • Audit usage, randomly or if anomalies are detected
  • Confirm with client organisations that you are legitimately working under their licence

These safeguards protect honest analysts as much as they protect licence holders — they are what stops an unlicensed competitor undercutting you on work you are properly licensed to do.