FAT Data Package Checklist: Raw Data, Videos, Calibration Records, and Photos That Buyers Should Request

For custom scientific instruments, Factory Acceptance Testing is not just a final demonstration before shipment.

It is the buyer’s last structured opportunity to confirm that the delivered system matches the agreed technical scope before the equipment leaves the supplier’s facility.

This matters especially for:

• Helmholtz coil systems
• electromagnets
• magnetic field drivers
• excitation power supplies
• Hall measurement systems
• VSM systems
• cryogenic temperature systems
• custom Magnet & Field Systems
• integrated laboratory platforms

A short video showing that the equipment powers on is useful.

But it is not enough.

For serious procurement, buyers should request a complete FAT data package that includes raw data, photos, videos, calibration records, serial numbers, test conditions, software versions, deviation records, and a clear pass/fail summary.

This article provides a practical FAT data package checklist for laboratories, universities, R&D teams, and procurement departments purchasing magnetic and cryogenic test systems.

1. What Is a FAT Data Package?

A FAT data package is the set of documents, files, images, videos, and measurement records generated during Factory Acceptance Testing.

It should help answer several questions:

• Was the correct system tested?
• Was the test performed under agreed conditions?
• What instruments were used?
• What raw data was collected?
• What results were calculated?
• Did the system pass or fail each test item?
• Were there deviations?
• Were corrective actions taken?
• What version of hardware and software was shipped?
• What should be checked again after installation?

For formal procurement, the FAT package becomes part of the technical delivery record.

2. FAT Is Different from a Sales Demonstration

A sales demonstration shows that the equipment can perform selected functions.

A FAT confirms whether the ordered system meets the agreed technical and functional requirements before shipment.

IEC 62381:2024 defines requirements and checklists for Factory Acceptance Test, Factory Integration Test, Site Acceptance Test, and Site Integration Test activities, and notes that these checklists can be adapted to the specific equipment or system being tested.

For buyers of scientific equipment, the key point is simple:

FAT should be based on agreed requirements, not only on a supplier’s preferred demonstration.

3. Why Buyers Should Request the FAT Package Before Shipment

Once a large custom system is shipped overseas, solving problems becomes harder.

After shipment, the buyer may face:

• Customs delays
• local handling limits
• missing accessories
• installation uncertainty
• damaged parts
• wrong cable routing
• software mismatch
• unclear acceptance responsibility
• site magnetic background
• limited supplier access
• time-zone support issues

A complete FAT data package reduces these risks.

It gives the buyer a technical baseline before the equipment leaves the factory.

4. FAT Data Helps Separate Factory Issues from Site Issues

If a system works at the factory but shows problems after installation, the FAT data package helps identify where the issue may have appeared.

For example:

• Factory field-current data is normal, but site field data is abnormal.
• Factory software version is different from installed software.
• Factory wiring photos show a different connector arrangement.
• Factory test used one probe position, but site test used another.
• Factory calibration file was not loaded after installation.
• Factory cooling flow was higher than site cooling flow.

Without FAT records, troubleshooting becomes guesswork.

With records, supplier and buyer can compare evidence.

5. What a Complete FAT Data Package Should Include

A useful FAT data package may include:

• FAT protocol
• FAT checklist
• pass/fail summary
• raw measurement data
• processed results
• field mapping files
• screenshots
• photos
• videos
• calibration certificates
• instrument serial numbers
• software version
• firmware version
• configuration file
• wiring records
• inspection photos
• deviation list
• corrective actions
• packing photos
• final shipment configuration

Not every project requires every item.

But the buyer and supplier should agree on the package before production is complete.

6. FAT Protocol: The Starting Point

The FAT protocol defines what will be tested.

It should include:

• Project name
• equipment model
• serial number
• quotation or PO reference
• agreed technical specifications
• test items
• test method
• test equipment
• pass/fail criteria
• required files
• responsible persons
• date
• location
• document revision

The protocol should be reviewed before testing begins.

If the buyer expects field mapping, continuous operation, software API testing, or cryogenic temperature stability testing, those items must be written into the FAT scope.

7. FAT Checklist: Do Not Rely on Memory

The FAT checklist converts the protocol into a practical test record.

A good checklist should show:

• Item number
• test description
• expected result
• actual result
• pass/fail status
• comments
• operator name
• reviewer name
• date
• related file name

