WorkWise
Climate-Aware Construction Task Scheduling & Workforce Communication Engine
A predictive heat-strain and occupational safety platform designed for Indian construction sites. Replaces crude 12:00–15:00 clock rules with peer-reviewed Liljegren (2008) physical WBGT modeling, CAQM GRAP statutory dust-ban gates, and guardrailed Amazon Bedrock operational briefings.
01. Research Audit: The Flaw of Rigid Clock Rules
Across India, more than 50 million construction workers face extreme summer temperatures exceeding 45°C. Today, contractors rely on crude rules of thumb: a mandated site shutdown from 12:00 to 15:00.
During severe summer heatwaves in Delhi NCR, 80.4% of shift hours outside the 12:00–15:00 break already breach occupational heat safety limits for acclimatized workers (and 95.8% for unacclimatized workers). Hazardous Wet-Bulb Globe Temperatures occur as early as 09:30 AM, while safe, shaded indoor tasks between 12:00 and 15:00 are shuttered indiscriminately.
02. Architectural Philosophy: Safety Engine Decides, AI Explains
┌─────────────────────────────────────────────────────────────┐
│ DETERMINISTIC SAFETY ENGINE DECIDES; AI EXPLAINS. │
│ NO SAFETY GUARANTEES. NO FABRICATED WEATHER DATA. │
└─────────────────────────────────────────────────────────────┘
[ Weather Feeds + CAQM Stage ] ──► [ Python Safety Engine (Liljegren WBGT) ]
│
▼
[ UI Heatmap & Schedule DAG ] ◄─── [ Ground-Truth Operational Plan ]
│
▼
[ Amazon Bedrock (Converse API) ]
│
▼
[ Strict Guardrail Filter ]
(Rejects claims promising '100% safety'
or overriding deterministic limits)03. Physical WBGT Modeling
Unlike simple Heat Index calculations, WorkWise implements the peer-reviewed Liljegren (2008) formulation, integrating:
- ▸Dry-bulb temperature ($T_a$) and relative humidity
- ▸Natural wet-bulb temperature ($T_{nw}$) via psychrometric energy balance
- ▸Black globe temperature ($T_g$) via radiative equilibrium with solar irradiance
- ▸Wind speed ($u$) convective cooling dynamics
04. Automated Testing & Pytest Harness
All thermal and scheduling algorithms are tested against published benchmarks: