Topics:
· About Financial Service Analytical Applications
· About Oracle Financial Services Data Integration with Unity
· FS Data Integration with Unity Architecture
· Sequence of Integration Processes
OFSAA is a suite of applications covering risk, performance, financial crime, compliance, customer insight, and regulatory reporting functions. These applications are built on common technology infrastructure, works off a singular data model that has unified structures for non-redundant acquisition, hosting, and processing of data, and renders rich information output that can be analyzed across a conformed set of perspectives. Sophisticated processing engines underlying the suite facilitates modular deployment and are controlled by comprehensive, user-configurable metadata. See Oracle Financial Services Analytical Applications portal for additional details.
Unity allows its subscribers to combine customer data from online, offline, and third-party sources to create a single, dynamic, real-time view of each customer. Oracle Unity Customer Data Platform also supports the application of machine learning to prescribe the best next action within any existing business process. It supports a host of functions including unified customer profile, profile enrichment, smart segmentation, customer analytics, and rendering of personalized customer experience.
It is part of the Oracle Advertising and Customer Experience suite of services and is in use at several institutions across the globe.
Core objectives of Financial Services Data Integration with Unity are as follows:
· Leverage information from advertising, behavioral intelligence, marketing, and campaigns, collated through CDP for analytical processing and usage.
· Leverage quantified financial services information and metrics for front-office functions, as above.
· Leverage factory-integrated environment for customer engagement.
· Provide accurate, verifiable, actionable Next Best Action or Next Best Offer information.
These objectives are achieved with these core considerations:
· Integration through standard APIs.
· Seeded content for financial services.
· User-configurable extensions.
· Intelligent coverage for PII, non-nullable and mandatory.
· Broader integration with Oracle Customer Experience ecosystem.
The rest of this guide expands on how the stated objectives can be met.
Unity identifies and exchanges data assets for customers or parties, party accounts, products, relationships, and transactions between OFSAA and Unity, Oracle’s enterprise customer data platform. This includes customer or party, behavioral intelligence, advertising, marketing, and campaign information, alongside quantified financial metrics and related information. Such financial metrics primarily include retail customer performance and related analytics. The information set provided by Oracle out of the box may also be extended in use by institutions to fit their individual needs.
The following schematic represents the architecture of integration between OFSAA and Unity. Such integration relies on Unity’s REST Application Programming Interfaces (APIs), Comma Separated Value files (CSV), and Secure File Transfer Protocol (SFTP) for the transport of files between the two environments. This user guide provides the details of the steps involved and specific mechanisms in play at each step.
Figure 1: OFSAA – Unity Product Integration Architecture
The following is a summary of the flow of data between the two systems:
1. OFSAA collates and hosts data on customers, customer accounts, products, account balance, and related risk, performance, crime, compliance, and customer insight information. Note that, the nature and detail of data hosted by OFSAA depend on the OFSAA application(s) deployed in your instance.
2. Unity collates and hosts detailed customer data covering advertising, marketing, campaigns, and behavioral intelligence. This data is processed or enriched to maintain Master Profiles and related information.
3. OFSAA registers structures necessary for data exchange with Unity.
4. Unity shares the master profile and other data with OFSAA.
a. This is handled through CSV files transported between the systems through SFTP.
5. OFSAA enriches data so obtained with models specific to financial services, including Next Best Offer and Product Propensity.
6. OFSAA shares enriched data with Unity.
b. This is handled through CSV files transported between the systems through SFTP.
FS Data Integration with Unity provides the mechanism for the exchange of data structures and data along with tools for configuring or managing such flow, the details of which are available in the following sections.
The process sequence to establish data exchange between OFSAA and Unity through FS Data Integration with Unity is listed as follows:
· Setup OFSAA details in Unity and Unity details in OFSAA
· Choose entities and attributes for exchange with Unity in OFSAA
· Publish entities and attributes structure to Unity in OFSAA
· Execute batches in OFSAA to export requisite data to files
· Transport files from OFSAA to Unity via SFTP
· Setup file ingestion in Unity
· Execute file ingestion in Unity
· Setup data export in Unity
· Execute data export in Unity
· Transport files from OFSAA to Unity via SFTP
· Execute batches in OFSAA to ingest requisite files
Only the execute and transport steps in the list above are operational tasks that must be repeated periodically. Others are one-time setup tasks or executed on changes, as detailed in the tabulation as follows:
Sl no. |
Process or Task |
Type |
---|---|---|
1 |
Define ‘Sources’ in Unity |
Setup Once |
2 |
Define ‘Unity – Setup’ in OFSAA |
Setup Once |
3 |
‘Refresh Data Interface’ in OFSAA |
Setup Once Repeat on data model refresh |
4 |
‘Choose Data Interface’ in OFSAA – ‘Inbound’ and ‘Outbound’ |
Setup Once Repeat on data model refresh or when changes are needed |
5 |
‘Review and Publish to Unity’ in OFSAA |
|
6 |
‘Generate Connectors’ in OFSAA |
|
7 |
Execute automatically generated Batches in OFSAA |
Operational – as needed, periodically |
8 |
Move files through SFTP to Unity |
Operational – as needed, periodically |
9 |
Define ‘Data Feeds’ of ‘Ingest Job’ type in Unity corresponding to the files and ‘Start’. NOTE: You can also set the Job to ‘Recurring’ and define a schedule for automated execution or notification. |
Setup Once Repeat when additional files are required |
10 |
Monitor Jobs of ‘Job Type’ ‘Ingest’ through ‘Jobs’ in Unity corresponding to the files. |
Operational – as needed, periodically |
11 |
Execute ‘System – Data warehouse’ job through ‘Jobs’ in Unity |
Operational – as needed, periodically |
12 |
Execute ‘System – Identity Resolution Pipeline’ job through Jobs in Unity |
Operational – as needed, periodically |
13 |
Define ‘Data Feeds’ of ‘Export Job’ type in Unity corresponding to the ‘Inbound’ ‘Data Interfaces’ in task 4, above, and ‘Start’. NOTE: You can also set the Job to ‘Recurring’ and define a schedule for automated execution or notification. |
Setup Once Repeat when additional files are required |
14 |
Monitor Jobs of ‘Job Type’ ‘Export’ through ‘Jobs’ in Unity corresponding to the files |
Operational – as needed, periodically |
15 |
Move files through SFTP to OFSAA |
Operational – as needed, periodically |
16 |
Execute automatically generated Batches corresponding to ‘Inbound’ ‘Data Interfaces’ in OFSAA |
Operational – as needed, periodically |