It's been a while since I used a Rete rule engine, back in my days as math nerd at a mortgage bank (ooof we survived the 08 meltdown by the skin of our teeth) we used an internal fork of Drools and paired it with a merkle tree datasctructure to store lending decisions.... I knew blockchain was gonna be a thing when the genesis block referenced the bailout... I kick myself daily cause should've bought more bitcoin.
I've used rete based CEP tool in the past for utility operations event management. We could tag the rule used to the event or event aggregate, but it was on a single node basis and a basic aggregate. If there was more coverage in understanding it would be a big help to operators. Based on say a set of outage events, can it further understand if it weather event, equipment failure, scheduled maintenance, etc. Linking it to possible operating procedures based on a broader understanding of the state would be very useful.
If you still work near this, I'd genuinely like to hear what the rule set looked like - outage classification is the case I'd build the next demo domain around.
It’s been a long time since I did the work and lost for details. The biggest issue we had was noise reduction when there was an upstream event. Could be a network issue and so meter reads were not expected to come in, so don’t send someone out to check the meter or do deeper analysis. Storm or other related outage, both diagnose and then quiet follow on events with a service ticket to acknowledge. Further we would build the history of events and if a meter or device wasn’t responding without the other broader events then create a service ticket to analyze or to send a technician out. This was all custom rules. Not sure how transferable it is as different utilities will have different ways of viewing and actioning. Interconnected are somewhat different. North America is also very different than say Germany or Brazil which I had a little bit of experience with. Wish I had more details.
This is a really interesting concept. Could be quite useful for agents. I worked on something similar, but more abstract; you managed to take it to the practical level.
I was expecting to see some Jev based influence on RETE/CEP rule handling ... the Typesafe.ai team have a lot more in the pipeline this use case is just getting started
I don't understand. If you're already building the rules, why have a clanker summarize and guess why the result happened when you can display the rules that passed/failed?
It's been a while since I used a Rete rule engine, back in my days as math nerd at a mortgage bank (ooof we survived the 08 meltdown by the skin of our teeth) we used an internal fork of Drools and paired it with a merkle tree datasctructure to store lending decisions.... I knew blockchain was gonna be a thing when the genesis block referenced the bailout... I kick myself daily cause should've bought more bitcoin.
I've used rete based CEP tool in the past for utility operations event management. We could tag the rule used to the event or event aggregate, but it was on a single node basis and a basic aggregate. If there was more coverage in understanding it would be a big help to operators. Based on say a set of outage events, can it further understand if it weather event, equipment failure, scheduled maintenance, etc. Linking it to possible operating procedures based on a broader understanding of the state would be very useful.
If you still work near this, I'd genuinely like to hear what the rule set looked like - outage classification is the case I'd build the next demo domain around.
It’s been a long time since I did the work and lost for details. The biggest issue we had was noise reduction when there was an upstream event. Could be a network issue and so meter reads were not expected to come in, so don’t send someone out to check the meter or do deeper analysis. Storm or other related outage, both diagnose and then quiet follow on events with a service ticket to acknowledge. Further we would build the history of events and if a meter or device wasn’t responding without the other broader events then create a service ticket to analyze or to send a technician out. This was all custom rules. Not sure how transferable it is as different utilities will have different ways of viewing and actioning. Interconnected are somewhat different. North America is also very different than say Germany or Brazil which I had a little bit of experience with. Wish I had more details.
For that there's Python: with 30 lines you can automate this task. If you want I can send you the script I use. DM me if interested.
This is a really interesting concept. Could be quite useful for agents. I worked on something similar, but more abstract; you managed to take it to the practical level.
I was expecting to see some Jev based influence on RETE/CEP rule handling ... the Typesafe.ai team have a lot more in the pipeline this use case is just getting started
I don't understand. If you're already building the rules, why have a clanker summarize and guess why the result happened when you can display the rules that passed/failed?
Fair question, and you can do exactly that( response_mode:"verdict_only") makes no LLM call