Build and check the first Empower Export Method Use a test result with at least two named components, then add a second injection. This exposes row-grouping mistakes that a single-peak file cannot reveal. The target is a repeatable export whose result identities, component values and sample context can be compared directly with the receiving Seal records. FIRST RUN 1. Create a Fields export in the project Open the Project window and create an Export Method from New Method. On Fields, enter a file root name, enable Export ASCII File and choose the output folder. For a table export, enable Export Table Data, use Load Table and edit the selected table to include the required component values. Check: Save a named method for the evaluation. Record the selected table, output folder and column layout so another operator can generate the same kind of specimen. Waters: exporting results with an Export Method: https://support.waters.com/KB_Inf/Empower_Tips_of_the_Week/WKB193142_Exporting_Data_Results_and_Reports_with_Export_Methods_in_Empower 2. Set grouping and include the sample identifiers Choose the report grouping deliberately. Enable Export Field Data and include Sample Name and Injection alongside the table. Record the column, row and text delimiters, label orientation, and whether fields precede or follow the table. Check: The file may contain an identifier block plus a table rather than one flat CSV. Test its actual structure. Exported row numbers are useful for tracing lines within a file but must not become the scientific result identity. Waters: Fields-tab settings: https://support.waters.com/KB_Inf/Empower_Breeze/WKB3071_How_to_create_an_export_method_that_exports_database_fields_and_tables_in_Empower Waters: exporting results with an Export Method: https://support.waters.com/KB_Inf/Empower_Tips_of_the_Week/WKB193142_Exporting_Data_Results_and_Reports_with_Export_Methods_in_Empower 3. Run the method on selected results Save the method. On the Results tab, right-click the selected result or results and choose Export. In Background Processing and Reporting, select Use Specified Export Method, choose the saved method and confirm. Check: Open the file from the configured folder and compare every selected component with the source result. Keep the file’s actual extension and Result ID context; opening it in a spreadsheet does not change the export contract. Waters: exporting results with an Export Method: https://support.waters.com/KB_Inf/Empower_Tips_of_the_Week/WKB193142_Exporting_Data_Results_and_Reports_with_Export_Methods_in_Empower 4. Export trace evidence separately when required For ASCII trace output, use Raw Data, select the format and destination, include the x axis when needed, choose delimiters and add sample fields. For CDF, select AIA and File on Raw Data. Check: Use trace files to preserve signal evidence. Waters notes that CDF does not contain the Empower processing methods and can differ in precision; compare selected numeric results through controlled peak-table exports, not by treating CDF as an equivalent processed report. Waters: raw data with sample fields: https://support.waters.com/KB_Inf/Empower_Breeze/WKB118708_How_to_export_raw_data_and_sample_information_from_Empower Waters: CDF scope and numeric comparison: https://support.waters.com/KB_Inf/Empower_Breeze/WKB26380_Can_data_be_exported_as_CDF_files_from_Empower_3 5. Test the configured automated route as a separate step After the manual specimen is reconciled, trigger the intended automated export and compare its method, selected population and output. For the documented Empower 3 case where PDF reports do not export despite an Export Method in Run Samples, Waters directs users to add the Export Method to the Method Set. Check: Confirm that the expected file actually arrives after the intended event. A successful manual export does not prove that the run uses the same Export Method or produces the same reviewed result population. Waters: PDF export and the Method Set: https://support.waters.com/KB_Inf/Empower_Breeze/WKB193024_Empower_Export_Method_not_exporting_reports_in_PDF_form Choose grouping before deciding what one file represents The Fields-tab report type controls grouping. Preserve that setting with the mapping and exercise it using multiple injections. A parser that assumes one result per file can appear correct on a small specimen and silently lose data later. Export grouping: Individual Source grouping: Separate output for each exported data item; channels or results within a set are separate What the receiving mapping must preserve: Read the selected result/component population, not a guessed count based on the number of files. Export grouping: Summary By All Source grouping: One summary for the selected data items What the receiving mapping must preserve: Keep the sample, injection and result identity for every component represented in the summary. Export grouping: Summary By Vial Source grouping: One summary per vial What the receiving mapping must preserve: Retain the separate injections within that vial; repeated injections are not duplicate deliveries. Export grouping: Summary By Injection Source grouping: One summary per injection What the receiving mapping must preserve: Retain all selected components and evaluations within the injection context. Export grouping: Area Component Summary table Source grouping: A supported example places samples down rows and peak names across columns What the receiving mapping must preserve: Map component columns explicitly. Preserve the source result association; a sample label alone cannot distinguish repeated injections. Waters: Fields-tab settings: https://support.waters.com/KB_Inf/Empower_Breeze/WKB3071_How_to_create_an_export_method_that_exports_database_fields_and_tables_in_Empower Waters: Area Component Summary export: https://support.waters.com/KB_Inf/Empower_Breeze/WKB85134_How_to_create_a_method_to_export_Area_values_with_sample_name_on_vertical_axis_and_peak_name_on_horizontal_axis_with_Empower_3 A two-injection specimen that exposes overwritten component rows Fictional normalized mapping worksheet derived from the fields selected for the evaluation. It is not a default Empower export format. Use an actual Export Method specimen to establish its headers, blocks, delimiters and quantity units. project,result_set,sample,injection,result,component,area,area_unit QC-DEMO,RS-18,S-482-01,INJ-06,RES-91,Main,125000,mAU*s QC-DEMO,RS-18,S-482-01,INJ-06,RES-91,Impurity A,420,mAU*s QC-DEMO,RS-18,S-482-01,INJ-07,RES-92,Main,124500,mAU*s QC-DEMO,RS-18,S-482-01,INJ-07,RES-92,Impurity A,435,mAU*s The expected receiving population is two source results and four component measurements for one sample. Deduplicating by sample would lose an injection. Deduplicating by result alone would lose a component. Within the agreed project and evaluation scope, both result identity and component identity are needed. PROPOSED RECEIVING CHECKS — NOT EXECUTED CUSTOMER VALIDATION Import all four component measurements Input: Map the complete worksheet above through the proposed receiving design. Expected: RES-91 retains Main 125000 and Impurity A 420; RES-92 retains Main 124500 and Impurity A 435. Both injections point to S-482-01 and retain their source unit. Deliver exactly the same file again Input: Resend the unchanged specimen under the same source/evaluation contract. Expected: There are still two results and four measurements. The repeated delivery is traceable without replacing one component with another or creating extra scientific results. Add a newly evaluated result Input: Provide RES-93 as a later evaluation of INJ-06, with Main 125100 and Impurity A 418, preserving RES-91. Expected: The new evaluation has its own two measurements and relationship to the earlier result. The receiving review identifies the changed values; arrival order does not silently erase RES-91. Change table shape without changing the science Input: Export equivalent selected data using a summary table with component names as columns rather than component rows. Expected: A mapping approved for the original layout either rejects the unfamiliar shape for review or uses a separately verified layout mapping. It never reports a successful two-row import while dropping two component measurements. HANDOFF Keep the named Export Method, its Fields/Report/Raw Data settings, two-injection specimen, quantity-unit evidence and expected result/component counts together. Seal can use this package to define a receiving mapping that survives repeated delivery, multiple components and later evaluations, while keeping the Empower source files available for review.