Are you a certified AVEVA or Inductive Automation partner?

No. Our engineers have worked across AVEVA and Ignition platforms, but we hold no certified or authorized partner status with either vendor, and we say so before the question gets asked.

What does a SCADA and HMI scope include?

Application configuration including tag architecture and alarm rationalization, graphics and operator workflow, integration to PLC and DCS over OPC UA or vendor-native drivers, factory and site acceptance testing, and turnover of as-built configuration and tag databases.

Which sectors do you deliver SCADA for?

Oil and gas, water and wastewater, utilities and power, mission-critical facilities, and process manufacturing. Most run on the same platforms, which is why we treat SCADA as one capability rather than five separate industry offerings.

Capability

SCADA & HMI Integration

Supervisory control that operators trust, delivered by the engineers who commission it.

Black Box Engineering configures, integrates and commissions SCADA and HMI systems for facilities where an operator's screen is the only view into a running process. Our engineers have worked across AVEVA and Ignition platforms, on scopes from a single graphics package to a plant-wide supervisory layer.

Platforms we work on

Ignition
OPC UA

Our engineers have worked on these platforms. We hold no platform certifications, and we are not an AVEVA partner or an Inductive Automation partner.

What we own

Where the certificate matters, this is the scope we sign for:

Application configuration — object and template design, tag architecture, alarm rationalization and shelving, historian configuration, and trend and report packages.
Graphics and operator workflow — screen hierarchy, navigation, alarm presentation, and the situational-awareness conventions that keep a control room usable at 3am.
Integration to the control layer — PLC and DCS connectivity, OPC UA and vendor-native drivers, I/O checkout against loop diagrams, and data validation from field device to trend.
Testing and commissioning — factory acceptance testing, site acceptance testing, and pre-functional and functional checks documented against the approved design intent.
Turnover — as-built configuration, tag databases, alarm registers and operator documentation, in the form the client's maintenance team will actually use.

Where it applies

SCADA is the same discipline across sectors that rarely share a supplier:

Sector	Typical supervisory scope
Oil & gas	Pipeline and wellhead monitoring, terminal automation, custody transfer metering
Water & wastewater	Lift stations, treatment trains, remote site telemetry
Utilities & power	Substation data concentration, generation monitoring
Mission-critical facilities	BMS and EPMS integration, alarm aggregation, capacity trending
Process manufacturing	Batch supervision, OEE and downtime reporting, historian reporting

Most of these run on the same platforms, which is why we treat SCADA as a capability rather than as something that belongs to one industry.

How we work

We are platform-agnostic by preference and specific by obligation. The right supervisory platform is the one your operations team can maintain after we leave, which is usually the one already in the building. Where there is no incumbent, we will say which we would choose and why.

Every engagement starts from the same three questions: what does the operator need to see, what decisions do they make from it, and what happens when the data is wrong. Alarm rationalization and tag architecture come out of those answers, not from a template.

Who does the work

Our engineers have AVEVA and Ignition experience and have commissioned systems in mission-critical facilities. Senior leadership brings more than five years on data-center and mission-critical programs where the supervisory layer was in scope.

Black Box Engineering is a young firm and we are plain about what that means here. We hold no platform certifications, and we are not an AVEVA partner and not an Inductive Automation partner. If partner status is a procurement requirement on your project, tell us at the inquiry and we will say so — rather than take you through a qualification round you were always going to fail us on.

What we do bring is engineers who have configured and commissioned these systems, and a firm small enough that the people who scope your job are the people who show up to it.

Ask us the specific question. If your site runs a particular product and version — System Platform, InTouch, Historian, Ignition — name it, and we will tell you plainly who on the team has worked on it and who has not. That answer is more useful than a capability matrix, and it is the answer you would get from us eventually anyway.

Talk to us about a supervisory scope

We are Mexico City based and work across North America. If you have a SCADA scope — a migration, a new supervisory layer, or an application nobody has maintained in five years — tell us what the operators need to see and we will tell you what it takes.

Request Consultation Mexico +52 55 9602 3423 United States +1 832-443-1849

Frequently asked

What people ask us first

Are you a certified AVEVA or Inductive Automation partner?: No. Our engineers have worked across AVEVA and Ignition platforms, but we hold no certified or authorized partner status with either vendor, and we say so before the question gets asked.
What does a SCADA and HMI scope include?: Application configuration including tag architecture and alarm rationalization, graphics and operator workflow, integration to PLC and DCS over OPC UA or vendor-native drivers, factory and site acceptance testing, and turnover of as-built configuration and tag databases.
Which sectors do you deliver SCADA for?: Oil and gas, water and wastewater, utilities and power, mission-critical facilities, and process manufacturing. Most run on the same platforms, which is why we treat SCADA as one capability rather than five separate industry offerings.