Tower
SOS
Mid-Shift
EOS
More
↻ 0 save(s) queued
Executive Dashboard
Real-time labor intelligence — MCL Operations
At a Glance — B193 — Current Week
| Function | Plan OPH | Actual OPH | Delta | % Target | Status |
|---|
Building Performance — Current Week
OPH Trend vs RFQ Target
Labor Hours — Plan vs Actual / Forecast
Headcount Gap — Required vs Contracted
OT Exposure & Cost Trend
Bowler Charts
Maersk Way Visual Management — Green = on/above plan • Amber = 1–3% below • Red = >3% below
Labor Simulation
Simulate operational demand, labor requirements, staffing gaps, and productivity impact based on forecasted workload and operational assumptions.
ⓘ Select a building and customer above to begin the simulation.
Prior Day Plan (PDP) Draft
PDP — Prior-Day Planning
Prior-day planning — volume forecast, shift assumptions, and HC plan for the next shift. Feeds Start of Shift and productivity tracking.
Start of Shift
SOS — Start of Shift Workflow
Draft
Confirm actual HC present, set daily goals per function, lock the planned baseline
Building
Account (Customer)
Date
Shift — supervisor handles one shift per SOS session
Departments
Select allClear
Actual HC Present & Shift Hours by Function
Expected Output vs Plan
Known Redeployments
Daily Goals by Function — SOS Baseline
| Dept | Function | Default Hrs | Today’s Hrs | UPH Target | Plan HC | HC Present | Gap | Expected Output | Plan Vol | Vol Target |
|---|
End of Shift
EOS — End of Shift Workflow
Record final actuals, calculate Performance Bridge variances, assign root cause, capture corrective actions
Building
Account (Customer)
Date
Shift — match the shift the supervisor finalized at MOS
Departments
Select allClear
Performance Bridge — Plan vs Actual
| Function | PDP Plan Vol | SOS Plan Vol | Actual Vol | Δ vs PDP% | Δ vs SOS% | Plan PH | Actual PH | Plan UPH | Actual UPH | Status |
|---|
Shift Notes — what happened this shift; pre-filled from MOS
Overall Accountability — who owns this shift's variance
Root Cause & Corrective Actions — per-function causes for in-scope misses
Handoff to Next Shift — forward-looking actions
Attendance & Hours
PENDING T&A
⏳ These fields populate from the T&A upload after EOS submission — no need to fill at EOS.
Absent Count
Attrition Count
Reg Hours
OT Hours
OT%: —
Productivity Tracking
Historical actuals — plan vs actual volume, hours, OPH, cost per unit
Period
Department
OPH Trend vs RFQ Target
Volume — Plan vs Actual
Daily Productivity Log
| Date | Shift | Function | Plan Vol | Act Vol | Vol Δ% | Plan Hrs | Act Hrs | Plan OPH | Act OPH | OPH Δ% | Root Cause | Status |
|---|
Shift Monitor
Live shift performance — auto-refreshes every 5 minutes
Loading shift monitor…
Labor Cost
T&A Upload
Upload time & attendance data to calculate cost per unit, OT%, and labor cost variance
Employee Type
Upload T&A Report
Supports ADP e-TIME (internal, per-day punch export) and SimpleVMS (temp, per-worker) reports, plus a generic CSV — uploaded as .csv / .tsv or .xlsx. The system is auto-detected; worked time only (Non-Worked & PTO excluded). Each upload is tracked by customer • building • system • period.
⇧
Drop T&A CSV / Excel here
or click to browse
Labor Cost by Department & Function
| Department | Function | Agency | Emp Type | Reg Hrs | OT Hrs | OT% | Total Cost | Volume | Cost/UOM | Status |
|---|
Configuration
Admin
MCL LIFT v6.7.95
Manage global network settings and per-site operational configuration
Buildings
Regions & Countries
Customers
Agencies
Roster Mappings
Archetypes
Departments
Labor Types
Maersk Calendar
All buildings in the MCL network
| Code | Name | Archetype | Region | Country | Timezone | Customers | Default | Status |
|---|
Admin & Access Management
Users, roles, permissions, and visibility scope
Users
Access Requests
Roles & Scopes
Display Profiles
Help & SOP
MCL LIFT Standard Operating Procedure — User Guide · v6.7.95
Azure Deployment
Production architecture • React + FastAPI + SQL Server + Microsoft Entra ID
Pilot mode active. This HTML prototype stores data in browser localStorage. Production deployment will use the React + Vite + FastAPI stack with Azure SQL Database and Microsoft Entra ID single sign-on.
Production Architecture
1
Frontend — React + Vite
Deployed to Azure Static Web Apps. Same UI as this prototype, served as a production SPA.
2
Backend — FastAPI (Python)
Deployed to Azure App Service. REST endpoints for SOS, EOS, Simulation, Users, Config, Benchmarks, Notifications.
3
Database — Azure SQL
35-table schema. Replaces all localStorage in this prototype. Production-grade durability and multi-user access.
4
Authentication — Microsoft Entra ID
Single sign-on via Maersk M365 tenant. Replaces the mock user switcher in this prototype.
Pilot → Production Migration
1
Validate workflows in this prototype
B193 team uses the HTML build to confirm PDP, SOS, MOS, EOS modules match daily operations.
2
Lock specifications
Once team-approved, every screen, calculation, and data field becomes the spec for the React build.
3
Generate React + FastAPI codebase
See mcl-lift-project.zip — scaffold ready. PDP/SOS/EOS modules regenerate from final HTML version.
4
Deploy to Azure
Static Web Apps + App Service + SQL Database. Configure Entra ID app registration. Migrate pilot data.
5
UAT and cutover
Parallel run with HTML prototype until production is validated. Sunset prototype after go-live.
Current Pilot Capabilities
What works now: All 15 modules functional with localStorage persistence. 6 mock users with full role hierarchy. Filter scope by region/country/division/building/customer. SOS/MOS/EOS daily cycle. Labor Simulation sandbox.
What requires production stack: Real multi-user data sharing across shifts and buildings. Entra ID single sign-on. Trending rate updates persisted in database. Roster integration with T&A system. Audit log of all changes.
What requires production stack: Real multi-user data sharing across shifts and buildings. Entra ID single sign-on. Trending rate updates persisted in database. Roster integration with T&A system. Audit log of all changes.
Control Tower
All Buildings
Updated: just now
• Auto: 5 min
Mid-Shift Tracker
MOS — Hourly Check-in
Track actual volume each hour — see projected end-of-shift and adjust headcount as needed
Building
Account (Customer)
Date
Shift — match the shift the supervisor locked at SOS
Departments
Select allClear
Hourly Check-in — enter HC + Volume per hour per function (auto-saved)
Hours shown: 0
Shift Projection
Auto-saved. Changes persist as you type.
Click Final Submit in the page header when the shift is complete.
Volume Trend — cumulative vs plan
Hourly UPH — Planned vs Actual
Function Breakdown
| Function | SOS Plan | To Date | Hourly Throughput | Projected | Remaining | Throughput Needed | HC Needed | Status |
|---|
Operational Benchmarking