FleetView 2.0

Weekly Sync #9

November 5, 2026

Date

Thursday, November 5, 2026

Presenter

Frank Jiang

Topics

US requests · Release milestones · Feature architecture

TODAY'S AGENDA

Six topics today

Three recent US requests — answered one by one

Ronnie's usage metrics, DT2's combined TPO account, Josh's operation logging.

Latest roadmap — Batch 2 and Batch 3 now run in parallel

Both batches sit on the same timeline now, and both launch on December 30.

Batch 2 progress — log management ships this week

Log management to UAT on 11/3 and to production on 11/5; functional permissions still affected by MFA.

TPO device permissions — Shenzhen review done, now in design

Submitted to Lun to schedule the US review. This is the critical path for Batch 3.

Feature architecture & menu restructure — positioning, boundaries and menu set

Detailed design on the device management and overview modules runs over the next two weeks.

Opening Smart Diagnosis and One-Click Fix to all internal accounts

T1 included. Account scope, execution rights and frontline ramp-up to be settled.

PRODUCT ROADMAP · LATEST (UPDATED 2026-10-29)

Four batches across Alpha / Beta / Launch

Target: wrap up before Chinese New Year 2027
Batch 1 · full rollout by end of December

Batch 1

Released

RELEASED

07.31

FULL ROLLOUT

End of Dec

Batch 2

Fix · Accounts · Logs

ALPHA

10.20

BETA

11.15

LAUNCH

12.30

Batch 3

Assistant · TPO

ALPHA

11.30

BETA

12.15

LAUNCH

12.30

Batch 4

UI/UX · Wall

ALPHA

01.15

BETA

TBD

TODAY

11.03

OCT

NOV

DEC

JAN

FEB

B2 / B3 in parallel

B3 Alpha (11.30) falls between B2's Beta and Launch. Same engineering team, and both launch on 12.30.

Internal UAT ≠ external milestone

UAT is our internal acceptance environment (B2: 11.10). Alpha / Beta / Launch is the external cadence. They are not the same date.

B4 Beta still open

Alpha is set for 01.15, but Beta and Launch are unscheduled, and there is still an unestimated gap before Chinese New Year.

Batch 3 · ChatBI In design. Use cases get aligned with the requester this week, detailed design follows | detailed design starts this week

US REQUESTS · THE LAST THREE ASKS

The three US requests, answered

Raised in last week's sync and during design discussions. Each entry gives the conclusion, the owner and where it lands.

Usage metrics — measure how features are actually used Raised by Ronnie Owner: Jeans Huang

Smart Diagnosis already collects usage data: how many users are using it, and how users respond to the diagnosis results. That part can be shared directly.
Platform-wide instrumentation goes into the Batch 4 UI/UX revamp: page structures and interactions are being rebuilt there anyway, so instrumenting at that point gives complete, consistent coverage instead of bolt-on tracking on pages about to be replaced. The event design goes to your team for review before we build it.

ClickUp subtask #868mr803y →

Replied

Combined TPO account — a company that is both Financer and Installer signs in once Raised by DT2 Owner: Fan Gong

When one company holds both roles, it should not end up with two accounts and two sets of billing. The internal design review in Shenzhen is complete and the work has moved into design and development. Submitted to Lun to schedule the US review.

ClickUp #868kznp9w →

In dev

Operation logs — record every action anyone, including installers, takes on a device Raised by Josh Brooks Owner: Jeans Huang

A large share of field failures are misconfiguration by installers, not hardware faults. Troubleshooting needs to answer "who changed what, and when". Already within the log management scope, no extra scheduling needed. Log management goes to UAT on 11/3 and to production on 11/5.

ClickUp #868khgt1f (with UAT trial guide) →

Covered

BATCH 2 · DELIVERY PROGRESS (INTERNAL UAT 11-10)

Log management ships to production this week; functional permissions still blocked on MFA

Smart Diagnosis

Owner Jeans Huang · All 11 US-reported issues fixed and deployed
Next: open to all internal accounts (incl. T1 and US front line)

Released · pending acceptance

Log Management

Owner Jeans Huang · Includes the installer operation records Josh asked for

