How to configure a hierarchical request (e.g for tender) in the 360 internal portal

Owned by Asfand Khan
Last updated: Dec 14, 2023
2 min read

Requests for tender (RFTs) sometimes ask for large and/or complex projects to be delivered.  In these circumstances many providers will only be able to tender for part of the work.  One option to receive many and varied tenders (which often results in better value for money), is to break the request up into multiple parts.  For example, instead of one RFT to build a road, you might break it up into landscaping, road surfacing, and road lighting.

360 supports multi-part tenders with Hierarchical Requests (previously called Parent - Child Jobs).

With a hierarchical request, all providers respond to the leading part but only the providers who are capable of delivering the requested goods and services respond to each subordinate parts.

The evaluation of the leading part influences the evaluation of the subordinate parts to a configurable extent.  For example, if the provider receives 100% for all criteria in the leading part, they may have automatically achieved 20% of the total attainable score for a subordinate part whereas another organisation who received a 50% score the leading part can, at best, only achieve 90% for the same subordinate part.

There are two types of hierarchical requests:

  • Standard (this help article)

    A Request that contains at least one Request that is evaluated separately as a Subordinate Part.

    Differs from a Single Submission Hierarchical Request because each Subordinate Part is configured as an entirely separate Request that can potentially have an entirely separate team of Evaluators.

  • Single Submission (see How to add a section (group of questions) to a request in the 360 internal portal)

    A Request that contains at least one Section that is evaluated separately as a Subordinate Part.

    Differs from a Standard Hierarchical Request because each part is contained in a single Request.  A standard Hierarchical Request's Subordinate Parts can contain multiple sections whereas, in a Single-Submission Hierarchical Request, each Subordinate Part is just one set of questions.


Step-by-step guide

To create a standard hierarchical request:

  1. Sign-in to https://360users.apetsoftware.com.au/ as a Request Manager
  2. From the home page:
    1. Select Requests
    2. Click New Request
  3. Configure this request as the leading part by following the steps in How to create a new request (e.g. for tender) in the 360 internal portal
  4. For each subordinate part:
    1. From the home page:
      1. Select Requests
      2. Click New Request
    2. Under the heading Part 1: Request Title and Key Information, select the Leading Part (the request you created in step 3)
    3. Enter the Leading Part Percentage

    4. Amend the Request Name for the subordinate request

      The name of a subordinate part must start with the leading part's name

    5. Complete the remaining steps found in How to create a new request (e.g. for tender) in the 360 internal portal

At this point, the hierarchy has been created and each part is ready for further configuration.

All parts need to be fully configured before a hierarchical request can be published


Terms of use

Visitors who are not part of the intended audience (as specified on this space's overview page) may not access this content.
If you are accessing content for which you are not the intended audience you may not use it for any purpose.
As private content can be published in error, if in doubt, you are not the intended audience.
Copyright © - Sharrowlane Pty Ltd