Sketch My Roof

Tags - Popular | FAQ  

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 01/15/2008 12:17 AM by  rickhans
Web Based Software Requirements
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
claimbuddy
Guest
Guest
Posts:6


--
11/12/2007 7:07 AM

    I would like to suggest a thread or (3), for the "potential" benefit of the catadjuster community, that attempts to stay focused on the "CatAdjuster" point of view.  Let me know if this is not appropriate here.  Large teams do not usually produce anything productive, fast....so....I suggest that as soon as we begin to develop a couple of different variations of "good ideas" we split the threads and allow the people that see things one way to work on that "system", and, those that see things another way, work on that system.  I suggest we think "out of the box"...and, without concern for "budget", however, I think it is a good practice to attempt to quantify a cost of development, including, a cost of defining the requirements...this mimics the actual cost of software development...for instance...let's assume our time is worth $55 bucks per hour.  Keep track of the time it takes you to reply or post...and include it at the bottom of the post.  For instance...this post will take me at least 2 hours to complete...So...we are already $110 into it....

    Also, if you will notice...I have included some formal looking text followed by a line.....then...I have added my "Ramblings".....which are just that..."Ramblings" as to why I think this may work...and, or some of the reasons why it may not...Remaining Questions, etc. etc.

    I.   Introduction

    A.   Entity Users & User Roles
    B.   Type of System
    C.   Objectives Summary
    D.   Functionality Summary

    I.     Introduction

    Let's just imagine we have recieved a "grant" from FEMA that called for the  "CatAdjuster" community to develop their own web based software system for back end databases and system maintainence, user management, the "dashboard" interface, the "data collection" interfaces, the integration with estimating softwares and carrier requirements, printed reports, data mining needs and interfaces, bookkeeping, etc. etc.

    A.     Entity Users & User Roles

    Insurance Companies, Adjusting Companies, Independent Adjusters  -  An entity has one primary administrator for its particular application.  The primary admininistator manages his users with the system and assigns each user a  "User Role".  Potential User Roles for an Insurance Company would be: Entity Primary Admin, Entity Secondary Admin, Call Center User, Claim Manager, Claim Adjuster....Most web based applications limit what the user can see and do based on User Roles. 

    B.     Type of System

    I don't know what the correct description of this would be, however, when I say type of system, I am really just referring to a web based system that is private for each entity...it must be secure...at least it must be as secure as anything else out there...so....assuming any web based system can be "hacked", we must design the system to pass the test of those entities that would be interested in seeing it work.....

    C.     Objectives Summary of the System

    Objectives of the System are bullet points for the highest level of functionality...not the specific features.  For instance....The overall objectives of a system designed from the point of view of the "Catadjuster Community" would be to allow the independent adjuster to do what:

    1) Work for Whomever and Wherever We Choose
    2) Recieve all the Assignments we ever wanted
    3) Be Cost Effective
    4) Help Reduce Software Requirements & Expenses - Certainly not increase the cost and difficulty
    5) Etc. etc.

    D.     Functionalities Summary of the System

    This is much more difficult than you would imagine...as...we must define the functionality for each entity and each user role within those entities.  For independent "CatAdjusters" it is much easier....for instance...

    1) Must be able ot earn a living and use the system with "One User Name and Password"
    2) Manage claims ..assignment, status updates, file uploading, diary, collaboration with contractors, summary, reports, etc. etc.
    3) Bookkeeping and Taxes - it would be nice if this were all included....


    Ramblings

    I would not expect any system to influence great changes in the way things work, especially with so many jobs and careers on the line that need to maintain the Status Quo.  

    If I were an Insurance Company I would like to track the variances between

    1) the Reserve, 
    2) the Call (initial estimated cost), and 
    3) the Final Actual Cost

    In addition, I would like to know

    1) Cost of Materials and the  Cost of Fully Burdened "Subcontracted" Labor  - meaning ...for each particular Catastrophe...maintain a common set of items for the processes and prices charged by the actual subcontractors that are doing the work....on a Trade, Job or Phase basis
    2) The status of the Reconstruction Process - how many Trades, Jobs, Phases left to complete....

    2 Hours - $110

     

     

     

     

     

    0
    Gale Hawkins
    PowerClaim.com
    Member
    Member
    Posts:386


    --
    01/01/2008 9:18 AM
    Donny your post shows lots of thought went into it. 2008 is here and web based claims management and estimating software will be on the minds of more and more.
     
    As you review the web options today in your effort to define the objectives and functional summaries mentioned above we would be pleased to set you up a PowerClaim Net Services account at no charge and maybe the other vendors would do the same with their web based solutions currently on the market so you can review what has already been created to help you nail down your wish list for future development that will better meet the industry needs. Like some of the other vendors PowerClaim Net Services can enable a vendor to have a full web presents complete with their logo to present to a carrier or TPA in 24 hours at no initial set up cost that can manage any number of adjusters. We at Hawkins Research Inc know there is much lacking in software tools that are flexible and affordable to all in the property claims handling arena but your effort to define the objectives and functional needs is a step in the right direction as I see it. Developing software is easy. Knowing what to develop is hard. Give us a call at 800-736-1246 or visit http://powerclaim.com/products/net_services if you or others would like or send me a private message by clicking my profile.
     
    We will be interested to see what thoughts others may share on this thread you have started. Some think independent adjusters will never work together for their own good but I think that is about the only choice there is because no external focus is going to step in to look out after the interest of the independent adjusters.
    0
    rickhans
    Member
    Member
    Posts:111


    --
    01/10/2008 2:01 AM
    You might add a catagory called "things we don't want it to do". For example
    1. Don't require an incomplete claim or notes to be uploaded. Examiners and carriers should not view the claim until the adjuster believes he has it finalized and has checked for errors, UNLESS the adjuster needs assistance and help from another adjuster. Then perhaps have an area to share the file with a helper or mentor, but allow the adjuster remove it from the system when ready to do so.
    2.Don't require any specific work to be done online over the internet. Just use if for sending and receiving information. I believe it is best to have all software tools and programs needed to do my job loaded on my computer, then just send the results when I have access to the internet.
    3.Don't require adjuster to keep an online log. Same as #2, if log is needed, allow it to be uploaded, replacing the prior log.
    0
    Ray Hall
    Senior Member
    Senior Member
    Posts:2443


    --
    01/10/2008 7:33 PM
    Well this was interesting reading, since I know most of the posters. This is some of my thoughts. Seems most of all the aforementioned programs are primarly residental western platform construction as they should be. Seems all have the ability to generate I2V and many type reports. Seems all have the ability to use the zip code for the risk to get acurate as possible estimates.

    I second Rick Hansen on the things we dont need, want and burden us down. E tranfer is a must and the carriers must bend and allow all systems to transfer data, INCLUDING the down load. Before puters I could climb, measure, photo and close 10-12 roof hail claims per day when I could hand write the 3 line estimate, run the tape,

    Paste the photos and turn in the files and now I am pushed to the limit to do 6; because of the puter.

    If this great tool does not make us more productive, lets go back 25 years and do it the old way. If the five estimating programs do not work like the auto claims, blame the carriers and I will testify for the folks.
    0
    rickhans
    Member
    Member
    Posts:111


    --
    01/15/2008 12:17 AM

    Ray,

    This may be a little off subject, but I noticed the same thing when after using EZbid for a long time I had to use Integraclaim to write roof claims.  I never broke the estimate down beyond tear off and put on, but with Integraclaim, and also Xact, I have to input every piece of doing a roof job.  Why do they now require us to input edging, felt, flashing, etc. etc. when most roofers charge one price per sq. to tear off and install? Up until 2007 the carriers that I did roof claims for gave us a  max price per sq. that they would pay turnkey,  and that has how the roofing subs have always charged me when I was a contractor.

    0
    You are not authorized to post a reply.


    These Forums are dedicated to discussion of Claims Adjusting.

     

    For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines: 

    • No Advertising. 
    • No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or others to respond. Any post that looks like trolling / poaching will be removed.
    • No Flaming or Trolling.
    • No Profanity, Racism, or Prejudice.
    • Terms of Use Apply

      Site Moderators have the final word on approving / removing a thread or post or comment.