Three HCAI preapproval programs get used interchangeably in specs and submittals, and they are not interchangeable at all. OSP covers equipment. OPM covers a manufacturer's anchorage details. PCS — Preapproval of Component Systems — covers a whole system with its supports and bracing. Referencing the wrong program on a hospital submittal is one of the most common causes of an HCAI back-check comment, and each round costs weeks.
What a PCS actually covers
A PCS preapproves a manufacturer's component system — the components, the supports, the bracing, and the installation instructions as a single reviewed package. Typical PCS subjects include:
- Seismic bracing systems for piping, ductwork, and conduit
- Trapeze and hanger support systems
- Cable tray and busway support assemblies
- Suspended ceiling and lay-in assemblies
- Modular headwall, casework, and equipment support systems
The value is repeat use: once a system carries a PCS number, an installer can reference it on any HCAI project inside the certified limits without resubmitting the engineering behind it.
PCS vs OSP vs OPM, side by side
| Program | What it preapproves | Typical evidence | Best for |
|---|---|---|---|
| OSP | A specific piece of equipment, certified operable after the design earthquake | ICC-ES AC156 shake table test plus a PE/SE certificate of compliance | Ip = 1.5 active equipment: generators, chillers, switchgear, UPS |
| OPM | A manufacturer's anchorage or attachment details for repeat use | Calculations and details covering a bounded range of conditions | Repeat anchorage of a product family across many projects |
| PCS | An entire component system with supports, bracing, and installation limits | Testing and/or calculations plus complete installation instructions | Distribution systems, ceilings, and support assemblies installed repeatedly |
If you want the OSP and OPM comparison in more depth, see OSP vs OPM: which preapproval you need. You can search the live listings in our HCAI PCS database, OSP database, and OPM database.
What goes in a PCS submittal package
- System description and scope. Exactly which components, sizes, materials, and configurations are included — and which are explicitly excluded.
- Design basis. Code cycle, ASCE 7 edition, the governing sections, and the analysis or test method used.
- Certified limits. Maximum SDS, z/h range, span, spacing, load per brace, and attachment substrate. These become the boundary conditions every project installation is checked against.
- Supporting engineering. PE/SE stamped calculations, or shake table / component test reports where the system is qualified by test.
- Installation instructions and details. The drawings an installer and an HCAI IOR will actually work from — legibility and completeness here drive review speed more than anything else.
The limits are the whole point
The most frequent field problem with preapprovals is treating the number as a blanket approval. A PCS is only valid inside its stated bounds. Before you reference one, check the project against every limit — particularly SDS and z/h, since a rooftop mechanical room can easily exceed what a system was certified for at grade. The same trap applies to OSP certificates; see height amplification and the Hf factor and when Ip equals 1.5.
When the project falls outside the certified envelope, the fix is a project-specific stamped calculation — not a looser reading of the preapproval. That path is covered on our seismic bracing calculations and hospital equipment anchorage pages.
When PCS is worth pursuing
A PCS pays for itself when the same system is installed repeatedly across California hospital work. The engineering is done once, and every subsequent project references the number instead of paying for and waiting on a fresh review. If a system ships on one or two HCAI projects a year, project-specific calculations are usually faster and cheaper than the preapproval process.
Getting a PCS through review
Most schedule loss in PCS review is self-inflicted: incomplete limits tables, details that don't match the calculations, and a design basis that references a superseded code cycle. Panache prepares and shepherds PCS packages end to end — design basis, stamped calculations, installation details, and HCAI comment response. See HCAI PCS certification services or talk to an engineer about your system.