# IL 202 — Enterprise AI Readiness Review：填寫範例（SYN-CS-001）/ Filled Example (SYN-CS-001)

> 本範例使用合成案例 SYN-CS-001（示例公司「示範服務公司 A」），所有人物、產品與數據均為合成，不代表真實
> 企業、成功案例或實際收益。本範例是 Module 4 課程內文「找出刻意保留的錯誤」練習修訂後的最終版本，
> 已把隱私準備度從錯誤的 not_applicable 改為 conditional。/ This example uses the synthetic case
> SYN-CS-001 (the example company "Demo Service Company A"); all people, products, and figures are synthetic
> and do not represent a real company, a real success story, or real financial results. This is the
> corrected final version of the "find the deliberate error" exercise in Module 4, with privacy
> readiness fixed from the erroneous not_applicable to conditional.

版本 / Version: v1.0（2026-09-26）

## 中文

| 面向 | 狀態 | 證據 | 缺口 | 是否 blocking | 責任人 | 期限 | 核准人 |
|---|---|---|---|---|---|---|---|
| 資料準備度 | ready | Module 1 資料盤點（knowledge_documents.csv 20 份文件）與資料流向圖 | 無已知缺口；過期／矛盾文件已標記並排除於自動回覆範圍 | 否 | — | — | 技術與治理負責人 |
| 安全準備度 | conditional | Module 2 最小權限矩陣、撤權演練紀錄 | AI 工具 API key 撤權延遲未通過演練，需改為即時撤銷機制 | 否（不影響目前小範圍試行） | 技術管理員（合成角色） | 2026-03-15 | 資安負責人 |
| 隱私準備度 | conditional | Module 1 資料分類、Module 2 存取範圍 | 案件記錄可能含客戶姓名、聯絡方式；尚未確認 AI 工具是否會把個人資料寫入草稿或傳送至外部服務 | 是（在資料流向圖完成個資標註前，不擴大試行範圍） | 隱私負責人（合成角色） | 2026-03-20 | 治理負責人 |
| 整合準備度 | ready | Module 2 整合測試紀錄（唯讀連接，無寫入需求） | 無已知缺口 | 否 | — | — | IT 整合負責人 |
| 治理準備度 | ready | 核准的 IL 101 Charter、決策權責紀錄 | 無已知缺口 | 否 | — | — | 治理負責人 |
| 營運準備度 | ready | Module 3 三種異常情境演練與 runbook | 無已知缺口 | 否 | — | — | 技術與治理負責人 |
| 人員準備度 | ready | 客服人員教育訓練紀錄、Module 3 演練參與紀錄 | 無已知缺口 | 否 | — | — | 客服部門流程負責人 |

| 段落 | 內容 |
|---|---|
| 最終建議 | Proceed with Conditions（附條件進入小範圍試行） |
| 建議理由 | (1) 資料、整合、治理、營運、人員五個面向皆已 ready，有具體證據支持；(2) 安全與隱私兩項條件皆有具名責任人、明確期限與核准人；(3) 隱私缺口已標記為 blocking，限制試行範圍不擴大，直到個資標註完成。 |
| 尚未涵蓋的範圍或已知限制 | 本次審查僅涵蓋一般與缺漏資訊兩類案件；來源矛盾與權限限制類別尚未納入試行範圍。 |
| 合成練習聲明 | 本範例為合成練習，不代表真實企業專案或實際核准結果。 |

## English

| Domain | Status | Evidence | Gap | Blocking? | Owner | Due date | Approver |
|---|---|---|---|---|---|---|---|
| Data readiness | ready | Module 1 data inventory (20 documents in knowledge_documents.csv) and data-flow map | No known gap; outdated/conflicting documents flagged and excluded from auto-reply scope | No | — | — | Technical and governance owner |
| Security readiness | conditional | Module 2 least-privilege matrix, revocation drill log | AI tool API-key revocation delay did not pass the drill; needs real-time revocation | No (does not affect the current limited-scope trial) | Technical administrator (synthetic role) | 2026-03-15 | Security owner |
| Privacy readiness | conditional | Module 1 data classification, Module 2 access scope | Case records may contain customer name/contact details; not yet confirmed whether the AI tool writes personal data into drafts or sends it to an external service | Yes (trial scope will not expand until the data-flow map's personal-data tagging is complete) | Privacy owner (synthetic role) | 2026-03-20 | Governance owner |
| Integration readiness | ready | Module 2 integration test log (read-only connection, no write need) | No known gap | No | — | — | IT integration owner |
| Governance readiness | ready | Approved IL 101 charter, decision-rights record | No known gap | No | — | — | Governance owner |
| Operations readiness | ready | Module 3's three drilled incident scenarios and runbook | No known gap | No | — | — | Technical and governance owner |
| People readiness | ready | Customer-service training records, Module 3 drill participation record | No known gap | No | — | — | Customer-service process owner |

| Section | Content |
|---|---|
| Final recommendation | Proceed with Conditions (a limited-scope trial under the stated conditions) |
| Rationale | (1) data, integration, governance, operations, and people are all ready with concrete supporting evidence; (2) both open conditions (security, privacy) have a named owner, a concrete deadline, and an approver; (3) the privacy gap is marked blocking, keeping the trial scope from expanding until personal-data tagging is complete. |
| Scope not yet covered, or known limitations | This review covers only the normal and missing-information case categories; conflicting-sources and permission-restricted categories are not yet in the trial scope. |
| Synthetic-exercise statement | This example is a synthetic exercise and does not represent a real company project or an actual approval outcome. |