How EPSIA works: fixed price, simulation first, checked rules
EPSIA follows four principles in its software projects – from taking over existing software to developing complete machine and plant software:
- Fixed price to specification: The agreed scope is offered as a result, not as a number of development hours.
- Simulation before real hardware: For systems with a hardware connection, EPSIA develops and tests software against a simulation of the plant as early as possible.
- Automatically checked rules: Architecture, source code and defined project rules are checked automatically – including when AI is used in software development.
- Handover to the customer: Customers receive source code, reproducible builds, automated tests and the agreed technical documentation.
Why does EPSIA work at a fixed price?
EPSIA offers clearly defined software projects at a fixed price, because the customer commissions an agreed result, not a certain number of development hours.
The basis is a jointly developed functional specification that describes functions, interfaces and acceptance criteria. Requirements that arise later can be defined and quoted as separate extensions.
The calibration machine for infrared temperature sensors, for example, was first planned in a separate concept phase and then delivered as a fixed-price project with three defined milestones.
Why does EPSIA develop against a simulation first?
For machines and technical plants, EPSIA starts software development as independently as possible of the availability of the real hardware. To do this, the relevant components and processes of the plant are simulated. Software, operator interface and control logic can then be developed and tested while the real plant is still being built.
On the calibration and test system for infrared temperature sensors, the customer could already use the operator interface on the digital twin while motors and control components still had lead times of several months. The simulated components were later replaced step by step with the real hardware.
On the automated machine for shaver foil production, the digital twin and the real machine run on the same software. The system has 21 servo axes. The customer also has a virtual test machine for checking processes and software changes without needing the production machine.
How does EPSIA use AI in software development?
EPSIA uses AI tools to support software development. Source code that is generated or changed this way is subject to the same technical rules and checks as conventionally developed code.
Architecture constraints, permitted dependencies and project-specific development rules are stored in the repository as automatically executable checks wherever possible. Changes must pass these checks before they are accepted into a released software version.
This lets EPSIA use the speed of AI-assisted development without leaving the checking of results to the AI system itself.
What does the customer receive at the end?
EPSIA hands over to the customer the technical basis needed to understand, build and continue operating the software. This includes the agreed source code, a reproducible release version, automated tests and the technical documentation.
On the booking platform for camping, motorhome sites, marinas and car parks, for example, 874 automated tests run before every rollout. In addition, a browser test checks the complete booking flow from the user's perspective.
Who does EPSIA work with?
For projects that go beyond pure software development, EPSIA works with established partners for mechanical design and electrical engineering.
On the calibration and test system for infrared temperature sensors, EPSIA acted as general contractor for the complete system. Mechanical design and electrics were delivered together with partners, and the sensor circuit boards were developed with an external engineering firm. EPSIA was responsible for, among other things, process control, control software, system integration and commissioning.
Does EPSIA train development teams?
EPSIA offers training for software development teams on the controlled use of AI agents in software development. The focus is not on operating individual AI tools, but on technical control of the results they produce.
Development teams learn to write verifiable development rules, build automated quality gates and validate AI-generated changes against defined criteria. The training is aimed at software developers and starts with a one-day workshop at a fixed price.
Where does EPSIA work?
EPSIA is a software company based in Berlin and works for customers throughout Germany – both on site and remotely.
Machines and systems with software from EPSIA are in use in Germany, the United Kingdom and China, among other places, and in the series production of a semiconductor manufacturer in Asia. Depending on the project, development and testing can be done remotely; for existing plants, EPSIA uses simulations and offline replay environments, among other tools.