This is especially important for complex systems with many subsystems.

For example, a three-axis Helmholtz coil may need separate checklist sections for:

• X-axis coil
• Y-axis coil
• Z-axis coil
• power supplies
• software
• field probe
• safety interlocks
• cable labels
• documentation
• packing

8. Raw Data: The Most Important Evidence

Raw data is often more valuable than a polished final report.

Buyers should request raw data for key tests such as:

• Field-current curves
• field uniformity mapping
• power supply stability
• current ripple
• temperature stability
• Hall reference sample measurements
• VSM loop measurements
• cryogenic cooldown curves
• resistance readings
• sensor calibration checks
• long-duration operation logs

Raw data allows the buyer to review:

• Test sequence
• noise
• drift
• outliers
• repeatability
• stabilization time
• calculation method
• possible filtering

A final PDF alone may hide useful diagnostic information.

9. Processed Results Should Be Linked to Raw Data

Processed results should not appear without traceable raw data.

For each calculated result, the FAT package should make clear:

• Which raw file was used
• which calculation method was used
• whether background correction was applied
• whether data was filtered
• whether averaging was used
• which units were used
• which pass/fail rule was applied

This is important for:

• Field uniformity
• Hall mobility
• carrier concentration
• VSM magnetic moment
• temperature stability
• power supply drift
• field noise
• current ripple

A result is easier to trust when the calculation path is visible.

10. Calibration Records: What Buyers Should Request

For test instruments used during FAT, buyers should ask for calibration records or calibration status.

This may include:

• Field probe
• gaussmeter or teslameter
• current meter
• voltmeter
• thermometer
• temperature sensor
• oscilloscope
• power analyzer
• reference resistor
• reference sample
• pressure or flow meter
• balance for VSM sample mass

NIST explains that metrological traceability requires a documented unbroken chain of calibrations, each contributing to measurement uncertainty.

For ordinary commercial equipment procurement, buyers may not always require national-laboratory-level calibration for every item.

But they should know what instrument was used, whether it was calibrated, and whether its accuracy is suitable for the FAT purpose.

11. Traceability Does Not Automatically Mean Fitness for Purpose

Buyers sometimes ask only:

“Is the test instrument traceable?”

That is not enough.

NIST also emphasizes that traceability alone does not guarantee fitness for purpose; the measurement uncertainty must be small enough for the intended measurement need.

For example:

• A calibrated field probe may still be unsuitable if its range is wrong.
• A calibrated thermometer may still be poorly placed.
• A calibrated current meter may not capture ripple.
• A calibrated reference sample may not match the system’s measurement range.

The FAT package should connect calibration records to actual test requirements.

12. Test Instrument List

The FAT data package should include a list of instruments used.

For each instrument, record:

• Instrument name
• manufacturer
• model
• serial number
• calibration date
• calibration due date
• measurement range used
• uncertainty or accuracy statement, if available
• role in the FAT

This helps future troubleshooting.

If the buyer repeats the test on site with different instruments, differences can be understood more easily.

13. Photos: What Should Be Photographed

Photos are simple but powerful.

A good FAT package should include photos of:

• Complete assembled system
• nameplate and serial number
• coil labels
• pole gap setting
• power supply front panel
• control cabinet
• cable connections
• grounding points
• cooling connections
• field probe position
• sample holder
• reference sample mounting
• software screen
• safety interlocks
• accessories
• spare parts
• packing condition

Photos prove configuration.

They also help the buyer reassemble, inspect, and troubleshoot the system after delivery.

14. Photos of Probe Position Are Especially Important

For magnetic systems, probe position can change the result.

A field reading without a probe-position photo is incomplete.

Request photos showing:

• Probe active area location
• probe axis orientation
• distance from coil center or pole face
• fixture used to hold the probe
• coordinate system
• mapping grid reference
• cable routing
• whether the probe is inside the sample volume

This matters for:

• Helmholtz coil center field
• electromagnet pole gap field
• field uniformity mapping
• three-axis vector testing
• low-field calibration
• acceptance reports

A calibrated probe in the wrong position does not verify the right field.

15. Videos: Useful but Not Sufficient

Videos can show that key functions were actually performed.

Useful FAT videos may include:

