Mansycom to Deploy Bentley Cloud PDMIS for Jaipur Metro Phase 2
Large metro projects do not run on drawings alone. They run on decisions, approvals, site records, design revisions, inspection notes, model updates, and thousands of small exchanges that must stay traceable from day one to handover.
Mansycom has been awarded the customization and deployment of a Digital Project Data Management Information System for Jaipur Metro Phase 2, Package 2C-01. The work order comes from IL&FS Engineering and Construction Co. Ltd., and the platform will run on Bentley Infrastructure Cloud (BIC).
For Mansycom, the award builds on nearly two decades of BIM and digital project management work in Indian metro rail. For Jaipur Metro Phase 2, it sets up a connected working environment where the owner, consultants, contractors, and project teams can use the same current information instead of chasing updates through disconnected files, email threads, and local folders.
The goal is simple: give a complex urban infrastructure project a reliable digital backbone from the first design submissions to final handover.
The award supports a digital-first approach for Jaipur Metro Phase 2
Jaipur Metro Phase 2 is one of the city’s major urban mobility investments. The Orange Line is planned as a 42.8 km north-south corridor from Todi Mod to Prahladpura, with 36 stations. The project is being developed by Rajasthan Metro Rail Corporation, formerly Jaipur Metro Rail Corporation.
Package 2C-01 is the first civil package of Phase 2. It has been awarded to the Ceigall India and Sam India Builtwell joint venture.
The package covers:
A 12 km elevated viaduct along Tonk Road
10 elevated stations from Prahladpura to Pinjrapole Gaushala
A depot spur line
A construction period of 34 months
A package of this scale generates a large volume of project information long before the first full span is cast. Design teams prepare drawings and models. Review teams issue comments. Contractors submit method statements, shop drawings, inspection requests, and progress updates. Site teams record tests, checks, measurements, and non-conformities. Project leaders need a current view of work fronts, approvals, risks, and dependencies.
When that information lives in different places, project control becomes harder.
A drawing may be updated, but a site team may still be working from an older revision. A design comment may sit in one email chain while the response is attached elsewhere. A progress report may show one status, while the latest inspection record tells a different story. None of these issues are unusual on large projects. They are the everyday friction points of engineering and construction delivery.
A cloud-based PDMIS reduces that friction by giving the project a governed, traceable place to create, submit, review, approve, and retrieve information.
Why Package 2C-01 needs a common data environment
Elevated metro construction is linear, repetitive, and highly coordinated. Work moves along a corridor, but each location depends on many parallel activities.
A single stretch of viaduct can involve:
Utility mapping and diversion records
Pile and foundation details
Pier and pier cap drawings
Segment casting and erection data
Temporary traffic management plans
Station interface drawings
Quality records and test certificates
Safety checks
Land and access constraints
Daily and weekly progress updates
The complexity rises around stations. An elevated station is not just a platform and roof. It can include concourse levels, access structures, lifts, escalators, fire systems, electrical rooms, signaling interfaces, telecom rooms, drainage, architectural finishes, and public access provisions. Each discipline produces its own data, and each depends on the others staying aligned.
On a corridor like Tonk Road, construction must also work within a live urban setting. That means site teams need tight coordination around traffic movement, local access, utilities, staging areas, and public safety. Delayed information can delay work. Conflicting information can create rework.
The PDMIS is intended to give the project one connected source of current information. In practice, that means the same platform can support:
Design submissions and approvals
BIM model coordination
Request for information workflows
Inspection and testing records
Drawing revision control
Construction progress tracking
Document transmittals
Issue logs and action tracking
Final records for handover
This matters because digital project control is not only about storing documents. It is about knowing what is current, what is pending, who is responsible, what changed, and what decision was made.
What the PDMIS will do on Bentley cloud
The PDMIS for Jaipur Metro Phase 2, Package 2C-01, will serve as the project’s single source of truth. Every stakeholder will be able to work from a common environment where the latest approved information is available and older versions remain traceable.
That role is especially important during the review and approval process. Metro projects involve many layers of review. A drawing may move from contractor submission to consultant review, then through comments, resubmission, approval, and construction release. If each step is handled manually, teams can lose time checking version numbers, searching inboxes, or confirming whether a file has been superseded.
A project data system changes the way that cycle works. Submissions can follow agreed workflows. Review comments can stay attached to the right document or model. Approval status can be visible without asking multiple people for updates. Project leaders can see bottlenecks before they affect site progress.
The platform is expected to support the project across the full construction information cycle:
Project need | How a cloud PDMIS helps |
Current drawings and models | Gives teams controlled access to the latest approved versions |
Review and approval tracking | Records submissions, comments, responses, and approval status |
BIM coordination | Keeps model data connected with project workflows and records |
Site quality records | Links inspections, test reports, and non-conformities to the right work package |
Progress reporting | Brings field updates and project controls into one shared view |
Handover preparation | Preserves approved records, as-built information, and closeout documents |
The value is not only in the software. It is in how the system is configured for the way this package will actually be delivered. Mansycom’s role includes customization and deployment, which means the PDMIS must reflect project-specific workflows, document types, review responsibilities, approval paths, reporting needs, and access controls.
Mansycom’s role combines BIM experience with project delivery needs
Mansycom brings long experience in BIM and digital project management for Indian metro rail projects. That background matters because a metro PDMIS cannot be a generic file repository. It must support the working habits, approval routes, and contractual requirements of infrastructure delivery.
A useful PDMIS needs to answer daily project questions quickly:
Which drawing is approved for construction?
Which review comments are still open?
Which station drawings are pending resubmission?
Which RFIs are critical for the next work front?
Which inspection records are complete?
Which documents are required for upcoming milestones?
Which model version was used for a specific coordination decision?
These questions look simple, but they become difficult when data is spread across disconnected systems. A well-configured cloud environment makes the answers easier to find and easier to trust.
Mansycom’s deployment work is expected to connect the technical platform with project discipline. That includes structured metadata, naming rules, permissions, workflow routing, dashboards, and records management. Each of these setup choices affects how easily teams can use the system under real construction pressure.
For example, metadata may sound like a back-end detail, but it is one of the keys to finding information fast. A drawing tagged by station, chainage, discipline, package, status, and revision is much easier to manage than a file stored under a loose folder name. The same applies to inspection records, RFIs, design models, and reports.
The system must also support different types of users. A design reviewer may need detailed model access and comment tools. A site engineer may need approved drawings, checklists, and inspection forms. A project controls team may need progress dashboards and submission trends. A client representative may need a high-level view of status, delays, and pending approvals.
A PDMIS works best when each user sees what they need without losing the structure required for audit and handover.
How cloud project data improves construction control
A digital-first construction approach gives teams better control over time, quality, cost, and risk. It does this by making project information easier to trust and easier to act on.
Faster reviews reduce waiting time
Design and construction teams often lose days because submissions and comments move slowly. A cloud workflow can show where a document is, who is reviewing it, how long it has been pending, and what action comes next.
This does not remove the need for technical review. It makes the review path clearer. Teams spend less time asking for status updates and more time resolving the actual engineering questions.
On a 34-month construction schedule, even small gains in review cycle time can matter. Faster approvals can help keep work fronts active and reduce idle time caused by pending information.
Version control reduces rework
Rework often starts with a simple issue: someone used the wrong information. In metro work, that may mean an outdated reinforcement drawing, a superseded alignment note, or a model that no longer reflects a design change.
A governed PDMIS helps prevent that by marking document status clearly and maintaining revision history. Teams can see whether a drawing is submitted, under review, approved, rejected, or superseded. The older data does not disappear, but it stays controlled.
That traceability is useful during construction and after completion. If a question arises months later, the project team can check which version was approved and when.
BIM becomes more useful when it is connected to workflows
BIM has the most value when it supports decisions. A model that sits apart from the project’s approval and document process can still help visualization, but it may not fully support construction control.
When model data is part of the project information environment, teams can connect geometry, documents, comments, and approvals more effectively. This helps with coordination across civil, structural, architectural, MEP, signaling, telecom, and station systems.
For an elevated metro corridor, BIM coordination can help teams identify potential clashes, check interfaces, and understand construction sequencing. The PDMIS provides the order around that data so teams do not lose the link between model updates and formal project decisions.
Site records become easier to verify
Quality control on a metro package depends on reliable site records. Inspection requests, test reports, non-conformities, approvals, and corrective actions all need to be recorded in a way that can be checked later.
If those records are digital and linked to locations, work packages, and document references, they become more useful. A project manager can see whether a section is ready for the next activity. A quality engineer can check whether required tests were completed. A handover team can assemble closeout records with less last-minute searching.
This is especially useful for repeated construction elements such as piles, piers, pier caps, segments, and station components. Repetition creates efficiency, but only if records remain consistent and easy to compare.
Progress reporting becomes less dependent on manual chasing
Progress data often passes through several layers before it becomes a report. Field teams submit updates. Planning teams check them. Managers compare them with milestones. Client teams review the results.
A PDMIS can reduce manual chasing by bringing updates into a shared structure. Project leaders can view progress by location, discipline, station, or work package. They can also compare progress against pending approvals, open RFIs, and unresolved quality issues.
This does not replace field judgment. It gives that judgment a clearer data base.
What a single source of truth means in practice
The phrase “single source of truth” is often used loosely. On a project like Jaipur Metro Phase 2, it has a practical meaning.
It means a site team does not need to guess which drawing is valid. It means a reviewer can see the full comment history. It means an owner’s representative can check progress against approved records. It means the contractor can submit, revise, and track documents through a defined process. It means closeout teams can find what they need when the project moves toward handover.
A strong single source of truth has four features.
Clear ownership
Each document, model, inspection, and workflow needs an accountable owner. Without ownership, data can become stale. With ownership, users know who must act and who can approve.
Controlled access
Not every user needs the same permissions. Some users create submissions. Some review. Some approve. Some only view. Access control protects the record while still giving teams the information they need.
Status visibility
A file name alone does not tell the whole story. The system should show status clearly, such as draft, submitted, under review, approved, approved with comments, rejected, or superseded.
Audit history
Major project decisions need a record. A PDMIS should preserve who submitted an item, who reviewed it, what comments were made, what changed, and when approval took place.
These features help the project maintain control as the volume of information grows.
Why the timing matters for Jaipur Metro Phase 2
Digital systems have the most value when they are set up early. If a project waits until construction is already moving at full pace, teams may have to migrate scattered documents, retrain users midstream, and correct inconsistent naming or approval habits.
For Package 2C-01, setting up the PDMIS at the early stage creates a stronger foundation. Workflows can be agreed before submission volumes become heavy. Document rules can be applied from the start. BIM model exchanges can follow a predictable process. Inspection and quality records can build in the right structure from the first major activities.
That early discipline also supports handover. Handover problems often begin years before completion, when records are created without enough structure. If approved data, inspection records, test results, and as-built information are maintained throughout the project, final closeout becomes easier to manage.
For a public infrastructure project, this matters beyond construction. Metro assets must be operated and maintained for decades. Clear records from construction can support future maintenance, upgrades, inspections, and asset management.
Digital project management is becoming standard for metro rail
Indian metro rail projects have grown in scale, complexity, and delivery speed. Cities need new corridors to move people more efficiently, but urban construction comes with high pressure. Agencies and contractors must manage traffic disruption, safety, stakeholder coordination, design changes, cost control, and public expectations.
Digital project management is becoming a core part of that response.
The shift is not only about adopting cloud software. It is about changing how project teams handle information. Instead of treating documents as separate files, teams manage them as controlled project records. Instead of relying on informal status checks, teams use shared workflows. Instead of waiting until handover to organize data, teams build the record as work progresses.
Metro projects are especially suited to this approach because they combine repetitive construction with complex interfaces. A corridor contains many similar elements, but it also includes stations, depots, utilities, rail systems, and civil structures that must work together. That mix requires both standardization and careful coordination.
A cloud PDMIS supports both.
What success should look like for the project team
A successful deployment will not be measured only by whether the platform goes live. It will be measured by whether teams use it every day to make work clearer, faster, and more controlled.
Signs of success may include:
Faster access to approved drawings and models
Fewer disputes about document versions
Clearer visibility into pending approvals
Better tracking of RFIs and review comments
More consistent quality and inspection records
Easier progress reporting across stations and viaduct sections
Stronger handover records at the end of the package
The system should also make collaboration more predictable. Each stakeholder may have different responsibilities, but all should work from the same structured record. That reduces confusion and helps decisions move through the project with traceability.
For Mansycom, the Jaipur Metro Phase 2 PDMIS award adds another major metro assignment to its digital delivery portfolio. For the project, it creates the information management framework needed to support a busy elevated corridor through design coordination, construction execution, and handover.
FAQ
What is the scope of Jaipur Metro Phase 2, Package 2C-01?
Package 2C-01 covers a 12 km elevated viaduct along Tonk Road, 10 elevated stations from Prahladpura to Pinjrapole Gaushala, and a depot spur line. The construction period is set at 34 months.
Who awarded the PDMIS work to Mansycom?
The work order was awarded by IL&FS Engineering and Construction Co. Ltd. for Jaipur Metro Phase 2, Package 2C-01.
What will the PDMIS be used for?
The PDMIS will provide a shared cloud environment for project documents, BIM models, submissions, approvals, RFIs, inspection records, progress updates, and handover data.
Why does a metro project need a cloud-based PDMIS?
A metro project produces thousands of records across many teams. A cloud-based PDMIS helps keep current information accessible, controls revisions, tracks approvals, and reduces delays caused by scattered data.
How does BIM fit into the PDMIS?
BIM models can be connected with document workflows, review comments, and project records. This helps teams coordinate design, check interfaces, and maintain traceability as the project moves into construction.
A connected foundation for delivery
Jaipur Metro Phase 2, Package 2C-01 will demand close coordination across design, construction, quality, planning, and project controls. The scale of the corridor, the number of stations, and the pace of a 34-month schedule make information management a delivery-critical function.
Mansycom’s deployment of a Bentley cloud PDMIS gives the project a structured way to manage that information. It brings drawings, models, reviews, inspections, and progress data into one governed environment, so teams can act on current information and maintain a clear record of decisions.
For a major urban metro corridor, that digital foundation can make the difference between simply collecting project data and using it to keep delivery on track.
