Configure CAD integration components on a server

  1. Identify the CAD system you want to integrate FH Mobile Response with.

    Example: FH CAD Monitor, Genisis 911, Spillman, Printrak, or PowerCAD.

  2. Depending on which CAD system you are integrating with, follow the steps for the appropriate system below.

    ClosedFH CAD Monitor

    The necessary components for integrating with FH CAD Monitor were installed automatically when you installed FH Mobile Response.

    • Perform the rest of the steps in this topic for configuring the integration with FH CAD Monitor on the FH Mobile Response server.
    ClosedAll other CAD systems

    1. Contact your FH sales representative and ask for the customized installer specific to your CAD system.

    2. Run the customized installer for your CAD system.

      Note: You may want to contact FH technical support and schedule a time with a support technician to walk you through the integration process for your specific CAD system.

    Warning: The rest of this topic is specific to integrating FH CAD Monitor with FH Mobile Response. If you are integrating with a different CAD system, refer to the instructions above, under All other CAD vendors.

    ClosedUnderstand how CAD files are processed and sent to FH Mobile Response and FH CAD Monitor

    If you have only FH CAD Monitor installed and running on your system, the data files coming from your CAD system are handled in the following way.

    1. The CAD system drops the data files into a specific folder on your network.
    2. FH CAD Monitor checks (polls) the folder at regular intervals, such as every five minutes.

    3. FH CAD Monitor processes the files and sends the data to the FH database.

    When you integrate FH CAD Monitor with the FH Mobile Response server, extra steps are inserted into the process so that FH Mobile Response can send the data to the client computers in the field as soon as possible.

    1. The CAD system drops the data files into a specific folder on your network.
    2. FH Mobile Response monitors the folder, immediately processes the data files, and sends them to FH Mobile Response client computers in the field.
    3. FH Mobile Response saves copies of the data files in the folder that FH CAD Monitor checks for new CAD data files.
    4. FH CAD Monitor polls the folder at regular intervals.

    5. FH CAD Monitor processes any files it finds, and sends the data to the FH database.

  3. ClosedSpecify where call data files coming from the CAD system are placed on the server.
    1. In Windows Explorer, navigate into C:\Program Files (x86)\FH Mobile Response\FH Server\Listeners\RuleConfiguration.
    2. In a text editor, open ListensFolderMonitorSendsToCadMonitorFIP.folderMonitorMessageRule.

    3. Scroll to the bottom of the file and find the line <Folder>C:\CADFileDump</Folder>.

    4. Change the path in this line to the location on your system where your CAD system is delivering the incoming CAD data files.
    5. Save the file.
  4. Closed(Optional) Specify parameters for handling premature incident closures.

    An incident can become closed prematurely and FH Mobile Response client computers do not receive a dispatch for the incident if a CAD system sends incorrectly formatted values in the following file types and fields.

    • An ASCII text file, in the fhClearDate or fhClearTime fields.
    • An XML file, in the Last_Unit_Cleared_Dttm field.

    You can specify parameters in the configuration file to allow the FH Mobile Response server to ignore items in the CAD files that force an incident to close.

    1. (If it is not open already) In a text editor, navigate to C:\Program Files (x86)\FH Mobile Response\FH Server\Listeners\, and then open RuleConfiguration\ListensFolderMonitorSendsToCadMonitorFIP.folderMonitorMessageRule.

    2. Find the parameter <IgnoreIncidentCloseTime> in the file, and specify a value of true or false.

      If you specify true, then in the CAD data file, FH Mobile Response removes the time value from <Last_Unit_cleared_Dttm> and the incident is left open.

      If you specify false, and if <Last_Unit_cleared_Dttm> has a value in the CAD data file, FH Mobile Response closes the incident.

    3. Find the parameter <AssumeCallShouldBeForcedOpenIfIncidentCloseTimeIsNotIncludedInCallUpdate> in the file, and specify a value of true or false.

      Note: This parameter applies when an incident already exists in FH Mobile Response, and for which another message comes through from the CAD system to change something in the incident.

      If you specify true, when a new update to the closed incident comes in from the CAD system, FH Mobile Response opens the incident again because a value is not specified in <Last_Unit_cleared_Dttm> .

    4. Save the file.
  5. Closed(Optional) Specify parameters for closing old incidents.

    Some CAD systems re-use incident IDs after a certain time period. This practice can cause FH Mobile Response to reopen an old incident instead of creating a new incident.

    You can specify parameters in the configuration file to close "old" incidents before this time period occurs.

    1. (If it is not open already) In a text editor, navigate to C:\Program Files (x86)\FH Mobile Response\FH Server\Listeners\, and then open RuleConfiguration\ListensFolderMonitorSendsToCadMonitorFIP.folderMonitorMessageRule.

    2. Find the following parameters in the file.

      <CloseIncidentsThatAreOld>
      <IncidentsAreOldAfterThisNumberOfHours>
      <CheckThatIncidentsAreOldEveryThisNumberOfMinutes>

    3. In <CloseIncidentsThatAreOld>, specify a value of true or false to indicate whether or not "old" incidents are automatically closed.

    4. In <IncidentsAreOldAfterThisNumberOfHours>, specify the number of hours to pass before an incident is considered "old.
    5. In <CheckThatIncidentsAreOldEveryThisNumberOfMinutes>, specify the number of minutes to pass before FH Mobile Response checks for "old" incidents.
    6. Save the file.
  6. Closed(Optional) Specify parameters for converting city codes to full city names.

    Some CAD systems send the name of the city in the data file as a character and/or numerical code instead of as a full city name. FH Mobile Response client computers do not recognize the codes as city names, and are then unable to geocode the location properly.

    To resolve this situation, you can specify parameters in the configuration file to map city codes to full city names.

    1. (If it is not open already) In a text editor, navigate to C:\Program Files (x86)\FH Mobile Response\FH Server\Listeners\, and then open RuleConfiguration\ListensFolderMonitorSendsToCadMonitorFIP.folderMonitorMessageRule.

    2. Find the following parameters in the file.

      <ConvertCityCodesToFullCityNames>
      <CityCodes>

    3. In <ConvertCityCodesToFullCityNames>, specify a value of true or false to indicate whether or not to use mapping of city codes to city names in the configuration file.

    4. Under <CityCodes>, for each code you need to map to a city, add the following block of code.

      <CityCodeToNameGroup>
           <CadCode></CadCode>
           <CityName></CityName>
      </CityCodeToNameGroup>

    5. In <CadCode> and <CityName>, specify the city code provided by the CAD system, and the full name of the city the code maps to.

      Example:  
      <CityCodes>
           <CityCodeToNameGroup>
                <CadCode>Milw</CadCode>
                <CityName>Milwaukee</CityName>
           </CityCodeToNameGroup>
           <CityCodeToNameGroup>
                <CadCode>Balti</CadCode>
                <CityName>Baltimore</CityName>
           </CityCodeToNameGroup>
           <CityCodeToNameGroup>
                <CadCode>Mpls</CadCode>
                <CityName>Minneapolis</CityName>
           </CityCodeToNameGroup>
      </CityCodes>       

    6. Save the file.
  7. ClosedSpecify where call data files are moved to after processing by FH Mobile Response.

    By default, call data files are moved to C:\Program Files (x86)\FH Mobile Response\FH Server\Listeners\SavedSamples\CadMonitorDispatchFiles.

    Note: If you do not need to change the default location, skip steps a–f below.

    1. In a text editor, open C:\Program Files (x86)\FH Mobile Response\FH Server\Listeners\RuleConfiguration\Listens via FolderMonitor And Sends to SAVE.folderMonitorMessageRule.template.

    2. Near the top of the file, find the line <HandlerStringConfig>Path=CADMonitorSavedDispatches</HandlerStringConfig>.

    3. Delete CADMonitorSavedDispatches from the line, and then type the path where you want the CAD data files to be placed after they are processed by FH Mobile Response.

    4. Near the bottom of the file, find the line <Folder>C:\CADFileDump</Folder>.

    5. Change the path in this line to the location on your system where your CAD system is delivering the incoming CAD data files.
    6. Save and close the file.
  8. ClosedStop and start the FH Mobile Response Server service.

    1. Choose Start → Control Panel.

      The Control Panel window appears.

    2. Double-click Administrative Tools.

      The Administrative Tools window appears.

    3. Double-click Services.

      The Services window appears.

    4. Scroll down and find the FH Mobile Server service.

    5. Right-click FH Mobile Server, and then choose Stop from the menu that appears.

    6. Right-click FH Mobile Server, and then choose Start from the menu that appears.

    7. Close the Services window.
  9. Continue with Configure a client for the integration.