Problem Statement:

RBI Guide Bot: Innovate to Educate - A Hackathon for Developing Smart Chat Bots for User
Assistance in Understanding RBI Guidelines

Background:

• In the age of digital advancements, there is a growing demand for tailored smart
chat bot solutions designed to respond to inquiries based on available datasets.
• Build a solution that is capable of understanding user queries related to RBI
guidelines, effectively guiding them to respective sections within the accompanying
help document.
• It's important to note that the RBI guidelines are available in both PDF and HTML
formats on their official website.
• For your convenience, the reference document can be accessed through below link-
Link:
https://rbidocs.rbi.org.in/rdocs/notification/PDFs/107MDITGOVERNANCE330357
2008604C67AC25B84292D85567.PDF

• The envisioned solution aims to interpret user queries on RBI guidelines, furnish
accurate responses, and direct users to the specific sections in the provided
document for additional reference.
Flow Example:

1. Home Chat Screen example:

2. Question-Anwer with PDF reference Examples:

For example:

Question: Tell me third-Party Arrangements rules

Answer: The rules for third-party arrangements include the following: 1. REs (Reporting
Entities) must have an appropriate vendor risk assessment process and controls in place,
proportionate to the assessed risk and materiality. 2. The vendor risk assessment process
should mitigate concentration risk, address any conflict of interests, and mitigate risks
associated with a single point of failure. 3. REs must comply with applicable legal,
regulatory requirements, and standards to protect customer data. 4. High availability of
services must be provided to ensure uninterrupted customer service. 5. Supply chain risks
must be effectively managed. 6. Transaction details of the sale of third-party products and
related records should be maintained. 7. REs must obtain customer due diligence records
or information from the third party within two days. 8. Adequate steps must be taken to
ensure that copies of identification data and relevant documentation relating to customer
due diligence requirements are available from the third party upon request. 9. The third
party must be regulated, supervised, or monitored for compliance with customer due
diligence and record-keeping requirements. 10. The third party should not be based in a
country or jurisdiction assessed as high risk. 11. The ultimate responsibility for customer
due diligence and enhanced due diligence measures lies with the RE.
Requirements:

• User Interface (UI):

o Develop a user-friendly chat interface that simplifies the process of asking
questions. The goal is to enhance usability, making it easy for individuals to
communicate and seek information through the chat interface.
o Incorporate distinct sections within the interface, such as "New Chat" and
"Guideline References." The "New Chat" section serves as a dedicated space
for initiating conversations, providing users with a seamless platform to ask
questions. On the other hand, the "Guideline References" section is designed
to display relevant information sourced from the guideline document.

• Backend:
o In the backend system, a crucial process involves data parsing, where textual
information is extracted from the documents. This involves systematically
retrieving and isolating relevant content from the raw document data.
Through data parsing, the system transforms unstructured text into a format
that can be easily understood and utilized.
o The next step involves creating embeddings. In this process, an open-source
model is utilized to convert the parsed sections into embeddings, which are
numerical representations of the text.
o Following the creation of embeddings from the parsed sections, the next step
involves a comparative analysis. The system compares these embeddings
with those generated from user queries. By evaluating the similarities, the
system identifies the most relevant section from the guideline document.
o Implementing a context-based search involves identifying the pertinent
section within the queried document and responding with an answer
sourced from the guideline document. This process ensures that user queries
are met with precise and contextually appropriate information. To support
the answer, the system also displays the official document reference,
reinforcing the response's credibility and allowing users to cross-reference
the information directly within the guideline document.

• Context Based Searching: You can refer to above shared links. Here's an example
implementation of vector search
https://medium.com/loopio-tech/how-to-use-faiss-to-build-your-first-similarity-search-
bf0f708aa772
• Domain-specific Features:
o Contextual Response: Provide contextual responses based on user queries
about RBI guidelines, ensuring the highest accurate and relevant information
retrieval.
o Default Message Response: Implement a default message response for
irrelevant queries, guiding users back to relevant topics within the RBI
guideline document.
o Error Handling: Include error handling mechanisms to gracefully manage
unexpected scenarios, displaying informative error messages when
necessary.
o Document Referencing: Integrate document referencing in responses,
showing users the official document section to support and validate the
provided answers.
Constraints:

• Time Limit:
o Participants have a total of 2.5 hours to complete the hackathon challenge.
• Team Composition:
o Teams must consist of a minimum of 4 members each.
o Roles within the team should include:
▪ At least one member responsible for UI design.
▪ At least one member responsible for backend development.
▪ At least one member responsible for Language Model (LLM)
integration.
▪ At least one member responsible for documentation.
• Video Demonstration:
o Teams are expected to create a screen capture video demonstrating the
overall output of their solution.
o The video should include a walkthrough of the UI, showcase the functionality
of the backend, and highlight the integration of the Language Model and
overall code.
• Code Submission:
o Teams should be prepared to submit their code as part of the hackathon
challenge.
o Code should be organized, well-commented, and follow best practices for
maintainability.
o The team must submit their code to Winjit in .zip file and video capture demo
by uploading it on google drive.
o Instructions for this will be given by the Winjit team.
 Evaluation Criteria:

• User Interface (Design, Usability):

o Design Creativity: Evaluate the creativity and visual appeal of the user
interface.
o Usability: Assess how user-friendly and intuitive the interface is for effective
communication and interaction.
• Backend Functionality (Scalability, Security):
o Scalability: Examine the backbend's ability to scale efficiently with increasing
data and user interactions.
o Security Measures: Evaluate the robustness of security implementations to
safeguard sensitive data.
• Context Based Searching System:
o Accuracy: Assess the accuracy of context-based searching and generating
accurate responses.
• Domain-specific Features (Implementation, Creativity):
o Implementation: Examine how well the domain-specific features, such as
context-based search and dynamic document updates, are implemented.
o Creativity: Assess the creative solutions and innovative features that enhance
the system's ability to assist users with RBI guidelines.
• Demo (Screen Capture Video):
o Presentation Quality: Evaluate the clarity and professionalism of the screen
capture video.
o Comprehensive Demonstration: Assess if the video provides a
comprehensive overview of the implemented solution, showcasing UI,
backend functionality, machine learning aspects, and domain-specific
features.
o Alignment with Requirements: Ensure that the demo aligns with the outlined
problem statement and features.

The teams will be scored based on how well they address each criterion. A balanced
and well-executed solution that demonstrates creativity, functionality, and
adherence to the constraints is likely to score higher. The evaluation aims to
recognize teams that successfully integrate UI, backend, machine learning, and
domain-specific features to create an effective and user-friendly solution for the RBI
guidelines chatbot.