⚠ The current problem statement
Currently, there is no standard CDA (Cloud data access) Connector to consume CDA data. Due to lack of standard connector, we are referring projects to SI partners as a standard approach and we are not able drive pace and predictability on the data project due to lack of standardization. Driving predictably where CDA is used is the main goal for this initiative. Feedback from client proved by Jay Coulson “Bridgett and I were on a call the other day where the CIO for BSI led us to believe that they might have interest in streaming data to Snowflake with CDA. She kind of said something like "it would be nice if Guidewire had a way to do this.”
👔 The future customers
Any project that is consuming CDA, will be benefited from the PS CDA Connector. It will provide a way for the client's data to team to consume CDA data and feed to their ecosystem.
💡 The idea & benefits
1: Standard services connector, will give options to our clients and have processional services engaged and implement standard PS CDA connector. We anticipate few customers will sign up. 2: This is also a great opportunity to provide alternatives to read replicas where we have for transitioning customers with subscription credits. 3: For transitioning customers will provide standardization through a services offering. 4: Professional Services engagement will provide input to cross selling opportunities that may be unrealized when the CDA work is outsourced to an SI partner.
Value proposition for the PS CDA Connector 1: Standardized solution 2: Block tables to save long term cost 3: Scalable horizontally 4: Real schema with proper data type 5: Extensive data reconciliation How 1: We will develop standardized Professional Services CDA Connector. Current Open source reader will be used as base. 2: We will be using Scala and Spark similar to what is being used by Product to develop CDA. 3: Current view generated based on the content provided by PS team. 4: Early access support for new features, like Lifecycle Events
Latest
15 October: Josh connected Bhavik to Abhi Tandon, as someone who might have capacity to help.
Sept 30: Josh to check-in with Bhavik re: funding - may be a sellable service
30 August: Bhavik has not been able to secure any dev capacity so far.
June 7th: Varada has offered to support this idea, and was to reach out to Bhavik to understand more about the ask - Josh to check in on progress.