Document Chunks
Chunk 0
# THRIVE360 Web Application – Functional Overview
> This document provides a high-level, non-technical description of how end-users interact with the THRIVE360 portal. It is intended to feed the on-site AI Chatbot so that visitors can ask questions such as “Where do I create a ticket?”, “What does the *Coverage Data* page show?”, or “How do I change the status of a ticket?”.
---
## 1. Getting Started & Navigation
Chunk 1
---
## 1. Getting Started & Navigation
1. **Login** – Most pages are available only after signing-in with Azure AD B2C. If a user visits a protected route while not authenticated, the application automatically redirects them to the Microsoft sign-in page.
2. **Top Bar** – Once signed-in, every page shows a blue top-bar that contains the main navigation menu (hamburger icon on smaller screens). Selecting a menu item loads the corresponding page without refreshing the browser.
3. **Country Selection** – At first login THRIVE360 may ask the user to choose their country (and, for UNICEF/WHO/Gavi staff, an *access level* – country / regional / global). The chosen country drives data filters across the portal.
4. **Support Chatbot** – A floating chat icon is available at the bottom-right of every page; it opens the THRIVE360 AI assistant that can answer questions, search documents, and file support tickets.
---
## 2. Page-by-Page Overview
Chunk 2
| Page | Purpose & Key Features |
|------|-----------------------|
| **Stock Performance** (`/stock-performance`) | Interactive Power BI dashboard summarising vaccine stock levels, stock-out trends, and supply chain indicators. Visible immediately after login. |
| **Data Warehouse** (`/data-warehouse`) | Embedded Swagger UI exposing the public THRIVE360 API. Users can explore endpoints and sample responses directly in the browser. |
| **AI / ML Models** (`/ai-ml-models`) | Demonstrates predictive models (e.g., *stock-out risk*). Users can adjust parameters and run live inferences powered by Hugging Face. |
| **Tracking System** (`/tracking`) | Map-based tracker that displays cold-chain equipment locations and real-time temperature data (RTMDs). |
| **Ticketing System** (`/ticketing-system`) | End-to-end issue management for country offices and global support teams. Detailed description in section 3. |
Chunk 3
| **Ticketing System** (`/ticketing-system`) | End-to-end issue management for country offices and global support teams. Detailed description in section 3. |
| **Ticket Details** (`/ticket/:id`) | Modal view of an individual ticket, including comments, attachments, and status history. |
| **Carbon Footprint** (`/carbon-footprint`) | Dashboard highlighting carbon emissions linked to cold-chain operations. |
| **Coverage Data** (`/coverage-data`) | Power BI reports on immunisation coverage at national & sub-national levels. |
| **Gaps** (`/gaps`) | Analytics revealing gaps in cold-chain capacity and resource allocation. |
| **Inventories** (`/inventories`) | List of cold-chain equipment and solar installation inventories. |
| **Temperature RTMDs** (`/temperature-rtmd`) | Real-time temperature monitoring for vaccine storage devices equipped with RTMD sensors. |
| **FSP4All / FSP4All Forecasting** | Modules related to the *Frontline Supply Planning* initiative and demand forecasting. |
Chunk 4
| **FSP4All / FSP4All Forecasting** | Modules related to the *Frontline Supply Planning* initiative and demand forecasting. |
| **DRIVE** (`/drive`) | Data repository for the *DRIVE* study (Delivery Resource Investment & Vaccine Efficiency). |
| **SCIP** (`/scip`) | Tools that support the Supply Chain Improvement Plan (SCIP). |
| **EVMA** (`/evma`) | Visualisation of *Effective Vaccine Management* assessment scores. |
| **NLWG Maturity** (`/nlwg-maturity`) | Self-assessment tool for National Logistics Working Group maturity levels. |
| **Solarization** (`/solarization`) | Dashboard following solarisation projects and off-grid device performance. |
| **Waste Management** (`/waste-management`) | Reports on safe disposal of medical and cold-chain waste. |
| **New Vaccine Introduction** (`/new-vaccine-intro`) | Gantt-style roadmap & resources for upcoming vaccine introductions. |
| **Outbreaks** (`/outbreaks`) | Situational awareness board for vaccine-preventable disease outbreaks. |
Chunk 5
| **Outbreaks** (`/outbreaks`) | Situational awareness board for vaccine-preventable disease outbreaks. |
| **Admin** (`/admin`) | Restricted to administrators. Tabs for user approval, usage statistics, error logs (Sentry), chatbot documents, email templates, and ticket oversight. |
| **Guest Ticket Page** (`/public/…` or `/guest/…`) | Read-only access to a specific ticket for external partners via a secure token link included in email notifications. Allows commenting & attachment upload without requiring login. |
Chunk 6
*(Pages not listed above follow similar patterns – data visualisations or forms tailored to a specific programme area.)*
---
## 3. Ticketing System Functionalities
The Ticketing System enables field staff to report cold-chain issues and track their resolution through a structured workflow.
### 3.1 Key Concepts
Chunk 7
---
## 3. Ticketing System Functionalities
The Ticketing System enables field staff to report cold-chain issues and track their resolution through a structured workflow.
### 3.1 Key Concepts
• **Ticket** – A record describing one operational issue (e.g., fridge failure, vaccine stock-out, data discrepancy).
• **Status** – Lifecycle stages: **Open → In Progress → Pending Approval → Implementing → Verification → Resolved → Closed**.
• **Priority** – Impact level: *Critical · High · Medium · Low* (colour-coded throughout the UI).
• **Supply-Chain Level** – Where the incident occurred (*Central · Subnational · Regional · Local*).
• **Roles & Access**
– *Country Office* users can create tickets for their country and update them until resolution.
– *Administrators / Global Support* can view and edit all tickets, re-assign, and change statuses.
– External partners receive a **guest link** allowing them to view & comment on a single ticket without an account.
Chunk 8
### 3.2 Creating a Ticket
1. Navigate to **Ticketing System** and press **Create New Ticket**.
2. Fill in the form:
• Title (short summary)
• Country, Supply-Chain Level, Store (auto-search list)
• Optional IDs (THRIVE ID, LMS ID, Parent Store)
• Antigen(s) affected (multi-select)
• Priority
• Rich-text Description (supports images & links)
• Root Cause (dropdown)
• Attachments (drag-and-drop or browse – multiple files allowed)
3. Submit – the ticket receives a numeric ID and notification emails are sent to assignee(s) and the creator.
### 3.3 Viewing & Filtering Tickets
The main table supports:
• Search by Title, ID, or Store
• Filters for **Status**, **Priority**, and (if you have multi-country access) **Country**
• Column sorting & responsive layout
• Badges show Status, Priority, and Supply-Chain Level colours at-a-glance
### 3.4 Ticket Details & Collaboration
Chunk 9
### 3.4 Ticket Details & Collaboration
Clicking a table row opens the **Ticket Detail** modal:
• Full metadata on the left, including timestamps, assignee, and device/location context
• Discussion thread with rich-text comments and inline attachments
• Status dropdown (visible only to authorised users) to advance the workflow
• External collaborators can post comments via the guest view; their messages are labelled “external”
### 3.5 Notifications
Emails are triggered on key events (creation, assignment, status change, new comment). Each email contains **both** a secure guest link and an internal link so that everyone can follow progress.
### 3.6 Administration
Admins may:
• Bulk-edit tickets under **Admin → Ticket Admin**
• Manage email templates used for notifications
• Audit ticket activity in the **Logs** and **Chatbot Logs** tabs
---
## 4. Asking the Chatbot
Chunk 10
---
## 4. Asking the Chatbot
When a user asks a question, match it against the information in this document. For example:
• “How can I raise an issue?” → Direct them to *Ticketing System → Create New Ticket*.
• “What does *Stock Performance* show?” → Explain the Power BI report.
• “Where do I check API endpoints?” → Point to *Data Warehouse*.
If the answer refers to a navigation step, explicitly mention the page name and any buttons or tabs to click.
---
*Last updated: {{DATE}}*