Skip to Main Content
Concourse & Jira Cloud Portal
ADD A NEW IDEA

Pinned ideas

PINNED Digital Assets - Consider Hierarchy and Tagging to remove repetitive Assets
I can see why the assets repeat themselves but simple use of hierarchy and metadata tagging would allow for different views and sorts without repeating the assets. Also - it would be good to delineate between external assets and internal PwC devel...

All ideas

Showing 1291 of 1291

Support for Phased Engagements

Put Simply Statement: Enable modeling and estimation across multiple phases and years for complex projects. Why it Matters: Supports real-world sales and delivery cycles, especially for ERP and AI projects, increasing accuracy and stakeholder conf...
Garrett Kelchner 5 months ago in  0 Not started

ePro-->Flex Integration

Put Simply Statement: Export hours, staffing plans, and contractor data directly and accurately into Flex Why it Matters: Streamlines budgeting, reduces manual entry, and ensures data integrity across connected systems. What’s Needed: Integratio...
Garrett Kelchner 5 months ago in  0 Not started

Accelerators (AI vs. Non-AI)

Put Simply Statement: Assign opt-in or opt-out savings by work item and distinguish between AI and non-AI tools. Why it Matters: Supports margin management and provides visibility into AI’s impact on project delivery and profitability. What’s Need...
Garrett Kelchner 5 months ago in  0 Not started

Dynamic/Conditional Drivers

Put Simply Statement: Allow a single user input (driver) to impact multiple work items differently. (i.e. a Driver has 1.5x / 2x / 2.5x uplift for Driver 1 / 2 / 3 Allow a driver to have varying impact depending on Project details (i.e. N of Offer...
Garrett Kelchner 5 months ago in  0 Not started

Admin-Defined Calculations

Put Simply Statement: Admins can define custom calculation logic to determine driver impacts. This is the largest POC potential outside of Excel inputs. This would be the single largest innovation to Estimation since its inception. Why it Matters:...
Garrett Kelchner 5 months ago in  0 Not started

Flexible Staffing Structures Metadata

Put Simply Statement: Allow configuration of Teams for each model at the role level and be able to include key staffing metadata (RSR, cost center, platform, equal spread staffing vs normal, potentially Product Code(?) etc) Why it Matters: Ensures...
Garrett Kelchner 5 months ago in  0 Not started

Multi-Team Work Item Assignment

Put Simply Statement: Enable a single work item to be assigned to multiple teams with unique estimation inputs. Why it Matters: Reduces duplication for ERP and complex projects, improving both accuracy and efficiency in estimation. What’s Needed: ...
Garrett Kelchner 5 months ago in  0 Not started

Shared + Cross-Team Roles

Put Simply Statement: Allow configuration of shared roles (e.g., PMO) that apply across teams but are mapped once. Why it Matters: Eliminates duplication, reflects real-world project setups, and simplifies role management in large, cross-team enga...
Garrett Kelchner 5 months ago in  0 Not started

Staffing Mix Selection End User/Admin

Put Simply Statement: End users can choose from pre-defined staffing models (Team Structures) to simplify effort allocation Admins will have the ability to define multiple (N?) pre defined team structures that encompass the different teams involve...
Garrett Kelchner 5 months ago in  0 Not started

Version Control + Iteration History

Put Simply Statement: Let admins create, track, and select estimate versions for flexible, auditable estimation create a full version and iteration, log and tracking history by admin Why it Matters: Supports consistent, quick and ideally iterative...
Garrett Kelchner 5 months ago in  0 Not started