Complex/Common Names

Complex/Common Names

Purpose

  1. The purpose of this Knowledge Base Article is to demonstrate how to create and manage the Complex/Common Name field in an Occupancy Record.
  2. Use case is to group a number of occupancies together whether they are on one site like an apartment complex, manufacturing complex, University campus, etc. or a group of occupancies owned by the same person/company across a FD jurisdiction.


Video



Instructions

Alert
Permission needed to manage the Complex Name field/table in Field Management:





1. Access an Occupancy Record by selecting the Address hyperlink on the following pages:
  1. Pre-Plan Organizer
  2. My Assigned Pre-Plans
  3. Pre-Plan List
  4. Pre-Plan (Address Details)
  5. Inspection Organizer
  6. Inspections List
  7. My Inspections



2. Select the Complex/Common Name from the dropdown list.






3. To create a new Complex Name on the fly, select Create New Complex Name, enter a Name and select "Create."
  1. We keep a historical record of all the modifications to the complex name. If a user edits one name, the old one is archived, and a new one is created. This is to be able to keep historical records for inspections and permits.
  2. The edit in a name will only affect in-progress, scheduled, and new inspections; it will not affect completed ones.
    1. The edit in a name will only affect new Permits.
    2. The edit in a name will only affect new Invoices.
  3. In the Pre-Plan Map, the "Complex Name" field will be part of the "Clone Address" and "Clone Address + Building Info" options when cloning the primary address.








4. Save the record or publish the Pre-Plan to retain the data selected.










5. Complex Common Names can be managed in Admin > Field Management > Complex Name:





Alternative method is to select Edit next to the Common Name field in the Occupancy Record or Address Details in a Pre-Plan:









6. Manage the List by selecting Edit:









7.  Mange Edit Roles Permissions:





Options include:
  1. Update - Can update the Common Name Field
  2. Read - Can view the Common Name Field
  3. Hide - Cannot view the Common Name Field





8.  The Complex Name Field is available in Advanced Search on the following pages:
  1. Pre-Plan Organizer
  2. Inspection Organizer
  3. Inspections List
  4. My Inspections
  5. Permits
  6. Invoice List





9. The Complex/Common Name Field is available in Form Builder to add to your Inspection and Permit Form(s):
  1. Note: If a Complex/Common Name for an Occupancy is changed, it will not affect previous Inspection Reports printed or emailed.



    • Related Articles

    • Complex/Common Names

      Purpose The purpose of this Knowledge Base Article is to demonstrate how to create and manage the Complex/Common Name field in an Occupancy Record. Use case is to group a number of occupancies together whether they are on one site like an apartment ...
    • Ad-Hoc Reporting: Custom Columns

      Purpose Statement Custom Columns in Ad-Hoc Reporting enable users to create calculated fields and combine data elements to generate new information not available in standard columns. This feature allows for mathematical operations, concatenations, ...
    • Pre-Plans: Address Details

      Purpose Statement This article explains the available fields and functions within the Address Details section of a Pre-Plan. Properly configuring address details ensures accurate dispatching, billing, and location-based visibility for responders. ...
    • AI-Powered ePCR Training Guide

      Purpose Statement This article provides comprehensive training guidance for EMS personnel to effectively utilize the AI voice-to-text feature in First Due's ePCR system. The AI feature dramatically reduces documentation time while maintaining ...
    • NERIS Reporting in First Due: Overview & FAQ

      NERIS Changes: A Data Perspective At a high level, the transition to NERIS does three things: Continues the use of many fields that already existed in NFIRS Introduces new fields added by NERIS Deprecates a number of NFIRS columns not being used in ...