Below is the step-by-step process that we will follow for FIU integration. Please have a look at it and reach out to your CSM in case of queries.
Sales meeting/LOI Signed
Sales and/or Ops will finalize the LOI and ensure it is signed by FIU (Expected Timeline - 1 to 2 Weeks)
Agreement closure
This will be a parallel procedure with UAT. CAMS Ops will get the agreement closed with FIU. This is a necessary step for CAMS team to raise and share Production credentials. (Expected Timeline - In parallel to UAT and prior to PROD credentials sharing)
Integration call between CSM & FIU
Sales SPOC will set up an introductory call between CSM & FIU SPOCs. Demonstration of AA capabilities, type of journey (standalone/integrated), usecases to be explored and finalized. CSM will share the relevant docs basis this discovery call. (Expected Timeline - Day 1 (Technical integration))
Integration call between CSM, FIU and BSA team (If applicable)
If the FIU signed for Anlaytics offering, Sales and CSM SPOC will set up BSA call between Think360 and FIU. Demonstration of BSA offerings, list of variables to be explored and finalized. CSM will enable BSA based on the variables chosen while creating UAT credentials. (Expected Timeline - Day 2 (Varies based on FIU decision))
Consent parameters confirmation; UAT credentials & UAT Webhook URL sharing
FIU to confirm the consent parameters for use case ID creation. Based on this, CSM will share the UAT credentials. (Expected Timeline - Day 2)
UAT Webhook URL sharing
FIU to share Webhook URL to receive data in UAT (in case of integrated journey). (Expected Timeline - Day 3 to 4)
Prototyping (Optional)
FIU can share details of their current journey to CSM, who will incorporate the AA flow and share back a figma of the entire flow. (Expected Timeline - Day 5 to 7)
UAT related Development/Testing
FIU will perform the UAT at their end and CSM to support on issues faced by FIU. (Expected Timeline - Day 7 to 9)
UAT Sign off
FIU to provide UAT signoff.
In case of BSA clients variables will be finalized at this stage.
Production entry with Sahamati
FIU to provide license copy, SPOC details to cc in mail to Sahamati and finalize consent parameters . In case of Integrated journey, FIU should share Webhook URL to configure in Production. CAMS CSM will raise a request with Sahamati for Production credentials.
Prod credentials to be shared on agreed consent parameters
In case of BSA clients, CAMS to configure BSA credentials in Production.
CSM to share prod creds with FIU based on agreed parameters.
CUG testing
Testing with Production credentials would be perfomed by FIU to check if data is being received in the back-end, and supported by CAMS CSM.
For One-time implementation cost clients, invoice to be raised at this point to FIU (as per agreement)
Within one week of sharing Production credentials OR 10 CUG pulls for one-time fetch usecases and 20 CUG pulls for recurring fetch usecases (whichever is earlier), CAMS Ops will raise the invoice to FIU. This will be done as soon as agreement is closed AND the above criteria is met.
FIU side Development (in Production); FIU pushes AA to live platform
Post CUG, FIU will do the necessary development to go live in their application/platform within a reasonable time.
Go-live support
CAMS CSM will support FIU as the journey is pushed live on the application/platform, and address any immediate go-live issues. Post going live, CSM will continue to provide updates and information on a regular basis to ensure meaningful utilization of AA data for FIU, enable additional usecases etc.