FLEETVIEW 2.0

Weekly Sync #4

Project Kickoff · Open Items Resolution · Next Steps

July 2, 2026·Bi-Weekly Sync·45 min

ACTION ITEMS FROM JUN 18

All Completed ✅

#	Action Item	Owner	Status
1	Draft Acceptance Criteria template	Auston	✅ Done
2	Update RTM, ClickUp, Overview, Roadmap (Log Mgmt → Batch 2)	Jeans	✅ Done
3	Share AC template with stakeholders	Auston	✅ Done
4	Complete AC for all 34 Batch 1 requirements (Layer 1 + Layer 2)	Jeans	✅ Done

Additionally resolved via email & ClickUp: response time approach, PDF export deferral, low-confidence handling, single source of truth (ClickUp)

DEVELOPMENT PROGRESS — SMART DIAGNOSTICS

• Smart Diagnostic Agent — tuning and optimization in progress
• Smart Diagnostics Frontend & Backend — integration testing underway

PROJECT KICKOFF

Roadmap Confirmed

Email sent Jun 27 — "No objections by June 30 = formally approved"

Batch 1

34 Requirements · Release 07.20

AI Diagnostic Assistant (Read Path)

Batch 2

71 Requirements · Release 09.07

Permissions + Log Management + Alarms + Write Path

Batch 3

51 Requirements · Release 10.27

Data Reports + Dashboards + Lists + Inspection

Batch 4

18 Requirements · Release 12.07

Device Lifecycle + Smart Inspection 2.0

Any objections received? If not, project is formally kicked off today.

🔗 Open Live Roadmap

OPEN ITEM #1

Response Time

Progressive output approach — needs final alignment with Ronnie

JOSH'S POSITION (Jun 27) ✅

"Partial results is a good starting point. The 10s window should show SN, fault codes, and parameter readings. Perceived speed will be high if we prioritize raw data output and follow up with AI inference."

OUR IMPLEMENTATION

≤ 10s: SN + device info + fault codes + key parameters (data layer)
AI conclusion follows progressively as inference completes
Simple cases: full result ≤ 10s · Complex cases: P95 ≤ 60s

⚠️ Ronnie (Jun 25): "10 seconds was the go-live gate and 3 seconds to be the optimization target." → Confirm alignment with progressive approach?

OPEN ITEM #2

Low-Confidence Handling

Simplified to static escalation for Batch 1

JOSH'S FEEDBACK (Jun 27)

"The only way for multi-turn to work is for the system to be smart enough to know what it's lacking. I think that exceeds Batch 1 criteria. Escalation with proper analysis and solution feedback linked to the same system can be added to the solution database for faster diagnosis on repeated occurrences."

AGREED APPROACH (Batch 1)

• Low confidence → Static escalation to T2/T3 with diagnostic data
• Zero confident-wrong principle maintained
• Escalation records + feedback → solution database
• Multi-turn context-gathering → Batch 2+ enhancement

Resolved Confirm no objections.

OPEN ITEM #3

PDF Export & Link Sharing

Deferred to later iteration

JOSH'S CONFIRMATION (Jun 27)

"As long as there is a record that can be referenced, that's what matters for Batch 1."

BATCH 1 DELIVERS

✅ Structured report viewable online
✅ Copy to clipboard (Markdown format)
✅ Diagnosis time + diagnostician recorded
❌ PDF export → later iteration
❌ Shareable link → later iteration

Resolved No further action needed.

OPEN ITEM #4

Starter Fault List

Chris's candidate list — pending final lock

WORKING CANDIDATE (Chris, Jun 22) — 15-20 CODES

0x2004-0x2017 aGate-aPower Comm · 0x2001 Cloud Comm · 0x100E CAN · 0x1032-0x1036 CT Unclamped · 0x6#0B/0C Battery Voltage · 0x6#0D/0F High Temp · 0x4#0E Inverter Precharge · 0x4#26 Neutral Open · 0x4#2C SW Version · 0x3001-0x300D Mains V/F · 0x1005 EPO · 0x3031 Wrong Locale

STATUS

✅ Cross-referenced against our diagnostic rule base — all codes covered
✅ "Device offline" confirmed included
⏳ Once locked: ≥ 90% accuracy becomes hard go-live commit

Action needed Darcy to validate against service frequency → lock the list 🔗 Open in ClickUp

OPEN ITEM #5

Solution Revision Notification

US team to be included in notification workflow

JOSH'S REQUEST (Jun 27)

"Should include US team at some level. Will improve the overall revision pipeline."

UPDATED FLOW

When solution effectiveness drops below threshold:

→ Notify LMT/T3 (original)
→ Also notify US service team (Josh/Chris/Darcy) (new)
→ Both sides collaborate on improvements

Agreed Will implement. Confirm no objections.

MOVING FORWARD

Next Steps

→

Lock starter fault list

Darcy validates service frequency, then 90% bar commits

🔗 Open in ClickUp

→

Development sprint planning

Against agreed acceptance criteria, targeting 7/20 UAT release

→

UAT environment preparation

Deploy test environment, prepare for acceptance testing

→

Bi-weekly cadence continues

Sprint Review + Demo format

KEY LINKS

Product Roadmap Batch 1 AC (All 34) AC Framework ClickUp Board