Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Benefits of a Guidewire-FileNet Integration
Semelhante a Benefits of a Guidewire-FileNet Integration (20)
Último
Último (20)
Benefits of a Guidewire-FileNet Integration
- 1. Leaders in Enterprise Content Management Connecting Content | Driving Performance
- 2. “Lack of attention to the document management process during our Guidewire implementation caused delays and cost overruns” Guidewire Program manager, Fortune 500 Insurance Company •Guidewire is winning! •They have a great product that is driving a new standard in insurance •Great at the sale •Consider ECM an “ancillary” system •Integrators of Guidewire are very expensive and possess little ECM expertise.
- 3. WHY IS ECM SO VITAL To a Guidewire Implementation Let The Rocket Scientist Launch the Rocket •Guidewire Integrators are great at installing, configuring and integrating •Have little experience with ECM •More to it than pulling documents from FileNet •An ECM expert knows how to optimize input streams
- 4. WHY IS ECM SO VITAL II • Don’t strap a jet engine to a Pinto • Evaluate all the options: o Mobile Access & Input o Forms Automation and Generation o One Version of The Truth o Enhanced Claims Fraud Investigation Real flying Pinto
- 5. Guidewire ECM Challange Risks to project from the changing input streams: •Your document capture system needs to change •Lack of attention to use cases •Delays in processing •Reduced Productivity in paper chasing • Sneaker Brigade •Inefficient capture processes •Decreased implementation satisfaction •Higher rate of exception processing •Lack of trust in the overall solution •Inaccuracies in processing SECRET - NOT MUCH HAPPENS IN GUIDEWIRE WITHOUT A DOCUMENT
- 6. Guidewire / FileNet Framework FileNet enhances a Guidewire implementation: •Seamless automation of multiple document input streams •Single source of the truth document repository •Improves seed of transaction GW/FN
- 7. Changing Input Streams Documents Centralized Document Capture • New use cases • New information needed in capture process • Potential volume increases • Indexing automation changes • Upgrade to existing Kofax • Hardware upgrade on scanners • Potential new forms development from GW output for auto recognition • Capture process needs to mature to keep up • Additional matrix • Integrated reporting with GW workflows
- 8. Changing Input Streams- Customer Correspondence Thunderhead Correspondence Management • Identify use cases • Sync GW data availability with form generation process (round trip) • Define standards for forms • Define distribution channels and impact to forms • Email • Fax • Web • PDF • Mobile
- 9. Changing Input Streams- Desktop Experience Desktop Interaction • Use case development • Document templates • Indexing data and auto population • Email input and indexing • Email attachment-attachments • Drag and drop management
- 10. Changing Input Streams- Other Mobile and Internet • Define use cases • Define security • Devices supported • Network/performance Workflows outside GW workflows needs to be handled • Adhoc exception processing • Fraud investigation • Intradepartmental processing
- 11. PROVEN MODEL
- 12. THE FRAMEWORK The Construction of the Framework encompasses design, architecture, integration, deployment and training: •Input Stream Assessment Workshops to identify the detailed requirements •Solution Architecture Appropriate sizing of the solution to insure the system can handle the volumes and complexity. •Process Transformation The Dayhuff Group has 17 years experience transforming redundant, cumbersome processes
- 13. THE FRAMEWORK cont’d • GWFN Gateway* We have created a seamless integration that can be configured to communicate and pass information between all three components: Guidewire, FileNet and Thunderhead • ECM Program Management Managing the transformation of the ECM process in concert with your Guidewire solution is essential and requires vast experience. We will guide and mitigate potential risk by aligning project personnel, providing consistent communication and utilizing an established project approach
- 14. GW ECM Deployment Team Use a project team that has successfully complete the same solution: •ECM Program Manager •Solution Architect •Business Analysts •FileNet Specialist •Thunderhead Reports Writer Mentor •Capture Specialist (design/technical) PHASE ONE Jan Feb Mar April May June July Aug Sept Oct Nov Dec Jan Feb Mar April May June July Aug Sept Oct Nov Dec Program Manager Solutions Architect Business Analyst Business Analyst SR IT Specialist Capture Specialist Thunderhead Dev FN Specialist FN Specialist
- 15. The Dayhuff Group has a long history of providing enterprise content management solutions in a wide variety of industries. • Successful business for over 17 years • IBM Premier Business Partner, Software ValueNet Partner • IBM Information On Demand 2012 Excellence Award • Over 200 projects at over 80 companies • 98% customer satisfaction rating 15 Short-cycle project completion within real-world budgets.
- 16. A smooth implementation of Guidewire requires a successful deployment of a document management system. The overall Project is dependent upon both solutions being effective. The Dayhuff Group Guidewire FileNet Framework will mitigate risk and reduce cost. More than anything, it will ensure that the business will get the optimization and efficiency for which you are investing. Let’s Get Started
- 17. Supporting Docs
- 18. Digital Input Management IBM Datacap •Provides option to customize capture processes to match YOUR needs •Is used to ingest and identify information from multiple sources •Provides consistent way to manage intake and the communication between Guidewire and FileNet •Handles high volume scanning operations and provides mobile capture capabilities for agents in the field. •Standardizes rules for input to assure information is consistently captured and stored •Acts as the central hub for rules •Provides detailed reports to ensure accuracy Claims and Underwriting are paper intensive processes…
- 19. Claims Fraud Investigation IBM’s Intelligent Investigation Manager •IIM is a powerful tool that expands the data collection of Guidewire to improve the way fraud is identified and managed •Coordinates and reports on cases, provides analysis and visualization •Enables more efficient and effective investigations •Visualization of fraud within structured and unstructured data across silos •Augments existing enterprise fraud solutions with fraud intelligence analysis, content analytics and thread detection analytics Guidewire ClaimCenter transforms the way and insurance company manages claims…… But together, IIM and Guidewire ClaimCenter provide a powerful set of tools for robust fraud investigation capabilities to minimize risk and loss.
Notas do Editor
- We don’t compete on a regular basis with GW integrators (PWC, Crow, E&Y, ETC.),
- Having a fast claims processing engine and taped together input streams will not allow you to realize your investment. Items commonly over looked are mobile, amount of forms automation, fraud investigation enhancements.
- The way you are capturing and indexing your documents today is not the way guidewire expects them. The metadata you are captureing will not be what is identified in the use cases and GW will need specific information from a document at a specific step in the process to move a process along. If the metadata changes the forms template changes and the auto indexing changes. The existing documents metadata may need to be dumped and the metadata field repopulated. GW needs information feed to it as it defines the workflow to operate properly. If not you will slow down the workflow.
- Interacting with guidewire from office applications is a critical function to the users. Storing a word document or a spreadsheet directly from Office seems like a remedial task, but is the user has to enter to much or make several clicks to just get it into guidewire it will cause dissatisfaction. Getting very detailed on the use cases for the desktop experience is necessary to make sure the information guidewire expects to get is received and conversely pulling data from guidewire or filenet or other to reduce the amount of indexing the user has to do will enhance the users experience. This needs to be done for every use case. You are going to build this great backend system with tons of capabilities, but If a user can’t efficiently store an office document to GW they will say the system is not working well.
- You may not choose to deploy the mobile functionality of guidewire now, but I bet your users are aware of it. If you do you need to distinctly define the use cases and the functionality that will be used. Guidewire will tell you that they handle all of the workflow in the GW product. This is true for the most part, but in our experience there are adhoc and one off workflows that you will run into that will require workflow outside GW. One example is fraud investigation.
- Most insurance company operate for the most part alike. About 75% of the work they perform will look much like the work in any other insurance company in the nation. The 25% is what make them unique and is their go to market strategy. By having the use cases defined for 75% of the work it allows you to focus on the 25% that make you unique. You are going to blow up the scanning and indexing operation as it works today to make sure it fits how GW is being implemented. This will require an evaluation of the entire solution to make sure is meets your performance requirements. GW is a transformational solution and will require you to address your ECM solution as a transformational asset as well we have 17 yrs experience in ECM transformational project to guide you through this process
- Most GW implementation we have seen have program mangers that run different parts of the project and then a program manager owner. There is typically a program mgr for the GW piece, one for the integrations efforts and one for the ECM component. Are you planning on structuring in this fashion? We have a PM that can guide the ECM effort and ensure it is in-line with all of the other programs. You would be surprised the number of times a decision in one area to more or slip a schedule causes a ripple effect in the other programs that cost weeks and months.