# Nachbau-Dokumentation Batch b_43

Datum der Screenshots: 2026-06-14 bis 2026-06-15
Bearbeitet: 20 Bilder

---

## Bild-Übersicht

---

### Bildschirmfoto 2026-06-14 um 22.27.10.png + 22.27.18.png + 22.27.23.png — SUBSTANZ: AWS IAM — Benutzerdetails „terraform" (Security Credentials Tab)

**Zusammengeführte Dokumentation aus 3 Frames.**

**Tool/App:** AWS IAM Console  
**URL:** `903393797582.us-east-1.console.aws.amazon.com/iam/home?region=us-east-1#/users/details/terraform`  
**AWS-Konto:** 903393797582  
**IAM-Benutzername:** terraform  

---

#### Layout

Linke Sidebar: IAM-Navigation. Hauptbereich: User-Detail-Seite mit Tab-Leiste oben, dann Sektionen in Card-Layout.

---

#### Summary-Sektion (obere Card)

| Feld | Wert |
|---|---|
| ARN | `arn:aws:iam::903393797582:user/terraform` |
| Console access | Disabled |
| Created | December 04, 2023, 19:03 (UTC+01:00) |
| Last console sign-in | – (kein Login) |
| Access key 1 | AKIASEVTXMXHMPFE4LJH — **Inactive** — Used 34 days ago, 923 days old |
| Access key 2 | Create access key (leer) |

---

#### Tab-Leiste

Tabs (in Reihenfolge):
1. **Permissions**
2. **Groups (1)**
3. **Tags**
4. **Security credentials** ← aktiv
5. **Last Accessed**

---

#### Sektion: Console sign-in

| Feld | Wert |
|---|---|
| Console sign-in link | `https://903393797582.signin.aws.amazon.com/console` |
| Console password | Not enabled |

Button: **Enable console access** (rechts oben in der Sektion)

---

#### Sektion: Multi-factor authentication (MFA) (0)

Beschreibungstext: "Use MFA to increase the security of your AWS environment. Signing in with MFA requires an authentication code from an MFA device. Each user can have a maximum of 8 MFA devices assigned."

Tabelle-Spalten:
- Type
- Identifier
- Certifications
- Created on

Status: **Keine MFA-Geräte.** Meldung: "No MFA devices. Assign an MFA device to improve the security of your AWS environment."

Buttons:
- **Remove** (grau/disabled)
- **Resync** (grau/disabled)
- **Assign MFA device** (blau, primär)
- Innerhalb der leeren Tabelle zusätzlich: **Assign MFA device** (mittig)

---

#### Sektion: Access keys (1) — Frame 22.27.18.png

Beschreibung: "Use access keys to send programmatic calls to AWS from the AWS CLI, AWS Tools for PowerShell, AWS SDKs, or direct AWS API calls. You can have a maximum of two access keys (active or inactive) at a time."

Button oben rechts: **Create access key**

**Access Key Card — AKIASEVTXMXHMPFE4LJH:**

| Feld | Wert |
|---|---|
| Access Key ID | AKIASEVTXMXHMPFE4LJH |
| Status | Inactive |
| Last used | 34 days ago |
| Created | 923 days ago |
| Last used region | eu-central-1 |
| Last used service | appconfig |

Button rechts: **Actions ▼** (Dropdown)

---

#### Sektion: API keys (0)

Beschreibung: "API keys grant access to specific AWS services. You can have a maximum of two API keys per service (active, inactive, or expired) at a time."

Filter: Service (Dropdown "Any") | Status (Dropdown "Any ▼")

Tabelle-Spalten:
- Service ▼
- API key name ▼
- Created ▼
- Expires ▼
- Status ▼

Status: Leer — Meldung: "No API keys"

Button: **Generate API Key** (Dropdown **Actions ▼** oben rechts)

---

#### Sektion: SSH public keys for AWS CodeCommit (0)

Beschreibung: "Use SSH public keys to authenticate access to AWS CodeCommit repositories. You can have a maximum of five SSH public keys (active or inactive) at a time."

Tabelle-Spalten:
- SSH Key ID
- Uploaded
- Status

Status: Leer — Meldung: "No SSH public keys"

Button: **Upload SSH public key** (rechts oben + in Tabellenmitte)

---

#### Sektion: X.509 Signing certificates (0) — Frame 22.27.23.png

(Vergrößerte Ansicht dieser Sektion.)

