Mongo Database
Awarded
Key facts
- Closing date
- Not stated by the buyer
- Buyer's estimated value
- Not stated The buyer's own estimate, not income to you.
- Procedure
- Direct award
- Notice type
- Contract award notice (UK6)
- Suitable for SMEs (per buyer)
- Yes
Decision brief
Taken from the buyer's published notice (shown as written, shortened where long). Tenderpatch has not added to or interpreted it. Always read the official documents before bidding.
- How bids will be scored
- Not stated in the notice.
- Conditions of participation (what you must show)
- None published in the notice. They may be in the tender documents.
- Contract length and extensions
- Period not stated.
- How to submit
- Not stated in the notice.
- Tender documents
- No document links in the notice. Use the official notice link.
New to public tenders? Plain-English guide to this page
- Framework
- An agreement that sets terms for work the buyer may order later, often from several suppliers. The value shown usually covers the whole agreement, not one job.
- Open for bids / closing date
- You must submit by the closing date and time, normally through the buyer's own online portal. Late bids are normally refused.
- Clarification questions
- A deadline for asking the buyer questions about the tender. It is earlier than the closing date.
- Conditions of participation
- What the buyer asks suppliers to show before they can be considered, such as experience, insurance or accreditations.
- Bids are scored on
- How the buyer will compare bids, usually a split between price and quality. A 60/40 split in favour of quality means the cheapest bid will not necessarily win.
- Lots
- A tender can be split into parts. You can often bid for only the lots that suit you.
- Area (ITL)
- The buyer names an official statistical area for where the work is, not a street address. Check the tender documents for the actual sites.
- UK4 and other notice codes
- Official codes for the type of notice. A "tender notice" means bids are being invited.
General explanations written by Tenderpatch, not part of this notice.
Description
At Aula, MongoDB is a core part of the platform's underlying infrastructure and acts as the centralised database used to store and manage records generated across the platform. Every interaction and action carried outby users within Aula is recorded within MongoDB. This includes user authentication, posts, submissions, resources, discussions, collaborative activity and other interactions carried out by students and educators across institution instances.
Aula's experience relies on seamless interaction between students, educators and content, and MongoDB supports this by storing the structured yet flexible data that enables these interactions to take place. Every action within the platform generates data, whether it is a student posting a submission, an educator sharing resources, or users collaborating through discussions. MongoDB's document-based model allows this information to be captured and stored in real time without being restricted by rigid table structures.
This flexibility is important for Aula because different institutions and courses can have different requirements and structures. MongoDB's schema-less design allows Aula to adapt and evolve its data model without requiring complex migrations or significant downtime. This enables the platform to continue developing and introducing changes without unnecessarily disrupting teaching and learning.