Scope & Approach / Confidential Draft

Driver Yard Maps —
Getting the right map
into the right hands.

A phased approach to solving distribution for yard maps across FedEx facilities — delivering a working portal before peak season, with a path to interactive wayfinding beyond.

<1,000
US & Canada Facilities
2
Phases
Aug/Sep
Phase 1 Target
0
App Installs Required
Scroll to explore
The Challenge

Drivers are landing blind at unfamiliar facilities.

Network 2.0 has expanded where linehaul drivers go — but hasn't given them the information they need when they arrive. The gap isn't map creation. It's distribution.

🗺️
No yard map at the moment of need
The previous static page on mygroundbiz.com was un-published due to outdated content and weak engagement. There's currently no centralized way for a driver to pull up a map when they arrive.
🏭
Unfamiliar facilities, no guidance
Drivers don't know where to pull off, where to drop dollies, where the restrooms are, or what location-specific rules (STA, esported requirements, gate procedures) apply.
📋
Creation is solved — distribution isn't
Facility managers already produce yard map PDFs from a standardized PowerPoint template. The missing piece is getting those maps to drivers in the field, at the right moment, without friction.
No map. Unfamiliar yard. Idle clock running.
— Driver pain point surfaced across the service provider cohort
What FedEx Has Already Built
A standardized PowerPoint template where Linehaul / Station Managers screenshot Google Maps, overlay required elements — entrance/exit, dispatch, fuel island, drop zone, dolly zone, trailers, restrooms, address, location rules, directional flow — and export to PDF.
✓ Creation side is handled.
Guiding Principles

Six principles that shaped this solution.

These came directly from the kickoff conversation and the FedEx requirements list — not agency defaults.

01
Drivers, not AOS owners, are the end users
The solution puts maps directly into driver hands without account creation or an intermediary printing and forwarding the map.
02
Two-tier access model
Drivers reach maps via QR code — no login, no friction. TSPs and location managers authenticate via single sign-on on the upload side.
03
No native mobile app required
App Store, Play Store, and MDM friction outweigh any advantage. Web-based delivery only — Progressive Web App available in Phase 2 if push notifications are wanted.
04
Independent of MGB and Sitecore
Lives as its own product on Nishtech-managed infrastructure — no infosec or RIT review cycles that could jeopardize the pre-peak timeline.
05
Real-time publishing
When a manager uploads or updates a map, drivers see it immediately. No batch publish cycle, no waiting.
06
Phased delivery
Ship the must-haves before peak; evolve toward the richer interactive experience without rebuilding the platform.
Proposed Approach

Two phases of the same product.

Phase 1 ships as the MVP for August / September. Phase 2 is the evolution layered onto Phase 1's foundation — individual maps upgrade from PDF to interactive without the platform being rebuilt.

Phase 1 — MVP
Driver Yard Map Portal
August / September 2026
QR-code portal, existing PDFs, smart lookup, SSO-authenticated CMS for managers
Phase 2 — Interactive
Interactive Wayfinding
Post-Phase 1, rolling rollout
Google Map with custom pin layer, drag-and-drop authoring, PWA with push on arrival
Capability Phase 1 — MVP Phase 2 — Interactive
Driver access QR code → secured web portal QR code + proximity push notifications
Map format Existing PDFs (PowerPoint template output) Interactive Google Map with custom pin layer
Find my map Smart lookup (ZIP, alpha, numeric) + browser geolocation Push notification on arrival at the facility
Authoring CMS — Linehaul/Station Managers upload PDFs + tags Drag-and-drop pin authoring on Google Maps base layer
Manager access Single sign-on for TSPs / location managers Same SSO, expanded role model
Map publishing Real-time — live the moment they save Real-time, with structured-data versioning
Distribution Web — Safari / Chrome, no install Progressive Web App (installable, no app store)
Target launch Pre-peak — Aug / Sep 2026 Post-Phase 1, per facility
Requirements Alignment

How we're delivering against your requirements.

Every requirement from the FedEx list is mapped to the phase that delivers it — and how.

