Re:Kogito – Cloud-based business automation platform
by salawat on Saturday March 21, 2020 @12:06PM
(#22647468)
Likely a rules engine bundled with some form of business process management/modeling tool.
The rules engine is used to constrain/model the edges (transitions) of the overall graph of states within your overall business workflow finite state machine. This is generally implemented by throwing said rules engine at reams of data in the form of data validation, and inferring information from the various contexts that make up a system.
It's usually quite boring. Once you've seen a few, you've basically seen them all. The only differences boil down to the specifics of the industry, data model, and implementation of your basic frameworks.
In actual businesses there's basically maybe 4 actual software buckets that just about everything seems to end up degenerating to.
BPMA(Business Process Management/Automation, I.e. case/customer relation management, stuff related to doing business as a whole), OLTP (On-Line Transaction Processing; how you get data in), AADPETLR (Accounting, Auditing, Data Processing, Extraction, Transformation, Loading, and Reporting; what you do with all that juicy data you've collected).
All of those as I understand it may tend to end up getting combined into something called an ERP, (Enterprise Resource... Platform, I think?)
Having worked on most individual parts at one point, it's a bloody drag reimplementing the same thing over and over again in different wrappers this time. It is, however, the glue that makes basically any modern business work. The funny bit is how pretty much everyone does the same bloody thing, but bends over backwards to protect info with regards to who they are doing/sharing it with; even from their own employees.
The rules engine is used to constrain/model the edges (transitions) of the overall graph of states within your overall business workflow finite state machine. This is generally implemented by throwing said rules engine at reams of data in the form of data validation, and inferring information from the various contexts that make up a system.
It's usually quite boring. Once you've seen a few, you've basically seen them all. The only differences boil down to the specifics of the industry, data model, and implementation of your basic frameworks.
In actual businesses there's basically maybe 4 actual software buckets that just about everything seems to end up degenerating to.
BPMA(Business Process Management/Automation, I.e. case/customer relation management, stuff related to doing business as a whole), OLTP (On-Line Transaction Processing; how you get data in), AADPETLR (Accounting, Auditing, Data Processing, Extraction, Transformation, Loading, and Reporting; what you do with all that juicy data you've collected).
All of those as I understand it may tend to end up getting combined into something called an ERP, (Enterprise Resource... Platform, I think?)
Having worked on most individual parts at one point, it's a bloody drag reimplementing the same thing over and over again in different wrappers this time. It is, however, the glue that makes basically any modern business work. The funny bit is how pretty much everyone does the same bloody thing, but bends over backwards to protect info with regards to who they are doing/sharing it with; even from their own employees.