0% found this document useful (0 votes)
7 views14 pages

Logistic Mapping OM&SOP

This Standard Operating Procedure (SOP) outlines the GIS-based data collection process for National Highways in India, aiming to enhance responsibility, data accuracy, communication, and transparency. It details login procedures for Regional Offices (ROs) and Project Implementation Units (PIUs), including data management and verification protocols. Additionally, it sets timeline guidelines for data submission and verification to ensure efficient operations within the Ministry of Road Transport & Highways.

Uploaded by

mantrade809
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views14 pages

Logistic Mapping OM&SOP

This Standard Operating Procedure (SOP) outlines the GIS-based data collection process for National Highways in India, aiming to enhance responsibility, data accuracy, communication, and transparency. It details login procedures for Regional Offices (ROs) and Project Implementation Units (PIUs), including data management and verification protocols. Additionally, it sets timeline guidelines for data submission and verification to ensure efficient operations within the Ministry of Road Transport & Highways.

Uploaded by

mantrade809
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Standard Operating Procedure (SOP)

for
RO / PIU Jurisdiction Data Collection
Objective of SOP for GIS based Data Collection for National Highways
The objective of this Standard Operating Procedure (SOP) is to streamline and
facilitate the GIS based data collection process for all National Highways in India
under the Ministry of Road Transport & Highways. The SOP aims to achieve the
following goals:
Define Responsibility Areas: Clearly define the responsibility areas for each
National Highway.
Utilize GIS Mapping: Utilize a GIS-based mapping system through the Media portal
for defining networks and data visualization.
Verify Data Accuracy: Implement a verification process by the admin team to
ensure data accuracy and reliability.
Support Communication: Use the collected data for various communication
purposes related to the highway system.
Enhance Transparency: Improve transparency within the system by providing
accurate and up-to-date information.
Improve Communication Flow: Enhance communication flow within the system by
establishing a standardized data collection process.
The SOP will follow a structured approach to accomplish these objectives, ensuring
efficiency, accuracy, and transparency in the data collection process for National
Highways.
Login Procedure
The login process for all Regional Offices (ROs) and Project Implementation Units
(PIUs) from Ministry of Road Transport & Highways (MoRTH), National Highways
Authority of India (NHAI), and National Highways and Infrastructure Development
Corporation Limited (NHIDCL) is as follows:
URL: https://media.morth.gov.in/morth_srs/login.php

Figure 1: Login Form

Login Credentials: Each user is provided login credentials based on their Email ID
and Closed User Group (CUG) mobile number.
The system grants access to users only if both the Email ID and mobile number
match the records in the system.
Support Contact: In case of any login issues or queries, users can contact the call
center for assistance.
OTP Verification: Upon entering the correct credentials, an OTP (One-Time
Password) is sent to both the registered Email ID and mobile number.
Users must use this OTP to complete the login process and access the system
securely.
Data Management Protocol for Regional Offices (ROs):
Regional Offices (ROs) have the responsibility of overseeing Project Implementation
Units (PIUs) and verifying their jurisdiction through the designated form. ROs can
access and review details of their profiles, including Organization, Name,
Designation, and Reporting Person Name. In case of any discrepancies, ROs can
contact the admin or call the support number for necessary changes.
Managing PIUs: ROs are tasked with managing PIUs under their purview.

Figure 2: PIU Jurisdiction

They can view the list of PIUs under their jurisdiction, add new PIUs, and modify
their details as needed by clicking on “View User” button.

Figure 3: Manage User

GIS Map Access: ROs have the capability to view the jurisdiction of PIUs under
them on a GIS Map for better visualization and management by clicking on “View all
on Map” button.
Figure 4: Highways Data on MAP

Data Verification: It is imperative for ROs to verify the data provided by the PIUs to
ensure accuracy and alignment with organizational standards.
By effectively managing PIUs, utilizing GIS maps, and verifying data, ROs contribute
significantly to maintaining a streamlined and efficient data collection process.
Data Collection Procedure for PIUs
PIUs are required to define their jurisdiction using the provided form. The form will
include details such as Organization, Name, Designation, and Reporting Person
Name. In case of any discrepancies, PIUs can contact the admin or call the support
number for necessary changes.

Figure 5: Profile Details

Procedure for Adding Highways to Your Jurisdiction:

Figure 6: Jurisdiction Form

Selecting National Highway Number: Users should choose the National Highway
Number from the dropdown list.

Figure 7: Highway Selection


If the desired National Highway is not listed, they can opt for the "Other" option to
define the number.

Figure 8: Verification of NH and State

Defining the State: After selecting the National Highway Number, users need to
specify the state and then click on the "Go" button.

Verification and Display: The system verifies the National Highway number with the
selected state. If the verification is successful, the system displays information about
the stretch of the National Highway within the state boundaries.

Figure 9: Highway details after Verification

The route of the National Highway will also be reflected on the map.
Figure 10: Points on Map

Point Definition on Map: Users need to define the Start Point, End Point, and
Intermediate Points on the map.
They can define coordinates by either clicking the "Set Start Point" button on the
map or using their current location coordinates by clicking "Get Current Location."
Figure 11: Setting Point on Map View

Submitting and Editing Points: Users can submit any point from the list at once
and later edit other points by clicking the edit button.
Once all data including latitude, longitude, and location details are filled, the system
verifies it with the National Highway number before saving.

Figure 12: Verification during Data Saving


Figure 13: Complete details with Coordinates

Saved Data and Editing: The saved list of data will be displayed above the form
and can be edited until verified by the RO or frozen by the admin.

Figure 14: Final View of Data

PIUs can submit multiple jurisdictions within their area, and the complete list can be
viewed on the map.
Figure 15: View with Multiples Highways
Figure 16: View on Map

Timeline Guidelines
Project Implementation Units (PIUs) are required to submit their data within a period
of 10 days.
PIUs have a window of 5 additional days to make updates to their data. However,
once the data is verified by the Regional Office (RO) and subsequently frozen by the
admin, no further changes will be accepted.
ROs are responsible for ensuring that the PIUs under their supervision adhere to the
timeline and provide accurate data.
ROs must verify the data provided by PIUs within 2 days of its submission.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy