PadhaikoAll subjects

Research Proposals, Research Reports & Technical Reports

Communication English (ENSH 204)

Open in the Padhaiko app

3.2 Research Proposals and Research Reports

Engineering research bridges theoretical principles and practical application. Whether seeking approval for an undergraduate major project at the Institute of Engineering (Institute of Engineering) or competing for national science grants, engineers must document their investigations through structured research proposals and formal technical reports.

A research proposal is a formal document requesting approval, academic sponsorship, or financial resources to investigate an engineering hypothesis, scientific phenomenon, or technological development. It establishes that the proposed inquiry addresses an authentic knowledge gap and will be executed through rigorous, valid methodologies.

Structure of a Research Proposal

Unlike commercial proposals for goods and services, a research proposal centers on an unresolved technical problem and an experimental or analytical methodology.

Definition

Research Proposal Structure

A formal engineering research proposal comprises eleven standard components:

  1. Title Page: Clear, specific title identifying variables; author names, institutional affiliations, supervisor name, and date.
  2. Abstract / Project Summary: Concise overview (under 250 words) synthesizing the research problem, specific objectives, proposed methodology, and anticipated contributions.
  3. Table of Contents: Hierarchical listing of sections and subsections with corresponding page numbers (lowercase Roman for front matter; Arabic for body).
  4. Introduction & Background: Broad technical context, theoretical foundations, and relevance to contemporary engineering.
  5. Problem Statement & Research Questions: Explicit definition of the specific technical hurdle, unexplored phenomenon, or design limitation.
  6. Objectives of the Study: Primary general aim divided into three or four measurable, actionable specific objectives.
  7. Literature Review: Critical synthesis of published scholarship, establishing current benchmarks and locating the exact research gap.
  8. Research Methodology & Experimental Design: Detailed description of materials, testing apparatus, mathematical models, algorithms, data acquisition protocols, and error analysis procedures.
  9. Work Plan & Timeline: Phased implementation schedule (Gantt chart) displaying milestones and task dependencies.
  10. Budget & Resource Estimation: Itemized direct costs (laboratory test fees, specialized sensors, computation hours, consumables) and justification.
  11. References & Appendixes: Complete bibliographic citations adhering to standard documentation styles (APA 7th or IEEE), supplemented by calibration sheets, circuit schematics, or questionnaires.

Front Matter Elements and Document Navigation

Long research reports and formal technical documents require standardized front matter to orient readers and facilitate selective reading.

Title Page

The title page provides essential bibliographic identification:

Table of Contents (TOC)

The table of contents functions as the navigational roadmap for technical documents longer than ten pages:

Summaries and Abstracts: Descriptive vs. Informative

An abstract is a concentrated synopsis of a technical document written for expert readers who must determine whether to read the complete text.

Definition

Descriptive vs. Informative Abstract

Engineering abstracts are classified into two categories:

AspectDescriptive AbstractInformative Abstract
Primary PurposeTells readers what topics the report discusses.Presents the report's actual data, findings, and conclusions.
Inclusion of ResultsExcludes results, data values, and final recommendations.Highlights key numerical results, percentages, and recommendations.
Standard LengthVery brief (50 to 100 words).Comprehensive (150 to 250 words).
Typical ContextUsed when space is extremely restricted (e.g., preliminary conference rosters or government proposals).Standard requirement for engineering theses, journal articles, and formal feasibility reports.

Abstract vs. Executive Summary

While an informative abstract focuses on technical parameters for an audience of researchers and engineers, an executive summary targets managerial decision-makers:


3.3 Technical Reports: Progress, Feasibility, and Case Study

Technical reports are operational instruments used by engineers to document investigations, evaluate alternatives, track active projects, and analyze engineering failures.

Progress Reports

A progress report (or status report) informs supervisors, clients, or funding agencies about the health and progress of an active project over a specified time interval. It monitors adherence to the work plan established in the original proposal.

Functions of a Progress Report

Organizational Patterns for Progress Reports

Writers organize progress reports using one of two primary structural approaches:

AspectTime-Based Progress ReportTask-Based Progress Report
Primary HeadingsStructured chronologically: past period, present period, future period.Structured by Work Breakdown Structure (WBS) task packages.
Section Flow1. Work Completed in Past Period
2. Work Currently Underway
3. Work Scheduled for Next Period
1. Task A: Sensor Deployment
2. Task B: Telemetry Firmware
3. Task C: Cloud Dashboard
SubheadingsDivided by tasks under each time interval.Divided by past, present, and future work under each task heading.
Best ApplicationShort, routine projects with straightforward sequential workflows.Complex, multi-team engineering projects with concurrent work packages.

