Home / Product
The drone-to-CMMS integration platform.
Any drone platform in. Any CMMS out. We don't fly the drones. We don't replace the CMMS. We're the mapping layer in between. Stratum Connector closes the seam between inspection output and work order — so drone programs produce preventive maintenance, not PDFs.
The Problem
You built the program. Where does the data go?
You have a drone inspection program — in-house pilots, a subcontracted service provider, or a mix. You're getting imagery. You're getting reports. Capture is solved.
Then the data hits the wall. JPEGs land in SharePoint. PDFs pile up in shared drives. A planner spends six hours retyping a roof report into Maximo — when they get to it at all. The drone program produced inspection data; the CMMS never heard about it.
The piece that's missing is action — the bridge from finding to work order, from JPEG to service request, from flight log to system of record.
Four Failure Modes We See
01 Activation Was Never Scoped
Programs get funded on the capture side. The activation side — how the data lands in Maximo, SAP PM, or Fiix — is assumed to handle itself. It doesn't.
02 Planners Retype Reports By Hand
A planner spends most of a workday converting a multi-page inspection report into individual service requests. By the time the work orders exist, the next inspection cycle has already started.
03 PDFs Accumulate Without Trend Data
Eight quarters of inspection PDFs sit in SharePoint. No comparable structure. No defensible condition history when the insurer asks for one.
04 Year-3 Reviews Have No Answer For The CFO
Flight hours logged is not the same as work orders generated. Programs without the second number get cut at the next budget cycle.
The Gap
What you've built. What's still missing.
Most drone programs over-invest in capture and under-invest in action — whether the pilots are W-2 or 1099. That's the gap Stratum closes.
The left column is where the budget goes. The right column is where the value gets realized — or doesn't. Capture has outrun action.
What Stratum Is
Stratum is the bolt-on.
We don't replace your pilots, your hardware, your processing platform, or your reliability engineers' flight plans. We complete the program by closing the seam between inspection output and work order.
We sell the seam — not the drone, not the analytics model, not the CMMS license. Everything you already invested in keeps doing what it does. Stratum makes it produce work orders.
How It Works
Three layers. One pipeline.
Inspection output enters Stratum from anywhere. It leaves as a structured, source-tagged record in your CMMS.
Ingest
Connectors for DroneDeploy, Pix4D, WebODM, Zeitview, DJI FlightHub, and Skydio Cloud. Direct ingest from shared drives (SharePoint, OneDrive, Google Drive, Dropbox) and thumb-drive uploads. PDF parsing via OCR plus structured extraction and human-in-the-loop validation on first ingest per processor — so we don't promise magic on documents we haven't seen before. EXIF metadata extraction (GPS, timestamp, altitude, sensor type) on every image.
Normalize
Defect classification mapped to your failure-code catalog. Severity scores translated to your CMMS priority field, tuned per asset class. Asset matching from image to asset ID via location, tag, or visual identification. A triage queue with human validation before anything hits the CMMS — because pushing a garbage work order is worse than pushing none.
Push
Pre-built connectors with documented field mapping: IBM Maximo (MXSR service request, not direct work order), SAP PM (PI/PO or CPI middleware, EQUNR + TPLNR aware), Fiix / Rockwell (with completion-webhook feedback loop), eMaint (storeroom-catalog aware), UpKeep, MaintainX, Limble (REST + Zapier/Make compatible), Dynamics 365 Field Service (Power Automate + Dataverse native). Every finding gets tagged SOURCE_SYSTEM = STRATUM so you can answer the CFO's question in one query.
Why Now
Four signals that the activation gap is about to bite.
01 Drone inspection is becoming a standing program, not a one-off.
Operators are running recurring drone inspections — some in-house, many through specialized service providers. Either way, capture is becoming routine. The workflow gap downstream is not.
02 Capture has outrun action.
Pilots are flying faster than planners can act. The bottleneck has moved from getting the data to using it.
03 Insurers are about to force the issue.
Major carriers are signaling that defensible inspection records will become a renewal condition on policies above a certain TIV within 24 months. Defensible means traceable inside a system of record.
04 CFOs are asking the hard question.
Year-3 program reviews surface the same question every time: “What did the drone program produce?” The answer needs to be defects caught and corrected before failure — preventive maintenance completed, downtime avoided, assets kept in service — not flight hours logged or PDFs filed.
Why Us
Built by the people who architect enterprise CMMS deployments.
20+ years architecting enterprise data and systems — as project manager, program manager, consultant, technical expert, and solution architect across ERP, WMS, and CMMS deployments. We know how data moves through industrial operations because we've built the systems it lives in.
FAA Part 107 domain fluency. We understand the drone-inspection stack from the inside — so the connector isn't a translation of someone else's data. It maps detection classes to failure codes against the platforms enterprise programs actually run.
Vendor-agnostic by design. We don't sell drones, analytics models, or CMMS licenses. We don't compete with what you've already built. We sell the seam that makes it work.
Read the founder bioFounding Premise
“The gap between a drone inspection and a structured CMMS work order is a solvable systems problem — and the industry hasn't solved it yet.”
Justin Birch, Founder
The Exchange