Skip to main content

Anomaly Detection & Incident Response — AI Autonomous Response Loop

PlantPulse AI provides a closed loop that detects anomalies, has AI diagnose them and propose actions, lets users execute those actions with a single approval, and then automatically verifies and tracks the results.

감지 (이상탐지·알람·고장 전조)
→ 인시던트 승격 + 알림 (인앱·이메일·Slack·모바일 푸시)
→ AI 진단 (원인 후보 · 신뢰도 · 제안 조치)
→ [승인·실행] — 사용자가 탭 한 번으로 조치 실행
→ 자동 재발 검증 (1시간 후)
→ "해결" 보드에서 실행·배정·결과 추적

Where to Find It

  • Web: Real-time anomaly detection (/anomaly) → expand a row via [Details] → Proposed actions below the AI diagnosis (AI Response)
  • Mobile: Anomaly detection tab → [AI Diagnosis] → recommended action list (tapping a push notification jumps straight to that item)

The 4 Proposed Action Types — What Each Button Does

AI diagnosis proposes four types of actions; the button and the actual behavior differ by type.

TypeButtonWhat actually happens when pressedAssignee selection
Acknowledge alarm (ack_alarm)Approve & ExecuteAcknowledges the corresponding alarm on the PlatformNone (executes immediately)
Notify assignee (notify)Approve & ExecuteSends an email with the incident summary to the selected assignee✅ Select from the dropdown, then execute
Order field inspection (inspect)Approve & ExecuteIssues an inspection task in Today's Recommended Work + assigns an owner + sends an email containing a link for registering the action result✅ Select from the dropdown, then execute
Further investigation (investigate)RecordNo external action is executed — only the fact that "the investigation item was received" is written to the audit log with the executor and timestampNone

💡 The assignee dropdown is pre-populated with an assignee matching the role suggested by the AI (maintenance/operations/safety); the list is registered under Assignee Management in the admin console.

Execution Rules

  • Who: Any logged-in user can approve — both the executor and the timestamp are recorded in the audit log
  • Duplicate prevention: An executed action cannot be executed again (only failed actions can be retried)
  • In-progress indication: The button turns into a spinner, and once complete a 실행됨 · 이름 badge remains
  • Safety scope: Equipment control commands are not eligible for execution — only reversible actions such as alarm acknowledgment, notification, and task issuance are executed

After Execution — Verification and Tracking

  1. Automatic recurrence check: One hour after execution, the system automatically checks whether the anomaly has recurred on the same equipment
    • No recurrence → 검증됨 badge (a sign that the action was effective)
    • Recurrence → 재발 badge (a sign that further response is needed)
  2. Resolution board (web /resolutions · mobile "Resolution" tab): Track every executed action on a single screen
    • KPIs: number of executed actions · verified ratio · number awaiting result registration
    • Per row: timestamp · incident · action · executor · assignee · result registration status
    • Click a row → jump directly to the corresponding incident (web)
  3. Result registration loop: An assignee who receives an inspection order (inspect) registers the action result (completed/not applicable + comment) via the link in the email without logging in, and the entry is reflected on the resolution board immediately.

Mobile Scenario (Summary)

① HIGH 인시던트 발생 → 폰에 푸시 도착
② 푸시 탭 → 해당 탐지의 AI 진단이 펼쳐진 채 열림
③ 조치안에서 담당자 선택 → [승인·실행] 탭
④ "해결" 탭에서 배정·결과 추적

Subscribe to push notifications via [Enable Push] on the mobile notifications tab (on iOS, supported in the app added to the home screen).