A DPR is a micro planning tool that typically provides the project rational, summary, user specifications, engineering designs of main and support infrastructure, as well as technical and financial aspects including financial sustainability. DPRs need to be developed for every project site.
1. Background and context to DPR Footfall categorization to provide an idea of the size of the project, plausible demand characteristics, and whether the project would be able to meet the CAPEX and OMEX requirements. Planning & construction norms and designs: Existing and envisioned norms need to be clearly stated to ensure that the overall design aspects (units and construction limitations) are clearly understood and agreed upon. Some support schemes require scheme-specific rather than universal standards. CAPEX & OMEX template is a checklist of items to be used while preparing cost estimates for construction or installation (guidelines developed based on best practices in the sector).
2. Detailed Project Report of Individual project site or project packages of project sites Project Summary: Abstract to provide a snapshot of the project; often together with an action plan. Project Rationale provides the logic of why the project is important in the overall city wide context, location specifications, the problems to be addressed, the project’s uniqueness and quantification of envisioned benefits.
3. User Profile provides a snapshot of the target users, their geographical spread, insights on usage timings and respective user perception survey recommendations. It also summarizes the analysis of land use around the PT location (demand); results from micro-level user surveys and focus group discussions on design requirements (e.g. different operational models in slums and tourist locations).
Proposed Technical Design provides a detailed analysis of the component units to be engineered (rehabilitation or new construction), assumptions on the structural designing and system functionality, detailed engineering designs (plans, elevations, sections as applicable) and detailed cost estimates that are detailed enough to use in the tender documents. Overall Layout provides an understanding of how the project could look (project visualization); often used for dissemination and discussions. Financial Analysis: Project feasibility (IRR & Net Present Values), considering estimated demand, project cost, O&M costs, concession period, unit rates. Demand Assumptions discuss the expected increase in footfall over the design period, issues pertaining to capacity utilization (rehabilitation) and optimization of structure components. Cost Estimates: Detailed item-wise engineering estimates of all project aspects including support infrastructure. Financial Assumptions related to construction of the asset, operation and maintenance, user charges and their expected increase, existing debt, annual escalations, interest rates, etc. Financial Projections verify the project viability against maintenance contracts or BOT projects, under the given assumptions detailed earlier. The operational and business model development section of the project structuring provides a more detailed financial analysis, relevant for the project’s structuring and contract documents. Recommendations summarize the project viability (technical & financial).