FAQs

You’ve forgotten your password and are unable to sign into Mosaiq Insights. Here’s some suggestions you could try:

• Click the “forgot your password” link on the sign in page (1).

• Enter your email address and click “send reset link to email”.

• Open the email and click on the “reset my password” link. If the “reset my password” link doesn’t work, copy and paste the link in your email into your internet browser window and try again. Follow the instructions on screen.

For security reasons, temporary credentials sent to new users will expire after 72 hours. Attempting to use the link & temporary password after 72 hours will result in a failed login.

• Contact your admin team member and let them know the temporary credentials from your invitation email aren’t working.

• Your admin team member will resend an invitation email for your account (1). For instructions on how to resend an invitation email please refer to the FAQ below “The email link sent to a user won't work”.

• You will receive a new email and temporary credentials to use (2).

• Make sure you login and set up your own password within 72 hours of invitation email receipt.

An invitation email gets sent out as soon as your admin team member creates an account for you in Insights. The email comes from no-reply@beta.mosaiq.co

• If you don’t see an email from no-reply@beta.mosaiq.co, check your junk folder first.

• If it’s still not arrived, contact your admin team member. 

For security reasons, temporary credentials sent to new users will expire after 72 hours. Attempting to use the link & temporary password after 72 hours will result in a failed login. If a new user contacts you advising their temporary credentials won’t work:

If a new user contacts you advising their temporary credentials won’t work:

• Navigate to the “Users” page in Mosaiq Live (1).

• Locate the username that cannot login, they will have a status = “Invite sent” (2).

• Clicking the button will prompt the admin user to confirm they want to resend another temporary password to the selected user, click “Resend” (3).

• The email link is valid for 72 hours

How can there be multiple first and last stops for the same service? How are stops classified?

Some routes have variants, where there is a deviation to the main journey pattern. These could be recorded by the service number having a suffix e.g. A, B, X etc.

The example below clarifies how we define the number of first stops, interim stops and last stops on a service. Service 6369 has 8 stops in one direction. It has two variants: 6369A (variant A) and 6369B (variant B).

• Variant A starts at stop 3 and ends at stop 6. Variant B starts at stop 2 and ends at stop 8. Therefore, service 6369 has three first stops (1, 2 and 3).

• The 6369 has 6 interim stops between it’s first and last stop. This doesn’t change regardless of the variants so long as all the variants fall within the footprint of the main service.

• 6369’s last stop is stop 8. This is true for its variant B also, but variant A ends its journey at stop 6. Therefore, service 6369 has two last stops (6 and 8).

GTFS defines timing points as:

A time point indicates if arrival and departure times for a stop are strictly adhered to by the vehicle or if they are instead approximate and/or interpolated times. This field allows a GTFS producer to provide interpolated stop-times, while indicating that the times are approximate. Valid options are:

• 0 - Times are considered approximate.

• 1 or empty - Times are considered exact.

A service is not judged on every stop being arrived at on time. Instead, certain stops along a route are designated as ‘timing points’. These timing point stops act to measure the interim performance of a service between the first and last stop and are helpful to analyse whether there are consistent issues at certain points of a route.

The first and last stop on a route are always timing points.

All other stops are defined as interim stops.

EOL is how we define, or categorise, on time performance (OTP).

To confirm what the current settings are for your EOL calculations, or to request a change please contact support.

Early - by count and percentage is the number of times the closest matching bus heartbeat was detected early* at this stop, out of the total number of matched instances. 

*Early = The default configuration is 60 seconds or more ahead of schedule.

On time - by count and percentage is the number of times the closest matching bus heartbeat was detected at this stop as neither early nor late, out of the total number of matched instances.

Late - by count and percentage is the number of times the closest matching bus heartbeat was detected late* at this stop out of the total number of matched instances.

*Late = The default configuration is 5 mins 59 seconds or more behind schedule.

Not detected - by count and percentage is the number of times the vehicle was not “seen” at the stop or timing point.

From 4th September 2023

Prior to this date data in the Punctuality On time performance chart will be missing or may look unusual as the chart first started gathering data on 4th of September 2023.

KPI calculations are currently defined once for each customer, and can be broken into 3 different components:

• Inputs - these cannot be customised, but include things like 1st Stop, Timing Points*, Last Stop*.

• Thresholds - these are global values used across a customers network for early, late, & stop geofence sizes.

• Weightings - these determine how much impact an “Input” has on your KPI result.

*Timing Points & Last Stop are combined into a single “input” at this time, but will be split in a future iteration

To confirm what the current settings are for your KPI calculations, or to request a change please contact support.

For more information on how the Punctuality or Reliability KPIs are calculated:

How is the Punctuality KPI calculated?

How is the Reliability KPI calculated?

All buses are equipped with GPS equipment which updates the network on the vehicle’s location. The GPS equipment on each bus pings data back to base every few seconds with its location. We call this data ping a heartbeat.

The heartbeat data is used in multiple ways:

• RTI panels to update passengers on when bus services are due.

• Track how the network is performing to schedule through Mosaiq Insights.

Each bus stop on a network sits at the centre of a geofence. When a bus passes through a geofence, it leaves a trail of heartbeats in the data.

Mosaiq Insights analyses the heartbeat that departs from the stop and compares this to the scheduled time to draw conclusions on whether the bus is early, on-time or late.

What is a geofence?

A geofence is a GPS-defined virtual geographic boundary that enables software to trigger a response when a device enters or leaves a specified area.

We determine dwell time by calculating the difference in the time between the arrival heartbeat and departure heartbeat at a stop.

If there is one or no heartbeats within a stops geofence then dwell time will not be calculated.

From the 14 October 2024

Dwell time for the last stop will be “---” before this date. Total dwell time for a trip no longer includes the last dwell time stop value in the total.

Cancelled trip

• If a trip has been cancelled (whether it happens before, after or during the trip) it counts as a cancellation if no heartbeats have been matched to that trip.

• Cancellations contribute to the no data category within the data quality visualisation.

Part-cancelled trip

• If a trip has been cancelled but has been matched to at least one heartbeat of a trip it will be counted as part cancelled.

• Part cancelled trips contribute to matched trips within the data quality visualisation.

Cancellations appear in the Journeys screen 2-3 hours after the cancellation event in the real time feed is received.

If you wish to provide cancellation data so that it can be displayed in Mosaiq Insights, get in touch

• If you’re in the UK, contact your account manager at Vix Technology

• For everyone else, send us a message here.

We currently support the SIRI-VM & SIRI-ET functional services.

For further information or to technically validate your specific feeds send us a message here.

In some cases, a new feature may not be available within Mosaiq Insights prior to its release. This can result in a data discrepancy if you have selected a timeframe that includes the release date.

The below table captures the dates where certain features within Mosaiq Insignts became available that may result in data discrepancies prior to release.