Edit Summary
cm366TSJwR-Q1BeojMKKNJxCshb_F0q8FZEbomjrS1ZMgIcm-nLHbboU5U66GMQtTwV159-UFMd_kCWdVI19tz_l6xOnUtdbmuj4Ldp9K3GRJg==
Back
Edit the source note directly. Frontmatter stays at the top.
0. Properties - Meeting Date: Unknown - Meeting Type: Call - Note Type: Summary - Attendees: Scott Warner, Bernd Obermeyer, Shawn Remick 1. Meeting Summary We aligned on near-term IT priorities tied to HQ coordination and the Shaper environment. Catherine at HQ will organize and own the IT swim lanes there and will be our primary contact to drive clarity and structure. Shawn confirmed that, in roughly 30 days, we will move their entire facility footprint to Lebanon from an IT perspective. I reiterated that anything with storage must return to Lebanon for data sanitization before any reuse or disposal to prevent any Shaper data leakage. Shawn has already done an onsite assessment and will bring repair, hardware-in-the-loop testing assets, and data-related systems into Lebanon, ensuring developers have continuity by standing up a server here and migrating their on-prem workloads with no downtime. General employees are largely cloud based, so business disruption should be minimal. We agreed to start with a technical-only working session on the Microsoft 365 multi-tenant topic and a walkthrough of the current infrastructure. Bernd will schedule and include the right technical stakeholders on his side. The spirit is to review together before deciding next steps so we avoid rework, duplicated accounts, or unnecessary complexity. The user base in scope is very small - six people - which should help us consolidate into our internal systems efficiently. Shawn shared positive feedback on momentum around SAP integrations and a Microsoft data lake, as well as the OneDrive initiative. He flagged broader O365 and identity topics we need to work through after the initial tenant session, including SSO approvals, Copilot enablement, and meeting recording. We also discussed a path to resolve SawStop developer admin access needs with a security-compliant approach, ideally through separate admin identities or just-in-time elevation rather than persistent local admin. There is some hesitance due to past friction with Ronnie, but we agreed to collaborate on a practical, policy-aligned solution and rebuild mutual confidence. I will summarize the broader issues and proposed agenda for the follow-on conversation so Bernd can identify the right participants. Separately, I will seek approval for an April HQ trip and coordinate timing with Bernd if approved. 2. Attendee List - Scott Warner - Bernd Obermeyer - Shawn Remick 3. Action Items - Bernd Obermeyer - Schedule the initial technical-only meeting for the infrastructure walkthrough and Microsoft 365 multi-tenant discussion. Include Marcel Crevo, Stefan Hooper, and Michael Crevo on the HQ side. - Scott Warner - Send Bernd a summary email outlining the broader O365/identity items (SSO approvals, Copilot enablement, meeting recordings) and the SawStop developer admin-access topic, with suggested stakeholders. - Scott Warner - Call Matt Howard to secure approval for the April HQ trip. If approved, coordinate dates with Bernd. - Catherine (HQ IT) - Drive structure across HQ IT swim lanes and align with our team; confirm meeting time with us. - Shawn Remick - Maintain the asset and system inventory from the Shaper site visit and coordinate the move to Lebanon, including: - Standing up a server in Lebanon to migrate developer workloads with no downtime. - Relocating repair and hardware-in-the-loop testing equipment and engaging Wolfram as needed. - Coordinating data-bearing device return to Lebanon for sanitization prior to disposition. - Working with HQ on Google Workspace/Google Cloud items, including whether to start new accounts or migrate email and documents, and proposing a retention and backup plan for legacy Google data. - Scott Warner and Shawn Remick - Enforce the data-handling standard: no devices with storage leave control until sanitized in Lebanon; decide disposition post-cleaning. - Scott Warner and Bernd Obermeyer - Jointly convene a follow-up session on SawStop developer admin access to agree on a compliant path forward (separate admin identities and/or just-in-time elevation), with the right HQ stakeholders. 4. Relevant Timelines - In approximately 30 days - Move the facility footprint to Lebanon from an IT perspective, with developer server cutover designed for zero downtime. Linked action items: Shawn Remick (migration), Scott/Shawn (data sanitization enforcement). - March - OneDrive-related initiatives are slated; monitor impact and dependencies for our teams. - April (pending approval) - Potential HQ trip. Linked action items: Scott Warner (approval and coordination). 5. Additional Notes - Data governance remains paramount. All storage-bearing assets from Shaper must be returned to Lebanon for wiping before disposal or redeployment. This is non-negotiable to prevent data leakage. - Multi-tenant stance: begin with a technical deep dive before any structural decisions. Given the very small in-scope user base, consolidating into our internal systems is the preferred end state. - Cloud services posture: partial access to Shaper's Google environment today; several in-house tools complicate visibility. We need a measured plan for account strategy, data migration, and historical retention/backups. - O365/identity friction points are recurring themes for US teams with small local IT staff. We need an improved, scalable approval and enablement model for SSO, Copilot, and meeting recording that balances security with velocity. - SawStop developer access: do not allow normal user accounts to be local admins. Target a phased solution with separate admin identities or just-in-time access. Acknowledge prior hesitance, but reset with clear requirements and a cooperative approach. - Bernd will join the technical sessions to ensure HQ stakeholders engage constructively and we build consensus quickly.
Save