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. |
...
Term | Meaning | Aliases | |
---|---|---|---|
1 | Account | [Term being phased out - see Buyer] | Buyer |
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. 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 requests | |
4 | ATM | Approach To Market - see Request (e.g. for tender) | Request |
5 | Boss | A User with full access rights for a Buyers include manage the Buyer's security and configuration settings within 360 | |
6 | Buyer | An organisation that publishes requests (e.g. for tender) | |
7 | Buyers' Portal | The website (https://360users.apetsoftware.com.au/) in which Requests are configured and Responses assessed | |
8 | Consensus Evaluator | An Evaluator who can combine the assessments of all other evaluators into a final assessment | |
9 | CoP | Conditions of Participation | |
10 | Dependency Question | A Hidden Questionnaire Item that is made visible, based on the Response to another Question | |
11 | Dependency Section | A Hidden Section that is made visible based on the Response to another Question | |
12 | A method of exchanging messages ("mail") between people using electronic devices | ||
13 | Evaluator | A User who can assess responses to a Request | |
14 | Expiry Date | The calendar day on which a project/role/Job, etc. ends | |
15 | Hidden Question | A Question that is hidden to Providers but visible to Evaluators | Private Question |
16 | Hidden Section | A Section that is hidden to Providers but visible to Evaluators | Private Section |
17 | Hierarchical Request | A Request that has a Leading Part and at least one Subordinate Part | |
18 | Industry | A group that Providers can join to receive Adcom notifications | |
19 | Job | [Term being phased out - see Request] | Request |
20 | Job 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 | Approver |
21 | Job Manager | A User who can create Requests and control all access rights within their Requests | Manager |
22 | Job 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 |
23 | Leading Part | A 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 |
24 | Non-Price | The tallied score given by Evaluators for Providers Responses. It does not consider Price. See VFM below. | |
25 | NPV | Net Present Value | |
26 | Opener | A User authorised to open a Request and release it for evaluation | |
27 | Panel | A group of Providers with similar qualifications | |
28 | Panel Manager | A User who can create Panel and controls all the access rights within their Panel | |
29 | Panel Name | A unique name of the Panel | |
30 | Password | A string of characters that is use to verify the identity of a User during the authentication process | |
31 | Phone No | String of specific numbers that a Phone User can dial to reach another mobile phone | |
32 | Price | The net present value of the Provider's goods and/or services | |
33 | Provider | A provider of goods and/or services | |
34 | Providers' Portal | The website (https://360providers.apetsoftware.com.au/) in which Requests are published and Responses submitted | |
35 | Question | A Questionnaire Item in a Request that usually needs a Response before a Provider can Submit their tender/quote/etc. | Questionnaire Item |
36 | Ranking | The comparison of one Provider against others. For example, the Provider with the lowest price is ranked first for price ranking, and the one with best value for money is ranked first for VFM ranking. | |
37 | Region | A location in Australia used for outreach and categorisation purposes | |
38 | REOI | Request for Expressions Of Interest | Request |
39 | Relative Weight | A value that ranks the importance of a Weighted Section or a Weighted Question against others | |
40 | Reporter | A User who can run evaluation reports | |
41 | 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 |
42 | Response | A Provider's answer to a Question consisting of a compliance statement, response text, and/or response attachments | Answer |
43 | RFGP | Request For Grant Proposals | Request |
44 | RFI | Request For Information | Request |
45 | RFO | Request For Offers | Request |
46 | RFP | Request For Proposal | Request |
47 | RFQ | Request For Quote | Request |
48 | RFS | Request For Service | Request |
49 | RFT | Request For Tender | Request |
50 | Score | An Evaluator's assessment of a Provider's Response | |
51 | Section | A group of Questions | |
52 | 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. | |
53 | Standard 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 |
54 | Start Date | The calendar day on which a project/role/Job, etc. initiates | |
55 | Subordinate Part | A Request that providers can choose to (or not to) respond to within a Hierarchical Request. Each Subordinate Part can be assessed by a separate evaluation team | Child Request Child Section |
56 | Super User | A User who can assist Buyers and Providers with technical difficulties. A Super User can log-in using as a User to help diagnose problems | |
57 | User | Someone who can sign in to 360 - either through:
| |
58 | User name | A unique sequence of characters used to identify a User and allow access to a 360 Portal | |
59 | VFM | Value For Money | |
60 | Weighted Question | A Question that receives Evaluator's Scores and contributes to Provider's Rankings | |
61 | Weighted Section | A Section that contributes to a Provider's Ranking |
...