Savvidis Technologies Request a quotation

Electronics that ship.

From a blank schematic to a fleet of connected devices on the road. Savvidis Technologies designs the boards, writes the firmware, builds the software and the factory tooling behind them, and ships its own platform for emergency medical services: ResQvara and AmbuLink One.

Request a quotation

ResQvara and AmbuLink One

Our own platform for emergency medical services, engineered end to end and built to be deployed: the AmbuLink One unit in every vehicle, its firmware, the ResQvara dispatch and operations software, and the factory tooling that prepares each unit. Both are in active development, and open to ambulance services, private EMS providers and fleet operators who want to run them.

A moving dot tells you where. ResQvara shows what is happening.

Dispatch and operations software for ambulance services, fed by the AmbuLink One unit in every vehicle. Calls, readiness, live positions, crews, care records and reports in one system, where every decision stays with the person accountable for it.

  1. 1Call
  2. 2Triage
  3. 3Assign
  4. 4Respond
  5. 5Care
  6. 6Insight

Six stages, one system. Scroll to put the dispatch screen together and run one mission through it.

Call. A call taker records the location, a callback number and notes, and incident 2207 is pinned. An assistant may suggest questions. It does not decide.

Triage. The dispatcher sets priority P1 at 14:03. Every change is attributed and kept in the audit trail.

Assign. Four checks before a unit goes: vehicle available, roster fit, a named driver, room for the crew. AMB-14 passes all four.

Respond. Siren, lights and speed come from the AmbuLink board. “En route” comes from the crew. The screen keeps the two apart.

Care. The crew completes the patient care record. At the hospital the board reports the ignition off and the rear door open.

Insight. Every mission feeds operations: emergencies, booked transfers and event cover on one timeline.

Incident 2207P1 · dispatcher

Adult, chest pain, conscious

Location
Ampelokipoi, pinned on the map
Callback
+30 69•• ••• •12
Notes
Pain for 20 minutes, breathing, talking
  1. Incident created · call taker
  2. Priority set to P1 · dispatcher
  3. AMB-14 assigned · dispatcher
  4. En route · crew
ReadinessFour checks before a unit goes
UnitVehicleRosterDriverCrew
AMB-14yesyesyesyes
AMB-07out of servicenot checkednot checkednot checked
AMB-22yesyesno named driveryes
AMB-31committed to event coveryesyesyes
  • AMB-14 ready, crew of two: assigned
  • AMB-07 out of service
  • AMB-22 no named driver
  • AMB-31 committed to event cover
AMB-14Mission 4471 · updated 4 s ago

From the AmbuLink board

Movement
Driving
Speed
46 km/h
Siren
On · mode 2
Warning lights
On
Heading
South · Kifisias Ave
Rear door
Closed

Set by people

Status
En route to 2207 · crew
Priority
P1 · dispatcher
Care recordMission 4471
  1. Observations recorded · crew
  2. Treatment recorded · crew
  3. Arrived at hospital · crew

At the hospital, from the board

Ignition
Off
Rear door
Open

Clinical review requested

38emergency missions

21booked transfers

2venues with event cover

06:0008:0010:0012:0014:0016:0018:0020:0022:00

Demo: units, people, times and figures are invented. Streets © OpenStreetMap contributors.

Who works in it

Dispatcher
runs the mission, sets priority, assigns units
Field crew
receives runs, sets status, writes the care record
Clinical staff
reviews care records, follows up
Operations
fleet use, workload, reports across services

What the board reports

Vehicle
speed, movement, ignition, doors
Emergency kit
siren and its modes, warning lights
Vehicle bus
OBD data over CAN or K-Line
Trust
signed sessions, jamming and spoofing watch

Signals depend on the board model, the wiring and the vehicle.

Oversight

Tenants
each service sees only its own data
Access
by role
Audit trail
every change, attributed
Decisions
made by people; assistants gather information

ResQvara runs your control room, your fleet and your care records as one system. See it with your own data.

Request a ResQvara demo

How the pieces connect

How ResQvara fits together AmbuLink One units send telemetry over LTE-M or NB-IoT to the ResQvara backend, which serves the dispatch dashboard over HTTPS. ResQvara Factory provisions each unit over a J-Link probe and registers it with the backend over HTTPS. LTE-M / NB-IoT HTTPS HTTPS J-Link RTT AmbuLink One In each ambulance: position and OBD-II data ResQvara backend Receives telemetry, serves the dashboard Dispatch dashboard Live fleet map, seven languages ResQvara Factory Provisions and checks every unit How ResQvara fits together AmbuLink One units send telemetry over LTE-M or NB-IoT to the ResQvara backend, which serves the dispatch dashboard over HTTPS. ResQvara Factory provisions each unit over a J-Link probe and registers it with the backend over HTTPS. LTE-M / NB-IoT HTTPS J-Link RTT HTTPS Dispatch dashboard Live fleet map, seven languages ResQvara backend Receives telemetry, serves the dashboard AmbuLink One In each ambulance: position and OBD-II data ResQvara Factory Provisions and checks every unit

Dispatch dashboard

  • Fleet dispatch and vehicle telemetry on a live MapLibre map
  • Interface translated into seven languages, Greek and English among them
  • Sign-in for authorised staff
  • Self-hosted and released through CI with near-zero downtime

ResQvara Factory

  • Windows and Linux app built with Electron, TypeScript and React
  • Talks to each board through a J-Link probe over RTT
  • Reads board identity: serial number, secure-element public key, IMEI
  • Exports a factory report of what actually ran: PASS, FAIL or INCOMPLETE
