Nassau, New York and Toronto

Services

The operating layer

Shared records, connections and controls across the systems you already run, so a case moves between them without an employee carrying it.

The principle

Your systems keep their records. The layer carries the work between them.

Accounting platforms, client systems and specialist applications retain their established responsibilities. We use supported product capabilities where they meet the requirement and build the business-specific work between them.

Recreating a ledger or a specialist calculation engine means taking over its maintenance, its testing and its control responsibilities. That requires a stronger justification than the ability to produce a new interface for the same work.

Responsibilities

What stays in your systems, and what the layer holds

The division is settled before anything is built, so every record has one owner.

Stays in your systems

  • Books of record and their calculations
  • Fund, investor and entity master data
  • Approved client reporting
  • Product licences, configuration and support

Held in the operating layer

  • Identifiers linking a case across systems
  • The status and history of every case
  • The evidence behind each step
  • Permissions, approvals and open decisions
The glass facades of two towers, seen from below

Connections

Connected through supported interfaces

We connect to each system through its supported interfaces and agree the integration route with the vendor where one is needed. Where a product has no suitable interface, the scope sets out how the work reaches it and who is responsible for that route.

An existing product should not set the limits of the whole operation because its current features stop at a particular step.

Design

Built to outlast any one model

The layer holds what must endure while models and execution methods change.

  1. 01

    Progress that survives

    A case keeps its status and evidence through a change of model or an interrupted session.

  2. 02

    Permissions outside the model

    What the system may read, change or send is enforced by the layer, independently of any model.

  3. 03

    Evidence for every action

    Each step records its sources, its result and who or what approved it, so a case can be traced.

  4. 04

    Data in approved environments

    Records and working data stay in your approved environments, under accounts held in your name.