11.03 UAT → 11.05 Prod

Permissions 2.0 — Functional

Owner Jeans Huang · Affected by MFA, some issues still being resolved

Next week (est.)

Permissions 2.0 — Data

Owner Jeans Huang · Shares the same account system as functional permissions

In test

The current blocker · MFA

Part of the permission checks depend on the MFA chain and several issues are still being worked. Expect updates next week. This does not affect log management or Smart Diagnosis, but it does affect whether Batch 2 reaches UAT on time.

Live on UAT Audit Log (account actions) · Cloud Log (field annotations) · Setting Record (change history) | Test account and screen-by-screen notes in ClickUp #868khgt1f ↗

BATCH 3 CRITICAL PATH · TPO DEVICE PERMISSIONS

Shenzhen review complete, now in design & development, heading into US review

Batch 3's biggest delivery risk: blocked from both ends. the design still needs to change, and the US team still needs to agree. | Owner Fan Gong

✓

Shenzhen review

Complete

→

Design & dev

In progress

US team review

Submitted to Lun

Ships with Batch 3

Alpha 11.30

The core problems it solves

① Devices carry no "owner" field. The system cannot answer who is responsible

② Changing financiers, homeowner buyouts, company exits: all done device by device, by hand

③ One company ends up with two accounts and has to sign in twice

Risks over the next three weeks

The US review has no date yet, and its outcome may change the design

Design output must land by 11.30 Alpha, competing with B2 close-out for the same people

The account system shares its foundation with Batch 2 permissions, so the functional-side MFA issue could carry over

Tracking ClickUp #868kznp9w | Solution doc TPO Device Lifecycle Business Solution (Word) | Deck TPO Device Lifecycle Management (PPT) | Demo Permissions demo →

BATCH 4 PREP · FEATURE ARCHITECTURE & MENU RESTRUCTURE

Feature architecture: detailed design starts

Owner Frank Jiang · Three foundational documents delivered; the US front line has already given feedback on the personas and use cases.

Delivered · three documents

① Product positioning & functional boundaries
What FV2.0 does and does not do; six modules and visibility by role

② Core personas & use cases US feedback in
Who the core users are and in what scenarios; the US front line has commented

③ Menu structure + FV1.0 migration mapping
Top-level menu is finalised; sub-level menus shift slightly as detailed design proceeds. Shows where each legacy page lands and whether it is kept

Six modules

M1 Overview
First screen, role-based dashboards

M2 Sites & O&M
Sites, devices, monitoring, config

M3 Alarms
Alarm list and handling

M4 Firmware
Versions and upgrade management

M5 Logs
Operation logs and device logs

M6 Assets
The Financer workspace

Next 2 weeks · in parallel

Device management

Reuse existing FV1.0 pages first, then extend on top

Overview

Brand-new design; no FV1.0 pages to reuse

→

After that

Alarms & diagnostics

Fold the shipped Smart Diagnosis and One-Click Fix into the new architecture

Device management reuses FV1.0 pages and extends them; overview is built from scratch, so the two cannot share a schedule. Alarms & diagnostics re-homes the shipped Smart Diagnosis and One-Click Fix.

Online doc FV2.0 menu structure + FV1.0 page migration | Open the migration guide ↗

LAST MEETING · FOLLOW-UPS FROM SYNC #8 (OCTOBER 22)

Six action items, closed one by one

Item	Owner	Status	Notes
Create ORs to track alarm management and firmware upgrade	Jeans Huang	Created	Both are out of project tracking, but still need an owner; ORs carry them Alarm Management ↗ · Firmware Upgrade ↗
Phased product release plan (exit criteria + US sign-off owners)	Frank / White	Finalised	See the roadmap earlier; US still needs to name the signer per feature
Josh to run the US service team trial of Smart Diagnosis and report back	Josh Brooks	Pending	Agreed at the 10/22 sync: "within two weeks", i.e. ~11/5 (not a hard deadline); no feedback yet
Josh to review the product definition and persona documents	Josh Brooks	Feedback in	The US front line has commented; still being consolidated. Documents continue to evolve with detailed design.
TPO device permission design review	Fan Gong	SZ done	Shenzhen review complete and now in design & dev; US review awaiting Lun
Internal decision on whether metrics go on the roadmap	Frank / Jeans	Replied	Replied to Ronnie: Smart Diagnosis has stats, platform-wide metrics in Batch 4 ClickUp #868mr803y ↗

