From practice
Teqsa comes from practice: our engineering runs as a software factory in which agents do this work.
The model of our own platform
The model of Pleqsa, our own fintech and regtech platform, holds more than 7,000 elements, among them over 2,300 specified scenarios, 320 recorded decisions and 136 requirements, every one traced to what realises it.
- 7,000+elements
- 2,300+specified scenarios
- 320recorded decisions
- 136requirements, every one traced
A field service system for a second country
With Teqsa we also build a heating-equipment manufacturer's field service system for a second country, with every legacy behaviour kept, changed or dropped by decision.
- Challenge
- A field service management system for installation, servicing and maintenance in a new country, derived from the system already running in another country, with different regulations and business rules, and without losing the field knowledge embedded in the legacy code.
- Solution
- Teqsa reconstructs the existing system from its source code into a verified model. The new country's system is modelled as a target in which every legacy behaviour is accounted for: kept, changed, or dropped by explicit decision.
- Impact
- A second country system built from a verified model instead of a copy of legacy code. Every difference between the two countries is documented and decided rather than discovered in the field.
What running it taught us
An agent is only as good as the knowledge it can read, and probabilistic output needs a deterministic check.