Tender App Overview

This article provides key details that relate to the Tender app and will impact your understanding of specific functionality when using the app. 

Your organisation's system may differ from the examples shown in the help centre. Various elements such as fields, page layouts, labels and process flows may have been customised to fit your organisation's specific needs and workflows. This guide remains a valuable resource for navigation and understanding of the Atamis system. The core functionalities remain consistent so you can apply general principles and instructions provided here to your own customised environment. For clarity on the specifics of your particular setup, please contact your system's administrator or super user.

Depending on the customisations undertaken when implementing your Atamis system, you may see different titles for list views and tabs from this guide. In older versions of the Atamis product, your system may refer to Tender App records as "Projects & Contracts". For consistency, we will refer to the Tender App using the Sourcing to Contract standard terminology for the object. 

 

System Overview

Atamis Tender provides a number of eSourcing templates that are linked to procurement processes. Clients often modify these templates to fit their individual processes and procurement steps. 

Templates provide a baseplate of tasks, requirements and documents for all new tenders created from the template helping drive efficiency and consistency in your procurement approach. 

The Sourcing to Contract object is the standard object used within the Tender app. This object has a number of record types that serve different purposes when working within Atamis Tender. It's important to ensure you choose the appropriate record type to ensure the fields and functionality are appropriate when you are creating new Sourcing to Contract records. 

The most commonly used record type by end-users is the Procurement record type. All other record types are used for specific scenarios, are generated through an action executed from a Procurement record type, or are used by your internal super users. 

 

Below is an overview of the various Sourcing to Contract record types and their objective:

Record Type Name Overview
Contract A contract record which is created post-award from a tender
Framework A framework with multiple suppliers that users can call off
Procurement Used for tender projects taking place through the Atamis system, pre-contract award
Procurement Template A template used as a baseplate for procurement projects
Supplier Assessment Records for questions and attachments sent to suppliers
Supplier Assessment Template A template containing questions and attachments for undertaking supplier assessments
Tender Used only to track the progress of tenders that are taking place outside of the Atamis system

 

 

Updated

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request