Smart Diagnosis trial feedback is still outstanding. Document feedback is in; the gap is the trial.

Five are closed: metrics answered, TPO Shenzhen review complete, release plan finalised, both ORs created, and document feedback received.

RELEASE PLAN · MILESTONES AND EXIT CRITERIA BY BATCH

Three things to lock down today

Ronnie asked on 10/22: "when do customers first get to use it?" That needs a table, not a sentence.

Batch	External milestones	Exit criteria	US sign-off owner
Batch 1	07.31 released Full rollout by end of Dec	Diagnostic accuracy accepted; T1 trial passed	To be named
Batch 2	Internal UAT 11.10 Beta 11.15 · Launch 12.30	Logs in production; MFA issues cleared on functional permissions; data permissions out of development	To be named
Batch 3	Alpha 11.30 Beta 12.15 · Launch 12.30	TPO device permissions pass US review and ship; ChatBI and Smart Assistant usable	To be named
Batch 4	Alpha 01.15 Beta / Launch TBD	UI/UX revamp and metrics design approved; detailed feature design complete	To be named

① Milestones per batch

Alpha → Beta → Launch, instead of a single "UAT release".

② Exit criteria

No release unless they are met, to avoid "still fixing after launch".

③ Who signs off per feature

This column is still blank. We need names from the US this week.

BATCH 1 + 2 · SMART DIAGNOSIS

Opening Smart Diagnosis and One-Click Fix to all internal accounts

Owner Jeans Huang · T1 is in scope. What needs settling is how far "all internal accounts" reaches, whether execution rights open with it, and how the frontline actually picks it up.

The proposal

Extend Smart Diagnosis and One-Click Fix to all internal accounts, T1 included.
T1 takes the most tickets. If they can diagnose and fix on their own, ticket volume comes down. Diagnosis is already live; One-Click Fix ships with Batch 2.

Why raise it now

If T1 cannot use them, both features stop at demos. Setting the account scope during detailed design is cheaper than changing permissions after launch.

Three things to settle

Scope of accounts

Whether "all internal accounts" covers contractors, temp accounts and LMT needs drawing once

Execution rights

Being able to diagnose is not the same as being able to fix. One-Click Fix changes device settings remotely; decide the two separately

Frontline ramp-up

How to read a diagnosis result, who to escalate to when a fix fails, and whether a short guide is needed

One-Click Fix ships with Batch 2, Beta on 11.15. Leaving execution rights until after launch drags in the role setup in Permissions 2.0.

NEXT STEPS & ACTION ITEMS

The next two weeks

Log management to production · Nov 5

Already on UAT since 11/3, production on 11/5. Includes Josh's installer operation records. Owner Jeans Huang.

Clear MFA issues on functional permissions · next week

The only blocker to Batch 2 UAT. Once cleared, data permissions close out alongside it.

TPO permissions · US review and design in parallel

Submitted to Lun to schedule the review; design must land by 11.30 Alpha. Neither side can wait for the other.

Feature architecture · M1 now, M2 next

M1 Overview detailed design starts this week, M2 Sites & O&M next week. Owner Frank Jiang.

Open Smart Diagnosis and One-Click Fix to all internal accounts

Account scope and execution rights to be settled at this week's sync. Diagnosis is live; One-Click Fix ships with Batch 2.

Three things we need from the US this week

① Complete feedback on the two foundational documents (product definition, personas): initial comments are in, but they need to be consolidated into decisions;
② A named sign-off owner per feature, per batch. This is the one column still blank in the release plan;
③ Smart Diagnosis trial feedback and blind-test cases: agreed two weeks out from 10/22, roughly 11/5.

FleetView 2.0

第九次周会

Weekly Sync · 2026 年 11 月 5 日

日期

2026年11月5日（周四）

主讲

Frank Jiang

议题

美方三项需求回应 · 发布节点定稿 · 功能架构进展

