Inspection mapping // automation

Data in. Maps out.

Ray turns structured inspection spreadsheets into validated, Surfer-ready outputs, SRF, PNG, DAT and summary artifacts, through one visible pipeline from intake to packaging.

Book a demo ▸▸ See pricing
ray / pipelineLIVE
Excel input
structured templates
in
Validation
sheet structure checks
pass
Surfer-ready processing
consistent configuration
run
Output generation
files + summaries
out
Outputs SRFPNGDATQA SUMMARY
Workflow snapshot · one run, one clear sequence
01 // The run

One run, one clear sequence

Ray keeps every stage visible from intake through packaging, so teams can review quickly and hand off with confidence.

Gate

Validated input

Every sheet is checked against a known structure before processing, so broken templates stop at the door, not downstream.

Standard

Consistent outputs

A single Surfer-ready configuration drives every run, so the same input always produces the same shape of result.

Trace

Review artifacts

Logs, summaries and a combined QA report ship with the maps, so reviewers can audit a run without rebuilding it.

Built for engineering teams, inspection contractors, and infrastructure asset owners who need a repeatable pipeline from field input to Surfer-ready deliverables. A practical pipeline designed for repeatable, robust and accurate outputs.

See pricing ▸
02 // How Ray works

From spreadsheet to delivered map

Four stages carry your data from intake to packaging. Ray runs each one the same way, every time, and records what happened so the result is easy to trust.

01

Excel input

Start from structured templates that define the faces and dimensions Ray expects.

02

Validation

Sheet structure is checked up front, so problems surface before any processing runs.

03

Surfer-ready processing

A consistent configuration runs each face, capturing validation as it goes.

04

Output generation

SRF, PNG and DAT files are written alongside summaries, grouped and traceable.

STEP 01

Generate the template

  • Define the faces a job will cover and any custom dimensions.
  • Ray emits a structured workbook that downstream stages can rely on.
  • One input contract, shared across every run.
ray / template
ray ▸ template --new faces F1 F2 F3 F4 dims width=auto height=auto sheet intake · validation · output ✓ template.xlsx generated
STEP 02

Load data and choose outputs

  • Drop your filled template in and pick the formats you need.
  • Ray verifies each face is present and accounted for.
  • Selection is explicit, so a run only produces what you asked for.
ray / load
ray ▸ load data.xlsx ✓ sheet structure OK (4 faces) outputs [x] SRF [x] PNG [x] DAT faces verified 4/4
STEP 03

Run per-face processing

  • Each face is processed under the same configuration.
  • Ray logs a clear pass or fail and captures the validation detail.
  • Issues are flagged in place, not buried in a folder.
ray / run --per-face
ray ▸ run --per-face F1 ✓ pass grid 240×180 F2 ✓ pass grid 240×180 F3 ✗ fail gap detected → flagged F4 ✓ pass grid 240×180 validation captured → run.log
STEP 04

Review output links

  • Results are grouped by face for fast scanning.
  • Direct file access, no hunting through nested folders.
  • Open any artifact straight from the run view.
ray / outputs
F1/ srf png dat F2/ srf png dat F3/ srf png dat F4/ srf png dat open ▸ direct file access
STEP 05

Confirm the full per-face package

  • Every face ships a complete, predictable artifact set.
  • Paths are traceable, so a result maps back to its source.
  • Nothing is implicit, the package is the contract.
ray / package
package/F1/ ├ F1.srf ├ F1.png ├ F1.dat └ F1-summary.txt ✓ paths traceable
STEP 06

Generate combined face outputs

  • Ray stitches the per-face results into a combined surface.
  • Edge conditions are surfaced as warnings, then resolved.
  • The combined output is built from the same validated pieces.
ray / combine
ray ▸ combine --faces all stitch F1 + F2 + F3 + F4 ⚠ F3 edge overlap → resolved ✓ combined.srf written
STEP 07

Inspect the combined QA report

  • An executive summary covers the whole run at a glance.
  • Parameters are documented, so settings are never a mystery.
  • One report a reviewer can sign off on.
ray / qa-report
QA REPORT // combined summary 4 faces · 0 errors params contour=0.5 grid=240 warnings 1 resolved ✓ reviewer ready
STEP 08

Deliver the final combined map

  • Cross-face visibility in a single, coherent deliverable.
  • Presentation-ready output for handoff and review.
  • The same run, packaged for the people who need it.
ray / deliver
ray ▸ deliver --combined file combined-map.png ✓ cross-face visibility ✓ presentation-ready
03 // The shift

From manual handoffs to a reliable production flow

The work does not change. The variance does. Ray replaces ad-hoc steps with a defined run, so the same process holds across people, jobs and reporting periods.

Where teams lose time
  • Template mismatches that break downstream processes.
  • Repeated manual checks before every run.
  • Inconsistent export setup from one job to the next.
  • Hard-to-audit output folders no one wants to open.
How Ray solves it
  • Structured Excel input contracts, checked on intake.
  • Automated validation gates before processing starts.
  • Standardized Surfer-ready setup on every run.
  • Consistent output packaging with traceable paths.