Tone and Ethics in Progress Reporting

Ethical engineers maintain strict objectivity and honesty in progress reports:

Feasibility Reports

A feasibility report evaluates the practical viability of a proposed project, technological modification, or engineering acquisition to determine whether it should be implemented.

Definition

Feasibility Report

A feasibility report is an analytical recommendation report that investigates a technical, organizational, or economic question to determine whether a proposed course of action is practical, viable, and prudent. It answers three fundamental questions:

The TELOS Framework for Feasibility Analysis

Engineers systematically evaluate options across five recognized feasibility dimensions:

The Problem-Solving Model and Decision Matrix

Preparing a rigorous feasibility report follows a six-step engineering decision framework:

  1. Identify the Problem or Opportunity: Articulate the precise operational challenge requiring resolution.
  2. Establish Evaluation Criteria: Determine both necessary criteria (mandatory pass/fail thresholds, such as maximum budget or voltage limits) and desirable criteria (ranked preferences, such as lower maintenance costs or user friendliness).
  3. Determine the Options: Identify all credible alternative courses of action (including the baseline option of taking no action).
  4. Evaluate Each Option Against Criteria: Systematically analyze options using empirical testing, simulations, and financial models.
  5. Construct a Decision Matrix: Tabulate scores by assigning numerical weights to criteria based on relative importance.
  6. Formulate Conclusions and Recommendations: Recommend the optimal alternative supported transparently by the scoring matrix.
Weighted Decision Matrix for Secondary Substation Backup Power Selection
Evaluation CriteriaWeight (1 to 5)Option A: Industrial Diesel GeneratorOption B: Lithium Iron Phosphate BESSOption C: Flywheel Kinetic Storage
Capital Cost (CAPEX)5Rating: 4 (Score: 20)Rating: 2 (Score: 10)Rating: 1 (Score: 5)
Operational & Fuel Cost4Rating: 2 (Score: 8)Rating: 5 (Score: 20)Rating: 4 (Score: 16)
Switchover Response Time5Rating: 2 (Score: 10)Rating: 5 (Score: 25)Rating: 5 (Score: 25)
Environmental Emissions3Rating: 1 (Score: 3)Rating: 5 (Score: 15)Rating: 5 (Score: 15)
Maintenance Complexity3Rating: 2 (Score: 6)Rating: 4 (Score: 12)Rating: 3 (Score: 9)
Total Weighted Score—47 / 10082 / 10070 / 100

Engineering Case Study Reports

A case study report is an in-depth retrospective analysis of a specific real-world engineering project, design implementation, or structural/systemic failure. Its objective is to derive generalizable technical and ethical lessons to improve future engineering practice.

Definition

Engineering Case Study Report

An engineering case study report investigates a real-world engineering event, failure, or innovation. It follows a five-part structural framework:

  1. Background & Operating Context: Description of the site, physical infrastructure, design specifications, and environmental conditions prior to the incident or project launch.
  2. Problem Identification & Forensic Analysis: Exhaustive technical investigation detailing the failure mechanism (e.g., fatigue failure, hydraulic scour, software race condition, thermal runaway) or operational breakdown.
  3. Evaluation of Interventions / Alternatives: Assessment of competing engineering strategies to rectify the failure or stabilize the structure.
  4. Selected Engineering Solution & Implementation: Detailed explanation of the remedial design adopted, materials selected, construction challenges, and testing verification.
  5. Lessons Learned for Professional Practice: Generalizable engineering principles, recommended modifications to building codes, quality control guidelines, or organizational procedures to prevent recurrence.

Worked Examples

Example 1

1

The central data centre at Pulchowk Campus hosts core university management databases and digital examination portals. Due to recurring localized power grid transients, the facility requires an upgraded uninterrupted power supply (UPS) system.

The campus infrastructure committee is evaluating two technical alternatives:

Apply a weighted decision matrix to analyze both alternatives across five critical engineering criteria: Capital Cost, Footprint & Space Utilization, Cycle Lifespan, Thermal Stability/Cooling Overhead, and Maintenance Requirements. Formulate a final recommendation with justification.