Beschreibung: "Use X.509 certificates to make secure SOAP-protocol requests to some AWS services. You can have a maximum of two X.509 certificates (active or inactive) at a time."

Tabelle-Spalten:
- Creation time
- Thumbprint
- Status

Status: Leer — Meldung: "No X.509 certificates"

Buttons:
- **Actions ▼** (Dropdown)
- **Upload** (blau outline)
- **Create X.509 certificate** (blau gefüllt)
- In Tabellenmitte: **Create X.509 certificate**

---

### Bildschirmfoto 2026-06-14 um 23.57.03.png + 23.57.11.png + 23.57.24.png + 23.57.38.png — SUBSTANZ: AWS ECS — Task Definition „backend-production:6"

**Zusammengeführte Dokumentation aus 4 Frames.**

**Tool/App:** Amazon Elastic Container Service (ECS) Console  
**URL:** `903393797582.eu-central-1.console.aws.amazon.com/ecs/v2/task-definitions/backend-production/6/Containers`  
**Region:** Europe (Frankfurt) — eu-central-1  

---

#### Layout

Linke Sidebar: Amazon Elastic Container Service Navigation. Hauptbereich: Task-Definition-Detail-View mit Tab-Leiste + Sektionen.

---

#### Breadcrumb

Amazon Elastic Container Service → Task definitions → backend-production → Revision 6 → Containers

---

#### Overview-Sektion

| Feld | Wert |
|---|---|
| Task Definition Name | backend-production |
| Revision | 6 |
| ARN | `arn:aws:ecs:eu-central-1:903393797582:task-definition/backend-production:6` |
| Status | ACTIVE |
| Time created | June 11, 2026, 08:19 (UTC+2:00) |
| App environment | Fargate |
| Task role | – (leer) |
| Task execution role | ecsTaskExecutionRole (Link) |
| Operating system/Architecture | Linux/X86_64 |
| Network mode | awsvpc |
| Fault injection | – (leer) |
| Last updated | June 14, 2026, 23:53 (UTC+2:00) |

Buttons oben rechts:
- **Deploy ▼** (Dropdown, blau)
- **Actions ▼** (Dropdown)
- **Create new revision ▼** (Dropdown)

---

#### Tab-Leiste

1. **Containers** ← aktiv
2. **JSON**
3. **Task placement**
4. **Volumes (0)**
5. **Requires attributes**
6. **Tags**

---

#### Task size

| Feld | Wert |
|---|---|
| Task CPU | 256 units (0.25 vCPU) |
| Task memory | 1.024 MiB (1 GB) |
| Task CPU maximum allocation for containers | Grafik: Balken-Chart horizontal |
| Task memory maximum allocation for containers | Grafik: Balken-Chart horizontal |

**Legende CPU-Chart:** log_router (gelb/orange), datadog-agent (blau), backend (grün), Shared task CPU (grau)  
**Legende Memory-Chart:** log_router, datadog-agent, backend, Shared task memory

---

#### Container: log_router — Details-Tab

| Feld | Wert |
|---|---|
| Image | `amazon/aws-for-fluent-bit:stable` |
| Private registry | Turned off |
| Secrets Manager ARN or name | – |
| CPU | 0 |
| Memory hard/soft limit | –/– |
| GPU | – |
| Neuron device | – |

**Sub-Tabs (Container-intern):**
1. Environment and secrets ← aktiv
2. Network settings
3. Security and permissions
4. Lifecycle and dependencies
5. Monitoring and log

**Environment variables (0):**

Tabelle-Spalten: Key ▲ | Type ▼ | Value ▼

Meldung: "No environment variables to display."

**Environment files (S3 ARN):** (Sektion sichtbar, kein Inhalt)

---

#### Container: backend — Details-Tab (Frame 23.57.24.png)

| Feld | Wert |
|---|---|
| Image | `903393797582.dkr.ecr.eu-central-1.amazonaws.com/backend-production:latest` |
| Private registry | Turned off |
| Secrets Manager ARN or name | – |
| CPU | 0 |
| Memory hard/soft limit | –/– |
| GPU | – |
| Neuron device | – |

**Sub-Tab: Environment and secrets aktiv**

**Environment variables (59):**

