Language: 繁體中文

AI-enabled central operations platform

Every signal becomes a response someone owns, with the evidence kept.

CoreX connects approved cameras, sensors, building systems and forms, adds context, decides who responds and keeps the evidence. Built and run by Nexus GP, deployed cloud, hybrid or private.

Open the CoreX product site Plan a lighthouse evaluation

Built by Nexus. Schematic views. The product itself is at corex.nexusgp.co.

CoreX Alert Centre summary strip with active, critical and total counts; the alert rows below fade into abstract bars
Alert Centre, demonstration data
One operating record Illustrative record
  1. Source Camera 07 saw movement in a restricted zone at 02:14
  2. Context Loading bay B, after-hours rule, no booking on file
  3. Owner Facilities duty team, response due in 20 minutes
  4. Evidence Clip and site photo attached for review
  5. Closure Verified by the duty officer and closed at 02:31

The operating problem

Signals arrive from everywhere. Ownership arrives from nowhere.

Cameras, sensors, building systems and forms each raise their own events. Without one shared record, the exception is seen but not owned, and the response cannot be shown afterwards.

  • Disconnected signals

    Video, IoT, BMS, network and form events live in separate consoles with no common context.

  • No named owner

    A dashboard shows the exception; nobody is assigned, no due time is set and escalation is informal.

  • Evidence that cannot be shown

    Actions, clips and photos are not kept with the case, so audit and management review start from memory.

  • Systems you must keep

    Existing VMS, BMS, PLC and access controls still work and must stay in control of their own function.

How CoreX works

One governed operating loop, from signal to closure.

CoreX is more than a dashboard. It connects approved sources, adds context, decides severity and routing, turns the alert into an owned record and keeps the history for audit. The views here are schematic; the product itself is at corex.nexusgp.co.

  • Source
  • Context
  • Owner
  • Due time
  • Evidence
  • Human verification
  • Closure

The operating loop

  1. Connect

    Cameras, sensors, meters, building systems, forms and APIs feed one shared, reusable data model.

  2. Understand

    Each signal is placed against its asset, zone, rule and time, on a map or digital twin when that helps.

  3. Decide

    Rules set severity, routing and cooldown. A quick test shows what a rule would do before it goes live.

  4. Act

    The alert becomes an owned record: acknowledge, assign, comment, attach evidence and resolve.

  5. Govern

    Roles, project-scoped permissions and activity history keep every decision traceable for audit and reports.

  • More than a dashboard

    A dashboard shows the exception. CoreX creates the accountable response and keeps its history.

  • Human in the loop

    People verify events, approve changes and close cases. Rules route the work; they do not replace judgement.

  • Audit by default

    One alert record holds owner, status, comments and history; configured workflows add due time, evidence, closure.

Open the CoreX product site

Platform modules

Six modules on one shared foundation.

All six modules share the same projects, permissions, data models and saved application versions, so a rule written for a camera and a rule written for a meter land in the same alert record. Start with the modules the first job needs; the rest are already there.

  • CCTV Hub

    Cameras, NVRs and encoders from mixed brands: RTSP pull, RTMP push and browser viewing in one registry.

    Camera registry and analytics profiles

  • IoT Hub

    Sensors, meters and equipment data over HTTPS JSON or an MQTT bridge, mapped by reusable device types.

    Device types and field mapping

  • Integration

    Read-only BMS edge logger, REST adapters and HTTP webhooks today; door events and forms as scoped integration work.

    BACnet/IP, Modbus, OPC, API

  • AI Analytics

    A catalogue of 59 video analytics use cases in five families, validated on the real scene before approval.

    11 standard, 4 configurable, 44 project-specific

  • Rules and Alerts

    Condition, severity, cooldown, recipients and response tracking, with a dry-run test before use.

    In-app, email, messaging, webhook

  • Apps and Dashboards

    KPI values, charts, maps and camera views in an editor with saved revisions and AI-assisted changes.

    Role templates and project-scoped permissions

Connects to approved streams and APIs from common vendors, for example Hikvision, Dahua, Uniview and Milesight cameras and sensors and Siemens or Daikin building systems, with each model and firmware qualified per project.

Schematic views. The product itself is at corex.nexusgp.co.

AI analytics catalogue

59 video analytics use cases in five families.

The catalogue helps select the analysis for the operating problem. Every selected model is validated on the camera scene with the site team before it goes live; delivery labels describe approach, not universal availability.

