---
name: New product line datasheet formats (MAQ20, PWRM, 10D, DSCMHV)
description: MAQ20/PWRM use XLS multi-sheet format, 10D will use JSON. Different paths and naming conventions from legacy QuickBASIC pipeline. Details from John Lehman 2026-03-27.
type: project
---

## MAQ20 Product Line
- Location: T:\ENGR\DESIGN\MAQ20 Design\Test Data (T: = old ENGR share)
- **Needs to move** from T: to K: (TEST share), then update programs to save to K:
- Format: .xls with multiple sheets:
  - Sheet 1: list of test steps used by test program
  - Sheet 2: test results
  - Some have customer-ready datasheet on another tab
  - Some have .pdfs
- First pass AND final pass data saved regardless of pass/fail
- Uses naming standard implemented ~2021

## PWRM10 (Energy Measurement Module)
- Location: U:\DESIGN\PWRM10 Energy Measurement Module\Test Data\Final Pass Test
- Format: .xls with numerical data + semi customer-ready datasheet on another tab
- First pass AND final pass data saved regardless of pass/fail

## 10D (Not yet released — ~2 months out as of 2026-03-27)
- Location: K:\10D\first_pass and K:\10D\second_pass\pass
- Data segregated by directory: first/second pass, pass/fail subdirectories
- Will use **JSON format** per John's earlier email

## DSCMHV
- New product line, uses same naming standard as MAQ20/PWRM/10D

## Standards Discussion
- User (Mike) and John discussing better serial numbering that encodes more product detail
- Current convention: sequential S/N can be all different products (confusing)
- Naming standard from ~2021 used for MAQ20+ lines but could be improved

**Why:** These are the next product lines to integrate after the legacy QB pipeline is restored.
**How to apply:** The current TXT pipeline (spec-reader + exact formatter) won't work for these. Need XLS parser for MAQ20/PWRM, JSON parser for 10D. John says customer-ready datasheets need improvement for all three.
