Development or characterization
Identify the planned variables, measurement points, accuracy and data recording needs.
Define the stack under test, operating envelope, measurement channels and utility interfaces before comparing a test platform and a simple rack.

Start with the stack and test protocol. The same stack connection can be used for different test programs, with different measurement channels, controls and data requirements.
Identify the planned variables, measurement points, accuracy and data recording needs.
Share the approved sequence, expected throughput and criteria for comparing results between runs.
Record both the stack interface and the instruments, controls and services needed to run the planned tests.
| What to compare | What to provide | What it helps confirm |
|---|---|---|
| Device under test | Share stack drawings, electrical limits, ports and media connections. | Which stack interfaces the rack or platform must accommodate. |
| Test protocol | List test sequences, ranges and the required method of control. | Whether a simple rack or a more instrumented platform should be reviewed. |
| Measurement and records | Identify channels, ranges, accuracy requirements and output format. | Which sensors, logging and calibration records need to be included. |
| Facility and gas management | List available power, water and cooling, and the lab’s requirements for connections and gas handling. | Which duties and interfaces the facility or equipment must provide. |
Compare the equipment by included controls, measurement channels and utility interfaces. Review any separate stack sourcing against the planned test fixture.
Use the stack and system boundary to separate the test article from supporting equipment.
Find the related equipment and purchasing information for laboratories, research & education.
Record known requirements, units, source documents and open questions. A planning worksheet, not a product specification or certificate.
Download CSV ↓