Adjuster uses Scoping App and Xactimate to enter inspection data

  • In this case, the claims would be created and assigned in XactAnalyis.
  • The same data would be available in Brush Claims home instance of XactAnalysis. (like a parent-child relation, where the parent is the XactAnalysis owned by Verisk and Child would be Brush Claims instance of XactAnalysis).
  • The claim must be created in Hubvia through EDI.
  • The Adjuster gets the assignment of the claim and will use Xactimate and Scoping App to enter the inspection data.
  • Any information entered by the Adjuster in scoping App must be imported to XactAnalysis and pushed to Xactimate. Xactimate calculates the estimates with the data entered and imported.
  • The Adjuster hits 'connect' in Xactimate and the estimates would be pushed to XactAnalysis home instance.
  • The supervisor reviews the estimates and if no corrections are needed then the status would change to QA approved.
  • The estimates would be pushed to XactAnalysis Parent Instance and Hubvia as well. This data would be kept in Hubvia storage.
  • Hubvia will use the estimates to populate TGL and will change the status of the claim to 'Ready to Invoice'.
  • The details of inspection, docs, attachments, images and all of the estimation data is stored in Hubvia's data storage as they set the base for any future references. (History Data).
  • The role of Hubvia in this scenario would be to get all of those data in XactAnalysis and get the invoicing and payment part done.