In product development

SALPION
SALPION

Monitor facility and road CCTV, verify decisions, and record actions.

We review existing CCTV and VMS footage alongside risk candidates, comparing object detection with independent AI evidence. We are developing a process that routes uncertain results to operators and links incidents, actions, and records.

There is no need to replace your CCTV. Live integration and analysis scope for facility and road video depend on authorization and site conditions.

VERIFY → RESPOND → LEARN
  1. 01Existing CCTV / VMS
  2. 02Independent AI verification · RIAN Reliability
  3. 03Facility safety incidents · Operator response
  4. 04History and reports · Safety Intelligence

We are expanding road CCTV monitoring
and candidate risk verification.

We tested multi-channel playback of public Korean road CCTV and review of recorded footage in a limited environment. Model evaluation and verification workflows for stopped vehicles, suspected collisions, road obstacles, and pedestrians remain under development.

Commercial display, storage, or AI analysis of live road CCTV requires source-provider permission and field verification. Testing video playback must not be presented as validated risk detection accuracy.

Alarms can be generated,
but people must verify the response.

Even if CCTV AI flags a risk candidate, operators still need to decide whether it is a false alarm and whether action is needed. RIAN includes this review in the product workflow.

OBJECT DETECTIONConceptual example
  • Person detected
  • Backpack detected
VLMConceptual example
  • No person detected
  • Insufficient evidence

Two AI systems can reach different conclusions from the same video.

RIAN does not simply accept existing AI results
and automatically confirm incidents.

Independent AI rechecks the original footage and event data, separating confirmed incidents from those requiring further review. Uncertain results are escalated for re-verification, deferred judgment, or operator review.

Verify alerts
and turn them into actionable incidents.

Keep existing CCTV and VMS while connecting risk candidates, verification, responses, and records in one workflow.

  1. 01Existing CCTV / VMSPreserve existing monitoring and video analytics
  2. 02Safety risk candidatesReceive candidates from existing AI and events
  3. 03Independent AI verificationRecheck original video and events separately
  4. 04RIAN ReliabilityAgreement, disagreement, insufficient evidence, or recheck
  5. 05Facility safety incidentSeparate actionable incidents from those needing review
  6. 06Operator review and actionAssignment, verification, action, evidence, approval
  7. 07History and reportsPer-incident action history and outcome reports
  8. 08Safety IntelligenceUse operational records for future safety decisions

Uncertain AI judgments do not trigger automatic action.

From verification to field response

Confirmed incidents follow a workflow covering assignment, field review, corrective action, evidence, manager approval, and incident reports. Every incident retains a record of who checked it and what was done.

Integrations with CCTV, video analytics, and external notification channels require scoping based on each organization's environment.

  • Safety event intake
  • Assign owner
  • Field verification
  • Action and evidence
  • Manager approval
  • Incident and results reports
  • Processing history and audit logs
  • Operations overview

No replacement needed.

Add verification and operations layers above existing CCTV/VMS, choosing connections appropriate to site security policies.

Recommended

RIAN Edge Connector

Keep CCTV/VMS connection details within the customer network and send only necessary events and video through encrypted connections.

Review for each environment

Existing VMS Connector

We review supported events, APIs, and integrations in the current VMS to preserve existing monitoring wherever possible.

Pre-validation

Recorded video analysis

Before live connection, available recorded footage can be used to test the Safety Event and verification flow.

Connection security principles

We never request RTSP passwords, camera passwords, API keys, or other CCTV credentials in the trial application. Actual connection details are handled later through secure onboarding after approval.

Actual integration and delivery scope depend on site network, VMS, and security policies.

We have implemented monitoring and verification workflows
and are assessing the scope of field deployment.

Confirmed during development and testing

  • CCTV monitoring and incident management UI
  • Object detection and independent VLM checks using public test footage
  • Disagreement, insufficient-evidence judgment, and operator-review routing
  • Trial flow for incident review, action, and history
  • Limited playback tests of Korean road CCTV
  • Related patent applications

Remaining validation before field deployment

  • Rights to use, analyze, and store video
  • Long-duration playback stability and fault recovery
  • Road risk model performance and false-positive evaluation
  • Site-specific CCTV/VMS integration
  • Notification and external delivery channel validation
  • Operator approvals and audit records
  • Approved field trial and outcome reporting

RIAN develops core IP and verification logic in-house, combining product UI, integration, and testing with specialist delivery teams.

Configure the types of risk each site needs
as a Safety Pack.

These are candidates for evaluation, not all fully validated functions. We distinguish model E2E and field-verified capabilities from features still preparing for integration or validation. Actual trial scope is set after review.

  • Restricted-area entry
  • Worker collapse
  • Safety helmet / vest
  • Pedestrian–forklift proximity
  • Smoke / fire
  • Emergency exit / passage obstruction
  • Loitering / crowding
  • Equipment hazard zone
MANUFACTURING

Manufacturing

  • PPE
  • Worker collapse
  • Forklift–pedestrian proximity
  • Hazard zone
  • Smoke and fire
  • Equipment hazards
LOGISTICS

Logistics and warehousing

  • Forklift proximity
  • PPE
  • Passage obstruction
  • Emergency exit
  • Worker collapse
  • Fire
CONSTRUCTION

Construction

  • Safety helmet
  • Safety vest
  • Work at height
  • Open Edge
  • Suspended load
  • Worker–vehicle interactions
FACILITY

Facility management

  • Restricted access
  • Worker collapse
  • Fire and smoke
  • Blocked emergency exit
  • Loitering
PUBLIC

Public facilities

  • Restricted area
  • Crowding
  • Worker collapse
  • Loitering
  • Unattended objects

Safety Packs are templates to illustrate potential offerings. Some features remain under validation. Applicability and test methods must be agreed separately according to the site, camera, VMS, and security conditions.

Connect detection events and real responses
so that they are not separated.

Without a clear path from site review to corrective action and reporting, risk events are difficult to preserve as operational records.

  • 01

    Even when CCTV detects risks, responsible staff still handle actions manually.

  • 02

    Detected events and real corrective actions are managed separately.

  • 03

    It is hard to track whether an owner has reviewed an event or if incidents remain open.

  • 04

    Site photos and action notes are scattered across chats and documents.

  • 05

    Incident, daily, and monthly reports take time to prepare.

  • 06

    Audit history of who checked and acted, and when, is hard to collect.

From handling a safety incident
through reporting it

A conceptual process for pilot configuration, not an actual operational screen.

  1. 01Video and site events
  2. 02Risk detection
  3. 03Safety event creation
  4. 04Owner assignment
  5. 05Field verification
  6. 06Action and evidence
  7. 07Manager approval
  8. 08Incident report
  9. 09Operations statistics

Use your company's CCTV
for a 30-day field trial.

This is not a free service that starts immediately upon sign-up. RIAN must review and approve the organization, site, CCTV usage rights, and integration conditions for a B2B field trial.

  1. 01
    Trial application

    Tell us about your company, work site, CCTV/VMS, and key safety concerns.

  2. 02
    RIAN review and approval

    We check permissions, networks, video supply conditions, and Safety Pack scope.

  3. 03
    Connection and onboarding

    Connect CCTV/VMS through an approved method and configure safety policies.

  4. 04
    Activate the trial

    Customers activate the trial after connecting the first approved camera.

  5. 05
    30-day field trial

    Use incident verification, review, action, and history workflows on site.

  6. 06
    Review results and next steps

    Review operating results, then discuss a separate quote and contract for paid conversion or end the trial.

When the 30 days start

Not from the application date: The first approved camera connection plus the customer's trial activationstarts the 30 days. Installation preparation is separate from the usage period.

Trial limits

Camera counts, sites, Safety Packs, VLM validation volume, and video retention are defined upon review of site needs and operating costs.

Paid conversion

There is no automatic card payment. Paid use requires a separate quotation and contract after trial review.

Not simply detecting video,
but automating operations.

  • 01

    Connect detection to practical response procedures

  • 02

    Review opportunities to use existing CCTV or supplied video

  • 03

    Combine operator review, action, approval, and evidence

  • 04

    Support incident reporting and process history

  • 05

    Configure Workflow to site operating procedures

  • 06

    Agree risk types and KPIs after assessing the site

Workflow engine for facility safety response

RIAN Workflow is the core operations platform for safety event intake, owner assignment, site action, review and approval, processing history, and outcome reports.

About the Workflow engine →

Not just a demo:
try it with your own company's CCTV.

First review the site and CCTV/VMS environment, then agree on the approved 30-day trial scope.