Establishing Criteria and Weighting Factors: Assign weights on a scale from 1 (least critical) to 5 (most critical) based on data centre operating constraints:

  • Capital Cost (CAPEX) [Weight = 4]: Budget is constrained by university fiscal allocations.
  • Footprint & Space Utilization [Weight = 3]: Server room space is premium and structurally constrained on the second floor.
  • Cycle Lifespan [Weight = 5]: Replacement cycles disrupt critical servers; long battery life is paramount.
  • Thermal Stability & HVAC Energy Overhead [Weight = 4]: Excessive battery heat requires increased air conditioning load.
  • Routine Maintenance Demands [Weight = 2]: Campus technicians manage multiple facilities; low maintenance is desirable.

Rating Option 1 (Lead-Acid VRLA Battery Bank): Score on a 1-to-5 scale:

  • Capital Cost: Rating = 5 (Significantly cheaper initial purchase price). Weighted = 5 * 4 = 20.
  • Footprint: Rating = 2 (Extremely heavy and bulky; requires reinforced floor slab). Weighted = 2 * 3 = 6.
  • Cycle Lifespan: Rating = 2 (Typically 300 to 500 cycles at 80% DoD; requires replacement every 3 to 4 years). Weighted = 2 * 5 = 10.
  • Thermal Stability: Rating = 2 (Requires strict 20-25 deg C ambient cooling to prevent thermal runaway and plate sulfation). Weighted = 2 * 4 = 8.
  • Maintenance: Rating = 3 (Requires quarterly terminal impedance tests, torque checks, and cell balancing). Weighted = 3 * 2 = 6.
  • Option 1 Total Score = 20 + 6 + 10 + 8 + 6 = 50.

Rating Option 2 (Lithium Iron Phosphate BESS): Score on a 1-to-5 scale:

  • Capital Cost: Rating = 3 (Approximately 40 percent higher initial capital investment). Weighted = 3 * 4 = 12.
  • Footprint: Rating = 5 (One-third the volume and one-fourth the weight of VRLA). Weighted = 5 * 3 = 15.
  • Cycle Lifespan: Rating = 5 (3,000 to 5,000 cycles at 80% DoD; 10 to 12-year operational life). Weighted = 5 * 5 = 25.
  • Thermal Stability: Rating = 4 (LiFePO4 chemistry has high thermal runaway threshold and operates safely up to 45 deg C). Weighted = 4 * 4 = 16.
  • Maintenance: Rating = 5 (Integrated Battery Management System [BMS] provides automated cell balancing and remote telemetry). Weighted = 5 * 2 = 10.
  • Option 2 Total Score = 12 + 15 + 25 + 16 + 10 = 78.

Formulating Final Conclusion and Recommendation: While Option 1 offers lower initial procurement expenditure (NPR saving at installation), Option 2 scores substantially higher overall (78 vs. 50 points) due to its triple lifespan, minimal spatial footprint, lower cooling overhead, and automated BMS telemetry. Over a 10-year total cost of ownership (TCO) evaluation, the LiFePO4 system requires zero battery pack replacements compared to two full replacements for VRLA.

Answer:

The weighted decision matrix decisively favours Option 2 (Lithium Iron Phosphate BESS) with a score of 78 compared to 50 for Option 1 (Lead-Acid VRLA). The recommendation is to procure the LiFePO4 system, as its superior cycle life (10+ years), compact footprint, and automated BMS diagnostics justify the initial capital cost premium through long-term lifecycle savings.


Model Documents

Research Proposal: Decentralized Greywater Treatment Using Biochar Filtration in Urban Kathmandu
Title PageFront matter identifying project metadata

RESEARCH PROPOSAL

Title: Performance Evaluation of Biochar-Sand Adsorption Columns for Decentralized Greywater Treatment in Urban Kathmandu Households

Submitted By:
Anish Thapa (Roll No. 079/BCE/012)
Pratima Poudel (Roll No. 079/BCE/045)
Department of Civil and Environmental Engineering
Pulchowk Campus, Institute of Engineering, Tribhuvan University

Supervisor:
Assoc. Prof. Dr. Rameshwor Lamichhane
Department of Civil Engineering, Institute of Engineering

Date of Submission: November 2026

AbstractInformative abstract of research proposal

ABSTRACT

Urban households across the Kathmandu Valley face chronic municipal water deficits, forcing heavy reliance on groundwater extraction and costly commercial tanker deliveries. Concurrently, domestic wastewater is discharged untreated into storm drains, contributing to the severe ecological degradation of the Bagmati and Bishnumati river systems.

