The platform
Three apps run the shop. Three records carry the aircraft.
Dash Aero is one platform. Mechanic Workbench, Shop Control, and Operator Portal sit on a single maintenance-event spine — backed by Collaboration Rooms, the Aircraft Service Record, and Technical Intelligence. Mechanics capture work at the aircraft. The shop runs from facts. The customer sees the view that is theirs. Proven inside a working aircraft maintenance operation.
A task card advances until a hold point blocks it; the step cannot continue until a photo lands; the hold clears the moment the photo lands. An offline badge flickers on and work carries on; when the signal returns, sync resolves.
Mechanic Workbench
For mechanics, leads, and inspectors — at the aircraft.
Capture work standing at the aircraft, not from memory at the bench. Copilot takes voice, photos, and measurements hands-free; Live Assist brings a second set of eyes to the exact spot you are looking at. Every step, hold point, and piece of evidence lands in the record as it happens.
- Task cards with hold points that block progression until the required evidence lands.
- Findings keep observation, suspected cause, and authorization distinct — never collapsed into one field.
- Evidence capture at the point of work: photo, video, voice note, measurement, borescope, NDT.
- Work performed carries parts traceability — removed and installed components, release documents, serials.
- Offline hangar mode: capture continues with no signal, nothing is lost, conflicts surface on sync.
Your careful work finally looks as careful as it was.
The command center assembles: today's tiles populate, a blocker surfaces with an owner attached, and the delivery-confidence gauge sweeps to its honest number.
Shop Control
For service advisors, project managers, schedulers, and the back office.
Run the shop from a command center, not from memory. One view holds every aircraft, decision, blocker, and delivery risk — each one drillable to the source work item behind it. AOG work inserts into the schedule and shows its downstream effect before you commit.
- Today command center surfaces the aircraft, decisions, and blockers that need attention now.
- Work board with gated columns — a card never moves past a missing authorization, inspection, or test.
- Records completeness matrix fills cell by cell; a missing signature blocks delivery, not hope.
- Delivery desk verifies eleven independent readiness dimensions — technical, quality, records, financial, each earned separately.
- Billing traces every invoice line to authorized, performed work — no line appears that nobody approved.
Explain any delay in ten seconds, not ten phone calls.
A record's status flips from Internal to Published. The audience fan opens — Owner and DOM — and the audit line appends the signature: version 2, published by S. Ortiz at 2:14 pm.
Operator Portal
For owners, DOMs, pilots, accounting, and management companies.
Your customers stop calling — because they already know. Each role opens to a different view of the same committed facts: the owner sees status and cost, the DOM sees work-item states, the pilot sees the squawk thread, accounting sees the invoice. Nothing internal reaches the customer until the shop chooses the audience and publishes.
- Role-adaptive home — owner, DOM, pilot, and accounting each see the view that is theirs.
- Findings and approvals inbox with per-line decisions: approve, decline, defer — each with its own life.
- Live event timeline replaces the status phone call; milestones link to the source finding or approval.
- Costs distinguish estimate, authorized, performed, and invoiced — the line between them never blurs.
- Pre-purchase workspace partitions buyer and seller access; a broker sees only what a broker should.
The invoice is never a surprise — because every line was approved when it happened.
An external expert enters a scoped collaboration room and sees the three items the scope admits, not the whole ledger. A timer sweeps the access window; when it expires, the expert leaves.
Collaboration Rooms
For OEMs, engineers, component shops, NDT providers, insurers, and regulators.
Bring outside expertise into one case without exposing the rest of the aircraft, the customer, or the shop. Access is scoped to the exact event, finding, or component the case needs — and it expires when the case closes. Every question, evidence request, and disposition stays attached to the case, not buried in an email thread.
- Scoped to one event, work item, finding, or component — never the whole aircraft or shop.
- Expiring access with a visible clock; the room closes when the case closes.
- OEMs, engineers, component shops, NDT, insurers, and regulators see only what the case requires.
- Every technical response carries author, organization, authority, and revision — a quote is never an authorization.
Bring in exactly who you need. Show them exactly what they need. Nothing else, and not forever.
Aircraft Service Record
The persistent layer under every maintenance event.
One longitudinal record per aircraft. Every event the shop has touched, every component it has serviced, every observation it has made — preserved with source and provenance, ready the moment the aircraft comes back. A recurrence reopens the complete original context instead of starting from a blank ticket.
- Persistent, longitudinal history — every event the shop has worked, in one record per tail.
- Component history and condition trends: compression, borescope, oil analysis, wear items over time.
- Source and provenance on every observation — shop-performed and customer-supplied never blur together.
- A comeback carries the original work, parts, tests, and prior communications forward — nothing is reconstructed from memory.
A comeback starts with the complete original context — not a blank new ticket.
A typed symptom surfaces prior cases from the hangar’s memory. The cards slide in with matched phrases highlighted, and a badge counts three similar cases.
Technical Intelligence
The shop’s compounding memory.
Every solved case makes the next diagnosis faster. Similar-case retrieval, recurring-discrepancy detection, and condition trends draw on the shop’s own history — the institutional knowledge that lives in a senior mechanic’s head, made searchable and attributable. The revision-controlled technical library keeps the source used for the work tied to the source cited in the record.
- Similar-case retrieval surfaces prior cases by symptom, fault message, component, or outcome.
- Recurring-discrepancy detection across aircraft, components, and tasks — correlation never presented as confirmed cause.
- Condition trends and longitudinal measurements, drawn from real shop observations.
- Revision-controlled technical library — the reference used for the work is the reference cited in the record.
Your shop’s memory compounds. Every solved case makes the next diagnosis faster — an advantage nobody can copy overnight.
The structure is the proof
No invented customer counts. These are the dimensions the platform actually governs — counted live from the data model, not rounded up for a slide.
- 0
Work-item states — every step has a name and an audit stamp
- 0
Independent readiness dimensions — each earned separately
- 0
Finding states — observation, diagnosis, and authorization never collapse
- 0
"No X" invariants the data model refuses to let a shop violate
Every performed item carries its authorization basis — sign here traces back to the approval that let the work happen.