Home / How It Works
How the Stratum Connector actually works.
The drone-to-CMMS integration platform, end to end. Any drone platform in. Any CMMS out. We don't fly the drones. We don't replace the CMMS. Here is exactly what happens in between.
Four stages. One pipeline.
Inspection output enters Stratum from any platform. It leaves as a structured, source-tagged record in your system of record — then the loop closes with completion feedback. Nothing about your capture stack or your CMMS license changes. Stratum is the mapping layer that connects the two.
Stage 01
Ingest — any drone platform's export format.
The connector reads native exports from DroneDeploy, Skydio Cloud, DJI Terra / FlightHub, Pix4D, WebODM, Zeitview, and custom pipelines. Direct ingest from shared drives — SharePoint, OneDrive, Google Drive, Dropbox — plus thumb-drive uploads.
EXIF metadata is extracted from every image: GPS, timestamp, altitude, and sensor type. PDF reports are parsed via OCR plus structured extraction, with human-in-the-loop validation on first ingest per processor — so we don't promise magic on document formats we haven't seen before.
Reads From
DroneDeploy· orthomosaic + annotations exportSkydio Cloud· scan + detection APIDJI Terra / FlightHub· job exportPix4D / WebODM· processed outputsSharePoint / OneDrive / GDrive· direct pickupPDF + JPEG· OCR + EXIF extraction
Mapping Catalog
| Drone detection class | CMMS mapping |
|---|---|
| Membrane blister / seam split | Failure code + P2 priority |
| Active corrosion (severity 3) | Failure code + P1 priority |
| Thermal anomaly (delta > threshold) | Failure code + inspection task |
| Blocked drain / ponding | Failure code + P3 priority |
Stage 02
Map — detection classes to failure codes and priorities.
The mapping catalog is the heart of the platform. Each drone-detection class is matched to your CMMS failure-code catalog. Severity scores are translated to your priority field, tuned per asset class — a P1 on a crane runway is not a P1 on a parapet cap.
Imagery resolves to a specific asset ID via location, tag, or visual identification against your asset register (EQUNR / TPLNR in SAP, asset + location in Maximo). A human-validated triage queue sits between detection and system of record — because pushing a garbage work order is worse than pushing none. The catalog compounds: every mapping validated for one deployment strengthens the next.
Stage 03
Push — a service request or work order via CMMS-native API.
Structured findings become native records through each system's own integration surface — not a CSV a planner has to import by hand:
- IBM Maximo — MXSR service request (not a direct work order), asset + location aware
- SAP PM — PI/PO or CPI middleware, EQUNR + TPLNR aware notifications
- Fiix / Rockwell — REST with a completion-webhook feedback loop
- Dynamics 365 Field Service — Power Automate + Dataverse native
- ServiceNow — incident / request via Table API
- eMaint, UpKeep, MaintainX, Limble — REST + Zapier / Make compatible
Every finding is tagged SOURCE_SYSTEM = STRATUM so leadership can answer, in a single query, exactly what the drone program produced.
Example Push Payload
POST /maximo/oslc/os/mxsr
{
"asset_id": "RF-ROOF-04",
"location": "BLDG-A/ROOF",
"failure_code": "MEM-SPLIT",
"priority": 2,
"description": "Membrane seam split,
NE quadrant, 1.2m",
"source_system": "STRATUM",
"evidence_url": "https://.../img_0421.jpg"
}Closed-Loop Feedback
Flight hours logged is not the same as work orders completed. The closed loop is how a drone program answers the CFO's year-three question.
Stage 04
Close the loop — completion feedback updates trend data.
When the CMMS closes a work order Stratum created, that completion event flows back through the connector. The finding is marked resolved, the asset's condition record updates, and program-level trend data builds across inspection cycles.
Over time this produces a defensible condition history — traceable inside the system of record, the kind insurers increasingly require on high-TIV policies. It also closes the accountability gap: for every finding surfaced, you can see whether it became a work order and whether that work order was completed.