| Key | Type | Value |
|---|---|---|
| APP_MODE | value | production |
| AWS_ACCESS_KEY | value | AKIASEVTXMXH7CNRNEB |
| AWS_REGION | value | eu-central-1 |
| AWS_S3_PUBLIC_BUCKET | value | kadi-public-production |
| AWS_SECRET_KEY | value | CYyz7Sbu28wQA8hVtzNMFiuNQQdRUpEuqpKewpP |
| CUSTOMER_APP_URL | value | `https://app.kadicon.de` |
| DASHBOARD_URL | value | `https://dashboard.kadicon.de` |
| DATABASE_HOST | value | main-db-production.copmvD0uJfs.eu-central-1.rds.amazonaws.com |

(Insgesamt 59 env vars; nur die ersten 8 sichtbar)

---

#### Container: datadog-agent — Details-Tab (Frame 23.57.38.png)

| Feld | Wert |
|---|---|
| Image | `datadog/agent:latest` |
| Private registry | Turned off |
| Secrets Manager ARN or name | – |
| CPU | 0 |
| Memory hard/soft limit | –/– |
| GPU | – |
| Neuron device | – |

**Sub-Tab: Environment and secrets aktiv**

**Environment variables (7):**

| Key | Type | Value |
|---|---|---|
| DD_API_KEY | value | 5dd2983e1c99231e09dc21dfc35acd2 |
| DD_APM_ENABLED | value | true |
| DD_APM_NON_LOCAL_TRAFFIC | value | true |
| DD_RUNTIME_SECURITY_CONFIG_EBPFLESS_ENABLED | value | true |
| DD_RUNTIME_SECURITY_CONFIG_ENABLED | value | true |
| DD_SITE | value | datadoghq.eu |
| ECS_FARGATE | value | true |

**Environment files (S3 ARN):** (Sektion sichtbar, kein Inhalt)

---

### Bildschirmfoto 2026-06-15 um 00.08.25.png — SUBSTANZ: AWS ECS — Task Definition „backend-production" Revisions-Liste

**Tool/App:** Amazon Elastic Container Service (ECS) Console  
**URL:** `903393797582.eu-central-1.console.aws.amazon.com/ecs/v2/task-definitions/backend-production`  

---

#### Seite: backend-production (7 Revisionen)

**Header-Info:**
- Last updated: June 15, 2026, 00:08 (UTC+2:00)
- Filter status: Active

**Buttons:** Deploy ▼ | Actions ▼ | Create new revision ▼  
**Pagination:** Seite 1 von 1

---

#### Tabelle: Task definition revisions

| # | Task definition:revision | Status |
|---|---|---|
| (Checkbox) | backend-production:7 | Active (grüner Kreis-Check) |
| (Checkbox) | backend-production:6 | Active |
| (Checkbox) | backend-production:5 | Active |
| (Checkbox) | backend-production:4 | Active |
| (Checkbox) | backend-production:3 | Active |
| (Checkbox) | backend-production:2 | Active |
| (Checkbox) | backend-production:1 | Active |

Alle 7 Revisionen haben Status **Active**.

Filter-Feld: „Filter task definition revisions by value" (Textfeld) mit Dropdown „Active" als aktiver Filter.

---

### Bildschirmfoto 2026-06-15 um 00.10.02.png — SUBSTANZ: Kadi-Reservierungs-E-Mail „Reservation Updated" (16 Jun)

**Tool/App:** E-Mail-Client (Gmail/Browser-basiert)  
**Absender:** no-reply@kadicon.de  
**Empfänger:** an mich  
**Zeitstempel:** 00:09 (vor 0 Minuten)  

---

#### E-Mail-Layout

- Oben links: Avatar-Kreis mit „MR" + rotes Offline-Dot, Absendername: (unklar, nicht lesbar)
- Oben rechts: Uhrzeit, Stern, Emoji-Reaction, Reply, Mehr-Menü (3-Punkte)

---

#### E-Mail-Inhalt

**Header-Logo:** „KA" (stilisiertes blaues Monogramm-Logo, Handschrift-Stil)

**Betreff/Heading:** Reservation Updated

**Bild:** Speisen-Foto (Restaurant-Tischszene mit verschiedenen Gerichten), breites Banner

**Reservierungsdetails:**

| Feld | Wert |
|---|---|
| Datum | 16 Jun |
| Restaurant | Restaurant Durrani |
| Kategorie | Upcoming reservation (grün) |
| Reservation for | 2 |
| Tag/Zeit | Tue . 22:30 CET |
| State | approved |

**CTA-Button:** Kreis-Icon mit Telefon-Symbol + Text **CALL** (zentriert)

