DELIVERY MODELS
Robolitics™ is available as a Cloudera Stack, based on Hadoop for high volume, real-time and mission-critical solution. Alternatively, for smaller transaction volumes as Robolitics™ Classic runs on SQL or MySQL. Robolitics™ is deployable to a shared cloud, private cloud or on-premises infrastructure.
DETERMINE THE STACK THAT'S RIGH FOR YOU
ROBOLITICS™ CLASSIC
Extended relational architecture. For small/medium size organizations
-
Up to 20k Transactions per month
-
Up to 10 TB Data volume
-
Focus: Descriptive/Diagnosis analytics
-
Self-service (ad-hoc reporting)
-
High data model extensibility
-
High data quality and consistency
-
Extensive security
-
Reliability and fault-tolerance
-
Reduced cost
ROBOLITICS™ ENTERPRISE
Big Data Architecture. For medium/large size organizations
-
More than 20k Transactions per month
-
More than 10 TB Data volume
-
Focus: Predictive AI/Machine Learning analytics
-
Self-service (ad-hoc reporting)
-
Unstructured data processing
-
High data model extensibility
-
Extensive security
-
Reliability and fault-tolerance
-
Low latency (near-real time)
CORE ELEMENTS
ALGOS (ROBOTS)
Real time, intraday and end of day monitoring algorithms, called Robots.
RDK
Robolitics Development Kit (RDK) for creation of new Robots.
GUI DESIGNER
Interactive GUI designed to provide an intuitive interface for interacting with the data.
DATA LOAD
A Subscribe Module for external access to data through a Secure API
ROBOLITICS FEATURES
DATA INTEGRATION
Robolitics™ is not a golden source of data but integrates with real-time systems such as the Core Banking systems as well as pricing and data engines.
REGULATORY ALGORITHMS
Components are built in Java (as services) and running in an Apache Tomcat container. Interfacing use an Open API protocol between layers and third-party client platforms.
REPORTS
Components are built in Java (as services) and Javascript + React (as UI) to deliver the functionality as Open API Services and Web Application.
WORKFLOW
The workflow engine is a component responsible for executing scheduled tasks. Case management is a proprietary component that can be disabled and instead case data can be integrated into the customer Case Management platform, such as JIRA or Remedy.
VISUALISATION
Components are built in Java (as services) and Javascript + React (as UI) to deliver the end user Web Application, including customisation pages, spider graphs, case escalation and a number of executive dashboards.
DATA SHARING
Robolitics™ can be used as a data source for business reporting as well as a secure source of data via request and publish. This meets the requirement for PSD2 and front office client performance reporting.
DATA FLOWS
INCOMING DATA
Transaction Data Ingestion and Enrichment
Transaction data ingestion is a straight forward process in Robolitics™ Classic.
The Robolitics™ data model has been extended to include data specifically related to standard Spot products as well as Options and Exotic Products. The data model also includes customer structure and formatting. During the initial data mapping process, we also consider the data life cycle (either real-time, periodic (daily) incremental archives or full data sets).
The service will process customer transactions and apply the necessary mappings to persist the data into the Robolitics™ Data Model. The output of the Service is a log file stating the processed rows, errors or exceptions found.
Reference Data Load Service
The service is designed in two ways:
- To provide access to Reference Data Open API to allow customer to directly interact with Robolitics™ Reference Data Model
- To provide a manual bulk load function to perform single load of Reference Data, overriding any existing data
OUTGOING DATA
Report Data Service
The service provides access to generated reports in order to be consumed by third party systems such as BI products or customer applications. Robolitics™ exposes reports as Open API Services, the same that are consumed by our UI Web Application.
Alert Data Service
The service provides access to the foundation of alerts detected by the Robolitics™ algorithms configured to run against the ingested transaction data (INCOMING). The Alert Open API Services are consumed by our UI Web Application, but they can be accessed from customer applications as well.
Case Management Service
Robolitics™ generates cases according to alerts detected against thresholds configured by the customer. The cases can be consumed by a third-party customer application using the Open API Service, or directly by our UI Web Application.
INTEGRATIONS OUT-OF-THE-BOX
AML Module
Integration with sanctions list data sources, either in real time or by periodic loading data into the Robolitics™ repository. KYC and client list can be loaded through the optional AML Data Load Service.
Client Data Store
Inetgration with CRM solutions can be done standalone for on-boarding and integrating the KYC system in order to simplify the re-KYCing process. This integration is based on the Reference Data Open API.
Trade Surveillance and Payments
Integration with Swift message gateway or FIC payment instructions, typically based on message bus of transaction messages and loads in real-time. This integration might be done in two ways: by the customer invoking Robolitics Open API Services to update payment orders or by developing specific components for the customer.
Workflow & Case Management
Integration with other workflow solutions such as JIRA or Pega; however, this requires backward integration of results into the data store.
