Block Chain Real-Time Analytics & Alerts using TriggerWare. Deborah Taylor, CEO Dr. Swamy Narayanaswamy, CTO Contact:

Transcription

1 Block Chain Real-Time Analytics & Alerts using TriggerWare Deborah Taylor, CEO Dr. Swamy Narayanaswamy, CTO Contact:

2 Origins in Federal R&D projects, SBIR and BAA competitions; Logic-based rules engine for realtime data analytics/automation; Raised over $ 5 Million in seed funds from DARPA, NSF, NIST; HISTORY TECHNOLOGY Processes huge variety of data sources, internal and external; Spun off from Cs3 Inc. in 2017 to focus on TriggerWare technology. Answers to questions and alerts using current data from anywhere. Cohesive unit with world class Computer Scientists / engineers; We solve hard problems. Innovation is in our DNA; 15+ year track record of developing IP and delivering production quality S/W solutions. TEAM Real-time Analytics and Automation for Data-Driven Companies MARKETS Pharma pharmacovigilance, signal detection, literature monitoring; Retail 360 o omni channel marketing to enhance UX and sales; Supply Chain Management smart sourcing with real-time market data; Smart Citites Command & Control Center to correlate real-time data. Deploying TriggerWare in various markets through Partners 1 US patent awarded, 1 pending

3 Core Technology Data Source Abstraction: Ability to represent many, many disparate data sources over a network as relations (i.e., tables); Use a logical query language to correlate data from different data sources very conveniently; Virtual Database Platform Constraints & Triggers: Full range of constraints in logic automatic violation detection; repairable via software; Full range of triggers expressed in logic with automatic activation as relevant. Complex Event Processing: Reasoning about event sequences and intervals; Events triggered automatically by database conditions expressed in logic; Dynamic definition of new complex events. 3

4 TriggerWare at a Glance Connectors to all kinds of data sources to extract First Order Logic (FOL) relations (i.e., TABLES); Queries in FOL over disparate, possibly non-persistent data sources; Events, time-based complex event correlation using FOL patterns; FOL rules that support data driven computation and compliance. Good question: what can a logic-based Technology Platform do with the requirements for Block Chain?

5 Define New Events Event Definer API ERL Compiler Data & Event Sources from Anywhere Data Source A Data Connector A Event Source B Event Connector B Event Source C Event Connector C Data Source D Data Connector D Event Source / Connector API ERL Event and Relation Logic Virtual Database and Event Monitor Orchestration API Apps issue queries and receive results Apps subscribe to events; Apps are notified about subscribed events; Apps must listen for push notifications; Apps are Written Using REST APIs 5

6 TriggerWare Improving Situation Awareness from Block Chain; Analytics combining data from the Block Chain & other sources; Event analytics and correlation, detection of anomalies in real-time Deliver Custom, d.i.y. Reports, Dashboards, Smart Alerts; The Block Chain To Decision end points in the Supply Chain

7 What we Did with C4SCS Reference Model Data was in multiple worksheets of a spreadsheet; Created a TriggerWare Connectors to those worksheets Each worksheet appears as a Table with columns inside TriggerWare Can replay the event sequence across all worksheets to simulate real-world conditions; Can analyze the past events to understand trends in the data; Can perform event analytics and detect anomalies in real-time

8 What the Demonstration Will Show The Happy Path as Bob Celeste likes to call it; TriggerWare s tabular view of the Block Chain Queries over the Block Chain tables View results in a BI tool like Tableau during the demo we are a server side platform connecting results to standard BI tools that customers are already familiar with Real-time event analytics to detect anomalous patterns in the event stream.

9 Blockchain from a Logician s Perspective - I 1. Derived properties: is the model that each node can have different derived properties and derivation methods / values? 2. Logic rules are a great formalism to articulate the governing principles of the block chain between partners. Beats reading code to understand what the parties have agreed to as the rules at a specification level. 3. Using logic-based Distributed event reasoning requires a coherent model of time; 4. Events can appear out of sequence due to varying latencies and vagaries of partners even with consensus on time management!

10 Blockchain from a Logician s Perspective - II 5. Fixing problems (e.g., human error) in Block Chain through corrective new blocks this is not easy in general; 6. In the worst case, this can become non-monotonic reasoning computationally complex and not guaranteed to converge; 7. Situation Awareness is hard in any circumstance. Presence of incomplete data (by design) makes it a challenge; 8. Do the benefits of transparency outweigh the potential harm of over-sharing data that leads to loss of competitive edge?