Many of our new customers' deployments of Quantexa, like most new software projects, will get tested and incorporated into one use case first, for example retail AML or KYC. Once proven successful, delivering data without doubt to drive business success and very likely a more efficient stack, it can extend into other use cases, perhaps customer intelligence, trade AML, or credit and counterparty risk management.

At this point, firms can look ahead and reduce their future maintenance overheads by coordinating sensibly their adoption of the Quantexa Decision Intelligence Platform. However, it is important that firms know the resources and components of the Quantexa Platform that can be shared across multiple use cases to optimize cost reductions and improve governance.

This article explores how Quantexa Platform components can be shared and reused so that customers can adopt and develop best practices optimally.

Opportunities to share Quantexa components across use cases

In our experience, following the successful implementation of a first use case, new teams may acquire Quantexa from the bottom up for an identified new use case. Alternatively, central development teams might own the process and start drawing in appropriate use cases across the organization. Centralized deployments more likely encourage repeatability and re-use, but understandably not all organizations are centrally coordinated. Even so, cross-coordination between separated teams, perhaps across a data fabric architecture, has proven extremely effective when best consistent practices are applied. For even the largest banks, heavily federated by business functions, such coordination may seem non-trivial. Yet even there, cross-departmental initiatives are particularly impactful, great vehicles for personal growth and collaboration.

To avoid inefficiencies and mistakes, Quantexa customers who have already undertaken this journey do recommend collaborating across use cases to develop common workflows and infrastructures. When successful, maintenance overheads can be minimized, costs lowered, scale expanded, stacks consolidated and new opportunities for knowledge generation created.

Quantexa Platform use case sharing highlights

At the core of a scalable and cost-effective multi use case deployment is a set of centralized component opportunities. One of these is centralizing data ingestion for common data sources, which reduces IT costs and saves time with reduced storage and processing, normally outweighing additional operational overheads. This particularly applies to “large” data sources, such as third-party corporate registry data.

Another of these is centralized batch entity resolution that could feature in the design, although carefully balance potential benefits against use-case-specific requirements for custom entity resolution.

Our experience is that the UI/Mid-Tier, Batch Networks and Analytics should not be centralized. The demands of use case-specific individuality, agility and flexibility usually outweighs any centralizing storage, processing and governance cost and time benefits.

To ensure development and operations remain smooth, deliver value and future-proof your design, you should:

• Clearly define interfaces between technical components and teams. This minimizes friction and improves coordination between teams and ensures a common understanding among stakeholders.

• Document and formalise previously ad-hoc processes, such as onboarding new use cases. This will ensure consistency as systems expand.

• Ensure infrastructure can scale both up and down with development activity. Otherwise, static infrastructure can cause contention during busy bursts of activity and sit idle during quiet periods. Such negative outcomes are costly.

Consider also the organizational structure of your Quantexa program. The best way to empower different use cases – possibly owned by disparate departments across the organization – is to build on top of a robust team dynamic which could include:

• A single IT owner, whose mandate is to make the Quantexa service available to those consumers who need it;

• A technical “Design Authority” of experienced resources, which provides a level of architectural assurance and technical decision making not limited to but including the platform’s long-term development and sustainability;

• A platform team, which treats (Quantexa) developers as customers. Think of them as a Quantexa Center of Excellence, creating tooling and automation to facilitate consistency and efficiency for all Quantexa developers and across all use cases.

Delivering data without doubt

Quantexa improves decision-making and performance across impacted business teams while helping consolidate technology stacks. Furthermore, when deployed well across multiple use cases, Quantexa allows cost and governance savings from optimized component and infrastructure-sharing.

For more information on hints, tips and deep dives on how to share and collaborate on specific components, see:

• Quantexa Deployment for Multiple Use Cases

• Quantexa Deployment Patterns: Best Practices

• Centralized Data Sources

• Quantexa Community Service Building and Transition Section