Original Summary

I’m building FaultBench, an early-stage tool for HVAC service techs. The idea came from a familiar field problem: when a unit is down, the answer may be somewhere in an IOM, wiring diagram, or service bulletin, but finding the right page can be slow. The current alpha runs locally on Windows/Linux. You add documents you already have, ask in plain language, and it returns an answer with the source page so you can check it. Mac support and several workflow features are still in progress. The demo uses a sample manual, not manufacturer documentation: https://faultbench.com/#demo I’m trying to learn whether this solves a real annoyance or whether normal PDF search is already good enough. For anyone who works in HVAC service or builds tools for field teams: what would you need to see before trusting a cited answer? Where would this fit (or fail) in an actual service call? What’s the first thing you’d change? I’m the builder, so I have an obvious bias; criticism about the problem, concept, or demo is especially useful.   submitted by   /u/Interesting-Total828 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/26 03:25:10