An ecosystem for unmanned systems workshops

The whole workshop —in one system

From a unit’s order to a finished drone in its box: planning, department boards, warehouse, logistics, personnel status, automated flashing and an app on every phone.

3
apps, one database
10+
flashing steps with no manual work
24/7
alarms and status requests on the phone

Ecosystem

Three apps that work as one

Data is entered once and is available everywhere at once: an assignment created in the web app shows up at the flashing bench, and a drone recorded there lands in the packing list and the statistics.

  • Web app

    WorkshopHQ

    The workshop’s command centre: orders, department plans and boards, warehouse, logistics, personnel status, the events calendar, dictionaries and settings.

    • Orders and routes between departments
    • Boards, plans and capacity
    • Warehouse, logistics, personnel status
  • Flashing bench app

    Auto-Flasher

    Takes a drone through the whole software cycle from a profile: flight controller firmware, fonts, configuration, receiver, memory backup.

    • Approved profiles with their files
    • Assignments, barcodes, boxes
    • Statistics for every step
  • Android and iPhone

    WorkshopHQ Mobile

    Full-screen alarms, status requests, the daily check-in, the duty calendar, logistics requests and drivers’ routes.

    • Alarms that ring through silent mode
    • Daily check-in and status board
    • Logistics on the road

How work moves

An order travels through the departments by itself

Every order item has a route. Departments see their part on their own board, pick up the work and hand it on — all of it or a part.

  1. 1

    Order

    Unit, items, deadlines, priority, extra works.

  2. 2

    Warehouse

    Issues drones into work; stock goes down automatically.

  3. 3

    Repair

    A queue of batches, output and rejects per shift.

  4. 4

    Flashing

    Assignments per person; Auto-Flasher records each drone.

  5. 5

    Packing

    Boxes, the packing list, flight-test status.

  6. 6

    Issue

    Daily issue to units and delivery logistics.

A route is set per drone type and can be changed for a single item. When a step is done, the next department is notified.

Web app

WorkshopHQ

Orders and boards

Orders you can follow from start to issue

A board, a calendar and a list over the same data. Every department works on its own board; command sees the whole picture.

Kanban-style boards

A card is one step of an item in a department. People drag it between columns, take it into work and hand the needed quantity to the next department.

  • Columns: Waiting, New, In progress, Done, Cancelled
  • Four priority levels, categories (production, testing, special task), assignees, work-in-progress limits
  • Shared views per department and personal settings
  • Reminders to assignees twice a day
The general orders board: one card per item, at its current route step

The order page

State, dates, items with their routes and a timeline with a completion forecast: it is clear at once whether the workshop will meet the deadline.

  • Items with drone type, quantity, bind phrase and extra works
  • A forecast from time norms and the people actually on shift
  • Time reserved for the flight test before the deadline
  • Repeat an order over several days
An order: state, timeline, items and progress by department
  • Orders calendar

    Day, week, month or year: order bars from start of work to the deadline.

  • Routes

    The sequence of departments for each drone type, with an assignee per step.

  • Repair queue

    Batches with “taken” and “handed over” buttons for quick tracking.

  • Work notifications

    Leads and assignees learn when new work arrives or a step is finished.

Planning and figures

Know in advance whether you will make it

The system calculates department load from time norms per drone and people’s real presence: shifts, duty, training, leave.

Workshop dashboard

Today’s load, orders at risk, deadlines, volume in work and the reject rate over a period.

  • Booked versus capacity charts for each department
  • A warning for orders that will not fit their deadline
  • Output per day, week, month or quarter
The workshop dashboard with department load and the forecast

The flashing department plan

What was done today, the work queue, who flashed how many, and which orders are next.

  • Each person’s output from assignments and Auto-Flasher data
  • Capacity per shift, allowing for leads and duty
  • The formulas can be shown right on the page
Department plan: load, output, the nearest queue, output per person
  • Department capacity

    How many drones a department can do in a day, per shift.

  • Time norms

    Minutes per drone per department, with factors for drone types and extra works.

  • Presence aware

    The plan accounts for duty, training, sick leave and holidays from the calendar.

  • Data for statistics

    Output and rejects are recorded per day, shift and person.

Flashing department

Assignments, profiles and bench statistics

The shift lead distributes the work, an admin curates the catalogue of approved profiles, and every flashed drone is recorded automatically.

Shift assignments

Who does what and how much today. An assignment comes from an order item and carries the bind phrase and the recommended profiles.

  • Progress updates from the bench in real time
  • Assignments shown on the department board cards
  • Move or finish an assignment in one click
Assignments for the day: person, item, bind phrase, progress

