What are the RTO and RPO targets for PartsCleanse AI?

PartsCleanse AI targets a Recovery Time Objective (RTO) of 4 hours and a Recovery Point Objective (RPO) of 24 hours for core platform services including the diagnostic engine, user account data, and report ownership records. The diagnostic processing engine has an RTO of 24 hours due to atomic run design — a disrupted run is restarted cleanly with no partial data loss.

How are backups handled for PartsCleanse AI data?

Database backups cover summary metrics, user account data, lead records, audit logs, and report ownership records. Source catalog CSV files are excluded from backup by design — they are purged after report generation and are not retained. Backups are taken on a daily cycle with a 24-hour RPO.

How does Industrial IQ communicate during a platform incident?

Active engagement contacts are notified within 2 business hours of a confirmed incident affecting their engagement. For confirmed material data breaches, affected clients are notified within 72 hours consistent with GDPR Article 33. Incident updates are communicated via email to registered account holders.

What happens to an in-progress diagnostic run during a platform outage?

Diagnostic runs are atomic — a run either completes with all five report artifacts delivered, or it does not start. There are no partial-run states that could result in data loss or incomplete output. If an outage occurs during a run, the run is restarted from scratch after platform recovery.

Business Continuity & Disaster Recovery

Component-level RTO and RPO targets.

Component	RTO	RPO	Notes
Diagnostic processing engine	24 hours	4 hours	Restart from last stable state. Diagnostic runs are atomic — either completed with all artifacts or not started. No partial-run data loss.
Open Findings browser reports	4 hours	24 hours	Backed up via database backup cycle. Open Findings data restored from the most recent backup.
Admin and user account data	4 hours	24 hours	User accounts, profile data, lead records, and audit logs restored from database backup.
Report ownership and quota records	4 hours	24 hours	Restored from database backup alongside account data.
Source catalog files (uploaded CSVs)	N/A — not applicable	N/A — not applicable	Source catalog files are purged after report generation by design. They are not backed up and cannot be recovered — this is the intended architecture.

Business continuity posture

Why PartsCleanse AI has lower continuity risk than live SaaS.

PartsCleanse AI is a diagnostic service, not a live production SaaS platform. Clients do not depend on real-time uptime for operational continuity — the engagement produces a report artifact that the client retains and acts on independently. A service interruption delays delivery but does not create an operational dependency failure for the client's ongoing operations.

This is structurally different from live SaaS platforms where downtime directly interrupts production workflows. Our SLA overrun remedy (10% fee reduction per 3-day overrun) is the primary continuity protection for active engagements.

Maintenance and incident communication

How we communicate planned and unplanned downtime.

Planned maintenanceAnnounced via email to active engagement contacts 48 hours in advance. Windows scheduled outside normal business hours where possible.

Unplanned outagesActive engagement contacts notified by email within 4 hours of confirmed outage affecting report delivery. SLA clock paused for outage duration.

Incident escalationContact support@ai2coe.com. Response: within 2 business hours for active engagement contacts.

Data breach notificationAffected clients notified within 72 hours of confirmed material breach, consistent with GDPR Article 33 processor obligations.