FedEx Requirement Phase How It's Delivered
Map creation by Linehaul / Station Manager via PowerPoint template Phase 1 Existing template stays in use; portal accepts the PDF output
Required map content: satellite image, entrance/exit, dispatch, fuel island, drop zone, dolly zone, trailers, restrooms, address, location rules (STA), directional flow Phase 1 Captured as PDF + tagged metadata; structured pins arrive in Phase 2
QR code distributed to drivers, scanned prior to arrival Phase 1 Single QR code resolves to the portal
Centralized URL where all maps are stored Phase 1 Secured web portal on Nishtech infrastructure
Single sign-on access for TSPs Phase 1 SSO on manager / upload side; drivers continue QR-only
Centralized storage with per-location upload by managers Phase 1 Lightweight CMS scoped to each manager's assigned facility(ies)
Smart address lookup by ZIP, alpha code, or numeric code Phase 1 Unified search box accepting all three identifier types
Capability to store all FedEx locations Phase 1 Seeded from FedEx-supplied facility list (<1,000 US / Canada)
Driver access via website, QR code, app if necessary Phase 1 Web + QR; no native app required. PWA option in Phase 2
Real-time upload and availability of map updates Phase 1 Maps go live immediately on save (optional approval step)
Auto pre-population based on location / geo-fencing (nice-to-have) Phase 2 Push notification when driver arrives at a registered facility
Phase 1 — MVP

Driver Yard Map Portal — built for pre-peak.

The lowest-barrier path to getting maps into drivers' hands. Optimized for speed-to-market and minimal infosec surface area. Target: August / September 2026.

Driver Experience — 5-Step Flow
Step 01
📱
Scan QR Code
In-cab, on dispatch sheet, or via existing channels — before arrival
Step 02
🌐
Portal Opens
Safari or Chrome — no app install required
Step 03
🔍
Find the Map
ZIP, alpha, numeric code; browser geolocation; or region filter
Step 04
🗺️
View / Download
Existing PDF from the PowerPoint template
Step 05
📋
Location Notes
STA, esported requirements, gate procedures, check-in rules shown alongside
Manager Experience (CMS)
🔐 SSO Authentication
TSPs and location managers sign in via single sign-on — each scoped to their assigned facility or facilities
⬆️ Upload & Tag
Upload PDF + tag with facility ID, ZIP, alpha, numeric, city/state/region, secure flag, STA flag, free-text rules
⚡ Real-Time Publish
Live the moment they save — no batch cycle. Edit, replace, or retire at any time
✅ Optional Review
Configurable approval step before publish, based on FedEx governance preference
Map Metadata Schema
Facility Identifiers
Facility ID · ZIP code · Alpha code · Numeric code
Map Content Elements
Entrance/exit · Dispatch · Fuel island · Drop zone · Dolly zone · Trailers · Restrooms · Directional flow
Location Rules + Flags
STA requirements · Gate procedures · Check-in instructions · Secure flag · Esported flag · Custom (extensible)
Technical Components
Driver-Facing (Public)
QR Code Generation & Management
Secured Web Portal (Safari / Chrome)
Browser Geolocation + Smart Lookup
↓
Auth Layer
SSO Integration (Manager / TSP side only)
↓
Admin / Data Layer
Admin CMS (Upload, Tagging, Lifecycle)
Tagged Map Storage
Facility Seed Data (~<1,000 locations)
All components on Nishtech-managed infrastructure — fully independent of MGB and Sitecore.
Phase 1 — Indicative Timeline
Discovery & Requirements
~2 wks
Design & Architecture
~2 wks
Build
~6–8 weeks
UAT & Rollout
~2–3 wks
August / September pre-peak launch is achievable on this trajectory, assuming requirements locked by end of May. The extra month vs. an August-only target provides buffer for SSO integration testing — typically the longest unknown in projects of this shape.
Phase 2 — Interactive

Interactive wayfinding — layered on, not rebuilt.

Phase 2 is not a platform replacement. Individual facilities upgrade from PDF maps to interactive Google Map experiences on a rolling basis, without disrupting the rest of the network.

1
Interactive Google Map with custom pin layer
Maps move from static PDFs to a Google Maps base layer with FedEx-defined pins. Entrance, dispatch, fuel island, drop zone, dolly zone, trailers, restrooms, gate, check-in — structured data drivers can tap, zoom, and explore.
2
Drag-and-drop pin authoring for managers
Replaces the PowerPoint template entirely. Linehaul or Station Manager opens their facility on the map, drags pins from a standard library onto the satellite view, and saves. Live the moment they save.
3
Progressive Web App with push notification on arrival
Drivers "install" the portal on their home screen from the browser — no App Store, no Play Store. When they arrive at a registered facility: "You're at the Plano facility — tap to view the yard map."
4
Rolling migration — no big-bang cutover
Phase 1 PDF maps keep working uninterrupted. Facilities migrate to interactive format based on driver volume, operational risk, or ad hoc priority. Real-world Phase 1 data informs which facilities go first.
Phase 2 timeline: To be scoped after Phase 1 launches and real driver feedback is in hand. Initial estimate: 4–6 months from kickoff for a feature-complete v1, with rolling facility migration thereafter.
Why Phasing Works

