Skip to main content

August 21, 2026

BluCARE Intelligence

a. Scope Resolution

  1. AI analyzes the email subject + email body + sender's scope to determine the appropriate System and Building.

  2. AI calculates a weighted confidence score for the suggested scope.

  3. Based on that score, the ticket gets one of four statuses:

    1. Auto Confirmed.
    2. Provisional.
    3. Pending Clarification.
    4. Unresolved.
  4. Autoconfirmed tickets are automatically resolved.

  5. Provisional, Pending Clarification, and Unresolved tickets require attention through the Unresolved Tickets area.

  6. Users can select an AI-suggested System/Building candidate or manually select the correct System and Building.

  7. Once the scope is manually resolved, the ticket becomes resolved and is removed from the Unresolved Tickets bucket.

  8. If AI cannot determine a suitable scope, the ticket is assigned the Global System and Global Building as the fallback.

  9. Only BB users can see unresolved tickets area.

Scope Resolution on ticket form with suggestions table

Scope Resolution detail view with confidence score and ranked suggestions

NLC Power Controller Support

a. New NLC Model

  1. Added NLC as a new Power Controller model.

  2. NLC is now available when creating or editing Power Controllers for users with the required permissions.

  3. Existing NL4, NL2, and NLR models remain available.

  4. NLC controllers can be saved and reopened with NLC retained as the selected model.

  5. NLC is available only for Power Controllers and is not shown for other LSP device types.

  6. Added appropriate permission and database validation to ensure NLC is available only where supported.

Create Power Controller form showing NLC model option

Edit Power Controller form with NLC selected

MP Controller Model Support in Board Info

a. Enhanced Board Info

  1. Enhanced Board Info to display the correct MP controller model name for supported MP controller families.

  2. Updated model information to include the MP model name alongside existing EP/LP model names.

  3. Extended model support for MP1501, MP1502, MP4502, and MP2500 controllers.

  4. Updated firmware upgrade messages to display the same MP model information shown in Board Info.

  5. Maintained existing behaviour for non-MP controllers and existing EP/LP models.

  6. Improved compatibility across Mercury pages that use Board Info model information.

Controller Door Floor Diagnostics showing MP controller model in Board Info

Facility Filter for Mercury Configuration Pages

a. New Facility Filter

  1. Added a Facility filter to the Controllers, Readers, Inputs, Outputs, and Portals pages.

  2. Users can now filter configuration records by facility based on their view permissions.

  3. Added support for Facility-based filtering and cascading with existing System, Controller, and SIO Board filters.

  4. Facility selections are retained while paging and can be reset along with other filters.

  5. Improved usability with alphabetical facility lists, localized labels, and clear handling when no matching results are available.

  6. Existing filters and page functionality continue to work as before.

Controllers

Controller List with Facility filter dropdown

Readers

Reader List with Facility filter dropdown

Inputs

Input List with Facility filter dropdown

Outputs

Output List with Facility filter dropdown

Portals

Portal List with Facility filter dropdown