Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Tip

Every software product has its own language - key words that have special meanings.

360's terms and definitions are found in the list below.

Definitions

Term

Meaning

AliasesBuyer
1

Account

[Term being phased out - see Buyer]

An organisation’s grouping of Users - either in the Buyers' Portal or the Providers' Portal

2

ADCOM

An extension pack for licensed Buyers who want to advertise and communicate through 360 with additional outreach and communication options (both internal and external)

3
Associated ...Associated Buyer.  Associated Provider. 

Addendum

A message from the Request Manager to all Providers (or a sub-set) with additional information about a Request

4

Association

A relationship managed by a Buyer between

itself and a Provider
An active association allows the provider to browse the buyer's public Requests and the buyer to select the provider for invitation-only requests45

the Buyer’s Account a Provider’s Account

5

ATM

Approach To Market - see Request (e.g. for tender)

Request
6

Boss

A User with full access rights for a Buyers include manage the Buyer's security and configuration settings within 360

6
7

Buyer

An organisation that publishes requests (e.g. for tender)

7
8

Buyers' Portal

The website (https://360users.apetsoftware.com.au/) in which Requests are configured and Responses assessed

8

9

Category

A classification that is used for subscription notices:

  1. Type of request (e.g. RFT)

  2. A price bracket for the likely contract (e.g. $0 to $150,000)

  3. A product or service (e.g. Software Development)

  4. A trade of skill (e.g. Carpenter)

  5. A location of region (e.g. Canberra)

10

Category-based Request

A Request that contains at least one Category Section that is evaluated separately from other Category Sections.

11

Category Section

A Section within a Category-based Request that is evaluated separately from other Category Sections.

Category Sections are used to establish Panels of Associated Providers within Categories (e.g. a Panel of carpenters)

12

Clarification

A request for more information from an Evaluator to a Respondent

13

Consensus Evaluator

An Evaluator who can combine the assessments of all other evaluators into a final assessment

9
14

CoP

Conditions of Participation

10
15

Dependency Question

A Hidden Questionnaire Item that is made visible, based on the Response to

another

a Trigger Question

11
16

Dependency Section

A Hidden Section that is made visible based on the Response to

another

a Trigger Question

12
17
Email

Direct Message

A

method of exchanging messages ("mail") between people using electronic devices13

private message sent between the Request Manager and a Participant

18

Enqury

A message sent from a Provider to the Request Manager

19

Evaluator

A User who can

assess responses 15

evaluate Responses to a Request

14Expiry DateThe calendar day on which a project/role/Job, etc. ends
20

Hidden Question

A Question that is hidden to Providers but visible to Evaluators

Private Question
21
16

Hidden Section

A Section that is hidden to Providers but visible to Evaluators

Private Section
22
17Job

Hierarchical Request

A Request that has a Leading Part and at least one Subordinate Part

18IndustryA group that Providers can join to receive Adcom notifications19Job[Term being phased out - see Request]Request2021

Job Manager

A User who can create Requests and control all access rights within their Requests

Manager22Job
23

Award Approver

A User who can check that a Request is ready for release and grant the Job Manager the rights to publish the Request

Approver23
24

Release Approver

A User who can check that a Request is ready for release and grant the Job Manager the rights to publish the Request

Approver
25

Leading Part

A

The first Sections within a Category-based Request that

providers must respond to within a Hierarchical Request.  The evaluation team's assessment of the Leading Part contributes to each Subordinate Part with a configurable percentage.

The Leading Part usually explains the main goals of the procurement activity and contains questions that allow Evaluators to make a high-level assessment prior to conducting a fine-grained review of the responses to Subordinate Parts.

Parent Request

24Non-PriceThe tallied score given by Evaluators for Providers Responses.  It does not consider Price.  See VFM below.25

are used to evaluate the criteria that apply to all Child Sections.

26

Leading Request

The first Request within a Hierarchical Request that is used to evaluate the criteria that apply to all Subordinate Request.

27

NPV

Net Present Value

26
28

Opener

A User authorised to open a Request and release it for evaluation

27
29

Panel

A group of Providers with similar qualifications

28
30

Panel Manager

A User who can create Panel and controls all the access rights within their Panel

29
31
Panel Name

Participant

A

unique name of the Panel30PasswordA string of characters that is use to verify the identity of a User during the authentication process31Phone NoString of specific numbers that a Phone User can dial to reach another mobile phone32

Provider that registered their interest in responding to a Request

32

Pre-submission Rule

A Condition of Participation that must be met and verified before a Provider can submit their Responses

33

Price

The net present value of the Provider's goods and/or services

33
34

Provider

A provider of goods and/or services

34

35

Provider Manager

A User who can create Associations between their Account and a Provider’s Account

36

Providers' Portal

The website (https://360providers.apetsoftware.com.au/) in which Requests are published and Responses submitted

3536
37

Question

A Questionnaire Item in a Request that usually needs a Response before a Provider can Submit their tender/quote/etc.

Questionnaire Item
38

Questionnaire

The collection of questions and instructions that Respondents use to prepare their Submission and Evaluators use to evaluate the Responses

39

Ranking

The comparison of one

Provider

Submission against others.  For example, the

Provider 38

Submission with the lowest price is ranked first for price ranking, and the one with best value for money is ranked first for VFM ranking.

37RegionA location in Australia used for outreach and categorisation purposes
40

REOI

Request for Expressions Of Interest

Request39
41

Relative Weight

A value that ranks the importance of a Weighted Section or a Weighted Question against others

40
42

Reporter

A User who can run evaluation reports

4142
43

Request

An approach to market (ATM) that can be in many specialised forms - Request for Tender (RFT), Request for Quote (RFQ), Request for Expression of Interest, Public Tender, Select Tender, etc.

Job
44

Request Manager

A User who can create Requests and control all access rights within their Requests

45

Response

A Provider's answer to a Question consisting of a compliance statement, response text, and/or response attachments

Answer43

46

Respondent

A Provider that responded to a Request

47

RFGP

Request For Grant Proposals

Request
48
44

RFI

Request For Information

Request
49
45

RFO

Request For Offers

Request46
50

RFP

Request For Proposal

Request47
51

RFQ

Request For Quote

Request48
52

RFS

Request For Service

Request
53
49

RFT

Request For Tender

Request
54
50

Score

An Evaluator's assessment of a Provider's Response

51
55

Section

A group of Questions

52
56
Single

Submission

Hierarchical Request

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.

53Standard Hierarchical Request

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.

Parent-Child Request

54Start DateThe calendar day on which a project/role/Job, etc. initiates55Subordinate Part

The collection of all Responses submitted by a Respondent

57

Subordinate Request

A Request that providers can choose to (or not to) respond to within a Hierarchical Request.  Each Subordinate

Part

Request can be assessed by a separate evaluation team

Child Request

Child Section

56

Super User

A User
58

Technical Support

simplylogical.net staff who can assist Buyers and Providers with technical difficulties

.  A Super User can log-in using as a User to help diagnose problems5759

59

User

Someone who can sign in to 360 - either through:

58User nameA unique sequence of characters used to identify a User and allow access to a 360 Portal
60

VFM

Value For Money

60
61

Weighted Question

A Question that receives Evaluator's Scores and contributes to

Provider's Rankings61

Submission’s Ranking

62

Weighted Section

A Section that contributes to a

Provider's

Submission’s Ranking

Info

Please contact us (support@simplylogical.net) to update this list if we use a term that is unfamiliar or strange.

...

...


Page Properties
hiddentrue


Related issues