TRAXIA case study
Case study – rolling out AI at TRAXIA
Time: 60 minutes Teams: 3 teams of 3–4 Output: a completed AI rollout canvas + a 4-minute pitch to the board
You are a management working group at TRAXIA s.r.o. (intelligent transport systems, ~220 employees, HQ in Banská Bystrica, branches in Bratislava, Žilina, Košice and Kraków). CEO Martina Kováčová wants a proposal by the end of the month on how to introduce AI in one process. The company runs Microsoft 365, and managers have Microsoft 365 Copilot licences. All names, companies and figures are fictional.
| Time | Step |
|---|---|
| 0–5 min | Read your case card |
| 5–30 min | Fill in the AI rollout canvas (start with boxes 1 and 7) |
| 30–35 min | Copilot as a challenger – prompt below |
| then | Pitch: 4 minutes + 3 minutes of questions from “the board” |
You are a sceptical CFO and a risk auditor. Read our AI rollout proposal [paste the canvas text]. Find the 5 weakest points: unrealistic business-case assumptions, missing risks (GDPR, AI Act, security), weak spots in the pilot and adoption. For each, suggest how to fix it.
Case A – Service 24/7, East region (Košice)
Process owner: Marek Oravec, head of Service 24/7
Process today: A customer (road authority, city, railway) reports a fault on a device – a variable message sign (VMS), a WIM scale, level-crossing protection or a junction controller. The dispatcher creates a ticket in TRAXIA Servis, sets the priority and assigns a technician. The technician goes on site, diagnoses, repairs or orders a part.
| Indicator | Value |
|---|---|
| Technicians in the region | 9 (2 joined in 2026) + 1 dispatcher |
| Tickets | ~1,400 per quarter |
| SLA met (repair within contract time) | 79.6 %, target 92 % |
| Average resolution time | 11.4 h (other regions 7.9 h) |
| Second call-out (missing part or wrong diagnosis) | 38 % of tickets |
| Contractual SLA penalties in 2026 | ~ €41,000 |
Pain points: Manuals are PDFs in three places (SharePoint, file server, technicians’ phones), some only in German and English (supplier SENSOTEC). New technicians phone experienced colleagues. Fault history has been in the system since 2021, but nobody searches it. The customer RSC Stred has filed a complaint.
Constraints: Technicians work on the carriageway and near tracks – safety procedures must be exact. Hiring new technicians is frozen for 2027. The service system has an API, but IT has only 20 days of capacity a year.
Case B – Tenders and bids
Process owner: Lucia Tóthová, sales director
Process today: Sales monitors public-procurement calls, decides bid/no-bid, prepares the technical part, the qualification documents, references and the price. The managing director signs the bid.
| Indicator | Value |
|---|---|
| Bids per year | 48 (60 % public procurement) |
| Average work per bid | 70 h (technical part 40 h, documents and compliance 20 h, pricing 10 h) |
| Win rate | 24 % |
| Average margin of a won contract | €60,000 |
| Team | 3 people + technical experts as needed |
| Disqualified for a formal error | 2 bids in 2025 |
Pain points: Tender documents often run to 200+ pages. The library of past bids (~300 documents) sits unstructured on a file server, references in Excel, certificates in e-mails. The company doesn’t yet have ISO/IEC 27001 (audit 03/2027) – some tenders require it. Sales would like to submit more bids but lacks capacity.
Constraints: Prices and calculations are confidential. Deadlines are fixed. An error in a bid = disqualification.
Case C – Technician onboarding
Process owner: HR (2 people) together with Service 24/7
Process today: A new technician receives a 120-page handbook, completes mandatory training (safety when working on the carriageway, electrical qualification) and shadows an experienced colleague (“buddy”) for 3 weeks.
| Indicator | Value |
|---|---|
| New technicians per year | ~25 across 5 branches incl. Kraków (PL) |
| Technician turnover | 18 % a year |
| Time to independence | 3 weeks + ~2 months of “questions” |
| Buddy time per newcomer | ~30 hours |
| Internal procedures | ~40 documents + 12 videos, Slovak only |
Pain points: Newcomers keep asking the same things. Experienced technicians lose time and get frustrated. Polish colleagues only have Slovak materials. HR doesn’t know where newcomers struggle most.
Constraints: Employee personal data. AI used to evaluate people’s performance = high risk under the AI Act – don’t use it to assess newcomers. Safety training must remain certified and led by a person.
Case D – Project reporting for the board
Process owner: Peter Hudec, CFO
Process today: Every month the controller assembles the board report from ERP (project costs), Excel plans and project managers’ e-mails. The report contains tables and written variance comments.
| Indicator | Value |
|---|---|
| Active projects | 30 |
| Controller’s work on the report | 2 days a month |
| Project managers’ work | 1–2 h each a month |
| D1 WIM Prešov project | +20.8 % over budget, detected late |
| What the board wants | early warning, not just month-end status |
Pain points: 80 % of the comments are the same every month. Warning signs (late supplier SENSOTEC) sit in e-mails, not in numbers. The report is ready only on the 8th working day.
Constraints: Numbers must be exact (review-ladder level 2). Few people have ERP access. Financial data is confidential.
AI rollout canvas
Team: ………………………. Case: A / B / C / D
| 1 Problem and goal – KPI today → target | 2 People and process – who, steps today → tomorrow, where AI sits |
|---|---|
| 3 Solution and tool – use / configure / delegate / build | 4 Data and systems – sources, quality, integrations |
|---|---|
| 5 Risks and controls – ladder, GDPR, AI Act, agents | 6 Business case – benefits, costs, payback |
|---|---|
| 7 Pilot – scope, time, success and exit criteria | 8 Change and adoption – fears, champions, communication |
|---|---|
Case-study scoring
Each criterion 0–2 points, max 12 points, pass ≥ 8.
| Criterion | 0 points | 1 point | 2 points |
|---|---|---|---|
| 1 Problem and KPI | missing or vague | clear problem, KPI without baseline | problem, baseline and target all measurable |
| 2 Solution and tool | tool without rationale | tool fits, weak rationale | chosen via the decision tree, alternative considered |
| 3 Business case | missing | numbers without assumptions | realistic assumptions (adoption, realisation, where the time goes) |
| 4 Risks and controls | missing | risks listed, no controls | ladder level, data, GDPR / AI Act and concrete controls |
| 5 Pilot | missing | pilot without criteria | scope, duration, success and exit criteria |
| 6 Change and adoption | missing | generic “we’ll train people” | people’s fears, champions, communication, 30-60-90 |