Governed Digital Platform for Raghuganga Hydropower Limited
Executive Proposal
| Prepared by | Aashik Baruwal |
| workwithaa.sik@gmail.com | |
| https://www.linkedin.com/in/aashikbaruwal/ | |
| Portfolio | https://aashikbaruwal.com.np |
| Date | September 11, 2026 |
1. Executive Summary
Raghuganga Hydropower Limited (RGHPL) is a wholly owned NEA subsidiary established in 2017 to develop the 40 MW Rahughat Hydroelectric Project in Myagdi District. Construction is complete and trial power generation began in August 2026. Commercial production is imminent.
At this stage, the digital presence must do more than display information. Lenders require structured reporting, NEA requires transparency from its subsidiary, and active procurement requires a governed tender system. The current CodeIgniter-based website provides none of that.
This proposal requests approval to replace it with a purpose-built, company-owned governed digital platform built for commercial operation and public sector accountability.
Decision Requested
Approval of a discovery and implementation engagement for a company-owned digital platform that will:
- Present the Rahughat project credibly to communities, lenders, NEA, government bodies, regulators, auditors, and the public.
- Establish controlled, auditable publication for corporate, project, financial, operational, and regulatory information.
- Create an organized corporate record ready for management review, audit preparation, government audit, RTI response, and regulatory scrutiny.
- Replace unrestricted CodeIgniter administrator access with defined roles and approval authority.
- Provide an immediately usable tender and sealed-bid workflow for active procurement, including current requirements such as security service tenders.
- Build an evidence-ready foundation aligned with NEA governance standards, public procurement regulations, and professional advice.
2. Why This Matters Now
RGHPL has completed construction and entered trial generation. With two 20 MW units under test since August 2026 and commercial production imminent, the company is moving from a construction organization to a commercial operator.
At this point lenders expect regular and verifiable reporting, NEA expects transparency from its wholly owned subsidiary, and the public expects accountability from a state-owned plant entering operation.
The company has also issued active procurement tenders, including security service requirements. Each live tender needs controlled notices, corrigenda, sealed submissions, and a defensible opening record.
The current e-procurement system enforces submission deadlines through interface controls alone, not cryptographic sealing. A platform that cannot prove bids were sealed before opening leaves procurement exposed at the exact moment scrutiny increases.
Government auditors, lenders, NEA oversight, and regulators will expect to find:
- A clear, accurate account of the company and the 40 MW Rahughat project, including trial generation status and progress to commercial operation.
- Current and historical project progress, not only social media posts.
- Approved notices, financial information, generation records, and corporate documents in a searchable archive.
- Active tenders, corrigenda, and award information with a complete audit trail.
- Consistent Nepali and English content.
- Evidence that information was reviewed and authorized before release.
The current CodeIgniter-based website cannot meet this standard. It can publish content, but it does not provide an inherent governance record.
Relying on manual procedures and direct database or code level changes leaves critical controls dependent on individual discipline, both of which are difficult to demonstrate to EXIM Bank of India, NEA, government auditors, or RTI applicants.
Replacing it before full commercial operation avoids carrying weak controls into the operational life of the plant.
3. What Is Proposed
The proposed platform is a new, company-owned application. It replaces the CodeIgniter-based website after an agreed migration period and does not operate as a CodeIgniter integration.
The platform has two connected areas.
The screenshots in this proposal are taken from a working prototype configured for a comparable hydro project context.
They illustrate the platform's functions and layout. The production system will be fully custom-built for Raghuganga Hydropower Limited with RGHPL branding, Rahughat project data, defined staff roles, and bilingual content developed during implementation.
Public Website
A modern, bilingual public website presenting:
- Company profile, leadership, governance, and contact information.
- Rahughat project details: 40 MW capacity in two 20 MW units, run-of-river configuration, location in Myagdi District, trial generation status since August 2026, milestones, progress to commercial operation, and approved photographs and documents.
- Generation profile: 247.89 GWh annual energy and 137.71 GWh firm energy, with approved operational updates once commercial production begins.
- Notices for project-affected communities and stakeholders.
- Project cost and EXIM Bank of India financing information authorized for publication, referenced against the original NPR 9.175 billion budget.
- Corporate notices, periodic reports, disclosures, and procurement and tender documents, including active tenders.
- A searchable archive with stable document links and integrity-checked downloads.
- A public accountability and regulatory disclosure area, with controlled release of audited statements, government audit responses, and RTI compatible records.
Public PortalProject Landing & Disclosure Surface
Figure 3.1: The public project surface featuring real-time project statistics (40 MW, 247.89 GWh), engineering breakdown, live disclosure notices, and institutional credentials. Representative illustration. Final design will be custom-built for RGHPL.
Protected Administrative System
A secure system for authorized management, company secretarial, finance, project, legal and compliance, communications, procurement, and IT personnel. It governs:
- Drafting and editing of records.
- Independent review and recommendation.
- Final management approval and scheduled publication.
- Corrections, withdrawals, superseded versions, and archival.
- Document upload, integrity verification, and access control.
- Project, compliance, procurement, staff, and audit records.
Admin EnclaveExecutive Management Workspace & Operational Queues
Figure 3.2: Executive console showing pending approvals, returned drafts, live 5x5 risk posture, published estate metrics, and procurement pipelines. Representative illustration. Final layout and roles will be configured for RGHPL.
4. Business Outcomes
Stronger Executive Control
Management gains visibility into what is pending review, what is approved, what is published, and what is overdue. Approval authority is assigned by role rather than shared through a single administrator account.
Better Stakeholder and Public Confidence
Project-affected locals, EXIM Bank of India, NEA, government auditors, and regulators can locate authorized information directly, without relying on informal channels or intermediaries. Communities near the Rahughat site see verified trial and commissioning updates. Lenders see consistent financial and operational reporting as the plant enters revenue generation.
Improved Public Accountability and NEA Governance Compliance
The platform provides a controlled environment for regulatory notices, audited financial information, project disclosures, procurement records, and correction history, the information-governance foundation needed for work with auditors, NEA oversight, government reviewers, and the company's legal advisers.
Procurement Ready for Live Tenders
The sealed-bid module is immediately relevant. RGHPL has active procurement, including security service tenders. Controlled notices, corrigenda with justification logs, sealed technical and financial envelopes, opening date locks, and a complete access audit give the procurement committee a defensible record from the first live tender on the new platform.
Reduced Disclosure and Reputational Risk
The system reduces the risk of publishing unapproved, outdated, or unverifiable content. When questions arise, corrections and historical reconstruction are orderly and documented.
More Efficient Operations
Staff work from structured records and defined queues instead of searching across email, spreadsheets, local folders, and messaging apps. Documents are found, reviewed, and archived without reconstructing their history.
Better Audit Preparation
Organized records and evidence packs can be produced efficiently for the management, EXIM Bank of India, government auditors, NEA oversight, legal advisers, or regulators on request, including timely and consistent responses to RTI requests during trial generation and early commercial operation.
5. How Information Is Governed
Notices, reports, disclosures, and project updates follow a structured approval process before publication:
Architecture Diagram
At every stage, the system records the responsible person, timestamp, decision, attached documents, and reason. Nothing is published without an authorized approval decision on record.
Maker-CheckerBilingual Disclosure Authoring
Figure 5.1: Bilingual disclosure editor with mandatory PDF attachment integrity check and immutable Maker-Checker-Approver audit trail. Representative illustration. Final workflows and branding will be custom-built for RGHPL.
Risk Engine5x5 Enterprise Risk Posture
Figure 5.2: Real-time 5x5 residual heat map, control assurance metrics, review freshness telemetry, and automated data quality alerts. Representative illustration. Final risk configuration will be set for RGHPL.
The enterprise risk register applies the same discipline. Risks are scored on a consistent 5x5 matrix, controls are reviewed by someone other than their owner, and anything overdue escalates automatically. Management, lenders, NEA oversight, and government auditors receive a defensible picture of what the risks are and what is being done about them.
The platform does not remove executive judgment; it makes that judgment easier to exercise consistently and easier to demonstrate afterward.
6. Public Accountability, RTI Compliance, and NEA Governance Foundation
The platform is configured to support the company's obligations as a 100% NEA-owned state entity:
- A controlled public disclosure area for regulatory notices, audited statements, project status, and procurement information.
- A disclosure register covering notices, reports, project status, risk information, and regulatory communications.
- Linked Nepali and English records where required.
- Version and correction history for public and regulatory information.
- Controlled internal access to audit working papers, NEA oversight materials, and government review documents.
- Publication checklists aligned with NEA governance standards, public procurement regulations, RTI requirements, and professional advice.
- Evidence-pack exports for authorized review by management, government auditors, NEA oversight, legal advisers, lenders, and regulators.
- Retained records for consistent and timely responses to RTI requests and government audit queries.
Accountability PortalApproval-Gated Public Accountability & Financial Depository
Figure 6.1: Public accountability interface allowing citizens, lenders, auditors, and oversight bodies to search and filter statutory audits, annual reports, and regulatory disclosures. Representative illustration. Final structure will be custom-built for RGHPL.
7. Principal Capabilities at a Glance
| Capability | What it delivers for the company |
|---|---|
| Public project website | Credible, professional presentation of RGHPL and the 40 MW Rahughat plant entering commercial operation |
| Nepali and English publishing | Consistent communication across different stakeholder groups |
| Approval workflows | Documented evidence that information was reviewed and authorized before release |
| Public accountability area | Controlled, release-gated communication of audited statements, regulatory disclosures, and procurement information |
| Document archive | Searchable, organized records for management, auditors, NEA oversight, and government review |
| Project records | Structured progress, milestone, permit, and stakeholder information |
| Compliance register | Obligations, owners, due dates, and evidence in one place |
| Enterprise risk register | Independent review, calibrated scoring, and automatic escalation of overdue risks |
| Secure tenders | Controlled notices, corrigenda, submissions, opening dates, and sealed-bid records, ready for current live tenders |
| Audit evidence | Traceable publication and access history with tamper-evident controls |
| Role-based administration | Defined access instead of shared administrator credentials |
| Security controls | MFA, session limits, file integrity checks, and encrypted financial bid envelopes |
| Search and reporting | Fast record retrieval for executives, advisers, auditors, and regulators |
8. Comparison: CodeIgniter-based Website vs. Proposed Platform
| Requirement | Current CodeIgniter-based website model | Proposed governed platform |
|---|---|---|
| Project communication | Pages and file uploads | Structured project records and searchable archive |
| Approval accountability | Plugin-dependent or manual | System-enforced roles and workflow states |
| Historical evidence | May require reconstruction | Retained versions, timestamps, checksums, and audit trail |
| Future public accountability communications | Ad-hoc pages and files | Approval-gated public accountability and regulatory disclosure area |
| Bilingual records | Separate pages or uploads | Linked language versions with translation tracking |
| Sensitive documents | General media library | Publication-state gateways with integrity checks |
| Executive visibility | General CMS dashboard | Approval queues, status views, risk, and audit dashboards |
| Procurement | Not inherently a bid portal | Controlled tender and sealed-bid workflow with corrigendum trail, opening locks, and access audit |
9. Implementation Approach
The system is built as a purpose-built application with an estimated delivery timeline of two months following project initiation.
| Phase | What is confirmed or delivered | Duration |
|---|---|---|
| Discovery | Obligations, roles, content, approval rules, and NEA governance and public accountability priorities | 10 days |
| Design and configuration | Branding, information architecture, roles, workflows, and content model | 12 days |
| Migration and implementation | Approved CodeIgniter-based website content migrated; production services prepared | 10 days |
| Validation and training | Security checks, user acceptance testing, publication rehearsals, staff training | 7 days |
| Launch and handover | Production cutover, monitoring, documentation, and operational handover | 5 days |
10. Ownership, Security, and Accountability
The production environment is provisioned under the company's corporate accounts, ensuring full ownership of data, domain, and infrastructure.
Security controls include:
- Multi-factor authentication (MFA) for administrative access.
- Role-based access with server-side authorization.
- SHA-256 document integrity verification.
- Cryptographically linked audit logs for governance events.
- Cloudflare edge protection, rate limiting, and security headers.
- Scheduled release controls for sensitive financial documentation.
Audit LedgerCryptographic WORM Execution Ledger
Figure 10.1: Append-only cryptographic audit ledger verifying 188 unbroken hash-chained entries and external checkpoint anchoring. Representative illustration from the working prototype.
11. Indicative Infrastructure Cost
Monthly costs are estimated on the basis of infrastructure needs rather than service fees.
| Usage scenario | Estimated monthly infrastructure cost |
|---|---|
| Normal month | Approximately $5 |
| Peak disclosure or audit month | Approximately $10 to 15 |
| Extreme traffic event | Up to approximately $20 |
Estimates are indicative and subject to actual service configurations and provider pricing at the time of deployment.
12. Working Prototype
The following links demonstrate the platform's governance capabilities in a hydro utility context. They are prototypes only and are not Raghuganga Hydropower Limited's production system:
- Governance portal: https://durbang.aashikbaruwal.com.np/
- Additional prototype and portfolio work: https://www.aashikbaruwal.com.np/arc-and-civ
The screenshots used throughout this proposal are taken from that existing working prototype, which was prepared for a comparable Darbang hydro context and is reused here to show function and layout. The working prototype will be fully adapted to Raghuganga Hydropower Limited's branding, Rahughat project information, roles, and operational requirements during implementation. Nothing shown is RGHPL production data.
Prototype Walkthrough
Video DemoWorking Prototype in Action
Video walkthrough: a demonstration of the working prototype in use in a comparable hydro project deployment. It is a prototype only and is not Raghuganga Hydropower Limited's production system.
Prototype Visual Showcase
Public SurfaceEngineering Dossier & Site Gallery
Public Project Dossier: Geomorphic metrics (catchment, head, design discharge) and engineering narrative tracks. Representative illustration. Rahughat content will replace all placeholder data.
ProcurementPublic Tender & Sealed Bid Portal
Tender Notice Board: Category-filtered procurement invitations with countdown timers and sealed bid guidelines. Representative illustration. Live RGHPL tenders will appear here after configuration.
About the Developer
This proposal is prepared and delivered by one developer, with one point of contact from proposal through build, testing, and handover.
The entire platform, from database design to security controls to the public interface, remains under a single accountable hand, with no subcontracting and no handoffs between firms.
The working prototype is currently configured for a hydro utility context. It would be fully adapted to Raghuganga Hydropower Limited's branding, project information, roles, and operational requirements during implementation.
Selected work:
- satya: an offline-first educational platform running retrieval-augmented generation on standard 4 GB hardware with no internet dependency: https://github.com/aa-sikkkk/satya
- woofie: a full-stack pet-management platform in live production use: https://woofie.aashikbaruwal.com.np/
- Developer tools: a C/C++ syntax checker and an AI-powered image upscaler, both publicly released: https://github.com/aa-sikkkk/C-syntaxChecker and https://github.com/aa-sikkkk/ImageUpscaler
Source code, the database schema, and full documentation transfer to the company at agreed milestones.
A standard confidentiality agreement can be signed before work begins. Further work samples or references are available on request.
13. Getting Started
This proposal is designed to be assessed with little effort and no obligation.
I am based in Beni Bazaar and available to meet in person at a time convenient to the company, as well as online.
1. Review at your own pace.
The proposal above, together with the live prototype in Section 12, gives a concrete picture of the platform and how it would serve the Rahughat project as it moves from trial generation to commercial operation.
No meeting is required to evaluate the fit.
2. A short walkthrough.
A 15-20 minute meeting, in person in Beni or online, with anyone from management is enough to begin.
I will demonstrate the working prototype against a realistic Rahughat trial-to-commercial scenario and answer questions directly. No preparation is needed.
3. A scoping discussion when the timing is right.
If the company wishes to proceed, a focused discussion with management or the company secretary would confirm the platform scope, approval rules, content to migrate, and a fixed commercial proposal with a target launch date.
If the present timing does not suit the company, the proposal and prototype remain available for later review.
14. Closing
Raghuganga Hydropower Limited has completed construction of the 40 MW Rahughat project and started trial generation in August 2026 on two 20 MW units. Commercial production is imminent. The public presence and disclosure infrastructure should be in place before the plant goes fully operational, not after.
A governed digital platform gives the company a professional public presence and a disciplined information process behind it. Management sees clearly what has been approved. EXIM Bank of India, NEA, auditors, and citizens find reliable, authorized information. Active tenders run on a controlled record with sealed bids and a complete audit trail.
The company retains a verifiable record that supports NEA governance compliance, government audit, RTI response, and public procurement accountability from the first day of commercial operation.
Submitted by
Aashik Baruwal
Email: workwithaa.sik@gmail.com