Module of the Month: “Project Request Portal”

In the latest of our “Module of the Month” series Cora Systems’ Account Manager Enda Smith takes a look at the Cora PPM Portal Request Portal.

The Portal is a flexible framework that provides access to data contained in Cora PPM to a wider audience.

It was developed as a companion site to Cora PPM with the aim of driving communication between external stakeholders and Cora PPM users. The Portal provides users with a secure, tailored, view of information, working as a “self-service” channel so stakeholders can quickly track and interrogate the progress of projects, programs and ideas within Cora PPM.

The Portal has multiple applications, for example it is used by local and national Government agencies as a means of displaying project information to the public. Similarly in the Healthcare sector, IT Departments use the Portal to display project information securely outside of Cora PPM. For Life Sciences, it has been a useful tool for capturing project ideas and for pipeline management. It can also be used to share information with external engineering and construction contractors, and as a C-level Dashboard for EPMO operations.

Today I will look at how the Portal can be used to manage the Project Request process.

The Project Request feature in Cora PPM puts a consistent, value-based set of approval criteria in place in order to decide which helps organizations select and approve projects that will fulfil their strategic goals. I will now give a brief high-level overview of the process and will go into more detail in my Webinar (see below). 

Cora PPM brings control and a variety of capabilities to the process for creating new projects including:

  • The Ability to configure a Smart Form to capture key information about the Project Request.
  • Optional Approvals via Workflow.
  • The Ability to programmatically move, rename and update Project Requests through workflow.
  • Full separation of unapproved projects from the programme structure.
  • A “My Project Requests” Widget, where Users can manage submitted project requests.

The Project Request Process can be configured so that all Users in an organization can use the feature or it can be restricted to users with specific Roles.

When creating a Project Request the process begins with a User selecting one of the Templates they have access to. Templates are also used in conjunction with the Project Request feature to allow Users to easily create new Projects that are pre-populated with key data. If an organization has a standard set of tasks or requirements that are always complete for particular Projects, they can be included in an associated Template, which means that all projects which are created from that template will automatically have those tasks/elements. This ensures consistency and save the Project Manager the effort of having to create a structure each time they start a new project. The start dates of all the tasks in the Projects you create from a template will be automatically adjusted based on the start date of the new Projects and the constraint option that you choose. Templates are simply Projects that are located in a particular place. The user create templates in exactly the same way as any other type of Projects. An organization can create as many templates as they need, but they should ensure that they have at least one for each Project Type that they will be using.

The Project Request process in Cora PPM utilizes Cora’s Workflow functionality so that the request can be approved by one or more Users e.g. a Program or Portfolio Manager. The Workflow can be configured so that approvers receive a notification when a Request is submitted and that it can only proceed to the next step when it has been approved.

Until they are approved, Project Requests do not ‘live’ within the programme structure. Therefore, users who will be approving a project (depending on how the workflow is set up) will need a profile on the project in order to view it. Project Requests can also be moved, renamed and updated through workflow.

The Project Request Portal Dashboard, shown above, displays the status of Projects and what stage they are at, the status of the Projects which have been requested, the names of Users who requested Projects (the Sponsors) and the number of requests they made. If a workflow is configured for a template but does not contain an approval step, the Project Request will be automatically approved.

As mentioned above Cora PPM users can view and manage their Project Requests using the My Project Request Widget on My Dashboard. Expanding the widget, displays a grid with the Project Name, Request Status and Submitted Date. Clicking the Project Name, opens the Project Request Smart Form (if the request has not been approved) or the Project Dashboard (if the request has been approved).

Find out more

This is just a small example of the capabilities of the Cora Portal. Join Enda on June 11th for a live demonstration of the Module. Sign up via the form here.

Alternatively, you can find out more about how Cora PPM can help your organization by visiting our PPM Page where you can watch a video Tour of the platform, see Client Testimonials and much more.

Previous Module of the Month

January: “Executive Dashboard and Snapshot Reports” | Blog | On-Demand Webinar

February: “Workflow” | Blog | On-Demand Webinar

April: “Forms and Registers” | Blog | On-Demand Webinar

Join our Mailing List

Enter your details to receive our updates direct to your Inbox

Read our Privacy Statement here