To ensure the system retrieves accurate distance matrices, monitor routing data quality.
Access response logs
To analyze service usage statistics and routing behavior on the OSS Response Log:
-
Navigate to Configuration > Scheduling > Matrix.
-
Click the Row Menu for the Online Matrix you want to analyze.
-
Select Response Log.
View routing behavior
To determine how routes are generated and if they are optimal, NextGen FSM tracks calculation requests.
Calculation types for requests
Requests can be calculated with and without the internet. The types include:
-
Full Routing (Normal): The online distance matrix completes the calculation.
-
Crow-Fly (Fallback): When the service is unavailable, the system calculates a straight line.
-
Mixed: Cached data is used when a live route temporarily cannot be calculated.
Configure log level
To balance detailed data with system performance, configure the company.fsm.optimization.ossResponseLogLevel parameter with one of these options:
-
ERROR: Logs only "Crow-Fly" responses (total fallback).
-
This is the parameter’s default configuration.
-
-
WARNING: Logs both "Crow-Fly" and "Mixed" responses.
-
TRACE: Logs all responses, including successful "Full Routing" calculations.
Tip: To get a comprehensive view of service quality, use TRACE during initial go-live or troubleshooting phases, then revert to ERROR or WARNING for standard operations.
Access service usage statistics
For Solvice matrices, the system links directly to the external provider’s health metrics. To access these metrics:
-
At the bottom of the OSS Response Log page, click Open Solvice Status Page.
-
The dashboard gives access to the vendor’s service monitor that shows:
-
Service Operationally: The current status of all provider services
-
Uptime: Historical performance data for each service
-
Incidents & Maintenance: Incidents or maintenance that happened
-
-
-
To retrieve real-time service updates, click Check Health Service.
-
Access the current status (Eg. Up, Down, or Degraded) of the service.
-
For each service, see the uptime percentage and any service disruptions.
-
Disruptions are degradations or downtime from the past 180 days.
-
There is a date and duration for each incident.
-
-
Data analysis example
Below is an example of a quarterly report with the TRACE level active:
|
Code |
Description |
Response Type |
Response Count |
|---|---|---|---|
|
SERVICE |
Service Matrix |
Normal |
204,223 |
|
SERVICE |
Service Matrix |
CrowFlight |
14 |
|
RT_SERVICE |
Service Real Time Matrix |
Normal |
60,000 |
|
RT_SERVICE |
Service Real Time Matrix |
Mixed |
12 |
|
RT_SERVICE |
Service Real Time Matrix |
CrowFlight |
3 |
|
NATIVE |
Gisware Matrix |
Normal |
132,000 |