GT-AiVision Incident Management

GT-AiVision Incident Management

Add a Structured Incident Workflow to AI Monitoring Services

Help customers turn detection events, Virtual Patrol findings, and manual reports into assigned, investigated, documented, and resolved incidents—with evidence and activity retained in one operational record.

Why it matters

Detection is only the beginning of the response process

An alert or patrol finding still needs review, ownership, evidence, action, and closure. When those steps are handled through messages, spreadsheets, and separate files, the operational record becomes fragmented.

Incident Management enables partners to offer a connected workflow from AI-generated evidence to accountable resolution and reporting.

From isolated alert to operational record

  • Give each incident an owner and status.
  • Keep evidence, comments, and actions together.
  • Track progress through investigation and resolution.
  • Review open, closed, and historical activity.
  • Support management reporting and service review.

Incident sources

Connect automated monitoring with human investigation

Incidents can begin from platform events or human reports, allowing partners to use one workflow across multiple monitoring services.

Live Monitoring

Detection event

Create an incident from a configured real-time event and its supporting snapshot.

Virtual Patrol

Patrol finding

Escalate a scheduled patrol verdict or exception for investigation.

Operator

Manual report

Record an incident identified by a guard, supervisor, operator, or service team.

Customer input

Upload and context

Add customer or operator images, documents, and relevant supporting information.

Incident lifecycle

Follow every incident from creation to review

1

Create

Start from a detection event, patrol finding, or manual report.

2

Classify and Assign

Record incident details, status, ownership, priority, and context.

3

Investigate

Add notes, comments, documents, images, and relevant AI analysis data.

4

Track Actions

Record follow-up actions, responsibilities, and progress.

5

Resolve

Document the resolution and close the incident when completion is confirmed.

6

Review and Report

Use dashboards, history, timelines, and reports to review activity.

Escalation rules, service levels, and response commitments are defined by the customer or partner service model; they are not implied by the platform alone.

Core capabilities

Keep ownership, evidence, actions, and history together

Partners can demonstrate a complete operational layer rather than stopping at the alert. The incident record provides a shared context for operators, supervisors, and managers.

  • Incident creation and editing.
  • Assignment and status workflow.
  • Notes and comment threads.
  • Action tracking.
  • Event and patrol links.
  • Documents and images.
  • Relevant AI analysis JSON.
  • Timeline and history.
  • Dashboard and status overview.
  • Filtering and reporting.

Evidence in context

Show why an incident was created and how it was resolved

Detection snapshots, patrol findings, uploaded images, documents, comments, and actions can be brought together within the incident record.

This helps operators and managers review what was observed, what was investigated, who took action, and how the incident was closed.

The platform supports record organisation. It does not independently determine legal responsibility, compliance status, or the correct operational response.

Evidence-to-resolution view

Source evidence

Detection snapshot, patrol result, manual report, or uploaded material.

Investigation context

Comments, documents, notes, and AI analysis where relevant.

Action history

Recorded follow-up steps and ownership.

Resolution record

Closure details, timeline, and retained history.

Dashboard and reporting

Give operators and managers a shared view of incident activity

Operational overview

  • Open and closed incident overview.
  • Status and ownership review.
  • Incident list, filtering, and details.

Investigation record

  • Evidence and document access.
  • Actions and comment review.
  • Incident timeline and history.

Management review

  • Incident activity reporting.
  • Workflow and status review.
  • Customer-specific formats discussed during solution design.

Partner service opportunity

Expand beyond installation and event notification

Incident Management helps partners present a complete detection-to-resolution platform story and build structured services around review, escalation, reporting, and customer-specific workflows.

View the Partner Program

Potential partner services

  • Managed monitoring and incident review.
  • Customer-specific categories and processes.
  • Reporting and service-review meetings.
  • Integration and customisation projects.
  • Operational workflows for security, facilities, and smart buildings.

No specific service margin or operational improvement is guaranteed.

Platform architecture

Designed as a separable incident service

Incident Management is provided through the GT-AiVision FastAPI backend and uses an isolated incident_mgmt database for incidents, documents, comments, and actions.

This separation can support a standalone service architecture where required and technically scoped. API-token support is available for external integrations.

Specific endpoints, integration scope, authentication, data ownership, and support responsibilities must be confirmed during technical design.

Documented platform controls

  • JWT-based authentication.
  • Roles and permissions.
  • API tokens.
  • User administration.
  • Password reset through email.
  • Configurable retention for relevant platform data.

Access and deployment controls

Define security and retention responsibilities for each project

HTTPS, VPN access, firewall rules, network segmentation, backups, customer retention policies, and external access must be designed and assigned during solution implementation.

GT-AiVision does not currently claim a cybersecurity certification.

Project design decisions

  • Users, roles, and operational ownership.
  • Network and remote-access controls.
  • Backup and recovery responsibilities.
  • Data and attachment retention.
  • Integration authentication and audit needs.
  • Customer-specific compliance requirements.

Partner delivery model

Define the workflow locally with Grep Tech product support

Partners can define the customer workflow, support first-line operation, coordinate users and incident categories, and package review and reporting services.

Grep Tech provides product training, platform configuration guidance, software support, and L2/L3 technical escalation.

Additional scope may be required for

  • Customer-specific workflow changes.
  • External system integrations.
  • Custom reports and fields.
  • Special authentication or network controls.
  • Data migration and retention requirements.

Partner demonstration

Show customers what happens after an AI event is detected

Follow a detection event from snapshot and review through incident creation, investigation, action tracking, resolution, and reporting.