We do not object to you linking directly to the information that is hosted on the Railnet and no prior permission is required for the same. However, we would like you to inform us (using the Contact Us option) about any links provided to our site.

We do not permit our pages to be loaded into frames on your site. The pages must load into a newly opened browser window of the user. Please visit Link to Us page for more details.

Your privacy is important to us Anyone can generally visit the site without revealing Personal Information unless he chooses to provide such information.

We collect and store the following information about user visits for statistical purpose:

• The internet domain of users services provider from which user access our website.
• The type of browser and operating system used to access our site.
• Date and time user accessed our site.
• The pages/URLs visited
• If the visitor reached this website from another website, the address of that referring website.

We make no attempt to link these addresses with the identity of individuals visiting our site unless an attempt to damage the site has been detected.

You would find various sections of this website links to other websites/portals. These links have been provided to enhance your user experience and are presented for information purposes only. IRTPMS is not responsible for the contents, usability, accessibility, reliability including cyber security related issues, if any, of the linked websites and does not necessarily endorse the views expressed in them. We cannot guarantee that these links will work all the time and we have no control over availability of linked pages.

Material featured on this Portal may be reproduced free of charge after taking proper permission by sending a mail to us. However, the material has to be reproduced accurately and not to be used in a derogatory manner or in a misleading context. Wherever the material is being published or issued to others, the source must be prominently acknowledged. However, the permission to reproduce this material shall not extend to any material which is identified as being copyright of a third party. Authorization to reproduce such material must be obtained from the departments/copyright holders concerned.

These terms and conditions shall be governed by and construed in accordance with the Indian Laws. Any dispute arising under these terms and conditions shall be subject to the exclusive jurisdiction of the courts of India.

When deploying large applications with many constituent components to IRTPMS Portal there can be a large number of steps required to install each component and configure required resources. The Solution Installer automates many of these deployment tasks. The Solution Installer requires a Portal Application Archive (PAA) file to describe how to install the application and to provide the installable artefacts.

The PAA file format is used to handle deployments ranging from applications with a small number of configuration steps to large scale enterprise portal solutions. The directory structure of the PAA file is important to the Solution Installer when determining how to install a specific artifact, for example, how to handle shared library files. In addition, the files also play a significant role in determining the installation steps as any extension points required for installation must be specified in file local to the component.

Daily Automatic backup system established for portal database and files with entire content.

Though all efforts have been made to ensure the accuracy and currency of the content on this Portal, the same should not be construed as a statement of law or used for any legal purposes. It accepts no responsibility in relation to the accuracy, completeness, usefulness or otherwise, of it’s content. Users are advised to verify/check any updated information available with the concerned Government department(s) and/or source(s), and to obtain any appropriate professional advice before acting on the information provided in the Website.

• In no event will the Government of India be liable for any expense, loss or damage including, without limitation, indirect or consequential loss or damage, or any expense, loss or damage whatsoever arising from use, or loss of use, of data, arising out of or in connection with the use of this Portal.
• Catalogs and Links to other websites that have been published through the IRTPMS Platform are provided for public convenience only. The Portal is not responsible for the content or reliability of linked websites and does not necessarily endorse the view expressed within them. We cannot guarantee the availability of such linked pages at all times.
• Catalogs featured on the IRTPMS if reproduced, have to be accurate and are not to be used in a derogatory manner or in a misleading context. Wherever the material is being published or issued to others, the source must be prominently acknowledged. However, the permission to reproduce this material shall not extend to any material which is identified as being copyright of a third party.
• Authorization to reproduce such material must be obtained from the departments/copyright holders concerned, wherever applicable.
• These terms and conditions shall be governed by and construed in accordance with the Indian Law. Any dispute arising under these terms and conditions shall be subjected to the exclusive jurisdiction of the courts of India.
• The catalogs and information available through the Portal are available under terms described in the “license” metadata element of individual dataset records except where otherwise noted.

All content is reviewed by the Editorial Board before authors develop a complete article or essay to help ensure that content is focused on translating interdisciplinary sustainability research to a broad audience and aligned with the IRTPMS Portal’s mission.

Abstracts: The Editorial Board will comment on whether a complete page (full manuscript) is likely to be accepted. Also, the Editorial Board provides suggestions to develop a full manuscript.

Peer Review: Two in-field reviewers, an out-of-field reviewer, and a member of the NAIR editorial board conduct a double-blind review.

• Content will be assessed for accuracy, quality, and relevance to the IRTPMS Portal.
• Final decisions to accept the article will be made following the submission and review of the completed content, such as an article manuscript.
• Article manuscripts are rated in three areas to determine acceptance:

1. Potential for idea transfer and development across fields;
2. Immediate use for practitioners and policy makers; and
3. Clarity and readiness for print.

Constructive Comments: The Editorial Board will provide Developers with consolidated comments from the review process, with suggested improvements for accuracy and clarity, to remove jargon, and to shorten length, if necessary. Some articles may undergo a second round of peer review after changes have been made.

Timeline: Content is reviewed on a rolling basis.

• The MJS editorial board responds to authors within six weeks of submission of content.
• Most content will be published online within six months of submission.

While each approval process will differ based on its purpose or the organization’s specific requirements, there are some general tasks that you will likely include when designing your own. These include:

• Submission: An approval process usually begins with someone submitting something. You’ll need to create a submission portal where users go to submit their content. Think about including a submission receipt option, so submitters have a record of their activity.
• Assign Approvers: The approval process hinges on someone else (not the submitter) approving the work, so you’ll need to identify the person or people who have the final say. If your process has multiple approval levels, define who will approve which aspects of work at each level.
• Set Permission Levels: Define the level of authority each user should have. Most systems have features to delineate among viewer, editor, and administrator permissions, so you can control who edits, rejects, or approves submissions.
• Set Due Dates: As with any project, it’s important to set deadlines to keep your workflows moving and prevent work backlogs.
• Automatic Alerts and Notifications: A program that automatically sends alerts and notifications about the status of a submission can help expedite workflow. Automatic alerts may be approval or rejection notifications, update requests (where the approver requests that the submitter makes changes to the original submission), or a simple status update alerting users that work is advancing to the next step in the process. Submissions may have to go through multiple rounds of edits before they are approved, so automatic alerts and notifications can ensure that items are accomplished quickly and that everyone is aware of the current status.
• Record/Log: Having a record of every step in the approval process is one of its greatest benefits for increasing transparency and ensuring consistency. If you plan on using an automated solution, look for a program that offers the following capabilities:
  • View User History: See who has made changes, to what, and when.
  • Lock Record: This will make the record uneditable, so that no user can change the log of actions.
  • Edit Record: In some cases, you might want the record to be kept editable – for instance, if you made a mistake or need to keep certain information private from other parties.
  While we’re on the topic of automated workflows, it’s important to note that some programs also offer additional functionality that can create a more customized feel, or help disrupt some of the inflexibility that can come with automation. Some of these functions include
• Email Templates: Some platforms have built-in email templates for notifications. This functionality adds a personalized touch and also provides a space for enhanced communication.
• Edit Requests: Similar to update requests, edit requests specifically notify a submitter when the submission has been (temporarily) rejected and that it requires changes before it can be approved.
• Task Lists: It can be helpful to build task assignment into the approval process, allowing each employee to clearly see their responsibilities, and informing management of resource allocation.

Many of these elements will be present in the approval process you design, regardless of the specific project or type or organization. In the next section, we’ll discuss the software programs that allow you to build approval processes and workflows, and additional features to consider.