<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Pradyumna</title>
    <description>The latest articles on DEV Community by Pradyumna (@prady1).</description>
    <link>https://dev.to/prady1</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3123469%2F3e5b9ccd-61fd-44fe-848a-4d15573a1d9f.png</url>
      <title>DEV Community: Pradyumna</title>
      <link>https://dev.to/prady1</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/prady1"/>
    <language>en</language>
    <item>
      <title>Empowering risk management users with data : Standardize data ingestion</title>
      <dc:creator>Pradyumna</dc:creator>
      <pubDate>Fri, 16 May 2025 02:03:53 +0000</pubDate>
      <link>https://dev.to/prady1/empowering-risk-management-users-with-data-standardize-data-ingestion-3587</link>
      <guid>https://dev.to/prady1/empowering-risk-management-users-with-data-standardize-data-ingestion-3587</guid>
      <description>&lt;p&gt;Risk management is a key function in banks to identify, access, maintain and monitor various risks. This is very important to ensure compliance with regulatory requirements and stability of the institution to continue investor confidence. Each institution will have its own structure, process to define adherence towards different types of risk functions. Most of Risk functions will involve the below steps =&amp;gt; &lt;br&gt;
Identification: Defining and uncovering potential risks, including their root causes&lt;br&gt;
Assessment and analysis: Evaluating the likelihood and potential impact of risks to prioritize mitigation efforts&lt;br&gt;
Mitigation: Implementing strategies to reduce risk exposure and minimize the likelihood of incidents&lt;br&gt;
Monitoring: Continuously testing, collecting metrics, and addressing emerging trends to ensure the effectiveness of controls&lt;br&gt;
Reporting: Generating reports on the progress of risk management initiatives to provide a dynamic view of the bank's risk profile&lt;/p&gt;

&lt;p&gt;Risk management is crucial now than ever given volatility in the banking industry and new risks emerging with evolution of new risks.&lt;br&gt;
Most Risk functions involve judgement from the users. Key Risk management strategy would be to automate the repetitive processes as much as possible and provide them diverse data points to allow Risk users to focus on key tasks requiring judgement.&lt;br&gt;
There are multiple considerations to automate a process however we will focus on the data aspect.&lt;br&gt;
To automate any steps for above Risk management functions, data will be required. Moreover data is needed from different departments across the institutions.&lt;/p&gt;

&lt;p&gt;However there are challenges to solve the data problem :-&lt;br&gt;
Ability to avail data from disparate systems within and outside the institution can be quite cumbersome given data formats, data types and data storage might be different&lt;br&gt;
Transform each source as per compliance needs&lt;br&gt;
Lot of risk functions may require past data availability which may have been in different formats given changes in technology landscape in the last few years. For example, Data storage can be on Cloud or On premise&lt;/p&gt;

&lt;p&gt;Lets focus on how to solve this problem of disparate data sources&lt;/p&gt;

&lt;p&gt;Step 1=&amp;gt;  Standardize a data ingestion layer&lt;/p&gt;

&lt;p&gt;Approach 1=&amp;gt;  Convert the data from different departments into a consistent format&lt;/p&gt;

&lt;p&gt;This can be achieved by building interfaces to convert different types of source data into one consistent format&lt;/p&gt;

&lt;p&gt;Pros : &lt;br&gt;
Abstract any source changes only at interface layer where source data is read and transformed to a consistent format&lt;br&gt;
Standardized format for output data&lt;/p&gt;

&lt;p&gt;Cons :&lt;br&gt;
Additional data persistence layers might be required. This will increase need to put controls for data processing&lt;br&gt;
Defining common format given volume and size of the data may vary as per different needs&lt;/p&gt;

&lt;p&gt;Below diagram shows standardization approach 1 =&amp;gt; &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Flz71bnp4icyu4v3czmox.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Flz71bnp4icyu4v3czmox.jpg" alt="Standardization Approach 1" width="719" height="270"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Approach 2 =&amp;gt; Define a common interface to ingest the data for Risk management usage&lt;br&gt;
Pros : &lt;br&gt;
Avoids duplicated transformations for each source&lt;/p&gt;

&lt;p&gt;Cons :&lt;br&gt;
Defining common format given volume and size of the data may vary as per different needs&lt;br&gt;
Building alignment from each department to publish data in requested format.&lt;/p&gt;

&lt;p&gt;Below diagram shows standardization approach 2 =&amp;gt; &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F48whz57pbehpea0z5h8j.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F48whz57pbehpea0z5h8j.jpg" alt="Standardization Approach 2" width="719" height="274"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Summary =&amp;gt; &lt;br&gt;
Risk management is a critical function for financial institutions&lt;br&gt;
Empowering users with data would be a key strategy&lt;br&gt;
Standardizing data ingestion is a key step towards enabling users with their data needs&lt;/p&gt;

