EN
“Ding!”
An Alert just came in.
But when you open it...
What is the Alert about?
Where did it happen?
When did it happen?
How urgently does it need to be reviewed?
And who is responsible for what happens next?
If a Notification arrives very quickly but the recipient still has to spend time searching for all these answers, that notification may not be fully supporting the Workflow.
That is why Clong-1 Ai believes:
A good notification should do more than simply say, “Something happened.”
It should help the team understand:
“There is something here that may need further review.”
For Canal One, system speed is not measured only by how quickly AI can Detect something.
It is also about how quickly important information can reach the relevant people, at the right time, in a format that is easy to understand.
When we hear Real-Time Notification, speed may be the first thing that comes to mind.
AI Detects something.
The system sends an Alert.
A Notification appears.
Done.
But in a real Workflow, delivery speed is only one part of the process.
Even if an Alert arrives almost immediately, imagine that the message simply says:
“Warning!”
With no Location.
No Event Type.
No relevant information.
And no indication of what should happen next.
The recipient may still need to open other systems to find the answers.
A Notification that truly helps people work should therefore reduce the distance between:
“An Event has occurred”
and
“The relevant person understands what happened and can begin the Review.”
For Clong-1 Ai, a good Real-Time Notification should combine:
Speed + Relevance + Easy-to-Understand Context
not speed alone.
When an Event occurs, people do not necessarily need to see every piece of Data in the system immediately.
What the team may need first is basic information that helps them understand the situation more quickly.
For example:
What Event occurred?
At which Location?
When did it happen?
Which system or AI Detection identified it?
Is there relevant CCTV footage or Sensor data?
And who should Review the Event next?
This information can transform a Notification from:
“There’s an Alert!”
into:
“An Event matching the defined conditions has been detected here, and this is the relevant information for further review.”
Clong-1 Ai does not want an Alert to be the final answer.
It should be a useful starting point for Human Review.
Imagine a Security Event occurs,
but the Notification is sent to someone who is not responsible for it.
Or Environment data triggers an Alert,
but the Alert appears on the screen of a team that does not manage that area.
No matter how quickly the system sends the information, the Workflow may still not be effective.
So the important question is not only:
“Can the system send an Alert?”
We also need to ask:
“Who should the system alert?”
ASAP, or All Smart AI Platform, therefore considers Notification as part of the overall Workflow.
Different types of Events may involve different people.
A Safety Alert may need to reach one team.
A Security Event may need to reach another.
Environment Monitoring may involve another group of responsible users.
Notification Design should therefore consider Event, Context, User, and Workflow
to help relevant information reach the relevant people more appropriately.
Sometimes we may think:
“If it’s important, just send it to everyone so nobody misses it.”
That may sound safer.
But if every Event becomes an Alert,
and every Alert is sent to everyone,
it will not take long before Notifications begin filling the screen.
Ding for this.
Ding for that.
Ding again.
Eventually, a genuinely important Alert may become just another Notification mixed into a long stream of messages.
This is the challenge of Alert Overload.
A good notification system should therefore not be measured only by:
“How many Alerts did the system send today?”
A better question is:
“Was the Alert relevant to the recipient, and did it help them continue their work?”
Because the goal is not to generate the largest number of Notifications.
The goal is to help Relevant Information reach Relevant People.
Clong-1 Ai would like to emphasize this point:
Detection ≠ Final Decision
When AI Detection identifies something that matches predefined conditions, it means the system has found information that may need further review.
It does not mean AI has already determined the full context of the situation.
The Workflow may therefore look like this:
Monitor → Detect → Analyze → Alert → Human Review → Decide → Respond
AI helps Monitor, Analyze, and Detect.
ASAP helps Connect and Organize information.
Real-Time Notification helps deliver the Alert.
And people continue to Review, Decide & Respond.
A Notification therefore acts as a bridge between:
AI Detection
and
Human Decision.
If that bridge delivers incomplete information, is difficult to understand, or sends information to the wrong person, the overall Workflow may still be inefficient even if the AI performs well.
That is why Notification Design is part of Human-Centric AI.
With AI Video Analytics, a system may help Detect Events from CCTV according to predefined Use Cases.
For example:
Intruder Detection
PPE Safety
Smoke and Fire AI Detection
Suspicious Object Detection
License Plate Recognition
or other Use Cases appropriate for the site.
Now compare two Notifications.
The first simply says:
“Intruder Detected.”
Another helps the team see when the Event was Detected, where it happened, which camera identified it, and whether there is relevant footage or information available for further Review.
The second example does not automatically mean the AI itself is smarter.
It means the Information Context has been designed around the person who needs to use that information.
For Clong-1 Ai, Notification should therefore not be separated from User Experience.
Because what matters is not only:
what the system knows
but also:
how the system communicates what it knows in a way people can understand.
Notifications do not come only from CCTV or AI Video Analytics.
ASAP can connect with Data and Intelligent Devices according to the appropriate Solution and Infrastructure.
For Environment use cases, this may include information from:
Water Level Monitoring
Air Quality Monitoring
Temperature Monitoring
or other relevant Sensors.
Imagine a Sensor detects a value exceeding a predefined Threshold.
Simply sending:
“Threshold Exceeded”
may not give the recipient enough information to understand the situation.
But if the Notification can appropriately connect relevant information such as Location, Sensor, time, and the value that triggered the Alert,
the team has a clearer starting point for Review.
The principle is the same as AI Detection.
An Alert is not a Final Decision.
It is a way of saying:
“There is some information here that matches the defined conditions. Let’s take a closer look.”
People do not spend their entire working day looking at the same screen.
Some work in a Control Room.
Some work in the field.
Some patrol different areas.
Some may need to receive information through a Mobile Device.
And certain Events may require an audible or visual signal in the area.
ASAP therefore supports the concept of Real-Time Notification through multiple channels and devices depending on the Solution, including LINE Official Account, Android / iOS Applications, Direct Message, Portable Radio, Wired Telephone, Strobe Light / Siren, and API.
But supporting multiple channels does not mean every Alert should be sent through every channel at the same time.
What matters is designing around:
People + Event + Urgency + Workflow
because the right channel for a Security Control Room may not be the same as the right channel for a field team.
A good Notification should appear where people can actually receive it and take the appropriate next action.
If a Notification tells someone that an Event occurred, but the recipient then has to leave the Notification, search through CCTV, open another Dashboard, and find Sensor data on another Platform,
the team is still spending time connecting the information manually.
This is where Smart Integration and Unified Monitoring come into play.
ASAP is designed to help connect People, Data, and Intelligent Devices.
When relevant systems can be appropriately Integrated, Events and supporting information can be connected within a Context that makes further Review easier for the team.
The goal is not to squeeze every Data Source into a single Notification.
That could simply create another form of Information Overload.
Instead, the goal is to select:
Relevant Data
for the
Relevant Event
and deliver it to the
Relevant Person.
That is Smart Integration from a notification perspective.
There is an important difference between supporting a decision and making the decision for someone.
Clong-1 Ai is here to support the first.
When a Notification contains relevant information, is easy to understand, and reaches the appropriate person, the team can use that information to Review the situation and make decisions according to its SOP.
AI may help say:
“Something matching the defined conditions has been detected.”
ASAP may help bring the Context together.
Notification helps deliver that information to the team.
But people still determine:
What actually happened?
Does action need to be taken?
What action is appropriate?
And who should be responsible for the next step?
This approach aligns with Human-Centric AI, AI Governance, and AI Security & Explainability.
Because good technology should enhance what people can do,
not remove people from the decision-making process.
Before designing an Alert, Clong-1 Ai believes the most important question may not be:
“What can the system send?”
It may be:
“What does the recipient need to know to continue their work?”
Security personnel may need one type of information.
The Safety team may need another.
The Environment team may focus on Sensor values and Thresholds.
Management may need a broader overview rather than the details of every Event.
Notification Design should therefore begin with real User Requirements and Workflows.
This is the idea behind Human-Centric Design.
Because a good Notification for one person may not be the right Notification for someone else.
The system should therefore be designed around the context in which it will be used,
rather than sending the same message to everyone simply because it is easier.
For Clong-1 Ai, the future of Smart Notification is not about how many millions of Notifications a system can send.
It is about what happens when important information appears.
Can the system help Detect it?
Can it Connect the relevant Context?
Can it Alert the appropriate people?
And once they receive it,
can they understand it quickly enough to begin Reviewing and Responding?
This is why Canal One sees Notification as part of an Intelligent System.
It is not simply a Pop-up that appears after AI Detects something.
It is part of a connected process:
Data → AI Detection → Context → Alert → Human Review → Decision → Response
through ASAP Platform, Smart Integration, Unified Monitoring, and Real-Time Notification.
Helping make People Safer, Businesses Smarter, and Environments More Responsive
through technology that is Ethical, Seamless, and Human-First.
And if you ask Clong-1 Ai:
“What should a good notification be like?”
Clong-1 Ai would say...
“It doesn’t need to be the Alert that says the most. It should be the Alert that helps the relevant people quickly understand what happened, what information they should review next, and be better prepared to make a timely decision according to their Workflow.”
What about you?
If you could choose, what would you want a Notification to tell you first?
Would you want to see the Event, Location, time, CCTV footage, Sensor Data, priority level, or something else that would make your team’s work easier?
Clong-1 Ai would love to hear from you.
Because a good Smart Notification should not begin with what the system wants to say — it should begin with what people need to know.
We’re ready to help your team take the next step in safety, sustainability, and smart operations.