This research proposes an experimental investigation into the efficacy of locally produced pine-wood biochar integrated into multi-layer sand filter columns for decentralized household greywater treatment. A laboratory-scale experimental rig featuring three column configurations (pure sand, sand with 10 percent biochar, and sand with 25 percent biochar by volume) will be continuously fed synthetic laundry and bath greywater.

Influent and effluent parameters, including biochemical oxygen demand (BOD5), chemical oxygen demand (COD), total suspended solids (TSS), turbidity, and fecal coliforms, will be evaluated across a 90-day testing regime. The objective is to establish hydraulic loading thresholds and adsorption saturation points, delivering an affordable, low-energy domestic recycling solution capable of satisfying Nepal National Drinking Water Quality Standards for non-potable toilet flushing and irrigation.

Introduction and Research GapBackground and rationale

1. INTRODUCTION AND PROBLEM STATEMENT

Rapid urbanization in the Kathmandu Valley has outpaced sewage infrastructure development. Over 75 percent of domestic water consumption generates greywater (non-toilet wastewater from bathing, washing, and laundry). While less contaminated than blackwater, untreated greywater contains high concentrations of surfactants, pathogens, and suspended organics.

Prior local research has evaluated constructed wetlands and sand filters; however, these systems suffer from substantial land footprint requirements or rapid media clogging. Pyrolyzed biochar produced from invasive forestry species (such as Lantana camara and Pinus roxburghii) exhibits high surface porosity and cation-exchange capacity. However, systematic engineering data regarding the breakthrough curves, microbial biofilm retention, and optimal grain-size blending of biochar in compact domestic sand filters under subtropical conditions remain absent from local literature.

Research ObjectivesPrimary and secondary aims

2. RESEARCH OBJECTIVES

General Objective:
To design, fabricate, and experimentally validate a compact gravity-fed biochar-sand adsorption filtration column for domestic greywater reuse in Kathmandu.

Specific Objectives:
1. To characterize the physical and chemical adsorption properties (BET surface area, pore distribution, surface functional groups) of local pine-wood biochar pyrolyzed at 500 deg C.
2. To quantify the removal efficiencies of BOD5, COD, TSS, and linear alkylbenzene sulfonate (LAS) detergents across varying biochar-sand volumetric ratios.
3. To determine the hydraulic retention time (HRT) and operational breakthrough capacity before backwashing is required.
4. To conduct an economic life-cycle cost assessment of the proposed filter unit for single-family residences.

Methodology and Experimental DesignWork program and testing protocols

3. RESEARCH METHODOLOGY

- Material Preparation: Pyrolysis of pine biomass in an oxygen-limited kiln at 500 deg C; crushing and sieving to particle sizes between 0.5 mm and 2.0 mm; washing to remove residual ash.
- Column Design: Three parallel acrylic columns (internal diameter 10 cm, bed depth 80 cm) equipped with sampling ports at 20 cm vertical intervals.
- Influent Composition: Synthetic greywater prepared with standard commercial detergents, vegetable oil, and diluted nutrient broth to maintain consistent benchmark loading.
- Analytical Protocols: Testing conducted at the Institute of Engineering Environmental Engineering Laboratory in accordance with APHA Standard Methods:
- Turbidity via nephelometric turbidimeter (NTU).
- COD via closed reflux titrimetric method.
- BOD5 via 5-day incubation at 20 deg C.
- Coliform enumeration via membrane filtration.

Work Plan and BudgetTimeline and financial requirements in NPR

4. WORK PLAN AND BUDGET

Timeline (6 Months):
- Months 1-2: Material sourcing, biochar pyrolysis, column fabrication, sensor instrumentation.
- Months 3-4: Continuous laboratory flow testing and bi-weekly chemical water quality sampling.
- Month 5: Breakthrough curve modeling, data collation, and regression analysis.
- Month 6: Final thesis report drafting, defense presentation, and peer-reviewed manuscript submission.

Budget Summary (NPR):
- Acrylic columns, plumbing fittings, peristaltic pump: NPR 42,000
- Biochar processing, kiln rental, and sieve shaker calibration: NPR 18,000
- Laboratory analytical reagents and standard buffer kits: NPR 35,000
- Water quality testing fees (third-party laboratory verification): NPR 25,000
- Report documentation and publication charges: NPR 10,000
TOTAL PROPOSED BUDGET: NPR 130,000