**Adresse (Icon Karte):** Brentanostraße 9, 63571 Gelnhausen, Germany

**Hinweis-Zeile (Icon Stift):** Modify your reservation by contacting Restaurant Durrani.

---

### Bildschirmfoto 2026-06-15 um 00.14.55.png — SUBSTANZ: Kadi-Reservierungs-E-Mail „Reservation Updated" (17 Jun)

**Tool/App:** E-Mail-Client (Gmail/Browser-basiert)  
**Absender:** no-reply@kadicon.de  
**Empfänger:** an info  
**Zeitstempel:** 00:14 (vor 0 Minuten)  

---

#### E-Mail-Inhalt

**Header-Logo:** „KA" (identisch zu vorherigem Frame)

**Betreff/Heading:** Reservation Updated

**Bild:** identisches Speisen-Banner

**Reservierungsdetails:**

| Feld | Wert |
|---|---|
| Datum | 17 Jun |
| Restaurant | Restaurant Durrani |
| Kategorie | Upcoming reservation (grün) |
| Reservation for | 2 |
| Tag/Zeit | Wed . 22:30 CET |
| State | approved |

**Kein CALL-Button sichtbar** (unterhalb abgeschnitten oder nicht vorhanden in dieser Variante)

**Footer-Zeile:** „In partnership with KADiCon"

---

**Vergleich 00.10.02 vs 00.14.55:**  
Beide E-Mails haben dasselbe Template. Unterschied: Datum (16 Jun Tue vs 17 Jun Wed), Empfänger (mich vs info), zweite E-Mail zeigt Footer „In partnership with KADiCon", kein CALL-Button sichtbar.

---

### Bildschirmfoto 2026-06-15 um 00.41.30.png — SUBSTANZ: AWS IAM — Neuer Benutzer „aria-automation" — Review and create

**Tool/App:** AWS IAM Console — Benutzer-Erstellungs-Wizard, Schritt: Review and create  
**URL:** (unklar, IAM Console)  

---

#### Abschnitt: User details

| Feld | Wert |
|---|---|
| User name | aria-automation |
| Console password type | None |
| Require password reset | No |

---

#### Abschnitt: Permissions summary

| Name | Type | Used as |
|---|---|---|
| aria-cost-readonly | Customer managed | Permissions policy |

Pagination: < 1 > (1 Policy total)

---

#### Abschnitt: Tags – optional

Text: "Tags are key-value pairs you can add to AWS resources to help identify, organize, or search for resources. Choose any tags you want to associate with this user."

Status: Keine Tags — Meldung: "No tags associated with the resource."

Button: **Add new tag**  
Limit-Hinweis: "You can add up to 50 more tags."

---

#### Aktions-Buttons (unten rechts)

- **Cancel** (Text-Link blau)
- **Previous** (outline blau)
- **Create user** (orange/gelb, primär)

---

### Bildschirmfoto 2026-06-15 um 02.09.30.png — SUBSTANZ: Webshare Proxy-Liste (Rotating Residential)

**Tool/App:** Webshare Dashboard — Proxy List  
**URL:** (unklar, webshare.io)  
**Produkt-Typ:** ROTATING RESIDENTIAL (Badge oben links)  

---

#### Header

- Badge: „ROTATING RESIDENTIAL" (grüner Badge)
- Button oben rechts: **Upgrade**
- Tabs: **All** | **Replaced**

---

#### Filter-Bereich

- **Authentication Method:** Username/Password ▼ (Dropdown)
- **Connection Method:** Backbone Connection ▼ (Dropdown)

---

#### Buttons

- **Download** (mit Download-Icon)
- **Countries** (mit Globe-Icon)

---

#### Tabelle: Proxy-Liste

Spalten:
- Proxy Address
- Port
- Username (geschwärzt)
- Password (geschwärzt)
- Country
- Last Checked

**Sichtbare Zeilen:**

| Proxy Address | Port | Country | Last Checked |
|---|---|---|---|
| p.webshare.io | 80 | United Kingdom | 37 minutes ago |
| p.webshare.io | 80 | Canada | 15 minutes ago |
| p.webshare.io | 80 | Germany | 1 hour ago |
| p.webshare.io | 80 | France | 1 hour ago |
| p.webshare.io | 80 | Australia | 3 hours ago |
| p.webshare.io | 80 | Netherlands | 3 hours ago |
| p.webshare.io | 80 | Italy | 1 hour ago |
| p.webshare.io | 80 | Spain | 1 hour ago |
| p.webshare.io | 80 | Belgium | 2 hours ago |
| p.webshare.io | 80 | Austria | 3 hours ago |
| p.webshare.io | 80 | Switzerland | 2 hours ago |
| p.webshare.io | 80 | Sweden | 2 hours ago |
| p.webshare.io | 80 | Norway | (unklar) |

