60 mins
Easy
Plan
The aim is to decide if standard project views are needed, and if so, how they should be set up.
Help you set up standard project views for your organization, and if you can replace your initial workspace hierarchy by using codes to group your projects.
There's a lot information associated with every project and that can be hard to manage. Start dates, end dates, phases and status. It all needs to be tracked and managed effectively.
Project views can make finding and managing projects, for all users, much easier.
If you're a previous P6 user, it can be tempting to use workspaces to replicate your Enterprise Project Structure (EPS). However, it's best practice and our recommendation to keep your workspace hierarchy as simple as possible.
So instead of using workspaces to recreate your EPS, consider creating an EPS code in a view.
This Play requires application administrators, project managers, and anyone else that will be essential in deciding how projects are set up and managed within Primavera Cloud.
Be mindful of having too many opinions. Groups of 4-5 tend to work best. More people means more discussion and fewer decisions. You can get feedback on decisions made with a wider audience later on.
Start by reading this guide that provides a simple overview of Primavera Cloud views. It'll help the group get on the same page and better understand what decisions need to be made.
What you need for your views.
Have a conversation with your project managers to determine what information needs to be tagged to each project at a high-level. Here are a few examples:
~ Project Phase
~ Project Status
~ Start Date
~ Manager
~ Enterprise Project Structure (EPS)
Don't limit yourself to what's already available. You can always create your own columns (configured fields) and codes. We will address this in a later step.
Making the views more manageable.
Group the metadata you determined earlier by a general theme.
Having too many columns or filters applied to one view can get messy, so determine if more then one view is needed.
For example: A Projects by Status View can contain all of the columns and metrics needed to understand the progress of a project at a high-level.
After you've determined how you'd like to arrange your views, move onto the next step.
Setting up what you need for your views.
During this step, you'll create all of the codes or configured fields you want to bring into your views as columns or use to group and filter your projects by.
This will be done at a workspace level.
For example, if you're creating views for all projects under the production workspace, you'd create the codes and configured fields within the production workspace.
Use these step-by-step guides to create codes and configured fields:
~ Learn how to create a code
~ Learn how to create a configured field
Now it's time to get creating.
Now you're ready to start creating standard views for your team. As you're doing so, here's a reminder on the different buckets you can place a project view under:
Are private and only accessible to the user who created them.
Are saved at the project level and can be accessed by other members of the project.
Are saved at the workspace level and are available to all users in the workspace.
If you're creating a standard view for everyone to use, place it under workspace.
Here a few helpful step by step guides to help you accomplish these tasks:
~ Assign a code to a project
~ Add a column to a view
~ Create a filter
~ Apply a filter
~ Configure grouping options.
That's the end of the Play.
Have your users take a look at what has been set up and provide feedback or any recommendations. Make any necessary tweaks, then go-live.
Ask your team to follow these steps, test the views, and report back.
1. Log into OPC https://primavera-us2.oraclecloud.com/web/
2. Click on the object selector (dropdown next to the Oracle logo)
3. Select projects, then select view all projects to open up the project list
4. Use the view dropdown to click through the view(s) created by your organization
5. Write down any notes for improvement and send those to your OPC admins
That's it!
You've decided what project views are important for you and your team, and set them up in Primavera Cloud.