Development of asset management system- A case ...

Development of asset management systemA case study of tube wells of IIT Kanpur Khushboo GUPTA1, Onkar DIKSHIT2, Sudhir MISRA2 1 Research Associate, Department of Civil Engineering, IIT Kanpur, India 2 Professor, Department of Civil Engineering, IIT Kanpur, India

ABSTRACT With rapid growth of cities, increasing urban assets like water supply, roads, public transportation systems and power supply demands proper handling. In this research, which uses the water supply system of IIT Kanpur as a case-study, development of a web enabled water infrastructure management system (WIMS) is suggested as a possible solution for proper handling of these assets focusing on tube well as one of the component of water asset. The purpose is to initiate the design of a centralized database of tube wells which can be used for decision support, inspection planning, community need-to-know, and check for regulatory compliance. The work includes: designing of format for data collection, database creation and web based representation using open source tools to answer non-spatial queries. The system has been built in a manner that it permits upload of spatial and related non-spatial information of tube wells. It facilitates appending information related to uploaded features thereby helping to build a spatial database for tube wells. There is a need for a standard format for data collection for each and every asset existing. This would not just ease the data collection process but will also enhance the data quality. This system is built to help an organization’s works department to carry out better management of water infrastructure by keeping an up to date water infrastructure database. The above research is applied in Indian Institute of Technology Kanpur (IITK) to enhance the management of water infrastructure (tube wells) by Institute Works Department (IWD).

Keywords: Urban asset management, tube well, data collection format, database creation, web enabled water information management system

1. INTRODUCTION When we refer to an asset management system, an "asset" is a component with an independent physical and functional identity, value and service life. Maintenance, renewal and replacement of these assets is an integral part of ‘managing’ the assets, which can be done effectively only if an accurate and appropriate database of the assets is available (Betti, 2010). Virtual non-availability of such a database is one of the challenges faced by managers of public assets in India. The problem is compounded by the multiplicity of organizations involved in operating and maintaining the assets (Mukherjee, 2013).

Taking the case of water supply related infrastructure, developing an efficient water information management system (WIMS) which stores appropriate data for relevant assets is important for several reasons, some of which are listed below: 1. Providing a location based approach to manage operational challenges like solving complex geographical, hydrological and planning problems related to distribution of water (Garg et al, 2000). 2. New ways of acquiring water asset data and providing efficient means of processing, managing and integrating this data to meet decision making needs (Opadeyi, 2007). 3. Integrating non-spatial attribute information within the map geography, linking databases together, consolidating workflows, and presenting a common operating picture for the end user to perform water asset related spatial and non-spatial query (Kulshreshtha, 1998) 4. Handling large volume of deteriorating water infrastructure systems, particularly underground water infrastructure like tube wells, underground tanks and pipelines, which pose serious threats to the environment if they fail; as the information about the establishment and condition of these valuable assets get buried with them (Karlaftis et al, 2009) (Singh, 2011). WIMS will help a water works’ manager to answer the above questions accurately and rationally, and assist in the day to day functioning of the department. This paper focusses on the issues relating to development and management of WIMS in an urban scenario and uses the campus water supply network in Indian Institute of Technology Kanpur (IITK) as a case study. It emphasizes the need to create and maintain appropriate databases and suggests a simplified approach by developing a format for data collection considering the case of tube wells at IITK. The final objective is development of web enabled WIMS, and also explore the possibility of extending this concept to management of other urban assets such as roads and power supply systems.

2. METHODOLOGY SUGGESTED The stages for developing the information management system for an organization’s water infrastructure are as follows: 1. Understanding the existing infrastructure and availability of related information. 2. Identifying the components of water infrastructure present (e.g. drinking water, waste water and storm water pipelines, tube wells, etc.). 3. Obtaining relevant information (as hardcopy, soft copy, interview, reports, etc.) about these assets. 4. Interviewing the engineers and gathering the information relevant with respect to the organization’s personnel for water assets. 5. Development of a data collection form (template) 2.1 Algorithm development for WIMS The methodology used in this study is described briefly in a flow chart in Figure 1, Development of asset management systemA Case study of IIT Kanpur water infrastructure