Quarterly Progress Report: Lalitpur Municipal Drainage Modernization Project
Header and Project IdentificationAdministrative transmittal details

QUARTERLY PROGRESS REPORT NO. 02

Project: Lalitpur Metropolitan City Urban Drainage and Stormwater Modernization Project (Contract ID: LMC-STM-2026/01)
Reporting Period: August 1, 2026 to October 31, 2026
Client: Infrastructure Development Division, Lalitpur Metropolitan City
Contractor: Himalaya Infrastructure Consultants & Builders Pvt. Ltd., Pulchowk
Submission Date: November 6, 2026

Executive Summary of StatusHigh-level operational overview

1. EXECUTIVE SUMMARY

During the second quarter, construction activities accelerated following the cessation of the monsoon rains. Overall project progress stands at 48.5 percent physical completion against the scheduled target of 52.0 percent (a variance of -3.5 percent).

Key achievements include the completion of 1.8 kilometers of reinforced concrete box culverts along the Jawalakhel-Lagankhel corridor, completion of structural earthworks for the primary stormwater retention basin at Balkumari, and procurement of all optical flow sensors. The minor schedule slippage resulted from unseasonal late-September monsoon flooding that temporarily submerged the southern excavation trenches. A revised two-shift recovery schedule has been implemented to restore alignment with the completion deadline of February 2027.

Task-by-Task Progress SummaryWork breakdown structure status

2. STATUS OF WORK PACKAGES

Work Package 1: Geotechnical Survey and Corridor Clearance
- Status: 100 percent complete.
- Work accomplished: All utility relocations (telecom optical fibers and municipal drinking water pipelines) successfully coordinated and executed.

Work Package 2: Box Culvert Civil Construction
- Status: 62 percent complete (Scheduled: 70 percent).
- Work accomplished: 1,820 linear meters of 2.0 m x 1.5 m pre-cast reinforced culverts laid and backfilled along Ward 4 and Ward 15 arterials.
- Variances and challenges: Inundation in late September required continuous dewatering, pausing placement for 11 days.

Work Package 3: Retention Basin and Silt Trap Civil Works
- Status: 45 percent complete (Scheduled: 40 percent).
- Work accomplished: Bulk earthwork excavation (14,500 cubic meters) completed at Balkumari retention site. Riprap stone pitching on retaining slopes commenced 10 days ahead of schedule.

Work Package 4: Smart Telemetry and Flow Monitoring Instrumentation
- Status: 30 percent complete (Scheduled: 30 percent).
- Work accomplished: Ultrasonic water-level transmitters and solar-powered telemetry RTUs received in Kathmandu warehouse; benchtop calibration completed at Institute of Engineering electronics laboratory.

Financial Status and Payment ApplicationsBudget tracking in NPR

3. FINANCIAL STATUS (NPR)

- Original Total Contract Sum: NPR 48,500,000
- Cumulative Invoiced Amount (IPC 01 and 02): NPR 21,340,000
- Current Invoice Submitted (IPC 03): NPR 6,250,000
- Total Value of Physical Work Certified to Date: NPR 23,522,500 (48.5%)
- Contingency Expenditure to Date: NPR 420,000 (dewatering pumps and emergency shoring during flash flood)
- Financial Health: Project remains strictly within the original contracted budget ceiling.

Plans for Upcoming Period and Corrective ActionsForward-looking operational commitments

4. WORK SCHEDULE FOR NEXT QUARTER AND CORRECTIVE MEASURES

- Corrective Measures for Schedule Recovery: Contractor has mobilized a second daily working shift (06:00 to 22:00) with dedicated lighting towers to accelerate culvert joint grouting along Lagankhel Road, recovering 2.5 percent of the schedule variance by November 30.
- Planned Work for Q3:
1. Complete remaining 1,180 meters of box culvert installation.
2. Complete concrete spillway and siltation gate structures at Balkumari retention basin.
3. Install ultrasonic level sensors across 12 designated overflow nodes.
4. Commission municipal SCADA telemetry dashboard.


Engineering Case Study Report: Structural Settlement and Retrofitting of the Manohara River Bridge Pier
Title and AbstractExecutive identification and summary

ENGINEERING CASE STUDY REPORT

Title: Forensic Geotechnical Investigation and Micropile Retrofitting of Differential Pier Settlement: The Manohara River Bridge Case Study