Username und Password-Spalten sind vollständig geschwärzt (schwarze Balken).

Unten rechts: **Get Started** Chat-Button (grün).

---

### Bildschirmfoto 2026-06-15 um 02.29.25.png — SUBSTANZ: Webshare Proxy Settings (Rotating Residential)

**Tool/App:** Webshare Dashboard — Proxy Settings  
**URL:** (unklar, webshare.io)  

---

#### Layout

Linke Sidebar:
- Header: aseckzai@gmail.com / Settings
- **PRODUCTS**
  - Proxy Server (aufklappbar)
    - Proxy List — Badge: INACTIVE
  - Static Residential (aufklappbar)
  - Rotating Residential (aufklappbar, aktiv)
    - Endpoint Generator — Badge: NEW
    - Proxy List — Badge: ACTIVE
    - **Proxy Settings** ← aktiv
    - Stats
  - Plans & Pricing
  - Subscription (aufklappbar)
  - Referral
  - API
- Unten: „Enhance Browsing with Chrome Extension" + **Install it Free** (Button)

---

#### Hauptbereich: Proxy Settings

**Tabs:**
1. **General** ← aktiv
2. IP Authorizations
3. Sub-Users

---

#### Formular: General

| Feld | Typ | Wert |
|---|---|---|
| Proxy Username | Text | prpp (teilweise sichtbar, restlich durch Texteingabe verdeckt) |
| Proxy Password | Text | 6/9y (teilweise sichtbar) |
| Proxy Session Timeout | Zahl (3 Felder) | 8 hours / 0 minutes / 0 seconds |
| Proxy Idle Timeout | Zahl (3 Felder) | 0 hours / 15 minutes / 0 seconds |

**Hinweise:**
- Proxy Username: „Alpha-numeric and minimum 8 characters."
- Proxy Password: „Alpha-numeric and minimum 8 characters."
- Proxy Session Timeout: „Maximum length of time a single proxy connection can stay running. Must be between 1 minute and 24 hours."
- Proxy Idle Timeout: „Maximum length of time of inactivity before a proxy connection is terminated. Must be between 15 seconds and 2 hours."

**Button:** **Save Changes** (blau, primär)

---

### Bildschirmfoto 2026-06-15 um 11.28.25.png — SUBSTANZ: GitHub Projects — „Welcome to Projects" + Projektliste

**Tool/App:** GitHub — Projects-Seite  
**URL:** (unklar, github.com)  
**Theme:** Dark Mode  

---

#### Onboarding-Banner (dismissbar mit X)

Titel: **Welcome to Projects**  
Text: "Built to be flexible and adaptable, Projects gives you a live canvas to filter, sort, and group issues and pull requests in a table, board, or roadmap. Tailor them to your needs with custom fields, saved views, workflows, and insights."

Button: **Learn more**

---

#### Filter/Suche

- Suchfeld: `is:open` (aktiver Suchterm)
- Button: **Link a project** (+ Icon, blau, oben rechts)

---

#### Projekteliste

Tabs: **Open 1** | Closed 0  
Sortierung: **Sort ▼** (Dropdown)

**Projekte:**

| # | Name | Typ | Status | Letzte Änderung |
|---|---|---|---|---|
| 1 | @SupplierPulse | Private | – | #1 updated 1 hour ago |

---

### Bildschirmfoto 2026-06-15 um 11.28.43.png — SUBSTANZ: GitHub Projects — @SupplierPulse Backlog/Board

**Tool/App:** GitHub — Projects — @SupplierPulse (Tabellen-Ansicht)  
**URL:** (unklar, github.com)  
**Kontext:** georg-zepf_adesose / Projects / @SupplierPulse  

---

#### Header

Breadcrumb: georg-zepf_adesose / Projects / @SupplierPulse  
Schloss-Icon (privates Projekt)  
Button: **Add status update** (oben rechts)  
**Users managed by:** adesso  

---

#### View-Tabs / Navigation