• System startup
• software connection
• current ramping
• field response
• polarity reversal
• three-axis field command
• electromagnet pole gap check
• cooling system operation
• emergency stop test
• cryogenic cooldown trend
• sample mounting
• VSM sample vibration
• Hall measurement sequence
• data export
• packing process

However, videos should supplement raw data and reports.

A video without numerical records is only a visual demonstration.

16. Video File Naming Matters

FAT videos should be clearly named.

Example:

• FAT_01_System_Startup.mp4
• FAT_02_X_Axis_Field_Response.mp4
• FAT_03_Polarity_Reversal.mp4
• FAT_04_Emergency_Stop_Test.mp4
• FAT_05_Packing_Before_Crate_Close.mp4

Poorly named files become difficult to use later.

Good file names help the buyer, supplier, and customs or internal receiving team identify the content quickly.

17. Screenshots: Software Proof

Screenshots should capture:

• Software version
• connected devices
• communication status
• active recipe
• calibration file
• field setpoint
• current readback
• measured value
• alarm status
• data export screen
• configuration page
• user interface language
• license status, if relevant

Screenshots are especially useful for remote support.

If a problem appears later, the supplier can compare the delivered configuration with the installed configuration.

18. Configuration Files Should Be Included

Many modern systems depend on software configuration files.

The FAT package should include backups of:

• Calibration tables
• field-current coefficients
• correction matrices
• axis polarity settings
• current limits
• voltage limits
• ramp settings
• communication parameters
• temperature controller settings
• sensor curves
• user recipes
• safety parameters
• data export templates

NASA’s configuration management guidance emphasizes preserving configuration records and maintaining traceability throughout the product life cycle.

For scientific equipment, this principle is very practical: if a configuration file is lost or changed, the system may no longer behave like the FAT-tested system.

19. Version Control: Hardware, Software, Firmware

The FAT package should record version information for:

• Main system hardware
• power supply firmware
• controller firmware
• software version
• driver version
• PLC program version
• temperature controller firmware
• motion controller firmware
• calibration file version
• manual revision
• wiring diagram revision

Version mismatch is a common source of confusion after shipment.

A buyer should know exactly which version was tested and delivered.

20. Serial Numbers and Nameplates

Record serial numbers for:

• Main system
• each coil axis
• electromagnet
• power supply
• control cabinet
• field probe
• temperature controller
• sensors
• chiller
• motion stage
• data acquisition unit
• reference sample
• software license dongle, if any

This is important for:

• Warranty
• customs
• inventory
• maintenance
• remote support
• future calibration
• spare parts

Photos of nameplates are better than typed numbers alone because they reduce transcription errors.

21. FAT Data for Helmholtz Coil Systems

For Helmholtz coil systems, the FAT package should include:

• Coil resistance for each axis
• axis wiring check
• positive and negative polarity test
• field-current curve
• center-field verification
• background field reading
• uniformity mapping, if required
• X/Y/Z axis verification
• cross-axis component data
• power supply current stability
• ramp test
• software control test
• field probe calibration record
• coil geometry photos
• cable connection photos
• fixture position photos
• safety interlock test

For three-axis systems, each axis should be tested separately before combined vector-field testing.

22. FAT Data for Electromagnets

For electromagnets, buyers should request:

• Pole gap measurement
• pole diameter and pole cap photos
• field-current curve at agreed gap
• maximum field test
• positive and negative field test, if bipolar
• remanence or zero-field check
• uniformity data, if required
• cooling operation
• coil temperature trend
• power supply voltage and current
• ramp rate test
• interlock test
• emergency stop test
• field probe position photos
• final pole gap record
• packing protection photos

If the electromagnet has adjustable pole gap, FAT data should clearly state which gap was tested.

23. FAT Data for Power Supplies and Magnetic Field Drivers

For power supplies, the FAT package may include:

• Output current range
• output voltage range
• current stability test
• ripple or noise test
• ramp rate test
• polarity reversal test
• load test
• protection test
• overcurrent behavior
• overvoltage behavior
• communication test
• analog control test
• readback accuracy
• cooling fan or water cooling check
• front panel photos
• rear terminal photos
• software screenshots

For magnet power supplies, the test should use a representative load when possible.

A no-load test does not prove real coil-driving performance.

24. FAT Data for Hall Measurement Systems

For Hall systems, request:

• Reference sample ID
• sample thickness and geometry
• contact configuration
• I–V contact check
• zero-field resistance
• positive and negative field data
• current reversal data
• Hall voltage raw data
• carrier type result
• carrier concentration
• mobility
• sheet resistance
• temperature condition
• software calculation settings
• reference sample mounting photos
• field probe or magnet verification data
• repeat measurement data
• data export files

A Hall FAT package should include both raw electrical data and final calculated results.

25. FAT Data for VSM Systems

For VSM systems, the FAT package may include:

• Reference sample ID
• sample mass
• sample dimensions
• mounting method
• empty holder background
• raw moment data
• hysteresis loop data
• field sweep condition
• saturation moment result
• coercivity and remanence
• repeatability test
• centering or positioning record
• noise check
• field calibration record
• sample holder photos
• software screenshots
• exported data files

If the system includes temperature options, room-temperature FAT alone may not verify the full temperature scope.

26. FAT Data for Cryogenic Systems

For cryogenic systems, buyers should request:

• Cooldown curve
• base temperature achieved
• temperature stability data
• sensor serial numbers
• sensor calibration curves
• temperature controller settings
• heater response
• vacuum level, if applicable
• cold head or cryostat photos
• wiring continuity
• sample holder photos
• temperature sensor mounting photos
• safety interlock test
• alarm behavior
• warm-up procedure
• chiller or compressor data, if applicable

For cryogenic magnetic systems, also include magnetic field testing at relevant temperature conditions if included in the agreed scope.

27. FAT Data for Cooling Systems

Cooling data may be required for:

• Water-cooled electromagnets
• high-current coils
• power supplies
• chillers
• cryogenic compressors
• temperature control systems

Record:

• Inlet temperature
• outlet temperature
• flow rate
• pressure
• chiller setpoint
• fan operation
• leak check
• flow switch test
• overtemperature protection
• continuous-run temperature trend

A system that passes a short field test may still fail a long-duty test if cooling is not verified.

28. FAT Data for Safety Functions

Safety functions should be tested and documented.

This may include:

• Emergency stop
• door interlock
• cooling flow interlock
• overtemperature shutdown
• overcurrent protection
• overvoltage protection
• communication loss behavior
• software limit
• hardware limit
• warning lamp
• alarm relay
• manual reset
• safe ramp-down

For each safety test, record:

• Test condition
• expected response
• actual response
• pass/fail result
• recovery method

Do not accept a safety checklist with only “OK” and no explanation.

29. Deviations and Nonconformities

A professional FAT package should not hide deviations.

If something differs from the original scope, document:

• Deviation number
• description
• affected specification
• root cause, if known
• corrective action
• retest result
• buyer approval, if required
• open or closed status
• effect on shipment

A small deviation may be acceptable.

An undocumented deviation becomes a future dispute.

30. Corrective Action Records

If a FAT item fails and is corrected, keep the record.

For example:

• Cable polarity corrected
• software parameter updated
• sensor curve reloaded
• loose connector tightened
• field probe position adjusted
• cooling flow increased
• power supply limit reset
• data export template corrected

The package should show:

• What failed
• what was changed
• who approved the change
• what retest was performed
• whether the final result passed

This is more trustworthy than pretending no problem ever occurred.

31. Packing Photos Are Part of the FAT Package

For overseas delivery, packing records matter.

Request photos of:

• Accessories before packing
• labels on each accessory
• protective foam
• coil frame supports
• anti-rust protection
• moisture protection
• shock indicators, if used
• crate exterior
• crate markings
• packing list matched to contents
• final sealed crate

Packing photos help if:

• A crate is damaged
• accessories are missing
• customs inspection occurs
• the buyer needs to reassemble the system
• shipping insurance claim is required

For large modular systems, packing documentation is not an afterthought.

32. Accessory List and Spare Parts Record

The FAT package should include an accessory list.

Examples:

• Cables
• connectors
• adapters
• field probe holder
• sample holder
• reference sample
• screws and tools
• software dongle
• USB drive
• manuals
• spare fuses
• cooling hoses
• interlock jumpers
• calibration certificate
• power cord
• shipping brackets

Each item should be identified clearly.

Missing small accessories can delay installation even when the main equipment is perfect.

33. Data File Format Should Be Agreed

Raw data should be delivered in usable formats.

Useful formats may include:

• CSV
• TXT
• XLSX
• PDF report
• PNG or JPG photos
• MP4 videos
• JSON configuration files
• software-native data files

Buyers should avoid receiving only screenshots when raw numerical data is needed.

A screenshot may be useful for evidence, but it cannot be easily reanalyzed.

34. File Naming and Folder Structure

The FAT package should be organized.

A practical folder structure may be:

• 01_FAT_Protocol
• 02_Checklist_and_Summary
• 03_Raw_Data
• 04_Processed_Results
• 05_Calibration_Records
• 06_Photos
• 07_Videos
• 08_Configuration_Files
• 09_Safety_Tests
• 10_Packing_Records
• 11_Deviations_and_Corrections
• 12_Final_Release

This structure makes it easier for engineering, procurement, QA, and receiving teams to review the package.

35. The FAT Summary Report

The final FAT report should summarize:

• Equipment tested
• serial numbers
• test date
• test location
• test personnel
• buyer witness status, if any
• major test items
• pass/fail results
• deviations
• corrective actions
• documents included
• final release decision

The summary should not replace raw data.

It should point to the files that support each result.

36. Witnessed FAT vs. Remote FAT

Some buyers witness FAT in person.

Others use remote FAT.

Remote FAT may include:

• Live video call
• pre-recorded videos
• shared raw data
• photos
• screen sharing
• remote review of checklist
• follow-up Q&A
• signed test report

Remote FAT can work well when the data package is complete.

But if the package is weak, remote FAT becomes a sales presentation rather than an acceptance process.

37. What Should Be Checked Again During SAT

Some FAT items should be repeated after installation.

Site Acceptance Testing may include:

• Shipment inspection
• reassembly check
• cable connection check
• software startup
• grounding
• cooling
• safety interlocks
• field polarity
• reference sample measurement
• selected field-current checks
• temperature stability check
• data export
• operator training

FAT confirms factory condition.

SAT confirms installed-site condition.

The FAT package should help define what must be repeated on site.

38. FAT Data and Warranty

FAT records can help support warranty claims.

For example:

• A power supply serial number is documented.
• A cable connection photo shows factory wiring.
• A packing photo proves the accessory was included.
• A field-current curve shows pre-shipment performance.
• A video shows safety interlock behavior.
• A calibration certificate confirms the probe used for FAT.
• A deviation record shows an issue was corrected before shipment.

Good records protect both buyer and supplier.

39. FAT Data and Future Maintenance

A FAT package is useful long after delivery.

It can support:

• Troubleshooting
• recalibration
• spare part ordering
• software recovery
• system relocation
• operator training
• audit review
• warranty service
• performance comparison
• upgrade planning

If a system is moved three years later, the original FAT data provides a baseline.

40. What Buyers Should Request Before PO

The FAT data package should be discussed before purchase.

Buyers should ask:

• What FAT items are included?
• Is raw data provided?
• Are videos included?
• Are photos included?
• What calibration records are included?
• Is field mapping included?
• Is long-duration testing included?
• Is a reference sample included?
• Is remote FAT supported?
• What is excluded from FAT?
• What will be checked only during SAT?
• What file formats will be provided?
• Who signs the final FAT report?

If the buyer waits until shipment week to request detailed FAT data, the supplier may not have planned the required tests.

41. Practical FAT Data Package Checklist

General Project Records

• Approved quotation
• PO reference
• final configuration list
• serial numbers
• document revision list
• FAT protocol
• FAT checklist
• FAT summary report

Raw Data

• Field-current data
• current stability data
• field mapping data
• Hall measurement data
• VSM loop data
• temperature logs
• cooling data
• safety test data
• reference sample data

Calibration Records

• Field probe certificate
• gaussmeter certificate
• current meter certificate
• thermometer or sensor certificate
• reference sample documentation
• balance certificate, if relevant
• calibration due dates

Visual Records

• System photos
• nameplate photos
• wiring photos
• field probe position photos
• sample mounting photos
• cooling connection photos
• safety interlock photos
• packing photos

Video Records

• Startup video
• operation video
• field ramp video
• polarity reversal video
• safety test video
• software/data export video
• packing video

Software and Configuration

• Software version
• firmware version
• calibration files
• configuration files
• communication settings
• user manual
• backup files
• license information

Deviations and Release

• Deviation list
• corrective actions
• retest records
• open issues
• buyer comments
• final release decision

42. Better RFQ Language for FAT Data Package

Instead of writing:

“Please provide FAT report.”

write:

“Please provide a complete FAT data package before shipment, including FAT protocol, checklist, pass/fail summary, raw data files, processed results, photos of test setup and probe position, videos of key functions, calibration records for test instruments, software and firmware versions, configuration file backups, deviation and corrective-action records, and packing photos. The package should clearly link each acceptance result to the supporting raw data and test condition.”

This language makes the expectation much clearer.

43. Common Buyer Mistakes

Mistake 1: Asking Only for a Video

A video is useful, but it does not replace raw data and calibration records.

Mistake 2: Accepting Only a Polished PDF

A final report without raw data is difficult to review or troubleshoot.

Mistake 3: Forgetting Probe Position Photos

For magnetic systems, the measurement location is part of the result.

Mistake 4: Ignoring Software Versions

A system can behave differently after software or configuration changes.

Mistake 5: Not Asking for Calibration Records

The buyer should know what instruments were used to generate FAT results.

Mistake 6: Skipping Deviation Records

Small problems are normal in engineering. Undocumented problems are dangerous.

Mistake 7: Waiting Until Shipment to Define FAT

FAT scope should be agreed before production and final testing.

Mistake 8: Confusing FAT with SAT

Factory data does not automatically prove site performance after shipment and installation.

44. How Cryomagtech Supports FAT Data Packages for Magnetic and Cryogenic Systems

Cryomagtech supplies Helmholtz coils, electromagnets, excitation power supplies, magnetic field drivers, Hall measurement systems, VSM-related magnetic characterization systems, cryogenic temperature instruments, field sensors, and custom Magnet & Field Systems.

For formal delivery projects, we help buyers define and prepare FAT data packages covering:

• FAT protocol and checklist
• field-current curves
• field mapping data
• power supply stability and ramp tests
• polarity and axis verification
• Hall reference sample measurements
• VSM reference sample measurements
• cryogenic cooldown and stability data
• cooling and thermal records
• calibration certificate review
• setup photos and probe-position photos
• operation and safety videos
• software version and configuration files
• deviation and corrective-action records
• packing and accessory photos
• FAT-to-SAT transition checklist

👉 Product link placeholder: Cryomagtech FAT Data Package Support for Helmholtz Coils, Electromagnets, Power Supplies, Hall, VSM, and Cryogenic Systems

A strong FAT data package does more than satisfy procurement paperwork.

It gives the buyer a technical baseline, reduces overseas delivery risk, improves remote support, and makes future site acceptance, troubleshooting, maintenance, and recalibration much easier.

References

• IEC – IEC 62381:2024 Factory Acceptance Test, Factory Integration Test, Site Acceptance Test and Site Integration Test
  https://webstore.iec.ch/en/publication/67572
• NIST – Metrological Traceability: Frequently Asked Questions and NIST Policy
  https://www.nist.gov/metrology/metrological-traceability
• NIST – Policy on Metrological Traceability
  https://www.nist.gov/calibrations/traceability
• NASA – Configuration Management
  https://www.nasa.gov/reference/6-5-configuration-management/
• NASA Configuration Management Standard
  https://standards.nasa.gov/node/210

Key Takeaways

• A FAT data package should include more than a short operation video.
• Buyers should request raw data, processed results, photos, videos, calibration records, software versions, configuration files, deviation records, and packing photos.
• FAT should be based on agreed technical requirements, not only a supplier demonstration.
• Raw data helps buyers review noise, drift, repeatability, field mapping, temperature stability, and calculation methods.
• Probe-position photos are essential for magnetic systems because the measurement location affects the result.
• Calibration records help buyers understand the reliability and suitability of FAT test instruments.
• Software versions and configuration files should be archived because they define how the delivered system operates.
• Deviation and corrective-action records should be documented rather than hidden.
• FAT confirms the factory condition; SAT confirms the installed site condition.
• A complete FAT package becomes the buyer’s baseline for installation, warranty, maintenance, troubleshooting, and future recalibration.

For formal equipment procurement, the key question is not only:

“Did the supplier test the system?”

The better question is:

“Can the supplier provide enough FAT evidence for the buyer to understand exactly what was tested, how it was tested, what data was produced, and whether the delivered system met the agreed requirements?”