along with the tools to be used at each step.

Format for Data Collection (Designing the format for tube wells)

Data Collection (Using GPS Receivers, and interviews with IWD engineers)

Data Representation (Shapefiles added and displayed in QGIS)

Database Creation (Performing queries in Postgre sql using Post GIS database)

Data Display on local host (Display of spatial queries on GeoServer)

Data Sanitization (Verification of data)

Data display on web (Linking the local host to web to display queries online)

Data Addition (Addition of spatial and non-spatial attributes in QGIS)

Development of the Platform (Styling of the layers, web page and platform, providing security essentials)

Figure 1: Flow chart for development of Water Infrastructure Management System (WIMS) 2.2 Application of suggested methodology as a case study for water assets in IITK The suggested methodology was implemented in the IITK campus established about 65 years ago in outskirts of Kanpur. It should be remembered that IITK is 1100 acre campus with a population of about 12000, has no ‘municipal water supply’ at present and relies completely on about 10 operational tube-wells to draw groundwater. The spread of all tube wells, working as well as abandoned in the IITK campus is described in Figure 2. The extent of campus is shown by boundary and road layers and the bullets in represent the locations of tube wells in the campus. The system is managed completely by the engineers of the Institute Works Department (IWD). The design of data collection format for water assets involved the following steps: 1. Identifying the components of water infrastructure and the state of its management: This step involved identification and classification of these components under different heads based upon their nature. For example: Tube wells (used for extraction of water from ground) 2. Interviewing the IWD engineers to get an insight about their requirements regarding data for managing the water assets in an efficient manner. 3. Grouping these parameters under different heads to provide individual as well as overall picture of the assets. These parameters are listed in Table 1. 4. Based on these parameter heads data collection format was created. Development of asset management systemA Case study of IIT Kanpur water infrastructure

Figure 2: Tube well locations in IITK campus 5. Information was obtained about these assets by going through documents (such as bore log reports) with IWD related to tube wells and interviewing the IWD personnel. 2.3 Description of tools used Relevant spatial data were collected by Trimble GPS receivers R3 and R7. The web enabled system was developed by using Quantum GIS (Quantum GIS 1.8 documentation), pgAdmin III (PostgreSQL Manual, 2006), GeoServer (Geoserver 2.0 Documentation), GeoNode (Geonode manual) and log plot utility of RockWare (for generating bore logs). A detailed description about these tools and their usage is presented in Gupta (2014).

3. RESULT AND DISCUSSION This section describes the data collection format and different types of queries performed on data. 3.1 Description of data collection format The data collection form consists of attributes for a tube well given in Table 1.

Development of asset management systemA Case study of IIT Kanpur water infrastructure

Table 1: Tube well attributes and their description included in data collection form Name ID Tube well Name

Type Numeric Text

Location

Double

Descriptive location

Text

Type1 Condition Start date Abandonment date Casing Size2 Hosing size2 Drilling depth Pipe depth Pipe material Pump specifications Establishment Charges3 Maintenance Charges3 Running Duration Running Schedule Discharge

Text Text Date Date Double Double Double Double Text Integer Integer Integer Integer Text Double

Comment Unique identity number for a tube well Naming convention followed Coordinates in UTM projection using WGS-84 reference ellipsoid Area or recognition point near which tube well is present On the basis of tube well depth (deep/shallow) Working condition or abandoned Year in which tube well started working. Year in which tube well was abandoned Diameter of the casing pipe Diameter of the hosing pipe Depth of bore drilled Depth till which the pipe is inserted in bore Material of tube well pipe Power of pump in HP (horse power) Expenditure (INR) spent during establishment of tube well Yearly expenditure on maintenance of tube well (INR) Total no. of hours of drawing water in a day Daily running schedule tube well Discharge measured in liters per hour.

Electrical units consumed

Integer

Hourly consumption of electrical units consumed for running tube well

Bore log4

