I just read the ‘Guide’ to the IRFI and its excellent, really well-written. As an independent developer, I really appreciate the detailed explanations of all aspects of the implementation. I’m excited about building solutions for clients – not only insurance producers – but, also working with carriers and agency management system vendors to help them provide the services needed for producers to effectively leverage the IRFI.

Here are (2) initial questions and comments:

1. Are the ‘Key Stakeholders’ in IFRI also the key to the FVC strategy? Page 54 of the guide under “Building Close Communication with Key Stakeholders” is perfectly understated. Seem to me, it’s the ballgame. If I’m following your work accurately, “Key Stakeholders” is the connection between the IFRI and the FVC.

“The Financial Value Chain is essentially an SDK or API set”, you said in Part 5. Seems to me, insurance producers aren’t going to get anywhere trying to implement the IFRI unless the carriers and agency management system vendors provide fully detailed “service catalogs” including ‘industry standard’ API’s for all relevant required functionality the insurance producer needs. To date, unambiguous SOA communication has not been part of many Key Stakeholders marketing strategies, to say the least. This is where the FVC fits into the scheme of things, I’m supposing - by re-framing software development reality in terms of service-oriented architecture.

2. I realize ‘Indigo’ is not going to be released until 2006. However, I’d like to provide the value added service of also preparing my clients for the next round of Microsoft SOA tools. Can you indicate what changes to the current IFRI would there be in light of what you know about the tools MS will be releasing in the future?

Thanks for the comments on the IFRI and as to your questions...

1. Yes, this is really a "meet in the middle" approach to information worker productivity. Lots of applicability in call centers where the carrier services and the user interface can be developed and supported inside the same enterprise. However, for the external producer to carrier, there is a need to get carriers to expose services that the forms can be plugged into. This could include custom forms as well using the same infrastructure once those services are developed.

The FVC is more encompassing than just IFRI, but that is surely part of the picture when it comes to data capture and user workflow.

2. Currently we have not scoped changes or updates to IFRI at this point. The next release of the WSE-style tools is likely to come with the VS.NET 2005 release, so that could be revisioned to incorporate those changes. But as of now, there may be no major changes that would influence the architecture in any major way.

PingBack from http://paidsurveyshub.info/story.php?title=josh-lee-s-financial-services-blog-just-released-at-long-last

PingBack from http://cellulitecreamsite.info/story.php?id=1876

PingBack from http://weakbladder.info/story.php?id=5324

PingBack from http://mydebtconsolidator.info/story.php?id=13061

PingBack from http://unemploymentofficeresource.info/story.php?id=5793

PingBack from http://lowcostcarinsurances.info/story.php?id=5781

PingBack from http://patioumbrellasource.info/story.php?id=1297

PingBack from http://debtsolutionsnow.info/story.php?id=5731