SCADA testing services for FAT, SAT, and ADMS regression

What SCADA testing services are not

This is not SCADA pentesting, ICS SCADA penetration testing, OT security testing, Nessus against a control network, or red-team theater. Those queries sit next to SCADA testing in search; they are a different buyer and a different risk. We will not script traffic at live breakers. We will not take NERC BES desk seats. Vendor upgrades and patch trains are exactly why the functional service exists, still on lab gold images, still with your OT owner accountable for production.

We are not a generic software-test shop and not a FAT/SAT glossary for pharmaceutical skids. SCADA, ADMS, protocol, model, and utility acceptance literacy are the filters. Commissioning support means scripts, dry runs, punch lists, and witness evidence. It does not mean we energize the plant or own SAT sign-off.

Factory acceptance test versus site acceptance test

Buyers searching factory acceptance testing, site acceptance test, or FAT and SAT usually want the difference, a procedure, and an example pack, not a pentest. A factory acceptance test, or FAT, demonstrates configured SCADA or ADMS behavior in the factory, integrator shop, or isolated program lab before the image ships. A site acceptance test, or SAT, verifies the approved installation and interfaces at the site under the owner’s change, safety, and access procedures. System integration testing, or SIT, sits between those gates when GIS, OMS, CIS, historian, or middleware contracts must be proven as a string, not as a single screen.

Regression covers HMI, alarm annunciation, and point databases after a vendor patch or model load. Point-to-point checks prove analog, status, and control mappings from RTU or IED through the gateway into the HMI and historian on a representative lab or approved SAT path. Related offers: test automation, GIS/OMS/ADMS data validation, technical documentation QA, non-prod DevOps. On-site FAT is possible. Most evidence work can start remote against lab images if your OT architecture allows isolated environments. We will not flatten ESP rules to go faster.

Who delivers SCADA testing

Named testers who have seen vendor tools, protocol-literate QA, and a U.S. lead on dedicated teams. Integrators buy surge capacity before a cutover weekend. IOUs buy standing regression after monthly patch trains. Energy software teams buy OT-safe testers who will not poke production APIs.

Pair testing services with ADMS engineers or SCADA engineers only when the defect is configuration, not coverage. Many programs should start here and add architecture later.

How we scope SCADA testing services

A useful testing brief names the vendor image, whether the work is regression after a patch train or evidence for a factory acceptance test or site acceptance test, and whether GIS, OMS, or historian contracts are in the pack. Generic “need QA” tickets waste a week. We will not pentest the grid, run ICS penetration testing, or attach simulators to production breakers. We will staff a U.S. lead plus testers who have seen Schneider, GE Vernova, OSI, or Ignition labs.

Start here when you need certainty before cutover. Add ADMS engineers later if the defect is configuration. Add GIS/OMS/ADMS data validation if the defect is the model. Houston, Dallas, Raleigh, Phoenix, Denver, and St. Louis are the first six metros we staff into. We identify suitable profiles after a complete project brief.

A defensible SCADA and ADMS test program

The first deliverable is a risk-based test inventory, not a stack of generic cases. We map requirements and interface contracts to business-critical workflows, then separate smoke, functional, regression, performance, failover, and recovery coverage. The utility identifies operational consequence and acceptance authority. Our team turns that direction into executable cases, traceability, defects, retest status, and release evidence.

A representative lab matters: software version, database baseline, point-list revision, interface builds, simulator limits, user roles, and data refresh. We establish entry criteria before execution so a failed environment is not reported as a failed application. FAT demonstrates configured behavior in the shop or isolated lab. SAT verifies the approved installation at site under the owner’s procedures. We prepare procedures, dry runs, evidence, and punch lists. The utility and OEM retain command authority and final acceptance.

Upgrade regression is prioritized by change impact. We compare the candidate build with the approved baseline, select affected tests, retain a stable smoke suite, and record unresolved defects with severity, workaround, owner, and release decision. Buyers should expect planned versus executed coverage, open defects by severity, blocked cases, and signed exceptions. The handoff identifies what was tested, what was excluded, and what remains for the owner or OEM.

How to buy testing in reviewing a complete brief

Open the project form, name vendor, lab versus SAT, and city. We identify suitable profiles for named testers. The lead stays if you convert to a dedicated team. We still will not bid live control-system operations.