Five reasons this approach wins here.

The two-phase structure isn't a hedge — it's the right architecture for what FedEx is trying to accomplish.

Speed to market
Drivers get a usable solution in the pre-peak window — not next year. Phase 1 is designed to hit the August / September target with the time and complexity that allows.
Lowest barrier to driver adoption
QR + browser, no install, no login. If drivers won't use it, nothing else matters. Phase 1 removes every reason not to scan.
Preserves existing investment
The PowerPoint template the team has already built keeps working through all of Phase 1. It's not deprecated until Phase 2 is ready to take over.
Real-world feedback shapes Phase 2
Driver behavior on the Phase 1 portal — which maps get pulled, how often, from where — directly informs which facilities to upgrade first.
Budget flexibility
FedEx leadership can fund Phase 1 today and decide on Phase 2 based on observed value, not projected value. Two separate line items — each approvable independently.
Investment

Phased investment. Independent approvals.

Phase 1 and Phase 2 are presented as separate line items — each can be approved independently. Detailed costing finalized within five business days of budget guidance from FedEx leadership.

Phase 1 — Driver Yard Map Portal (MVP)
Pre-Peak MVP
TBD
Covers full Phase 1 scope: discovery, design, build, SSO integration, UAT, and pre-peak rollout. All in, ready to run before peak season.
  • Web portal with smart address lookup (ZIP, alpha, numeric)
  • SSO-authenticated CMS for manager uploads and tagging
  • Browser geolocation + real-time map publishing
  • QR code generation and management
  • Seeded from FedEx-supplied facility list (<1,000 US / Canada)
  • Independent of MGB and Sitecore — Nishtech-managed infrastructure
Directional range — confirmed through requirements lock-in. Revised pricing within 5 business days of budget guidance.
Phase 2 — Interactive Wayfinding Platform
Interactive Evolution
TBD
Scoped after Phase 1 launches and real driver feedback is in hand. Initial estimate: 4–6 months from kickoff to feature-complete v1.
  • Interactive Google Map with custom FedEx pin layer
  • Drag-and-drop pin authoring (replaces PowerPoint template)
  • Progressive Web App with push notification on arrival
  • Rolling facility migration — no big-bang cutover
Ongoing
Platform Support & Hosting
TBD / mo
Infrastructure, security patches, uptime monitoring, and Nishtech support SLA for the running portal.
  • Nishtech-managed hosting environment
  • Security and platform updates
  • Reactive support — defined SLA
Open Items & Next Steps

Three open items before Phase 1 kicks off.

These are the remaining unknowns. Resolving them — especially SSO — is what unlocks the August / September date.

1
SSO provider and scope
Confirm which identity provider TSPs will use (FedEx corporate SSO, a federated provider scoped to this portal, or another arrangement) — and confirm the two-tier interpretation: SSO for managers / uploaders, QR-only for drivers.
⚠ Longest pole — impacts August / September date
2
Manager-to-facility mapping and approval workflow
Confirm whether each Linehaul / Station Manager is scoped to a single facility or several — and whether uploads self-publish or go through a review step before going live to drivers.
3
Seed data delivery
Canonical list of in-scope facilities with ZIP, alpha code, numeric code, address, and assigned manager(s) — needed to populate the system at launch.

Next Steps

Nishtech
Steve & Team
  • Finalize proposal with concrete pricing once budget guidance is received
  • Schedule follow-up to walk through proposal and lock Phase 1 scope
FedEx
Kim & Team
  • Confirm SSO provider and scope (two-tier model)
  • Share canonical facility list (ZIP, alpha, numeric, assigned managers)
  • Provide budget guidance from leadership
Joint
Kim, Steve, Libby, Michael
  • Schedule follow-up to walk through this proposal and lock Phase 1 scope
  • Loop Libby and Michael into all subsequent communications
Target
Requirements locked & Phase 1 kicked off by end of May — to hit pre-peak August / September delivery.