ResQvara Factory

Factory workflow

  1. DeploymentImport the approved profile, verify the backend and live TLS, install the CA bundle.
  2. DeviceConnect the J-Link probe over RTT and read the board’s identity.
  3. DiagnosticsRun the safe-command checks on the connected board.
  4. ProvisioningRegister the unit’s credentials and enrol it with nRF Cloud.
  5. Factory reportExport what actually ran, PASS, FAIL or INCOMPLETE, as JSON and Markdown.
The production workflow in ResQvara Factory, from deployment profile to the final report.

From layout to board

How AmbuLink One comes together, from the first outline to a finished board.

Board outline

The edge comes first: the outline everything else has to fit inside.

Placement

Every footprint on its spot: the radio, the vehicle interface, memory, power stages and connectors.

Routing

The top layer, routed net by net, then the inner signal layers.

Planes and the bottom layer

Power planes poured on the inner layers, then the bottom layer.

Vias, then 3D

Vias stitch the layers together. Next: the same file as a real board, part by part.

Every layer of your product

Products fail in the gaps between disciplines: a board the firmware cannot drive, firmware the factory cannot test, a cloud that cannot trust its devices. The engineering behind ResQvara and AmbuLink One is available for your product too. Bring an idea, a prototype in trouble, or a design on its way to production.

Hardware design

Schematics and multilayer layout for boards that have to leave the lab: mixed-signal, power and RF on one board, with signal integrity, thermal paths and EMC designed in from the first placement instead of patched in after the first failure.

Schematic and layout
KiCad, Altium Designer
Multilayer boards
stack-up, controlled impedance, differential pairs, length matching
Via technology
epoxy-filled, capped, tented
Power electronics
DC/DC, protection, high-current motor drives
Analog and sensing
precision ADC front ends, active filters
RF and antennas
LTE-M, NB-IoT, GNSS, 433 MHz
Vehicle-grade inputs
reverse polarity, transients, ESD
Manufacturing
DFM, test access, BOM risk

Firmware and software

Firmware that boots every time, updates itself safely and survives the field, in C and C++ from register-level drivers to signed updates over the air. And the software above it: the tools, apps and dashboards a product needs to be built, sold and supported.

Embedded
Zephyr, vendor SDKs, bare metal
Board support
Devicetree, Kconfig, bring-up
Boot and updates
MCUboot, signed FOTA
Security
secure-element identity, TLS
Drivers and buses
UART, SPI, I²C, CAN FD, USB
Applications
TypeScript, React, Electron
Automation
Python, test rigs, CI builds

Embedded systems engineering

The whole product, not only the board: the architecture that decides what runs where, connectivity that holds in a moving vehicle, a cloud that knows which device is talking, and a factory process that provisions, tests and traces every unit it ships.

Architecture
hardware, firmware and cloud split
Connectivity
cellular IoT, GNSS, short-range RF
Vehicle buses
CAN FD, K-Line, OBD-II
Cloud and fleet
device identity, telemetry, live maps
Validation
oscilloscope, spectrum analyser, VNA
Production
fixtures, provisioning, factory reports
Field support
diagnostics, root cause, fixes

Consultancy: senior engineering judgement on your design reviews, architecture decisions and prototypes in trouble, by the day or by the project.

Ask about consultancy

How a project runs

Evidence over assumptions, at every step. Each stage ends with something you can hold and check: a document, a board, a log or a report.

Project traveller

Before design

Define
requirements, cost target
Architect
block diagram, part choices

Design and build

Design
schematic, layout, firmware plan
Bring-up
powered boards, bring-up log

Proof and production

Validate
bench measurements, test report
Production
test fixtures, provisioning tools

You holddesign files, firmware, test record

About Savvidis Technologies

Savvidis Technologies exists for one reason: a lifelong passion for electronics that work, on the bench, on the road and years after they ship. It is the practice of Nikolaos Savvidis, an electronics and embedded systems engineer based in the Netherlands, who takes a product from the first sketch and schematic to firmware, cloud and a tested unit, across mixed-signal design, embedded control and power electronics. It is the same engineering that built ResQvara and AmbuLink One. Boards are drawn in KiCad and Altium Designer. Firmware is written in C and C++, on bare metal and on Zephyr and vendor SDKs. The radios range from 433 MHz links to LTE‑M, NB‑IoT and GNSS. Every design is measured before it is trusted: oscilloscope, spectrum analyser, VNA. In Nikolaos’s own words, “I build systems that don’t just simulate well, they work in the lab.” Tell us what you are building.

Tell us what you’re building

A custom design, a product in trouble, or ResQvara and AmbuLink One for your service: request a quotation or ask a question. Prefer email? Every inbox is listed below the forms.

Request for quotation

Choose what you need and the stage you are at. Your request takes shape here.

What helps us quote

  • What the product does and where it will be used
  • Interfaces, radios and power source
  • Quantities and a target unit cost
  • Deadlines and the standards that apply

Quotation requests go to [email protected].

What do you need? Required
Where is the project now? Required

What it does, where it will be used, the interfaces and radios it needs, and any standards that apply.

We use these details only to answer your request. Read the privacy notice.

General inquiry

Questions about our work, partnerships, supplies or press.

Messages go to [email protected].

What is it about? Required

We use these details only to answer your message. Read the privacy notice.

Write directly

Based in the Netherlands. Schematics, code or documents can follow by email once we reply.