Quality

Your software must stay right after every change.

Your processes change. Equipment is replaced, records are extended and new requirements call for adjustments. You want to know what such a change means for how your system works and for its qualification.

That is why every change follows a fixed route with us: from registered request to review, test and acceptance. We record what changes, which checks were carried out and which version is delivered.

So you can follow how your software comes about and on what grounds a change is taken into use.

Every change takes the same route

01
ReportedYour question or change request is registered.
02
PlannedApproach, consequences and the work needed are determined.
03
BuiltThe change is developed for your system.
04
ReviewedThe code is read and approved before it enters the managed source version.
05
TestedThe agreed checks are carried out and recorded.
06
AcceptedYou review the change in the acceptance environment.
07
QualifiedWhere required, we carry out the agreed qualification activities.

Qualification activities can also be part of preparing for acceptance and for taking the system into use.

Every release traceable

Source code, configuration, test scripts and documentation are under version control. Every release has a unique version designation and build date, and is assembled from recorded source versions.

For every release we record the source versions used, the reviews and the test results. The release package carries version information and checksums. Installation in production follows after the agreed review and your approval.

That lets us find out what was delivered, which changes it contains and which test results belong to it.

Qualification tailored to your process

A useful qualification dossier starts with clear agreements on requirements, checks and responsibilities.

Where qualification is needed, we agree the approach, protocols and responsibilities with your quality department in advance. After approval, the checks are carried out and the results are recorded.

You receive the agreed documentation for your installation and software version. Performance qualification takes place within your own process, with the support we agree together.

PhaseStroetengaYour organisation
ProtocolsStroetengaDrafts the agreed protocols.Your organisationReviews and approves them.
IQ: correct installation in your environmentStroetengaCarries out and documents.Your organisationReviews the result.
OQ: functions work as specifiedStroetengaCarries out and documents.Your organisationReviews the result.
PQ: operation in your daily processStroetengaSupports as agreed.Your organisationCarries out and provides the evidence.
Taking into useStroetengaDelivers the release and documentation.Your organisationDecides on taking it into use.

For our main systems we use automated screen tests. Reusable test scripts reduce repeated work at later releases. For each change we decide which additional checks are needed.

See how we record quality

Request an example dossier with documents from completed projects, with customer details removed. That way your quality department can assess in advance how we record changes, checks and results.

Example test report

Which checks were carried out and which results were recorded.

One change from request to delivery

How request, implementation, review, test and acceptance connect.

Example structure of a qualification dossier

Which documents can be part of the agreed delivery.

Audit proposal

Which topics and evidence can be examined during an audit.

Request the example dossier

Follow your issues in the customer portal

As a customer you report questions and change requests in our customer portal. There you follow every issue, with the related feedback:

1
Reported
2
Open
3
In progress
4
Awaiting approval
5
Closed
Screenshot of the customer portal: the sign-in screen only, no customer data

How we benefit from AI

AI helps us work faster and more consistently: in writing and reviewing code, and in creating the automated test scripts that produce our test documentation.

People keep deciding. AI commits nothing to our version control and makes no releases: a developer, designer or tester always does that. Everything is tested before it reaches you; we are the filter between what AI suggests and what you receive.

Your software and its content stay under our control.

Speak with a user

Would you like to know how our software and our collaboration work out in practice? On request, we look into which customer can tell you about it. Once agreed, we put you in touch.

Our systems run at, among others, an isotope producer, a chemical site, a manufacturer of radiopharmaceutical equipment, a nuclear power station and a defence site.

Request a reference

Come and see how we work

We are setting up our quality management system according to ISO 9001 and we are not certified. That is exactly why we like to show you how we work: which route a change takes, how we test and what we record. If you want to go further, a formal audit is possible too.