Works from CSV or workbook exports produced from SAP, IBM Maximo, Oracle ERP, Hexagon EAM, Infor, and other ERP, EAM, or CMMS systems. No direct integration or write-back is required — Review data requirements →
Data Handling Commitment

Your MRO catalog CSV is processed for the report pack and then purged.

The most common question before any industrial organization uploads a spare-parts catalog: what happens to the data? This page answers that question directly as a first-class operating commitment.

Download DPA TemplateRequest Diagnostic Pilot
Source purgeAfter report generation
Governance metadataRetained for audit controls
Session-scopedDownloads expire with session
Evidence summary

Trust and governance guide

Data Handling Commitment: The Trust Center explains the control posture behind Industrial IQ so enterprise buyers can inspect data handling, review boundaries, and evidence discipline before adoption. PartsCleanse AI processes MRO catalog CSV files, purges source uploads after report generation, and retains only governed summary metadata.

Review Trust Controls
Review ownerCISO, CIO, legal, procurement, governance, data owners, and executive sponsors evaluating diagnostic boundaries
Input file contextUpload lifecycle, authentication, retained metadata, report ownership, audit events, policy documents, and data-handling commitments.
Diagnostic evidenceA trust view of no ERP write-back, human review, confidence tiers, source-data handling, report ownership, and governance limits.
Recommended actionReview the controls, then use Snapshot or sample reports to inspect the evidence model before private upload.
The core commitment

We process your catalog to generate the report pack, then purge the source file.

PartsCleanse AI is a diagnostic engine, not a data-hosting platform. When you upload a catalog CSV, the file is processed for duplicate-family detection, confidence scoring, and report generation. The source file is then purged after report generation.

This is a deliberate architectural decision. Catalog enrichment platforms may retain and steward source records as part of their service model. PartsCleanse AI produces a governed diagnostic finding, purges the source file after report generation, and retains only the governance layer needed for report ownership, score history, usage control, feedback, and auditability.

If your legal team is comparing vendors: The answer to “what do you retain?” is summary metrics, Open Findings, report ownership, quota usage, feedback, and audit metadata. Source files are purged after report generation. We can document this in a countersigned DPA.
Retained vs. purged
Data elementStatusCatalog source purged?
Uploaded catalog CSV (source file)Purged after report generationYes — immediate
Individual part descriptions and item numbersProcessed for the diagnostic run; retained output is limited to governed findings and metadataSource file purged after report generation
Manufacturer part numbers, vendor codes, plant codesProcessed for matching, confidence scoring, and report generationSource file purged after report generation
Open Findings summary and duplicate group countRetained, tied to authenticated userN/A — retained
Diagnostic metadata (SKU count, runtime, exposure estimate)Retained for dashboardN/A — retained
Report ownership and access logRetained for authentication and auditN/A — retained
Quota usageRetained to govern plan limitsN/A — retained
Processing lifecycle — six steps

From upload to purge: what happens inside the diagnostic engine.

1. Secure upload

Received over HTTPS into an isolated, session-specific run folder. No other user, session, or admin process has read access to that folder during or after processing.

2. In-memory analysis

The file is read into application memory for duplicate-family detection, description normalization, and confidence scoring. Raw catalog rows never enter the database.

3. Report generation

Five report artifacts are produced: browser Open Findings, Excel workbook, Word executive narrative, PDF summary, and clean deduplicated catalog CSV. Written to the run folder, not the database.

4. Source file purge

The uploaded source catalog file is purged after report generation completes. Industrial IQ does not maintain a standing source-file repository; summary metrics, Open Findings, report ownership, quota usage, feedback, and audit metadata may be retained for governance.

5. Session-scoped downloads

Excel, Word, PDF, and clean CSV downloads are available only during the active generation session. After the session ends, only the authenticated browser Open Findings report remains accessible to the generating user.

6. Permanent retention only

Open Findings summary, SKU count, duplicate rate, exposure estimate, runtime, report ownership, quota usage, feedback, and audit metadata. No catalog rows. No item descriptions. No part numbers.

Quotable commitment — source purge

PartsCleanse AI processes the uploaded catalog CSV to generate the diagnostic report pack and then purges the source file after report generation. Summary metrics, Open Findings, report ownership, quota usage, feedback, and audit metadata may be retained for governance.

Competitive differentiator — data model

Catalog enrichment and optimization platforms may retain and host source records as part of their service model. PartsCleanse AI is a diagnostic engine: the source file is processed for the report pack and then purged. You own the output; AI2COE retains only the governance metadata required to support report ownership, usage controls, feedback, score history, and auditability.

Data handling FAQ

Questions legal, procurement, and CISO teams ask before approving upload.

Who can access our uploaded catalog file?

Nobody except the PartsCleanse AI processing engine during the active analysis window. The file exists within an isolated session run folder with no admin, employee, or contractor read access. It is deleted before any human review of the diagnostic run is possible.

Can Industrial IQ use our catalog data for AI model training?

No. Customer source files are not used for model training, benchmarking datasets, or competitive analysis. The upload is processed to generate the diagnostic report pack and then purged; governance metadata may be retained for report ownership, usage control, and audit history.

What if our catalog contains sensitive part descriptions or export-controlled items?

The source file is processed for duplicate detection, report generation, and confidence scoring, then purged after report generation. Retained records are limited to governed findings, summary metrics, ownership, quota usage, feedback, and audit metadata.

How does this compare to Verdantis and Verusen?

Verdantis and Verusen are catalog enrichment platforms — they retain, enrich, and host your catalog records as the core of their service model. PartsCleanse AI is a diagnostic engine: we process the data, purge the source, and deliver the finding. You own the output. We retain only the metadata required to govern the report and your account.

Is a Data Processing Agreement available?

Yes. A GDPR Article 28-compliant DPA template is available for immediate download without a sales call. Enterprise accounts requiring custom DPA terms or countersignature should contact support@ai2coe.com before uploading.

What jurisdiction does data processing occur in?

Processing occurs in the United States. For EU, UK, and GCC accounts with data localization requirements, contact support@ai2coe.com to discuss jurisdiction-specific arrangements before initiating the first diagnostic session.

Enterprise accounts — pre-upload legal review

DPA, custom data residency, and countersignature.

For accounts requiring a countersigned GDPR Article 28 Data Processing Agreement, a jurisdiction-specific data residency arrangement, or legal review before first upload: contact support@ai2coe.com with “DPA Request” in the subject line. A standard template is available for download without a call at /dpa.

Download DPA TemplateView Full Trust CenterSecurity Overview
AI2COE Copilot