Recover the Cyber Attack
1- Utilize filezilla to backup the server - DONE
2- Utilize NaviCAT and copy the entire database - DONE
1- I dumped the database files and analyzed.
All the files are now at /Users/jaydenbay/Desktop/BCS_5_23_2026
And also /Users/jaydenbay/Desktop/BCS_Recovery
I have couple more entries to check but mainly recovered with minimum data loss.
If for some reason you prefer to utilize a database you can create tables under this database: u773187720_IRIS. Each time you need to create a table please make sure another table with the same name doesn't exist there. The tables you created must be efficient and minimalist.
Name
Iris
Role
Autonomous assistant that executes tasks directly, with minimal clarification, and concise output.
System / Instruction Prompt (recommended)
You are Iris, an autonomous assistant.
Your job is to complete tasks efficiently and correctly.
Rules:
- Be obedient and task-focused.
- Do not ask follow-up questions unless absolutely required to proceed.
- Make reasonable assumptions when information is missing.
- Prefer action over explanation.
- Be concise and precise.
- Avoid long descriptions, background, or theory.
- Output only what is needed to complete the task.
- Use bullet points or numbered steps when giving instructions.
- If multiple solutions exist, choose the most practical one.
- Do not add commentary, opinions, or extra context unless asked.
Response Style Guidelines
• Length: Short
• Tone: Neutral, professional
• Formatting:
• Lists > paragraphs
• No emojis
• No filler phrases
• Default structure:
• Result first
• Steps only if necessary
Example:
Done.
Steps:
1. X
2. Y
3. Z
Autonomy Rules
Iris should:
• Proceed without confirmation unless blocked
• Infer intent from context
• Choose defaults silently
• Flag blockers only when unavoidable
Use this format for blockers:
Blocked: missing API key.
Required: API_KEY value.
What Iris Should NOT Do
• Ask “Do you want me to…”
• Over-explain
• Provide multiple alternatives unless requested
• Add summaries like “Let me know if you need more help”
If you want, I can:
• Tighten this further (even more terse)
• Adapt it specifically for OpenClaw syntax
• Add a command-mode (e.g. /run, /plan, /fix)
Just say the word.
#
Topic
Best Conceptual YouTube Video
1
Harvard vs Von Neumann
https://www.youtube.com/watch?v=Er15cA9wnH0
2
ARM Cortex-M/R/A Families
https://www.youtube.com/watch?v=rDvLaOe5_Ws
3
Clock Systems & PLLs
https://www.youtube.com/playlist?list=PLgwJf8NK-2e5-QInY0r0VZSQCOri3mAss
4
Memory Types
https://www.youtube.com/watch?v=KcVfQy1WbZc
5
Memory Mapping & Linker Scripts
https://www.youtube.com/watch?v=5xGZKzK7G8I
6
GPIO Architecture
https://www.youtube.com/watch?v=1nYv6gQfQ6I
7
Interrupt Controllers (NVIC)
https://www.youtube.com/watch?v=KXfC3QpFZ9E
8
Timers & Counters
https://www.youtube.com/watch?v=QJzX9xJ5h2I
9
ADC (SAR vs Sigma-Delta)
https://www.youtube.com/watch?v=EnU6n5v2M0E
10
DAC Fundamentals
https://www.youtube.com/watch?v=5z5N8pQ9B3o
11
Watchdog Timers
https://www.youtube.com/watch?v=ZyQz8kG1ZgE
12
Power Management & Sleep
https://www.youtube.com/watch?v=F9W5Zt2X7E8
13
Voltage Regulators & PI
https://www.youtube.com/watch?v=QG0F6J6Yc9U
14
Reset & Brown-Out
https://www.youtube.com/watch?v=Kqz0k8U8kBU
15
AEC-Q100
https://www.youtube.com/watch?v=QmQpGZCzL8A
16
EMI / EMC
https://www.youtube.com/watch?v=R0z7Z2G7X8k
17
Temperature & Reliability
https://www.youtube.com/watch?v=ZzFJcWzC9G4
18
PCB Design
https://www.youtube.com/watch?v=ySuUZEjARPY
19
Hardware Bring-Up & Debug
https://www.youtube.com/watch?v=2d7Wk2kI1xY
20
Sensors & Actuators
https://www.youtube.com/watch?v=R0n0Y3Zz2Jk
(Curated from AUTOSAR practice, ISO standards, OEM requirements, and Tier-1 supplier expectations)
Microcontroller Architecture (Harvard vs Von Neumann)
Automotive Microcontrollers (ARM Cortex-M/R/A families)
Clock Systems & PLLs
Memory Types (Flash, SRAM, EEPROM, NVRAM)
Memory Mapping & Linker Scripts
GPIO Architecture & Electrical Characteristics
Interrupt Controllers (NVIC, priority levels)
Timers & Counters (PWM, Input Capture, Output Compare)
ADC Fundamentals (SAR, Sigma-Delta)
DAC Fundamentals
Watchdog Timers (Windowed & Independent)
Power Management & Sleep Modes
Voltage Regulators & Power Integrity
Reset Sources & Brown-Out Detection
Automotive Grade ICs (AEC-Q100)
EMI/EMC Considerations
Temperature & Reliability Constraints
PCB Design for Embedded Systems
Hardware Bring-Up & Debug Interfaces (JTAG, SWD)
Automotive Sensors & Actuators Overview
Bare-Metal Programming
Startup Code & Boot Sequence
Linker Scripts (Memory Layout Control)
Interrupt Service Routines (ISR Design)
Register-Level Programming
Drivers vs HAL vs BSP
Polling vs Interrupt vs DMA
DMA Controllers
Peripheral Initialization Order
Firmware Update Mechanisms
Bootloaders (CAN, UDS, OTA)
Flash Programming & Wear Leveling
Low-Power Firmware Design
Exception Handling & Fault Registers
Debugging Embedded Firmware
Real-Time System Fundamentals
Hard vs Firm vs Soft Real-Time Constraints
Task Scheduling Algorithms
Preemptive vs Cooperative Scheduling
Context Switching
RTOS Architecture (Kernel, Scheduler, HAL)
Inter-Task Communication (Queues, Mailboxes)
Synchronization (Mutexes, Semaphores, Spinlocks)
Priority Inversion & Inheritance
Timing Analysis & WCET
Memory Management in RTOS
Automotive RTOS (OSEK, AUTOSAR OS)
Stack Sizing & Overflow Detection
Multicore RTOS Concepts
Safety-Critical Task Design
CAN Bus Fundamentals
CAN FD
LIN Protocol
FlexRay
Automotive Ethernet
SPI Protocol (Master/Slave Timing)
I2C Protocol
UART & Serial Communication
Network Topologies in Vehicles
Message Arbitration & Priority
Bus Load Calculation
Error Detection & Handling
Gateway ECUs
Time-Triggered vs Event-Triggered Communication
Diagnostics Communication Overview
AUTOSAR Classic Platform
AUTOSAR Adaptive Platform
Layered Software Architecture
ECU Software Architecture
BSW (Basic Software) Concepts
RTE (Runtime Environment)
Software Components (SWC)
Configuration vs Code Generation
Legacy vs AUTOSAR Migration
Model-Based Development (MATLAB/Simulink)
Functional Safety Fundamentals
ISO 26262 Overview
ASIL Levels (A–D)
Hazard Analysis & Risk Assessment (HARA)
Safety Goals & Safety Requirements
Fault Tree Analysis (FTA)
Failure Modes and Effects Analysis (FMEA)
Safety Mechanisms (End-to-End Protection)
Redundancy & Diversity
Safety-Certified Software Development
On-Board Diagnostics (OBD-II)
UDS (ISO 14229)
Diagnostic Trouble Codes (DTC)
ECU Flashing & Reprogramming
Secure Boot
Hardware Security Modules (HSM)
Cryptography Basics for Embedded Systems
Secure Communication (TLS for Automotive)
Intrusion Detection in Vehicles
Fault Tolerance Techniques
Error Correcting Codes (ECC)
Logging & Traceability
Automotive Cybersecurity Standards (ISO 21434)
Over-the-Air (OTA) Updates
Software Lifecycle & ASPICE
Microcontroller Architecture in Safety-Critical Automotive Embedded Systems**
This chapter establishes the architectural foundations of microcontrollers used in automotive Electronic Control Units (ECUs). The goal is not to describe what a microcontroller contains, but to explain why its architecture is structured the way it is, and how architectural decisions propagate upward into software design, timing guarantees, safety analysis, and system certification.
After completing this chapter, the reader will be able to:
Formally reason about microcontroller execution models
Analyze architectural trade-offs affecting determinism and safety
Understand how hardware architecture constrains software structure
Prepare for real-time scheduling, RTOS design, and AUTOSAR concepts
Automotive ECUs are best modeled as deterministic reactive systems:
They continuously react to external stimuli
They must respond within bounded time
Correctness depends on both value and time
This immediately distinguishes automotive embedded systems from:
Desktop computing (throughput-oriented)
Cloud systems (latency-tolerant)
Mobile devices (best-effort scheduling)
A microcontroller architecture for automotive systems must therefore satisfy:
\text{Correctness} = f(\text{Logical correctness}, \text{Timing correctness})
This fundamental equation drives every architectural choice discussed in this chapter.
An automotive ECU is not a computer. It is a closed-loop control system.
Formally, an ECU implements:
u(t) = C(x(t), r(t), s(t))
Where:
x(t) = sensor inputs
r(t) = reference values
s(t) = system state
u(t) = actuator outputs
The microcontroller is responsible for:
Sampling x(t)
Computing control logic C
Producing u(t) within strict deadlines
Detecting faults and transitioning to safe states
Thus, the microcontroller is not merely a processor — it is the temporal coordinator of the ECU.
A microcontroller is formally defined as:
A single-chip computing system integrating processing, memory, peripherals, and timing mechanisms designed for deterministic, real-time interaction with the physical environment.
This definition implies architectural constraints absent in general-purpose CPUs.
The CPU core defines:
Instruction set architecture (ISA)
Execution pipeline
Interrupt and exception behavior
Automotive CPUs prioritize:
Bounded interrupt latency
Predictable pipeline behavior
Minimal speculative execution
This is why deep pipelines, out-of-order execution, and aggressive speculation are either limited or entirely absent.
Memory architecture is defined by:
Address space partitioning
Access latency characteristics
Fault detection mechanisms
In automotive systems, memory is architecturally divided into:
Program memory (Flash)
Data memory (SRAM)
Peripheral address space
Safety and diagnostic regions
This partitioning enables static analyzability, a prerequisite for ISO 26262 certification.
Peripherals should not be viewed as “I/O devices” but as specialized hardware accelerators that:
Offload real-time tasks from the CPU
Reduce timing jitter
Enforce hardware-level determinism
For example:
Timers enforce temporal correctness
DMA enforces bounded data transfer latency
CAN controllers enforce protocol correctness
In a pure Von Neumann architecture:
Single memory space
Single access path
Sequential fetch-execute behavior
This introduces the Von Neumann bottleneck, defined as:
T_{\text{cycle}} = T_{\text{instruction}} + T_{\text{data}}
This unpredictability makes pure Von Neumann architectures unsuitable for hard real-time automotive systems.
Harvard architectures eliminate contention by separating:
Instruction fetch
Data access
This allows:
T_{\text{cycle}} = \max(T_{\text{instruction}}, T_{\text{data}})
This bounded behavior is essential for Worst-Case Execution Time (WCET) analysis.
Modern automotive MCUs implement modified Harvard architectures, combining:
Separate physical memories
Controlled interconnects (bus matrices)
Predictable arbitration
The key design goal is:
Preserve software flexibility while maintaining analyzable timing behavior.
In automotive systems:
Interrupts are not exceptional
They are the primary control-flow mechanism
Architectural requirements:
Fully nested interrupts
Static priority assignment
Bounded latency guarantees
Interrupt architecture directly constrains:
RTOS design
Task preemption
Safety monitoring reaction time
Thus, interrupt controllers are architectural primitives, not peripherals.
Time is a first-class system resource in automotive ECUs.
Architectural time sources include:
CPU clock
Peripheral clocks
Independent watchdog clocks
Design goals:
Detect clock drift
Tolerate oscillator failure
Support multi-rate systems
Without this temporal architecture, real-time guarantees collapse.
Automotive microcontrollers embed safety mechanisms at the architectural level:
Lockstep execution
Memory ECC
Redundant clock domains
Fault injection logic
Hardware self-tests
These mechanisms are not optional; they are architecturally mandated by ISO 26262.
Dimension
Automotive Priority
Performance
Bounded, not peak
Memory
Predictable, not large
Caching
Deterministic, not aggressive
Power
Stable, not minimal
Cost
Controlled, not minimal
This leads to a defining principle:
Automotive architecture optimizes predictability under fault rather than performance under ideal conditions.
Every subsequent topic depends on the architectural assumptions established here:
RTOS scheduling relies on interrupt determinism
AUTOSAR depends on memory partitioning
Functional safety depends on architectural redundancy
Communication stacks depend on peripheral autonomy
If you do not understand microcontroller architecture, you cannot reason correctly about:
Deadlines
Race conditions
Safety violations
System certification
Explain why out-of-order execution is fundamentally incompatible with hard real-time guarantees.
Derive how memory arbitration affects WCET in a modified Harvard architecture.
Argue whether caches can ever be fully deterministic.
Explain why peripherals are architecturally closer to co-processors than I/O devices.
Chapter 2: Automotive Microcontrollers and CPU Families
will rigorously analyze ARM Cortex-M, Cortex-R, and Cortex-A from an architectural suitability standpoint, not a marketing one.
What you are building is not a tutorial.
It is a reference-grade engineering text.
Role & Objective
You are a senior full-stack web application architect and engineer. Design and implement a complete, secure, and extensible web-based Prediction Tracking Application using PHP (backend), MySQL (database), and JavaScript (frontend). The system allows a single user (initially) to record predictions about stocks, life events, or other outcomes, track progress over time, and evaluate accuracy after the target date.
The application functions as a prediction journal + outcome evaluator.
Users can:
Record predictions
Update them over time
Assign confidence and trend status
Mark final outcomes
Review historical accuracy
Each prediction must store the following:
Required Fields
prediction_id (auto-increment primary key)
title (short descriptive title)
prediction_text (detailed description of the prediction)
category (enum/string: Stock Market, Finance, Career, Health, Personal, Custom)
prediction_date (date prediction was made)
target_date (date when outcome is expected)
confidence_level (integer 1–5)
trend_indicator (see Trend Levels below)
status (Active, Resolved, Abandoned)
Optional but Recommended
symbol_or_reference (e.g., stock ticker, event reference)
expected_value (numeric or text, e.g., price target)
actual_value (filled once resolved)
notes (free-form text)
created_at, updated_at
Implement a 5-level standardized trend system to reflect how the prediction is tracking:
Strong Miss – Outcome clearly moving far away from prediction
Miss – Likely to fall short
Uncertain / Flat – No clear direction yet
On Track – Progressing as expected
Strong Hit – Exceeding expectations
Store this as:
Integer (1–5)
Display with color coding (red → green)
Users must be able to add time-stamped updates to each prediction.
Each update stores:
update_id
prediction_id (FK)
update_date
commentary (what changed, new insight, reasoning)
trend_indicator_at_update
confidence_level_at_update
Updates must:
Never overwrite past data
Be shown in chronological order
Serve as an audit trail of thinking over time
When the target date is reached or manually triggered:
Prediction can be marked Resolved
User selects final outcome:
Black Swan
Welcomed Surprise
Hit
Near Miss
Strong Miss
Final notes and actual value can be entered
Final trend indicator is locked
List of Active Predictions
Filters by:
Category
Trend Indicator
Confidence Level
Target Date (past / upcoming)
Visual indicators (icons, colors)
Full prediction info
Timeline of updates
Trend history visualization
Edit / Add Update actions
Resolved predictions
Accuracy summary:
% Hit / Miss
Confidence vs outcome correlation
Optional charts (JS-based)
REST-style endpoints:
create_prediction.php
update_prediction.php
add_update.php
get_predictions.php
resolve_prediction.php
Use prepared statements (PDO or MySQLi)
Server-side validation
Simple authentication placeholder (single-user for now)
Tables
predictions
prediction_updates
(Optional future) users
Include:
Proper indexing on dates and foreign keys
Cascading deletes for updates
Clean, minimalist UI
Forms with validation
Dynamic updates without page reload (AJAX / fetch)
Color-coded trend indicators
Mobile-friendly layout
Secure input handling (XSS / SQL injection safe)
Modular and extensible codebase
Designed for future:
Multi-user support
Prediction scoring algorithms
Export to CSV
AI-assisted prediction review
Confidence decay over time
Reminder notifications before target date
Accuracy scoring per category
“Post-mortem” reflection field after resolution
Tagging system
Dark mode
Produce:
Database schema (SQL)
PHP backend files
JavaScript frontend logic
Basic HTML UI templates
Clear setup instructions
Comments explaining architectural decisions
End Goal
Deliver a fully working, local-hostable web application that acts as a long-term personal prediction tracking system with accountability, history, and insight into decision-making accuracy.
Please provide me the full system code including the MySQL schema/script.
Please also add/suggest quant finance–specific features (price thresholds, percent moves, time decay)
You are a senior full-stack software architect, quant-finance system designer, and production engineer.
Your task is to design and fully implement a complete web-based Prediction Tracking & Accuracy Scoring Application called BFEM Prediction Tool, delivered with working source code using:
PHP (backend)
MySQL (database)
JavaScript (frontend)
HTML / CSS (UI)
The system must run on a standard PHP/MySQL hosting environment and be fully functional upon deployment.
Build a Prediction Ledger that records forecasts, tracks evolving confidence, evaluates outcomes using structured taxonomy, and computes quantitative accuracy scores over time.
This is not a demo or conceptual design — you must output complete executable code, schemas, and instructions.
Each prediction must store:
prediction_id (INT, PK, auto-increment)
title (VARCHAR)
prediction_text (TEXT)
category (ENUM: Stock, Macro, Career, Health, Personal, Custom)
prediction_date (DATE)
target_date (DATE)
confidence_level (INT 1–5)
trend_indicator (INT 1–5)
status (ENUM: Active, Resolved, Abandoned)
asset_symbol (VARCHAR, nullable)
starting_price (DECIMAL)
target_price (DECIMAL)
price_threshold_upper (DECIMAL)
price_threshold_lower (DECIMAL)
expected_percent_move (DECIMAL)
actual_price (DECIMAL, nullable)
actual_percent_move (DECIMAL, nullable)
time_decay_model (ENUM: Linear, Exponential, None)
time_weighted_score (DECIMAL)
notes (TEXT)
created_at
updated_at
Used during the life of a prediction:
Strongly Diverging
Diverging
Flat / Uncertain
Tracking Well
Exceeding Expectations
Stored as INT (1–5) with visual color coding.
Each update records:
update_id (PK)
prediction_id (FK)
update_date
commentary
trend_indicator_at_update
confidence_level_at_update
observed_price
observed_percent_move
Rules:
Append-only
No edits to historical data
Full audit trail
When resolving a prediction, user must select exactly one:
Black Swan
Welcomed Surprise
Hit
Near Miss
Strong Miss
Stored fields:
final_outcome
final_notes
resolved_at
After resolution:
Prediction becomes read-only
Outcome is immutable
actual_percent_move = (actual_price - starting_price) / starting_price × 100
Hit target
Breach upper threshold
Breach lower threshold
Remain neutral
You MUST implement and persist an accuracy score per prediction.
Component Weight Directional Accuracy 40% Magnitude Accuracy 30% Timing Accuracy 20% Confidence Calibration 10%
Total score range: 0.0 – 100.0
If direction correct → 40 If near miss → 25 If incorrect → 0
magnitude_error = |actual_percent_move - expected_percent_move| score = max(0, 30 - (magnitude_error × k))
Where k is a tunable constant (default: 0.5).
timing_error_days = |resolved_date - target_date| score = max(0, 20 - timing_error_days)
Cap minimum at 0.
confidence_score = If high confidence & hit → +10 If high confidence & miss → 0 If low confidence & hit → +6 Else → +3
final_accuracy_score = direction_score + magnitude_score + timing_score + confidence_score
Store:
accuracy_score
Sub-component scores (optional but encouraged)
decayed_score = confidence × (remaining_days / total_days)
decayed_score = confidence × e^(−λ × elapsed_days)
Persist decay values for analytics.
Active predictions
Countdown timers
Trend indicators
Asset filters
Accuracy by category
Confidence vs accuracy
Outcome distribution
Black Swan frequency
Score trends over time
PDO with prepared statements
REST-style endpoints:
create_prediction.php
add_update.php
get_predictions.php
get_prediction_detail.php
resolve_prediction.php
calculate_accuracy.php
analytics.php
Business logic separated from routing
You MUST provide:
Full SQL schema
Indexes & constraints
ENUM definitions
Foreign keys
Seed data
Tables:
predictions
prediction_updates
Dynamic forms
AJAX / fetch API
Trend & score visualization
Charts (pure JS)
You MUST output:
Complete MySQL schema + setup script
All PHP backend files
Frontend JavaScript
HTML/CSS templates
Setup & deployment instructions
Clear inline comments
Do not summarize.
Do not omit code.
This must be deployable and functional.
Deliver a fully working Prediction Ledger with Quant Accuracy Scoring, enabling long-term accountability, statistical review, and decision-quality improvement across financial and life forecasts.
In your environment, diversity isn’t about titles or org charts — it’s about where friction and insight live.
You have six natural perspective lenses already. Use them deliberately:
👉 Innovation happens at the seams between these views, not inside one role.
Your job is to force those seams to talk in safe, repeatable ways.
Open brainstorming fails in systems teams. Senior voices dominate, juniors stay quiet, and contractors disengage.
Instead, use designed forums with guardrails.
Purpose: Surface insights from failures, not successes.
Structure:
10 min — SWIL: What we built, what surprised us
15 min — CIE: What actually failed on bench & why
10 min — NATS: What this says about system health
10 min — Group: What would we change if this repeats?
Rules:
No root-cause debates
No ownership assignment
Focus on system, not person
💡 This gives junior SWILs and contractors a voice without challenging authority directly.
Pull-ahead builds are innovation killers unless you learn from them.
Create a 5-question template every time:
What forced the pull-ahead?
What risk did we accept knowingly?
What risk surprised us?
What helped us survive?
What would make this easier next time?
Rotate facilitation between SWIL → CIE → NATS.
You have a rare mix:
SWILs / CIEs at level 6–7
NATS at level 8 (peak IC)
Contractors (TCS) with deep legacy knowledge
Tell the team — explicitly:
“During delivery, hierarchy matters.
During learning, it doesn’t.”
Then enforce it.
Practical moves:
In learning forums, NATS speak last
In delivery calls, NATS decide fast
This single rule unlocks honest input from SWILs and contractors.
Right now, NATS are your escalation layer. That’s necessary — but insufficient.
Add one non-negotiable expectation:
Every NATS must surface one systemic improvement per quarter
(tooling, process, interface, or architectural guardrail)
Examples that fit your world:
A pre-build sanity gate for mixed-baseline builds
A “known unsafe combinations” registry
A lightweight controller health checklist before releases
This channels their experience into preventative innovation.
Contractors often stop innovating because:
They’re not invited early
They’re blamed late
Fix that with one deliberate move:
Must be a TCS SWIL
They present:
What legacy constraints are biting us now
What shortcuts we rely on
What would break if we removed them
This does two things:
Respects their knowledge
Protects MCU0/SDV from repeating old mistakes
Your north star isn’t ideas — it’s flow + resilience.
So measure innovation by:
Reduced rework after bench testing
Fewer emergency NATS escalations
Faster pull-ahead recoveries
Clearer build/release expectations
If an idea doesn’t move one of those, park it.
Month 1
Establish the two forums
Set the hierarchy rule
Clarify NATS expectations
Month 2
Rotate facilitators
Run 2–3 pull-ahead retros
Identify 1 systemic pain per domain
Month 3
Turn one pain into a concrete change
Communicate the win loudly
Tie it back to team learning
You’re not just building a team — you’re building a mini-SWIM function without the title.
If you want, next we can:
Draft a team charter that signals this shift
Design a Jira intake + prioritization lightweight model
Create a career growth map for SWIL → CIE → NATS paths
Engine, Transmission, Chassis Integration Team is responsible for integrating SW components to release vehicle level SW to downstream to calibrators and test engineers. My team consists of SWILs (Software Integration Leaders), CIEs (Controller Integration Engineers) and NATS (New Architecture Specialists). We are responsible for the Engine, Transmission and Chassis domains. Within Chassis Domain we also have the SDV projects. SDV projects are new and they are called MCU0 projects, we are responsible for SEAT, Closure and Auth modules. SWILs and CIEs could be 6 or 7th level within the organization hierarchy and NATS are 8th level as they are the highest level an engineer can get. We are also getting SWIL support from TCS team which is a contract company that works directly with us. They are mainly focusing on the legacy Engine and Transmission projects. From our local team we still support them with CIEs and NATS.
Our specific group gets the work from SWIMs (SW Integration Manager) in terms of Jira tickets and SWILs in my team builds, sanity checks and releases the SW as per the ticket. After the release the issues found mostly on the bench is debugged again the CIE members of the team. NATS are there to handle any request that is beyond the SWILs and CIEs as they are trying to get the operational status of controllers achieved at all times. We are a systems team and although we supposed to get cadence builds and requests in relation we also get pull ahead build requests where the new component have to be build with the old baseline of software in situations like when it is too risky to move to the latest software. Similarly the issues can pop up at any point which requires attention from CIEs or NATS.
I am setting up this team starting September 2025. Previously I was managing the SWIL team for all domains and we went through a reorganization and I ended up bringing the part of the SWIL team working on the Engine, Transmission, Chassis areas including MCU0s. On top I received same domain CIEs and NATS which was not part of my previous team. I don't have any SWIMs coordinating the work within and that role is provided by the larger organization. My goal is to create a performing team now kind of vertical including the integration with SWILs and issue resolution and support with CIEs and NATS.
Here is the roles and responsibilities for each role within my team as well as mission and primary customers:
Role 1: SWIL: Software Integration Leader (SWIL)
Mission: Build Integrated Vehicle Motion Control Software that exceeds customer expectations and business requirements.
Primary Customers: Calibration Community, Platform Teams
ROLES/RESPONSIBILITIES
• Integrate and build software for controller system releases and interim software builds
• Single point contact with controller supplier for software
• Assist in development of software content and software anomaly corrections as required
• Integration and verification testing of an integrated software build
• Prepare software for production release
• Manage controller resources for given ECU
• Oversee bench and instrumentation issue resolution
• Provide, communicate, and support common best practices among SWIL community
DELIVERABLES
• Software release including build products and instrumentation files
• Release notification communicated to team
• Changes from previous release
• main/secondary/boot/BSP compatibilities
• part numbers
• ARXML (Global B and GEM programs)
• Supplier software issue resolution
• Coordination of Software impact analysis of Controller Supplier exceptions and outstanding PCE’s with SME (For example, NATS, SWIM, TRB, Safety).
• Support for SWIM in Supplier software CR task scheduling for new GM CTRS requirements and BSP anomalies.
• Scheduling of and/or participation in BSP Controller Supplier software design and verification reviews.
• Mentoring to software team members
• Software review
• Communication of common anomaly corrections with SWIM & SWILs for other ECUs
• SW tested per SWIL checklist and procedures
• First-pass verification
• Compiler/linker/locator logs
• C Source Code Parser log
• Second-pass verification
• Bench/vehicle testing
• Software and calibration parts configuration managed
• Support for system calibration development
• Software released and posted according to process and SWET requirements
• Resolution of ROM, RAM, and Throughput constraint issues
• Resolution of software build proliferation issues
• Support for resolution of issues identified by calibration and platform teams
• Expedient resolution of bench problems
• Documentation (CRs) of requested process and tool updates
• Usage of common tools (e.g., tool catalog and make files)
• Active participation in SWILs Meeting
Role 2: CIE
Controller Integration Engineer (CIE)
Mission Statement: First responder to troubleshoot vehicle or bench level VMEC specific integration issues and recommend solutions.
Primary Customers: SWILs, SWIMs, Software Development Teams (ARTs / Value Streams), Software Execution Teams (SWET), Controller Integration Teams, Calibration and Vehicle teams, Test Environment providers
ROLES/RESPONSIBILITIES
• This role is responsible for vehicle embedded control system engineering with a primary focus on forming and leading cross-functional teams to troubleshoot issues through all the different life cycle stages (early development through launch and through end of production) on the full range of GM vehicles.
• Lead efforts to work closely with internal development teams including manufacturing, controls development, software, calibration, and testing activities, as well as other cross functional teams in tackling a wide variety of issues as they arise and plotting the best path towards resolution.
• Focus on vehicle system level integration issues including hardware, software, calibration, and vehicle wiring issues (including development activities, in-vehicle build events, buy-off rides, test trips, general fleet usage, durability, VeSCoM Checkout, etc.)
• Lead efforts and develop strategies to best support:
• Test Engineers when facing issues on bench or vehicle for testing (KBT, Milestone, etc.)
• Software support for calibration teams and development trips
• Assembly plant and field problem resolution.
• Test Environment Engineers in troubleshooting and commissioning HIL/SIL/SOLE systems for executing tests and developing operating scenarios to emulate vehicle functions.
• Controls development (SWAT, VIP, SDV, Infrastructure teams) as required.
• Basic Software Development team during emergency builds and testing (e.g., compliance updates)
• Prototype shop and dynos/durability cars / test & development fleets
• Evaluating controller field returns
• Controller rework/reflash (at Pre-PPO and PPO facilities)/Red X activities
• Vehicle software updates if users need help flashing software or investigating and resolving implementation issues.
• Analyze in-house software by applying debugging tools in troubleshooting issues in the ECU memory management, infrastructure operation and applications code.
• Respond to issues from PRTS, Defect Tracking, etc. and actively participate or lead the appropriate stakeholder priority discussion forums.
• Work on both internal SW testing issues and/or with suppliers in outsourced programs.
• Confirm resolution of CIE documented hardware and software anomalies.
• Act as point contact with Issue Resolution Teams and Technicians at PPO and Plants to implement processes that enable rapid problem resolution.
• Educate/train/support/mentor new and less experienced Controls Integration Engineers (CIE) and others learning about the tools and methods employed in this role.
• Develop new tools and processes supporting troubleshooting.
• Integrate and apply applicable Agile SAFe methods in CIE tasks.
DELIVERABLES
• Document hardware and software anomalies using JIRA (or similar database) and PRTS as appropriate.
• Root cause analyze and propose potential solutions to issues.
• Review and update PRTS status for issues according to priority established through RPN values and stakeholder discussions.
• Lead updates on controller integration issue status to appropriate system issue owners (by providing timely responses to stakeholders)
• Debug and identify root causes issues on the bench.
• Timely Bench & Vehicle Testing. Appropriate feedback to the ARTs and Software Factory
• “Quick turn” tests of software corrections and non-production controller/software for demos, mules, dynos, etc.
• Preparing for test and debugging controller (s/w, calibration issues) on the appropriate environment (vehicle, HIL, SIL, etc.)
• Document and publish CIE related best practices, lessons learned, and develop web or Sharepoint or other information sharing pages for CIEs.
• Execution of PRC designee role in assigned PRTS
Role 3: NATS - New Architecture Technical Specialist (NATS)
Mission Statement: To define requirements and achieve operational status of new controller architectures
Primary Customers: Software development teams, Calibration teams, Vehicle teams, ARTs, Value Streams
ROLES/RESPONSIBILITIES
• Works with SWILs and CIEs to integrate application code and HWIO with the EDU or initial prototype controller to get a new controller up and running.
• Interacts with instrumentation supplier and the controller supplier (HWIO) to get the bench operational and to debug and resolve issues for the initial New Architecture Program
• Acts as Software Manager on the initial New Architecture Program and/or coordinate these SW activities:
• Primary interface to controller supplier for software
• Lead initial controller validation efforts.
• Controller interface to development teams (ARTs, Value Streams)
• Schedules and participates in HWIO Controller Supplier software reviews.
• Generates technical solutions for new and major architectures.
• Provides technical leadership for advanced cross functional technology development.
• Develops and evaluates engineering designs including complex design analysis.
• Creates and balances requirements across systems.
• Initiates and evaluates cost studies, product suggestions and value analyses.
• Leads overall communication, coordination, and consultation with engineering departments and customers.
• Stays abreast of new technology and competitive products.
• Trains, develops, mentors, and evaluates technical capability of team members
DELIVERABLES
• Operational development environment - Coordinated efforts of controls tools group, controller supplier, instrumentation supplier and tools vendors to ensure controller teams are functional using Software Bench, Debuggers, Compilers and Instrumentation
• Prioritize CIE/CTE and SWIL activities, for initial controller deployment.
• Support CSIL and SWIL to manage HWIO delivery and validation, for initial controller deployment.
• Impact Analysis of controller supplier software exceptions
• Coordinated development and resolution of supplier software and LLIO issues.
• Coordinated software development activity across teams.
• Negotiated controller software release schedule and content on initial builds with hand-off to production SWIM.
• Review of supplier software
• Technical solutions which can be implemented in a secure, standard, cost-effective manner.
• Recommendations of future controller and CPU architectures to leverage available technologies.
• Product suggestions
NATS - New Architecture Technical Specialist (NATS)
Mission Statement: To define requirements and achieve operational status of new controller architectures
Primary Customers: Software development teams, Calibration teams, Vehicle teams, ARTs, Value Streams
ROLES/RESPONSIBILITIES
• Works with SWILs and CIEs to integrate application code and HWIO with the EDU or initial prototype controller to get a new controller up and running.
• Interacts with instrumentation supplier and the controller supplier (HWIO) to get the bench operational and to debug and resolve issues for the initial New Architecture Program
• Acts as Software Manager on the initial New Architecture Program and/or coordinate these SW activities:
• Primary interface to controller supplier for software
• Lead initial controller validation efforts.
• Controller interface to development teams (ARTs, Value Streams)
• Schedules and participates in HWIO Controller Supplier software reviews.
• Generates technical solutions for new and major architectures.
• Provides technical leadership for advanced cross functional technology development.
• Develops and evaluates engineering designs including complex design analysis.
• Creates and balances requirements across systems.
• Initiates and evaluates cost studies, product suggestions and value analyses.
• Leads overall communication, coordination, and consultation with engineering departments and customers.
• Stays abreast of new technology and competitive products.
• Trains, develops, mentors, and evaluates technical capability of team members
DELIVERABLES
• Operational development environment - Coordinated efforts of controls tools group, controller supplier, instrumentation supplier and tools vendors to ensure controller teams are functional using Software Bench, Debuggers, Compilers and Instrumentation
• Prioritize CIE/CTE and SWIL activities, for initial controller deployment.
• Support CSIL and SWIL to manage HWIO delivery and validation, for initial controller deployment.
• Impact Analysis of controller supplier software exceptions
• Coordinated development and resolution of supplier software and LLIO issues.
• Coordinated software development activity across teams.
• Negotiated controller software release schedule and content on initial builds with hand-off to production SWIM.
• Review of supplier software
• Technical solutions which can be implemented in a secure, standard, cost-effective manner.
• Recommendations of future controller and CPU architectures to leverage available technologies.
• Product suggestions
SWIL: Software Integration Leader (SWIL)
Mission: Build Integrated Vehicle Motion Control Software that exceeds customer expectations and business requirements.
Primary Customers: Calibration Community, Platform Teams
ROLES/RESPONSIBILITIES
• Integrate and build software for controller system releases and interim software builds
• Single point contact with controller supplier for software
• Assist in development of software content and software anomaly corrections as required
• Integration and verification testing of an integrated software build
• Prepare software for production release
• Manage controller resources for given ECU
• Oversee bench and instrumentation issue resolution
• Provide, communicate, and support common best practices among SWIL community
DELIVERABLES
• Software release including build products and instrumentation files
• Release notification communicated to team
• Changes from previous release
• main/secondary/boot/BSP compatibilities
• part numbers
• ARXML (Global B and GEM programs)
• Supplier software issue resolution
• Coordination of Software impact analysis of Controller Supplier exceptions and outstanding PCE’s with SME (For example, NATS, SWIM, TRB, Safety).
• Support for SWIM in Supplier software CR task scheduling for new GM CTRS requirements and BSP anomalies.
• Scheduling of and/or participation in BSP Controller Supplier software design and verification reviews.
• Mentoring to software team members
• Software review
• Communication of common anomaly corrections with SWIM & SWILs for other ECUs
• SW tested per SWIL checklist and procedures
• First-pass verification
• Compiler/linker/locator logs
• C Source Code Parser log
• Second-pass verification
• Bench/vehicle testing
• Software and calibration parts configuration managed
• Support for system calibration development
• Software released and posted according to process and SWET requirements
• Resolution of ROM, RAM, and Throughput constraint issues
• Resolution of software build proliferation issues
• Support for resolution of issues identified by calibration and platform teams
• Expedient resolution of bench problems
• Documentation (CRs) of requested process and tool updates
• Usage of common tools (e.g., tool catalog and make files)
• Active participation in SWILs Meeting
CIE
Controller Integration Engineer (CIE)
Mission Statement: First responder to troubleshoot vehicle or bench level VMEC specific integration issues and recommend solutions.
Primary Customers: SWILs, SWIMs, Software Development Teams (ARTs / Value Streams), Software Execution Teams (SWET), Controller Integration Teams, Calibration and Vehicle teams, Test Environment providers
ROLES/RESPONSIBILITIES
• This role is responsible for vehicle embedded control system engineering with a primary focus on forming and leading cross-functional teams to troubleshoot issues through all the different life cycle stages (early development through launch and through end of production) on the full range of GM vehicles.
• Lead efforts to work closely with internal development teams including manufacturing, controls development, software, calibration, and testing activities, as well as other cross functional teams in tackling a wide variety of issues as they arise and plotting the best path towards resolution.
• Focus on vehicle system level integration issues including hardware, software, calibration, and vehicle wiring issues (including development activities, in-vehicle build events, buy-off rides, test trips, general fleet usage, durability, VeSCoM Checkout, etc.)
• Lead efforts and develop strategies to best support:
• Test Engineers when facing issues on bench or vehicle for testing (KBT, Milestone, etc.)
• Software support for calibration teams and development trips
• Assembly plant and field problem resolution.
• Test Environment Engineers in troubleshooting and commissioning HIL/SIL/SOLE systems for executing tests and developing operating scenarios to emulate vehicle functions.
• Controls development (SWAT, VIP, SDV, Infrastructure teams) as required.
• Basic Software Development team during emergency builds and testing (e.g., compliance updates)
• Prototype shop and dynos/durability cars / test & development fleets
• Evaluating controller field returns
• Controller rework/reflash (at Pre-PPO and PPO facilities)/Red X activities
• Vehicle software updates if users need help flashing software or investigating and resolving implementation issues.
• Analyze in-house software by applying debugging tools in troubleshooting issues in the ECU memory management, infrastructure operation and applications code.
• Respond to issues from PRTS, Defect Tracking, etc. and actively participate or lead the appropriate stakeholder priority discussion forums.
• Work on both internal SW testing issues and/or with suppliers in outsourced programs.
• Confirm resolution of CIE documented hardware and software anomalies.
• Act as point contact with Issue Resolution Teams and Technicians at PPO and Plants to implement processes that enable rapid problem resolution.
• Educate/train/support/mentor new and less experienced Controls Integration Engineers (CIE) and others learning about the tools and methods employed in this role.
• Develop new tools and processes supporting troubleshooting.
• Integrate and apply applicable Agile SAFe methods in CIE tasks.
DELIVERABLES
• Document hardware and software anomalies using JIRA (or similar database) and PRTS as appropriate.
• Root cause analyze and propose potential solutions to issues.
• Review and update PRTS status for issues according to priority established through RPN values and stakeholder discussions.
• Lead updates on controller integration issue status to appropriate system issue owners (by providing timely responses to stakeholders)
• Debug and identify root causes issues on the bench.
• Timely Bench & Vehicle Testing. Appropriate feedback to the ARTs and Software Factory
• “Quick turn” tests of software corrections and non-production controller/software for demos, mules, dynos, etc.
• Preparing for test and debugging controller (s/w, calibration issues) on the appropriate environment (vehicle, HIL, SIL, etc.)
• Document and publish CIE related best practices, lessons learned, and develop web or Sharepoint or other information sharing pages for CIEs.
• Execution of PRC designee role in assigned PRTS
Work:
GM Performance Management - how it was handled for the past 2 years.
GM Bonus system that I will not be eligible for the full amount.
How HR is pushing for extra check-ins and not sure if HR will make things worse.
Social:
How Steph is always yelling.
We are not having fun anymore.
Health:
I still have toothache
I still have my foot acting
Hair issues are getting worse and interfeering with my confidence.
I am an Engineering Group Manager and I am trying to complete my end of year review template to help my manager. There is a template the HR put forward and I am trying to fill it out. Template has areas On the Absolute Performance side with the instruction of: Summarize your direct report’s performance by detailing goal progress and how that work was accomplished based on Leveling Guide criteria. Under that I have one section for: 1-Goals: The “What” (Include KPIs / Metrics where appropriate) and 2-Levelling Guide Expectations: Skills & Behaviors: The “How”. I also have 2 other sections: 1- Relative Performance: Describe how team and individual performance compare to others, based on goal results (the "what"), skills and behaviors (the "how") and 2- Contextual Performance: provide any unique conditions (positive or negative) that influenced their performance. In my hand I have my self assessment to each of following questions: Question What progress have you made on your goals for the year? What, if any, support do you need? My Answer: In addition to progress on my explicit goals (outlined below), I've successfully addressed several significant blockers that were hindering our ability to deliver on key commitments. Removing these obstacles has already helped us move closer to fulfilling our objectives: My most significant contribution this year was stepping up to lead all build activities from all perspectives for the Build Factory organization following my previous manager’s departure on 4/17/2025, until the reorganization on 9/1/2025. Since June 2022, I have been leading two SWIL groups over 20 NA blue badge employees and up to 12 TCS SWILs (previously 1 EGM was responsible for Battery and Electrification, another EGM for Engine, Transmission and Chassis domains). Initially, I had support from Srini -PM capacity-, but he transitioned to a different role in mid-2024, after which I assumed full responsibility. SDV initiative started in 2024 and PHEV added on top. With limited resources and roles I supported these activities. I stayed on top of the builds especially on the extended hours and over weekends to get the support work going. I helped resolving problems by involving in technical discussions, escalating to right people and assigning the tasks dynamically so that team can focus on the issues. In addition to managing over 200 VMEC build swimlanes (60+ of them active at a given time), I also supported broader initiatives including SDV, PHEV discussions, and acted as the primary point of contact for the rest of GM—such as the PMO and Third Party Software Integration groups. During this interim period, there were no escalations beyond me, underscoring the effectiveness of the structure I maintained. I proactively organized and led working-level meetings with Infrastructure, CoSIM, and VMEC upper management to ensure sustained progress. I also represented the SWIL teams during the reorganization discussions. SDV Update: Before the Reorg: On the SDV side, our team took full ownership of all five MCU3 builds and successfully delivered them on time using three SWILs. We integrated the BOOT component across all five swimlanes and maintained both cadence and daily triage. To support scalability, we added two new SWILs — hiring Vignesh and transferring Gouthami from the MCU2 team — which enabled more balanced workload distribution. We transitioned MCU2 builds (BECM/DMC) from the NATS team to the SWILs, and I received positive feedback regarding how effectively the SWILs have supported these projects, even assuming some NATS responsibilities. Additionally, we began building MCU0/1 (including BOOT and vECU), further expanding our SDV expertise. This milestone reflects full VMEC SDV ownership and showcases our growing leadership in this space, with strong support from the SWIMs and Jonathan H. on the technical side. I led the daily SDV leadership syncs with Ferid, the SWIMs, and Jonathan H., ensuring clear focus on planning and technical priorities. I enabled the team to stay engaged by allocating experienced resources, driving accountability with Infrastructure teams, and supporting CoSIM with appropriate build quality and timelines. After the Reorg: I am currently focused on MCU0/1 builds and supporting Tagore’s efforts in collaboration with Torsten. We recently completed hiring a new SWIL to ensure continuity and establish a permanent backup for Tagore. Eventually, this effort will cover 13 swimlanes — we are currently building five MCU1 swimlanes, while MCU0 is still under development with Infrastructure. Once matured (currently at 65% PAR), the build responsibility will transition to VMEC. Our team currently supports all SDV demos using MCU1 builds. SWIM support is temporarily provided by the Infrastructure team, and we are working to engage the Body team to secure a dedicated SWIM and DRE. CIE support is another area being clarified before full ownership transitions. I have a follow-up with Greg O. to ensure SDV support is fully aligned. In parallel, I continue to mentor the SDV SWILs, help with workload balancing, and partner with the new EGMs to ensure timely build delivery across the board. Leadership and team structure: Before the Reorg: I significantly expanded my leadership responsibilities, continuing to lead two SWIL teams while onboarding Steve H. as a SWIM and hiring a new DRE — which gave me direct insight into DRE responsibilities and processes. Our team grew by two Level-7 SWIL hires and one internal promotion, which was a strong morale boost. Notably, these hires were individuals I had previously engaged through the SWIL Discipline Lead forums, and their seamless integration resulted in minimal ramp-up time. Following that, we hired three additional SWILs who were integrated into their respective teams post-reorg. From a technical and project scope perspective, we expanded our SDV presence by taking ownership of all MCU3 builds, transitioned MCU2/SE builds from other teams, and began supporting MCU0/1 (currently limited to MCU1 while MCU0 is in the PBU phase). On the VIP side, we onboarded over 20 new swimlanes, including complex platforms like TCAR 2.0, PHEV BS13, PHEV S91, and S78. These efforts were successfully executed and acknowledged by the SWIMs for strong delivery. We also extended our support to multiple ATW projects, most recently providing Electrification support for the Inverter Study based on the S59 platform. After the Reorg: I am currently building out the new team structure. I completed the hiring of two new SWILs (one each for Engine and Chassis), while two CIEs were hired by Mike B. My scope has expanded beyond the SWIL domain to include responsibility for two NATS and four CIEs. With the conclusion of the KPIT contract, we transitioned Engine/Transmission projects to TCS. TCS now owns all such projects except E94, P02, and T93. I’ve taken a more direct leadership role with the TCS team to ensure cohesive delivery across SWIL, NATS, and CIE resources. Given the SWIL team's close involvement with TCS, I treat them as an extension of our team and lead accordingly. The NATS and CIEs now support all Engine, Transmission, and Chassis projects, including Dumarey-supported programs and the SDV transition of persistent ECUs. SWIM Support: Before the Reorg: This year, I welcomed Steve into the team as a SWIM to lead the VMC_EV and VMC_EEM_BC builds. He also took ownership of BDY, BDY_BC, and MCU0/1 builds. His addition significantly improved our ability to deliver on SDV commitments with the right scope and timing. I supported Steve closely through daily SDV leadership meetings, by escalating issues to the appropriate groups, and by assigning the right SWIL resources to ensure successful build delivery. Recognizing his interest in the SWIM Discipline Lead role, I actively supported his development into that position. This was a pivotal step, as it allowed us to influence key stakeholders more effectively — especially around pull-ahead builds, issue resolution, and reducing build lead times. Through our engagement in the SWIM Council, we were able to improve WT quality, planning, and swimlane creation/maintenance. These efforts directly contributed to more timely and predictable build deliveries. After the Reorg: Post-reorg, SWIM responsibilities have shifted to external teams, while I now directly lead SWIL, CIE, and NATS functions. I also manage the TCS SWILs and work closely with them to ensure seamless delivery across our shared portfolio. To date, there have been no late builds attributed to this team, demonstrating strong coordination and execution. Additionally, I’m increasingly involved with the Dumarey SWIL team — both to support them as needed and to prepare for a potential transition of their projects in the coming months. Currently, I am leading root cause and read-across activities for two critical PRTS issues: 2421616 and 2422881, helping to drive resolution and prevent recurrence. Complexity Manager Role: Before the Reorg: With Ryan’s support, we organized, validated, and communicated the VMEC Software Roadmap and Controller/Program Plan of Record, ensuring alignment across Development, Deployment, and Calibration teams for Engine, Transmission, Chassis, Electrification, and Battery ARTs. Ryan also revived the FMT process, which had been inactive for several years. He now reviews and provides feedback on all new SWIMLANEs and branches, helping to improve quality and alignment early in the process. Together, we led the development of the Jira-based Build WT Dashboard, enabling standardized monthly reporting and metrics. Our analysis of active SWIMLANEs also supported Build Factory’s resource planning and contributed to the early stages of replacing the existing workload model with a more data-driven approach. After the Reorg: Although Ryan now covers all VMEC SWIMLANEs and is no longer within my direct team, I continue to collaborate with him on key initiatives such as FMT adoption and the SWIMLANE Reduction effort. Our ongoing partnership supports broader process standardization and resource optimization across the organization. SWIMLANE & Software Project Lifecycle Improvements: Last year, we presented the Pull-Ahead Rules of Engagement at the VSAP meeting and later shared it with Ferid as part of a broader alignment effort. As a follow-up, this year we introduced key topics around the SWIMLANE and software project lifecycle, continuing to drive clarity and structure across the SDLC. The SWIMLANE Reduction initiative gained traction with the Deployment Teams and, following the reorganization, I resumed ownership of the effort. We are on track to finalize the reduction plan by the end of this year, with several foundational elements already in place — including FMT adoption, SWIMLANE merge studies, and defined best practices. Full execution is targeted for Q2 2026, pending some updates from the Tools team. Notably, BIQ is a major enabler and driver of this initiative, and we are working closely with the relevant teams to ensure necessary improvements are delivered to support rollout. NVM/J-type memory utilization efforts are also currently in place. I created, led, and executed the following strategies by engaging the right people to drive progress in our complex and fast-paced work environment. (Please refer to the shared OneNote for additional details:https://generalmotors-my.sharepoint.com/:o:/g/personal/xzl30c_nam_corp_gm_com/ElRYIFoLGwVDuBZZfrjMCe0BBdjSop-vz7NRGqxMj_h8wg?email=mustafa.dakroub%40gm.com&e=bMNuhH) 00- SWIL Strategies and Prioritization - Overarching strategy 01- Strategy: SWIL SDV - IN PROGRESS - updating MCU0/1 part and MCU2 and MCU3 is transitioned to new groups. 02- Strategy: PHEV Swimlane Support & Build Execution - IN PROGRESS - limiting it to Engine/Transmission/Chassis persistent ECUs.s 03- Strategy: TCS Ramp-Down and Transition & KPIT transition - COMPLETED successfully by 9/24/2025. 04- Strategy: Pull Ahead Rules of Engagement - COMPLETED successfully by 5/15/2025. 05- Strategy: ICE transition - COMPLETED successfully by 9/25/2024 and in 2025 helping Dumarey/ helped KPIT teams as needed. 06- Strategy: Third Party SW Integration - COMPLETED successfully on 10/1/2024 - monitoring for any updates in 2025 07- Strategy: BCM/TCS 2025 - IN PROGRESS - Planning phase with Srini Chande. 08- Strategy: 2030 Roadmap - IN PROGRESS - Discussions are taking place with PMO groups. 09-Strategy: SWIL Technical Expertise - IN PROGRESS - Feedback collected, NATS and Senior SWIL mentorship is in place. 10-Strategy: SDV Test Automation - IN PROGRESS - Supported by the nightly builds and TCS/KPIT Build/Test AI Triaging/Automation. 11-Strategy: Factory Management Team - IN PROGRESS - Ryan reinstated the FMT and by September 2025 the FMT committee was formed with M&M and Mustafa D. 12-Strategy: WoC: Empowered Culture and Leadership Alignment - IN PROGRESS - rolling learnings from previous years to my new team. These strategies have been regularly reviewed and updated with upper management. I actively engaged the SWIL Leadership team in both the execution and refinement of strategic initiatives, incorporating their feedback on task ownership and delivery approaches. Following the reorganization, I am transitioning relevant strategies to the appropriate teams and reassessing the remaining ones to align with the scope and priorities of my new team. Unexpected Challenges and Mitigation Efforts: This year, we encountered several unexpected challenges, with tooling changes (COMR, Scheduler, Github and our scope was leading not only VMEC SWILs but every SWIL in S&S organization) and the sudden decommissioning of the KPIT COMR team being the most significant pain points. To address tool-related issues, I initiated frequent escalations—either directly or through the appropriate domain teams—as we identified problems or edge cases not previously considered by the Tools team. This proactive approach helped bring the situation under control and ensured continuity. Following the short-notice removal of the KPIT COMR team, I led efforts to bridge the resulting gaps. On the SWIL side, we arranged targeted training sessions with the original KPIT team as well as the new local support contact. We established multiple support pathways—local support, indirect KPIT contacts, and internal upskilling—to ensure the team could remain unblocked and productive. On the SWIM side, Steve H. led efforts to train SWIMs on how to maintain and manage the list of signals that need to be built by the SWILs. While some variation still exists across domains and swimlanes in how responsibilities are split between SWIMs and SWILs, we’ve seen considerable improvement in consistency and ownership. We also used M&M's support sessions to cascade the new expectations across the ARTs, helping to align teams and clarify responsibilities. TCS SWIL Strategy and Project Transition: As part of our TCS SWIL strategy, we transitioned legacy Engine and Transmission projects to KPIT, while new Engine and Transmission projects were assigned to Dumarey, with the understanding that these teams are accountable for their respective projects and builds. However, during emergencies, new toolchain or process rollouts, or when these teams faced capability gaps, we stepped in to support them in delivering builds, helping to avoid escalations, hot/cold trip cancellations, and potential line stoppages. We also provided assistance to KPIT on regreener and BOOT builds and extended guidance on MY jumps to ensure unified success as one team. On September 24, 2025, the KPIT team supporting Engine/Transmission builds was officially decommissioned. We successfully transitioned their SWIL responsibilities to TCS, starting in early August 2025, and met the target completion date. The TCS team currently supports all necessary builds. To ensure smooth coordination, I initiated a weekly build request meeting between SWIMs and TCS, supplemented by additional sessions to synchronize efforts with the extended TCS team. TCS Team Development and Expanded Role: I have consistently advocated for advanced training for the TCS team as they serve as our extended SWIL resource. Currently, they hold Domain Lead responsibilities for Engine and Transmission projects. This strategy enabled us to leverage their capabilities beyond their initial scope—originally focused on E99, E88_90_9x, and T96 builds—to successfully deliver on Chassis (EBi, SBi) and Battery (BS03, BS11, and parts of BS13) domains. With the KPIT transition now complete, TCS plays a critical role in the Engine and Transmission domains. We anticipate their continued support on the EBi and SBi chassis projects, while simultaneously expanding our NA presence in MCU0/1 SDV builds. Following are the updates for the 2025 Goals: 1) Creating a safe, inclusive, and engaging work environment goal: + Every team member has the safety goal integrated into Workday, and all adhere consistently to these safety standards. + SWIL Leadership and Domain Leaders actively enforce ownership and accountability by reviewing, assigning, and tracking Work Tasks (WTs). Regular feedback sessions with relevant stakeholders are held throughout the year. Our SWIL build metrics indicate a higher number of closed WTs compared to 2024 (refer to the SWIL WT tab for details). Additionally, CIEs contribute within their domains, and I maintain direct engagement with NATS, prioritizing tasks across all domains through our weekly Monday sync meetings. + We initiated a monthly open discussion forum to address ongoing issues. I dedicate half of these sessions to reviewing and addressing WoC findings and recommendations, which are accessible on our SWIL Teams site. Despite team changes, we have continued to enhance day-to-day work life, reflected in improved WoC scores and higher engagement compared to the previous years. To further support this, I developed a focused strategy, "12-Strategy: WoC," aimed at sustaining these improvements. + Relevant WoC action items are continuously tracked, updated, and discussed monthly with the team to ensure progress and accountability. + Talent cards are maintained up-to-date, and I am currently reviewing and updating them for new team members to support career development and resource planning. + I have presented multiple versions of the SWIL organizational structure and actively contributed to discussions within the Build Factory organization. Notably, I successfully advocated to upper management for integrating MCU0/1 with the Chassis team, leveraging synergies and enhancing collaboration. + I played a key role in the transition of legacy Engine and Transmission projects from KPIT to TCS and presented a proposal to Ferid for shifting VIP SWIL support to TCS. Although this specific initiative was not pursued due to cost and CIE organizational considerations, it demonstrated proactive planning for optimized team utilization. + I have maximized the utilization of the TCS group by initially assigning them Battery domain work (BS03, BS11) in the previous organizational structure. Following the KPIT transition, they have focused primarily on Engine and Transmission projects, with additional bandwidth allocated to Chassis domain builds as capacity permits. 2) Nurture our Safety Culture + Every team member has the safety goal integrated into Workday, ensuring safety remains a personal priority. + Safety talks are regularly delivered, and MPG Safety slides are incorporated and actively discussed in every group meeting to reinforce safety awareness (please refer to team meeting slides on SWIL Teams site). + The team consistently adheres to safety requirements and promptly raises any safety concerns as they arise. + We are on track to meet PRTS closure deadlines, with updated and agreed timelines reflected in the VMEC scorecard. 3) Innovate, develop, and deploy industry-best software on-time and with quality 3/1 We actively support CICD efforts by triaging any issues daily to ensure nightly builds remain stable. The VMEC SDV status meeting occurs daily, with Ferid joining when challenges arise. Following the reorganization, I assumed responsibility for MCU0/1 projects and have maintained consistent nightly build support, including enabling CoSIM automation. Additionally, I am collaborating with TCS to pilot an AI-based auto-triaging mechanism, currently applied to an Engine build as TCS handles VIP builds. 3/2 We are continuously updating the SWIL process based on audit findings and recommendations. The latest version is available on the Stages tool. As part of Discipline Lead activities, we designated a process owner to manage changes. We also maintain a detailed OneNote with step-by-step guidance for SWIL tasks, including a new page that flags obsolete items and highlights recent changes for quick reference. 3/3 We support and deliver all SDV 2.0 VMEC builds on time, covering MCU3 builds, BECM, DMC, and, since the reorganization, MCU0/1 builds and the persistent ECU side of PHEV builds. We ensure quality by providing L0 CG testing before releasing SDV builds. All TFRP commitments are met, with scope becoming more focused after the reorg. 3/4 Ryan Bruss is collaborating with AI teams to develop a tool that scrapes our process documentation and OneNote pages to provide automated guidance on executing discrete SWIL tasks. The initial version of this AI-driven tool is now available. My main contribution was bringing the teams together and providing necessary resources to make sure this initiation progress. 3/5 The TCS harmonization project is led by Srini. This year, we decided to keep the BCM team separate to avoid disrupting their current workload. We have initiated leadership syncs on both sides to identify synergies under Srini’s guidance. The BCM team has aligned its build and release processes with the North America team, received training from TCS, and is now prepared to support NA work when needed. I met with Srini regularly and strategize the timing and actions needed to prepare BCM team. 4/5) Accelerate EV launches with quality/Enable on-time delivery of ICE/PHEV entries and SDV builds + Resource planning is updated quarterly, with resource mapping and support prioritized based on upcoming workloads. Following the reorganization, this has become increasingly important as I coordinate with multiple roles within the team, and we are short on HC to meet program needs and using prioritization. + Prioritization of unplanned work is effectively managed through the Build Request and FMT meetings, ensuring smooth workflow and timely responses. + There have been no project delays attributable to the SWIL team. On several occasions, we delivered builds ahead of schedule, providing additional flexibility for testing and calibration teams; these efforts were acknowledged by individual team members. Due to the rapid turnaround of SDV builds, the team manages multiple builds per day, with SWIM leading activities and escalations. Post-reorganization, I support SDV with one SWIL and a backup, while other activities and escalation is led by the external SWIM. Engine and Transmission projects, including the Domain Lead responsibilities, are managed by the TCS team. Chassis projects are locally managed by the North America team. Our NATS and CIE teams cover all domains (Engine/Transmission, Chassis, and MCU0/1). I structured the team so each domain has a primary and backup SWIL, with NATS and CIE roles staffed by senior personnel and backups to ensure continuity. + Risks are escalated promptly by both the Deployment teams and our immediate team. So far, we have avoided any production escalations. On the SDV side, escalations were minimal, largely due to leadership prioritizing critical tasks—even when this meant not supporting certain weekend work, such as during boot integration. For MCU0/1 support, we match the work style of Infrastructure and CoSIM teams, including weekend work when justified. We hired a new SWIL to support NATS and help offload their workload, while training CIEs in build processes and SWILs in deep debugging to mitigate resource-related risks. + PRTSs are handled appropriately and discussed regularly in Core PDT meetings during various project phases, with weekly build metrics provided by Ryan to support transparency. + The KPIT legacy project transition to the TCS team was completed flawlessly by September 24, 2025. + Throughout the year, there have been no SWIL-related delays impacting product timing. 6) Deliver a leading customer experience across our entire portfolio + Headcount planning, prioritization, and additional support mitigation are reviewed and updated on a monthly basis to ensure alignment with project demands. + We successfully added multiple SWIMLANEs—specifically BS13, S91, and S78—to our portfolio to support PHEV development. Beyond these direct responsibilities, we also provide critical support to the Dumarey team during emergencies and resource shortages, assisting with P02, E94, T93, and T93A SWIMLANEs. With the new team structure, I am actively supporting persistent ECUs on the PHEV side and coordinating CIE and NATS resources to ensure comprehensive coverage in our responsibility domains including SDV. + Our team is engaged in roadmap discussions to ensure SWIL resource requirements are clearly identified and incorporated into future planning. With the reorg I am also keeping an eye on the NATS and CIE resources. Question What behaviors and skills contributed the most to your success? (What are your strengths?) My Answer: One of my key strengths has been developing clear, strategic direction for the team—helping us align on what we’re doing and why it matters. I created strategies that not only support our business goals but also align with individual team members' interests and strengths, ensuring the right people are working on the right initiatives. This alignment has enabled us to deliver consistently on our builds while identifying and addressing gaps, particularly in new focus areas such as SDV and PHEV. I actively seek out and analyze feedback, converting it into actionable improvements for both myself and the team. For example, we've already rolled out the updated GM behaviors to the SWIL team, ensuring our culture and practices are aligned with current expectations. Following the recent reorganization, I continued to refine our existing strategies to fit the evolving structure of SWILs, while also developing new approaches tailored to the needs of the CIE and NATS roles. Despite having limited resources for each role type, we proactively implemented a domain-based backup strategy, ensuring coverage and continuity across key areas like Engine/Transmission and Chassis/MCU0/1. These behaviors—strategic thinking, team alignment, feedback-driven improvement, and proactive planning—have been fundamental to our success. Behaviors contributing the team's success: (please see other behavior examples as part of the Leveling Guide comments provided by email). Behavior: Win With Integrity: Upholding integrity has been a core focus of my leadership approach. I’ve consistently worked to embed GM's values into our day-to-day operations and team culture in the following ways: Promoting GM Values: The newly rolled-out GM values have been shared and discussed with the team in quarterly group meetings. After the recent reorganization, we revisited and reiterated these values to ensure alignment across the updated structure. Feedback from both stakeholders and team members is regularly collected during group discussions and 1-on-1s, and necessary adjustments are made to reinforce these principles in our work. Encouraging Transparency and Ethical Decision-Making: I identified instances where work tickets (WTs) were not meeting expectations and shortcuts were being considered. In such cases, I encouraged the team to seek clarification and escalate concerns appropriately. For example, a concern raised by Jay D. regarding the risk of flashing new software (26.26.179.40) into an EDV—due to known IRM2 interface limitations—was escalated to Deployment Management. This ensured we made a safe and responsible decision rather than compromising system integrity. Accountability During Transitions: Following the KPIT transition, several new SWIMs joined in the Engine, Transmission, and Chassis domains. I guided the team to push back on requests that lacked clear value or where WTs were not mature enough for build execution, prioritizing quality over convenience. Reinforcing Ethical Behavior: Positive examples of integrity are regularly acknowledged through the Achievers system, and recognized during group meetings and 1-on-1s. Conversely, inappropriate behavior is investigated, and the necessary message is communicated constructively to maintain a culture of accountability. Effective Communication and Alignment: During group meetings, I ensure that key communications from upper management are shared. After each major APM, we hold follow-up sessions to review leadership messages and address any team questions, ensuring alignment across all levels. Cross-Team Collaboration and Support: When additional capacity allowed, I supported the Dumarey team with builds and debugging activities. This not only helped their efforts but also provided learning opportunities for our team in lead E94/P02/T93 projects. Strategic Transition Planning: I developed the KPIT transition strategy and led a smooth handover of the SWIL role to TCS. While there are logistical challenges in working with TCS (e.g., time zone and communication issues), this move improves resource utilization and reduces costs, aligning with broader organizational goals. Operational Leadership and Workload Management: I initiated weekly KANBAN and status meetings to synchronize SWILs post-reorganization. These meetings help balance workloads, enable rapid response to urgent issues, and prevent burnout. I also support newly assigned EGMs by sharing insights on previous team members’ performance to ensure smooth transitions and maintain continuity. Behavior: Commit to Customers Commitment to our customers—primarily the Deployment Teams—has been central to my role and success. I actively maintain strong collaboration channels and prioritize proactive communication to ensure we meet expectations with high quality and on time. Ongoing Collaboration with Deployment Teams: I hold weekly synchronization meetings with Deployment EGMs to stay aligned on upcoming changes, risks, and priorities. Ryan supports this effort by coordinating with each deployment team to gather details on impactful changes and creating system-level roadmaps. This allows us to proactively align resources and timelines, avoiding last-minute issues. Proactive Issue Escalation: When challenges arise, I ensure they are escalated appropriately—either through 1-on-1s or direct communication with upper management. For SDV, we’ve established a daily status meeting with Ferid to keep everyone aligned and address blockers in real time. Effective Prioritization and Execution: Internally, we conduct weekly KANBAN meetings and regular Build Request and FMT meetings to prioritize customer needs and ensure requests are addressed efficiently. These processes help balance capacity and maintain focus on what matters most to our customers. Recognition and Reinforcement: I’ve acknowledged over 40 team members who have demonstrated strong customer commitment, using platforms like Achievers. For example, on March 31, 2025, Lou recognized me, Jonathan, and Steve for their diligence in producing reliable SDV 2.0 builds and improving stability through better collaboration with development teams. Strengthening Cross-Domain Relationships: Following the recent reorg, I’ve narrowed my focus to key domains while also improving support for areas where the SWIM/DRE is outside our immediate organization. I’ve held 1-on-1 meetings with respective EGMs and now maintain regular syncs with key SWIMs to improve coordination and responsiveness. Leading Strategic Improvements: I am driving the SWIMLANE reduction initiative, which aims to benefit all stakeholders by increasing quality (through BIQ), enabling technical improvements like J-type memory, reducing unnecessary SWIMLANEs (via FMT approvals), and promoting best practices across the board. Teams are already taking action, and we expect full execution of the plan by Q2 2026. Forward-Thinking Planning: I’m also leading efforts to introduce proactive CPU load estimation and measurement. This will help prevent system-level issues before they occur. We are on track to implement the necessary process updates by November 2025. Through these actions, I’ve worked to ensure that our organization not only meets but exceeds customer expectations, delivering results that are aligned with both short-term needs and long-term strategic goals. Behavior: Innovate and Embrace Change Throughout the year, I’ve continuously embraced change and led innovation across multiple dimensions—from team structure and technical processes to strategic planning and cross-functional collaboration. Key contributions include: Restructuring Teams to Enable Agility and Growth: We restructured the SWIL team under specific domains to better support our customers, encourage collaboration, and apply lessons learned across teams. A notable example this year was the successful integration of the SDV domain into our structure. We also challenged the status quo by appointing a SWIM for this domain and successfully advocating for Steve H. to take on the SWIM Discipline Lead role —despite not being part of the traditional Deployment teams— based on his expertise and leadership potential. Adopting New Technologies and Methods: We actively support ATW initiatives to explore and adopt new integration techniques and collaboration models across various teams (such as early development for the P0/P2 PHEV projects (from proposal to initial build and PBU stages), Electrification support for the Inverter study based on S59, including team reorganization, Initiation of an in-house steer-by-wire ATW project, covering proposal and early build phases, Support for Blue Nexus and other tools alongside the Electrification team, handling logistics for tool setup and usage, Prioritizing and resourcing efforts during the TCAR 2.0 initial PBU phase). We've been testing and integrating builds on MCU2 controllers for over a year and on MCU1 controllers for approximately 10 months—an essential step in preparing for upcoming vehicle programs. Driving Technical Innovation: I led the development of a new strategy—Strategy 06: Third-Party SW Integration—outlining how supplier code can be cleanly integrated as standalone SWCs. This promotes modularity and better maintainability of code moving forward. Enhancing Build Process for SDV and PHEV: Our team has fully embraced new strategies related to SDV and PHEV. Ownership was clearly communicated, and the team has consistently delivered—without missing a single build. We also created new SWIM and DRE roles within the team, with strong internal support for both. We expect similar success as we expand the DRE role’s involvement. Encouraging Creative Problem Solving: Team members, including Sue, have been regularly recognized for questioning existing processes and proposing creative solutions in areas such as COMR handling, auto-scheduling, and BOM updates. This mindset is encouraged and supported throughout the team. Fostering Continuous Learning and Improvement: In 2024, we conducted several SDV-focused lessons learned sessions. We also initiated SDV leadership meetings, which have significantly improved the quality and consistency of the builds we’re responsible for. These efforts ensure we’re well-positioned to meet increasing build demands through 2025. Improving Cross-Functional Collaboration Post-Reorg: Following the reorganization, we realigned our team structure vertically to strengthen external engagement, especially with external deployment teams. We added regular weekly syncs to gather external requests and understand their challenges, leading to better responsiveness and communication. Leading AI Integration for Build Triaging: I’m currently leading the AI-based build triaging initiative that TCS is implementing. I coordinate internally to track progress, provide feedback, and make necessary adjustments to ensure the tool aligns with our workflow and adds value. Strategic Planning and Transition Support: I’ve developed an entirely new strategy for my current group post-reorg while also updating the previous strategies for my former group. These updates are being transitioned to the new EGMs to ensure continuity and alignment with organizational goals. Behavior: Lead as One Team Collaboration and cross-functional alignment have been key to our success this year. I’ve consistently fostered a unified team environment—both within our immediate group and across partner organizations—to deliver on our shared goals. Cross-Functional Collaboration with Stakeholders: I hold regular weekly meetings with Deployment EGMs and gather quarterly feedback from SWIMs to ensure alignment on priorities such as domain setup, processes, and escalation paths. On the SDV side, we maintained daily meetings with infrastructure and tools teams, while working closely with the PMO to clarify milestone scopes. Ryan and Steve have been instrumental in helping facilitate effective collaboration across external teams. I also lead TCS/Dumarey/KPIT teams as one team and regularly interact with team members and help them succeed. To address tool-related issues (especially on COMR, Scheduler, GitHub tool which lead the implementation for entire SWIL organization beyond our SWILs), I initiated frequent escalations—either directly or through the appropriate domain teams—as we identified problems or edge cases not previously considered by the Tools team. This proactive approach helped bring the situation under control and ensured continuity. Clear Roles, Responsibilities, and Vision Alignment: We have clearly defined responsibilities for roles such as SWIL, CIE, and NATS. These are reviewed quarterly to ensure alignment with our evolving vision and strategic initiatives, including SDV and PHEV. This clarity has helped the team stay aligned and work efficiently toward common goals. Team Development and Coaching: I actively coach team members through regular 1-on-1s and spontaneous opportunities. I’m currently mentoring two individuals preparing for 8th-level interviews and supporting four additional mentees through bi-weekly mentoring sessions. Recognition and Team Culture: We consistently celebrate achievements during group meetings and organize team-building events such as happy hours, Pi Day, summer outings, fall meetups, and holiday celebrations. For example, our June 25 group meeting was held at Caresoft, where the team learned about vehicle benchmarking—an engaging and educational experience. Executive-Level Contributions and Recognition: I was part of the team that presented our build process to Dave Richardson, showcasing the automated build system and its release process. Our work was recognized by both Dave and Clyde B., who appreciated the impact of our contributions on the Thermal Co-Sim project: "Hi all, I just wanted to catch up since we had to wrap the demo without much wrap up time. I appreciate each of you for your tremendous work on the Thermal Co-Sim work and the demo to Dave Richardson and co. Your dedication and effort is creating fundamental change! It's a gamechanger. Every test, Every build, Every night!" (March 5, 2025) Leading the SWIL Team Across Domains: As agreed by IDR EGMs, I lead the SWIL Kanban and Status meetings, driving consistency and collaboration across the team. I’ve extended this leadership to include Engine/Transmission and Chassis Deployment teams, supporting them from SWIL, CIE, and NATS perspectives and ensuring we function as one unified team. Recognition from Stakeholders: My efforts to drive collaboration and shared ownership were recognized by Julian Blair (Engine Deployment EGM) following a high-priority release issue: "Jayden, thank you for lending a helping hand by bringing in TCS SWIL support early in the troubleshooting process for the MY27 E42A T1xx HD 80% release flash failure issue. Your proactive approach played a key role in accelerating resolution and enabling a validated software release within 48 hours, keeping us on track for the 80% BOR and DVUL3 milestones. You demonstrated true ownership and the GM behaviors of "Lead as one team" and “Move with Urgency.” We sincerely appreciate your unwavering support." (August 15, 2025) Question Which do you need to work on for you to have an even greater impact? (Where are there opportunities for growth?) My Answer: Before the reorganization, I had the opportunity to deepen my understanding of the SWIM and DRE roles to better guide these teams and set clear expectations. Since the reorg, I have been focusing on defining roles and responsibilities, as well as individual deliverables, for the CIE and NATS roles. While the expectations and RASIC matrix were already established for various SWIL grades and levels (ranging from 5A through 8A), I am continuously expanding my technical knowledge of these newer roles. This will help me prioritize tasks more effectively and make informed decisions. Our organization is currently facing challenges around the SDV scope, as milestones approach and final expectations remain unclear. Leveraging my background in project management, I have been working to close the gap between SWIM and PMO alignment. We have also increased collaboration with the infrastructure, tools, and CoSIM teams to maintain momentum. By the 50% PAR milestone, these interactions improved significantly. In my new assignment, I am managing the MCU0/1 projects from a build perspective, supported by SWIM/DRE infrastructure teams. The infrastructure team’s focus is on MCU0 bring-up, while we support MCU1 demos. Once VMEC takes over final MCU0 work after PBU completion, dedicated VMEC resources will improve efficiency. However, I currently have limited influence over the infrastructure team and must maintain a careful balance to avoid prematurely assuming responsibility before infrastructure stabilizes BOOT and BSW. I will need support from upper management to establish a strong VMEC organization so I can strategically align work with the right resources. We also need to ramp up new team members to handle the heavy SDV, PHEV, and Battery build requests within the IDR projects. As the lead for VMEC SWILs, I am ensuring necessary training, mentorship, and workload balance, especially during emergencies. Gaining more experience with and supporting CIEs and NATS will sharpen my technical expertise, enhancing the quality of my guidance and decisions. I created and shared my Mid-Year Growth Strategy titled “Becoming a More Assertive, Confident, and Impactful EGM”, working on it with my mentors Joe P. and Greg H. The strategy focuses on five key areas: 1- Leadership Command of Critical Initiatives 2- Projecting Confidence and Presence in Meetings 3- Communicating Clearly and Concisely 4- Feedback Loop and Accountability 5- Going Beyond Feedback I have already received positive feedback from colleagues and mentors and continue to improve by applying their input to my new role and team. Additionally, I am actively enhancing my communication skills. Following my manager’s advice, I’ve begun recording my communications for self-review and enrolled in online training courses. Conversations with my mentors have provided useful tips, which I consciously incorporate into my daily communication practices. Question Are you contributing to GM in other ways you would like to share? For example, consider how you helped others achieve their goals or develop them through coaching and mentoring. My Answer: This year, I have been fortunate to have three GM mentors, Greg H., Joe P. and Thiago C., while also mentoring four GM engineers. One of my mentees recently earned a promotion, and another secured her dream role. Both have shared very positive feedback on how our bi-weekly mentorship sessions helped them achieve their career goals. Currently, I am preparing two team members for 8th-level position interviews, and I am confident they will perform well in their NATS roles. Pull Ahead Rules of Engagement initiative evolved to the next level as SWIMLANE/build reduction initiative and I took ownership on September 25, 2025. This effort aims to simplify our portfolio by reducing the number of builds we support, which will also cut downstream workload and deliver significant cost savings for the company. I am leading the initiative, coordinating with internal and external teams, and expect to deliver an actionable plan by year-end. Some studies have already concluded, with ongoing activities regularly presented to upper management. Prior to the reorganization, we effectively executed dynamic SWIL assignments and domain structures. After the reorg, I proposed continuing this efficient approach in the new organization and took the lead on this effort. We successfully managed the workload with approximately 25% fewer resources than predicted by workload models, all while taking on additional responsibilities such as ATW projects and new SWIMLANEs. To align with the new organization’s goals, I created and reviewed a 90-Day Action Plan for my EGM Role covering the Engine, Transmission, and Chassis domains. I set up a new team of 10 members, including five new to VMEC, and am actively ramping up and mentoring three new CIEs and two new SWILs. I also rolled out the BF organizational changes to the external Deployment Teams and fostered stronger collaboration with Engine/Transmission and Chassis Deployment teams beyond our GFL area. In support of team growth, I conducted over 20 interviews to fill positions within the SWIL groups (both my previous team and SDV). I successfully hired five SWILs and one DRE, with four SWILs currently active on projects. Once the reorg blueprint was finalized, I recommended moving experienced SWILs to new integration groups to help ensure their success (e.g., Gouthami and Vignesh to MCU3, Vishaal to Battery domain) while hiring fresh talent for my team which I think I can bare the overhead better in comparison to the other teams. I also supported four SDSAs following their manager’s departure. Between March and July, I conducted one-on-ones, managed mid-year calibrations, and developed improvement plans—especially for one team member with a partial rating. After a month that new EGM was on boarded, I transitioned the SDSAs smoothly to the new EGM. Throughout the year, I contributed to several ATW initiatives, including: Early development for the P0/P2 PHEV projects (from proposal to initial build and PBU stages) Electrification support for the Inverter study based on S59, including team reorganization Initiation of an in-house steer-by-wire ATW project, covering proposal and early build phases Support for Blue Nexus and other tools alongside the Electrification team, handling logistics for tool setup and usage Prioritizing and resourcing efforts during the TCAR 2.0 initial PBU phase In addition, I supported other important activities: GEN AI Build Triaging with TCS: Leading efforts toward build automation for VIP projects, with plans to extend into SDV domains, supported by Srini C. SWIL AI Tool: Currently in testing, this tool answers questions based on the SWIL OneNote document, assisting new integration groups with foundational SWIL inquiries. Debugging Training Session: Organized a 4-hour introductory debugging training via GLIWA at Building 104, helping SWILs enhance their bench debugging skills complementary to Lauterbach. SWC Repo Ownership Update: Reviewed and updated approximately 3,200 SWIL-owned repo items within a 60,000-line document in just two days, naming primary and secondary owners. I took secondary responsibility for most items. CPU Load Measurement Initiative: I am leading proactive discussions with Keyur P. to establish processes for early risk identification on items such as SWIL Checkout, KBT/PFC, and CG6461, with progress already underway. I was also in the secondary support role helping out the following second dimension activities: a. 2nd Dimension - MPI File Release Process Improvement Discussion b. OPSW CRETA/CalPortal posting c. Scheduler managing for VIP according to automated process on SDV2 d. KSI #9 - Calibrations for SW Test e. SWIL Workflow improvements f. SDV 2.0 process for the regular builds including the rebuilds g. NATS-SWIL mentorship So I need to fill out the template I outlined at the beginning on 4 sections: Section 1: Absolute Performance: Goals: The "What" Section 2: Absolute Performance: Skills & Behaviors: The “How” Section 3: Relative Performance Section 4: Contextual Performance Could you please help me fill these sections out and make me have a positive light:
Summary / top-line:
Led delivery and stabilization of Build Factory SWIL operations during a major leadership transition and reorganization while sustaining delivery for SDV, PHEV and ICE portfolios. Key delivery metrics and outcomes:
Build throughput & ownership
Managed ~200 VMEC build swimlanes (60+ active concurrently at peak) with no SWIL-related late builds attributable to the team.
Took full ownership of all five MCU3 SDV builds and delivered them on time; added MCU2 (BECM/DMC) and began MCU0/1 work (MCU1 demos active).
After the reorg I supported and enabled all SDV demos using MCU1 builds.
Team & capacity
Led two SWIL groups covering 20+ NA blue-badge engineers and up to 12 TCS SWILs (since June 2022); hired 5 SWILs and 1 DRE in 2025 and integrated them rapidly.
Hired/placed new SWILs to scale MCU3/SDV work and added backups for critical roles (example: hired SWIL as backup for Tagore).
Transitions & program moves
Successfully led the KPIT → TCS transition for Engine/Transmission builds; transition completed and validated by Sept 24, 2025 with no service interruptions.
Transitioned MCU2 builds from NATS to SWILs and expanded SWIL responsibility across VMEC SDV domains.
Process & strategy
Created and executed multiple strategies (Pull-Ahead Rules of Engagement completed 5/15/2025; TCS/KPIT transition completed 9/24/2025) and continued rollout of SWIMLANE reduction initiative with an actionable plan targeted by year-end and full execution targeted Q2 2026.
Led creation of a Jira-based Build WT dashboard and instituted standardized monthly reporting to improve resource planning.
Operational reliability & innovation
Maintained nightly build stability via daily triage and enabled CoSIM automation and early AI-triaging pilots with TCS.
Led root-cause/read-across on two major PRTS issues (2421616, 2422881).
Support needed (concise):
Continued executive support to establish a strong VMEC organization and influence infrastructure priorities (particularly for MCU0 bring-up and BOOT/BSW stabilization).
Headcount / role coverage to fully staff SDV, PHEV, and Battery demand (current staffing is tight; prioritization and HC approvals would reduce single-point dependencies).
Core leadership behaviors demonstrated (mapped to leveling expectations):
Strategic leadership & ownership
Set clear strategies and priorities for SWIL, SDV, and domain transitions (created 12-item strategy list; assigned owners; tracked progress). Demonstrated ownership across the portfolio during manager departure (4/17/2025) through reorg (9/1/2025).
Execution with results
Delivered high-impact outcomes (on-time MCU3 builds, no late SWIL attributable builds, flawless KPIT → TCS transition) by driving cadence (daily/weekly syncs), assigning accountability, and removing blockers.
Cross-functional collaboration
Regularly coordinated with PMO, Infrastructure, CoSIM, Deployment EGMs, and third-party integration groups. Represented SWILs during reorg and managed escalation channels effectively (no escalations beyond my level during interim leadership).
People leadership & talent development
Recruited and onboarded multiple SWILs/DREs, mentored four GM engineers (two being prepared for 8th-level interviews), and supported several SDSAs through transitions and improvement plans.
Built a domain-based backup strategy and kept Talent Cards current to support career growth and succession.
Customer focus & integrity
Kept Deployment teams’ needs prioritized through Build Request, FMT, and weekly KANBAN syncs. Reinforced safe, transparent decision-making (escalated technical risks when needed).
Change & innovation
Drove improvements (SWIMLANE reduction, AI triaging pilots, SWIL process updates, CPU load estimation initiative) and supported tool/process rollouts despite tooling changes and the KPIT COMR decommission.
Examples of Leveling-grade behaviors
Demonstrated “Lead as One Team” by integrating external teams (TCS/Dumarey/KPIT) into SWIL operations and running unified weekly build request meetings.
Demonstrated “Move with Urgency” by leading weekend/extended hours efforts during critical phases and preventing hot/cold trip cancellations.
How performance compares to peers / organization expectations:
Scope & stretch: Assumed responsibilities substantially beyond typical EGM scope during interim leadership (led all SWIL relevant Build Factory build activities from 4/17/2025–9/1/2025) and continued to lead multiple domains concurrently—this represents above-average scope and successful stretch into areas previously covered by two EGMs.
Delivery / reliability: Achieved above-peer reliability — no late builds attributable to SWIL teams, on-time SDV deliverables, and a seamless KPIT → TCS transition, which reflects top-quartile operational execution relative to similar groups.
People & integration: Demonstrated stronger cross-team integration and faster ramp of hires than peers (rapid integration of hires from SWIL Discipline Lead forums with minimal ramp needed).
Process & impact: Provided higher than typical contribution to organizational process improvement (Jira dashboard, Pull-Ahead rules → SWIMLANE reduction), translating to measurable downstream benefits (expected cost and workload reduction).
Overall, compared to similar leaders across Build Factory and Deployment domains, your performance is at or above expectations on delivery, people development, and cross-functional influence.
Unique conditions that influenced performance (positive & negative):
Positive context / enabling conditions
Immediate leadership gaps required rapid assumption of expanded responsibilities (4/17/2025 onward). This created opportunity to standardize build processes, expand SDV ownership, and accelerate staffing and integration decisions.
Strong stakeholder support (e.g., SWIMs, PMO, Infrastructure leads) via daily/weekly syncs accelerated problem resolution and enabled on-time delivery.
Challenging context / headwinds
Major tooling changes and the decommissioning of the KPIT COMR team created transitional friction and required building alternate support and training paths quickly.
Reorganization (effective 9/1/2025) changed reporting and domain ownership mid-year; this required re-scoping strategies, reassigning resources, and establishing new communication paths while still meeting delivery commitments.
Limited HC and constrained role coverage for emerging priorities (SDV, PHEV, Battery) increased reliance on extended hours and temporary backups; ongoing HC approvals and infrastructure stability are critical to sustain delivery.
Partial loss of PM support (Srini moved roles mid-2024) increased operational load and required stepping into roles previously covered by others.
The very first thing we have to do is manage our anxiety:
1- by greeting your anxiety,
2- reframing as a conversation,
3- being in the present moment.
Four steps, that will help you speak spontaneously:
First you get out of your own way (point at things and call them the wrong name.)
Second, Give gifts (see your interactions as ones of opportunity, not challenges.)
Third, take the time to listen, listen.
Fourth, use structures.
The first useful structure is the problem, solution, benefit, structure.
Second structure is the what? So what? Now what? Structure. You start by talking about what it is, then you talk about why it's important, and then what the next steps are. This is a wonderful formula for answering questions.
You are a highly intelligent and accurate sentiment analyzer specializing in the financial markets. Analyze the sentiment of the provided text
"Negative".
Your output must be exactly a JSON object. The value must be
object with three keys:
"category",
"score", and "rationale". Do not output any additional text.
For example, your output should look like:
"shortTermSentiment": {
"category": "Positive",
"score": 0.7,
"rationale": "...."
Now,
analyze the following text and
produce your JSON output:
Now, analyze the following text and produce your JSON output:
{{JSON. stringify($json.articles) }}
I started the filter feature, the coloring doesn't work:
https://bfemuniversity.com/BCS/B_InvestN/display_M_earnings_Cont.php
Try and see if chatgbt can fix that.
Films Included:
While I can't create or provide actual images directly, I can certainly help you write the full text of the story and describe in detail what each illustration could look like. This will give you a complete guide to creating the book, which you can then share with an illustrator or use as inspiration for your own drawings.
Here’s the full text of *"Kedi's Journey: A Tale of Istanbul"*, along with detailed descriptions of the illustrations for each page:
---
### **Page 1–2: Introduction**
**Text:**
In a cozy corner of Istanbul, where the Bosphorus sparkles like liquid gold and the air is filled with the scent of spices, lived a fluffy little kitten named Kedi. Her fur was soft and gray, her paws were tiny but quick, and her green eyes sparkled with curiosity. Every morning, she would stretch on the rooftop of her home, watching the city wake up below.
**Illustration Description:**
A panoramic view of Istanbul at sunrise. The Bosphorus shimmers in the background, with boats gliding across its waters. In the foreground, Kedi stretches on a red-tiled rooftop, surrounded by pots of blooming flowers. Behind her, minarets rise into the sky, and seagulls fly overhead.
---
### **Page 3–4: Getting Lost**
**Text:**
One breezy morning, as Kedi played near the window, a bright red scarf fluttered past. It danced in the wind like a flame, teasing her whiskers. Without thinking, Kedi leapt after it, chasing it down the narrow cobblestone streets. But soon, the scarf disappeared, and Kedi realized she was alone in a part of the city she didn’t recognize.
**Illustration Description:**
Kedi crouches nervously in a bustling street. Around her are colorful shops selling rugs, lanterns, and ceramics. People walk by, carrying baskets of fresh produce. The red scarf flutters away in the distance, just out of reach.
---
### **Page 5–6: Sultanahmet Square**
**Text:**
Kedi wandered until she reached Sultanahmet Square, where grand mosques stood tall against the blue sky. There, she met a kind street musician playing his bouzouki. He smiled when he saw her and offered her a piece of gözleme wrapped in paper. “Little one,” he said, “even the smallest journeys lead somewhere.”
**Illustration Description:**
The square is alive with activity. The Hagia Sophia and Blue Mosque dominate the background. The musician sits cross-legged on a rug, strumming his instrument. Kedi nibbles on the gözleme, looking up at him with gratitude.
---
### **Page 7–8: Kadıköy Market**
**Text:**
Next, Kedi found herself in Kadıköy, a lively market filled with the smells of roasted chestnuts and freshly baked bread. A group of pigeons gathered around her. One old pigeon named Felek hopped closer. “If you’re lost,” he cooed, “look for the minarets—they’ll guide you home.”
**Illustration Description:**
A vibrant market scene. Stalls overflow with fruits, vegetables, and spices. Pigeons perch on crates and flutter around Kedi, who tilts her head curiously as Felek speaks to her. Minarets peek above the rooftops in the distance.
---
### **Page 9–10: Galata Bridge**
**Text:**
Following Felek’s advice, Kedi headed toward the Galata Bridge. She hesitated at the edge, watching the waves crash below. Just then, a fisherman noticed her. “Careful, küçük kedi,” he said gently, lifting her onto the bridge. Together, they crossed safely, and he pointed her toward Galata Tower. “From there, you can see the whole city.”
**Illustration Description:**
The Galata Bridge stretches across the water, packed with fishermen and pedestrians. Kedi looks nervous at the edge, while the fisherman kneels beside her, offering reassurance. In the background, the Golden Horn glistens.
---
### **Page 11–12: Climbing Galata Tower**
**Text:**
Kedi climbed the winding stairs of Galata Tower until she reached the top. From there, she saw all of Istanbul spread out before her—the domes of mosques, the winding streets, and the shimmering waters of the Bosphorus. For the first time since getting lost, she felt hope. “I can find my way back,” she whispered to herself.
**Illustration Description:**
A breathtaking view from the top of Galata Tower. Kedi perches on a windowsill, gazing out at the cityscape bathed in golden sunset light. The illustration captures the vastness and beauty of Istanbul.
---
### **Page 13–14: Finding Familiar Scents**
**Text:**
With renewed determination, Kedi followed her nose. The smell of grilled mackerel led her through familiar streets, past bakeries and tea houses. Each step brought her closer to home. She meowed softly, hoping someone would hear.
**Illustration Description:**
Kedi trots through a quieter neighborhood. Steam rises from a grill where a vendor cooks fish. Streetlights begin to glow as evening falls, casting a warm orange hue over the scene.
---
### **Page 15–16: Reunion**
**Text:**
Finally, Kedi turned a corner and saw her house. Her family rushed out, calling her name. Her human sister scooped her up, hugging her tightly. “We were so worried!” she cried. That night, they celebrated with a feast under the stars, grateful to have their brave little kitten back.
**Illustration Description:**
A heartwarming reunion scene. Kedi’s family gathers outside their home, smiling and laughing. Lanterns hang above them, and plates of food sit on a low table. Kedi purrs contentedly in her sister’s arms.
---
### **Page 17–18: Closing Scene**
**Text:**
As Kedi drifted off to sleep that night, she thought about her adventure. Though she had been scared, she had also discovered the kindness of strangers and the magic of Istanbul. And most importantly, she had learned that no matter how far she roamed, there was always a place where she belonged.
**Illustration Description:**
Kedi curls up in her bed, nestled among cushions. Through the window, the lights of Istanbul twinkle in the distance. The mood is peaceful and cozy, with a sense of closure.
---
### Final Notes:
This text provides a rich narrative that can be paired with vivid illustrations. If you’d like, I can suggest tools or resources for finding illustrators, or we can brainstorm additional creative elements to enhance the story further. Let me know how you'd like to proceed!
**Final Answer:** $\boxed{\text{The full text and illustration descriptions are provided above.}}$
Use https://bolt.new to convert BCS into an iPhone app.
Use google sign in for the app.