1. **Backlog** ← aktiv (mit Tabellen-Icon)
2. Board
3. Current Iteration
4. Roadmap
5. My items
6. + New view

---

#### Werkzeug-Leiste

- Filter-Feld: „Filter by keyword or by field"
- **View ▼** (Button oben rechts)
- Insights-Tab | Workflows 7 (Zahl-Badge)

---

#### Spalten der Tabelle

(von links nach rechts)
- Title
- Assignees
- Status
- Linked pull requests
- Sub-issues progress
- Iteration
- Estimate
- Start date
- Target date
- + (weiteres Feld hinzufügen)

---

#### Zeilen / Issues

**Gruppe: (Empty issues) — 3 Items — Estimate: 0**

| # | Issue | Assignee | Status |
|---|---|---|---|
| 1 | empty #9 | – | (Empty issues) |

---

**Gruppe: Todo — 3 Items — Estimate: 3**  
Hinweis: „This item hasn't been started"

| # | Issue | Assignee | Status |
|---|---|---|---|
| 2 | Meeting-Transkript vom 11.06 #7 | – | Todo |
| 3 | E01-E04 generieren via RE-Agent #8 | – | Todo |
| 4 | [FEATURE] Agentisches Team Setup #13 | – | Todo |

---

**Gruppe: In progress — 3 Items — Estimate: 0**  
Hinweis: „This is actively being worked on"

| # | Issue | Assignee | Status | Linked PR | Sub-issues |
|---|---|---|---|---|---|
| 5 | [FEATURE] GitHub MCP einrichten #2 | ensar-dautovic_adesose | In progress | #4 | – |
| 6 | [TASK] Externalize repo reference as variable + add .env.example #3 | ensar-dautovic_adesose | In progress | #4 | – |
| 7 | Grundlegendes agentisches Setup des Repos #11 | georg-zepf_adesose | In progress | – | 0/2 (Fortschrittsbalken 0%) |

---

**Gruppe: Done — 1 Item — Estimate: 0**  
Hinweis: „This has been completed"

| # | Issue | Assignee | Status |
|---|---|---|---|
| 8 | [FEATURE] Code-Review Standards & CI/CD Pipeline Setup #14 | – | Done |

---

### Bildschirmfoto 2026-06-15 um 12.00.49.png — NOISE: Privater Chat-Verlauf

Privater Nachrichten-Austausch (Kohn Robert, MD-54) über Südfrankreich-Urlaub und Gesundheitszustand. Keine App/Tool/Produkt-relevante Information.

---

### Bildschirmfoto 2026-06-15 um 15.08.09.png — SUBSTANZ: BMW B2B Portal — Onboarding-Anleitung / Dokumentation (Tabelle)

**Tool/App:** Dokument / Tabellen-Anleitung (Screenshot eines Dokuments, kein Browser-UI)  
**Inhalt:** Schritt-für-Schritt-Registrierungsanleitung für BMW B2B-Portal für externe Mitarbeiter  

---

#### Tabelle: Onboarding-Schritte

Spalten: **No** | **What** | **Who** | **How to**

| No | What | Who | How to |
|---|---|---|---|
| 01 | Self-registration for the BMW B2B Portal | external employee | Visit the BMW Group B2B Portal via URL (unklar, Button zu klein). Click on the button via `https://b2b.bmwgroup.com`. |
| 02 | Create C/I Account at the partner company | Master admin active employee | The employee is responsible for the authorizations in the partner systems. Note: After the self-registration must be confirmed by the master admin at the partner company for a C/I account to be assigned to the applicant. |
| 03 | Confirm the BMW B2B Portal registration | master admin at the BMW B2B Portal active employee | As soon as the account has been set up and confirmed, the new employee will receive an e-mail from the system-admin authorizes you to log in to the B2B portal of BMW Group. The account is linked to the C/I number the master admin authorizes for this account. |
| 04 | Role assignments in the BMW Group | master admin active employee | As soon as you have confirmed the logon to the B2B portal, you will receive your C/I account to your internal BMW contact. The IT technical user name — the so-called Q-number — is the Windows role that is automatically assigned to the newly created account. |
| (unklar) | Request roles in RightNow | internal BMW employee | When the „Add members" to the persons in contact, select the correct account assigned to the Partner access. It's also in RightNow: Maintain a contact — from point (unklar). See also RightNow handbook. |

**Hinweis:** Der untere Teil des Dokuments ist teilweise abgeschnitten. Letzter erkennbarer Text: „See also the RightNow handbook."

