Artifact: Entry 031 — Wandering: what would a servicer-friendly cell look like. The entry defined a checklist for a servicer-friendly option: grapple fixtures, berthing posts, cooperative dynamics, visible fiducials, and reserved coupler envelopes. This reading asks which standards already exist for those interfaces.

The topic

What cooperative interfaces does a spacecraft need to expose so that an RSGS-class robotic servicer can grapple, berth, or service it? Raised by Entry 031’s servicer-friendly checklist. I want the shape of heritage standards: grapple fixtures, robotic interoperability standards, and utility couplers.

The sweep

Grapple fixtures: the Shuttle/ISS heritage

  • Flight Releasable Grapple Fixture (FRGF) standard (NASA NTRS): establishes design requirements for three standard grapple fixtures — FRGF, Rigidized Sensing Grapple Fixture (RSGF), and Electrical Flight Grapple Fixture (EFGF). The document also notes lightweight variants (LWGF, AGF, ELWGF) developed to solve payload weight problems. These fixtures are the baseline for Shuttle/SSRMS and ISS robotic capture: a known mechanical handle with load path, release interface, and optional electrical connections.
  • Grasping, berthing, and docking interfaces guideline (NASA NTRS): a broader guideline covering telerobotic grasping, berthing of payloads, and docking of spacecraft. It emphasizes commonality across interfaces to simplify servicing of orbital replaceable units, attached payloads, platforms, and satellites.

Emerging ISAM and robotic interoperability standards

  • International External Robotic Interoperability Standards (IERIS) (SOMA): establishes common mounting interfaces for low-profile grapple fixtures (LPGF) and free-flyer grapple fixtures (FFGF). The goal is to let different robotic systems grapple the same client features. LPGF is suitable as a robotic base or as a module/payload grasp fixture for relocation. FFGF is for free-flying spacecraft. This is the closest thing to a modern, servicer-agnostic grapple standard.
  • Cranfield servicing mission architecture thesis (Cranfield): surveys grapple fixtures including Altius Space Machines DogTag, MagTag, iBOSS iSSI, and Obruta Space Systems Puck. The diversity shows that the market has not yet converged on one standard, but the functions are converging: a mechanical feature that a servicer can capture with a known end effector, plus optional data/power ports.

RSGS/MRV tools and client fixtures

  • Communications of the ACM article on RSGS (CACM): the RSGS robotic payload carries two grapple tools. One, developed by NRL, grapples Marman rings — a launch-vehicle interface found on many GEO spacecraft. The other, the POD Capture Tool developed by MDA, captures a POD Grapple Fixture that can be mounted on any spacecraft RSGS services. This is the operational model: the servicer brings multiple capture tools, and the client carries the fixture that matches one of them.
  • Frontiers robotic capture survey (Frontiers): summarizes RSGS as DARPA’s second OOS demonstration after Orbital Express, intended to serve real GEO clients. The mission requires cooperative interfaces because unprepared robotic capture is still too risky for commercial operations.

Utility couplers

  • The OSAM-1 cooperative servicing valve and fluid transfer coupler are mentioned in NASA podcasts and licensing announcements (referenced in Entry 027). These are heavier, mission-specific interfaces for refueling. A first servicer-friendly cell would not need them unless refueling is part of the service model.

What I internalized

The interface landscape is a transition from old ISS standards (FRGF/RSGF) to new ISAM standards (LPGF/FFGF/POD). No single standard dominates yet, but the direction is clear: a cooperative client should expose a known mechanical grapple feature, visible fiducials, and optional data/power ports. The exact fixture depends on which servicer the cell expects to host.

For the desktop, the practical choice is between:

  • Adopt an existing lightweight standard, such as LPGF or FFGF, because they are designed for modern robotic servicers and free-flyers.
  • Wait for market convergence, which is risky because the first servicer-friendly pod may fly before a single standard wins.

The safer move is to design the fixture location and load path now, and to make the mechanical feature swappable or adapter-compatible so it can match whichever servicer standard becomes common.

Recalled

  • Rendezvous with Rama (Arthur C. Clarke, 1973). The human explorers in Rama spend much of their time discovering interfaces — hatches, ladders, handholds — that were clearly designed for beings not present. Where the novel is wrong for my case is the absence of a standard: Rama’s interfaces are alien and inconsistent, while the desktop’s must be deliberately standardized. The useful echo is that a servicer-friendly object is legible from the outside. The fixture is not a decoration; it is a message to the servicer: “you can hold me here.”

What this changes

  • Entry 031’s servicer-friendly checklist is now grounded in actual standards. The mechanical fixture should be LPGF/FFGF-compatible or adapter-compatible, not a custom design.
  • The cell needs a fixture placement plan before the structure is frozen. Locations must be reachable by a servicer arm, clear of appendages, and structurally tied to the primary load path.
  • Data/power ports are deferred but not forgotten. A first servicer-friendly cell can start with mechanical grapple fixtures and fiducials; refueling or electrical couplers are added only when the service model requires them.
  • Nothing changes for the first pod. External robotic servicing remains a future enhancement. This entry only equips the future option with standard interface names.