> For the complete documentation index, see [llms.txt](https://about.liferesources.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://about.liferesources.in/cria/ongoing-projects/demand-supply.md).

# Demand-supply

A number of volunteers (product, software, management backgrounds) are trying to build a model to predict how Oxygen demand will shape. When supplies improve, they wish to be able to help agencies distribute to the correct places, logistics issue as you might imagine. There is a model they are trying to build but too many unknown variables/uncertainties.

We are trying to build a model to predict demands on covid relief resources in coming days. Whenever supply side opens up (it will), we need a good way to distribute the supply to fulfil the demand. Here are the resources we should predict demand for: Oxygen cylinders, Oxygen refillers.&#x20;

## Supply-side bot

To get direct updates from suppliers on the availability of resources like medicines, oxygen, hospital beds etc.&#x20;

## Action plan (evolving)

* These predictions can be made at various zoom levels: Country  , States  , Districts  , Ward  , Hospitals / care centers.
* Build what if scenarios based on next few weeks and make recommendations&#x20;

  * What if some districts, state manage to curb covid outbreak&#x20;
  * What if one hospital doesn't have medical staff any more&#x20;
  * What if covid spread increases&#x20;
  * What if +ve diagnosis to hospitalisation ratio changes&#x20;
  * What if lockdown happens partially?&#x20;
  * What if virus transmission rate changes?&#x20;
  * What if quarantine rate changes?&#x20;
  * Impact of vaccination (reducing or increasing) spread.&#x20;

## Immediate goals

* Estimate total Oxygen supply needed for Bangalore based on current data (no forecasting)&#x20;
* Ward / hospital wide distribution of Oxygen when supply is available

## Model

Excel [model ](https://docs.google.com/spreadsheets/d/1tI4j2jnoprMfPn1vg66mN4CEpVv-hFNLR1kX0XMB7ZI/edit#gid=1130088558)made so far

![](https://lh3.googleusercontent.com/DJ-E_2bUNuLDKp5Mt3xea6lFk-LrmNncCYzJL0S4952qu7WBMuq0n1aSCs3LXcOJXa9s_v4jpxNRn0Xw9h_qtWER-bRWoN952P5molsoAz0I9JW1fCqSpOut3qt1kEwq3XSmoEcT)

## Demand data sources

Supply data sources:

## What we need:&#x20;

1. Data Science folks: Relevant forecasting/demand prediction experience could be immensely valuable. We can share whatever data points we have. But most people in this sub probably already know what this entails.

Team

Viksit Gaur\
Padmini Ray Murray\
Sumit Datta - [Git URL](https://github.com/brainless)\
Shreenath Regunathan<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://about.liferesources.in/cria/ongoing-projects/demand-supply.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
