Engineering heritage is a constraint, not a product catalogue
Adqueo exists because software that ignores how engineering work actually happens fails in the field. The parent group is context. The work is still software.
In this note
Tecapa Electric holds a broader electrical engineering practice. Adqueo is the unit that turns operational knowledge into systems: custom software, agents, and products. That relationship should make the software more precise — not turn this site into a general engineering brochure.
A constraint you can feel in the spec
Heritage shows up as questions a generic software house does not ask: how the isolation is recorded, who owns the spare, what the auditor will open, why the tag on the skid does not match the drawing. Those questions narrow the design. They are not a second offer of civil works or plant construction.
The parent group is why the software knows the grain of the work. It is not the product we sell from this site.
If you need engineering of the plant, that conversation belongs with Tecapa Electric. If you need the system the plant will actually run — specified, auditable, safe to touch on shift — that conversation belongs here.
