A manufacturer data record, or MDR, turns the production history of industrial heat-transfer equipment into a controlled, usable record. It connects the agreed duty and design basis with drawings, materials, inspections, tests, changes and final release information. Done properly, the MDR gives the plant engineer a clear path from what was ordered to what was supplied.
For Extran work, the required contents still depend on the equipment, purchase order, nominated standard and inspection plan. An MDR is not a generic bundle that should be copied from one job to another. Its index and evidence need to match the actual scope.
That distinction matters during a shutdown. When a cooler needs inspection, repair or replacement, an orderly record can help the duty engineer confirm construction details, previous changes and relevant test evidence before making the next decision.
Why the Production of an MDR Matters
The production of an MDR gives engineering, maintenance, procurement and quality personnel a common project record. Depending on the agreed scope, that record may include approved drawings, material documentation, inspection results, test certificates, change records, non-conformance closeout and release documents. The final index should show what is included without implying that every project requires every possible record.
Equipment type changes the evidence that is useful. A shell and tube unit may require clear identification of the shell, tubes, tubesheet, nozzles, flanges and gasket arrangement. The record should let a competent reviewer connect those parts to current drawings and the applicable inspection evidence.
A usable MDR also preserves context. A test result without an equipment number, procedure reference or acceptance outcome is difficult to apply later. A drawing without a visible revision can send a maintenance planner towards a superseded nozzle position or an obsolete bundle detail. Documentation control prevents those isolated records from becoming the weak point in an otherwise sound job.
Planning the MDR Before Manufacture Starts
MDR planning should begin when the duty, datasheet, purchase order and inspection requirements are being settled. The buyer and supplier need to identify which records are mandatory, which require review, which contain hold or witness points, and which are retained as supporting traceability. This is where the plant, shutdown or duty engineer should make site requirements explicit.
The document register is the practical control. It can list the record, responsible party, planned submission stage, revision and final status. It should also distinguish vendor documents from information the plant must provide, such as process conditions, approved datasheets, site interfaces and acceptance comments. That division reduces duplicated requests and late gaps.
The nominated code needs the same precision. Where a project requires AS 1210, its published scope covers materials, design, manufacture, testing, inspection, certification, documentation and dispatch for pressure vessels. Extran’s live information says mechanical designs can be performed to AS 1210 or ASME VIII, with API 661 used where required. The applicable code must be set by the actual duty and specification, not treated as a blanket certification across all equipment.
Linking Quality Assurance to Real Inspection Points
Quality assurance is strongest when records are generated as the work progresses. The inspection and test plan should connect the fabrication sequence to the checks required at each stage. Hold points, witness points and review points need clear owners, because a signature added after access has been lost cannot recreate the inspection that should have occurred.
For air-cooled exchangers, the record may need to address both the pressure-containing assembly and the air-side package. The agreed scope can cover dimensions, materials, fabrication checks, fan or drive details, calibrated instrument references and the relevant test result. API 661 should only be stated where that project calls for it.
Test documentation needs enough detail to stand on its own. It should identify the item, method, test medium or operating condition where relevant, instrument, duration if specified, acceptance criterion and outcome. Extran’s live site states that pressure and air-movement equipment testing uses calibrated gauges and measurement tools, with results documented on test certificates. The project register should still identify which certificate is required for the particular item.
Managing Materials and Traceability
Material traceability should follow the parts and risks named in the specification. For a pressure-containing assembly, that can mean connecting material documents, part identification, drawings and inspection records. For a non-pressure cooling package, the useful traceability may centre on the core, headers, fins, fans, coatings or replacement components instead.
A gasketed plate unit calls for a different record from a shell and tube exchanger. Plate material, gasket selection, frame arrangement and tightening information may matter to the next service intervention. The MDR should reflect that construction rather than filling space with records that do not help the plant operate or maintain the unit.
Traceability also needs to survive document assembly. File names, equipment numbers and drawing references should use the same identifiers. If a certificate covers more material than was consumed on the job, the record needs a practical connection between the certificate and the fitted part. The aim is an auditable chain, not a large folder with no navigable relationship between its contents.
Handling Changes During the Build
Industrial heat-transfer work rarely remains untouched from first enquiry to release. A nozzle orientation may change, site measurements may correct an assumed interface, a material substitution may be proposed, or an inspection finding may require an accepted repair. The MDR should preserve the approved outcome and the revision that carries it into the finished equipment.
Across the industrial equipment we design, manufacture, supply, service and maintain at Extran, our job tracking system supports traceability of designs, components, manufacturing methods and tests through the production of an MDR. That traceability is most useful when each change is tied to the affected drawing, approval and closeout record.
A non-conformance record should explain the issue, disposition, authority and final verification required by the agreed process. It should not be a vague note that leaves the next engineer to infer whether a repair was accepted. Equally, an informal workshop instruction should not bypass drawing control when it changes the delivered configuration.
Testing Records That Stay Useful
Testing records need to describe the test that actually occurred. A pressure value by itself is not enough. The equipment identity, procedure, calibrated instrument reference, test condition and result need to align with the nominated specification. If a certificate is issued only when requested for the work, that request belongs in the register early rather than at dispatch.
The same principle applies to fan systems. A useful record may identify the fan arrangement, drive configuration, rotation, relevant measurement method and accepted operating result according to the project scope. It should not borrow pressure-vessel language where the real acceptance issue is air movement, mechanical arrangement or site interface.
For repair and refurbishment, pre-work condition and post-work evidence should remain distinct. Fouling, damaged fins, tube leaks, gasket condition and corrosion can affect the repair path, but the current inspection must establish the actual condition. Historical MDR information gives that inspection a stronger starting point without replacing it.
Keeping the File Usable After Handover
The final MDR should have a logical index, current revisions and consistent equipment references. Drawings, certificates and closeout records need names that a plant engineer can search during an outage. Superseded documents can remain where the history is useful, but their status must be unmistakable.
For a process skid, usability includes the interfaces between equipment. The package may combine heat-transfer components, piping, valves, instruments and structural elements according to the job. The MDR structure should help the plant identify the applicable drawing and evidence for each part without assuming the same documentation applies to every component.
At Extran, digital handover does not fix poor structure. One oversized PDF can be as hard to use as an unlabelled folder. A clear index, sensible bookmarks or file hierarchy, visible revisions and searchable names make the record practical. The plant’s own asset number should be included where agreed so the package remains connected to the installed item.
What to Check Before Accepting the MDR
Acceptance starts by checking the MDR against the approved document register, purchase order, inspection and test plan, and delivered item. Missing records are easier to resolve while job files, personnel and workshop evidence are still accessible. The review should focus on identity and consistency rather than page count.
Check that nameplate data, serial numbers, design conditions and drawing references agree. Where the equipment was designed to AS 1210 or ASME VIII, or API 661 was required, the record should make the project-specific basis clear. It should not turn those references into a general statement that every Extran item carries every code.
The same discipline applies to oil-air coolers. Confirm that the record identifies the supplied arrangement and the acceptance evidence called for by the order. Do not assume a test, material certificate, non-destructive examination record or inspection stage belongs in the package unless the code, specification or agreed plan requires it.
Common Documentation Weak Points
Weak MDRs often contain the right document types but the wrong relationships. Common problems include inconsistent equipment numbers, missing revisions, certificates with no part connection, test sheets with no acceptance result, and non-conformance records with no clear closeout. Generic templates can magnify the problem when project fields are left blank.
Late compilation is another risk. If the project waits until dispatch to gather evidence, missing signatures or unidentified material may be impossible to recover properly. Progressive collection allows the quality record to follow the workshop sequence and gives the reviewer time to resolve discrepancies before release.
An industrial radiator rebuild may need a compact but specific record of received condition, agreed work, core or component details, inspections and relevant testing. That is more useful than padding the file with unrelated forms. The document depth should match the duty, risk and purchase requirements.
How MDR Evidence Helps Future Maintenance
A good MDR helps a maintenance team establish what was built before it plans what to do next. Original drawings, materials, gasket details, test evidence and recorded changes can inform a retube, cleaning plan, fan adjustment or replacement decision. The team must still inspect current condition because service, ambient conditions and fouling can alter performance over time.
The record is particularly valuable during a constrained shutdown. It can help the engineer identify dimensions to verify, parts to source, isolation assumptions to challenge and inspection access to prepare. It also reduces the chance that a previous approved change is mistaken for damage or that an obsolete drawing drives the work pack.
Reviewing Supplier and Site Responsibilities
The supplier’s records cannot compensate for missing plant inputs. The site needs to provide the duty, process conditions, operating constraints, interfaces and acceptance requirements needed for the agreed scope. The supplier needs to control the drawings, records and test evidence it is responsible for producing. The document register should make that boundary visible.
Review timing matters as much as ownership. Comments on design or inspection documents need to arrive before the affected work passes the relevant point. During an outage, a late query can hold up a release even when the physical work is complete. Defined review windows and named technical contacts keep the record moving with the job.
Keeping Revision Control Under Control
Revision control should show which information governed manufacture and which documents represent the final supplied condition. A changed tubesheet drilling, nozzle location, fan arrangement or skid interface must flow through the documents that depend on it. Related test and inspection records should point to the correct equipment identity and current basis.
Final assembly is therefore a controlled closeout, not a formatting exercise. The index, document revisions and release status need one last reconciliation against the register. Superseded material can be retained for history, but the accepted revision must be obvious to the engineer opening the file years later.
Making the Record Practical for Maintenance Teams
Maintenance personnel need fast answers to trade questions: which gasket was fitted, whether the bundle was retubed, which drawing shows the installed approach, what was tested after repair, and what condition was recorded before work. A useful MDR makes those answers findable and identifies any limits in the agreed evidence.
The strongest package is not automatically the largest. It is the one that reflects the delivered industrial heat-transfer equipment, preserves project-specific traceability and supports the next competent decision. That is why MDR planning belongs beside the duty, inspection plan and shutdown programme from the start.
Frequently Asked Questions
What Is Included in a Manufacturer Data Record?
The contents depend on the equipment and agreed project requirements. They may include approved drawings, specifications, material documents, inspection records, test certificates, revision history, accepted non-conformance closeout and final release evidence. The document register should define the actual list.
When Should the MDR Be Planned?
Plan it before manufacture or repair begins. Early agreement lets the workshop collect evidence at the right inspection points and gives reviewers time to resolve gaps before access is lost or the equipment is released.
Is an MDR Only for New Equipment?
No. A structured record can also support service, rebuild and repair work when the purchase order, risk or inspection plan calls for it. The contents should describe the work actually performed rather than mimic a new-equipment file.
What Makes an MDR Useful After Handover?
A clear index, current drawings, consistent equipment identifiers, labelled test records and documented changes make the file easier to use. The record should help a plant engineer prepare maintenance or shutdown work without guessing which revision or item a document describes.
Put the MDR to Work
The production of an MDR should finish the documentation decision, not simply gather paperwork. Define the index with the duty and inspection plan, collect evidence as the workshop work proceeds, control changes, then reconcile the final file with the delivered equipment. If an industrial exchanger, cooler, skid or repair needs a project-specific documentation path, Speak with us about the duty, shutdown constraints and required record.
Recent Comments