TODAY'S AGENDA · 今天议程

今天六个议题

美方近期提出的三项需求 — 逐条回应

Ronnie 的数据埋点、DT2 的综合 TPO 账号、Josh 的操作日志记录。

最新路线图与发布节点 — B2/B3 并行推进

Batch 2 与 Batch 3 已在同一条时间线上并行，12 月 30 日两批同步 Launch。

Batch 2 交付进展 — 日志管理本周上生产

日志管理 11/3 上 UAT、11/5 上生产；功能权限受 MFA 影响，部分问题处理中。

TPO 设备权限 — 深圳评审完成，进入设计开发

已提交 Lun 安排美国团队评审，这是 Batch 3 的关键路径。

功能架构与菜单重构 — 定位、边界、菜单结构已定

接下来两周并行推进设备管理与总览模块的详细设计。

智能诊断与一键修复开放给全部内部账号

T1 也包含在内。要定账号范围、执行权限和一线怎么用。

PRODUCT ROADMAP · 最新路线图（2026-10-29 更新）

产品路线图 — 四批次与 Alpha / Beta / Launch 节点

目标：2027 年春节前收官
Batch 1 · 全量铺开至 12 月底

Batch 1

已发布

RELEASED

07.31

全量铺开

12 月底

Batch 2

一键修复 · 账号 · 日志

ALPHA

10.20

BETA

11.15

LAUNCH

12.30

Batch 3

智能助手 · TPO

ALPHA

11.30

BETA

12.15

LAUNCH

12.30

Batch 4

UI/UX · 巡检 · 大屏

ALPHA

01.15

BETA

待定

TODAY

11.03

10 月

11 月

12 月

1 月

2 月

B2 / B3 并行

B3 的 Alpha 11.30 落在 B2 的 Beta 与 Launch 之间，两批共用同一批研发，12.30 同日 Launch。

内部 UAT 与对外节点分开

UAT 是内部验收环境（B2 为 11.10），Alpha / Beta / Launch 是对外节奏，两者不是同一个日期。

B4 的 Beta 仍未定

Alpha 定在 01.15，但 Beta 与 Launch 未排，与"春节前收官"之间还有估算缺口。

Batch 3 · ChatBI 目前在设计中，本周与需求方对齐使用场景，之后出详细设计 | 详细设计本周启动

US REQUESTS · 美方近期提出的三项需求

美方三条需求的答复

来自上周例会与设计沟通，逐条给出结论、责任人与落地位置。

数据埋点 — 用埋点数据评价功能实际使用情况 Ronnie 提出负责人 Jeans Huang

智能诊断已经在统计使用数据，包括用户量和对诊断结果的反馈，这部分可以直接给美方看。
全平台埋点纳入 Batch 4 的 UI/UX 改版。那一批本来就要重做页面结构和交互，埋点可以一次做完整，不用先在将要重做的页面上打补丁。方案定稿前拉美方一起评审。

ClickUp 子任务 #868mr803y →

已回复

综合 TPO 用户 — 既做 Financer 又做 Installer，要一个账号登录 DT2 提出负责人 Fan Gong

一家公司同时具备出资方与安装商身份时，不应产生两套账号与两份账单。深圳内部设计评审已完成，已进入设计开发阶段，并已提交 Lun 安排美国团队评审。

ClickUp #868kznp9w →

开发中

操作日志 — 记录所有人（含安装商）对设备做过的操作 Josh Brooks 提出负责人 Jeans Huang

大量故障根因是安装商误配置，不是设备故障。排查时要能查到谁在什么时候改了什么。已在日志管理范围内，不需要额外排期。日志管理 11/3 上 UAT、11/5 上生产。

ClickUp #868khgt1f（含 UAT 试用说明）→

已包含

BATCH 2 · 交付进展（内部 UAT 11-10）

日志管理本周上生产，功能权限还卡在 MFA

智能诊断

负责人 Jeans Huang · 11 项美方反馈问题已修复上线
下一步：开放给全部内部账号（含 T1 与美方一线）

已发布 · 待验收

日志管理

负责人 Jeans Huang · 含 Josh 要求的安装商操作记录

11.03 UAT → 11.05 生产

