exec-4

To transfer this plan into **Word** while preserving formatting, here are the best approaches. I'll give you **3 options** (ranked from best to quickest), and I've also prepared a **ready-to-copy Word-friendly version** below.

---

## Option 1: Copy as Rich Text (Best for Word)

I've prepared a **clean, Word-optimized table** below. Just **copy the entire table** and paste it directly into Word. It will retain:
- Bold headers
- Column alignment
- Clean spacing
- Color coding (if you paste with "Keep Source Formatting")

---

### COMET-NAM Migration Plan (Adapted from EMEA Template)

| **Phase** | **Task ID** | **Task Name** | **Description (NAM version)** | **Start Date** | **End Date** | **Duration (Hrs)** |
|-----------|-------------|---------------|-------------------------------|----------------|--------------|-------------------|
| **Phase 1: IAM & Group Setup** | 1.1 | Define the Pilot Group | Identify NAM users for the initial production pilot (consider onshore/offshore support + existing pilot users). | TBD | TBD | 1 |
| | 1.2 | Create AD Groups | Submit requests to IAM/Directory Services to create NAM-specific AD groups (e.g., SG-COMET-NAM-Dev-CitiDesktop and SG-COMET-NAM-Support-CitiDesktop). | TBD | TBD | 1.5 |
| | 1.3 | Create New Atom Groups | Define NAM-specific user groups within the Atom deployment console (e.g., COMET-NAM-Pilot and COMET-NAM-Prov). | TBD | TBD | 1 |
| | 1.4 | Consult with EMEA Team | Reach out to the EMEA team (who just completed their pilot) for lessons learned, pitfalls, and best practices. | TBD | TBD | 2 |
| **Phase 2: Prod Config & Portal Setup** | 2.1 | Create AppD Portal Configurations | Configure AppD portal profiles for NAM Prod and Pilot environments (Launch Info, atom stream, toggles). | TBD | TBD | 1 |
| | 2.2 | Merge Atom Users into Prod/Pilot Groups | Consolidate and map all existing legacy Atom users in NAM into the newly created COMET-NAM-Pilot and COMET-NAM-Prov groups. | TBD | TBD | 2 |
| | 2.3 | Sync AD Groups with AppD Portal | Map the newly created NAM AD groups to their respective roles/permissions within the AppD portal. | TBD | TBD | 2 |
| **Phase 3: Pilot & Communication** | 3.1 | Launch Pilot Phase | Enable Citi Desktop for the COMET-NAM-Pilot group to validate stability in Prod. | TBD | TBD | 2 |
| | 3.2 | Send Retirement & Access Notices | Broadcast retirement notices to all COMET-NAM Prod users with instructions to request Citi Desktop & EEMS access. | TBD | TBD | 2 |
| **Phase 4: Prod Rollout & Handover** | 4.1 | Resolve Pilot Feedback | Address any bugs, config mismatches, or performance issues identified by the NAM Pilot group. | TBD | TBD | 2 |
| | 4.2 | Phased Production Migration | Gradually enable Citi Desktop for batches of COMET-NAM production users. | TBD | TBD | 2.5 |
| | 4.3 | Hypercare Support | Provide dedicated support via the new NAM Support AD group (e.g., SG-COMET-NAM-Support-CitiDesktop). | TBD | TBD | 2.5 |
| | 4.4 | Handover to Decommissioning Team | Compile migration sign-off report and hand over to the team responsible for decommissioning legacy Atom in NAM. | TBD | TBD | 0.1 |

---

### Decision Points for COMET-NAM

| **Area** | **EMEA Choice** | **NAM Decision Needed** |
|----------|----------------|--------------------------|
| Number of groups | 3 separate: Prod, Pilot, Support | Does NAM want the same, or combine Pilot & Support? |
| Pilot group composition | Onshore/offshore support + existing pilot users | Who will NAM include? |
| AD group naming | SG-COMET-EMEA-... | Use SG-COMET-NAM-... |
| Atom group naming | COMET-EMEA-Pilot / COMET-EMEA-Prov | Use COMET-NAM-Pilot / COMET-NAM-Prov |
| Consultation | Consulted OneTouch team | Consult EMEA team (just finished) |
| Hypercare support | Dedicated Support AD group | Dedicated or combined? |
| Decommissioning | External team | External or internal? |

---

## Option 2: Export as HTML → Open in Word

1. Copy the **HTML code** I provided in my previous response.
2. Save it as a `.html` file.
3. Right-click → **Open with Word**.
4. Word will render the table with all styling intact.
5. Save as `.docx`.

---

## Option 3: Paste into Google Docs → Download as Word

1. Paste the plain table into Google Docs.
2. Use **Table → Table properties** to adjust borders and shading.
3. Download as `.docx` — formatting is usually preserved well.

---

## Quick Tip for Word

After pasting into Word:
- Go to **Paste Options** → choose **Keep Source Formatting** (or **Merge Formatting**).
- If the table looks off, click **Layout** → **AutoFit** → **AutoFit Window** to stretch it cleanly.

---

Would you like me to:
- **Generate a plain-text version** (no markup) for easier copy-paste?
- **Provide an HTML file** you can save and open directly in Word?
- **Adjust any columns** (e.g., add a "Status" or "Owner" column) before you export?