Quaeris Implementation Document (QID):
RiskKarma
Powered by Quaeris
SECTION I:
BACKGROUND
WHY QUAERIS
RiskKarma is currently running their analytics using traditional BI and are interested in utilizing Quaeris
to expand the impact of their data. Primary interest for Quaeris is regarding the ability for users to query
in plain English, receive recommendations, and have a seamless experience when interacting with their
data and reports.
A Proof to Production (PtP) of Quaeris is being proposed and this QID captures the details of the PtP.
KEY CONTACTS
Company
RiskKarma
Name
Jo Lynn
Clemens
Title
CEO
Client Lead
RiskKarma
Quaeris
Role
Contact
<jolynn.clemens@riskkar
ma.io>
Client Lead
Anya Bhatnagar
Principle Consultant
Implementation Lead
PROJECT TIME-LINES
Estimated POV Start Date
Estimated POV Delivery Date
Estimated POV End Date
Confidential: To be used only by authorized clients of Quaeris
September 2023
September 2023
October 2023
anya@quaeris.ai
513-680-4248
PTP PROJECT OVERVIEW
USE-CASES
Sample Use Cases:
Use Case 1: Ad Hoc/Personal Insights
-
User should be able to run simple Natural Language Search and complex Structured Searches.
Searches should return the correct chart and data.
User should be able to create personal PinBoards and Pin the results.
User should be able to do progressive discussion using the Threads feature.
Use Case 2: Standard Reporting
- Ability to create representative PDF/PPT reports using ‘Stories’ feature.
Not in scope:
- Active Directory or Single Sign-On
- Additional Data sets/source or additional users
PTP SUCCESS DEFINITION
Quaeris POV will be considered successful when:
-
We deliver on the above use-case
Flexibility to adopt an existing insight/dashboard/report/s to personalize the content
Speed to insight – 2 minute responses VS waiting on someone else to answer the question
ROI quantification
IMPLEMENTATION PLAN & EXPECTATIONS
IMPLEMENTATION STEPS
Confidential: To be used only by authorized clients of Quaeris
DATA REQUIREMENTS
Please provide detailed information on/about your data:
-
Client to provide data for Quaeris in Analytical Views. While Quaeris can offer a great use-case for
Data Quality improvement, for this POV, Data Quality is the responsibility of the client.
-
Please share read-only credentials for us to access the above: Internally hosted
-
Data access and credentials:
Data
1.
2.
3.
4.
4.
5.
Comments
Data Set: Table or view, number of tables
DB Type: Azure SQL/Synapse/Postgres?
Live connection/off-line data
On Prem/Cloud, Live connection?
Credentials for read-only access
Refresh frequency
DATA STRUCTURE
Please provide the Description of any industry-specific columns:
Column
Columns Description
1.
2.
3.
4.
SAMPLE QUESTIONS
Please provide at-least five sample questions that users may want to ask:
Natural Language Questions
Confidential: To be used only by authorized clients of Quaeris
Structured Queries
TECHNICAL CONSIDERATIONS:
Consideration
1.
Please white-list the following IP addresses:
1.
2.
3.
4.
Active Directory Integration
Data source location for POV
Data source location in Production
Response
Q.ai Dev Env: 52.186.46.159
Q.ai Dev Env: 52.177.196.66
Anya’s IP: 74.66.0.129
Ruchi’s IP: 107.214.65.179
Not in scope
Quaeris DB
Cloud?
ASSUMPTIONS
1. Client will assign a dedicated role as ‘Quaeris Owner’
2. A set of sample questions should be provided to Quaeris in this QID, which will be used to test
model performance.
3. Read-Only dataset is available on a performant data-store on cloud.
4. Quaeris is not responsible for data-quality or performance of queries, if we leverage in-database
queries at client site.
5. Your business and IT SMEs available during the configuration steps. We estimate this effort to
take about two to four hours spread over the implementation time.
PTP PRICING
PtP Pricing includes everything from Implementation to Production:
Confidential: To be used only by authorized clients of Quaeris
USER ACCEPTANCE TESTING (UAT)
Quaeris Implementation Demo: Once implemented, Quaeris will demo the application. Get feedback,
incorporate the same and do another demo.
Enable the User IDs of users to be enabled in Quaeris.
Set up a training session/s for the users.
Training: Training schedule to be worked/decided when Quaeris implementation is demoed.
UAT Duration: User Acceptance Testing should be completed in a dedicated ‘War Room’ setting over
Zoom. This should take no more than an hour after Quaeris training has been provided.
UAT Results: UAT testers will use the below provided UAT Testing Results/Success Criteria sheet to
confirm test success. This should be completed in electronic format as email to Quaeris from all UAT
testers.
UAT Testers: UAT Testing will be done by no more than two people, or a max of one tester per persona,
whichever is higher
No.
UAT Tester Name
Role
Comments
1.
2.
3.
ACCEPTANCE OF PTP
We accept the scope of PtP and Acceptance Criteria as laid out in the QID and agree for PtP fee of
$20,000 at the beginning of the PtP effort.
SIGNATURES
RiskKarma
Quaeris, Inc.
CEO & Project Sponsor
Customer Success Manager
Signature
___________________
Signature
_____________________________
Name
___________________
Name
_____________________________
Title
___________________
Title
_____________________________
Date
___________________
Date
_____________________________
Confidential: To be used only by authorized clients of Quaeris
Confidential: To be used only by authorized clients of Quaeris