Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
Put Simply:
Team Builder and Flex are now the source systems for deployment and engagement staffing. Concourse should read from these systems during pursuit of a project to enable Staff Modeling for effort estimation. During delivery, these systems should automatically add / remove users to the project space in Concourse based on deployment changes.
Why It Matters:
Improves user experience: Users added to an engagement during delivery will automatically be added to the right Concourse Workspace and therefore other integrated systems. Reducing the time to onboard
Enables effort estimation: future effort estimations will automatically update as Flex Budgets are filled out with both named and unnamed resources to model cost to deliver during pursuit work
Supports adoption: A simpler workflow encourages more consistent use
What’s Needed:
Flex integration: Utilize FlexID's relationship to the SF Opp ID to locate the draft Flex and connect to the Concourse Project. API call / GIF event subscription to receive async updates to staffing in Flex
Team Builder integration: similar use case as above. May be redundant but may provide additional details.
UI updates: split team members display in the Concourse WS during pursuit to show Opportunity Team from Salesforce who has access to the Pursuit Project Space and the Delivery Team Members list pulled from Flex / Team Builder
Estimation features: Utilize the named and unnamed resources from Flex as the staffing model against scope effort estimates. Use against a baseline / template staff mix from Concourse to show divergence from optimum and recommend updates to the staffing in Flex if possible
Activation logic: during project activation, add the named members of Flex / Team Builder to the Project workspace
Fallback: Continue supporting manual entry of IDs for edge cases.
Questions:
Is it possible to track if the user is no longer in the firm through flex?
If yes, do we need to show their name during pursuit phase or duing transition?
Post activation, can we mark users as inactive, if they are no longer with the firm, by monitoring flex?
How to control roles and permissions (should we assign default permissions)?
Garrett Kelchner
For global - territories are interested in Team builder (and hoping this AHA record can be tagged so that it shows up in our global query). Also as a reminder global doesn't use Flex Forecast at this time as well (US only)
FYI - Rose Leeson who looks after EMEA adoption also raised a question re: Team Builder integration. Below were the details she outlined in a note so global is keen on understanding possible timing timing
In brief: Team Builder is an out-of-the-box product by Certinia, a trusted third-party supplier, and runs on the cloud-based Salesforce platform. Essentially it's our new Global resourcing and deployment Solution replacing TalentLink (and other alternatives). The system interacts with GFS SAP4 HANA, Skyhive and also US 'Sync Layer' and a future Global Instance.
In terms of global contacts that may be helpful, Nareen has shared the following contacts in case you want to dicuss: Juliet Hops is also UK sponsor CC'd in - Global contacts: Naomi Foster, Prasanna Rajagopalan, Hilda Klune