The PATH Architecture

PATH employs four major engines to deliver a Tool Set and application that enables rapid of a myriad of solutions ranging from simple protocol translation to full Business Process Management.  The engines are:

Universal Translator

The communications protocol and format manipulation engine.

TCB (Transaction Core Binder)

The Trade oriented data set that acts as both a store and forward queuing mechanism and a data warehouse.

Decision / Process Milestone Management

The engine that manages the sequencing and systemic placement of Decision Automation tasks.

Decision Automation

This engine manages ‘if then else’ processing of data. That is, it takes the content of the data packets transform the data where need and then determines how the data is to be routed.

PATH is built to very strict standards ensuring consistency and continuity.  It is written in C and C++ with the capability to cross compile on various operating systems.

Application Modules

Processing and User

Process Manager/Monitor

  • Receive New or associated message
  • Secure Orders as TCB or Bind Executions/fills to the Order TCB
  • Acknowledge Message receipt
  • Send Messages to Target applications
  • Process Send response
  • Best Execution Decision Processing
  • Possible Market Abuse Decision Processing
  • Reference table access

Work Baskets

  • Process Exceptions
  • Real Time Reporting of Workflow applications such as confirmation matching, CLS etc.
  • Real Time Reports of Routing Status at Route, Trade and Message Level
  • Query at Trade and message level of On Route and archived Trades and messages
  • Crystal Report
  • XML Publisher

Service Applications

Toolkit

  • Communications Specification
  • STP TCB Definition
  • Work Flow Moddeling

          Change Control

  • Automated Promotion of Workflow Models to Quality Assurance
  • Automated Demotion of Workflow Models failing Quality Assurance Tests
  • Automated Promotion Tested and Signed Off Workflow Models to Production
  • Automated Roll Back of Workflow Models failing in Production
  • Provision for Controlled emergency patching

      User Administration

  • Definition of View at Route, Trade, Message and Component Level
  • Definition of Access Rights at Route, Trade, Message and Component Level
  • Follow me User preferences such as colour and font
  • Route failure early warning recipient detail
  • Template management

      System Administration

  • Routing Task logon management
  • Certificate management ( e.g. for SSL)
  • Communications sequencing