> 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/access/local-governance-stack/water-and-sewerage/water-charges-master-data-templates/pipe-size-types.md).

# Pipe Size Types

## Introduction <a href="#introduction" id="introduction"></a>

Water pipes are available in different sizes. Pipe size is a common parameter used for calculating water charges. The allotted pipe size for new water connections depends on specific service requirements.

## Data Table <a href="#data-table" id="data-table"></a>

| Sr. No. | Pipe Size\* | UOM\*  |
| ------- | ----------- | ------ |
| 1       | 0.25        | Inches |
| 2       | 0.50        | Inches |

The data given in the table is sample data for reference.

## Procedure <a href="#procedure" id="procedure"></a>

### Data Definition <a href="#data-definition" id="data-definition"></a>

| Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description                                 |
| ------- | ----------- | --------- | --------- | --------- | ------------------------------------------- |
| 1       | Pipe size   | Decimal   | (2,2)     | Mandatory | Value for Pipe size                         |
| 2       | UOM         | Text      | 256       | Mandatory | Unit of measurement for the pipe size value |

### Steps to fill data <a href="#steps-to-fill-data" id="steps-to-fill-data"></a>

1. Download the data template attached to this page.
2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.
4. Enter the Pipe Size details.
5. Enter the corresponding UOM for the specified Pipe Size.
6. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

## Checklist <a href="#checklist" id="checklist"></a>

The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per specifications. These activities have been divided into 2 groups as given below.

### Common Checklist <a href="#common-checklist" id="common-checklist"></a>

This checklist covers all the activities which are common across the entities.

| Sr. No. | Checklist Parameter                                                               | Example                                                                                                                      |
| ------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| 1       | Make sure that each and every point in this reference list has been taken care of | ​[Checklist](https://docs.digit.org/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist)​ |
| 2       | UOM should same for all the values provided pipe size in the template             | E.g. If it is given as Inches then it should be inches for all.                                                              |

### Entity Specific Checklist <a href="#entity-specific-checklist" id="entity-specific-checklist"></a>

A separate entity-specific checklist is not needed for this module data.

## Attachments <a href="#attachments" id="attachments"></a>

{% file src="/files/8edZe8zOjsc2BQIIESI9" %}

{% file src="/files/ds5IIG92JuH2S46SAYO7" %}


---

# 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/access/local-governance-stack/water-and-sewerage/water-charges-master-data-templates/pipe-size-types.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.