Case Study: How Global Infrastructure Partners Optimized PMO Delivery with Project Plan 1 vs Plan 3 vs Plan 5 vs Project 2024

Background: The Fragmented State of Project Management 🏗️

In the high-stakes world of civil engineering, precision is not just a goal; it is a regulatory requirement. Global Infrastructure Partners (GIP), a mid-sized firm with 450 employees, found themselves at a crossroads in early 2024. Their project management infrastructure was a fragmented ecosystem of spreadsheets, legacy desktop software, and disconnected task lists. As they prepared for a series of large-scale municipal contracts, the leadership team realized their current tooling could not sustain the complexity of modern infrastructure builds.

This case study examines the strategic evaluation of Project Plan 1 vs Plan 3 vs Plan 5 vs Project 2024 conducted by GIP’s IT and Project Management Office (PMO). The goal was to consolidate their workflows into a unified Microsoft environment while balancing the high costs of specialized licenses against the functional needs of different user personas. This transition represents a typical journey for organizations moving from localized project tracking to a centralized, data-driven Project Portfolio Management (PPM) approach.

By the end of this analysis, we will see how GIP moved from a "one-size-fits-all" mentality to a tiered licensing strategy that saved thousands in annual OpEx while significantly improving project delivery timelines. For any IT procurement manager, understanding these nuances is essential for avoiding the common pitfall of over-provisioning expensive Plan 5 seats for users who only need basic task visibility.

The Challenge: Eliminating Data Silos and Resource Conflicts ⚠️

GIP’s primary struggle stemmed from "version chaos." The engineering department relied on standalone installations of Project 2019, while the administrative and marketing teams used Planner or Excel. This created a massive data silo. When a project manager updated a schedule, the stakeholders wouldn't see the changes until a PDF was exported and emailed. This lack of real-time visibility led to a 15% increase in project delays due to resource conflicts.

The challenges were categorized into three main areas:

• Visibility Gap: Executive leadership had no way to view the status of all projects in a single dashboard. They needed a portfolio-level view to decide which bids to pursue.
• Resource Over-allocation: Because schedules lived on individual hard drives, two different project managers would often book the same lead structural engineer for the same week without knowing it.
• Licensing Complexity: The firm was paying for disparate licenses under various agreements. They needed to decide between the modern "Project for the Web" experience and the traditional "Project Desktop" experience, while also considering the benefits of Project 2024 LTSC vs subscription cost models for their remote site offices with limited connectivity.

The firm specifically needed a solution that could handle Microsoft Project for construction management, requiring robust dependencies, lead/lag time calculations, and deep resource leveling capabilities that basic tools simply could not provide.

Options Considered: Decoding the Project Ecosystem 📊

The IT department evaluated four primary paths. Each had distinct implications for user experience and the company's bottom line. During this phase, it was vital to distinguish between "Project for the Web" (the modern, simplified interface) and "Project Online" (the power-user environment).

1. Project Plan 1: The "Lightweight" Entry

This plan was considered for site supervisors and junior engineers. It offers a clean, web-based interface. However, it lacks the Project Plan 3 desktop client features like advanced baselining and local file support. For GIP, this was an excellent candidate for users who only needed to update task percentages.

2. Project Plan 3: The Project Manager's Workhorse

Plan 3 was the most discussed option. It includes the desktop application, which is non-negotiable for complex civil engineering schedules. It also includes "Project Online," allowing for a centralized cloud database of all project files. This was the baseline for anyone responsible for building a schedule from scratch.

3. Project Plan 5: The Strategic Portfolio Tier

GIP’s PMO Director was particularly interested in Project Plan 5 portfolio management value. This tier allows for "Demand Management" (capturing project ideas and ranking them) and "Portfolio Selection" (modeling different project combinations based on budget and resource constraints). While expensive, it promised to solve the leadership's visibility problem.

4. Project 2024: The Perpetual LTSC Option

For their high-security environments and offline field offices, GIP looked at Project 2024. It is important to note that while some vendors might offer OEM keys, GIP strictly adhered to Volume Licensing. They viewed Project 2024 as a way to avoid monthly fees for specific "static" workstations, though they recognized it would not contribute to the real-time cloud reporting they craved.

Decision and Reasoning: The Hybrid Licensing Strategy ✅

After a three-week discovery phase, GIP decided against a uniform rollout. Instead, they adopted a "Hybrid Tiered Model." The reasoning was based on a user-persona analysis rather than departmental silos. This is often the best project management software for engineering firms strategy because it aligns cost with actual tool utilization.

• The PMO & Executives (10 Users): Licensed with Project Plan 5. Reasoning: The firm needed the Portfolio Analysis features to justify their $50M capital expenditure budget to the board. Without the "What-If" modeling in Plan 5, they were guessing at resource capacity.
• Senior Project Managers (40 Users): Licensed with Project Plan 3. Reasoning: They required the desktop client for complex scheduling but didn't need the portfolio-level modeling tools. This saved the company nearly 40% compared to putting everyone on Plan 5.
• Site Leads and Team Members (150 Users): Licensed with Project Plan 1. Reasoning: These users only need to see their assignments and mark them as complete in a browser.
• Offline Field Stations (5 Licenses): Purchased Project 2024 via Volume Licensing. Reasoning: These laptops are used in remote tunneling sites with zero internet connectivity where a subscription-based sign-in would fail.

The core of the decision was migrating from Project Professional to Project Online to ensure that every PM was working off a shared resource pool. This eliminated the double-booking of engineers, as the system now provided a "Red-Line" warning when a resource exceeded 100% utilization across all active projects.

Implementation: From Local Files to Enterprise Cloud 🚀

The rollout was executed in three phases over 90 days. The most critical technical hurdle was the Microsoft Project resource leveling guide implementation. IT had to configure the "Enterprise Resource Pool" in Project Online to reflect the actual skills and availability of the engineering staff.

Phase 1: Foundation (Days 1-30). IT established the Project Online tenant and migrated existing .mpp files from local drives to the cloud. They set up the Power BI Content Pack for Project, which allowed executives to see a real-time "Health Dashboard" without needing to open a single project file.

Phase 2: Training (Days 31-60). Users were divided by license type. Plan 1 users received a 30-minute briefing on the web interface. Plan 3 and 5 users underwent a 3-day deep dive into advanced scheduling, focusing on how to use the desktop client in "Online Mode" to ensure their data synced with the central repository.

Phase 3: Optimization (Days 61-90). The PMO began using the Plan 5 "Portfolio Analysis" module. They input their 2025 project proposals and used the system to identify that they were understaffed in the "Environmental Impact" department by three headcounts, allowing them to hire proactively rather than reactively.

"The transition wasn't just about software; it was about shifting from 'My Project' to 'Our Portfolio.' The tiered licensing made the ROI clear to the CFO immediately." — GIP IT Director.

Results: Data-Driven Success and ROI 📈

Six months after the full implementation, GIP conducted a post-mortem to measure the impact of their new licensing structure. The results were quantifiable and transformative for their operations.

• 22% Increase in Resource Utilization: By using the centralized resource pool, GIP reduced the "idle time" of senior engineers who were previously hidden in siloed schedules.
• $14,000 Annual Savings: By correctly identifying Plan 1 users instead of defaulting everyone to Plan 3, the firm avoided unnecessary subscription costs while still maintaining data integrity.
• Zero Scheduling Conflicts: The "Enterprise Resource Leveling" features virtually eliminated the issue of double-booking staff across different municipal contracts.
• Faster Executive Reporting: The time required to produce monthly project status reports for the board dropped from 4 days to 15 minutes, thanks to the automated Power BI integration.

The Project Plan 1 vs Plan 3 vs Plan 5 vs Project 2024 debate was settled: the subscription model provided the collaboration needed for the majority of the firm, while the LTSC version served its purpose for edge cases. GIP now operates as a truly integrated firm, capable of taking on larger, more complex projects with a leaner administrative overhead.

Lessons Learned: A Blueprint for IT Procurement 💡

The journey of Global Infrastructure Partners offers several vital lessons for any organization evaluating Microsoft’s project management suite:

1. Don't Over-License: Roughly 70% of your users likely only need Plan 1. Don't pay for the desktop client (Plan 3) unless the user is actually building and maintaining complex logic-linked schedules.
2. Portfolio Management is a Specific Skill: Plan 5 is incredibly powerful, but only if you have a PMO capable of managing "Demand" and "Portfolio Prioritization." If you don't have those processes, Plan 3 is sufficient.
3. Beware of Standalone Keys: Always procure through official Volume Licensing or CSP channels. GIP avoided the risks of unauthorized keys, ensuring their software remained compliant and supported by Microsoft.
4. Internet Connectivity Matters: While the cloud is superior for collaboration, always keep a few perpetual licenses (like Project 2024) in your back pocket for "dark sites" or offline field work where a SaaS sign-in is impossible.

Ultimately, the choice between Project Plan 1 vs Plan 3 vs Plan 5 vs Project 2024 isn't about which is "better"—it's about which combination creates a seamless flow of data from the field to the boardroom.

📊 Comparison