---

### Bildschirmfoto 2026-06-15 um 16.17.08.png — SUBSTANZ: BMW B2B / RightNow — Projekt-Verwaltungssystem „CNT-17009 SupplierPulse"

**Tool/App:** BMW RightNow / B2B Projektmanagement-System (internes BMW-Tool, webbasiert)  
**URL-Fragment:** (internes System, nicht sichtbar)  
**Projektkennung:** CNT-17009  
**Projektstatus:** Aktiv  
**Sternmarkiert:** Ja  

---

#### Linke Sidebar — Projekt-Metadaten

| Feld | Wert |
|---|---|
| Projektnummer | CNT-17009 |
| Projektstatus | Aktiv |
| Projektname | SupplierPulse |
| Unternehmen | ADESSO SE |
| Projekt Enddatum | 31. Dezember 2027 |
| Partner Kontakt | David Koenig, (ext.) |
| BMW Kontakt | Kais Aseckzai, MO-23 |

---

#### Sidebar-Navigation (Menü unterhalb Metadaten)

- Projektübersicht
- Projektbasisdaten
- **Projektrollen und Anwender** ← aktiv
- Berichte:
  - Applikationen (Badge: 16)
  - Rechte und Rollen (Badge: 0)
  - XenApps (Badge: 0)
  - HSA (Badge: 0)
  - VDI (Badge: 0)
  - VDI.Next (Badge: 0)
  - Firewallfreischaltungen (Badge: 0)
  - ESFT (Badge: 0)
- Notizen und Dokumente

---

#### Hauptbereich: Projektrollen

**Überschrift:** Projektrollen

**Bestehende Projektrolle — Card:**

| Feld | Wert |
|---|---|
| Rollenname | Entwickler |
| Status | Aktiv (Badge grün) |
| Beschreibung | Der DL ist beauftragt die Applikation SupplierPulse zu entwickeln auf... |
| Bestellungen | Germany (Germany ...) |
| Kosten (Nutzer pro Monat) | 63,14 € |

Buttons in der Card:
- **Details**
- **Bearbeiten**
- **Nutzer zuweisen** (blau, primär)

