A conversation, an analysis, an offer
The conversation about the problem is free of charge. The analysis under a non-disclosure agreement (NDA) has a defined scope and deadline, and its cost is credited towards the implementation.
Let's talk about your projectAI models and agents in an energy company's processes, maintained after launch.
ERP, CRM, document recognition, automation of debt collection and of financial product distribution.
A digital insurance platform and online policy sales on a global scale.
Inter-operator systems built to the TM Forum industry standard, a wholesale operator's product catalogue and infrastructure monitoring.
An AI platform run as a medical device under FDA, CE and MDR rules, on the EU and US markets.
An ERP with risk analysis for container trade and an intranet with company knowledge management.
JIRA customisation and automation of HR, IT and legal processes in public administration.
Close to 30 projects in the team's experience, seven sectors
One collection, three filters: sector, topic and service.
See the workA sector in which software can be a medical device and is subject to the same regime as equipment.
Healthcare and MedTech are two worlds with the same stakes: providers and payers, whose systems must run without interruption and protect health data, and manufacturers, for whom software can be a certified medical device. In both, the consequences of an error in the system fall on the patient, who did not choose that system.
In this sector we have one project and we show it in full: an AI platform for in vitro fertilisation, run under the FDA, CE and MDR medical device regime, on the EU and US markets. This project brings together our practices of systems delivery, data and artificial intelligence, and compliance and risk; it belongs to the theme ‘AI that passes an audit’.
A program that influences a diagnosis or the choice of treatment stops being a tool and becomes a device: with a risk class, documentation and post-market surveillance. The release rhythm is then set by the regulatory process, not by the team's plan.
Information on a person's health is one of the most sensitive categories of data: it must always be possible to say where it sits, who has seen it and why. Every secondary use needs its own legal basis, and a copy taken into an analytical environment usually has none.
Admissions, the laboratory, imaging, the pharmacy and billing run on separate systems, and each holds a different fragment of the patient's history. Exchange standards exist, but every vendor implements them in its own way, so the full picture of treatment is assembled by hand.
A model that suggests a diagnosis or ranks patients by urgency enters a process in which a person is responsible for the decision. It must therefore show what it based its result on, and be monitored after deployment: data from the ward changes faster than the model.
An emergency department has no night and no weekend, so there is no hour in which stopping the system harms nobody. On the same network stands equipment whose software may not be touched without the manufacturer's consent, and continuity has to be designed around it.
We start with an as-is audit: what actually works, where the data sits and what it costs to keep the current state running. The result is a roadmap with an order of magnitude for the budget, not a presentation about transformation. The conversation starts with what can be postponed or simplified, not only with what is worth buying.
Technology advisoryBilling, asset registers, spatial systems and control systems rarely talk to each other without an intermediate layer. We build integrations and operational portals that bring these sources together into a single picture for the operations team. We design the integration layer so that it can be maintained without us.
Systems deliveryLanguage models over a base of regulations, documentation and ticket history, with control over the sources and a trail showing where each answer came from. This is how we work today for a large energy group. A model that cannot be checked and justified does not enter the production process.
Data and artificial intelligenceKSC audit preparation, SZBI development and internal regulations, carried out together with the technical team. Requirements go into the backlog as acceptance criteria, not into a separate document. The audit trail is created while the system runs, not reconstructed after the fact.
Compliance and riskSome data cannot leave the client's infrastructure, and that is the starting point, not an exception. We design the architecture so that the data stays where the regulation requires: within the European Union or in the client's infrastructure. The same code and the same release process, regardless of the target environment.
Cloud and infrastructureOur track record in this sector
One piece of work for a client in this industry, shown in full.
A platform supporting fertility treatment, built from the start to FDA, CE and MDR requirements for the EU and US markets.
Healthcare and MedTechSystems and integrationsAutomation and artificial intelligenceKSC and NIS2
Track record from other industries
Work from other sectors where the substance is technology, not the domain. Each carries the sector it comes from.
OriginManufacturing and trade
A manufacturing and trading company has one place for knowledge, documents and internal communication.
Systems and integrations
OriginBanking, finance and debt collection
A debt collection company handles cases automatically: the system recognises documents and links data from ERP and CRM.
Systems and integrationsAutomation and artificial intelligence
OriginPublic sector
A public institution runs HR, IT and legal matters in one tool tailored to the way it works.
Systems and integrations
OriginTelecommunications
A US internet provider monitors its infrastructure with a system that keeps up with the network’s growth.
Systems and integrationsCloud and infrastructure
OriginBanking, finance and debt collection
A European financial institution sees customer and campaign data in one place instead of many sources.
Automation and artificial intelligence
OriginBanking, finance and debt collection
The companies of a multi-industry banking group work in one tool to one standard, rather than each in its own way.
Technology advisorySystems and integrations
OriginNo industry assigned
A US cloud and security company analyses network traffic as it happens, not after a delay.
Automation and artificial intelligenceCloud and infrastructure
OriginNo industry assigned
A European company runs its case workflow in the Azure cloud, and operating the system no longer takes manual work.
Cloud and infrastructureSystems and integrations
OriginBanking, finance and debt collection
A European bank releases application changes automatically, without building and publishing versions by hand.
Cloud and infrastructureSystems and integrations
You describe the process or system that no longer keeps up and what has to change. The conversation costs nothing.
We examine the process and the systems and hand over a recommendation with a scope of work. You know the scope, deadline and price of the analysis before it starts.
You receive the scope, team, schedule and price of the implementation. You decide whether we go ahead.
The cost of the analysis is credited towards the implementation if you order it.
Phone: +48 455 406 404 E-mail: contact@aliaxit.com
This site uses cookies that are necessary for it to work and, with your consent, analytics cookies that help us count visits. The details are in the Privacy policy.
Choose the categories you consent to. You can change your decision at any time via the ‘Cookie settings’ link in the footer.