59 catalogue use cases

  • 18

    People and safety

    Safety helmet detection, people and footfall counting and other people-centred events.

  • 13

    Access and traffic

    Vehicle detection, illegal parking detection and other access and traffic events.

  • 12

    Fire and facilities

    Smoke and flame detection, waterlogging detection and other facility conditions.

  • 10

    Behaviour and procedures

    Phone use or calling, procedure monitoring and other behaviour checks.

  • 6

    Equipment and quality

    OCR and meter reading, surface defect detection and other equipment checks.

  • 11 · 4 · 44

    Delivery approach

    11 standard, 4 configurable and 44 project-specific. Selection depends on camera, stream and scene.

  • Human approval

    Site setup and improvement

    Set the scene, validate events, approve with the site team. Model updates are optional, staged and reversible.

CoreX airside video intelligence demo: a public reference video of an apron with simulated detection boxes on a crew member and the nose of a parked aircraft
Airside video intelligence demo, public reference video with simulated analytics

How CoreX is layered

From platform foundation to industry application, in five layers.

Read it from the bottom up. Nine hubs sit on one project foundation; a thin band of setup tools configures each hub for a project; solution domains combine hubs into workflows; applications serve industries. Maturity is labelled wherever an item is planned or a concept.

Read from the bottom up, L0 to L3

  1. Industries

    Who uses each application. Government buildings and campuses come first; other markets are adjacent or planned.

    • Government buildings
    • Universities and campuses
    • Retail and commercial facilities
    • Construction and industrial sites
    • Solar farm owners and operators
    • Municipal programmes and smart city
    • Hotels and managed properties
    • Building owners and energy teams

  2. Applications

    Configured for one job and labelled by delivery maturity; planned and concept items are not delivered products.

    • Construction safetyValidated on a live scene (configured demo)
    • Construction progressSaved app, sample data
    • Building securityDemonstration pack
    • Campus operationsDemonstration pack (12 instrumented scenarios)
    • Building condition inspectionWorkflow demonstration, reconstructed case
    • Retail footfall and facilitiesAvailable app with seeded pack, demo data
    • Energy management and savingPlanned application on the IoT foundation
    • Solar farm operationsPlanned application, sample-data design
    • Factory operation and process monitoringConcept

  3. Solution domains

    Each domain combines hubs into one operating workflow: detect, review, respond and keep the evidence.

    • Safety and security
    • Energy
    • Project and progress management
    • Operations and facilities management
    • Process and quality monitoring
    • Inspection and compliance
    • Network operationsPlanned (phase 2)

  4. Setup and integration tools

    How each hub is configured and integrated for a project; the work Nexus and the local partner do together.

      • Video analytics profiles
      • Streaming and media gateway
      CCTV Hub
      • IoT data mapping
      IoT Hub
      • Connectors and edge logger
      Systems integrationIntegration required per project
      • Forms designer
      Forms
      • Twin integration
      Spatial and Digital TwinImplemented with demo mappings
      • Rule editor and notification templates
      Rules and Alerts
      • Dashboard editor
      Reports and Dashboards
      • Assistant knowledge and budgets
      • Model registry and validation
      AI Assistant
      • Network HubPlanned (phase 2)

      Project foundationProjects and team access · solution modules and branding · cloud, hybrid edge or customer hosted

      Platform foundation and hubs

      Nine hubs on one project foundation: projects, team access, solution modules, branding and deployment.

    Planned, concept, future and historical items are labelled as such and are not delivered products.

    Industry applications

    One product core. An application for each industry.

    The loop stays the same; the data, workflow and interface change by industry. Each card lists the applications an industry uses, the solution domains they draw on and the delivery maturity of each one, never a customer outcome.

    • Government buildings

      Facilities, security and IT teams: disconnected cameras, room conditions, plant and response records.

      • Building security Demonstration pack
      • Campus operations Demonstration pack (12 instrumented scenarios)
      • Energy management and saving Planned application on the IoT foundation
      • Safety and security
      • Operations and facilities management
      • Energy
      Digital operations solution

    • Universities and campuses

      Estates, security, IT and sustainability teams: many buildings with separate occupancy, IAQ and incident views.

      • Campus operations Demonstration pack (12 instrumented scenarios)
      • Energy management and saving Planned application on the IoT foundation
      • Operations and facilities management
      • Energy

    • Retail and commercial facilities

      Mall operations, property managers and FM contractors: fragmented footfall, facilities and maintenance follow-up.

      • Retail footfall and facilities Available app with seeded pack, demo data
      • Operations and facilities management

    • Construction and industrial sites

      Contractors, site managers and safety teams: hard-to-review CCTV events and disconnected inspection evidence.

      • Construction safety Validated on a live scene (configured demo)
      • Construction progress Saved app, sample data
      • Factory operation and process monitoring Concept
      • Safety and security
      • Project and progress management
      • Process and quality monitoring
      Construction safety solution

    • Solar farm owners and operators

      Asset owners, O&M contractors and energy investors whose production, weather and maintenance evidence sit apart.

      • Solar farm operations Planned application, sample-data design
      • Energy
      • Operations and facilities management

    • Municipal programmes and smart city

      Programme owners, building owners and assessors: inspection, repair and report evidence scattered across parties.

      • Building condition inspection Workflow demonstration, reconstructed case
      • Inspection and compliance

    • Hotels and managed properties

      Owners, FM operators and engineering leads: fragmented facilities alarms and follow-up. Hospitals: a concept case.

      • Building security Demonstration pack
      • Energy management and saving Planned application on the IoT foundation
      • Safety and security
      • Operations and facilities management
      • Energy

    • Building owners and energy teams

      Owners, FM, energy leads, ESCOs and SIs with fragmented consumption, peak demand and indoor-environment records.

      • Energy management and saving Planned application on the IoT foundation
      • Energy

    • All nine industries and the stack in detail

      The CoreX page adds the historical airside reference and every planned application, each with its maturity label.

    Planned, concept, future and historical items are labelled as such and are not delivered products.

    Deployment

    Deploy where the project requires. Local systems stay in control.

    Fully cloud is the current reference. Hybrid edge can be connected for a project. Private hosting is engineered per project. Capacity, resilience and recovery are qualified by load test for each project, never assumed.

    • Fully cloud

      Current reference. Applications, platform services, storage and analytics run in an agreed cloud region.

      1. Site sources
      2. Managed CoreX cloud
      3. Web and mobile users

    • Hybrid edge and cloud

      Video analytics or device processing stay at the edge; workflow, dashboards and governance run centrally.

      1. Edge analytics or logger
      2. Encrypted outbound link
      3. Cloud control plane

    • Private data centre

      Platform services and data hosted in a customer or integrator managed environment, scoped and validated.

      1. Private site network
      2. Dedicated CoreX stack
      3. Approved internal users

    No rip-and-replace

    Native VMS, BMS, PLC and access controllers keep their authority. CoreX reads approved points only and coordinates the response above them.

    A read-only path from the building to the platform

    1. Field equipment
    2. Local controllers
    3. Existing building system
    4. Approved interface
    5. Read-only edge logger
    6. Encrypted uplink
    7. CoreX

    How to start

    Start with one lighthouse. Then scale.

    You do not need every module or every site on day one. Choose one sector, one sponsor and one operating problem with approved data, then let the evidence decide the next step.

    1. Confirm the inputs

      Camera and NVR details, approved stream or point access, priority events and the people who respond.

    2. Build the operating example

      One connected view, two or three selected events, a response workflow and a scoped integration plan.

    3. Review the evidence

      Useful-alert rate, time to acknowledge and completed follow-up against the agreed examples.

    4. Scale by reuse

      Turn the accepted setup into a repeatable package: templates, roles, rules and training for the next site.

    Built by Nexus

    The company that builds CoreX also runs it.

    Nexus GP develops and controls the CoreX product core, roadmap and releases. That gives you direct access to the team that makes product decisions, and one accountable escalation path.

    Multi-project control plane, schematic view

    • Product ownership

      Nexus controls the product core, release direction and application framework: one roadmap, tested releases.

    • Configure first, engineer second

      Roles, schemas, dashboards and rules are configured first; only what is truly project-specific is engineered.

    • Delivery partners

      A delivery partner leads the customer relationship; a local technical team installs, trains and supports on site.

    • Enablement kit

      Sales story, demo script, user and admin guides, training and an escalation RACI, so delivery is repeatable.

    About Nexus GP

    Next step

    Name the first site and the operating job.

    Tell us the sector, the sponsor, the systems you can approve and the exception that matters most. We will propose one lighthouse scope with the evidence to judge it.