How Trane gets building insights 60x faster with Amazon Bedrock AgentCore
https://aws.amazon.com/blogs/machine-learning/how-trane-gets-building-insights-60x-faster-with-amazon-bedrock-agentcore/📌 HVAC 診斷從 20 分鐘變 20 秒,Trane 怎麼用 AgentCore 做到
TL;DR:Trane Technologies 用 Amazon Bedrock AgentCore 打造對話式代理,把多螢幕診斷流程壓縮成一句自然語言查詢。
管理全球數百萬臺連網 HVAC 設備是什麼概念?對 Trane 的技術人員來說,過去要回答一個維運問題,可能得在多個儀表板間切換、在層層選單裡鑽 20 分鐘。這種摩擦不只是體驗差,而是實際拖慢維修決策、造成企業層級的損失。
🤔 同一份資料,不同角色需要完全不同的視角
Trane Technologies 年營收超過 210 億美元,業務遍及 100 多個國家,旗下 Trane Cloud 彙整來自數百萬臺 HVAC 系統的即時效能資料,理論上足以支撐預測性維護與能源最佳化。但問題在於:現場技術人員需要冷媒壓力、故障碼這類診斷級精度;客戶經理需要正常運行時間、成本節省機會;建築業主則需要效能分數、永續指標這種高階摘要。既有的儀表板工具卻是「一套介面打天下」,逼每個角色都得在不屬於自己工作流程的畫面裡摸索,連基礎的跨設備比較都得靠人工手動串聯多個畫面。
🧩 用 Strands + AgentCore 搭出的多代理架構
Trane 工程團隊只花 3 到 4 週,就在 Amazon Bedrock AgentCore 與 Strands framework 上建出對話式代理,並用 AWS CDK 做基礎設施即程式碼部署。團隊選擇 Strands 負責 agent 行為的開發者 SDK 與編排邏輯,AgentCore 則接管底層的 managed runtime、記憶、工具閘道與生產環境基礎設施。為避免單體式設計的侷限,架構採用多代理設計:每個專門助理由自己的 system prompt 治理,只專注單一能力領域,且可透過 AgentCore Gateway 與 MCP 這類開放標準,接入更多 agent 或工具(例如工單管理系統、企業 CRM)。
打造這套系統時遇到四個架構挑戰:整合(要同時串接即時遙測資料、大型知識庫的智慧搜尋,還要能連到 CRM 等外部系統)、分離(agent 邏輯必須和後端工具執行解耦,才能獨立部署、劃清權責邊界)、上下文(要在診斷過程中維持對話狀態,卻不想自建複雜的向量資料庫基礎設施)、可觀測性(agent 在多步驟推理鏈中協調多個工具,一旦出錯很難定位是 API 憑證缺失、工具回應格式錯誤,還是模型幻覺)。
團隊在導入 AgentCore 前,也評估過用 Amazon ECS 或 AWS Lambda 自建,但那意味著要在運算層之上自行打造 session 隔離、自動擴縮、按 session 計費等邏輯。最終選擇 AgentCore 的關鍵有四點:managed runtime 免去基礎設施維運(不需要自建叢集,session 間也沒有閒置容量要付費);內建 session memory 省去自建與維護外部向量資料庫的成本;AgentCore Gateway 提供原生工具編排,讓既有內部 API 不必逐一手寫整合就能變成 agent 可用的工具;框架無關的設計則讓團隊能用 Strands SDK,不被綁死在某個專有的編排層上。
📊 60 倍的 time-to-insight 改善
根據 Trane 內部與技術人員進行數週的實測基準,這套解法把原本 20 分鐘的多螢幕診斷流程,壓縮成 20 秒內完成的自然語言對話,相當於 time-to-insight 提升 60 倍。曾經需要人工在多個畫面間手動串聯的跨設備比較與診斷工作流程,如今透過單一自然語言查詢即可完成。
🎯 實務啟示
這個案例對正在評估企業級 agent 架構的工程團隊很有參考價值:與其自己在 ECS/Lambda 上手刻 session 隔離、記憶體管理和工具整合,用託管的 agent runtime 能省下大量重工。多代理設計(每個 agent 綁定單一領域 system prompt)也是應對「不同角色需要不同視角」這類需求分歧的實用模式,而不是硬把所有邏輯塞進一個巨大的 prompt。
🔗 來源
- 標題:How Trane gets building insights 60x faster with Amazon Bedrock AgentCore
- 作者/機構:Senthil Chinnaiyan(AWS ML Blog)
- 連結:https://aws.amazon.com/blogs/machine-learning/how-trane-gets-building-insights-60x-faster-with-amazon-bedrock-agentcore/
#AWS #BedrockAgentCore #AIAgents #Strands #HVAC #IoT #GenAI #EnterpriseAI #MultiAgent #TraneTechnologies
原始資料 AWS ML · 收集於 2026-09-22
摘要原文
Trane Technologies manages millions of connected heating, ventilation, and air conditioning (HVAC) assets worldwide, but getting a single operational answer could mean cross-referencing multiple dashboards and drilling through menus for 20 minutes or more. For organizations operating at this scale, that kind of friction slows operations, defers corrective action, and creates material business impact across the enterprise. In 3–4 weeks, Trane’s engineering team built an AI-powered agentic solution on Amazon Bedrock AgentCore that reduced a 20-minute multi-screen diagnostic workflow to a 20-second natural language interaction. This is based on Trane’s internal benchmarking with technicians over several weeks. This represents a 60x improvement in time-to-insight, helping shift operations from reactive response to more proactive, data-driven optimization. In this post, we describe the architectural approach and key design decisions behind the solution: Trane Technologies is a global climate innovator with over $21 billion in annual revenue and operations in more than 100 countries. Through its strategic brand Trane, the company manages millions of connected HVAC assets, spanning data centers, hospitals, manufacturing facilities, and commercial real estate portfolios. At the heart of this vast landscape is Trane Cloud , a digital hub that aggregates real-time performance data from millions of HVAC systems. Trane Cloud transforms raw equipment telemetry into actionable intelligence for predictive maintenance, energy optimization, and operational excellence. While dashboard-based building management systems provide a foundation for monitoring and control, extracting cross-system insights can still require users to navigate multiple screens, layered menus, and disconnected dashboards. By combining natural language processing with deep integration into Trane Cloud, users can access that operational context through a single conversational interface. The result is faster answers to complex building management questions and a more proactive, informed approach to facility operations. Building operators, field technicians, and service managers have abundant data at their fingertips. Equipment telemetry, performance analytics, fault alerts, energy consumption patterns, and optimization opportunities flood in from disparate systems, yet extracting actionable insights remains difficult. The fundamental problem is that different stakeholders need radically different views of the same data. Field technicians require diagnostic precision. They need refrigerant pressures, fault codes, and system-level troubleshooting workflows. Account managers need strategic intelligence. They need uptime metrics, cost savings opportunities, and portfolio performance trends. Building owners demand executive clarity. They need efficiency scores, sustainability metrics, and simplified operational summaries. Existing tools present a single interface across all roles, requiring each user to navigate features outside their workflow. Existing building management applications rely on screen-by-screen navigation that makes cross-equipment comparison more challenging and demands that users memorize menu hierarchies and technical terminology. Even basic portfolio-level questions can require time-intensive manual workflows across multiple screens. Together, Trane’s agentic AI solution and Trane Cloud deliver four capabilities: These capabilities create a more scalable way to access building intelligence across roles, workflows, and operational environments. The challenge of scaling intelligent building operations lies in turning the massive volume of data generated by millions of connected assets into actionable insight. Although Trane Cloud ingests real-time telemetry at scale, answering operational questions has traditionally required users to navigate disconnected dashboards and manually connect information across systems. To solve this, the team built a conversational agent on Amazon Bedrock AgentCore and the Strands framework , deployed through AWS Cloud Development Kit (AWS CDK) infrastructure as code. The team chose Strands for the agent framework layer because it provides the developer SDK and orchestration logic for building agent behavior, while AgentCore handles the managed runtime, memory, tool gateway, and production infrastructure underneath. To avoid the limitations of a monolithic design, the solution uses a multi-agent architecture where each specialized assistant is governed by its own system prompt, keeping it tightly focused on a single capability domain: This architecture is designed for extensibility. Teams can connect additional agents or tools, such as work order management systems and enterprise customer relationship management (CRM) systems, through AgentCore Gateway, a capability of Amazon Bedrock AgentCore, and open standards like the Model Context Protocol (MCP). Figure 1: High-level architecture of Trane’s conversational agent on Amazon Bedrock AgentCore Supporting these distinct user needs at enterprise scale requires an architecture that can evolve independently across capabilities. A monolithic agent would force every change (new tools, updated prompts, additional data sources) through a single deployment pipeline, creating bottlenecks as the system grows. Reducing a 20-minute manual diagnosis to a 20-second conversation surfaced four architectural challenges. The first challenge was integration. The solution had to combine real-time telemetry with intelligent search across an extensive knowledge base while supporting connections to external systems like CRMs. The second was separation. Agent logic had to be untangled from backend tool execution so the two could deploy independently, with clear ownership boundaries. Third was context. The system needed to maintain conversational state across troubleshooting sessions without standing up complex custom vector database infrastructure. Fourth was observability. When an agent orchestrates multiple tools across a multi-step reasoning chain, failures become difficult to localize. A wrong answer could stem from a missing API credential, a malformed tool response, or a model hallucination. Without end-to-end tracing, the team had no way to distinguish between them at production scale. Amazon Bedrock AgentCore is an agentic platform to build, connect, and optimize agents at scale, with any framework or model. The Trane team used four AgentCore capabilities to address the preceding challenges. Before selecting AgentCore, the team evaluated hosting the agent on Amazon Elastic Container Service (Amazon ECS) and AWS Lambda. That approach would have required building session isolation, auto scaling logic, and per-session billing on top of the compute layer. Four differentiators drove the decision. First, the managed agent runtime alleviates infrastructure operations. There are no clusters to provision or scale, and no idle capacity to pay for between user sessions. Second, built-in session memory removes the need to stand up and maintain external vector databases or build custom context-window management code. Third, native tool orchestration through AgentCore Gateway turns existing internal APIs into agent-compatible tools without writing custom integration logic for each one. Fourth, AgentCore’s framework-agnostic design meant the team could use the Strands SDK without being locked into a proprietary orchestration layer, preserving flexibility as requirements change. The real-time data flow works as follows: Using Amazon Bedrock AgentCore and the Strands framework, the team achieved the 60x time-to-insight improvement described earlier. Cross-equipment comparisons and diagnostic workflows that once required navigating multiple screens now complete through a single natural language query in seconds. This helps teams move faster, reduce analysis steps, and take a more proactive approach to facility operations.
由 claude-code/sonnet 自動生成