权限 2.0 — 功能权限

负责人 Jeans Huang · 受 MFA 影响，部分问题仍在处理

预计下周更新

权限 2.0 — 数据权限

负责人 Jeans Huang · 与功能权限共用同一套账号体系

测试中

当前阻塞 · MFA

功能权限的部分校验逻辑依赖 MFA 链路，目前有若干问题在处理中，预计下周更新。这不影响日志管理与智能诊断，但会影响 Batch 2 整体能否按时进 UAT。

UAT 可试用审计日志（账号操作） · 云通讯日志（协议字段注解） · 设置记录（设备变更历史） | 测试账号与逐屏说明见 ClickUp #868khgt1f ↗

BATCH 3 关键路径 · TPO 设备权限

深圳评审已完成，进入设计开发，正在走美国评审

Batch 3 里这块风险最高：设计还要改，美方还要认。｜负责人 Fan Gong

✓

深圳内部评审

已完成

→

设计开发

进行中

美国团队评审

已提交 Lun 安排

随 Batch 3 交付

Alpha 11.30

解决的核心问题

① 设备上没有"产权方"字段，谁是最终负责人，系统答不出来

② 换出资方 / 房主买断 / 公司退出，全靠人工逐台拆

③ 一家公司在系统里是两套账号，用户要登两次

接下来 3 周的风险点

美国评审会还没排期，评审意见可能改动设计

设计开发的产出要赶 11.30 Alpha，与 B2 收口撞在同一批人

账号体系与 Batch 2 的权限 2.0 共用底座，功能权限侧的 MFA 问题可能连带

需求跟踪 ClickUp #868kznp9w | 详细方案 TPO Device Lifecycle Business Solution（Word） | 汇报材料 TPO Device Lifecycle Management（PPT） | Demo 设备权限演示 →

BATCH 4 前置工作 · 功能架构与菜单重构

功能架构：进入模块详细设计

负责人 Frank Jiang · 三份基础文档已交付，美国一线已对用户与用例文档给出反馈意见。

已完成 · 三份文档

① 产品定位与功能边界
FV2.0 做什么、不做什么，六模块划分与角色可见性

② 典型用户与 Use Case 美方已反馈
核心用户是谁、在什么场景下用；美国一线已提出反馈意见

③ 功能菜单结构 + FV1.0 迁移映射
顶层菜单已基本定稿，子级菜单随详细设计微调。FV1.0 各页面落到哪个模块、是否保留，附 demo 演示说明

六模块划分

M1 总览
登录后第一屏，分角色看板

M2 设备与运维
站点/设备、监控、配置下发

M3 告警
告警列表与处置

M4 固件
版本与升级管理

M5 日志
操作日志与设备日志

M6 资产
Financer 的资产工作台

接下来 2 周 · 并行

设备管理模块

优先复用 FV1.0 现有页面，在复用基础上增补

总览模块

全新设计，FV1.0 没有可复用的页面

→

完成之后

告警与诊断模块

把已上线的智能诊断与一键修复纳入新架构

设备管理复用 FV1.0 页面再增补，总览全新设计，两边排期不能按同一个节奏。告警与诊断要把已上线的智能诊断、一键修复重新收进新架构。

在线文档 FV2.0 菜单结构 + FV1.0 页面迁移去向 | 打开迁移说明 ↗

上次会议 · 第八次周会（10月22日）遗留事项

六项 action items 逐条过一遍

事项	负责人	状态	说明
建 OR 跟踪告警管理与固件升级	Jeans Huang	已创建	两块已移出项目跟踪，但不等于不做，靠 OR 承接 Alarm Management ↗ · Firmware Upgrade ↗
出分批次产品发布计划（含 exit criteria 与美方 sign-off 负责人）	Frank / White	本次定稿	见上一页路线图，仍需美方确认每个功能的签核人
Josh 组织美国服务团队试用 Smart Diagnosis 并反馈	Josh Brooks	待反馈	10/22 会上约定「两周内」，折算约 11/5（非硬截止），目前未收到反馈
Josh 审阅产品定义与用户画像两份文档	Josh Brooks	已有反馈	美国一线已提出反馈意见，正在收敛；文档随详细设计继续补充
TPO 设备权限设计评审会	Fan Gong	深圳完成	深圳内部评审已完成并进入设计开发，美国评审待 Lun 安排
内部讨论埋点是否纳入 roadmap	Frank / Jeans	已回复	已回复 Ronnie：智能诊断现有统计，全平台埋点进 Batch 4 ClickUp #868mr803y ↗

