Inspection that scales with the risk.
Every order is checked before it is dispatched, and how much checking it gets depends on the product type, the order risk and whether the item is a custom build. What follows is the rules we work to — not a claim about our own quality.
- Functional checks for thrusters, ESCs, cameras, lights, sensors and control units
- Specification, quantity and appearance checks for mechanical parts
- Reinforced inspection for high-risk, critical-function and custom items
- 300 m and 500 m depth classes in the buoyancy range
Inspection grading
- Electrical and control products
- Basic functional check
- Mechanical parts
- Specification, quantity, appearance
- High-risk and custom items
- Reinforced, full inspection where needed
- Simple mechanical parts, mature variants
- Mainly sampling-based
- When it happens
- Before dispatch
- Test data
- Requested per product
Scope is set by product type and order risk, not by a single blanket rule
The four questions a test report has to answer.
These are the concerns buyers in this industry raise most often, and the ones inspection is built around.
Are the parameters real?
Thrust, current, depth class and interface data have to match the datasheet, not the sales page.
Will the batch match the sample?
A sample proves what one unit can do. Batch consistency is a separate question, and it is decided before dispatch.
Does it seal, and does it last?
Sealing reliability and long-run stability are the two failure modes that hurt most in the water.
What happens if something fails?
Inspection is only half the answer; the other half is a clear path for after-sales and a documented responsibility boundary.
Test curves, test conditions, pressure and underwater testing, datasheets, manuals, interface documentation, batch control and published after-sales rules do more for buyer confidence than any description of our team.
Three levels, decided by product type and order risk.
Functional check
Thrusters, ESCs, cameras, lights, sensors and control-class products receive a basic function check before dispatch.
Specification, quantity, appearance
Penetrators, feed-through bolts and comparable mechanical parts are checked mainly for specification, quantity and appearance.
Reinforced or full inspection
Batch projects with high risk, critical function or custom parts are inspected more closely, and fully where the order requires it. Simple mechanical parts and mature variants stay mainly sampling-based.
Depth-rated hardware is judged in conditions that match its use.
Functional, pressure, leakage and dimensional checks run before dispatch. Test data is read together with the conditions it was taken under.
-
Pressure and leak testing Depth-rated hardware is tested under pressure; the relevant test data is requested per product.
-
Depth class Buoyancy materials and floats are supplied in 300 m and 500 m depth classes.
-
Dimensional inspection Specification, quantity and appearance of mechanical parts such as penetrators and feed-through bolts.
-
Electrical function Function check for thrusters, ESCs, cameras, lights, sensors and control units.
-
Test conditions Test data is read with the conditions it was taken under; ask for both together.Ask →
Scope is graded per order: simple mechanical parts and mature variants are mainly sampling-based, while high-risk, critical-function and custom items are reinforced or fully inspected.
.jpg?width=1200)
A running build should not be surprised.
Inspection protects the order; documentation protects the project that depends on it.
- Datasheet
- Manual
- Wiring and interface data
- Test reports
- Batch control
- Version management
- Change notices
How it is handled
- High-risk and critical-function batch orders
- Reinforced or full inspection
- Simple mechanical parts, mature variants
- Mainly sampling-based checks
- Test reports
- Kept in one place — the technical documentation — and requested per product
- Test data
- Read with the conditions it was taken under
- Product revisions
- Handled through version management and change notices
- After-sales rules
- Published, with the responsibility boundary stated in advance
Parameters, documentation and change history are what make a component repeatable
If something is not right.
An exception found before dispatch is handled in a fixed order, so the decision is made on evidence rather than on assumption.
Hold the batch
The affected units are isolated so nothing ships while the question is open.
Engineering judges the cause
The fault is traced to the part, the process or the incoming material.
Re-check or reinforce the check
Affected units are re-tested, and the inspection level for the batch is raised where the risk calls for it.
Rework, remake or re-date
We decide whether the batch is reworked, remade or re-scheduled — and what that does to the delivery date.
Tell you, with a new date
You are told what was found and what the new delivery position is, instead of finding out at dispatch.
Ask for the test data behind the product you are specifying.
Tell us the product, the configuration and the depth class you need. We point you to the documentation and test data that exists for it, and confirm what your order will be checked against before dispatch.
AQUROV · Engineering Store