Auto-Flasher statistics

How many drones were checked, how many failed, which steps are retried most — by operator, profile and shift.

  • An overview and details per process step
  • Filter by period, shifts and operators
  • Each drone counts once; step retries are counted separately
Flashing bench statistics for the chosen period
  • Profile catalogue

    Approved flashing recipes with files, tags and filters by control link, video and board.

  • Base profiles

    One base profile generates variants for different frequencies and modules.

  • File store

    Firmware, fonts and receiver builds are stored once and verified by checksum.

  • Drafts

    Prepare a new profile and publish it when it is ready.

Packing and warehouse

From the bench to the box and the stock on the shelf

Every drone has a barcode, a box and a flight-test status. The warehouse knows what is on the shelf and how many days it will last.

Stock and “time to reorder”

Stock of each drone type, the average daily issue and the number of days it will last. When stock falls below the threshold, the system warns.

  • Deliveries and recounts with a change log
  • Automatic deduction when the warehouse issues drones into work
  • A daily notification about types to reorder
Warehouse stock: quantity, daily issue, days of cover

Daily issue

A versioned list of what is issued to whom every day. It can be imported from a message’s text, and two versions can be compared.

  • Quantity per day, week or month; pause and priority per line
  • Text import that recognises drone types
  • Version comparison with export to an image
Daily issue: lines per unit, frequency, state and priority

Boxes and the packing list

Drones are collected into boxes by type and customer. The packing list shows what the flight group collects, with control and video frequencies.

  • A drone is recorded by scanning its barcode — at the bench or in the web app
  • Flight-test status for every drone
  • A warning about drones without a box
Packing list: configurations, boxes, people, flight test
  • Barcodes

    The history of every drone: who flashed it, when and with which profile.

  • Boxes

    Daily numbering, capacity by drone type, handover to the flight group.

  • Warehouse board

    Issue-into-work and collect-finished steps as cards.

  • Stock log

    Every change to stock: deliveries, issues, recounts — who, when and why.

Logistics

Requests, trip sheets and the fleet

Department command raises requests to move people and cargo. Logistics groups them into trip sheets, and the driver runs the route from a phone.

Logistics plan

What awaits planning, what is on the road, which vehicles and drivers are free — on one screen.

  • Requests with a time window, urgency and a contact person
  • The fleet with readiness and reasons for unavailability
  • Routes completed today and over the week
The logistics plan for today

Trip sheet

Stops are built from the requests automatically: pick up first, then drop off. The order can be changed, and a waypoint or a note added.

  • Several requests in one route; shared addresses are merged
  • The driver marks stops; a journal records every action
  • A warning if the driver has duty or leave that day
A trip sheet: vehicle, driver, stops, request items and the journal
  • Schedule

    A day or a week by vehicle or by driver — overlaps and free slots are visible.

  • People and cargo

    Request items: who or what, from where to where, with locations from the dictionary.

  • Notifications

    The driver learns about an assignment; the requester about planning and completion.

  • “Departure soon”

    A reminder on the driver’s phone before the route starts.

Personnel status board

Know who is on duty every morning

A daily check-in, figures over a period, alarms and status requests with a live board of answers.

Daily check-in

Everyone confirms their status before a set time — from the phone, the web app or the flashing bench. The duty officer sees who has not answered yet.

  • A reminder on all of a person’s phones before the deadline
  • Leave, sick leave and trips are accounted for automatically
  • A ready-made report text for a messenger and XLSX export
Daily check-in: today’s statuses and those still to confirm

Alarm board

An alarm arrives as a loud notification on the phone and a window in the apps. The board shows who is safe, who needs help and who is silent.

  • Alarm templates by location, department, role or person
  • “All clear” or “need help” answers with a note
  • Reminders to those who did not answer; call or message from the card
Alarm board: answered, need help, not answered

Status figures

Personnel status over a day, week, month or year — by status or by person, filtered by unit, department and location.

  • On duty, duty officer, reserve, training, leave, sick leave, trip
  • A history of alarms and status requests
  • Export of the chosen columns
Personnel status: figures over a period
  • Alarms

    Raised from a template; an alarm always takes priority over other notifications.

  • Status requests

    A calmer format: “confirm you are fine”. Sent by hand or on a schedule.

  • Personnel list

    Rank, callsign, department, location, contacts, roles and status of each person.

  • Roles and access

    User, shift lead, duty officer, administrator.

Personnel events calendar

Duty and reserve days — fair, and without spreadsheets

A month calendar for everyone and a planner that distributes duty and reserve days by clear rules.

Event planner

