AI inspections for Intelex

Overview

Intelex is very good at getting the picture off the floor and into a record. The picture then waits for a human. Its observation and inspection forms carry photos, annotations and location, online or offline, which means a plant on Intelex is already generating exactly the raw material an inspection engine needs. RapidEye reads that stream: the pictures, plus the site, the area and the date they carry, returned as one finding per issue visible in the frame, including the issues nobody filed the record about.

How it works with Intelex

Intelex separates the ways a plant reports what it sees, and each one produces images with a different shape to them. These are the common ones rather than the boundary: RapidEye reads whatever documentation your teams produce, video walkthroughs and 3D scans included, and reports against the standard you set for that area.

• Safety observations. A worker photographs one unsafe condition and moves on. RapidEye reads the rest of the frame and the same spot's history, so the third photo of that racking in two months reads as a trend rather than a third report.
• Scheduled inspections. Inspection rounds cover the same equipment on a cadence, which makes them the strongest signal on the platform: the same angle, week after week, is what change detection is for.
• Audit walks. Photos taken through an internal or external audit become the reference state for the area, so the next round shows what held and what came back.
• Incidents and near misses. The pictures taken around an event show the surrounding condition, and RapidEye reports what was already different about that area in the weeks before it.
• Quality checks on the line. The same reading applies to product and packaging photos: the station, the bench and what changed there since the last check.

A RapidEye finding carries the site, the area, where in the frame the issue is, its type, how serious it looks, the pictures before and after, and a suggested next step. It arrives in the RapidEye dashboard and, if you want it there, in an inbox or a Slack channel for the EHS office. Whether any of it becomes an Intelex record, an action or nothing at all is your team's call. If your programme runs on a record type or an input not listed here, that is a setup conversation, not a wall.

How to connect Intelex to RapidEye

1. The sites in scope. Choose the sites and locations to read first. Intelex sorts and filters records by location, so scope follows the location tree you already maintain rather than a new one.
2. The record types that carry pictures. Safety observations, inspections, audits, or all three. Where a form produces no images today, RapidEye sends a capture link that opens on any phone, no app to install, and the inspector takes a fixed set of angles for the area.
3. A RapidEye user on the account. Add RapidEye as a user in Intelex so it can read those records. The Connect Intelex box on this page has the name and email to use.

What Intelex captures on a record, and what it does with it

Checked against Intelex's product documentation, September 2026.

Intelex is an EHSQ platform: environment, health, safety and quality in one place, sold as a set of applications on a shared platform rather than one product. According to Intelex's product documentation (intelex.com), Safety Observations Management lists media attachments as a feature, describing attaching and annotating pictures directly from mobile devices to add visual context to safety observations, alongside location reporting with coordinates, categorization, and corrective and preventive actions assigned off the back of a report. Its inspection application describes capturing notes, photos and locations on any device and consolidating them into a centralized system of record, with a complete audit trail. Intelex Mobile describes photo and voice annotation with GPS location, working online or offline for confined spaces and areas without a signal.

Fields as listed on Intelex's safety observations, inspection management and audit management pages. The closing line of each card is RapidEye, not Intelex.

Who reads the pictures on an Intelex record?

The person it routes to, once. Intelex is explicit that the point of mobile capture is speed: get the observation in from where it happened instead of waiting for a desk at the end of the day, and its analytics then aggregate what was typed into the structured fields. That works, and it is why observation volume goes up when a plant adopts it. The consequence is arithmetic rather than a flaw: a site that files hundreds of observations a month has hundreds of pictures a month, each looked at once by one reviewer answering one question, and never looked at again or against each other. Categorization and severity are typed by the reporter; the picture is the only part of the record nobody has been able to query. Reading that layer, at that volume, across a year of history, is the whole of what RapidEye does here.

Intelex integration FAQ