Step 01
Generate the template
Define each face and create the structured Excel file that anchors the run.
- Create as many faces as you want.
- Each face can have custom dimensions and spacing.
- Template file creation is confirmed in the results panel.
Data in. Maps out.
Ray transforms structured inspection spreadsheets into validated, Surfer-ready outputs with consistent SRF, PNG, and DAT delivery.
Built for engineering teams, inspection contractors, and infrastructure asset owners who need a repeatable pipeline from field input to Surfer-ready deliverables.
How Ray Works
A practical pipeline designed for repeatable, robust & accurate outputs.
01
Excel Input
Teams start with structured templates for inspection values, coordinates, and metadata.
02
Validation
Ray checks sheet structure and required fields before processing begins.
03
Surfer-Ready Processing
Validated data is prepared with consistent configuration for map generation.
04
Output Generation
Deliverables are generated as SRF, PNG, DAT, plus summary files for QA and reporting.
Step 02
Load data and choose outputs
Import the completed template with site data, chose your formats, and start processing.
- Output types can be selected per run.
- Detected faces are verified before map generation begins.
- You can chose any combination of outputs.
- The current run log is saved for transparency and audit purposes.
Step 03
Run per-face processing
Ray executes each face and logs pass/fail outcomes with run context for QA review.
- Project metadata stays attached to the run.
- Face-level validation status is captured in one results feed.
- Per face information about the data is given, and validated.
Step 04
Review output links
Open generated files directly from the results pane to speed up operator checks.
- Contour PNG, QA PDF, SRF, and DAT links are grouped by face.
- Teams can jump from run summary to file review immediately.
- This batch function can potentially save hundreds of hours of manual work.
Step 05
Confirm full per-face package
Validate that each face produced its complete export set in the expected folder structure.
- All generated artifacts are listed in sequence.
- File paths remain traceable for handoff and audit.
- Each file path is clickable, so you can easily navigate the outputs.
Step 06
Generate combined face outputs
Switch to combined mode to stitch selected faces into one aggregate output set.
- Ray reports geometry mismatches and stitching warnings.
- Combined PNG, PDF, SRF, and DAT files are exported together.
- Missing data or dangerous levels of corrosion are also highlighted.
Step 07
Inspect the combined QA report
Use the auto-generated report to review validation outcomes, data quality, and grid settings.
- Executive summary highlights action-needed conditions.
- Measurement and gridding parameters are documented for reviewers.
- The QA report is easily customizable, just contact support and set up a meeting.
Step 08
Deliver the final combined map
Publish the unified contour result for engineering interpretation and decision workflows.
- Cross-face transitions are visible in one map surface.
- The final output is ready for presentation and technical signoff.
- You can still fully manually edit the .SRF file in Surfer.
From manual handoffs to a reliable production flow.
Many teams still rely on fragmented spreadsheets, manual validation, and ad hoc output setup. Ray brings those steps into one controlled process.
Where teams lose time
- Template mismatches that break downstream processing.
- Repeated manual checks before every run.
- Inconsistent export setup between operators and projects.
- Hard-to-audit output folders during QA review.
How Ray solves it
- Structured Excel input contracts for predictable ingestion.
- Automated validation before expensive processing steps.
- Standardized Surfer-ready setup and run configuration.
- Consistent output packaging with summary context.
Key Capabilities
Designed to remove routine overhead while keeping outputs clear and reviewable.
Automated Face Processing
Run repeated face-level workflows with less manual setup from project to project.
Combined Map Outputs
Generate combined views for teams that need whole-asset context, not only single slices.
QA-Friendly Summaries
Reviewers can quickly confirm what was processed, what passed validation, and what was produced.
Repeatable Setup
Standardized run logic helps teams maintain consistency across operators and project cycles.
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
Standardized templates, validation gates, and output structures support repeatable execution.
Traceable workflow
Each run is easier to inspect because pipeline stages and generated outputs follow the same pattern.
Use Cases
Where Ray is typically deployed.
Engineering Teams
Standardize repeat mapping runs
Use one template and one run structure across recurring asset inspections.
Inspection Contractors
Reduce handoff variability
Deliver consistent output packages across clients and project scopes.
Asset Owners
Improve QA review cadence
Give internal reviewers predictable summaries and map exports for faster signoff.
Frequently Asked Questions
Practical answers teams ask before rollout.
Does Ray require a specific Excel format?
Input requirements
Ray works with defined template structures. Validation checks highlight missing or mismatched fields before processing.
What output files does Ray generate?
Output formats
Typical outputs include SRF, PNG, DAT, and run summaries. Actual output sets can be configured to project needs.
Can Ray support combined map deliverables?
Combined workflows
Yes. Ray can produce combined map outputs for teams that need aggregate visibility across multiple faces or segments.
How does validation help QA teams?
Quality control
Validation surfaces issues before processing, reducing avoidable reruns and giving QA a clearer run history.
Is Ray suited for repeat project cycles?
Repeatability
Ray is designed for repeat operations where consistent setup and output packaging matter across many runs.
Can we review Ray output structure before rollout?
Pilot workflow
Yes. A short pilot can confirm template compatibility, validation behavior, and output organization with your team.
How do we start with Ray?
Getting started
Book a demo to review your current workflow, sample inputs, and the output package your stakeholders need.
Ready To Evaluate Ray?
See how your current workflow maps into a repeatable run structure.
Bring a sample template and target deliverable set. We will walk through how Ray can fit your process.