Raster

Information about lithology type existing in the bore varying with depth

Notes: 1. A tube well classified on the basis of its depth – those with depth greater than 200 m are called ‘deep’ and those with depth less than 200 m are defined as ‘shallow’. 2. A tube well casing houses the inlet, cylinder, piston valves and rising main of a "down-the-hole" type hand pump. The upper casing has a bigger diameter than the normal casing which is known as hosing. In the data set used (IIT campus), the diameter of the hosing and casing pipes are 350 mm and 250mm, respectively. 3. The cost detail is split into development and operational charges. The former consists of the all expenditure for establishment of the well, the latter includes the operational electricity charges, and repair and renewal charges. 4. Bore logs give the variation of lithology, and locations of aquifer and non-aquifer layers at different depths.

Development of asset management systemA Case study of IIT Kanpur water infrastructure

The form was used to create a database for all tube wells including functional and nonfunctional ones in the campus. This database formed the basis of a (local) WIMS, which provided greater insight to the asset manager and provided answers to non-spatial queries, as explained in the following paragraphs. 3.2 Analysis Basically, to be able to answer the queries of an asset manager (AM), the information can come from the data of the tube well (discharge, etc.) and/or bore log. It should be borne in mind that it may not be possible to answer all the questions that AM may have from the overall data set created. To that extent, it may become necessary to modify the data collected from time to time. Questions that can be answered based upon tube well data include those relating to location, condition, efficiency, present value of discharge, running hours, cost details, etc. Another set of questions which arise include bore log related questions like soil profile, aquifer related information, etc. Queries relating to integration of tube well and bore log data can provide us information related to possible new locations of tube well, abandoning of deep tube wells, etc. A number of queries, single or multiple, can be performed in a WIMS which are needed to set consciousness of saving and cost control, to make decisions on the strength of knowledge and analysis of resource utilization. The following paragraphs discuss some examples of the kinds of information that can be useful to an AM in a local WIMS. 3.2.1 Description of tube well data From the data collected for tube wells, it can be stated that: 1. Total number of tube wells present in the campus (working or abandoned) are 22. Majorly tube wells are located towards the periphery of the campus. Out of which currently 10 are in the working condition and rest 12 tube wells are abandoned. 2. Initially, most of the tube wells built in the campus were shallow but with time all the shallow tube wells have been replaced by deep tube wells. Currently there are 12 deep tube wells and 10 shallow tube wells (working/abandoned). There is just one shallow working tube well and the others are deep tube wells. 3. The deepest bore dug is more than 400m and the shallowest bore is about is about 150m. 4. Abandoning of deep tube wells is majorly due to malfunctioning of tube well parts, like damaging of hosing pipe, inadequate screen and filter-pack selection or installation, incomplete development, screen corrosion, collapse of filter pack. 5. On the basis of establishment year of tube wells, it was realized the number of tube well currently employed for extraction of water were built after 1999. The average life span of tube wells is about 18 years. 3.2.2 Descriptive analysis on the basis of bore logs The variation of lithology of soil with depth of drilled bore is defined as a bore log. These bore logs are generated using RockWare’s log plot utility ((Rockware, 2007). Individual bore log reports (Gupta, 2014) show how the soil profile varies for a Development of asset management systemA Case study of IIT Kanpur water infrastructure

particular bore and area around that bore. The major soil types found in IITK campus are clay, morum, sand (fine to coarse), kankar clay, kankar and sand stone layer. Some layers are a combination of the above types. Bore log reports also help in deciding the position of blind and slots to be provided in a pipe for a tube well bore. Slots are provided for the aquifer layers (medium to coarse sand, morum, gravel, sand stone layers) and blinds are provided in the non-aquifer layers of the bore (majorly clay layers). These bore logs are an important initial database requirement for performing soil profiling of the campus. 3.2.3 Information retrieved from both tube well and bore log data There are certain aspects which need derived results using tube well and bore log data. Information related to new possible locations of tube wells require both tube well data for knowing the current locations of working tube wells and bore log data for determining the better choice for building tube wells in future based upon soil profile in respective bore logs. Reasoning behind abandonment of tube wells, majorly shallow tube wells can be understood by integrating both the available data. The individual bore logs also gives the aquifer layer corresponding to a bore. These aquifer layer were used to study the shift of shallow tube wells to deep tube wells. On studying individual bore log reports, it was found that water in the aquifer layer existing from 100 m - 200 m below surface is almost dried up. It was observed below 200 m, aquifer layer existed deep down at about 320 m and further down. From these aquifer layers water can be extracted. Thus deep tube wells were dug and all the existing shallow tube wells on the verge of abandonment were replaced by deep tube wells.

4. CONCLUSION AND FUTURE RECOMMENDATION This research concluded with a well-defined format to include most of the possible fields for tube wells. Based upon this format, data collected is utilized in successful development of web enabled WIMS for tube wells of IITK using open source tools. The data collection format forms the basis of creating a well-structured database for tube wells. It would solve the problem of data scarcity and will be helpful in proposing models based upon various attributes described. This WIMS provides user with easy to understand GUI. The secured platform built facilitates user to upload and append the spatial features in the form of vector layers. It gives freedom to perform spatial and nonspatial query for pipelines and tube wells. This platform also provides the facility of exporting and printing of layers and maps in various formats. Web enabled WIMS built can be further used to develop models for cost estimation and cost comparison between different techniques. This format can be further strengthened by including the cost drivers of tube well development. The bore log information available can be modelled to obtain bore log profiling for the soil of the institute. This will require interpolation of bore log data.

Development of asset management systemA Case study of IIT Kanpur water infrastructure

ACKNOWLEDGEMENT Work reported in this paper is a part of the research work being carried under the Obama-Singh Knowledge Initiative at IIT Kanpur in collaboration with Virginia Tech, USA. The authors are grateful for financial support from the Initiative and to Prof. Sunil Sinha for his inputs. REFERENCES Betti, R., 2010. Buildings and Infrastructure Protection Series: Ageing Infrastructure. US Department of Homeland Security. Garg, P., Gupta, R., and Arora, M. 2000. Analysis of Intra-District Disparities using GIS Technique. 3rd International Conference on GIS/GPS/RS. New Delhi. GeoNode Manual. Retrieved March 5, 2014, from GeoNode: http://GeoNode.org GeoServer 2.0 documentation. 2012. Retrieved January 11, 2014, from GeoServer: http://GeoServer.org/display/GEOS/Welcome Gupta, K., 2014. A web GIS for IITK water infrastructure. M Tech thesis submitted to IIT Kanpur, India Karlaftis, M., and Peeta, S., 2009. Infrastructure Planning, Design and Management for Big Events. Journal of Infrastructure Systems. Kulshreshtha, N., 1998. System Design and Considerations in some Geo Information Systems. M Tech thesis submitted to IIT Kanpur, India Mukherjee, A., 2013. Archives. Retrieved from Waterscapes: http://aditimukherji.wordpress.com/2012/07/13/how-many-wells-and-tubewells-inindia-no-one-really-knows/ Opadeyi, J., 2007. Road Map Towards Effective Mainstreaming of GISfor Watershed Management in the Caribbean. Retrieved January 13, 2014, from http://www.cep.unep.org/events-and-meetings/13th-igm-1/IWCAM-2en.pdf PostgreSQL:Manuals. 2006. Retrieved http://www.PostgreSQL.org/docs/manuals/

January

15,

2014,

from

Quantum GIS user guide. Release 1.8. http://docs.qgis.org/1.8/pdf/QGIS-1.8-UserGuide-en.pdf Rockware, 2007. Logplot user manual. colorado. https://www.rockware.com/assets/products/176/downloads/documentation/7/logplot7_ manual.pdf Singh, N., 2011. India’s water management challenge. Retrieved March 15, 2014, from http://www.eastasiaforum.org/2011/02/08/indias-water-management-challenge

Development of asset management systemA Case study of IIT Kanpur water infrastructure