**Neue Projektrolle erstellen:** Plus-Icon-Card (+ in türkisem Kreis, Beschriftung „Neue Projektrolle erstellen")

---

#### Hauptbereich: Anwender

**Überschrift:** Anwender

**Tabelle-Spalten:**
- Q-Nummer (Sortier-Arrow, Suchfeld)
- Name (Sortier-Arrow, Suchfeld)
- BMW E-Mail-Adresse (Sortier-Arrow, Suchfeld)
- Lieferant (Sortier-Arrow, Suchfeld)
- Projektrollen

**Sichtbare Zeilen:**

| Q-Nummer | Name | BMW E-Mail-Adresse | Lieferant | Projektrollen |
|---|---|---|---|---|
| QXZ5SQC | Benjamin Janisch, FG-... | Benjamin.JA.Janisch@... | ADESSO SE | Entwickler × |
| QXZ57WD | David Koenig, FG-45-... | David.DK.Koenig@par... | ADESSO SE | Entwickler × |
| QXZ6K2T | Ensar Dautovic, FG-4-... | Ensar.Dautovic@part... | ADESSO SE | Entwickler (kein × sichtbar) |
| QXZ2S2T | Georg Zepf, DE-500 (... | Georg.Zepf@partner... | ADESSO SE | Entwickler × |

**Gesamt:** 1 bis 4 von 4

**Bulk-Aktionen:**
- Checkbox „Alle auswählen"
- Dropdown (Aktion auswählen)
- Button: **Ausführen**

**Pagination:** << < 1 bis 4 von 4 > >>

Button: **Als CSV exportieren**

---

### Bildschirmfoto 2026-06-15 um 16.33.03.png — SUBSTANZ: BMW G65 Supplier Launch Readiness Program — Folie (CONFIDENTIAL)

**Tool/App:** Präsentation (PowerPoint/PDF) — BMW interne Unterlage  
**Foliennummer:** 2  
**Betreff:** G65 SUPPLIER LAUNCH READINESS PROGRAM — WEBASTO SKYROOF — IRAPUATO  
**Target Date:** 29.05.2026  
**Closure Date:** (grün markiert, Datum teilweise unklar — vermutlich erfüllt)  
**Stempel:** CONFIDENTIAL  

---

#### Layout

Tabelle mit 4 Spalten:
- Focus Area
- Observations
- Recommendation
- Result / Effect

---

#### Inhalt

**Focus Area:** Execution & Shopfloor

**Observations:**
- Encapsulation: capacity plan does not cover current peak volume (incl. 20% flex); Planned+ NOX parts in final assy. (7%) are not considered in demand for pre-process encapsulation.
- Encapsulation: Utilization exceeds >100% per tool at GP3 process.
- Bottleneck: encapsulation process (GP3) with achieved average CT of 194s and OEE of 83%.

**Recommendation:**
- Update capacity planning to include NOK/rework loop (7%) impacting encapsulation pre-process.
- Resolve capacity constraints (tools/lines/shifts) and balancing.
- Show planned actions to achieve CT and OEE at GP3 encapsulation.

**Result / Effect (Textbox rechts):**
„The PU capacity is calculated in KapaTool with the 80% OLE assumption as indicated in the file as maximum OLE. This is the main driver that we noted that we would have to work some Saturdays when the peak volumes come. It is well documented that the Webasto IR plant averages 90% OLE in PU area."

**Improvement:**
- N/A
- N/A

**Before/After Vergleich:**

*Before-Tabelle (teilweise sichtbar, viele Zahlen):*
- Capacity critical processes: (mehrere Metriken sichtbar aber zu klein für vollständige Werte)

*After-Tabelle (teilweise sichtbar):*
- Encapsulation zielwert: (unklar, grün markierte Felder)

---

**Footer:** G65 Supplier Launch Readiness Program | MO-1G, MO-2, MO-5, MP | 1 June, 2026 — CONFIDENTIAL

---

### Bildschirmfoto 2026-06-15 um 16.34.51.png — SUBSTANZ: BMW G65 Supplier Launch Readiness Program — Folie 5 (CONFIDENTIAL)

**Tool/App:** Präsentation (PowerPoint/PDF) — BMW interne Unterlage  
**Foliennummer:** 5  
**Titel:** PRE ASSEMBLY – ENCAPSULATION TOOL CAPACITY – ORIGINAL ASSUMPTIONS  
**Stempel:** CONFIDENTIAL  

---

#### Layout

Linke Hälfte: Kapazitätstabelle  
Rechte Hälfte: Bullet-Liste mit Annahmen

---

#### Tabelle: Tool Capacity

Spalten: (Zeilen-Label) | **Encapsulation** | **Glueing / Adhesive** | **Assembly**

**Kopfzeile:**
- 1082 / bestätigt (gelb markiert)
- 5412 / bestätigt (gelb markiert)

| Zeile | Encapsulation | Glueing/Adhesive | Assembly |
|---|---|---|---|
| (IR) | IR | IR | IR |
| 15.75 | 15.75 | 15.75 | 15.75 |
| 7.22 | 7.22 | 7.22 | 7.22 |
| 3x8 | 3x8 | 3x8 | 3x8 |
| 800% | 800% | 200% | 200% |
| 458.4 | 120 | 120 | – |
| 240 | 240 | 240 | – |
| 5 | 5 | 5 | 5 |
| 93% | 93% | 93% | 93% |
| 93% | 93% | 93% | 93% |
| 93% | 93% | 93% | – |
| **max. 80%** | **80%** | 80% | 80% |
| (leer) | **1143** | **1092** | **1092** |
| (leer) | **5716** | **5458** | **5458** |
| ja | – | – | – |

---

#### Bullet-Liste: Annahmen

- 3 sets of tools
- 8 total carriers (3 dedicated for rear glass; 2 dedicated to Front Glass, 2 dedicated to Moveable Glass and 1 shared between moveable glass and front glass)
- Assumed OLE 80% (Max as noted in KapaTool)
- Front GP Cycle time: 130 second (22.15pph)
- Moveable Glass CT: 150 seconds (19.2pph)
- Rear Glass Cycle time: 180 seconds (16pph)
- Some Saturdays are required during peak volume

**Footer:** G65 Supplier Launch Readiness Program | MO-1G, MO-2, MO-5, MP | 1 June, 2026 — CONFIDENTIAL

---

## Zusammenfassung

**Substanz-Screens:** 13  
**NOISE:** 1 (12.00.49 — privater Chat)  
**Zusammengeführte Gruppen:** 2 (IAM terraform = 3 Frames; ECS backend-production = 4 Frames)