Introduction: An image-guided surgery (IGS) project usually follows one of three camera paths—a standard AimPosition unit, a combined camera-and-accessory package, or a customization discussion—and defining that path early gives the first inquiry a concrete technical and commercial scope.
The camera is one part of a larger navigation system that includes software, instruments, markers, a workstation, and quality documentation. Define the project type—standard integration, combined hardware package, or custom scope—and ask for that scope directly. This structure helps the first supplier response address configuration, interfaces, mounting, and package boundaries without a generic price-only exchange.
Image-guided surgery uses imaging to guide a procedure in real time. In that system, the tracking camera reports where markers and instruments are in space so navigation software can align them with the patient image. AimPosition Series cameras are intended for image-guided surgery and surgical robot integration. They track near-infrared markers and output marker 3D coordinates, 6D tool positions, NIR images, and color images over USB3.0, Ethernet, or optional WiFi. The camera is a component; many IGS projects can start with a standard unit that matches the working volume and an interface the software already handles. Consider a typical planning scenario. A device team has navigation software in beta, three instrument types in development, and a cart-based OR layout. Its fit conditions are simple: the procedure working volume falls within the series' listed Pyramid range, the tool count stays within the 50-tool and 200-marker capacity, the host uses Ethernet or USB3.0, the cart arm can accept the 608.5 × 122.5 × 108.5 mm metal housing at 2.5 ± 0.1 kg without custom mechanics, and the room power can supply PoE or the adapter. When these conditions line up, a standard AimPosition configuration is the most direct path, and the project can treat the camera as a catalog component. Constraints outside that standard envelope—unusual mounting geometry, a working volume outside the listed range, an interface the host cannot adapt to, or marker hardware built into proprietary instruments—point to a customization discussion. That conversation has different inputs, so name those constraints early. A team that needs custom marker geometry should describe that need in the first message instead of relying on a price-only inquiry.
The most useful first message to a surgical navigation camera supplier describes the system the camera must fit. Six items do most of the work: target procedure types, required working volume, number and type of tracked tools, interfaces and data formats the software consumes, mounting and power in the OR layout, and the scope you plan to build in house. Each item changes the scope of the reply. Tool count and marker strategy illustrate the point. A project tracking two rigid instruments needs a smaller accessory scope than one tracking a dozen tools with mixed passive and active markers. The larger project also needs a plan for marker replacement and geometric verification over time. Interface choice has a similar effect: Ethernet or WiFi changes the cabling and power plan compared with USB3.0, and PoE changes what must be mounted on the cart. Mounting and OR footprint determine whether standard mounting hardware fits the cart or mechanical parts need their own discussion. On the software side, the camera's output types—marker 3D coordinates, 6D tool positions, NIR and color images—show how much conversion work sits on your side of the interface. State plainly what you build and what you expect the partner to supply. A team with a mature software stack and a strong mechanical group often wants a camera plus markers. A team assembling a full navigation cart may want camera, markers, tools, workstation, and cabling planned as one configuration. Both are valid OEM/ODM starting points, and stating yours removes guesswork. Project-specific terms such as price, MOQ, lead time, IP ownership, certification coverage, and development schedule are confirmed in that same discussion rather than assumed ahead of it.
A combined package is a set of scope lines rather than a single larger camera order. Each line has its own specification, validation work, and replacement plan once the system is in the field. Camera performance, marker supply, and workstation questions often land with different people, so clear scope lines keep each discussion with the right decision maker.
Within the standard series, the choice is straightforward. The M631 is listed at 0.08 mm RMS with a 96 Hz sampling rate for projects where positional precision matters more than refresh speed. The M632 is listed at 0.12 mm RMS at 300 Hz for workflows with faster tool motion, where a higher update rate helps the display keep pace with the instrument tip. The deciding question is what your software does with each frame and how much latency the workflow tolerates. Interface and power planning belong in the same decision: USB3.0, Ethernet, WiFi, and PoE each impose different cabling, and the +5 °C to +40 °C operating range should match the cart's working environment.
Items that touch the instrument or cart deserve separate treatment. Passive and active markers have their own geometry, attachment method, and replacement cycle. Tracked tools need a defined relationship to the marker set that stays stable across a case. The workstation and cabling form a third line: they determine where the camera sits, how power reaches it, and what the surgical team sees. Planning these as separate scope items lets different groups review each one on its own terms and keeps a marker redesign from reopening the camera specification. Accessory scope and camera body scope stay distinct from the first meeting onward.
Most image-guided surgery projects need a clear decision about how much of the system the camera partner should carry. If the working volume, tool count, interface, and mounting match the standard AimPosition configuration, use the standard product and move to integration. If markers, tools, workstations, and cabling belong in the same delivery, plan a combined package with separate scope lines. If geometry, protocols, or instrument integration fall outside the standard envelope, open a customization discussion with those constraints on the table from the first message. As an optical tracking camera manufacturer working with medical device OEM/ODM teams, AIMOOE supports project scoping through OEM/ODM, custom project discussion, engineering consultation, and system integration support. The conversation can cover camera version, marker and tool options, workstation layout, and the hardware and accessories that complete the package. Share the procedure type, working volume, tracked tool count, interface plan, mounting arrangement, and package scope to open a project discussion around the right AimPosition configuration.
A: A standard unit fits when the working volume is inside the listed range, the tracked tool count stays within the listed 50-tool and 200-marker capacity, the software can use the available outputs over USB3.0, Ethernet, or WiFi, and the camera mounts on the existing cart or arm without custom mechanics. When all four conditions match, the standard AimPosition configuration is the appropriate starting point for integration.
A: Bring the target procedure types, required working volume, number and type of tracked tools, interfaces and data formats the software consumes, mounting and power arrangement in the OR layout, and a clear statement of what you build in house versus what you expect the partner to supply. With these six items, the discussion can move directly to configuration.
A: Passive and active markers, tracked tools, the workstation and its mounting, cabling and power adapters, and any spares plan should each carry their own scope line. They have different validation steps, different replacement cycles, and often different owners inside your organization. Keeping them separate from the camera specification means a marker redesign or workstation change does not reopen the camera decision.
Image-Guided Surgery | National Cancer Institute
Computer-Assisted Surgical Systems | FDA
Robotic surgery - About - Mayo Clinic