Demonstration

Two applications, one platform

The same edge, core and management plane, configured for two very different rooms: an operating room in a hospital and a packaging line in a plant. Each application is a room profile and a template; everything underneath is shared.

Smart operating room6 min · clinic to operating room to back office Factory line stop3 min · PLC tags and radio to an incident report

Healthcare

One patient, three moments

Two clinic visits captured by the ambient scribe, a procedure in a real operating room with the live console, and the drafts that leave for the EHR, billing, inventory, scheduling and compliance.

0:00 Title and architecture: edge in the room, core on site, workstations, management plane.
1:35 Before the case: the clinic visits, the signed notes, the pre-operative record with provenance.
2:50 During the case: room camera, wearable cameras, room audio, time-out verification and alerts.
4:05 After the case: operative note, claim, supplies, timings, compliance, and what stays on premises.
5:00 Hardware, caveats and the platform underneath.

What is real in this video

  • The scribe, the operating-room console and the back-office drafts ran on the actual Ambit edge and core services, with on-premises models.
  • The operating-room footage is a real procedure room with a real team. The time-out items shown as not confirmed are genuine detections: no time-out was performed in that recording.
  • Billing and diagnosis codes come from the scheduling booking; the system confirms them against the record and never assigns codes on its own.

What is synthetic

  • The patient and both clinic visits are fictional, scripted and voiced with synthetic speech. No real patient data appears.
  • The electronic health record is a sandbox implementing the FHIR R4 resources used, not a vendor system.
  • Hardware costs are list-price estimates, not quotes. The cloud operator and self-healing loop are shown as designed; heartbeat, relay and watchdogs are live.

Manufacturing

A line stop, written up before the line is back at speed

A labeller jams on a packaging line. The edge box in the cell reads the PLC tags and listens to the operator's radio; the on-site model drafts the incident report from both, and the work order, nonconformance report and downtime code go where the plant works.

0:00 The cell: an edge box on the line, a core on site, an audit chain underneath.
0:14 The fault: the PLC tag and the operator's call land in one record, on one clock.
1:08 Clearing the jam: lockout, cause, rejects and the lot hold, from the radio and the tags.
2:14 The incident report: every sentence cites a tag or a transmission.
2:33 Where it goes: maintenance, quality, the line system and the audit log.

What is real in this video

  • The radio audio and the tag sequence were run through the actual Ambit edge and core services. Speech-to-text, the tag reader and the drafting model all ran on premises.
  • The incident report on screen is the one the system drafted from that run: 35 facts, none unsupported, citing 16 tag changes and 20 radio segments.

What is synthetic

  • The plant, line, lot and people are fictional. The radio exchange is scripted and voiced with synthetic speech.
  • The PLC tags are replayed from the scenario rather than read from a live controller; in production the same service subscribes to the line over OPC UA.
  • The footage is stock factory video, not the line in the scenario. The work order, nonconformance report and downtime code are drafts; they are not posted to a vendor maintenance or quality system.

Operating-room footage: EgoExOR dataset, Özsoy et al., Technical University of Munich, used under the Apache 2.0 licence; volunteers performing an emulated procedure in a simulation centre. Defence footage: U.S. Department of Defense via DVIDS, public domain; the appearance of U.S. Department of Defense visual information does not imply or constitute DoD endorsement. Manufacturing footage: Pexels.

Request a live demonstration Read about the platform