YARDMASTER — S5 Knowledge Architecture Doc

Section 1

Problem Statement

Readymix concrete dispatching is one of the most cognitively demanding coordination jobs in construction logistics. A dispatcher must simultaneously track truck locations, driver hours, plant capacity, mix design requirements, job schedules, and the concrete clock — all in real time, primarily over radio. No single software system sees across all of these domains simultaneously.

The Integration Gap

Jonel (plant batching) and fleet tracking systems (TruckTrax, Verifi, Digital Fleet) are separate products that do not communicate intelligently. The dispatcher is the human bridge.

No Proactive Alerts

TruckTrax can show time-on-job and time-at-washout — but only if the dispatcher manually checks each truck. There are no automatic alerts. No pop-ups. The system is silent until you look.

Plant Disruptions Cascade

When a plant goes down, the dispatcher finds out via phone call — 2 to 5 minutes after the fact. Every minute is trucks moving toward an offline plant.

The Cost of Failure

One missed variable — a truck already loaded, a plant already at capacity — cascades into a missed pour. Missed pours cost $10K–$100K per incident.

90 min

Concrete Clock Limit

$10K–$100K

Cost Per Missed Pour

40+

Trucks Per Dispatcher

0

Proactive Alerts in Current Stack

Section 2

Product Scope Decision

Strategic rationale: The dispatcher feels the pain every shift. Win them first with measurable ROI — prevented pours, response time, reduced cognitive load. The management visibility layer is the upsell after 90 days of operational data. Management features explicitly scoped to V2.

✓ V1 — Dispatcher Layer

▸Real-time truck status monitoring
▸Automated pace alerts (slow trucks, stalled trucks)
▸Plant disruption detection
▸Cross-plant reallocation recommendations
▸Concrete clock monitoring per load
▸Driver push notifications
▸Job schedule integration
▸Multi-system integration hub (Jonel + fleet trackers)

→ V2 — Management Layer

▸Real-time field visibility dashboard
▸Delay escalation notifications to managers
▸Shift performance reporting
▸Historical trend analysis
▸Customer communication automation
▸Executive KPI dashboard
▸Cross-location benchmarking
▸Automated after-action reports

Section 3

Entity Categories — V1 (7 of 9)

Core knowledge nodes powering dispatcher intelligence. Management and Operator entities scoped to V2.

🚛 Truck E1

The primary moving asset. Tracked in real time across location, status, load, and driver assignment.

▸Truck ID / unit number
▸Current GPS location
▸Status (loading, in-transit, on-job, returning, idle, down)
▸Assigned driver
▸Assigned plant
▸Current load (mix design, yardage, batch time)
▸Concrete clock elapsed (minutes since batch)
▸Time on current job site
▸Time at washout
▸Estimated return time

👤 Driver E2

Human operator of each truck. Hours-of-service and availability directly constrain dispatch decisions.

▸Driver ID / name
▸Assigned truck
▸Hours on shift (current)
▸Hours remaining (HOS compliance)
▸Shift start / end time
▸Availability status (active, break, end-of-shift)
▸Current plant assignment
▸Push notification receipt status

🏭 Plant E3

Production facility. Status, capacity, and mix design capability determine truck routing constraints.

▸Plant ID / name / location
▸Operational status (online, degraded, offline)
▸Current batch queue depth
▸Available capacity (yards/hr)
▸Mix designs supported
▸Trucks currently assigned
▸Estimated downtime (if offline)
▸Distance to active job sites

🏗️ Job Site E4

Active pour location. Pour windows and mix requirements are hard constraints — missing them is the core cost event.

▸Job ID / name / address
▸Pour start time (scheduled)
▸Pour window (duration)
▸Required mix design(s)
▸Total yardage ordered
▸Yardage delivered (running total)
▸Trucks currently on site
▸Assigned plant source
▸Customer contact

🧱 Mix Design E5

Specific concrete formulation for a job. Not all plants produce all mix designs — hard routing constraint.

▸Mix design ID / code
▸PSI / strength class
▸Admixture requirements
▸Plants approved to produce
▸Concrete clock limit (minutes)
▸Slump / water-cement ratio
▸Special handling flags

⚡ Dispatch Event E6

Real-time operational occurrence requiring dispatcher awareness or action. The core intelligence feed of YARDMASTER.

