Announcement Management

| Overview

Announcement Management provides a centralized mechanism for administrators to create, schedule, manage, and distribute announcements across supported 75F ecosystem interfaces.

An announcement can be configured once and delivered to one or more supported surfaces based on its defined scope. This enables administrators to communicate important product, system, maintenance, or operational updates consistently across the ecosystem.

Supported delivery surfaces include:

• Internal Portal
• Facilisight Portal
• Facilisight Mobile App
• Occupant App
• CCU

The announcement scope determines which users, applications, portals, or devices receive the announcement.

| Purpose

The Announcement Management capability addresses the need for a centralized and controlled communication mechanism across the 75F ecosystem.

It enables administrators to:

• Create announcements from a single management interface.
• Target announcements to specific ecosystem surfaces.
• Define when an announcement becomes active and when it expires.
• Include formatted message content and an optional URL.
• Save announcements as drafts before publishing.
• Activate, deactivate, edit, reschedule, or delete announcements.
• Extend an announcement's end time when continued visibility is required.

| Access and Permissions

Announcement Management is accessible through:

Internal Portal → Announcement Management

Only users with the required administrative permissions can create and manage announcements in the Production environment.

Role Permissions

Only authorized roles can create or manage announcements.

| Creating an Announcement

An administrator can create an announcement from the Announcement Management page.

The Create Announcement form requires the following information:

1. Scope
2. Start Date and End Date
3. Start Time and End Time
4. Message
5. Optional Link

The administrator can either create the announcement directly or save it as a draft for later activation.

Scope

Defines the ecosystem surfaces where the announcement is delivered.

Supported scopes include:

• Portals
• Mobile applications
• CCU

The announcement is visible only to users or systems included within the configured scope.

Schedule

The administrator must specify:

• Start date
• End date
• Start time
• End time

The start time determines when the announcement becomes eligible for display, while the end time determines when it expires.

The following scheduling rules apply:

• Dates and times cannot be in the past.
• Start date/time must occur before the end date/time.
• An expired announcement can be extended by changing its end time.

Message

The announcement message is mandatory.

Messages must contain valid HTML text. An optional URL can be included with the message.

Additional message behavior:

• Long messages automatically scroll within the announcement banner.
• Links open in a new browser tab.
• Images and videos are not supported.

| Announcement Lifecycle

An announcement follows a defined lifecycle:

Create → Draft → Activate → Live → Expire

Create

The administrator configures:

• Message
• Optional link
• Scope
• Schedule

Draft

The announcement is saved without being made visible to users.

A draft:

• Is not displayed to users.
• Can be edited.
• Can be activated when ready.

Activate

The administrator activates the announcement.

Once activated, the scheduler evaluates the configured schedule and scope to determine when and where the announcement becomes visible.

Live

When the configured start time is reached, the announcement becomes available on the selected surfaces.

Users within the configured scope can view the announcement.

Expire

At the configured end time, the announcement stops being displayed.

An administrator can extend the end time to make an expired announcement active again.

Administrators can also deactivate or delete an announcement at any point in its lifecycle.

| Announcement Delivery

Internal Portal

The Internal Portal provides access to Announcement Management.

Administrators can:

• Create announcements.
• Edit announcements.
• Activate announcements.
• Deactivate announcements.
• Delete announcements.
• Modify scope and schedule.

The announcement banner is also displayed within the portal when applicable.

Facilisight Portal

Announcements are displayed as a banner at the top of the Facilisight Portal.

The banner:

• Appears after login or a hard refresh.
• Supports long text through automatic scrolling.
• Can be closed for the current session.

Mobile Applications

Announcements can be delivered to the Facilisight App and Occupant App when the corresponding mobile scope is selected.

The mobile experience provides:

• The same announcement message across supported apps.
• Banner display after login or hard refresh.
• Automatic scrolling for long messages.
• Optional links that open in a new tab.
• Session-level dismissal when the user closes the banner.

The Occupant App displays an announcement only when the announcement scope includes the applicable audience.

| CCU Announcement Behaviour

Announcements can also be delivered to the CCU when CCU is included in the announcement scope.

Requirements

• CCU must use version 5.6.x or later.
• Only one active announcement is displayed on a CCU at a time.
• Announcement data refreshes during the 24-hour/data synchronization cycle.

Multiple Announcements

The CCU supports only one displayed announcement at a time.

When multiple announcements are applicable, the last updated announcement is displayed.

| Managing Existing Announcements

Administrators can manage announcements from the Announcement Management list.

Available management operations include:

• Edit
• Activate
• Deactivate
• Delete
• Change Scope
• Change Schedule
• Extend End Time

Editing an announcement allows the administrator to modify the message, optional link, scope, or schedule.

After an announcement is updated, users see the updated content on their next login or hard refresh, depending on the applicable surface.

| Scheduler Behavior

The announcement scheduler evaluates active announcements against their configured schedules.

The current scheduler interval is 15 minutes. This interval is configurable and can be changed if required.

As a result, there may be a delay between the configured activation time and the scheduler processing the announcement.

| Functional Rules and Limitations

These rules define the current supported behaviour of Announcement Management.

| User Experience Flow

Administrator Flow

Internal Portal
↓
Announcement Management
↓
Create Announcement
↓
Configure Scope
↓
Configure Schedule
↓
Enter Message / Optional Link
↓
Save as Draft or Activate
↓
Scheduler Evaluates Announcement
↓
Announcement Becomes Live
↓
Users See Announcement on Applicable Surface
↓
Announcement Expires or Is Deactivated

| Example Use Cases

Planned Maintenance

An administrator can schedule an announcement informing users about planned system maintenance.

The announcement can be targeted to the required portals, applications, or CCUs and automatically expire when the maintenance window ends.

Product or Feature Updates

A new feature or capability can be communicated through a centrally managed announcement without requiring separate messages to be created for each ecosystem surface.

Operational Notifications

Administrators can communicate important operational information to users within a defined scope and schedule.

Time-Bound Notifications

Announcements can be configured with a specific start and end time, allowing temporary messages to be automatically removed after the defined period.

| Administration Best Practices

For effective announcement management:

• Use concise and actionable message content.
• Define the scope carefully to avoid exposing information to unintended users.
• Schedule announcements in advance where possible.
• Validate the start and end times before activation.
• Use drafts when content requires review before publication.
• Deactivate announcements that should no longer be visible.
• Extend the end time when an announcement needs to remain active beyond its original schedule.
• Avoid relying on images or videos because these content types are not supported.