Case Study 03: GlobalTrade Logistics — Presentation Notes
AI-Generated Content — Use for Reference Only
This content is AI-generated and has only been validated by AI review processes. It has NOT been reviewed or validated by certified Salesforce CTAs or human subject matter experts. Do not rely on this content as authoritative or completely accurate. Use it solely as a reference point for your own study and preparation. Always verify architectural recommendations against official Salesforce documentation.
Presentation Format
Total time: 30 minutes presentation + 30 minutes Q&A Strategy: Go deep on 3 high-risk decisions, summary-level on 6 supporting artifacts
Opening (2 min)
“GlobalTrade Logistics faces a triple challenge: consolidating three fragmented Salesforce orgs, integrating a cold-chain acquisition, and managing 413 million historical tracking events growing at 50 million per year. My solution prioritizes three decisions that determine success or failure: the LDV strategy, carrier integration consolidation, and multi-region security with data residency.”
Show System Landscape. Frame the scale: 5,800 users, 18 countries, 413M records, 40+ carrier APIs, 24-month timeline. State the single-org decision and Hyperforce choice.
Deep Dive 1: LDV Tiered Storage (6 min)
“The combined tracking volume is 413 million records. The NA org already shows 8.2-second page loads with 210M — combining all orgs makes this worse.”
Three-tier model: hot (90 days, ~12M records, standard objects, sub-3s queries), warm (90 days-2 years, Big Objects, async SOQL), cold (2-5 years, Data Cloud, analytics/compliance). Nightly batch migrates hot to warm. Shipment detail page: hot events load immediately; “Load Full History” button triggers async query to Big Objects. Trade-off: operational complexity of two storage mechanisms, but alternative is an unusable org.
Deep Dive 2: Carrier API Canonical Model (6 min)
“Currently 40+ point-to-point integrations across three orgs. When a carrier makes a breaking change, it takes weeks to diagnose which org is affected.”
MuleSoft API-led connectivity with a Canonical Shipment Event schema. Each carrier gets a thin system API translating native format. New carrier = one system API, zero changes to Salesforce. Top 10 carriers (80% volume) migrate in Phase 1; remaining 30 over 12 months. FrostGuard follows the same pattern: MQTT-to-MuleSoft bridge aggregates 60-second readings into 5-minute summaries; excursion alerts bypass aggregation for 2-minute SLA.
Deep Dive 3: Multi-Region Security (5 min)
“Single global org creates tension between unified visibility and regional isolation.”
Private OWD + Territory Management for 18 countries. German rep sees only German accounts by default. 4,200 global accounts get criteria-based sharing to relevant regional teams. EU data residency: Hyperforce Frankfurt. Japan/Singapore: Shield encryption on specific fields. Sensitive data (hazmat, denied-party, pharma): Restriction Rules + permission set. Audit trail via Shield Event Monitoring.
Supporting Artifacts (7 min)
Identity (1 min): Entra ID SAML 2.0 + SCIM for 5,800 employees. Portal: Salesforce Identity + MFA; enterprise clients federate. FrostLine: JIT provisioning via Entra.
Data Migration (1.5 min): Three-phase: Phase 1 consolidates accounts and migrates NA. Phase 2 handles EU (MuleSoft abstracts SAP upgrade). Phase 3 migrates FrostLine. Account dedup: Informatica matching (Company Name + Tax ID), manual review for top 200 by revenue.
Governance (1 min): GARB for cross-region changes. Regional admin teams for local config within guardrails. All automation via Flow or Apex (no Process Builders). All integrations through MuleSoft.
Environment (1 min): Full Copy for performance testing at 413M-record scale. Three regional Partial Copy for independent UAT (EU tests GDPR automation). Dev sandboxes per workstream.
Roadmap (1.5 min): 24-month program with phase overlap. Foundation + NA by month 8. EU starts month 6 (data extraction during NA parallel run). Cold-chain month 12. EU SAP swap month 16-18 insulated by MuleSoft. Carrier consolidation top-10-first over 12 months.
Transitions
- Opening to LDV: “Let me start with the highest-risk technical decision — handling 413 million tracking events.”
- LDV to Carriers: “The tracking data feeds in through 40+ carrier integrations. Let me show the consolidation approach.”
- Carriers to Security: “Now that data flows from everywhere, the question is: who sees what, in 18 countries with different laws?”
- Security to Supporting: “With the three highest-risk decisions covered, let me walk through the remaining artifacts.”
- Supporting to Close: “Before I wrap up, the three biggest risks and how my architecture mitigates them.”
Closing (2 min)
Three risks and mitigation:
- LDV performance: Tiered storage, daily CRM Analytics monitoring, trigger at 15M hot-tier records
- EU dual transformation (SF + SAP): MuleSoft abstraction; EU SF cutover month 10, SAP swap month 16 — never simultaneous
- Portal at 8K concurrent: CDN caching, LWC lazy loading, MuleSoft cached tracking API, 2-month load test phase
“This is a consolidation where architecture must balance global unity with regional autonomy, handle extreme data volumes, and sustain 40+ integration points — without disrupting 35,000 clients tracking shipments in real-time.”
Timing Checkpoints
| Segment | Duration | Cumulative |
|---|---|---|
| Opening | 2 min | 2 min |
| LDV Deep Dive | 6 min | 8 min |
| Carrier Deep Dive | 6 min | 14 min |
| Security Deep Dive | 5 min | 19 min |
| Supporting Artifacts | 7 min | 26 min |
| Closing | 2 min | 28 min |
| Buffer | 2 min | 30 min |