Robotic storage tank inspection for bottom, shell and roof assets
Connect the right PetroBot robot to the tank inspection job: ITIS Rover for in-service tank bottom inspection and MagRover for shell, roof and external UT work that supports API 653 inspection programs.
Connected robots
ITIS Rover and MagRover cover complementary tank inspection workflows for API 653 inspection planning: in-service floor inspection inside operational storage tanks and magnetic UT inspection on external tank surfaces.
ITIS Rover
Used for in-service tank bottom inspection where the goal is to inspect operational storage tanks without shutdown.
MagRover
Used for magnetic climbing inspection on tank shells, roofs and other accessible ferromagnetic tank surfaces.
Asset types
- Storage tanks
- Tank bottom plates
- Tank shells
- Tank roofs
- Ferromagnetic tank surfaces
Inspection deliverables
- Tank bottom inspection observations
- UT thickness readings where applicable
- Visual inspection records
- Tank condition report for API 653 inspection and maintenance planning
Next step
Share asset type, diameter or dimensions, access constraints, temperature, coating condition and inspection objective so PetroBot can confirm robotic suitability.
Contact PetroBotFrequently asked questions
Which PetroBot robot is used for tank inspection?
ITIS Rover is used for in-service tank bottom inspection, while MagRover is used for magnetic climbing inspection on tank shells, roofs and other suitable external tank surfaces.
Can tanks be inspected without shutdown?
For suitable storage tanks, ITIS Rover supports in-service tank bottom inspection workflows that reduce shutdown dependency. Suitability depends on product, access, sludge, obstacles and safety constraints.
What tank inspection data can PetroBot deliver?
Typical deliverables include visual evidence, UT readings where applicable, mapped observations and an inspection report that supports maintenance and integrity planning.
Does PetroBot support API 653 tank inspection programs?
PetroBot robotic inspection data can support API 653 inspection planning, condition assessment and repair prioritization. Final API 653 decisions should remain with the owner/operator and qualified API 653 inspector.