> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/urban/release-notes/program-roll-out-plan.md).

# Program Roll Out Plan

DIGIT Urban 2.9 release has a new following features:

* DIGIT Urban 2.9 Beta Features
* DIGIT as a Service
* Bug Fixes

| Task                                                                     | Status      | Owner         |
| ------------------------------------------------------------------------ | ----------- | ------------- |
| Upgrade of UPYOG with Beta features                                      | 15/05/2023  | Pradeep Kumar |
| Session with NUDM team on Central Instance                               | 31/07/2023  | Ajay Rawat    |
| Getting approval from partners for UPYOG upgrade with DIGIT as a Service | In Progress | Ajay Rawat    |
| Effort Estimate for Upgrade created                                      | Done        | Vinoth        |
| Gate 2                                                                   | In Progress | Ajay Rawat    |
| Release Communication Shared with Partners                               | To Do       | Ajay Rawat    |

### NUDM Roll Out <a href="#nudm-roll-out" id="nudm-roll-out"></a>

The NUDM Team has shared the following requirements for upgrading UPYOG with the Central Instance:

**\*Conditions for Upgrading UPYOG with Central Instance**

* Role & Access Management at Cluster Level so that each State SI can do its scope of work
* Role & Access Management at Logs Level  so that each State SI can do its scope of work
* Role & Access Management at Elastic Search & Kibana Level  so that each State SI can do its scope of work
* Enhancement & verification of Product default Kafka with more nodes, partitions, etc so that it sustains and performs for National Level traffic
* Enhancement & verification of Product default ElasticSearch with more nodes, shards, etc so that it sustains and performs for National Level traffic
* Availability of all States data in its DB schemas and the same should apply with ElasticSearch
* Other enhancements so that the State Infra & DevOps team can manage their resources independently.

## **Adoption Metrics**

| Feature            | Metric                                                                  | Estimate                                                                                                                                               |
| ------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Citizen Feedback   | No. of states adopting feature and sharing data with National Dashboard | At least 2 states to implement the feature under NUDM in next 6 months                                                                                 |
| Consent form       | Compliance to NUIS Assessment                                           | Compliance report already shared post release of feature                                                                                               |
| Dashboard KPIs     | No. of states sharing data on new KPIs                                  | Citizen Feedback feature to be implemented in states, for KPIs to start reflecting data. 2+ states to implement the feature and share data on the KPIs |
| DIGIT as a Service | No. of accounts/projects using feature in all missions                  | At least 2 accounts use DIGIT as a Service in next 6 months                                                                                            |

## Success Metrics

| Feature            | Objective                                      | Estimate                                                                  |
| ------------------ | ---------------------------------------------- | ------------------------------------------------------------------------- |
| Citizen Feedback   | Improvement in Citizen Satisfaction            | Improvement in Metrics by 20% in first 3 years in state using the feature |
| Consent form       | Compliance to NUIS Assessment                  | Compliance report already shared post release of feature                  |
| Dashboard KPIs     | Improvement in Citizen Satisfaction            | Improvement in Metrics by 20% in first 3 years in state using the KPIs    |
| DIGIT as a Service | Optimizing resources for saving in infra costs | Saving to be estimated                                                    |


---

# 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://docs.digit.org/local-governance/urban/release-notes/program-roll-out-plan.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.