What goes on a supplier data requirements list?
A supplier data requirements list sets out, one row per deliverable, every document and data item a supplier must hand over for the scope being bought, and how each one must be delivered. A typical line carries a unique document number, the document title and type, a document-type or category code, the responsible discipline, the required format and number of copies, the review class it needs (for approval, for review, or for information only), and the submission stage tied to a project milestone: with the bid, on award, before manufacture, at factory acceptance test, on delivery, and in the final data dossier. The deliverables themselves range across general arrangement drawings, single-line diagrams and schematics, datasheets, calculations, inspection and test plans, test and inspection certificates, operation and maintenance manuals, spare parts lists and as-built documentation. On a power, electrical or heavy-industry package the list often runs to dozens of items, and on a large package to hundreds, so it is a scope in its own right.
What is the difference between an SDRL, an SDL, a VDRL and an MDR?
The core difference is that the SDRL is the buyer's requirement while the SDL is the supplier's response. The SDRL (supplier data requirements list), sometimes issued as a VDRL or VDR (vendor data requirements list), is the buyer-issued list of documents a supplier must produce, with the required formats, review classes and due dates. The SDL (supplier document list) is the supplier's reply: their committed register of exactly which documents they will provide and when, prepared to satisfy the SDRL. Two further terms sit alongside them. The master document register (MDR) is the live register that then tracks each required document through its revisions and review status during execution. The manufacturing record book (MRB), also called the data dossier or final documentation, is the compiled book of all the completed and accepted documents handed over at the end. In sequence: the SDRL (or VDRL) names the requirement, the SDL commits to it, the MDR tracks it, and the MRB is the finished evidence.
Where does the SDRL appear in a tender, and what must a bidder do with it?
In a tender, the SDRL usually appears as an attachment to the request, referenced inside the conditions of contract and the scope of work, and it is frequently listed among the returnable schedules a bidder must address. At bid time a bidder has to do four things with it: confirm it can produce every listed deliverable in the required format, to the required review class and timing; price the documentation effort, because preparing, submitting and revising that many documents is real engineering time, not a free add-on; flag any line it cannot meet or takes exception to, as a departure or qualification; and, where asked, return a populated supplier document list committing to submission dates. Treating the SDRL as a formality is how documentation hours go missing from a bid.
Why the SDRL is where bid teams quietly lose scope
The SDRL defines documentation effort, review cycles and milestone dates that need to be carried in the bid. Elora Grid can help identify these requirements from the tender and organise the documents each supplier needs. Keep the SDRL and your document register together, and check that the drawing revision, issue purpose, owner and due date match what you intend to send.