04 // Capabilities

Key capabilities

Designed to remove routine overhead while keeping outputs clear and reviewable.

Automated face processing

Every face runs under one configuration, with pass or fail logged and validation captured as it goes.

PER-FACE · LOGGED

Combined map outputs

Per-face results stitch into a single combined surface, with edge conditions surfaced and resolved.

STITCHED · COHERENT

QA-friendly summaries

An executive summary and documented parameters ship with the maps, so reviews do not start from scratch.

SUMMARY · PARAMS

Repeatable setup

The same input contract and configuration drive every run, so results stay consistent across cycles.

CONSISTENT · REUSABLE
05 // Philosophy

Built for consistency and transparent process control

Ray focuses on reducing variance in setup and output, so teams can spend more time on review, interpretation and decisions.

Consistency signals

A fixed input contract and a single processing configuration mean the same data always produces the same shape of result. When something changes, it is a deliberate change, not drift, and it shows up clearly in the run record.

Traceable workflow

Every stage leaves a mark, validation logs, per-face packages, a combined QA report, so a finished map can always be traced back to the input that produced it. Reviewers audit the run, they do not reconstruct it.

06 // Use cases

Where Ray is typically deployed

Teams reach for Ray when the mapping work is repetitive, the standards matter, and the handoff has to hold up.

Engineering teams

Standardize repeat mapping runs so the output is the same regardless of who kicks off the job.

STANDARDIZE

Inspection contractors

Reduce handoff variability between field data and deliverable, so clients get the same quality each time.

REDUCE VARIANCE

Asset owners

Improve the QA review cadence with a consistent report and a record that is easy to trust.

QA CADENCE
07 // Pricing

Licensing built around your scope

Start with a guided evaluation, subscribe per branch once Ray fits, or scope a multi-branch rollout. Pricing is in euros and billed through Stripe.

Demo
// Evaluation
€0
Pre-purchase Ray software evaluation
  • ✓Ray product-fit call focused on your workflow and licensing scope
  • ✓Input template compatibility check for your dataset structure
  • ✓Guided sample run to validate Ray processing behavior
  • ✓Preview of standard outputs: DAT, GRD, SRF, PNG and PDF
  • ✓Next step after fit: Standard or Custom subscription
Request demo
Recommended
Standard
// Per branch / location
€1000/month
One named branch subscription
  • ✓One named branch or location, up to two authorized computers (seats)
  • ✓Full Ray desktop workflow for DAT, GRD, SRF, PNG and PDF
  • ✓Onboarding for template validation and output packaging alignment
  • ✓Email support for licensing and operation, first response within 2 business days
  • ✓Support window 10:00 AM to 7:00 PM Eastern European Time (EET/EEST)
  • ✓Recurring monthly billing through Stripe checkout
Get Standard plan ▸▸
Enterprise
// Build your own
Customquote-confirmed
Total contract range, quote-confirmed
  • ✓Typical total contract range: €1,000 to €5,000 per month
  • ✓Multi-branch commercial model and branch rollout planning
  • ✓Custom seat volumes and license policy requirements
  • ✓Onboarding, deployment and process alignment scope
  • ✓Support-level customization and response model options
  • ✓Jurisdiction, currency, tax and procurement-specific terms
Build your own

Final amount and currency are confirmed in a private quote and at checkout.

08 // FAQ

Questions, answered

Practical answers teams ask before rollout.

What Excel format does Ray require?+
Ray works from a structured template that defines the faces and dimensions for a job. You generate the template once, fill it with your inspection data, and Ray validates the sheet structure on intake. If the structure does not match, the run stops before any processing, so issues are caught early.
What output file types does Ray generate?+
Each run produces Surfer-ready outputs, SRF, PNG and DAT files, grouped per face, plus summary artifacts. You choose which formats to generate when you load the data, so a run only produces what you asked for.
Does Ray support a combined map deliverable?+
Yes. After per-face processing, Ray stitches the validated faces into a single combined surface, surfaces any edge conditions as warnings, and produces a presentation-ready combined map alongside a combined QA report.
What role does validation play in QA?+
Validation is the gate before processing. Ray checks sheet structure up front and logs a clear pass or fail per face during the run. That validation detail flows into the QA report, so reviewers can see what was checked without rerunning the job.
Is Ray suitable for repeat cycles?+
That is the point. A fixed input contract and a single processing configuration mean repeat runs stay consistent. The same template and setup carry from one cycle to the next, which is what keeps results comparable over time.
Can we review Ray before rolling it out?+
Yes. Bring a sample template and a target deliverable set, and we will walk through how a real run maps into Ray's structure, from intake and validation through to the combined map and QA report.
How do we get started?+
Book a demo and bring an example of your current workflow. We will define the input contract and output requirements with you, then confirm the run structure so your first cycle goes live with a repeatable setup in place.
09 // Evaluate

Ready to evaluate Ray?

See how your current workflow maps into a repeatable run structure. Bring a sample template and target deliverable set, and we will walk through how Ray can fit your process.

Book a demo ▸▸ Contact sales