Author: Structural Engineering Research Group, Pulchowk Campus, Institute of Engineering
Target Audience: Practicing Structural and Bridge Engineers, Department of Roads

EXECUTIVE SUMMARY
In August 2024, during a 25-year flood event on the Manohara River in eastern Kathmandu, Pier P-3 of a four-span prestressed concrete girder bridge exhibited sudden differential settlement of 142 mm accompanied by a 1.8-degree lateral tilt, resulting in deck joint spalling and emergency bridge closure.

This case study investigates the forensic failure mechanisms that precipitated the settlement, evaluates competing structural stabilization alternatives, documents the execution of the selected micropiling retrofitting program, and synthesizes critical engineering lessons for bridge foundations constructed on heterogeneous alluvial floodplains.

Background and Failure Forensic AnalysisPhysical context and failure mechanism

1. BACKGROUND AND FAILURE INVESTIGATION

The Manohara Bridge was constructed in 2018, supported on bored cast-in-situ concrete piles terminating at a depth of 18 meters into sandy-silt strata. Post-incident borehole logging, electrical resistivity tomography (ERT), and underwater scour surveys revealed the primary failure mechanisms:
- Scour Depth Underestimation: Upstream illicit sand-mining had lowered the active riverbed profile by 2.2 meters over six years, exposing the pile cap to direct hydrodynamic scour during high-velocity monsoon flows.
- Unidentified Peat Lens: Original borehole logs spaced 40 meters apart had missed a localized 3-meter-thick compressible organic clay and peat lens beneath Pier P-3 at 19 to 22 meters depth.
- Excessive Negative Skin Friction: Scour and riverbed drawdown induced downward drag on the piles, overloading the end-bearing layer and triggering shearing of the soft organic lens.

Evaluation of Remedial AlternativesEngineering trade-off analysis

2. EVALUATION OF REMEDIAL ALTERNATIVES

The emergency engineering team assessed three intervention strategies:
- Alternative 1: Complete Demolition and Reconstruction of Pier P-3 and Adjacent Decks. (Estimated duration: 9 months; cost: NPR 38,000,000; unacceptably severe economic disruption to city transport corridor).
- Alternative 2: High-Pressure Permeation Chemical Grouting of Subsurface Void. (Estimated duration: 6 weeks; cost: NPR 11,000,000; high risk of grout washout into river current and uncertain long-term bearing capacity).
- Alternative 3: Underpinning Pier Cap via High-Capacity Drilled Micropiles and Hydraulic Jacking. (Estimated duration: 10 weeks; cost: NPR 17,500,000; high structural reliability, load transfer directly to bedrock at 28 meters depth, preserves existing superstructure).

Selected Intervention and ImplementationExecuted technical solution

3. SELECTED ENGINEERING SOLUTION AND IMPLEMENTATION

Alternative 3 was executed:
1. Substructure Stabilization: 16 high-capacity micropiles (diameter 250 mm, featuring high-strength steel casing and central API steel rebar) were drilled through the existing pile cap into bedrock at 29 meters depth.
2. Pressure Grouting: High-strength non-shrink micro-fine cement grout (water-cement ratio 0.42, 28-day compressive strength 45 MPa) was injected under 15 bar pressure.
3. Hydraulic Re-leveling: Four 200-tonne synchronized hydraulic jacks were positioned beneath the girder bearing pedestals to lift the settled deck by 125 mm, correcting the roadway gradient to within acceptable serviceability limits.
4. Scour Protection: The exposed pier base was armored with heavy wire-crated stone gabion mattresses and an upstream submerged concrete deflector wall.

Lessons Learned for Professional PracticeGeneralizable engineering principles

4. LESSONS LEARNED FOR PROFESSIONAL PRACTICE

This structural failure highlights vital engineering imperatives for bridge design in alluvial river basins:
- River Morphology Must Account for Anthropogenic Activity: Hydrological scour design must not rely solely on static historical records; it must incorporate active bed degradation induced by urbanization and aggregate extraction.
- Increased Geotechnical Sampling Density: On heterogeneous alluvial floodplains, geotechnical drilling must be conducted at the exact footprint of every individual pier rather than interpolated across spans.
- Mandatory Foundation Telemetry: Critical river crossings must incorporate automated tiltmeters and scour monitoring sensors to detect early sub-surface displacement before catastrophic joint failure occurs.


Exercises

