CLEAR SCOPE. ENGINEERING VALUE. PRACTICAL QUOTE.
Request a Quote for RAUZ Monitoring Intelligence
Tell RAUZ what you are monitoring, what data you have and what engineering decision you need to support. We will define the technical scope before preparing a project-specific quotation.
Request a Quote
A useful quotation starts with a clear engineering scope.
RAUZ does not quote geotechnical monitoring intelligence as a generic hourly service or a standard instrument package. The scope depends on the question to be answered, the quality and volume of available information, the required review frequency, the intended deliverable and the level of technical reliance expected.
Tell us what is being monitored
Identify the asset, project stage, location, construction activity and, where available, the ground or geological conditions relevant to the monitoring problem.
Tell us what information already exists
A quotation becomes more reliable when RAUZ can understand the instrument types, data period, reporting format, trigger criteria, drawings and other project information already available.
Tell us what you need to decide
The most important part of the brief is the engineering question: what do you need RAUZ to review, interpret, diagnose, design or report?
What RAUZ Can Quote
Choose the scope closest to the problem you need solved.
Monitoring Intelligence
Recurring technical review of monitoring data, trends, thresholds, anomalies and engineering significance for a project, site or asset portfolio.
Independent Monitoring Review
Independent assessment of monitoring plans, baselines, data quality, trigger logic, monitoring reports and observed movement.
InSAR Ground Motion Intelligence
Geotechnical interpretation of satellite-derived movement for screening, historical assessment, ongoing review or comparison with field monitoring.
Monitoring Design & Strategy
Monitoring philosophy, instrument selection, layout concepts, baseline requirements, frequency, trigger frameworks and reporting requirements.
Monitoring Data Diagnostics
Focused technical investigation of unusual movement, inconsistent datasets, questionable trigger exceedances, instrument behaviour or unexplained trends.
Automated Monitoring Reporting
Technology-enabled workflows for data checks, charts, rates, thresholds, reporting tables and engineer-reviewed technical commentary.
What We Need
Send enough information to understand the work — not every file on day one.
The list below is a practical guide. Not every item is required for every enquiry, and RAUZ does not ask clients to disclose sensitive project information before a suitable confidentiality route is agreed.
- Project / asset name or anonymised reference
- Country and project location
- Asset type and project stage
- Relevant geology or ground conditions if available
- Excavation, tunnelling, loading or other current activity
- Instrument types and approximate quantities
- Monitoring period and reading frequency
- Existing trigger / alert criteria
- Sample dataset or recent monitoring report
- Relevant drawings, sections or monitoring layout
- Required deliverable and review frequency
- Target date or procurement deadline
Scope Drivers
What changes the effort behind a quotation?
Two projects with the same instrument type can require very different levels of engineering work. RAUZ therefore prices the review scope rather than using a single public rate for every monitoring problem.
Data volume & structure
Number of instruments, monitoring duration, reading frequency, file formats, missing data, metadata quality and whether information is already organised.
Engineering complexity
Ground conditions, asset sensitivity, construction sequence, groundwater behaviour, multiple movement mechanisms and the need to correlate different datasets.
Review frequency
One-off review, weekly review, monthly monitoring intelligence, event-driven diagnostics or portfolio-level recurring assessment.
Deliverable
Technical memorandum, independent review report, monitoring design note, diagnostic assessment, dashboard input, presentation or recurring reporting package.
Turnaround & response requirement
Normal planned review differs from urgent incident support, accelerated procurement deadlines or work requiring defined response windows.
Reliance & contractual responsibility
The quotation must distinguish advisory analysis from deliverables intended for formal contractual, regulatory or third-party reliance.
Commercial Models
Different monitoring questions suit different commercial structures.
Defined Technical Review
Suitable for an independent report review, monitoring diagnostic, trigger assessment or focused technical question with a clearly bounded deliverable.
Monitoring Intelligence
Suitable where data arrives continuously and the client needs scheduled engineering review, interpretation and reporting over a defined period.
Design & Strategy Scope
Suitable for monitoring plans, trigger frameworks, data-management requirements, tender inputs and other defined pre-construction or project-stage deliverables.
Multi-Asset Review
Suitable where an owner or operator wants a consistent monitoring-intelligence framework across multiple sites, corridors or critical assets.
Quotation Process
From enquiry to a defined scope.
Initial brief
Describe the project, existing monitoring information and the engineering question you need RAUZ to address.
Scope check
RAUZ identifies missing information, technical assumptions, scope boundaries and whether the requested output can reasonably be delivered remotely.
Quotation
The commercial proposal defines deliverables, assumptions, programme, exclusions, information required from the client and the proposed fee structure.
Data onboarding
After appointment, project information is transferred through the agreed route and the technical review or recurring workflow begins.
Quote Brief Builder
Prepare the information RAUZ needs for a quotation.
Complete the fields below and select “Prepare Quote Email”. The page will open your own email application with the information arranged into a structured enquiry. No project files are uploaded through this page.
Scope Boundaries
Clarify responsibility before the quotation becomes a contract.
RAUZ’s remote-first model can work with client-owned systems and third-party monitoring contractors, but the quotation should state clearly what RAUZ is and is not responsible for.
Field data responsibility
Identify who installs, maintains and reads instruments; who validates survey control; and who provides calibration, metadata and instrument-status information.
Engineering reliance
Distinguish advisory interpretation from formal design certification, statutory approval, Engineer-of-Record duties or other jurisdiction-specific responsibilities.
Data, confidentiality & IP
Define ownership of raw data, derived analyses, software outputs, confidential project information and any project-specific methods or developments.
FAQs
Before requesting a quotation.
Can RAUZ quote without receiving the full project dataset?
Does RAUZ provide fixed public prices?
Can I request a quote for a one-off abnormal reading or trigger exceedance?
Can RAUZ quote for monthly monitoring review?
Can RAUZ quote if another company installed the instruments?
Can RAUZ provide a quotation for InSAR work?
What if the project requires local statutory sign-off?
Request Your Quote
Send the project question first. RAUZ will help define the scope.
For a quotation, send a concise project brief, representative monitoring information and the engineering outcome you need. If the project is still early or the correct RAUZ service is unclear, start with a technical discussion rather than guessing the scope.