--:--:-- UTC
Intuitive systems for the teams running live missions. Mission assurance and risk reduction one shift at a time, and operators ready to run what comes next.
Simulated Argos handover. The outgoing operator transmits the brief, the incoming operator restates it in their own words, the outgoing operator confirms the read-back, and responsibility transfers.
Ossirand builds software for the people running missions from the ground. Argos is the first of those products: an integration layer across the tools an operations team already runs, built to improve mission success and reduce the risk that collects between shifts, sites and systems. We intend to finish it to a standard operators trust before we start the next one.
Argos sits on top of the operations platform a team already runs and turns what it produces into a record people can hand over. Structured shift briefs, decision threads that survive a shift change, and a log the next console can query.
Telemetry, commanding and situational awareness tools already produce more than one shift can absorb. Argos interprets what they emit and applies a coordination method to it, so the output at the end of a shift is a brief the next console can act on. It does not replace any of those tools.
An operational decision is recorded with the reasoning behind it, the person who took it, and the data in front of them at the time. A correction becomes a new entry rather than a silent overwrite.
Events and actions written up during the shift while the detail is still fresh, structured as they are entered so nobody has to reconstruct the day from memory at 06:00.
A conjunction plays out over roughly a day and several shifts, with CDM revisions arriving and changing the picture. Argos tracks the thread: what each shift assessed, on which revision, and why they chose to wait or act.
A structured brief at the end of every shift, and a closed loop on the other side of it. The incoming console confirms receipt, so items cannot be quietly dropped between teams or time zones.
The Deep Space Network spaces its three complexes 120° apart, so a spacecraft is always in view of one of them. It also means no single team ever sees a full mission day. Control of the spacecraft passes between these rooms twice a day, every day of the mission.
DSS-14, the antenna in the incident below, sits at Goldstone.
NASA found three contributing causes: software weaknesses, human error, and an undetected failure in the antenna’s hydraulic limit system. That system is the antenna’s last mechanical safeguard. It was already inoperable on the day, damaged in an earlier incident that nobody wrote down. The protection was gone and the people on console had no way to know. Other industries that run around the clock have been documenting this failure mode for decades. Space operations has not.
It depends on the mode the spacecraft is in, the activity that just ran, and whether the number has been climbing all week. An operator spends the shift comparing what was supposed to happen against what appears to be happening. The comparison is the work. The reading on its own is not.
Telemetry, events, alarms, command history. Your platform captures all of it, timestamps it, and can give you any of it back on request.
The plan for the shift, the activities that were meant to run, the state the spacecraft was supposed to be in by 0400. A brief that lists what happened without carrying what was supposed to happen has handed the next operator the same raw problem in a tidier format.
These are the things an operator knows at 06:00 that no telemetry feed, alarm log or command history contains. When that person goes home, so does all of it.
“It is not the battery. I already checked.”Negative knowledge. Nothing was done, so nothing was logged, and the next operator repeats the work.
“That alarm fires every eclipse entry. Ignore it.”The system records the alarm. Only the human knows it carries no information.
“I thought about power-cycling it and decided not to. We are eight hours from a pass.”Command history records what was sent. Nothing anywhere records what was considered and rejected.
“That sensor has been flaky since Tuesday. Do not believe it.”The data looks clean. The operator knows it is not.
“I rang the thermal SME. She said give it two more orbits.”The advice has an owner and an expiry, and it lives in no system.
“I told the payload team they would have data by 0600.”A promise made to another human, now inherited by someone who never made it.
Three independent lines of evidence, all published.
DSS-14 is dated, costed and publicly investigated. Undocumented institutional knowledge cost NASA millions and took a national asset offline for years.
NASA's SpaceOps 2012 paper on ISS console logging describes flight operations tracking events, decisions and rationale to support shift handover, then notes those logs were usually kept by one operator and never visible to anyone else in real time. A separate NASA study, "Passing the Baton," found errors and accidents cluster right after handover.
The I-PASS trial (NEJM, 2014) rolled out a structured handover bundle across nine sites and 10,740 admissions. It answers the obvious objection about whether this slows operators down.
The ground segment already has good tools at every layer except one. Argos works alongside whatever telemetry and commanding platform an operator runs today, and adds the layer underneath them all.
Enterprise ground-segment platforms already serve well-funded operators. Argos is built for the teams doing real work without that budget.
Small satellite operators
Real missions on lean teams, where one person's notebook is the institutional memory.University & training labs
Rotating student operators, high turnover, almost no continuity between crews.Ground station & service providers
Multiple customers, multiple passes, handover across sites as well as shifts.Mission operations consultancies
Accountable to clients for decisions taken months earlier, often by someone else.Argos is an early working prototype. It runs. We demonstrate it directly with operators, mission teams and potential partners, and there is no open sign-up yet.
Ossirand Pty Ltd was registered with ASIC in August 2026. We are opening structured discovery conversations with operators before building further. If you run a console and have twenty minutes, we want to hear from you.
Hospitals and aviation turned shift handover into a discipline decades ago. Space operations never did. We are closing that gap before the number of people running things in orbit gets much larger. Ossirand mission statement
Tell us about your operation and we will set up a walkthrough.