Oracle AI World:Fusion 实施代理与 NetSuite SuiteExpress 把配置工作交给代理起草
Oracle AI World 2026 上,Fusion 侧推出含六阶段的 AI Success Navigator 实施代理,并公开机器可读的 Setup and Configuration Registry;NetSuite 发布 SuiteExpress,App Composer 可用 OpenAI Codex 建应用。分析指仅部分阶段写明人工审阅。
企业应用买家在 Oracle AI World 2026 上看到的一条主线是:让代理承担实施与配置起草,缩短「上线前漫长准备期」。
据 @Greyhound_R(约 2026-10-29)对大会发布的梳理,NetSuite 创始人 Evan Goldberg 在发布 SuiteExpress 时指出,漫长的 ERP 实施往往让客户在见到价值前承担过多前置工作。Oracle 的回应被概括为四块:面向 Fusion 实施的 Oracle AI Success Navigator(含 Discovery 到 Innovation 等六类代理);公开发布、机器可读的 Fusion Setup and Configuration Registry;面向 NetSuite 的 SuiteExpress;以及允许员工借助 OpenAI Codex 构建应用的 App Composer。
早期证据仍偏窄:Lexington Health 的 IT 负责人 Tom Tan 称,代理化交付方式已使部分设计与配置工作量下降约 80%,且实施仍在进行中。分析文章提醒:配置决定了后续代理应用遵守的审批、角色与权限边界;当代理起草配置时,签字人实际是在授权。公开材料描述在六阶段中的 Design 与 Configuration 有人工批准,但对其余阶段的身份主体、变更记录与回滚机制着墨不足。
对 CIO 与实施负责人,可执行的核对项包括:先确认 Registry 与各代理的书面可用状态;在首个代理跑起来前完成流程、数据与法务评审;把代理使用写入 SOW 并以可测结果挂钩付款;明确「谁起草、谁批准、谁共签权限变更」;并自建 Oracle 尚未完整描述的变更台账。原帖为第三方研究解读,具体能力边界以 Oracle 正式文档与合同附件为准。
Oracle AI World: Agents Draft ERP Implementation and SuiteExpress
Oracle AI World 2026 has wrapped. One of its most practical stories for enterprise application buyers: agents that do the implementation work.
“Long ERP implementations ask too much of customers before they can start realizing value,” said Evan Goldberg, founder of @Oracle @NetSuite, as NetSuite launched SuiteExpress at the event.
Oracle’s answer comes in four parts. Oracle AI Success Navigator brings six agents to Fusion implementations, from Discovery to Innovation. The Oracle Fusion Setup and Configuration Registry publishes how Fusion should be set up, as a public, machine-readable source. SuiteExpress does similar work for NetSuite. And App Composer lets employees build applications with OpenAI’s Codex.
The early evidence is narrow but specific. Tom Tan, executive director of IT, Business Services at Lexington Health, says Oracle’s agentic delivery approach has cut certain design and configuration efforts by 80 percent, with the implementation still under way.
So, is this good news for buyers?
Greyhound Research reads it as the right target, and as a shift that moves risk rather than removing it.
Configuration holds the approvals, roles, and limits that Fusion Claw and other agentic applications later obey. When agents draft the configuration, whoever signs it off is signing off authority.
Oracle’s releases describe a person approving the agents’ work at two of six stages, Design and Configuration. They do not yet describe the identity the agents act under, a record of their work, or a way to roll back applied configuration.
What should a CIO do before the next implementation contract?
1/ Start with the registry now, and get Oracle’s written status before any undated agent goes into a project plan.
2/ Settle process, data, and legal review before the first agent runs. Agents draft from the decisions you have already made.
3/ Write agent use into the statement of work, and tie payment to tested outcomes, so the time saved is visible and shared.
4/ Name who signs. The drafter never approves its own output, and the owner of the delegation of authority co-signs any change to who may approve what.
5/ Keep the record Oracle has not yet described, and give every generated application an owner before the first one is built.
The research note sets it out in full: a roles grid, nine contract clauses, four risks with their early warnings, a six-move Greyhound CXO Runbook, and six questions for Oracle.
When agents draft your setup, who signs for it?
Full research note in the first comment.
#AIWorld #OracleFusion #NetSuite #AgenticAI #ERP #CIO #GreyhoundStandpoint