1. CoreLogic
  2. Solution home
  3. MICA Web
  4. DASH Integration

Equipment / inventory sync between DASH and Mitigate

Overview

Mitigate (fka MICA) users can access their DASH inventory equipment from within a loss in Mitigate and move that equipment onto a loss in the Mitigate mobile app.


This feature allows you to scan equipment in Mitigate if the job is linked to a job in DASH and you have equipment added in DASH.


This article covers two topics relating to the Mitigate & DASH inventory sync:

 


Adding equipment

Disclaimer

The job must be linked between DASH and Mitigate to utilize the equipment sync. If you need assistance linking your job between the systems, see this article for more information - Linking jobs between DASH and Mitigate

  1. When you are ready to add equipment navigate to the Equipment section on the loss in Mitigate.
  2. Click the Add External Equipment button
  3. Mitigate will automatically sync with the server to display all the available inventory equipment.
    • NOTE: if you notice any equipment is missing from the list, make sure that the equipment is "Linked to Manufacturer Specs" in DASH. You can do this by going to into DASH > hover over Administration > select Equipment > on the Equipment Details page filter for the equipment > select the check box next to the equipment > then click Link Selected Equipment to Manufacturer Specs
  4. From here, you can choose between two options:
    1. Picking equipment manually

    2. Scan barcodes of equipment

  5. Once the equipment has been added to the job in Mitigate (fka MICA), it will automatically show up in the equipment section of the Job Slideboard in DASH. Here you will be able to see: Equipment Name, Equipment Type, Barcode/Serial Number, Start Date/Time, End Date, Days on Job, Moved By (the user in Mitigate who placed the equipment), Current Location

 

Picking equipment manually

  1. Select the Equipment Type drop-down.
  2. Check the box next to the equipment you want to add
  3. Select Save at the top left corner of the window. The equipment will be added to the job.
  4. IMPORTANT: Currently, when you are adding a dehumidifier, for the AHAM Pint rating to be associated with the unit, you will need to select the “Subtype” drop-down and choose the matching model of the dehumidifier from that list. Neglecting this step will result in Mitigate not knowing how much moisture removal has been applied to any given chamber. This step is expected to be eliminated in a future release.

 

Scan barcodes of equipment

  1. Click on the Scan Equipment tab option
  2. Select Scan
  3. The barcode scanner will launch. Begin scanning the equipment you have placed on the job site into Mitigate.
  4. Once you have completed scanning, tap Done at the top right corner. All the barcodes that have been scanned will be added to the queue.
  5. Confirm the selection by selecting Save.

 

 

Removing equipment from the job

When the equipment is being picked up from the job site, all you need to do is indicate which unit is being stopped in Mitigate (fka MICA), which will automatically populate the “End Date” field in the Equipment section of the DASH  job.


NOTE: If removing multiple pieces of equipment, you can check the box next to the equipment being removed then choose “Stop All Selected” from the top of the window.

 

To return the equipment from the job to the storage location, you will need to access the Equipment section in DASH and update the location and status of that equipment manually.

  1. Navigate to the Equipment section under Administration in DASH.
  2. Locate the piece of equipment you want to update and click on the name.
  3. Adjust the Current Location and Status. 
  4. Click Save
  5. Repeat steps 2-4 for each piece of equipment that is being returned from the job site.



Questions? Contact Us!

 


 


 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article