Exercise — Research & Technical Reports

Question 1

Explain the essential differences between a descriptive abstract and an informative abstract. Under what specific engineering circumstances is each type used?

Analyzing Descriptive Abstracts: A descriptive abstract summarizes the scope and topics covered in a report without presenting detailed findings, quantitative data, conclusions, or recommendations. It reads like a narrative version of the table of contents (e.g., "This report discusses the effects of fly ash on concrete strength, outlines curing protocols, and provides recommendations for site testing"). It is very brief, typically 50 to 100 words.

Analyzing Informative Abstracts: An informative abstract condenses the entire document, presenting the research problem, methodology, specific numerical findings, and conclusions/recommendations (e.g., "Replacing 20 percent cement with fly ash increased 28-day compressive strength by 14.2 MPa while reducing hydration heat by 18 percent. Replacing beyond 30 percent caused delayed initial setting times"). It ranges from 150 to 250 words.

Identifying Appropriate Engineering Applications:

  • Descriptive abstracts are used when publication space is severely restricted, such as conference call-for-papers preliminary programs, library bibliographic indices, or brief multi-volume government project catalogs.
  • Informative abstracts are the universal standard for technical research reports, journal papers, dissertations, and formal engineering feasibility studies where peer reviewers and researchers require immediate access to conclusions and quantitative results.
Answer:

A descriptive abstract lists the topics covered without revealing data or conclusions (50-100 words), whereas an informative abstract summarizes the entire document including methodology, quantitative findings, and recommendations (150-250 words). Descriptive abstracts are used when space is extremely restricted (e.g., conference rosters); informative abstracts are required for engineering theses, research reports, and journal papers.

Question 2

List the five dimensions of the TELOS feasibility framework and explain how an engineering team applies each dimension when evaluating an infrastructure proposal.

Explaining Technical Feasibility (T): Evaluates whether the technology, materials, and engineering expertise are physically and practically capable of achieving the design specifications. For example, verifying whether local soil can support an 8-story foundation or if wireless communication protocols can penetrate mountainous valleys.

Explaining Economic Feasibility (E): Analyzes life-cycle costs (capital expenditure, operation, maintenance) against projected financial returns, energy savings, or societal benefits. Ensures the organization has sufficient capital and that the project represents the most cost-effective alternative.

Explaining Legal and Regulatory Feasibility (L): Ensures compliance with national building codes, environmental protection acts, labor laws, zoning restrictions, intellectual property patents, and land acquisition regulations.

Explaining Operational Feasibility (O): Assesses how effectively the completed system integrates into the existing organizational culture, staffing skills, and maintenance procedures. Evaluates whether local technicians can operate and repair the system after handover.

Explaining Schedule Feasibility (S): Determines whether the project can be designed, procured, constructed, and commissioned within mandatory seasonal or contractual deadlines (e.g., completing riverbed foundations before the start of the monsoon season).

Answer:

The TELOS framework evaluates:

  1. Technical (engineering viability and physical possibility).
  2. Economic (cost-benefit and financial affordability).
  3. Legal (compliance with laws and building codes).
  4. Operational (ease of use, maintenance, and organizational integration).
  5. Schedule (completion within operational calendar deadlines).
Question 3

Differentiate between time-based and task-based structures in progress reporting. For a multi-team municipal engineering project, which structure is superior and why?

Contrasting Organizational Structures:

  • Time-Based Structure: Arranged chronologically under three primary divisions: (1) Work completed during the past reporting period, (2) Work currently underway, and (3) Work planned for the upcoming period. Sub-tasks are nested under each time heading.
  • Task-Based Structure: Arranged by Work Breakdown Structure (WBS) work packages (e.g., Task 1: Civil Works, Task 2: Electrical Integration, Task 3: Software). Chronological status (past, present, future) is nested under each individual task heading.

Evaluating Suitability for Multi-Team Municipal Projects: For complex municipal projects with concurrent engineering teams, the task-based structure is decisively superior:

  • Independence of Work Packages: Civil, electrical, and software streams operate at different tempos; a task-based report allows each technical reader to immediately assess the status of their specific discipline.
  • Traceability to Milestones: Direct alignment with the original proposal's WBS makes budget tracking and variance detection significantly clearer.
  • Avoidance of Chronological Confusion: In a time-based report, fragmented updates from multiple teams merged under "Work Completed This Month" obscure the cumulative progress of individual deliverables.
Answer:

