Flooded Tunnel Inspection: A Procurement Planning Guide

1. Define the inspection result you are buying

A procurement brief should say what the asset owner needs to decide after the inspection. General condition video, a mapped defect register and a measured tunnel cross-section are different deliverables. A system capable of producing one should not automatically be priced or accepted as capable of all three.

For each objective, identify the target condition, required coverage, usable evidence and intended reviewer. For example, a buyer may want suspected concrete spalling linked to a location reference and supported by clear imagery. That is a requirement to discuss, rather than proof that a particular camera or sonar will identify every defect.

Also distinguish an equipment purchase from an inspection service. Ownership of a vehicle does not include an operator, field deployment or an engineering assessment unless those items appear in the offer. Our underwater tunnel inspection application page explains the equipment-selection context.

2. Build an engineering input pack with an assumptions register

Give competing suppliers the same starting information. Use current drawings where available, record their revision and identify gaps. Mark unknown conditions explicitly so a supplier can explain how they affect configuration, price or the decision to proceed.

Keep an assumptions register beside this pack. Record each unresolved item, who will supply the information and which part of the quotation depends on it. A qualified price based on unknown flow should remain distinguishable from a confirmed configuration. The existing tunnel inspection planning checklist provides a downloadable collection sheet; this guide explains how to turn those inputs into purchasing decisions.

3. Separate nominal range from an achievable inspection mission

The official AD-400 product page states a maximum operation distance of 5 km. The supplied manufacturer brochure lists 5.5 km, including a long-tunnel project reference. These figures are different statements from different materials. Neither is a guarantee of suitability for any tunnel.

Do not silently choose the larger figure. Request the current vehicle version, tether and power configuration, basis of the stated range, relevant test record and conditions attached to the proposed mission. Intended route length, tether length and inspected coverage should be identified separately.

A route with bends, constrictions or deposited material requires its own assessment. Procurement should ask what evidence supports the offered configuration under comparable conditions and where its scope ends. Consult the AD-400 equipment page for the published starting specifications, then resolve the deliverable range in the written proposal.

4. Specify the tether, power and recovery package as part of the purchase

A long-distance vehicle needs an integrated field system. The supplied AD-400 brochure describes external umbilical power and shows tether management, a control station and a power-supply system. A vehicle-only line item therefore cannot describe everything needed to support the intended inspection.

Ask for the tether's proposed length, reel or management arrangement, power interfaces, communication equipment and relevant installation constraints. Require a list of buyer-provided facilities. Review how the supplier assessed the proposed route's bends, contact points and drag rather than accepting an unsupported statement that a long cable solves the reach problem.

Recovery is also a procurement responsibility. Request a documented engineering assessment of abnormal events and the included recovery capabilities, equipment and support responsibilities. Features mentioned in a development project should be confirmed for the delivered version. This review should be carried out by the responsible site and engineering teams; a purchasing article cannot supply operating or emergency procedures.

5. Buy usable location references and sensing evidence

Useful observations need a connection to the tunnel. Ask how the proposed system references distance and position, where that reference begins, how sensor records are synchronized and what uncertainty the supplier can substantiate. A feature described as defect localization is not, by itself, a measured accuracy specification.

The appropriate sensing package depends on the question and environment. Ask suppliers to demonstrate that the proposed camera, sonar or measurement arrangement can produce the required evidence in comparable visibility and geometry. Sonar intended to support navigation should not automatically be accepted as a complete condition-measurement package.

Specify sensor models and interfaces rather than a generic optional-sonar label. Request representative exported files, the software needed to open them, license conditions and any processing steps required. Review ownership and access to original records as well as the final report. Our camera versus sonar guide helps frame that discussion without assuming that every instrument has been integrated into every vehicle.

6. Agree acceptance evidence before the order

Acceptance should test the purchased scope, using criteria agreed by the buyer and supplier. Separate checks of the supplied equipment from demonstration of the inspection output. A functional camera check alone does not establish tunnel coverage or the usefulness of a defect register.

The following is an illustrative record structure, not a completed inspection, a manufacturer test result or a proposed accuracy threshold. Actual values and criteria must be agreed for the project.

Ask to review a sample observation entry and navigate from it to the underlying file. Record how missing coverage, unusable imagery or uncertain positions will be identified. Avoid accepting an attractive edited video as the only evidence when the purchase requires traceable findings. Specify who reviews the results and how deviations are documented before acceptance is decided.

7. Compare the complete system cost

No reliable general price can be inferred from a model name or maximum range. The useful comparison is the cost of the package that meets the same stated requirements. Separate one-time equipment costs from services, recurring software charges and buyer-provided facilities.

• Core equipment: vehicle, installed payload, controller, tether, reel, power equipment and transport protection.
• Sensing and data: named instruments, integration, recording, processing software, licenses and report preparation where included.
• Project preparation: configuration review, agreed testing, documentation and any custom engineering.
• Deployment support: training, field attendance, transport coordination and specifically included support.
• Lifecycle items: spare parts, consumables, repair arrangements and ongoing software costs.

State currency, quotation validity, delivery basis and what transport or other destination expenses are included. Avoid treating a lower equipment subtotal as a lower project cost if the other offer includes sensors, tests or support that must otherwise be purchased separately.

For uncertain items, request a priced option or a clearly stated dependency. This preserves a useful comparison without asking suppliers to disguise unresolved engineering as a fixed commitment.

8. Require a quotation scope that identifies responsibility

A reviewable proposal should include an equipment schedule, the assessed application, exclusions, acceptance evidence, delivery milestones and named commercial responsibilities. List standard, optional and custom items separately so a sensor shown in an illustration is not mistaken for supplied equipment.

Require the proposal to identify the seller, equipment manufacturer, test provider and parties responsible for training, warranty assessment and repair coordination. State which activities are included remotely or on site, and which depend on a separate service arrangement. Do not assume an overseas service location exists unless it is identified in the offer.

Finally, connect payment and delivery stages to the agreed deliverables. A buyer should be able to determine what is supplied, what remains conditional and what documents will accompany it. Clarify how configuration changes or newly discovered site information affect scope and price. Keep unresolved questions in a decision log rather than accepting broad promises that cannot be checked.

9. Use the manufacturer tunnel reference as evidence to investigate

The supplied brochure attributes a 5.5 km hydropower diversion-tunnel development project to the manufacturer and China Southern Power Grid. The manufacturer's official project report describes acceptance work, long-distance umbilical engineering and motion, sensing and return-related development. It is a manufacturer reference in China, not an overseas delivery by PanPan Marine.

Use that reference to request the original configuration, relevant records and conditions. Identify which development features are present in the system currently offered and which need additional work. A reference can show that a technical approach has been investigated; it does not transfer every reported result to a different tunnel.

The manufacturer tunnel case page separates the reported project context from questions a buyer should resolve for a comparable application.

10. Send a purchasing brief that can produce a useful response

Start with the asset, intended route, inspection objective, known operating conditions and required outputs. Attach or describe the engineering input pack, then list the unknowns. Indicate whether you need equipment, a service proposal or help deciding between them.

Ask for a preliminary suitability response before a firm configuration where important information is missing. Request a proposal that separates scope, evidence and price, with a clear next step for unresolved engineering questions. This lets both sides identify whether further assessment is justified.

Use the project enquiry page to prepare a structured brief or contact PanPan Marine. A focused enquiry gives the supplier a better basis to respond than a request for the price of a long-range ROV alone.

Frequently asked questions