LX workspace FAQ
1 What geographic area does this LX workspace cover?
This LX workspace covers France and includes 100% of the active road–rail level crossings (LX) in the national network. The crossings and sites you see are therefore based on real assets.
2 Which roads and emitters are analysed?
On the road side, the analysis focuses on the network that matters most for access: motorways and trunk roads, motorway access roads, and primary, secondary and tertiary roads. Very local road classes — such as service, residential or unclassified roads — are not used as primary carriers for access in this workspace.
On the emitter side, the workspace concentrates on operationally sensitive emitters of traffic-at-risk: Seveso-type industrial sites, hazardous logistics hubs and depots, and public-service sites such as schools and elderly care homes.
3 Which indicators and metrics are shown?
Two key indicators are exposed directly in this workspace: a single-point-of-failure (SPOF) flag for crossings where emitters have no alternative, and a prohibitive detour flag for crossings where avoiding the LX would require costly detours.
Behind these indicators, SAMRoute computes 100+ summary metrics per LX related to access patterns and situational awareness. These metrics can be explored, sorted and reviewed in dedicated views.
4 How often is the data updated?
In this concept workspace, data is not updated continuously. It is refreshed manually during development cycles or when new data sources are integrated.
For a commercial deployment, the same approach would be set up with regular data updates (for example weekly or monthly), and, where relevant, near-live updates driven by machine-to-machine notifications. This will ensure that changes in the data are reflected in the indicators.
5 What are the main limitations of this workspace?
This LX workspace is a concept demonstrator that shows how portfolio-scale analysis and deep dives can work. The UX is intentionally simple and based on our own projection of the use case, i.e., to find LX where emitters of traffic-at-risk are functionally dependent.
However, it does not yet include the full range of enterprise features that would be specified with a client, e.g., it does not expose full export capabilities, fine-grained access and perimeter control, or enterprise-grade notification and workflow features. These elements are part of the discussion for a dedicated workspace on your perimeter.
6 Who can access this LX workspace?
Access to this workspace is controlled. Users sign in with a password or with a one-time passcodes (OTP) sent to their email.
Once connected, users can invite collaborators by email directly from the interface (invite panel in the lower-right corner), so that COMEX, operations teams and other stakeholders can review the same maps and indicators.
7 Where is the workspace hosted?
The LX workspace is hosted on OVHcloud infrastructure in the North of France, as well as on our own infrastructure in Brittany, in the West of France.
8 What should we do if we want a similar workspace?
If this LX workspace matches the type of questions you are asking, the next step is simply to reach out. We can discuss your perimeter, your emitters of traffic-at-risk and your constraints, and see what a tailored SAMRoute workspace could look like for your organisation.