> 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/works/reference-implementations/muktasoft-v2.2/implementation/pilot-go-live-definition.md).

# Pilot Go Live Definition

<table><thead><tr><th width="99.5">Sr. No.</th><th>Go Live Definition (Pilot)</th></tr></thead><tbody><tr><td>1</td><td>The employee and CBO Portal are developed and deployed into production instance with the features given below</td></tr><tr><td>1.1</td><td>Employee Portal: The list of features which a employee users will be able to perform</td></tr><tr><td>1.1.1</td><td>Time Extension: Create, Search, View, and Process the estimate for approval, download estimate PDF</td></tr><tr><td>1.1.2</td><td>Time Extension: While processing time extension below are the actions enabled based on the role a user has<br>1. Create and Forward<br>2. Verify and Forward<br>3. Approve<br>4. Send Back<br>5. Send Back To CBO<br>6. Reject</td></tr><tr><td>1.1.3</td><td>JIT-FS Integration: Smart Payments - Create PI/ Revised PI, Search, View PI</td></tr><tr><td>1.1.4</td><td>1. Fund Allocation Register (Without UI)<br>2. Create Payment Instruction (Auto)<br>3. Update Payment Details<br>4. Update Failure Details<br>5. Create Revised Payment Instruction<br>6. Search Payment Instruction<br>7. View Payment Instruction</td></tr><tr><td>1.1.5</td><td>MUKTA Dashboard: KPIs</td></tr><tr><td>1.1.7</td><td>Action Items<br>SLA Breached<br>Leaderboard<br>Status<br>Payments<br>Payments Vs Person Days<br>Cost By Project Type<br>Billing by Expenditure Type<br>Payment By Gender</td></tr><tr><td>1.2</td><td>CBO Portal/ Mobile App: The list of features which a CBO user will be able to perform</td></tr><tr><td>1.2.1</td><td>My Work Orders: Create Time Extension</td></tr><tr><td>1.2.2</td><td>My Service Request: View and Edit Time Extension</td></tr><tr><td>2</td><td>Notifications: SMS Notifications on various events intimating users about the action completed.</td></tr><tr><td>3</td><td>Localization: Application support English and Odia language.</td></tr><tr><td>4</td><td>UAT/ training feedback is incorporated</td></tr><tr><td>5</td><td>CBO mobile app is released and uploaded on Play Store</td></tr><tr><td>6</td><td>All the application users of the pilot ULBs are created</td></tr><tr><td>7</td><td>Production application URLs are shared with the users</td></tr><tr><td>8</td><td>Users training is completed</td></tr><tr><td>9</td><td>Help manuals and videos are created and shared in both the language English and Odia</td></tr><tr><td>10</td><td>Adoption success metric is defined</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/implementation/pilot-go-live-definition.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.