&lt;p&gt;References =&amp;gt; &lt;br&gt;
&lt;a href="https://www.experian.com/blogs/insights/the-importance-of-risk-management-in-banking/" rel="noopener noreferrer"&gt;https://www.experian.com/blogs/insights/the-importance-of-risk-management-in-banking/&lt;/a&gt;&lt;br&gt;
&lt;a href="https://corporatefinanceinstitute.com/resources/career-map/sell-side/risk-management/importance-of-risk-management/#:%7E:text=The%20Role%20of%20Risk%20Management,-Primarily%2C%20risk%20management&amp;amp;text=These%20potential%20risks%20can%20include,guidance%20to%20mitigate%20risks%20effectively" rel="noopener noreferrer"&gt;https://corporatefinanceinstitute.com/resources/career-map/sell-side/risk-management/importance-of-risk-management/#:~:text=The%20Role%20of%20Risk%20Management,-Primarily%2C%20risk%20management&amp;amp;text=These%20potential%20risks%20can%20include,guidance%20to%20mitigate%20risks%20effectively&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Enable Risk management with ML through Scalable Cloud-Native Data Management</title>
      <dc:creator>Pradyumna</dc:creator>
      <pubDate>Sun, 04 May 2025 21:58:35 +0000</pubDate>
      <link>https://dev.to/prady1/enable-risk-management-with-ml-through-scalable-cloud-native-data-management-5eai</link>
      <guid>https://dev.to/prady1/enable-risk-management-with-ml-through-scalable-cloud-native-data-management-5eai</guid>
      <description>&lt;p&gt;Financial crimes are a persistent threat to financial institutions. Financial institutions have to build intelligent Risk management systems leveraging AI/ML which can defect and present malicious activities. Ability of computing power with the evolution of cloud computing has enabled leveraging machine learning(ML) for Risk management functions like anti money laundering.&lt;/p&gt;

&lt;p&gt;Data is the foundation of any machine learning project. One of key consideration is availability of high quality data as data quality plays a vital role in identifying and mitigating financial crimes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why data quality is important&lt;/strong&gt; =&amp;gt; &lt;br&gt;
According to Gartner, organizations in the financial sector experience an average annual loss of $15 million due to poor data quality&lt;br&gt;
Data quality and integrity is a critical challenge 66% of banks struggle with data quality, gaps in important data points and some transaction flows not being captured at all&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What are possible data quality challenges&lt;/strong&gt; :-&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpqtk6nlfwjnz0qe3zi98.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpqtk6nlfwjnz0qe3zi98.jpeg" alt="Data quality issues" width="800" height="600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Lack of data standardization across enterprise&lt;/strong&gt; =&amp;gt; &lt;br&gt;
Different systems across the enterprise may have data in various formats. For example, key data elements may have been defined using different data types across systems.&lt;br&gt;
This can cause issues in merging the data if required&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Accuracy and completeness&lt;/strong&gt; =&amp;gt; &lt;br&gt;
Data might not be complete or missing. If data is not complete then it can lead to issues in reporting which may lead to financial penalties&lt;br&gt;
If data updates may not be reflected across all systems it may lead to using incorrect data for compliance purposes&lt;/p&gt;

&lt;p&gt;Machine learning models may need data from past years which might not have been updated or may be in different formats&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What are ways to solve for these challenge&lt;/strong&gt; : &lt;br&gt;
Define data management policies and enforcing the policies&lt;br&gt;
Enterprises can look to define data management policies to define standards on how datasets and data elements should be defined&lt;br&gt;
Technology investment &lt;br&gt;
With Onset of cloud computing, building cloud native solutions which can allow for data lineage tracking, real-time validation and anomaly detection&lt;br&gt;
Building an technology ecosystem to ensure adherence to data management policies throughout data life cycle&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Let's look at below reference architecture&lt;/strong&gt; : &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F849y4zvvdukdg5kvgcn6.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F849y4zvvdukdg5kvgcn6.png" alt="Reference Cloud architecture" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Architecture components&lt;/strong&gt; =&amp;gt;&lt;br&gt;
Data Sources (Structured &amp;amp; Unstructured)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Financial Transactions&lt;/li&gt;
&lt;li&gt;Customer &amp;amp; Credit Data&lt;/li&gt;
&lt;li&gt;Compliance Data&lt;/li&gt;
&lt;li&gt;External Feeds (Sanctions, Market Data, etc)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Data Ingestion Layer&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;AWS Glue / Apache Kafka for real-time ingestion&lt;/li&gt;
&lt;li&gt;AWS Lambda for event-driven processing&lt;/li&gt;
&lt;li&gt;Amazon S3 for raw data storage&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Data Processing &amp;amp; Quality Validation&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Databricks / AWS EMR for batch data processing&lt;/li&gt;
&lt;li&gt;Apache Spark for large-scale transformations&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Metadata &amp;amp; Data Lineage Management&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;AWS Glue Data Catalog&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Data Storage &amp;amp; Warehousing&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Amazon Redshift / Snowflake for structured risk data&lt;/li&gt;
&lt;li&gt;Amazon S3 (Lakehouse Architecture)&lt;/li&gt;
&lt;li&gt;Data Lake&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Data Quality Monitoring &amp;amp; Alerts&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;AWS CloudWatch / Prometheus for monitoring&lt;/li&gt;
&lt;li&gt;Custom dashboards using Amazon QuickSight / Power BI&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Risk &amp;amp; Compliance Reporting&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;ML-powered anomaly detection for risk scoring&lt;/li&gt;
&lt;li&gt;Self-service analytics using Databricks SQL / AWS Athena&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Benefits of Cloud native solution&lt;/strong&gt; =&amp;gt; &lt;br&gt;
Accurate Data for Monitoring and Detection to ensure better data quality. This will enable accurate reporting for Compliance with Regulatory Requirements&lt;br&gt;
Seamless capture of metadata required for data management functions&lt;br&gt;
Efficient Risk Management through system controls avoid manual errors allowing key performers to focus on tasks requiring judgement&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt; =&amp;gt; &lt;br&gt;
Implementing cloud native solutions will integrate data management into the data lifecycle. This will benefit internal users as required data will be available to the users in an automated manner. Internal users can focus on data analysis required to complete regulatory reporting&lt;br&gt;
Improved data management will aid to reduce data quality errors which will enable machine learning/AI model development and adoption&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
