The Origins of XERRA: Why We Built It
To understand XERRA, you have to understand the problem it was created to solve. We sat down with Mark Wrighton, XERRA Co-Founder, to discuss the development of a purpose-built corridor LiDAR and imagery platform for rail professionals.
Can you introduce yourself and your role in the development of XERRA?
My name is Mark Wrighton. I’m one of the Co-Founders of XERRA, and I work as a Rail SME and Senior Surveyor on our client projects.
My work is deeply rooted in the capture, processing, and application of LiDAR and imagery data to solve a broad range of railway engineering use cases. I’ve always been interested in real-world problem-solving with LiDAR, but the platforms available to visualise and manipulate it weren’t really designed for rail engineering workflows.
That gap is what ultimately led to the development of XERRA.
What motivated the creation of XERRA?
The short answer is frustration, but constructive frustration.
Across the rail industry, vast amounts of LiDAR and imagery data are captured yet those datasets often end up constrained by platforms that:
- Lock data into proprietary formats
- Limit engineering-level measurement capability
- Struggle to adapt to existing and evolving rail industry use cases
- Locked scalability for processing large datasets.
Very early in the development process, we recognised that if we were going to solve these problems properly, we couldn’t simply build another desktop tool. The key development decision was to architect the backend so it could natively process thousands of kilometres of corridor data using cloud compute and scalable database storage. We needed to move away from the limitations of desktop processing entirely.
That meant establishing robust processing engines first, capable of parallel cloud computation and handling corridor-scale datasets, before even thinking about user interface design. The GUI was always going to follow, but the processing architecture had to be right from the beginning.
One of the early catalysts was a clearance project for Queensland Rail between Corinda and Thallon. It was a long regional corridor requiring rollingstock clearance assessments across a large geographic footprint. At the time, most available tools were desktop-based and not scalable, and we had quite tight timeframes to meet. Luckily, we had already commenced development of a cloud-based clearance solution that eventually became XERRA and as they say, there is nothing like a client deadline to really focus the mind.
We were working with command line prompts to spin up cloud computers to process in parallel, with limited visuals to cross-compare to the manual assessments completed. But we were confident in the algorithms, and we always knew that cloud computing and LiDAR are a match made in heaven and that rail networks would need this computational power to truly digitise their work practices.
What happened then?
Everything grew from there. We won a tender to record mobile LiDAR and imagery datasets across the ARTC interstate corridor, and again, the computational power of XERRA was key to delivering clearance reports, DEMs, centrelines and asset inventories. That was quickly followed by a network survey at MTM and V/Line. Those projects brought forward the development of a user interface and map so that rail users at those organisations could visualise and interact with the LiDAR and corridor imagery.
We really designed the user interface from the rail user’s perspective so that the datasets are presented the same way that other railway datasets are presented, i.e. correctly indexed to the corridor using conventions that everyone understands. It was also really important that anyone could use the software without special training because engineering software is often really complex to use, and we wanted to change that.
How is XERRA different from generic point cloud platforms?
The difference starts with intent.
XERRA was not adapted from another industry. It was built from the ground up around rail engineering use cases.
That means:
- Datasets that are properly indexed to the network.
- Measurement tools aligned with rail clearance workflows
- Integration of imagery and LiDAR for virtual corridor access
- A structure that supports repeatable engineering processes
Importantly, XERRA is responsive. Because it was developed by a local team working directly with rail clients, feedback loops are short. Enhancements are driven by real-world project demands, not abstract feature roadmaps.
What benefits have clients seen?
The most immediate benefit is productivity.
Teams can conduct virtual corridor reviews without repeated site visits. They can validate clearances, assess structures, and review asset conditions from anywhere.
There is also a safety benefit; reducing time in live rail environments really matters.
Was XERRA always intended to be a product?
The answer is that XERRA has evolved into a product that our clients love using.
Initially, it was about solving a project need, particularly highlighted by the Corinda to Thallon clearance work. But as more projects were delivered, it became obvious that the same limitations existed across the industry.
What started as a practical solution became a really powerful platform.
Today, XERRA reflects years of rail engineering experience translated into software — built by people who understand the operational, compliance, and technical realities of rail networks.
What’s the broader vision for XERRA?
The broader vision is simple: enable rail professionals to make better decisions, faster, using trusted corridor data. As LiDAR capture becomes more common and networks continue to modernise, the value shifts from collecting data to applying it efficiently.
XERRA exists to make that application seamless.