Intrinsically safe tablets for pipeline inspection

Why tablets fit pipeline routes

Pipeline inspection is route work with a record-keeping burden: maps, checklists, asset histories and photographs, all tied to locations along a line. A phone screen is too small for that bundle, and paper forms create transcription work back at base. A tablet sits between the two: large enough for maps and forms, portable enough for a walking route, and able to capture photographs and positions in the same record. That is why tablets are the natural first device class for pipeline inspection teams, with phones for contact and terminals for tag reading alongside.

Screen size and the route

Tablets on this site list 8.0 inch, 10.1 inch and 10.36 inch screens. The 8.0 inch XPad_08 suits a route walked mostly on foot, where the tablet is carried in one hand and consulted in short bursts. The 10.36 inch Ex Tablet08 and the 10.1 inch Ex Tablet09 and Ex Tablet10 suit routes where the tablet is the working surface — long checklists, site drawings, photographic evidence reviewed on the spot. Weight matters on a long route, and only one tablet listing publishes it: 1390 g for Ex Tablet10. Do not assume the others are lighter; ask.

Positioning, cameras and battery

Positioning ties a reading to a place. The XPad_08 listing names a built-in positioning system with altitude measurement and a compass; the Ex Tablet08 listing names four-system positioning with altitude and compass; the Ex Tablet09 listing names GPS, Galileo, Glonass, altitude and compass. Cameras turn a finding into evidence: XPad_08 lists front 8.0 MP and rear 13 MP autofocus; Ex Tablet08 lists front 16 MP and rear 20 MP with flash; Ex Tablet09 lists dual 16 MP cameras. Battery decides whether the tablet survives the route: 7000 mAh, 9000 mAh and 20000 mAh are published for different models, and Ex Tablet10 publishes no battery figure. Compare only within a listing, and confirm expected shift life for your route length in the quote request.

System questions to settle early

Two system questions should be settled before ordering, because they decide whether site software runs at all. First, the operating system: Ex Tablet08 lists Android 13.0 on the manufacturer's website, Ex Tablet09 lists Android, and Ex Tablet10 deliberately carries no system claim on this site — confirm the operating system configuration before ordering that model. Second, the site software itself: confirm that inspection apps, maps and forms run on the configuration you order, and confirm update support duration in the quote request.

What to put in the quote request

Confirm MOQ and lead time in your quote request. Confirm certification scope and marking for your target market before ordering. Confirm the model availability for your site before ordering. Certificates available upon request. Related reading: intrinsically safe tablets, tablet selection guide, pipeline inspection and dispatch, XPad_08, Ex Tablet08.

A worked route example

Consider a 40-kilometre pipeline section inspected on foot in two days, with 120 assets to check, photograph and record. The tablet for that route needs a screen large enough for maps and checklists, a battery that survives a full day away from power, cameras for photographic evidence, and positioning that ties each record to a location. On the listed parameters, the Ex Tablet09 shortlists first on battery — 20000 mAh with standby up to 900 hours — but standby is not shift life, so the inquiry must ask for screen-on field life with positioning and photography active. The Ex Tablet08 shortlists on screen and cameras — 10.36 inch, dual cameras with flash, four-system positioning — but publishes no storage figure, so offline maps need a storage question. The XPad_08 shortlists on handling — 8.0 inch for one-handed route work — but its 7000 mAh battery needs a shift-life question for a two-day route. The worked example shows that the right tablet is the one whose gaps are answerable, not the one whose headline numbers are biggest.

Tablet versus phone on the same route

It is tempting to run the whole route on phones and skip tablets, because phones are cheaper and already in pockets. The trade is readability and record quality: a phone screen forces maps and checklists into scrolling views, photographs are taken on a device also handling calls, and long-form entries become slow. Tablets reverse those trade-offs at the cost of weight and a second device to charge and manage. Most pipeline teams settle on both — tablets for the record, phones for contact — with terminals added where assets carry tags. The comparison guide sets out that split in full, and the fleet decision should be made per role, not per device count.

Offline maps and records

Pipeline routes run beyond reliable connectivity, so offline capability is not a convenience but a requirement. Maps for the route, asset histories for the stops, checklists for the round and photographic records for findings must all work without a network, and sync must happen reliably when connectivity returns. That requirement turns into a set of questions: how much storage does the ordered configuration provide for offline maps and records, and is expansion supported; how does the record system queue photographs and readings taken offline; what happens to a half-synced record if the connection drops mid-upload; and how are conflicts resolved when a record is edited in two places? Storage figures are published for some tablet listings and not for others — Ex Tablet09 lists 128 GB expandable to 1 TB, while Ex Tablet08 publishes no storage figure — so the offline question must be asked per model, not assumed across the range. A tablet that cannot hold the route's maps offline cannot run the route, whatever its screen and battery figures say.

Protecting the record on the route

A pipeline record is only as good as its protection on the route. Photographs need to survive a dropped tablet, readings need to survive a dead battery, and half-finished checklists need to survive a shift change. That means asking about local storage behaviour: are records saved continuously or only on submission, what happens to an unsaved record when the battery dies, and how does a half-finished checklist pass to the next operator? It also means asking about backup: is there a sync point at the route's end, a vehicle dock, or a base station where records are confirmed received? A tablet deployment that answers those questions before the first route will lose no records; one that discovers them on the route will lose the records that matter most — the ones from the hardest stops.