Proposes a plan for the month: as few duties per person as possible, shared equally among a location’s people, and a reserve day every week on the same weekday. The plan can be previewed and adjusted by drag and drop before it is applied.

  • No back-to-back duties, none on the eve of a reserve day or straight after leave, sick leave or training
  • A cap on the share of a department on reserve at once
  • Requests for a preferred reserve weekday, with approval
  • Penalties and pinned events survive a recalculation
Planner: what is added, what is removed, warnings

Events calendar

Duty, reserve, leave, sick leave, training and trips for everyone. Department capacity is calculated from it too.

  • Filters by event, person, unit, department, location
  • Cards for “my next events”, “on duty today” and birthdays
  • An absence automatically removes duty on those days
The personnel events calendar

Flashing bench app

Auto-Flasher

Automated drone flashing and configuration

The operator connects a drone, picks a profile and presses one button. The app runs every step, checks the result and records it in WorkshopHQ. It suits any unmanned system on a supported controller: multirotors, fixed wing, VTOL and more.

What one run does

  1. Finds the flight controller and checks the board
  2. Compares the firmware version and reflashes if needed
  3. Uploads OSD fonts
  4. Runs the CLI configuration commands
  5. Configures the speed controllers
  6. Calibrates battery measurement
  7. Sets up the video transmitter ports
  8. Saves a backup of the controller’s memory
  9. Builds and flashes the ExpressLRS receiver
  10. Records the drone in the assignment, box and statistics

A profile is a ready recipe

A profile describes one drone configuration: the expected firmware, files, commands and receiver settings. Approved profiles come from the server with their files — the operator has nothing to look for on disk.

  • The workshop’s approved profiles and the operator’s own
  • Search and filters by control link, video, board and tags
  • Import and export a profile as JSON
  • Tag stickers with the profile’s data
Preparing a run: the chosen profile and its parameters

Assignments right at the bench

The operator sees the shift’s assignment, how much is done, which drones are recorded and which boxes they are in. The barcode is scanned before the run.

  • Today’s load on the home screen
  • The assignment’s drones and boxes
  • Works offline: records are sent when the server is reachable again
A shift assignment: progress, drones, boxes

Operator statistics

Drones checked per shift, the success rate, flashed controllers and receivers, step retries. A shift report is produced in one click.

  • Filter by day and shift
  • Breakdown by profile and step
  • Export as JSON
Flashing statistics for the chosen period
  • Drivers and tools

    Diagnostics finds ports and DFU mode and installs the drivers and utilities needed.

  • Different controllers

    STM32 and AT32 boards; several firmware images in one profile — the app picks the right one.

  • Alarms at the bench

    The daily check-in, alarms and status requests appear in Auto-Flasher too.

  • Updates

    New versions of the app arrive from the workshop’s server.

Android and iPhone

WorkshopHQ Mobile

The workshop in everyone’s pocket

An app for Android and iPhone: personnel status, alarms, the calendar and logistics. It works outside the workshop network through a protected gateway.

  • Full-screen alarm
  • Status request
  • Daily check-in
  • Events calendar
  • Alarm board
  • Logistics plan
  • An alarm you cannot miss

    Opens full screen and sounds even in silent mode. One tap to answer.

  • Daily check-in

    A reminder before the deadline and a status confirmed in seconds.

  • A board for the duty officer

    Who has not answered an alarm or confirmed a status — with a call right from the list.

  • Calendar and reserve

    Your own duties, shift handover, a request for a preferred reserve day.

  • Logistics

    Requests, trip sheets, the schedule; the driver runs the route and marks stops.

  • PIN and demo mode

    Quick unlock with a PIN. Demo mode shows the app with no server or account.

Android and iPhone

Platform

Your server, your data

The system is deployed on the workshop’s own server and does not depend on third-party cloud services.

  • Self-hosted

    Runs on a small server in the local network; the data never leaves the workshop.

  • Protected access

    A private network for workstations and a separate keyed gateway for phones.

  • Role-based rights

    What a person sees and may change is set by role and department — at the database level.

  • Notifications

    In the apps and as push notifications on Android and iPhone.

  • Background jobs

    Reminders, checks and clean-up run on a schedule with a run log.

  • Journal and feedback

    Users’ reports and the apps’ error reports are collected in one place.

Contact

Get in touch

Want to see the system at work, order a rollout, ask something or share feedback? Pick the type of request and write a few words. We will reply to the address you give.

  • A demonstration or a trial on fictional data
  • A rollout on your own server: departments, routes and profiles for your processes
  • Feedback, suggestions and questions from users

Or write directly:info@workshop-hq.dev