Edit Summary

TBBzYZ0D7k-PbvJeuJesZiOU5LYFMfAArefB4PhwMgHpiIh0NMrj6sIOswgyE794KF258u2AEZ0FdgmreveSucPOGbi4luCiu5ODDj2pYVDp

Back

Edit the source note directly. Frontmatter stays at the top.

## Properties
- Meeting Date: Unknown
- Meeting Type: 1x1
- Note Type: Summary
- Attendees: Scott Warner, Amity Sendama

## 1.  Meeting Summary
I spoke with Amity to align on priorities around the SAP restore issue and whether we needed to move the AdaptDx meeting.  Given the scale of the disruption, I agreed it made sense to try to reschedule AdaptDx so I could at least join the beginning of the 10:00 AM logistics discussion and understand the recovery plan at a high level.

I shared the current state of the SAP recovery effort as I understood it.  Deliveries that were printed but not picked need to be reassigned new delivery numbers, partially picked deliveries need to be reimported, and there are shipments already on trucks that are not fully visible in the system.  On top of that, we will need inventory reconciliation to confirm account accuracy.  My assessment was that logistics could not reasonably be brought back in that day given the amount of rework and uncertainty.

We also discussed the broader impact on repair and finance.  I had already sent an email to the ELT group but had not yet heard back.  Since I had not received clarity on Pascal's position, I noted that I would likely reach out to him directly rather than wait for Robert to manage that side.  Amity also noted that a finance meeting would likely determine who from her team would participate in the restore process.

Finally, I confirmed there is a dedicated Teams workspace for the SAP recovery effort, created through Marcus Moser, and noted that Amity would likely be added once finance participants were identified.

## 2.  Attendee List
- Scott Warner
- Amity Sendama

## 3.  Action Items
- [Amity Sendama] Try to reschedule the AdaptDx meeting so I can attend at least part of the 10:00 AM logistics meeting.
- [Scott Warner] Join the 10:00 AM logistics meeting, if possible, to get an overview of the SAP restore and recovery plan.
- [Scott Warner] Reach out directly to Pascal to ensure he has what he needs to make a decision on repair operations.
- [Scott Warner] Continue monitoring ELT responses regarding operational decisions tied to the SAP disruption.
- [Amity Sendama] Participate in the finance discussion to determine who from her team should be assigned to the SAP restore process.
- [Finance team / Amity Sendama] Identify finance participants for the SAP restore effort so they can be added to the dedicated Teams workspace.

## 4.  Relevant Timelines
- 10:00 AM - Urgent logistics meeting regarding the SAP restore and operational recovery.
- Same day - Target to determine whether the AdaptDx meeting should be moved.
- Same day - Need clarity on repair and finance participation in the SAP restore effort.
- Same day - Finance expected to identify team members for the restore process and Teams assignment.

## 5.  Additional Notes
- The SAP interruption created a four-hour gap with incomplete transaction visibility, which raises significant concerns around shipment status, delivery records, and inventory accuracy.
- Key recovery tasks include reassigning delivery numbers, reimporting partially picked deliveries, identifying shipments already on trucks, and reconciling inventory and account impacts.
- My view was that logistics operations were too disrupted to resume normally that day.
- There is a dedicated Teams channel for the incident: "SAP P10 Restore 3/26".
- The immediate theme was triage and visibility - understanding what happened during the outage window and assigning the right people into the restore process quickly.