Comment The patron saint of lazy 'digital transformation' (Score 1) 71
Sounds like there is already an actual piece of simulation software in place; but the people feeding it scenarios need to manually assemble them from outage reports and maintenance notes; because apparently you can perform, even schedule, maintenance without generating a record of which asset you'll be working on. And so someone proposes that the obvious answer is to bandaid that with a summarizer, and their notorious penchant for accuracy?
Does that strike anyone else as slightly insane? We're already recording outages and maintenance events and those records refer to various pieces of infrastructure; but not in a format that can be programmatically extracted from the report to load into the analysis system; so rather than doing the boring thing and slapping serial numbers on transformers or adding a "things we turned off for maintenance and when" field to the maintenance report; we'll just continue doing that as a big free text blob and hope that an LLM will save us?
Seems sort of like deciding that postal addresses and mailing labels would be a huge pain; so let's find a chatbot that can, hopefully, follow a rambling account of how mail for the Johnson place is 3rd right past the old rail bridge; but if you see the silo you've gone too far.