MHUID Asset Mapping & Workflow Manual

MHUID Geoportal Workflow & Asset Mapping Guide

Maharashtra Unique Identification System for Public Works Geotagging & Validation
Official Portal: mhuid.mrsac.org.in
Helpdesk Support: mrsachuid@gmail.com
Documentation: MHUID User Manual (PDF)

1. Executive Overview & Administrative Framework

The MHUID Geoportal (developed via MRSAC) establishes a centralized spatial repository designed to eliminate duplicate infrastructure works across departments. System administration and user creation rights are managed directly by the District Planning Officer (DPO) as the competent authority. Authorized personnel access the portal via their Sevarth ID, authenticated using dynamic One-Time Passwords (OTP) issued to their registered mobile numbers.

Statutory Deadlines & System Directives:
  • Mandatory Geotagging Mandate: Administrative approvals for public works shall be issued exclusively after generating a valid UID on the portal.
  • HOD Validation Requirement: The Head of Department (HOD) is mandated to review and validate all uploaded spatial data on the portal.
  • Historical Backlog Requirement: All infrastructure works executed over the last 5 years must be mapped onto the geoportal.
  • Document Format Constraints: Proposal documentation must be uploaded in PDF format only, capped at a maximum file size of 1 MB.

2. Visual Workflow Architecture

The diagram below tracks user navigation, mapping decision trees, environmental proximity checks, and information update pathways for new and existing assets.

flowchart TD A[Start: Login as User] --> B[Select Taluka, Village, Asset, Subtype] B --> C{Department & District will be as per Sevarth Id} C --> D{Choose Workflow} D -->|New Mapping| E[Create Asset] D -->|Existing Mapping| F[Select Asset] D -->|Repair Work| F D -->|Additional Work| F %% New Mapping Path E --> G[Select Point, Line, Polygon] G --> H[Create Asset] H --> I[Create MHUID] I --> J{Asset within 300 m of Forest Area?} J -->|No| K[End] J -->|Yes| L[Inform the user] L --> M[Add Project Details – Scheme, Proposal date, proposal cost] M --> N[Create UID] N --> O[Reports & Maps] %% Existing / Repair / Additional Path F --> P[Zoom to area of asset] P --> Q[Select Asset] Q --> R[Update Info] R --> S[View Project Details – Scheme, Proposal date, proposal cost] S --> T[Add Technical Sanction, Administrative Sanction, Work Order, current status, etc.] T --> U[Update Info] U --> V[Reports & Maps] %% Styling classDef startEnd fill:#f9f,stroke:#333,stroke-width:2px; classDef process fill:#bbf,stroke:#333,stroke-width:1px; classDef decision fill:#f96,stroke:#333,stroke-width:2px; classDef info fill:#ffcc80,stroke:#333; class A,K startEnd; class B,E,F,G,H,I,L,M,N,P,Q,R,S,T,U process; class J,D decision; class C info;

3. Step-by-Step Operational Instructions

Stage 1: User Authentication & Attribute Selection

Upon Sevarth ID log in and OTP validation, the department and district parameters automatically lock to the user's official profile. The operator selects the administrative hierarchy down to the Taluka and Village level, followed by the specific Asset Category and Subtype.

Stage 2: Operational Path Decision

  • Path A: New Asset Mapping — Selected when creating a newly sanctioned or unmapped asset.
  • Path B: Existing / Repair / Additional Work — Selected to update records, attach repair orders, or log additional work on an existing asset ID.

Stage 3: Spatial Vectorizing & Environmental Sensitivity Check

For new mappings, spatial geometry is defined using Point, Line, or Polygon vector tools depending on the asset topology (e.g., points for wells/buildings, lines for roads, polygons for water bodies). The system executes an automated spatial buffer query:

Forest Proximity Buffer Assessment: If an asset boundary falls within 300 meters of a declared Forest Area, an explicit environmental alert notification is flagged to the user prior to adding project scheme details, proposal dates, and costs.

Stage 4: Administrative Data Entry & Report Generation

Users record technical sanctions (TS), administrative sanctions (AS), work order numbers, and current execution milestones. Once submitted, final GIS maps and summary compliance reports can be exported directly for sanctioning records.

4. Technical & Compliance Specifications

System Requirement Specification Details
System Administrator District Planning Officer (DPO)
Authentication Mechanism Sevarth ID + Mobile OTP Verification
Spatial Geometries Supported Point, Line, Polygon
Environmental Buffer Trigger Automated flag for assets within 300 meters of Forest Areas
Historical Mapping Scope Mandatory retroactive mapping of all works executed in the last 5 years
Document Upload Standards PDF format only; Maximum file size ≤ 1 MB