Smart Diagnosis 试用反馈还没到。文档反馈有了初步意见，卡点在试用。

五条已收口：埋点已回复、TPO 深圳评审完成、发布计划本次定稿、两个 OR 已建、文档反馈已有初步意见。

RELEASE PLAN · 各批次发布节点与准出条件

这次要定下来的三件事

Ronnie 在 10/22 问的是"客户什么时候第一次能用上"。这个问题一句话答不了，需要一张表。

批次	对外节点	准出条件（exit criteria）	美方 sign-off 负责人
Batch 1	07.31 已发布全量铺开至 12 月底	诊断准确率验收、T1 试用通过	待美方指定
Batch 2	内部 UAT 11.10 Beta 11.15 · Launch 12.30	日志管理上生产；功能权限 MFA 问题清零；数据权限完成开发	待美方指定
Batch 3	Alpha 11.30 Beta 12.15 · Launch 12.30	TPO 设备权限美国评审通过并交付；ChatBI 与智能助手可用	待美方指定
Batch 4	Alpha 01.15 Beta / Launch 待定	UI/UX 改版与埋点方案评审通过；功能架构详细设计完成	待美方指定

① 每批的对外节点

按 Alpha → Beta → Launch 三段走，不再是单一"UAT 发布"。

② 准出条件

不满足就不发布，避免"发布之后还在修"。

③ 每个功能谁签核

这一列还空着，需要美方本周给人名。

BATCH 1 + 2 · SMART DIAGNOSIS

把智能诊断与一键修复开放给全部内部账号

负责人 Jeans Huang · T1 也在开放范围内。要定的是账号覆盖多大的范围、执行权限是否同步放开、一线怎么用起来。

提议

智能诊断与一键修复的可用范围扩到全部内部账号，T1 包含在内。
T1 接单最多，能自己查故障、自己修，工单才降得下来。现在诊断已经上线，一键修复随 Batch 2 交付。

为什么现在提

T1 用不上，这两个功能的价值就停在演示阶段。账号范围在详细设计阶段定，比上线后再改权限便宜。

要定的三件事

账号覆盖范围

"全部内部账号"包不包括外包、临时账号和 LMT，要一次划清楚

执行权限是否同步放开

能用诊断不等于能执行修复。一键修复是远程改设备，两个权限要分开定

一线怎么用起来

诊断结论怎么读、修复失败往上找谁，要不要配操作指引

一键修复随 Batch 2 交付，Beta 在 11.15。执行权限如果留到上线后再开，会牵动权限 2.0 的角色配置。

NEXT STEPS & ACTION ITEMS · 下一步计划

接下来两周要做的事

日志管理上生产 · 11 月 5 日

11/3 已上 UAT，11/5 上生产。含 Josh 要求的安装商操作记录。负责人 Jeans Huang。

功能权限 MFA 问题清零 · 下周

这是 Batch 2 进 UAT 的阻塞项，解决后数据权限一起收口。

TPO 设备权限 · 美国评审 + 设计开发并行

已提交 Lun 安排评审会；设计要求赶 11.30 Alpha，两头不能等。

功能架构 · M1 本周 / M2 下周

M1 总览详细设计本周启动，M2 设备与运维下周启动。负责人 Frank Jiang。

智能诊断与一键修复开放给全部内部账号

本周会上定账号范围和执行权限。诊断已经上线，一键修复随 Batch 2 交付。

需要美方这周给的三样东西

① 两份基础文档（产品定义、用户画像）的完整反馈：已有初步意见，需要收敛成结论；
② 每个批次每个功能的 sign-off 负责人姓名：发布计划表里还空着这一列；
③ Smart Diagnosis 试用反馈与盲测案例：10/22 约定两周内，约 11/5 到期。