PSC H270

Overview

The Product Service Code (PSC) taxonomy is a four‑character system that classifies what the federal government buys and populates FPDS/SAM reporting fields; the PSC Manual is maintained and published by GSA/FPDS. PSC H270 is described in the PSC Manual as "Equipment and Materials Testing‑ Automatic Data Processing Equipment (Including Firmware), Software, Supplies and Support Equipment." Use of H270 applies when the predominant contract line item is testing, evaluation, validation, diagnostics, or acceptance testing focused on ADP hardware, firmware, software, supplies, or associated support equipment. ¹

What this PSC covers

• ADP hardware test services and validation, including acceptance testing and conformance checks. ¹
• Firmware conformance and verification testing for embedded ADP devices and controllers. ¹
• Software functional, performance, interoperability, and compatibility testing when software is part of an ADP system requirement. ¹
• Testing of ADP supplies and peripherals, such as media, input/output devices, and consumable components. ¹
• Support‑equipment diagnostics, calibration, and systems‑level ADP testing covering environmental and interoperability criteria. ¹

Related NAICS and PSC codes

Not specified by official sources ¹.

Related PSC entries on G2X (non‑numbered links):

• H270
• H370
• H274

FPDS reporting notes

When recording contract actions in FPDS the PSC must represent the predominant product or service being acquired; the PSC Manual and FPDS guidance require selecting a single PSC even when multiple items are present. Agencies must follow FPDS data‑entry rules and complete required fields (for example, Reason for Purchase) when using codes in the H‑series. ²

Frequently asked questions

• Q: What specifically is covered by PSC H270?
  A: PSC H270 covers testing, evaluation, and materials/equipment acceptance related to Automatic Data Processing equipment and the associated firmware, software, supplies, and support equipment where testing is the predominant contract requirement. ¹

• Q: Does H270 include software testing as well as hardware testing?
  A: Yes. The PSC Manual lists software alongside ADP equipment and firmware; use H270 when software testing constitutes the primary contract performance or deliverable. ¹

• Q: How does H270 differ from inspection codes such as H370?
  A: H270 is for equipment and materials testing focused on ADP items; H370 is an inspection category. The PSC Manual separates the “Equipment and Materials Testing” group from the “Inspection” group and provides distinct descriptors for each code. ¹

• Q: Are there FPDS reporting constraints when selecting H270 for DoD actions?
  A: Yes. FPDS rules require certain fields be populated for DoD actions using codes in the H series; follow the FPDS data‑entry guidance (for example, Create a PO) to ensure required fields such as Reason for Purchase are completed. ²

Useful resources

• G2X — PSC H270 overview: https://app.g2xchange.com/psc/H270
• Product and Service Code (PSC) Manual (current edition): https://www.acquisition.gov/sites/default/files/manual/PSC%20Manual%20April%202025.pdf
• FPDS glossary and reporting guidance: https://www.fpds.gov/help_V1_1/Glossary.htm
• FPDS data‑entry guidance (Create a PO): https://www.fpds.gov/help_V1_1/Create_a_PO.htm

References

1. Product and Service Code Manual (PSC Manual, April 2025). https://www.acquisition.gov/sites/default/files/manual/PSC%20Manual%20April%202025.pdf

2. FPDS help — Create a PO (FPDS data‑entry reporting guidance). https://www.fpds.gov/help_V1_1/Create_a_PO.htm