Human-in-the-loop command software for Air–Ground coordination
MARDE Nexus is the proposed human-in-the-loop coordination layer for Air, Ground and responders. V1 planning includes aerial and ground video, two-way communication, supply counts, dispensing confirmation and explicit authorization of deployment, release and retreat. A responder tablet or laptop view is a demonstration objective. The website interface is illustrative and has no live aircraft, patient or dispatch connection.
MARDE Inc. is a Delaware C-Corporation based in New Jersey, with an initial institutional focus on New Jersey and the Northeast United States. It is pre-seed, pre-prototype and pre-revenue. There are no deployed systems, commercial pilots or validated full-system performance results. The next milestone is an integrated, human-in-the-loop V1 demonstration. This page describes development objectives, not an available emergency-response service.
Where it fits in the intended response
The proposed demonstration sequence is simulated dispatch, Nexus review, Air transport, controlled hover lowering, outdoor Ground approach, human-authorized supply dispensing and a simulated EMS handoff. Authorized retreat and pickup by a landed Air platform complete the recovery concept. This is not an existing dispatch integration. Each transition needs a responsible person, a known system state and a way to stop when assumptions no longer hold.
Coordination means more than showing several vehicles on a screen. The person controlling Air may need to confirm that Ground can proceed, that the payload remains secured and that a handoff location is understood. An agency also needs to know who may stop the mission and how responsibility transfers to professional responders. These are proposed workflow requirements to investigate with practitioners.
Human oversight comes first
V1 is intended to remain human-in-the-loop. Consequential actions require operator authorization, and the overall system is intended to complement EMS rather than replace clinicians or responders. Higher autonomy is a possible future direction that depends on measured reliability and appropriate evaluation. A concept drawing or interface illustration does not establish safe operation.
Requirements conversations should distinguish who operates the system, who accepts the payload and who makes clinical decisions. These responsibilities may involve different people. The proposed workflow needs explicit boundaries and a practical fallback when the mission cannot continue. An emergency-response concept must remain useful to professionals even when the robotic component is unavailable.
Open engineering questions
Nexus engineering must investigate the information an operator needs before an action, how current that information is and how uncertainty is displayed. A readiness label is useful only if its source and limitations are clear. Communication loss, stale telemetry, ambiguous location and competing alerts need defined handling. MARDE has not published measured control latency, availability, integration coverage or operator workload results.
Testing needs to connect the subsystem to the rest of the architecture. A component can succeed in isolation while the combined workflow fails because of timing, packaging, communications or a confusing handoff. MARDE's immediate goal is to investigate those interactions in a controlled integrated demonstration before making claims about operational use.
Evidence needed before evaluation
A useful Nexus evaluation would measure operator understanding, missed alerts, mistaken authorizations, time to recover from communication loss and clarity of the handoff record. Controlled exercises should include interrupted and rejected missions. There is no public operational robot-control API or deployable Nexus software offered through this website. Research and requirements conversations should use the existing Contact page.
Agency evaluation should start with a written use case and success criteria agreed before testing. Records should distinguish design targets, bench observations, integrated exercises and operational outcomes. Changing a configuration or setting can invalidate a previous result. Published evidence should therefore describe limitations, exclusions and the circumstances under which a conclusion applies.
Discuss requirements with MARDE
MARDE welcomes institutional conversations with EMS agencies, fire departments, municipalities, researchers and public-safety teams. Useful input includes access barriers, operator responsibilities, dispatch constraints and acceptable evaluation conditions. The initial regional focus is New Jersey and the Northeast United States; this describes research interest, not service coverage.
Use the Contact page to discuss requirements or future evaluation opportunities. Do not send patient records or request live emergency assistance through the website. No price, purchase offer, deployment date or pilot commitment is implied by this page. The appropriate next step is a factual discussion about what would need to be built and demonstrated.