▸Event ID / timestamp
▸Event type (delay, disruption, alert, reroute)
▸Triggered entity (truck, plant, job site)
▸Severity (critical, warning, info)
▸Recommended action
▸Dispatcher acknowledgment status
▸Resolution status + timestamp
▸Downstream jobs at risk

🔗 Integration Source E7

External systems feeding data into YARDMASTER. Each operator runs a different combination — YARDMASTER is the hub.

▸System name (Jonel, TruckTrax, Verifi, Digital Fleet)
▸System type (batching / fleet tracking)
▸API status (confirmed open / TBC)
▸Data fields exposed
▸Update frequency / latency
▸Operator assignments
▸Connector build status

Section 4

Knowledge Triples — Sample Set

Subject → Predicate → Object relationships powering YARDMASTER inference. Scenario: Plant Phoenix North goes offline mid-shift.

#	Subject	Predicate	Object	Category
01	Truck_047	is_assigned_to	Plant_Phoenix_North	Truck
02	Truck_047	carries_load	MixDesign_4000PSI	Truck
03	Truck_047	concrete_clock_elapsed	74_minutes	Truck
04	Driver_Ramirez	operates	Truck_047	Driver
05	Driver_Ramirez	hours_remaining_on_shift	2.5_hours	Driver
06	Plant_Phoenix_North	has_status	OFFLINE	Plant
07	Plant_Phoenix_North	estimated_downtime	90_minutes	Plant
08	Plant_Phoenix_South	has_available_capacity	120_yards_per_hour	Plant
09	Plant_Phoenix_South	supports_mix_design	MixDesign_4000PSI	Plant
10	JobSite_Chandler_Office	requires_mix	MixDesign_4000PSI	Job Site
11	JobSite_Chandler_Office	pour_window_closes	14:30_today	Job Site
12	JobSite_Chandler_Office	yardage_remaining	45_yards	Job Site
13	MixDesign_4000PSI	concrete_clock_limit	90_minutes	Mix Design
14	MixDesign_4000PSI	approved_plant	Plant_Phoenix_South	Mix Design
15	DispatchEvent_001	triggered_by	Plant_Phoenix_North	Event
16	DispatchEvent_001	has_severity	CRITICAL	Event
17	DispatchEvent_001	puts_at_risk	JobSite_Chandler_Office	Event
18	DispatchEvent_001	recommended_action	Reroute_3_trucks_to_Phoenix_South	Event
19	Jonel	provides_data_type	Plant_batch_queue	Integration
20	Verifi	used_by_operator	SRM	Integration

Section 5

Driver Workflow — V1 Intelligence Layer

How YARDMASTER monitors and acts at each stage of a driver's shift. Every step currently requires manual dispatcher attention. YARDMASTER makes it automatic.

01

Shift Start — Plant Assignment

Driver checks in at assigned plant. YARDMASTER ingests driver ID, shift start time, HOS clock initialization, and plant assignment from Jonel + fleet tracker. Baseline established.

Entities Active

Driver · Truck · Plant · Integration Source

02

Loading — Batch Confirmation

Jonel confirms batch: mix design, yardage, batch timestamp. YARDMASTER starts the concrete clock. Truck status → LOADING. Destination job site linked. Mix design constraints validated against job requirements.

Entities Active

Truck · Mix Design · Job Site · Plant

03

In Transit — Pace Monitoring

Fleet tracker provides GPS updates. YARDMASTER calculates ETA vs. pour window. If truck is behind pace — automatic alert generated. No manual check required. Concrete clock continues running.

Entities Active

Truck · Driver · Dispatch Event (if alert)

04

On Job Site — Time Monitoring

Fleet tracker confirms truck arrival. YARDMASTER starts time-on-job clock automatically. If truck exceeds expected on-site duration — alert fires. Yardage delivered updates job site running total.

Entities Active

Truck · Job Site · Dispatch Event (if stall)

05

Washout — Return Tracking

Fleet tracker detects washout location. YARDMASTER timestamps washout start and monitors duration. If washout runs long — alert generated. ETA back to plant calculated for queue optimization.

Entities Active

Truck · Driver · Plant

06

Return & Reallocation Check