Time-based reports organize content chronologically (past, present, future periods), while task-based reports organize by project work packages (WBS) with chronological status nested within each task. For multi-team municipal projects, the task-based structure is superior because it maintains accountability across distinct engineering disciplines, aligns directly with contract deliverables, and prevents fragmented reporting across concurrent operations.

Question 4

What is the function of a weighted decision matrix in a feasibility report? Explain how criteria weights and option ratings are determined and combined.

Defining the Function: A weighted decision matrix is an analytical tool used in feasibility and recommendation reports to systematically and objectively evaluate competing engineering alternatives against multiple, often conflicting, criteria (such as cost versus performance).

Determining Criteria Weights: The engineering team identifies all critical evaluation parameters and assigns each an importance weight (typically on a scale of 1 to 5). Higher weights correspond to critical organizational priorities (e.g., human safety or severe budget ceilings).

Assigning Option Ratings and Computing Weighted Scores:

  • Each competing alternative is assigned an objective rating (e.g., 1 to 5) for each criterion based on empirical testing, manufacturer specifications, or financial modeling.
  • The rating is multiplied by the criterion's weight to produce a weighted score for that cell.
  • Weighted scores are summed vertically down each column to compute the Total Weighted Score for each alternative. The option with the highest total score is recommended.
Answer:

A weighted decision matrix provides an objective, transparent framework for selecting the optimal engineering alternative. Criteria are assigned importance weights (1 to 5), each option receives an empirical rating (1 to 5) per criterion, and the product of rating and weight is summed to determine the highest-scoring recommended solution.

Question 5

Describe the five core structural sections of an engineering case study report. Why is the "Lessons Learned" section vital for engineering practice?

Enumerating the Five Core Sections:

  1. Background and Context: Environmental, geotechnical, and operational conditions prior to the incident.
  2. Problem Identification and Forensic Analysis: Technical investigation uncovering the root physical, chemical, or operational failure mechanisms.
  3. Evaluation of Alternatives: Trade-off analysis of potential structural remediations or interventions.
  4. Selected Engineering Solution and Implementation: Detailed description of the executed repair or redesigned system.
  5. Lessons Learned for Professional Practice: Broader systemic insights, code revisions, and design precautions.

Significance of the "Lessons Learned" Section: The ultimate purpose of engineering forensic analysis is not merely fixing a single isolated defect, but advancing professional knowledge:

  • Prevents catastrophic recurrence across similar infrastructure.
  • Informs updates to national engineering standards, design codes, and safety safety factors.
  • Trains future engineers to recognize subtle hazard indicators and vulnerabilities during the design phase.
Answer:

The five sections are: Background & Context, Problem Identification & Forensic Analysis, Evaluation of Alternatives, Selected Engineering Solution & Implementation, and Lessons Learned. The "Lessons Learned" section is vital because it translates an isolated engineering failure into actionable knowledge, guiding revisions to building codes, safety factors, and professional design practices to protect public safety.

Question 6

Explain how pagination and heading conventions differ between the front matter and the report body in formal engineering reports.

Pagination Conventions:

  • Front Matter: Numbered sequentially using lowercase Roman numerals (i, ii, iii, iv, etc.), typically centered at the bottom of the page. The title page is counted as page i but does not display a visible page number. The abstract is typically page ii, followed by the Table of Contents on page iii.
  • Report Body & Back Matter: Numbered sequentially using Arabic numerals (1, 2, 3, etc.), typically positioned at the upper right or bottom center of the page. Page 1 begins on the first page of the Introduction.

Heading Conventions:

  • Headings in the report body follow a strict hierarchical decimal system (e.g., 1.0, 1.1, 1.1.1).
  • Headings in the front matter (Abstract, Table of Contents, List of Figures) and back matter (References, Appendixes) are unnumbered major headings, typically formatted in centered or left-aligned bold capitals.
  • The Table of Contents must reflect the exact wording, capitalization, and hierarchy of the headings in the body.
Answer:

Front matter pages use lowercase Roman numerals (i, ii, iii), with page i (the title page) unnumbered, while the body and back matter use Arabic numerals (1, 2, 3) starting from page 1 at the Introduction. Front and back matter headings are unnumbered, whereas body sections follow a strict decimal numbering scheme (1.0, 1.1, 1.1.1) exactly mirrored in the Table of Contents.

Past exam questions for Communication English

← Technical ProposalsManuscript for a Journal →