Truck returns to plant. YARDMASTER checks: Is assigned plant still online? Are there higher-priority jobs needing this truck? If plant is down, automatic reroute recommendation fires. Driver available hours recalculated.

Entities Active

Truck · Driver · Plant · Dispatch Event (if reroute)

07

Plant Disruption — Cross-Plant Intelligence

If Jonel signals plant offline or degraded: YARDMASTER immediately identifies all trucks assigned to that plant, all jobs at risk, available capacity at alternate plants, and mix design compatibility. Dispatcher receives ranked reallocation recommendations — not raw data. This is the core YARDMASTER value prop. No existing system does this automatically.

Entities Active

All 7 entities engaged simultaneously

Section 6

Integration Architecture

Architecture principle: YARDMASTER does not replace Jonel or fleet tracking systems. It sits above them as an integration and intelligence layer — ingesting data from both domains, normalizing it, and surfacing proactive recommendations to the dispatcher.

Jonel

Batching Software

Plant-level batching control. Mix design execution, batch queue management, load tracking, dispatch scheduling module. Advertises open API architecture. Appears universal across target operators.

API: Open (Advertised)

Verifi

Fleet Tracking — SRM

Fleet tracking system confirmed in use by SRM. Provides truck GPS, status, and location data. API access status not yet confirmed — priority call required before architecture is committed.

API: Confirm Required

TruckTrax

Fleet Tracking — CalPortland

Dispatch-level fleet tool. Shows truck positions, time-on-job, time-at-washout. No automatic alerts — dispatcher must manually check each truck. Used by CalPortland.

API: Confirm Required

Digital Fleet

Fleet Tracking — Martin Marietta

Fleet tracking system confirmed in use by Martin Marietta. API status unknown. Third connector required for MM customer acquisition.

API: Confirm Required

YARDMASTER Core

Intelligence Layer — V1 Build Target

Normalization layer, event detection engine, recommendation engine, dispatcher interface. Connects all upstream data sources. Outputs proactive alerts and ranked reallocation recommendations.

Build Target: V1

Driver Notifications

Field Communication — V1 Build Target

Push notifications to drivers for reroute instructions and status updates. Replaces radio for routine communications. Reduces dispatcher bottleneck. Critical gap in current stack.

Build Target: V1

Section 7

What We Don't Know — Risk Analysis

Open questions that could materially change the architecture, integration strategy, or unit economics.

Open Question	Risk If Unresolved	Impact	Next Action
Does Jonel's API expose real-time plant status and batch queue data?	Core intelligence layer has no feed. Architecture must be redesigned from scratch.	CRITICAL	Call Jonel partnerships team
Do Verifi, TruckTrax, and Digital Fleet have open APIs?	Fleet integration requires partnership agreements or is architecturally impossible.	CRITICAL	Three vendor calls before architecture commits
Will any vendor require revenue share or exclusivity for API access?	Unit economics and go-to-market strategy change materially.	HIGH	Surface in vendor calls. Model both scenarios.
What are API rate limits across these systems?	Real-time monitoring of 40+ trucks may hit ceiling. Latency degrades intelligence quality.	MEDIUM	Request technical docs from each vendor
How do operators handle cross-plant reallocation today?	Recommendation engine logic may not match actual dispatcher decision framework.	MEDIUM	Dispatcher interviews — 2-3 target operators
Are drivers willing to use push notifications vs. radio?	Driver communication layer adoption fails. Radio remains only channel.	MEDIUM	Field observation + driver interviews
Does CalPortland use Jonel for batching?	Jonel-first connector strategy may not reach CalPortland without additional integration.	LOW–MED	Confirm in CalPortland outreach call

Section 8

Operator Integration Matrix

Confirmed stack by target customer. Connectors required before first sale to each operator.

Operator	Batching Software	Fleet Tracking	Connectors Required	Sales Priority
SRM	Jonel ✓	Verifi (TBC API)	Jonel + Verifi	Priority 1
CalPortland	Jonel* (assumed)	TruckTrax (TBC API)	Jonel + TruckTrax	Priority 2
Martin Marietta	Jonel* (assumed)	Digital Fleet (TBC API)	Jonel + Digital Fleet	Priority 3

* Jonel usage by CalPortland and Martin Marietta is assumed — confirm before committing connector roadmap.